jeremyh8 wrote:If it is just redo logs then this must mean it is booting the vms off of my backup storage and running it from there like an instant recovery correct?
jeremyh8 wrote:With that being said if i have a backup that has a retention of 7 days and I am runnign that vm in my virutal labe then what happens? Will backups even work or does that lab lock the backup file? What if i want to keep the lab up for 10 days does it extend the retention of the backup? I apologize for so many questions but i am having a difficult time grasping this for some reason.
dellock6 wrote:Hi Jeff,
I usually create pre-emptively a small firewall appliance (I use pfSense, but any firewall distro is ok) acting as a double nat system just like the virtual lab appliance does, connected to a new dedicated portgroup.
Then, I simply restore all the needed VMs, give them a different name then the production copies, and after restore I change the network connection to the lab portgroup. If somebody needs their new VMs in no time, I simply restore them via instant recovery instead of normal restore, and then I storage vmotion them in a production storage.
jg159357 wrote:Is there a way to flag a restore as a long term recovery? If I do a vmotion of the "recovered" machines and power on the proxy machine would that work?
foggy wrote:If you need to keep a lab for a long time, you could deploy a separate Veeam B&R server, copy backup files to it, import them there, and run required SureBackup jobs permanently.