Veeam instant vm recovery how to#
But I did not know how to handle this one. That’s what I did as I knew well what the issue was and I could see this reflected in the logs. Than it is key to figure out why this could be happening. Combine that with an understanding of the problem and some common sense and you can quickly find what you need to look for. The trick is to search for relevant entries and that is something you learn by doing. Reading logs can seem an intimidating tedious task. With instant recovery for some reason, in the restore phase, it selects the default host network which is 1Gbps. For backups and normal restores, it correctly decides to use the preferred network. The logs confirmed what we already noticed.
To solve the issue we dive into the VBR logs, but also into the logs on both the repository/extent and the Hyper-V server where we restore the VM to. But in this blog post, it is time to dive into the log files to figure out what is going on? To read up on instant recovery go to Instant VM Recovery. But when it came to Instant Recovery we noticed that while the mount phase leveraged the preferred network, the actual restore phase did not. The reason for this is described in Optimize the Veeam preferred networks backup initialization speed.Īs you might have guessed from the blog post title “Make Veeam Instant Recovery use a preferred network” this all worked pretty much as expected for the backup themselves and standard restores. Note that the Veeam Backup & Replication server also has connectivity to the preferred networks. The IPs for the preferred networks are NOT registered in DNS. This is for redundancy but also because there are different networks in use in the environment. but also for the backup traffic via the Veeam Backup & Replication preferred network settings. This is leveraged for CSV, live migrations, storage replication, etc. Next to the management network, all of the target and source nodes have connectivity to one or more 10/25Gbps networks. We back up to a Scale Out Backup Repository that exists of several extend or standard repository. We have a Hyper-V cluster, shared storage (FC), that acts as our source. This is what this blog post is all about. To make Veeam instant recovery use a preferred network we had to do some investigation and tweaking. That uses the default host management network. While the mount phase leverages the preferred network this is not the case during the restore phase. We ran into an issue with instant recovery. The backup jobs and the standard restores both leveraged the preferred network as expected. The issue became apparent when we set up the preferred networks in VBR. In this post, I will be discussing an issue we ran into when leveraging the instant recovery capability of Veeam Backup & Replication (VBR).
0 kommentar(er)
