AOMEI Cyber Backup
Fixed: Veeam Instant Recovery Quick Migration [3 Solutions]
Veeam Instant Recovery provides a solution to recover VMs in a short period of time, but there are some issues that may occur when configuring Instant Recovery for fast migrations, and one of them is that the snapshot files copy taking too long.
By Amelia / Updated on November 15, 2024
Instant Recovery Quick Migration: Snapshot file copy taking too long
I have been migrating a Windows file server VM with about 5.5 TB of written storage for about 52 hours now. For about 2 1/2 hours, Veeam has suspended the VM and is now copying over the snapshot files. All the VMDK files for the individual drives combined are about 80 GB in size. My problem now is that the whole process has just surpassed 4%, and I don't know why it's taking so long for just 80 GB of data. I have to say, although the recovery has taken 50 hours so far due to multiple failed attempts, the original backup file is 10 days old, so the whole 80 GB is data from the last 10 days.
- Question from Reddit
Veeam can provide users with a backup and instant recovery solution with disaster recovery features. However, when using Veeam, you may encounter performance bottlenecks, the most common of which is slow snapshot file replication. This reduces system performance and increases the time required for backup and instant recovery. In this article, we will explain the reasons for this problem and how to solve it.
What is Quick Migration in Veeam
In Veeam, Fast Migration allows the migration of virtual machines or virtual disks between ESXi hosts and datastores while preserving their current state and data. It is typically used for instant recovery or VM migration where a VM needs to be recovered or relocated quickly. Snapshot file copy is one of the steps in fast migration.
Causes and Resolution to Snapshot File Copy Taking Too Long
In some cases, instant recovery snapshot file copying in the quick migration step of instant recovery in Veeam may take too long, which may delay recovery. This can happen for several reasons, and in this next section, you will be provided with the reasons for this problem as well as a solution.
Storage Performance Issues
The performance of the source backup repository and target VM storage is crucial for fast migration. Slow or heavily utilized storage can greatly delay snapshot file replication, so optimizing storage performance is essential for efficient operations.
🔶Solutions:
▶Optimize backup repository storage: Use fast, high-performance storage devices like solid-state drives for backup files to speed up recovery processes.
▶Evaluate target storage performance: The storage destination for the virtual machines (VMs) must be fast enough to handle incoming data. When migrating VMs back to production, ensure that the target disks on the same SAN, NAS, or local storage are not bottlenecked.
▶Storage I/O throughput: Check the IOPS and throughput of the backup and target storage systems to ensure they can support both recovery and fast migration.
Network Bottlenecks
During instant recovery quick migration, snapshot data is transferred over the network from the backup repository to the target VM host. If the network infrastructure is suboptimal or experiencing high congestion, it may lead to decreased data transfer rates.
🔶Solutions:
✦Upgrade network infrastructure: Ensure the network between the backup repository, agent, and VM hosts is fast enough for data migration. Aim for at least a 10GbE connection for optimal transfer rates.
✦Use a dedicated network interface: For critical recovery operations, use a dedicated network interface for Veeam backup traffic to isolate it from regular activity and reduce congestion.
Snapshot Size and Virtual Machine Activity
A large snapshot file will take longer to transfer if the virtual machine has changed significantly since it was created. Active virtual machines with many write operations during recovery can also increase snapshot size, slowing down the replication process.
🔶Solutions:
✈Minimize virtual machine activity: Reduce the workload of virtual machines during recovery to prevent rapid snapshot growth.
✈Use storage-level snapshots: If your storage system supports it (like VMware's VAAI or Hyper-V's CSV), use storage-based snapshots to expedite recovery and migration, bypassing the backup agent and reduce copy time.
Free Tool with Instant Recovery and Fast Migration
When the process of creating snapshot file copies takes an excessive amount of time, it can severely impact critical data recovery efforts. This delay not only leads to extended periods of downtime but also threatens the continuity of both personal and business operations.
Fortunately, AOMEI Cyber Backup offers an efficient and secure instant recovery solution designed to alleviate these concerns. With this powerful tool, you can swiftly and seamlessly transition back to normal operations in just one straightforward step after initiating the instant recovery process, ensuring that you can effectively respond to urgent data recovery needs with minimal disruption. What’s more, you can enjoy more features:
😊User-friendly Interface: Experience seamless navigation with our user-friendly interface, making your backup and recovery tasks simpler and more efficient than ever.
🔰Powerful Disaster Recovery: Ensure the security of your vital systems and data against unforeseen disasters by implementing robust backup and recovery plans.
🎯Centralized Management: The process allows simultaneous backups of multiple virtual machines (VMs) from a single console, enhancing management and efficiency.
Now you can try AOMEI Cyber Backup for free by clicking the download button below.
Follow Simple Steps to Set Instant Recovery Safely
Step 1. Navigate to Task > Instant Recovery > + New Instant Recovery, and choose Restore from task.
Step 2. Choose the virtual machine and backup version in Source.
Step 3. Choose the target device in the Restore to section.
Step 4. Set the hardware settings for the new virtual machine, including CPU quantity, CPU Cores, and memory size.
Step 5. Click Start Restore to start the instant recovery.
Step 6. Click Start Migration to restore the virtual machine to the production environment after the production environment resumes normal.
👉Note: At the beginning of the instant recovery, you can also choose Restore from local path. But when you select the source, please note that the local image file can only be selected from the ESXi virtual machine JSON file.
Conclusion
Instant Recovery Fast Migration in Veeam can lead to some problems if it is not functioning properly. After following the methods provided in this article, the problem of long snapshot file copying time can be effectively improved to ensure that Instant Recovery can run properly.
