Skip to main content
  • 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

PowerProtect Data Manager 19.17 Microsoft SQL Server User Guide

Restoring Microsoft SQL Server databases to a virtual machine

Learn how to restore Microsoft SQL Server database backups taken in a PowerProtect Data Manager virtual machine application-aware protection policy.

If replication is enabled for the PowerProtect Data Manager protection policy, you can restore database full and transaction log backups from the primary or secondary DD system . However, when you restore from the secondary DD system, the tail-log backup option is not supported.

Restoring a backup that was moved to the cloud using Cloud Tier

An application-aware workflow supports application-aware full backups that are tiered to the cloud using Cloud Tier. This support is available for Amazon Web Services (AWS) and Elastic Cloud Storage (ECS) profiles.

Before you perform a database recovery from backups that are tiered using an application-aware workflow, the backups must be recalled to the active tier.

When you try to restore a backup after an associated full backup is moved to the cloud using Cloud Tier, the restore fails. The following error message appears:

"reason" : "Missing or invalid value specified for property 'copyId'"

This error occurs when you try to restore one of the following backups:

  • A full backup that is tiered to the cloud.
  • A tail-log backup when the associated full backup is tiered to the cloud.

For example, the following full and tail-log backups are performed at the specified times:

  • FULL1: 10:00 AM. (in cloud tier)
  • TLOG1: 10:30 AM.
  • TLOG2: 11:00 AM.
  • FULL2: 11:15 AM. (in active tier)
  • TLOG4: 11:30 AM.
  • TLOG5: 12:00 PM.

In this case, the restore of the FULL1, TLOG1, or TLOG2 backup fails with the error message because the FULL1 backup is tiered to the cloud. The restore of the FULL2, TLOG4, or TLOG5 backup succeeds because the FULL2 backup is in the active tier.

To resolve this issue, contact the PowerProtect Data Manager administrator to recall the associated full backup (FULL1 in this example) from the cloud tier to the active tier. Then you can perform the restore.

Restoring a tail-log backup when PowerProtect Data Manager is updated before the next scheduled backup

In the following case of a VM Direct Microsoft SQL Server tail-log backup, you must meet specific restore and deletion requirements:

  • You select to perform the tail-log backup during a VM Direct database restore.
  • Before the next scheduled backup of the database, the PowerProtect Data Manager server is updated from a pre-19.17 version to version 19.17 or later.

In this case, you must use the Microsoft application agent for VM Direct SSMS plug-in to restore the tail-log backup copy. You must use the SSMS plug-in because PowerProtect Data Manager cannot discover the pre-19.17 tail-log backup.

NOTE:You cannot use the PowerProtect Data Manager UI to restore the tail-log backup copy. PowerProtect Data Manager also does not delete the tail-log backup copy.

To delete the tail-log backup copy, you must contact Customer Support for assistance.


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: <>()\