PowerProtect Data Manager 19.17 Microsoft SQL Server User Guide

Notes

• For each database that you add as an asset in a protection policy, ensure that the database has only one hostname. A single database must not have more than one hostname.
• If a database is protected in an Always On availability group, you cannot configure standalone backups of that database in a protection policy group.
• You can only protect an asset with one policy at a time. If the asset type supports protection rules, assets can move between protection policies depending on the protection rule priorities. Protection rules do not automatically move assets that were manually added to a policy to a different policy.
• Before scheduling weekly, monthly, or yearly backups, set the PowerProtect Data Manager time zone to the local time zone. Otherwise, the backup still runs but is triggered based on the PowerProtect Data Manager time zone.
• Policy-level credentials are mandatory. Credentials that you set at the asset level and host level take precedence over the credentials that you set at the protection policy level. Asset-level credentials have the highest precedence.
• For database backups, PowerProtect Data Manager chains the dependent backups together. For example, the incremental or transaction log backups are chained to their base full backup. The backups do not expire until the last backup in the chain expires. As a result, all incremental and transaction log backups are recoverable until they have all expired.
• When a new asset is added to a protection policy, the asset is not protected until the next full backup runs, whether or not the asset is added within the backup schedule window. To immediately start protecting the asset, run a manual full backup of the entire policy from the policy page or the newly added asset from the assets page.

Initial configuration

• Enable the Microsoft SQL database asset source.
• Review the authentication requirements for a Microsoft SQL database.
• Add any required Microsoft SQL database credentials.
• Set the sysadmin privilege for the Microsoft SQL database hosts.
• Register the application hosts with PowerProtect Data Manager.
• Perform a discovery of the application hosts.
• Where applicable, configure any necessary Service Level Agreements (SLAs). The PowerProtect Data Manager Administrator Guide provides instructions.

Objectives

• To move a backup or replica to Cloud Tier, the corresponding objectives must have a retention time of 14 days or more.
• The retention period cannot be less than any associated replication frequency. If you set a shorter retention time this value automatically updates to match the replication frequency.

Storage

• Add protection storage.

  The PowerProtect Data Manager Administrator Guide provides more information about working with storage units, such as the relationships between storage units and policies, security considerations, and applicable limitations.

• Before you add a replication objective, add remote protection storage for the replication target.
• Before you add a Cloud Tier objective, PowerProtect Data Manager requires:
  • Protection storage set up for Cloud Tier, with the system passphrase set.
  • The discovery of protection storage with a configured Cloud unit.
  • A configured and running data movement schedule on the cloud storage unit.
  The DDOS Administration Guide provides more information.

Networking

If applicable, complete all of the virtual network configuration tasks before you assign any virtual networks to the protection policy. The PowerProtect Data Manager Administrator Guide provides more information.