schedule.dat

NAME

SYNOPSIS

AVAILABILITY

DESCRIPTION

FILEFORMAT

DATALIST ; DESCRIPTION ; HOSTNAME ; RETENTION ; COMPRESSION ; SCHEDULE ;

Rows starting with a # are considered as comments. Empty lines are allowed, too.

OPTIONS

DATALIST

name of the data list as defined in the datalist.dat file. For each scheduled DATALIST in the schedule.dat file at least a DATALIST in the datalist.dat file must exist.

DESCRIPTION

description of the schedule.

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.

HOSTNAME

hostname where the schedule should be active.

RETENTION

number of days the data is locked for. If multiple schedules match for a certain day, the schedule having the highest retention will be executed.

If the defined RETENTION is outside the RETENTION_MIN and RETENTION_MAX range as defined in the lots.cfg file, the effective RETENTION is adjusted accordingly.

COMPRESSION

compression mode:

NONE

no compression.

GZIP

use gzip to compress the data. The command executed is: gzip -cv --fast.

COMPRESS

use compress to compress the data. The command executed is: compress -cv.

ZIP

use zip to compress the data. The command executed is: zip.

BZIP2

use bzip2 to compress the data. The command executed is: bzip2 -cv --fast.

SCHEDULE

schedule definitions. This is a space separated list of schedule definitions of the format explained below. A schedule can consist on any combination of the following entries:

DD.

day of the month. This schedule will match each month on the day specified. Therefore the schedule 28. will match each month at the 28th.

DD.MM.

specify day and month. This schedule will match each day of the month every year. Therefore the schedule 04.07. will match on the July 4th every year.

DD.MM.YYYY

precise date specification. This schedule will only match on the precise date. Therefore the schedule 28.01.1986 will only match on the January 28th 1986. It is allowed to specify the schedule entry 00.00.0000 to mark a prepared but not really planned schedule.

WDay

short English weekday name: Mon Tue Wed Thu Fri Sat Sun. This schedule will only match on the weekday specified. Therefore the schedule Fri will match every Friday.

EXAMPLES

#
# var/lots/objects/schedule.dat - schedule and retention information
#
# [00] 30.09.2009 CWa   Initial Version
#
#   LEVEL       RETENTION               BACKUP (= DB export)    => SAVE_SCHEDULING
#   ---------   ----------------------  --------------------------------------------------------
#   Silver      5 Months =>  150 days   Sunday                  => Mon
#   Gold        2 Years  =>  730 days   last day of the month   => 01.
#   Platinum    4 Years  => 1460 days   last day of the quarter => 01.04. 01.07. 01.10. 01.01.
#
#
#DATALIST   ;DESCRIPTION            ;HOSTNAME       ;RETENTION  ;COMPRESSION    ;SCHEDULE;
DB_CEDPROD  ;Silver-Level-Backup    ;adm_ora1_tst   ;150        ;NONE           ;Mon;

DB_COIPROD  ;Silver-Level-Backup    ;adm_ora1_tst   ;150        ;COMPRESS       ;Mon;
DB_COIPROD  ;Gold-Level-Backup      ;adm_ora1_tst   ;730        ;COMPRESS       ;01.;
DB_COIPROD  ;Platinum-Level-Backup  ;adm_ora1_tst   ;1460       ;COMPRESS       ;01.04. 01.07. 01.10. 01.01.;

DB_DMSPROD  ;Silver-Level-Backup    ;adm_ora1_tst   ;150        ;BZIP2          ;Mon;
DB_DMSPROD  ;Gold-Level-Backup      ;adm_ora1_tst   ;730        ;BZIP2          ;01.;

DB_ASYPROD  ;POC-Test-Backup        ;adm_ora1_tst   ;103        ;ZIP            ;13.01.2010;

SQL_plumdb  ;Silver-Level-Backup    ;adm_ora1_tst   ;150        ;ZIP            ;Mon;

SQL_CHaT    ;Silver-Level-Backup    ;adm_ora1_tst   ;150        ;ZIP            ;Mon;
SQL_CHaT    ;Gold-Level-Backup      ;adm_ora1_tst   ;730        ;ZIP            ;01.;

SEE ALSO

NOTES

BUGS

AUTHOR

COPYRIGHT

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.