→ Applies to: SynetoOS 6.x
By design, when a VM is migrated from one site to another and registered at the destination, it remains visible at the source site as unregistered. This is expected behavior and persists until a replication relationship is established from the destination site back to the source. Once reverse replication is configured and the destination site begins replicating the VM back to the source, the original VM entry is automatically removed from its previous location and appears under the Replicas section.
Step 1. Login to SynetoOS GUI
https://<your_ip_address_or_hostname>
Step 2. Add Replication Target ("How to Manage Replication Targets in SynetoOS 6")
IMPORTANT
Configure all nodes as mutual replication targets to establish bidirectional replication across the entire cluster. This creates a full-mesh topology in which every node both sends and receives replicas to and from all other nodes. If replication targets are already configured, skip this step.
Step 3. Configure a SLA policy to replicate (“How to Configure a SLA policy to Replicate on a Secondary System in SynetoOS 6”)
If the SLA policy is already configured, this step is not required
Step 4. Protect VM ("How to Protect a VM in SynetoOS 6")
If the VM is already protected, this step is not required
If the VM is not yet protected, it is necessary to wait until the first recovery point is completed. The initial backup will be a full backup of the entire VM
Step 5. From Virtualization menu, click on Virtual machines
Step 6. Select the virtual machine you want to migrate
Step 7. In the top right corner, click on the three dots and then on Migrate
IMPORTANT
If the VM is not powered off at the time of migration, the system will automatically shut it down before the process begins.
Step 8. Fill in the required fields and click on Next button
IMPORTANT
It is possible to register it either during the migration process or manually at a later stage
Step 9. Cold Migrate the VM
Step 10. Select the SLA policy and click on Next
IMPORTANT
A protection policy from the replication target can be selected at this stage or configured at a later time.
The choice of whether to assign an SLA policy at this stage determines the resulting state of the original VM on the source site.
- Scenario 1: SLA Policy Assigned If an SLA policy is assigned during this process, the first replication to the destination site will automatically convert the original VM on the source site into a replica.
- Scenario 2: No SLA Policy Assigned (recommended when replication will be configured later) If no SLA policy is assigned, the VM will remain in an unregistered state on the source site until a replication relationship from the destination site back to the source is established.
Step 11. Check the entire configuration and click on Migrate
