Explaining the Device Migration Process
Topic
This article explains the process of submitting a Device Migration with support and prerequisites for performing a device migration.
Environment
- Datto SIRIS
- Datto ALTO
- Datto NAS
Description
A device migration is the process of moving local data from one device to another and re-associating the corresponding offsite data. Device migrations are usually used to upgrade a device and, to a much lesser extent, hardware corruption or load balancing. The original device must be able to perform the tasks necessary for a device migration.
Generally, device migrations transfer at roughly 1TB per day. Network speeds or device-to-device connections will affect this rate. Once the local agents datasets are moved to the destination device, the offsite data can be re-associated to the new device, if desired.
Prerequisites
-
A device migration cannot be performed while any restores are active on the source appliance. Restores include File Restores, Volume Restores, Image Exports and Virtualizations. Remove all restores before initiating a device migration, they can not be migrated.
-
Both devices will need to be on-site and checking in before starting the migration process.
-
The new device will also need to be registered before the migration can be started.
-
If your device migration involves the transfer of ownership of data or equipment from one Managed Services Provider to another, both parties must consent to the transfer. Contact your Sales Executive for guidance if there are any concerns or ambiguities.
Important Considerations
-
Offsite Synchronization will need to be paused on both of the devices, during the migration process.
-
A window for the cutover will need to be established, where the backups will need to be paused and the shares on the device will be inaccessible. It is recommended to pause these for the entirety of the migration if possible.
-
The migration process is a manual support procedure. Once you are ready to begin the migration, please contact Datto Technical Support.
-
Rescue Agent datasets will take more space once migrated, if there is local backups associated with the Rescue. The reference to the source is removed and will take up the space of a new base image for the protected machine. Please confirm the destination will have the required space available before proceeding.
Information to Provide Support
The following information will need to be provided to support, to start the migration procedure.
- Source Device Serial Number:
- Destination Device Serial Number:
- Are we migrating local data, offsite data, or both?
- Are we migrating all agents or shares (Y/N)?
- If not specify what agents or shares need to be migrated:
- Can backups be paused during the migration process Y/N (please note backups will need to be paused in order to complete the local migration)?
- Are shares being migrated (Y/N)?
- If Yes, please be advised that all users will need to be disconnected during a cutover window for the shares to be migrated.
- When can the device migration be started?
- Have you verified that all restores (local, offsite) have been removed?