Cisco Cisco MeetingPlace Gateway SIM Guia De Configuração Rápida

L1 (Level 1) backup. The L1 backup is an incremental backup. It contains a backup of all the data 
that has been changed since the last L0 backup. It takes much less disk space than an L0 backup; 
however, it cannot be used for full restoration. If the system fails, you must use both the L0 and L1 
backup files to restore data. 

L2 (Level 2) backup. The L2 backup is incremental to the L1 backup, so it needs both the L0 and 
the L1 backups to restore data. 

Cisco Unified MeetingPlace uses a combination of L0, L1, and L2 backups and uses an Informix 
command called ontape for the backup mechanism. 

The database backup file is physically located on the system disk of the Application Server. The system 
disk can contain up to three automatically-created L0 backups: the current L0, plus the previous one or 
two L0 backups. The L1 and L2 backups are also kept there. All of the older backups are removed from 
the system disk during the cleanup process. 

Use caution if you manually modify the backup files on the local disk or in the archive location. For 
successful data restoration, the three levels of backup files must be present in the correct order. For 
example, if the correct L0 and L2 backup files are present while the appropriate L1 backup file is 
missing, then the data cannot be restored. 

You can enable or disable an automatic backup. If the automatic backup is enabled, an L0 backup 
happens twice a week, every Monday and Thursday at 11:00PM, local server time. The L1 backup is run 
each day at 1:00AM, local server time, while the L2 backups are done daily at 4:00AM, 8:00AM, 
12:00PM, 4:00PM, and 8:00PM, local server time. The schedule is stored in the crontab file.

Advanced system administrators can change the frequency of the automatic backups by editing the 
crontab file. Be careful when modifying the cron schedule, which determines the order of the backups.

The automatic backup process also incorporates archiving (if enabled) and cleanup. This ensures that if 
there is a database corruption or disk failure, in the worst case, less than five hours of data is lost.

The cleanup process occurs before every scheduled backup in the crontab file. During the cleanup 
process, the following files are deleted:

Backup files older than seven days. 

Unusable files, such as L1 and L2 backup files that are older than the oldest remaining L0 backup 
file. 

If you disable automatic backups, the cleanup process continues to run as scheduled in the crontab file. 
Therefore, if you want to keep backup files that are older than seven days, you must archive them.