Server, storage and site migrations have always been the elephant in the room. IT managers know that it is necessary to reduce costs and improve workload management but cringe over the potential impact to production. In the past, migrations have usually required significant planning, design and downtime, which is no longer acceptable. Now flexible, more efficient workload infrastructure is necessary to reduce costs. A few years ago virtual migrations were no different than any other server or storage migration: P2V products were complex and time consuming - and some P2V solutions haven’t changed. As with any migration, whether converting a physical machine to a virtual workload, new blades or centralizing data to iSCSI storage, once the workload is converted it is usually missing changes that were transacted during start of the conversion.

So, this further complicates the problem: even if the P2V process allows the physical server to be online, how are the changes captured once the conversion begins? Differential tape backup? I don’t think so.

This is the migration paradigm: How are migrations completed while keeping changes in synch and the production systems available to users?

Workload portability is the answer that keeps transactions up-to-date until the physical or virtual workload is ready, eliminating any downtime or user interruption.

What are some of the challenges you face with the P2V or workload migration process?

• Protect Your Home While You Travel, Says Florida Association of Realtors(R)
• CSA Travel Protection Announces: How to Protect Your Vacation Investment
• Protect Your Home While You Travel, Says Florida Association of Realtors(R)