Migrating Instances
Instances can easily be migrated between servers, data centers, or even between cloud providers. Migrating an instance shuts down the instance and creates and starts a new instance on the target server.
Migrating Stateful Instances
When migrating a stateful instance with a volume attached, the instance is shut down and Cycle compresses the volumes and streams them to the destination server so they're available. The volume contents are migrated with the instance to the new server.
The original instance will not be deleted until the purge time is reached, in case the migration needs to be reverted. The purge time for stateful instances is 3 hours.
Migrating Load Balancers
Due to load balancer instances having publicly assigned IPv4 addresses, it isn't possible to migrate instances of this service.
In order to achieve a similar result, a new instance must be created explicitly:
- Create a new load balancer instance on a different server.
- Allow the new load balancer instance to come online.
- Once online, delete the old load balancer instance.
Bulk Migration
To migrate all instances from a server in a single action, use the server evacuation functionality.
Reverting a Migration
Migrated instances can be reverted quickly. A reverted migration runs the same process as the original migration, in reverse.