[Detailed Guide] How to Set Up Instant Recovery Network
Having the proper Instant Recovery Network configuration ensures a smooth Instant Recovery process and successful migration to production after it is over, so the Instant Recovery Network setup is extremely important.
Force Instant Recovery network
When performing an instant recovery, the ESX server initiates an NFS-datastore mount over the management network. Suppose a server with lots of i/o is being made operational after a instant recovery there is a risk the network capacity of the management network is all used by the virtual machine. Is there a method besides creating a local /etc/hosts to force an ESXi host to use the VMkernel port which is configured for our backup network instead of the management network?
- Question from Veeam R&D Forums
When an ESX server mounts an NFS datastore over the management network during immediate recovery, and when recovered virtual machines with high I/O requirements begin to run, it consumes a significant amount of capacity on the management network. This can cause performance issues and potential disruption to other management-related traffic. We need to find a way to redirect this traffic to the VMkernel port configured for the backup network instead of the default management network. This article will provide you with the requirements of instant recovery network and a way to set up an Instant Recovery network.
The Requirements of Instant Recovery Network
Some network requirements you need to meet when setting up instant recovery, the following part lists some requirements.
1. Network Bandwidth Requirements
▶Adequate Transfer Rate: Instant Recovery requires fast data transfer, 1 Gbps for small environments and 10 Gbps for medium to large ones.
▶Scalable Bandwidth: Networks must be scalable to efficiently handle growing data volumes and recovery tasks, avoiding bandwidth bottlenecks.
2. Network Configuration for NFS Traffic
◆The VMkernel port on which the NFS client service is enabled.
◆Routing rules to direct traffic through the required VMkernel interface.
◆Correct DNS or static IP configuration to ensure that the ESXi host communicates with the Veeam NFS server over the proper network.
3. Network Traffic Rules
★Configure network traffic rules in Veeam to force specific networks to be used for backup operations.
★Ensure that the firewall policy allows NFS traffic between the Veeam server and ESXi hosts over the specified network.
How to Set Up Instant Recovery Network
You can follow the steps below to configure Veeam for Instant Recovery on a Specific Network.
Step 1. Create a VMkernel Port for NFS Traffic
Make sure that your ESXi hosts have a VMkernel port dedicated to the backup or NFS network.
Log into the vSphere Client, go to Host > Configure > Networking > Network Adapters. Click Properties > Add… and assign it to the desired network to enable the NFS Client service on this VMkernel adapter.
Step 2. Configure the NFS Mounting Networking
Verify the backup network configuration for adequate bandwidth and connectivity to the Veeam server. Optionally, add a routing rule in the ESXi table to direct backup repository traffic through the backup network.
Verify the backup network configuration: Ensure that the backup network has sufficient bandwidth and connectivity to the Veeam server.
Add a routing rule: If there are multiple networks, configure the ESXi routing table to ensure that the traffic destined for the backup repository uses the backup network.
Step 3. Modify Veeam Instant Recovery Settings
Ensure that Veeam communicates over the desired network during instant recovery:
🔶In the Veeam Backup & Replication Console, go to Backup Infrastructure > Managed Servers to edit the properties of the ESXi host and verify that its management IP matches the required network.
🔶Configure the NFS service in Veeam:
Under Options, bind the NFS server to the IP address of the backup network. Navigate to General Options > Network Traffic Rules. Add a rule to prioritize the backup network for all Veeam-related traffic, including NFS operations.
Easy and Free Instant Recovery Tool – AOMEI Cyber Backup
A good network configuration can ensure that instant recovery goes smoothly. At the same time, choosing a satisfactory instant recovery software is also a factor in the smooth progress of this process. AOMEI Cyber Backup can provide you with a comprehensive and free instant recovery solution, which can restore virtual machines from backups in a short time and minimize downtime.
Why choose AOMEI Cyber Backup?
User-friendly Interface: The user interface is simple, allowing easy setup and operation for less tech-savvy users.
Instant Disaster Recovery: It offers an instant recovery solution to minimize downtime, enabling a seamless recovery directly to your VMware environment.
Centralized Management: The process of backing up multiple virtual machines (VMs) simultaneously from a centralized console enhances management efficiency and simplifies overall administration.
Flexible Backup Policies: It can provide you with various backup strategies, such as full, incremental, and differential backups, which you can choose according to your needs.
Step 1. Navigate to Task > + Create New Instant Restore, and you can choose Restore from task or Restore from local path. The following is choose Restore from task as an example.
Step 2. In Source, click Select to choose VM and version.
Step 3. In Select Virtual Machine, click Select to choose the virtual machine and backup version.
Step 4. To choose the target device in Restore to.
Step 5. Then you can set the hardware settings for the new virtual machine, such as CPU quantity, CPU Cores, and memory size.
Step 6. Click Start Restore to begin the instant restore.
Step 7. Then you can choose Start Migration to restore the VM to the production environment when the production environment resumes to normal.
Conclusion
Configuring Veeam Instant Recovery to run on a dedicated network, such as a specific backup or VMkernel network, is a simple but effective strategy that can significantly improve performance and stability during recovery. By adjusting the network settings in vSphere and Veeam, you can effectively minimize the risk of network congestion.