Server Migration: Things to Remember
Migrating servers can be a daunting task. Whether you're upgrading server versions, or migrating from an old server to a new one, there is a lot to consider. Migrations can typically fall into four categories: Physical to Physical (P2P), Physical to Virtual (P2V), Virtual to Physical (V2P), and Virtual to Virtual (V2V). The most common migrations are P2P, however, with the recent boom in cloud computing, P2V and V2V are becoming more popular.
Take Precautions
When migrating servers it's important to note the physical requirements of the system (Operating System and Application requirements) and ensure that you have a fall back solution if the migration fails. A full backup (if not backing up the server currently) or incremental backup should be taken and verified before beginning a migration. For services such as Active Directory, it is considered best practice to take a Windows system state backup in case there is a need for a restore.
Understand the Differences
Performing a P2V is usually the easiest way to migrate a server because a virtual machine can use fewer resources than a physical server would. The ability to monitor the guest Operating System from the host environment is a great advantage. This gives the administrator the ease of changing resources on an as needed basis (dynamically), compared to the static resources allocated to a physical machine. With newer backup technologies, such as Datto's SIRIS, migrations of a physical to virtual server is simplified. With the ability to share out vmdk or vhd files, a user can copy over the files to the VM host and instantly create a virtual machine that boots from these files.
Do Your Homework
The most fundamental rule that should always be remembered is to never forget the basics. As each server is a unique combination of hardware, software and individual setup preferences, it's best to assume that any technological process may not work perfectly right out of the box. Migrations that are successful should be planned, prepared, predicted, and then finally executed. Before you attempt to migrate your server, make sure you understand the specific steps for your particular hardware and software setup. Server Migration is performed differently on a case by case basis. Nothing beats taking the time to read the documentation that came with your specific device before starting the process.
Suggested readings
Microsoft Migration Planning Process
David Lasecki is a Technical Support Engineer at Datto, Inc.
Questions? Comments? Send them to blog@dattobackup.com.
