Before you configure a protection policy for asset protection, observe the following points and perform the following actions:
Notes
You can only protect an asset with one policy at a time. 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.
When creating a policy, limit the number of database assets within the policy to under 500 and stagger the start time of replication policies. These actions prevent potential replication failures.
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.
Discovery of a Kubernetes cluster discovers namespaces that contain volumes from both container storage interface (CSI) and non-CSI based storage. However, backup and recovery are supported only from CSI-based storage. If you select a namespace from non-CSI storage, the backup fails.
Optionally, if you want to protect a namespace that contains non-CSI storage, you can exclude the non-CSI PVC from the backup. If excluding the PVC, ensure that such a policy still meets your protection requirements.
Initial configuration
Enable the Kubernetes asset source.
Register the application hosts with
PowerProtect Data Manager.
Add credentials for Kubernetes assets.
Where applicable, enable Changed Block Tracking (CBT).
Deploy
VM Direct protection engines.
Where applicable, configure any necessary Service Level Agreements (SLAs). The
PowerProtect Data Manager Administrator Guide provides instructions.
Objectives
For replication after backup completion,
PowerProtect Data Manager 19.12 or later and application agents 19.12 or later are required. It is recommended that you update the application agents to the latest version.
To move a backup or replica to
Cloud Tier, the corresponding
objectives must have a retention time of 14 days or more.
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 Tierobjective,
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.
NOTE:PowerProtect Data Manager does not support the automatic retention lock (ARL) setting on the
DD system. The option to create a storage unit during protection policy configuration does not support compliance mode retention locking, only governance mode. To use compliance mode retention locking, create and configure a storage unit before you configure an associated protection policy. If you activate retention locking and select a storage unit where the retention lock mode is
None, the retention lock defaults to governance mode. The
PowerProtect Data Manager Administrator 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.
Data is not available for the Topic
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: <>()\