Covering the Bases: Backup Before, During and After Server Migrations

By Carbonite Guest Blog

By now, you’re undoubtedly aware that Microsoft is discontinuing support for Windows Server 2003 on July 14. Businesses have been preparing to migrate to newer operating systems, but there’s a lot more work to be done. It’s estimated that nearly 24 million environments worldwide are still running Windows Server 2003, which means terrific sales opportunities for VARs like you.

Not only will these businesses be seeking new software, but many of them will upgrade their hardware, as well. Plus, there’s support for the migration itself, in the form of continuity strategies and services. Server migrations can put data at risk—and you’ll set yourself and your customers up for success by bundling a backup plan into their migration package. Then, help customers see that backup has a key role at every stage of a server migration.

Backup Before Migration

It goes without saying that a major move like this requires data backup beforehand. Full server backup with scheduling and bandwidth options can help protect your customers’ businesses without affecting their day-to-day operations.

File system backups, system state backups, and database and application-specific backups all have key roles in smoothing the transition to new server software, and it’s worthwhile to test every required type of backup in the days before migration. This helps ensure that each data set appears in its proper place, so customers are prepared if recovery should become necessary.

Backup During Migration

It’s critical that customers can roll back during migration to recover lost or corrupted data. When a new server is deployed, customers should back up data from both the old and new hardware to enable recovery on either one, if necessary. And system state backups after key configuration milestones can help save time if a rollback is required later. But backups can help with more than just rollbacks; they can also help a business move forward. For instance, database and application-specific backups not only protect data, they can also help port data into a newer version of the same database or application.

With so much at stake, and time always an issue, solutions that offer hybrid backup are extremely useful. They offer fast recovery from local storage, along with the ultimate protection of the cloud.

Backup After Migration

Once migration is complete, a comprehensive server backup plan will protect the new “clean” server deployment and ensure business continuity. This is a perfect time to institute backup best practices if customers haven’t already done so. How much data is backed up—and when it happens—depends on the specific application environment, data volatility and tolerance for downtime. Full server backups, differential backups and Incremental backups all have merits, and most businesses find that a tailored combination of these three types of backup is the best way to preserve and protect data.

Consider Carbonite Server Backup

The bottom line is this: For every customer planning to migrate from Windows Server 2003 in the coming months, it’s worth proposing Carbonite Server Backup to help execute a smooth transition. Carbonite’s server plans offer customizable, comprehensive hot backup, ensuring that critical data is protected with the security and speed of a hybrid solution. You can increase your profits by adding Carbonite as a service to new server hardware bundles, and you’ll demonstrate to your customers that you understand their challenges and care about the future of their businesses.

Learn more about Carbonite Server Backup.

If you’re not already a Carbonite Partner, you’re invited to join today.

Guest blogs such as this one are published monthly and are part of The VAR Guy's annual platinum sponsorship.