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.11 Microsoft Exchange Server User Guide

Recall and re-tier the cloud tier backup

You can restore directly from a cloud tier backup. You can also manually recall the cloud tier backup and then restore from the local copy.

The direct restore from the cloud tier backup is identical to a normal restore operation. PowerProtect Data Manager software recalls the backup from the cloud tier to the local (active) tier and then restores the recalled backup.

NOTE

When a backup is recalled from the cloud tier to the active tier, the copy is removed from the cloud tier.

You can restore from a cloud tier backup to either a backup objective or replication objective. For restore to a replication objective, ensure that you select a cloud tier enabled DD.

As an alternative, you can manually recall the backup from the cloud tier and restore the local copy:

  1. In the PowerProtect Data Manager UI, go to Infrastructure > Assets and select the Exchange Databases tab.
  2. Select the required asset, and then click View Copies.
  3. Select the backup in the cloud, click Recall, and then specify how long to keep the copy on the active tier.

    A job is created to recall the backup copy from the cloud tier for the selected asset. The copy moves from the cloud tier, and the status changes from Cloud to Local_Recalled.

  4. Select the recalled asset, and then click Restore.

To re-tier the recalled copy, select the recalled copy and click Re-tier.

To change the retention period for the recalled copy, select the recalled copy and click Edit Recall Retention.


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