Introduction and Prechecks
If there is a request to move DualShield Replication cluster to a new set of servers the best approach would be to Clone just one dualshield/mysql node in the cluster using the instructions as written here...
How to move DualShield to a new machine with the same Windows OS System Type
Then create a new replication cluster using the DualShield Assistant tool to clone from the new server and set up a new replication cluster.
However, this may not be 100% straightforward as there are a couple of factors to consider, such as the size of the audit log table , eg
And the amount and total size of the existing binary log files from the current replication cluster.
Ideally, you should have a few..
..but, if you have a large amount, dating back a long time, together with a large audit log table, cloning will take too long, or may even fail.
The easiest way to check the size of your audit log table is to go to C:\Program Files\Deepnet DualShield\mysql\data\dualshield and search for the log.idb file
In the screenshot posted above 3Gb is acceptable and should not hamper the cloning, but if you have 10, 20, or 30 Gbs + then you will need to cut this down.