Configuring a Pool for Incremental Backups

If you want to create a separate pool for incremental backups, be aware that the Backup hierarchy of precedence affects the way the data is stored. If the Level attribute value is "incremental," incremental data is routed to the associated pool but the corresponding changes to the client's file index are not. Backup saves all client file indexes at level 9 to speed the recovery operation, if one is needed.

If the client file indexes do not meet the criteria for the pool associated with the incremental backups, Backup matches the indexes to another pool (usually the Default pool) and looks for an appropriately labeled volume to write to. If you need to recover your data, you might have to use a large number of volumes to recover all your data. Thus, to store the client file indexes along with the incremental backup data and to speed the recovery operation, define the Level value in the Pools resource to accept both level 9 and incremental data.

You can use the Backup preconfigured NonFull pool settings to ensure that the client file indexes belong to the same pool as their incremental backups. When you keep the indexes in the same pool as their incremental backups, you reduce the number of volumes you need for a recovery.