iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
The safest VMware migration starts with an independent, verified image-level backup of every virtual machine and critical host configuration. Keep that restore point outside the source cluster, test a restore in an isolated network, and only then move workloads. Use compute vMotion or Storage vMotion when the VMware licensing, compatibility, and storage design support them; use a backup-orchestrated method such as Veeam Quick Migration for cross-boundary or license-limited moves. Preserve the restore point until the new placement, networking, encryption, applications, monitoring, and backup jobs all pass validation.
This runbook explains how to prepare, choose a migration method, execute a pilot, restore to another host or datastore, and prove that a recovered VM will boot without exposing production systems to duplicate identities or network traffic.
What to protect before moving a VMware VM
A migration changes where a VM runs, but it does not remove the need for a recoverable copy. Broadcom’s VMware migration guidance calls for backing up VM data, host configurations, and critical workloads before migration, including a full image-level backup before shutting down a host. Treat the backup as your rollback point, not merely as a compliance artifact.
Inventory each VM and its dependencies
Build a migration record for every VM. Include the VM name, owner, application role, power state, ESXi host, cluster, datastore, network or port group, snapshots, guest operating system, VMware Tools status, encryption state, SCSI bus-sharing mode, recovery-point objective, recovery-time objective, and the person authorized to approve rollback. Record upstream and downstream dependencies such as domain services, databases, message queues, licensing servers, and shared file systems. Group VMs that must move together and assign a migration window for each dependency-aware batch.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
Identify conditions that affect relocation
- Check CPU compatibility between source and destination hosts. A vMotion can fail or require an Enhanced vMotion Compatibility configuration when CPU generations differ.
- Record whether the VM uses shared disks, physical-mode RDMs, mounted ISO files, passthrough devices, or SCSI bus sharing. Veeam documents SCSI bus sharing as a blocker for Quick Migration.
- Note encrypted VMs and encrypted datastores. VMware vMotion does not automatically retain VM encryption settings, so encryption must be verified and, where necessary, re-enabled after the move.
- List snapshots and confirm that application owners understand whether they are temporary operational artifacts or part of an approved recovery plan. Do not use a snapshot as your only migration backup.
- Measure the target datastore’s usable free space, including room for VM disks, configuration files, swap, snapshots created during the move, and normal operational headroom.
Build and verify an independent restore point
Run a full image-level backup for every VM in scope and back up the critical configuration of the ESXi hosts and management infrastructure. A full image contains the VM’s configuration and virtual disks so it can be restored to the original location or a different host and datastore. Veeam’s full-VM restore workflow requires at least one successfully created restore point.
Keep the copy independent of the source cluster
Store the backup on a repository that will remain available if the source cluster, vCenter, or datastore is unavailable. Confirm that the repository has capacity for the full backup, incremental chains, retention policy, and temporary files used during restore. If the repository is on the same storage system or depends on the same failed management plane, it is not an adequate sole rollback copy.
Verify the backup, not just the job status
After the job reports success, open the restore-point details and verify that all intended disks and the VM configuration are present. Check that the restore point is readable from the repository, retained for the entire migration window, and protected by the repository’s access controls. If your backup platform provides health checks or synthetic full verification, run them before the source host is shut down. Record the restore-point timestamp and the person who approved it for rollback.
Recommended Free Tools
Plan encryption and credentials
Document the encryption keys, key-management server dependencies, backup encryption passwords, and the administrators authorized to use them. A backup that cannot be decrypted during an outage is not a usable rollback. Confirm that the destination hosts can obtain the required keys before moving an encrypted VM.
Prepare the destination, network, and backup transport
Register or inventory both the source and destination ESXi hosts in the backup system. In vCenter, confirm that the destination cluster, resource pool, port groups, datastores, and permissions are ready. For a cross-vCenter or otherwise separated move, validate DNS, routing, firewall rules, and authentication between management endpoints before the migration window.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
Capacity and storage checks
- Compare the provisioned size of every virtual disk with free capacity on the target datastore. Thin-provisioned disks can consume more physical space than their current guest usage during a copy.
- Allow space for VM swap files, configuration files, snapshots, and growth after cutover.
- For vSAN Quick Migration, plan for potentially longer transfer times: the operation can require full-disk reads rather than reading only guest-used blocks.
- Check datastore latency and queue depth during a pilot. A destination that has enough gigabytes but cannot sustain the read and write load can extend downtime.
Network and proxy placement
Place backup proxies and repositories so that backup traffic uses a preferred or dedicated network whenever possible. Veeam recommends keeping backup traffic off the VMware management network where possible. Confirm throughput, MTU consistency if jumbo frames are used, and firewall rules for the actual source, proxy, repository, and target paths. Do not assume that a fast vMotion network is also suitable for backup traffic; they may use different interfaces and controls.
Licensing and compatibility
Verify that the VMware edition and configuration include vMotion and Storage vMotion if those methods are planned. Check host CPU compatibility, virtual hardware support, datastore accessibility, virtual switch or distributed-switch configuration, and VM hardware features that the destination cannot provide. Resolve compatibility warnings before the outage window rather than accepting them during a production move.
Choose the migration method
The right method depends on whether you need to move compute, storage, or both; whether the VM can remain powered on; and whether the VMware licensing and topology support a native operation.
| Method | Power state and downtime | Key requirements | Best fit | Rollback consideration |
|---|---|---|---|---|
| Compute vMotion | Powered on; normally a short switchover while execution transfers | Compatible source and target hosts, suitable licensing, reachable networks and storage | Moving a running VM to another ESXi host while keeping its datastore | Keep the verified backup until host, network, and application checks pass |
| Storage vMotion | Powered on; storage copy runs while the VM serves traffic, followed by a brief cutover | Supported licensing, source and target datastores, sufficient destination capacity and I/O | Moving VM disks to another datastore or storage tier | The independent image backup remains the clean rollback point if the storage move fails |
| Veeam Quick Migration with SmartSwitch | VM runs during copying, then is suspended briefly for final synchronization | Source and target hosts registered in Veeam, reachable repository or proxy paths, and no blocking VM features such as SCSI bus sharing | Cross-boundary moves or environments where native VMware migration is unavailable | Retain the original restore point and record the final sync result |
| Veeam Quick Migration with ColdMigration | VM is powered off for the copy, producing a longer outage | Same transport and destination checks as Quick Migration, with an approved outage | Cases where a hot move is not possible or a clean powered-off copy is preferred | Power the original VM back on only under the documented rollback decision to avoid split-brain changes |
| Instant Recovery to VMware vSphere | Recovered VM starts directly from the compressed, deduplicated backup; final placement happens later | A verified restore point, repository access, and a destination that can run the recovered VM | Urgent service resumption while the permanent datastore or host is being prepared | Finalize with Quick Migration or Storage vMotion, then validate the resulting VM and backup job |
Native vMotion and Storage vMotion
Use compute vMotion for a host move and Storage vMotion for a datastore move when the VMware environment supports them. They generally provide the least disruption because the VM remains powered on during most of the transfer. Native operations still require capacity, CPU, network, storage, and permission checks; a successful start does not guarantee that the final destination has the same security or encryption settings.
Quick Migration, SmartSwitch, and ColdMigration
When you invoke Quick Migration, Veeam Backup & Replication analyzes the virtual environment, VM configuration, and current state, then selects an appropriate relocation method. SmartSwitch copies the VM and briefly suspends it for the final synchronization. ColdMigration powers the VM off before copying, so it is slower from the application’s perspective but avoids trying to synchronize ongoing writes. SCSI bus sharing prevents Quick Migration, so such VMs need a different method or a redesign approved by the application owner.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Instant Recovery as an emergency path
Instant Recovery is a recovery operation rather than a completed migration. It starts the VM directly from the compressed and deduplicated backup so service can resume while the permanent placement is prepared. Veeam states that finalizing recovery still requires moving the VM to a new location; use Quick Migration or Storage vMotion to complete that step, then verify the resulting disks, networking, and backup protection.
Execute a low-risk pilot
Do not begin with the most critical database or the largest VM. Select a representative, noncritical workload that exercises the same host CPUs, datastore type, network path, encryption settings, and backup policy as the production batch.
- Confirm the approved restore point, rollback owner, change window, and application contact.
- Record the VM’s current host, datastore, power state, IP configuration, snapshots, encryption state, and backup-job membership.
- Run the selected migration method and capture elapsed time, copy throughput, datastore latency, CPU-compatibility behavior, and any stun or outage interval. For SmartSwitch, record the final synchronization pause; for ColdMigration, record the full powered-off period.
- Check guest boot, VMware Tools, virtual disks, time synchronization, DNS, authentication, application listeners, and monitoring alarms.
- Run an application-owner transaction test rather than relying on a ping. For a database, test a controlled read and write; for an API, exercise an authenticated request; for a file service, create and retrieve a test file under the owner’s procedure.
- Confirm that the backup job still targets the VM at its new host or datastore and that the next run completes. Record the new inventory path and any changed identifiers used by the backup system.
- Keep the original restore point and the written rollback decision. Do not delete the source VM or old backup chain until the pilot and the agreed retention period have passed.
Restore a VM to the original or a different host
Conventional full-VM restore
Use a verified restore point when the migrated VM is corrupt, missing, or unsuitable for the destination. In Veeam’s full-VM restore workflow, choose the restore point and select the original location or a new host, cluster, datastore, and network. If the original VM is still running at its original location, Veeam powers it off before restoring the disks included in the backup. Coordinate that power-off with the application owner to prevent two copies of the same service from accepting writes.
- Select the restore point whose timestamp meets the approved recovery objective and confirm that every required virtual disk is included.
- Choose the destination host or cluster, datastore, resource pool, and port group. Map each source network to a destination network deliberately; do not accept an accidental default port group.
- Review disk provisioning, controller type, virtual hardware compatibility, and encryption choices. Supply key-management access if the VM is encrypted.
- Start the restore and monitor repository reads, target datastore capacity, and task errors. Do not interrupt the operation because the progress estimate changes.
- Power on the restored VM only in an isolated network first. Complete the boot and application checks before connecting it to production.
- When the owner approves cutover, connect the production network, update monitoring and inventory, and run a new backup from the restored location.
Restore to a new host after migration
Restoring to a different host is supported when the destination can run the VM’s virtual hardware and provide equivalent devices and networks. Check CPU compatibility, datastore access, virtual switch mappings, guest tools, and encryption before power-on. If the target host lacks a required device or feature, remove or replace it according to the application owner’s change plan rather than forcing the VM to boot with missing dependencies.
Test that the backup will actually boot
A completed backup job does not prove that an application can start. Perform a recovery test in an isolated network so the restored VM cannot conflict with its production identity, DHCP lease, DNS records, domain membership, monitoring agents, or application endpoints.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
Isolation controls
- Use a port group or virtual network with no route to production. Apply firewall rules that allow only the test dependencies required by the application owner.
- Prevent duplicate IP addresses and hostnames. If the guest must contact a directory, DNS server, license service, or database, provide a controlled test equivalent or explicitly approved temporary access.
- Label the VM and its disks as a test recovery so an operator cannot mistake it for the production instance.
Boot and service checklist
- Power on the restored VM and confirm that the guest operating system reaches a stable login or service-ready state.
- Check VMware Tools, virtual CPU and memory presentation, all expected disks, filesystem mounts, and guest time.
- Verify DNS resolution, authentication, certificates, service accounts, scheduled tasks, and license dependencies.
- Confirm that application listeners bind to the expected interfaces and that the service starts without database or filesystem recovery errors.
- Have the application owner perform a transaction-level test and confirm data consistency. A generic ping or open TCP port is not sufficient.
- Check monitoring, alert suppression, log forwarding, and backup scheduling in the test environment so the recovery procedure does not create false production incidents.
- Document the test date, restore point, destination, elapsed time, observed issues, and corrective actions. The exact acceptance checks are workload-specific; vendor restore documentation defines mechanics, not one universal application checklist.
Cut over in dependency-aware batches
After the pilot passes, migrate groups in dependency order. Move foundational services and their dependents according to the owner-approved sequence, allowing time between batches for application and monitoring checks. For each VM, confirm the new host and datastore, port-group and security-policy mapping, resource-pool placement, encryption state, guest tools, and snapshots.
Reconnect backup protection
Plan backup-job migration as part of the move, not as a cleanup task. Confirm that the job recognizes the VM in its new inventory location, that proxy selection uses the intended network, and that repository retention still meets policy. Run or schedule a post-migration backup and verify its restore point. If the VM was restored under a new name or identifier, remove stale job entries only after the new protection is proven.
Verify encryption after vMotion
Because vMotion does not automatically retain VM encryption settings, inspect the VM and datastore policies after the move. Re-enable encryption or reapply the approved storage policy where required, confirm key access, and document the resulting state before closing the change.
Troubleshoot common migration and restore failures
Quick Migration is unavailable or fails immediately
Check for SCSI bus sharing, unsupported virtual hardware, inaccessible source or target hosts, missing permissions, and unavailable proxy or repository paths. If SCSI bus sharing is required by the workload, use a native VMware method or an application-approved alternative. Do not remove bus sharing casually; it can change how clustered applications access shared disks.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →The destination datastore runs out of space
Stop the operation according to the tool’s recovery procedure, preserve the original restore point, and add capacity or choose a datastore with adequate headroom. Recheck thin-provisioned disk growth, swap files, snapshots, and vSAN behavior before retrying. A datastore that is merely equal to the current guest-used size is not necessarily large enough for the copy.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Migration downtime is longer than expected
Review datastore latency, network throughput, changed-block volume, CPU compatibility, and the final synchronization size. vSAN Quick Migration can require full-disk reads, which may lengthen the transfer. If the outage exceeds the approved window, use the documented rollback decision rather than leaving two uncertain VM copies active.
The restored VM boots but the application is broken
Check disk order and controller mappings, guest time, DNS, authentication, certificates, service accounts, network bindings, database consistency, and external dependencies. Re-run the owner’s transaction test in isolation. Do not declare success based only on the guest login screen.
The next backup does not include the moved VM
Refresh the VMware inventory in the backup console, inspect job inclusion and exclusion rules, and confirm that the VM’s new host, cluster, datastore, and identifier match the job configuration. Verify proxy routing and run a protected test backup before deleting the old job reference.
Migration closeout checklist
- Every VM is running on the approved host, datastore, network, and resource pool.
- Application owners have completed transaction-level validation.
- Encryption and key-management access match policy.
- Monitoring, logging, DNS, authentication, and security controls are healthy.
- Backup jobs target the new placement, use the intended transport network, and have produced a post-migration restore point.
- The independent pre-migration restore point remains retained for the agreed rollback period.
- Old VM registrations, snapshots, temporary networks, and stale backup-job entries are removed only after approval.
- The change record contains the migration method, downtime or stun observations, restore test result, exceptions, and rollback owner.
There is no universal migration speed, success rate, recovery-time objective, or recovery-point objective that can be safely applied to every VMware environment. Those values depend on VM size, changed data, storage latency, network capacity, licensing, application behavior, and the chosen method. Measure them in the pilot and record the result for each workload class.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
