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.9 Administration and User Guide

PDF

Before you create a protection policy

Consider the following best practices before creating a protection policy.

  • An asset can be protected by only one policy at a time. Assets can be moved from one policy to another policy based on the priority of protection rules. In cases where protection rules result in assets moving from one policy to another, any assets that were manually selected for inclusion in the policy, however, will not be moved to a different policy.
    NOTE If a SQL Server is hosted on a virtual machine, you can protect the SQL database with an application-consistent backup without interfering with the SQL agent-based backup.
  • When creating a policy, limit the number of database assets within the policy to under 500 and stagger the start time of replication policies to avoid potential replication failures.
  • Before adding replication to a protection policy, ensure that you add remote protection storage as the replication location. Add protection storage provides detailed instructions about adding remote protection storage.
  • Before you perform any backups on a weekly or monthly schedule from the protection policy, ensure that the PowerProtect Data Manager time zone is set to the local time zone.

Understanding backup terminology and managing backup frequency

When scheduling backups in a protection policy, be aware of the following:
  • Different backup policy types can use different terminology to describe available backup levels. This terminology can differ not only between 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.

Refer to the following table to understand the different backup levels provided by each protection policy and to manage backup frequencies.

Table 1. Backup terminology and frequency
Protection-policy backup types Available backup levels Description Equivalent traditional terminology Minimum frequency recommendation
VMware application-aware Full Backs up all the blocks. Full Monthly
Synthetic Full Backs up only the blocks that have changed since the last synthetic-full or full backup, and then performs an operation to merge those changes with the last synthetic-full or full backup in order to produce a full backup in storage. Only the changed blocks are actually 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
Log Backs up the transaction logs. - 30 minutes
VMware crash-consistent Full Backs up all the blocks. Full Monthly
Synthetic Full Backs up only the blocks that have changed since the last synthetic-full or full backup, and then performs an operation to merge those changes with the last synthetic-full or full backup in order to produce a full backup in storage. Only the changed blocks are actually 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
Kubernetes crash-consistent Full Backs up the namespace metadata and persistent volumes. Full Daily
Synthetic Full Backs up the namespace metadata, the blocks that have changed for persistent volumes on VMware first-class disks since the last synthetic-full or full backup, and all other persistent volumes in full. Although not all data has actually been copied over the network, the result is still a full backup in storage. A combination of full and differential backups are performed, followed by a merge operation that produces a full backup in storage. 12 Hours
File System centralized Full Backs up all the data. Full Monthly
Synthetic Full Backs up only the data that has changed since the last synthetic-full or full backup, and then performs an operation to merge those changes with the last synthetic-full or full backup in order to produce a full backup in storage. Only the changed blocks are actually 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
Exchange centralized Full Backs up all the data. Full Weekly
Synthetic Full Backs up only the data that has changed since the last synthetic-full or full backup, and then performs an operation to merge those changes with the last synthetic-full or full backup in order to produce a full backup in storage. Only the changed blocks are actually 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
SQL centralized Full Backs up all the data. Full Daily
Differential Backs up only the data that has changed since the last differential backup, or the last full backup if there are no other differential backups. A differential backup is performed, followed by a merge operation that produces a full backup in storage. 12 hours
Log Backs up the transaction logs. - 30 minutes
Oracle centralized Full Backs up all the data. Full Daily
Incremental Cumulative Backs up only the data that has changed since the last full backup. Differential 12 hours
Incremental Differential Backs up only the data that has changed since the last incremental differential backup, or the last full backup if there are no other incremental differential backups. Incremental 6 hours
Log Backs up the archived logs. - 30 minutes
SAP HANA centralized Full Backs up all the data. Full Daily
Differential Backs up only the data that has changed since the last full backup. Differential 12 hours
Incremental Backs up only the data that has changed since the last incremental backup, or the last full backup if there are no other incremental backups. Incremental 6 hours
VMAX storage group centralized Full Backs up all the blocks. Full Daily
Synthetic Full Backs up only the blocks that have changed since the last synthetic-full or full backup, and then performs an operation to merge those changes with the last synthetic-full or full backup in order to produce a full backup in storage. Only the changed blocks are actually 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 this include, but are not limited to, 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.
  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: <>()\