We have 4 servers in a single DAG over 2 sites. There are DB partnerships in both directions
To ensure we stick to best practice we need to create a new DAG and migrate 2 of the servers to the new Dag. This is because the DAg primary server keeps switching between the 2 remote sites at will and we have the potential for split brain syndrome.
Can we evict the active server from the DAG while the Databases are still ownded by that MBXserver? We were going to use a swing server to complete the migration by using DB portability to mount the DB's on the standalone server then re-mount the DB on the existing server once the new DAG was online and the existing server a member of it.
However there is a concern with the storage It is also against best practice to do so. the official thread is to build a new mailbox server and migrate all the mailboxes to new databases.
All the referencing I have shows that the database cant be evicted while holding DB copies as part of a DAG.
To be clear,
1) We would remove all the passive copies leaving only the live copies on the server we want to evict.
2) Can we interactively update the DB master ? This seems to be the issue with evicting from the DAG as the DB master will remain as the DAG name, not the host server.
3) Is this method feasible, has anyone on EE done it this way before.
4) I would prefer to complete this using the BP method but its not 100% feasible.
I will try and deploy a test server