Changing Centera Compliancy

You can change the compliance mode however once changed you will not be able to change it back. I do believe there are license requirements but am not familiar with whats involved in the aspect.

It does not make much sense to me why you would want one cluster basic and the other compliant in a replicated environment. Basic has no retention enforcement while compliant does - Allowing deletes to occur on one and not the other can be accomplished by removing the "replicate delete" functionality setup within the replication configuration if this is your objective.

Hi Naty

Replication and Compliance are licenses you license on a per system level.

The reasoning applies even if you do not replicate all pools. I have found it to be troublesome not to create the pools on both sides. It results in profiles that have a home pool in the source system that does not exist on the target. As the Centera is replicated the profile needs to be able to access the target anyway so something exists in the target.

We create all pools and profiles in both systems, do not grant the replication profile capabilities in non-replicated pools and also do not replicate the pools we do not want. Then when you look at a system all it takes is a show replication detail and a show pool capacity on both systems to verify everything is as it should.

This also facilitates things if a customer then suddenly wants to replicate a pool that wasn't. Just say it's replicated, grant the capabilities to the replication profile and perform a full restore.

Holger

Hi Naty

Enabling Governance Edition or Compliance Edition Plus require the appropriate license. EMC will need to change your system to the new mode as it requires the emcservice login and the GlobalServices Version of the viewer.

For the current setup you could enable just on one. Later on if you were to export / import pools for replication configuration you could only export on the one that is in basic mode. You cannot import pool definitions from a GE or CE+ cluster in a basic mode cluster.

The issues that Dennis mentions are very valid points too. It does not make sense to have only one cluster in any of the compliance modes and the other not. The delete would not get repliated if the target were in compliance and the source in basic mode. All your deletes would end up in the parked entries for as long as the retention period has not expired. This is something you do not want to happen.

I suggest you buy the amount of 2/4 Node Compliance Licenses you need for both of your clusters and then change both of them to it.

Best regards, Holger