Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

PowerProtect Data Manager 19.15 Microsoft Exchange Server User Guide

PDF

Protection policy best practices

Before you create a protection policy, note the following best practices:

  • In the Protection Policies window, you can export protection policy data by using the Export All functionality.

Understanding backup terminology and managing backup frequency

When scheduling backups in a protection policy, be aware of the following:

  • Different protection-policy types can use different terminology to describe available backup levels. This terminology can differ not only between protection-policy types, but also from traditional terminology.
  • To avoid high CPU usage that can lead to failure issues, do not schedule backups more often than recommended.

To understand the different backup levels to manage backup frequencies, see the following table.

Table 1. Backup terminology and frequencyTable of backup terminology and frequency
Protection-policy types Available backup levels Description Equivalent traditional terminology Recommended minimum backup interval
Microsoft Exchange Server centralized Full All the data is backed up. Full Weekly
Synthetic Full Only the data that has changed since the last synthetic-full or full backup is backed up. An operation to merge these changes with the last synthetic-full or full backup produces a full backup in storage. Only the changed blocks are copied over the network, but the result is still a full backup in storage. A differential backup is performed, followed by a merge operation that produces a full backup in storage. 12 hours
NOTE:In some situations, a full backup might be performed even though a synthetic-full backup was scheduled. Possible reasons for a full backup include the following:
  • There is no existing full backup.
  • The size of a volume has changed.
  • There has been a file path change.
  • The asset host has been rebooted.

You can increase the backup frequency of a protection policy by scheduling more full or synthetic-full backups with different retention times to meet your requirements.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\