This article explains the process, rationale, and prerequisites for performing a device migration.
A device migration is the process of moving data from one device to another. Device migrations are usually in response to either hardware corruption or device upgrades and, to a much lesser extent, 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.
Most device migrations begin through contact with either Datto Support or your Sales rep. However, if you do need to initiate a device migration, you should file a ticket and include the following information:
- If the device should continue taking backups during the migration
- If you need to move your user and group accounts from the old device to the new
- If you would like the transfer to be done NIC-to-NIC or over the network
- If you will be re-purposing the old device
- If you want the new device to continue backing up to the same chain of data or if you want to begin a new chain
- If you would like your offsite data reassociated from your old device to your new device.
Refer to your User License Agreement for details if you choose to disassociate your old data chain.
Data migrations cannot be performed while any restores are active on the source appliance. This includes file restores and virtualizations. You must remove all restores before initiating a device migration. Restores cannot be migrated.
Be sure to have the new device in-hand and to check that both devices are checking in before initiating the migration process.
During the migration, your Technical Support Engineer will broadly follow these steps:
- Pause local and offsite operations on the original device.
- Install sshpass onto the destination device, allowing Datto to create a secure shell using passphrases.
- Perform tests to verify the destination device is a viable backup environment.
- Sync data on the original device, verify that all necessary snapshots completed syncing, and then sync additional utilities (SAMBA, ShadowSnap keys).
- Transfer user and group accounts to the destination device, if necessary.
- Re-pair ShadowSnap agents to the destination device.
- Re-create original directories in the destination device.
- Begin re-enabling local backups on the destination device.
- Back on the source device, re-enable offsite syncing and send file creation.
- Re-enable backups.
- Transfer NAS Shares at a scheduled window when your NAS Shares are not in use.
- Re-associate your offsite data from your old device to your new device.