Protection rules comprise one or more conditions that select matching assets and automatically assign them to a corresponding protection policy.
PowerProtect Data Manager applies these rules to assets at discovery time.
You can apply protection rules to policies for the following asset types:
Virtual machine
File System
Kubernetes
Microsoft Exchange
Microsoft SQL
Network Attached Storage (NAS)
Oracle
SAP HANA
PowerStore block volumes
Before defining a protection rule, note the following:
Creating protection rules requires at least one existing protection policy.
An asset can only belong to one protection policy.
Assets can move from one policy to another policy based on the priorities of the protection rules. You can manually move an asset into a protection policy and override automatic placement through protection rules. Manual assignment protects the asset through the specified policy but protection rules no longer apply to that asset. To apply protection rules again, remove the asset from the protection policy.
To ensure the protection of homogeneous assets, the protection rule must specify a storage asset type.
For virtual machine protection policies, virtual machine tags created in the
vSphere Client can only be applied to a protection rule.
A virtual machine application-aware protection policy that protects a Microsoft SQL Server Always On availability group (AAG) must include all the virtual machines of the AAG in the same protection group. Failure to meet this requirement might result in Microsoft SQL Server transaction log backups being skipped. Ensure that the protection rules are designed to include all the AAG virtual machines.
For Oracle assets, ensure that the Oracle protection rules do not use the DB ID and Oracle SID Name field settings that were supported with versions prior to
PowerProtect Data Manager 19.6.
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: <>()\