08-21-2018 06:57 AM
Quick question...
...is there a technical recommendation from either Microsoft or Veritas that one should not backup the Hyper-V hosts themselves ?
If so, could someone share a link ?
Thank you.
Solved! Go to Solution.
08-21-2018 02:52 PM
Finding a Microsoft official comment on not backing up an Hyper-V server might be difficult but I recommend thinking why in the first place should we back it up? It's commonly because the hypervisor is offering additional services apart from Hyper-V Server. Try looking for a Microsoft note about that. For example, here's a blog that mentions this somewhat:
"Do not install any other Roles on a host besides the Hyper-V role and the Remote Desktop Services roles (if VDI will be used on the host)."
08-22-2018 12:33 AM - edited 08-22-2018 07:29 AM
Hi SDO
Thinking out loud.
We backup stuff to protect data. So backup of VM on top of the hypervisor is needed.
But hypervisor itself is in my view "data less" and can be disposed when causing trouble. So why do you want to back it up.
Is there more in your question, or just searching for best practice :) ?
08-21-2018 02:52 PM
Finding a Microsoft official comment on not backing up an Hyper-V server might be difficult but I recommend thinking why in the first place should we back it up? It's commonly because the hypervisor is offering additional services apart from Hyper-V Server. Try looking for a Microsoft note about that. For example, here's a blog that mentions this somewhat:
"Do not install any other Roles on a host besides the Hyper-V role and the Remote Desktop Services roles (if VDI will be used on the host)."
08-22-2018 12:33 AM - edited 08-22-2018 07:29 AM
Hi SDO
Thinking out loud.
We backup stuff to protect data. So backup of VM on top of the hypervisor is needed.
But hypervisor itself is in my view "data less" and can be disposed when causing trouble. So why do you want to back it up.
Is there more in your question, or just searching for best practice :) ?
08-22-2018 05:52 AM
Yes, thanks, I get that any other Windows technology server role should not be installed alongside Hyper-V Server role. And/but/also note or be aware of... that when we install NetBackup Client on a Hyper-V server for the function of VM backups then this is effectively a server-ish like function because it backs-up potentially many VMs. So, a separate third party role is effectively deployed, and has to be deployed, in order to take VM style backups.
As for taking a backup of a Hyper-V hosts itself, yes, ordinarily one would not expect to have to, nor expect to need to, take a backup of any Hyper-V host itself. My initial exploration was that, in the absence of log scraping/capture, then might it be useful to capture the Windows Event Logs via a backup process... i.e. to capture failures or alerts of nefarious events on an off-host system (the backup infrastructure) - but that is a separate question of perceived risk versus perceived value.
So, I guess I can re-phrase my question... is it harmful, or disruptive in anyway, to the Hyper-V service function to have a third party backup tool effectively instantiate a VSS snapshot of the C: volume of a Hyper-V host ?