1. Proposed title of this feature request
The current implementation of ACS does not have HA/DR capabilities. Per docs, there are only back and restore procedures.

2. What is the nature and description of the request?
The customer's initial plan was to simply spin up a new cluster and re-introduce the secured clusters to a newly built central. This would result in a loss of data from the old DB and is not acceptable to the security team at the customer (MUFG). Beyond this, the idea to backup a central instance and restore in a new cluster would conceptually work, if the secondary cluster maintained the same name. Unfortunately, cluster DNS differs. I assume this would create issues with both certs and data in the DB which contains the original cluster name.

3. Why does the customer need this? (List the business requirements here)
Without a DR plan, CU does not want to sign off to prod. For now, the architect on-site approach is to buy time with the backup and restore options that have been discussed earlier, then sort out active:active or active:passive in Postgres/Crunchy. If the latter is not planned, it is something we should discuss in depth, internally as many of the financial institutions have DR requirements. (There are some options within ODF storage for replication but it is unclear on utilizing the present data on a cluster with a different name, certs, etc.)

4. List any affected packages or components.