Pre-P2V
- Cleanup Irrelevant Data
- Don’t bring over that downloads folder on every server full of drivers, hotfixes, patches, service packs, etc.  Remember storage is now shared among many VMs now, try not to duplicate things like that.
- Stop transactional services during P2V
- Disable Windows Updates
- You don’t want your source to reboot due to automatic updates mid-P2V
- Do not resize volumes during P2V
- Resizing volumes will increase P2V time significantly because instead of doing a block-level copy the convert would have to use file-level copy
- Set Target disks to Thin
- Take advantage of thin provisioning–make sure you have vCenter Alarms setup to alert you when datastores near capacity
Post-P2V
- Move the Page File to a seperate volume (if it isn’t already)
- If you are moving away from traditional backup methods to new vStorage methods you can’t exclude the page file from backups typically–however if it’s on a dedicated volume (separate vmdk) you can typically exclude it then
- Don’t Team NICs
- You should build redundancy at the vSwitch level and use a single NIC for the VM (having a separate NIC connected to another vSwitch for backups, or Internal/External Interfaces is still ok)
- Cleanup
- Get rid of all the extra software/agents physical servers require–Dell OpenManage, HP Insight, Broadcom/Intel Teaming Utilities – If your using Dell Servers use my Cleanup Script to automate the process
Leave a Comment