Example: Scheduling Large Client Filesystems

At a moderate backup rate of 400KB per second, a full backup for a client with 10GB of data takes about 5.5 hours to complete. Consequently, it may not be convenient to complete a scheduled, full backup for client save sets as large as this because of the amount of time the backup takes.

You can schedule the client's disk volumes for backup at different times by separating them into different backup groups. When you split one client's save sets into multiple backup groups, you back up all the client's files, but not all at once. It is less time-consuming than a full backup of all the local data at one time.

To back up the client's filesystems individually, add and configure the same client several times addressing the different filesystems in the Clients resource. For example, configure the first client resource to back up one filesystem, /usr, with one backup schedule in one group, and configure the second client resource to back up another filesystem, /var, with a second backup schedule in another group.

When you create separate backup schedules and explicitly list save sets, any files or filesystems not included in an explicit list are omitted from backup. This includes any new disk volumes that are added to the system. This risk of omission does not exist when you enter the special value "All" in the Save Set attribute; Backup automatically adds the new disk volumes to the backups.