Here’s a really great function of NetWorker: being able to kick off the recovery of multiple virtual machines simultaneously. One operation, multiple image based recoveries. It barely takes any more time than starting the recovery of a single virtual machine, so if you’re in a rush or need a bunch of systems restored at once, why wouldn’t you use this?
Here’s a video that takes you through the process:
(You can click on the caption above to jump to the YouTube video directly.)
I actually hadn’t known you could do this for some time, but then a colleague mentioned it to me last year and I’ve been meaning to highlight it since. (Clearly, I’m easily distracted.)
While you’re here, the second edition of Data Protection: Ensuring Data Availability has been released. If you work in backup and recovery or data protection more broadly, it’ll be a great resource for you! You can check some details about the release here.
Hi Preston, love the blog it has helped me a lot over the last decade! Slightly off topic from this post, but I’ve been searching high and low and can’t seem to find any solid answer on the web or in the NW documentation. When running VMware backups (I’m talking specifically with NW 19.x, vSphere 6.7, to DD w/ boost, hotadd, vproxy, etc) what is the recommended/best practice backup level to use? Should every backup be a full backup, or should it be more of a traditional weekly full/daily incremental situation? Does it even make a difference with CBT being used? Do synthetic fulls come in to play at all? Look forward to hearing from you!
Hi Pat,
Thanks for the feedback!
I configure my VM image-based backups as incremental. If you check the logs, you’ll see that they’re promoted to virtual synthetic fulls anyway as part of the backup process.
Cheers.