cmsadm:backup performs a UNIX command that states, essentially "Copy every
single file stored in memory in the system to the backup tape."
CMS data collection must be shutdown while running a cmsadm backup, which can take from one to
several hours, depending on the size of the system and the type of tape drive being used.
The second type of backup is referred to as a “full maintenance” backup, “CMS full maintenance”
backup, “CMS maintenance” backup or “maintenance” backup. This is the type of backup performed
when the backup is done from within the CMS application, via the “Maintenance:Back Up Data” menu
item.
In the input screen displayed via the Maintenance:Back Up Data menu, you can choose which of the two
types of maintenance backups to perform: incremental or full. If full is chosen, all of the data (system
administration, ACD administration, historical, or specific historical data files) will be backed up.
Typically, all of the CMS data possible is selected and backed up. If incremental is chosen, all of the data
that has changed since the last backup (full or incremental) will be copied to the tape.
The recommended frequency of running backups:
· cmsadm backups should be run monthly, and before/after any upgrades.
· CMS Full Maintenance backups should be run weekly.
· CMS Incremental Maintenance backups should be run daily.
The cardinal rule of backups applies here - you cannot have too many backups! The last two types
of backups can be run automatically via timetables and require only the effort of keeping track of the
tapes used to make them. The cmsadm backup always requires manual intervention and requires
downtime for the CMS; you’ll never be so glad to have it as when it’s needed.
Hope this explains a bit...
John