Disaster recovery configuration fails if the lockdown mode on the secondary cluster is enterprise or compliance

Welcome to Cohesity Documentation.

Ask me anything. From setup and configuration to troubleshooting, architecture, features, and release updates, I'm here to help.

AI may make mistakes. Always verify critical information.

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products

Data Security Alliance

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products

Data Security Alliance

Disaster recovery configuration fails if the lockdown mode on the secondary cluster is enterprise or compliance — NetBackup Flex Scale 3.0 | Cohesity Documentation

Home

Veritas NetBackup™ Flex Scale Release Notes

Known issues

Disaster recovery issues

Disaster recovery configuration fails if the lockdown mode on the secondary cluster is enterprise or compliance

Veritas NetBackup™ Flex Scale Release Notes · PDF

Download PDF

If you start disaster recovery configuration on the primary cluster and the lockdown mode on the secondary cluster is not normal mode, then the configuration fails. (IA-36129)

Workaround:

Reconfigure the secondary cluster with normal mode and then perform disaster recovery configuration.

Feedback

Was this page helpful?

If both primary and secondary clusters are down and are brought online again, it may happen that the replication is in error state

Unable to perform a takeover operation from the new site acting as the secondary

Feedback

Was this page helpful?