Using Deduplication › Back up Data with Deduplication › How Staging Jobs Work with Deduplication › Considerations for Specifying Deduplication Device Copy and Purge Policies

Considerations for Specifying Deduplication Device Copy and Purge Policies

Consider the scenarios that follow when specifying deduplication copy and purge policies:

• If you use a deduplication device as the destination in a non-staging backup job, you may configure purge policies. Click Deduplication Policy. The policy is enabled by default.
  • On the Full Backup and Differential/Incremental Backup tabs, specify a purge policy, if desired. The default setting is 4 weeks for full backups and 2 weeks for incremental/differential backups.
  • On the Miscellaneous tab, choose the desired options.
    • Purge cancelled sessions from disk -- Use this option to delete sessions from the destination device after a backup to destination device is cancelled.
    • Purge failed sessions from disk -- Use this option to delete sessions from the destination device after a backup to destination device fails.

    Both options help reclaim disk space as quickly as possible.

• If you use a deduplication device in a staging job as a staging device, you can specify both copy and purge policies by clicking the Policies tab. For more information, see Specify Copy and Purge Policies for Disk Staging Backups.
• In staging jobs where you use deduplication devices for both staging and destination locations, your jobs will have two purge policies.

Purge policy is always enabled. You cannot disable purge, but you can adjust the purge schedule.

More information:

Back up Data with Deduplication in a Staging Backup Job