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 Cyber Recovery User Guide

Policy actions

The Cyber Recovery UI supports the Secure Copy Analyze, Secure Copy, Sync Copy, Copy Lock, Sync, and Copy policy actions.

NOTE If you enabled the automatic retention lock feature, the Cyber Recovery UI only supports the Secure Copy Analyze, Secure Copy, Copy Lock, and Sync policy actions.
Copy
A Copy action makes a point-in-time (PIT) copy of an MTree's most recent replication in the Cyber Recovery vault and stores it in the replication archive.

This figure illustrates a Copy operation.

Copy Lock
A Copy Lock action retention locks all files in the PIT copy.
Sync
A Sync action (or replication) replicates an MTree from the production system to the Cyber Recovery vault, synchronizing with the previous replication of that MTree. This figure illustrates a Sync operation.
NOTE From the CRCLI, you can perform a Sync action to a system other than the Cyber Recovery vaultDD system. Replicate an MTree from the Cyber Recovery vaultDD system to the production DD system or an alternate DD system. For more information, see Recovering data to an alternate DD system.
Sync Copy
A Sync Copy action combines the Sync and Copy actions into one request. It first performs the replication and then creates a PIT copy.
Secure Copy
A Secure Copy action performs a replication, creates a PIT copy, and then retention locks all files in the PIT copy.
NOTE You can also retention lock an existing PIT copy as described in Securing a copy.
Secure Copy Analyze
A Secure Copy Analyze action performs a replication, creates a PIT copy, retention locks all files in the PIT copy, and then runs an analysis on the resulting PIT copy.

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