Summary
A protection policy is a reusable configuration that defines a schedule for taking snapshots and optionally replicating them to a specified native replication peer or S3 replication peer.
A replication peer is another cluster configured as a destination for native replication.
The protection policy is mirrored to the replication peer, where it can be used for replicating in the reverse direction in the event of a failover.
Question
If we set up native replication between cluster A and cluster B, then the protection policy created on cluster A is mirrored to the replication peer Cluster B
So does this add to the count of protection policy on Cluster B ?
Solution
Yes, since the protection policy from Cluster A is mirrored to Cluster B , this mirrored protection policy is also counted as a protection policy on Cluster B
Further Reading
Also refer to the VAST Cluster Scale Guidelines, which specify the maximum number of protection policies that can be created in a cluster