In this file sets of files are defined that can be scheduled to be saved in the schedule.dat file.
DATALIST ; DESCRIPTION ; DIRECTORY ;
Rows starting with a # are considered as comments. Empty lines are allowed, too.
It is allowed to have multiple lines in the file having the identical DATALIST definition, but different DIRECTORY entries to enable to save data from different directories with one schedule. If multiple lines are defined, ensure that all DESCRIPTION entries of those lines are identical due to the fact that only the first DESCRIPTION definition of a DATALIST will be saved in the lots job and conserved for the duration of the data retention.
Be aware that this should be a meaningful description due to the fact that this data is saved for a long time and people having done the definition might have moved on before the data might be needed for restore.
To resolve the files/directories to be saved, lots uses
find DIRECTORY -print
internally. Therefore if you are unsure if your definition is correct, use this command for verification or start a collect run using ' lots -a collect -d DATALIST ' to verify the setting.
# # var/lots/objects/datalist.dat - data save definition # # [00] 30.09.2009 CWa Initial Version # #DATALIST ;DESCRIPTION ;DIRECTORY; DB_CEDPROD ;Database, PRODUCTION, PReCED ;/orara/be/CEDPROD/export/daily/g0; DB_COIPROD ;Database, PRODUCTION, OpenCO ;/orara/be/COIPROD/export/daily/g0; DB_DMSPROD ;Database, PRODUCTION, Phoenix DocumentManagementSystem ;/orara/be/DMSPROD/export/daily/g0; DB_ASYPROD ;Database, PRODUCTION, AutoSYS Job Scheduler ;/orara/be/ASYPROD/export/daily/g0; SQL_CHaT ;MSSQL Database, PRODUCTION, CHaT ;/dat/sqlra/be/CHaT/export/daily/g0; SQL_plumdb ;MSSQL Database, PRODUCTION, plumdb ;/dat/sqlra/be/plumdb/export/daily/g0;
This is free software; see edrc/doc/COPYING for copying conditions. There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.