I don't understand the difference between this two kind o job
If i want to backup the fully computer from Backup & Replication Server, which is the difference between these two choice?
Because with a Virtual Machine I've some problems with external disk insted of Windows Computer that works fine
-
- Novice
- Posts: 7
- Liked: never
- Joined: Oct 26, 2021 1:34 pm
- Full Name: Gianni Albori
- Contact:
-
- Chief Product Officer
- Posts: 31793
- Liked: 7295 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Virtual Machine or Windows Computer?
Host-based (data captured at the hypervisor level) vs. agent-based (data captures from inside of each machine) backup.
The former is far more efficient, but does not support storage that is not managed by the hypervisor, like external disks.
The former is far more efficient, but does not support storage that is not managed by the hypervisor, like external disks.
-
- Veeam Software
- Posts: 3622
- Liked: 608 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Virtual Machine or Windows Computer?
Hi Gianni,
There are too many differences but the main one is that "Windows Computer" job does not know about the hypervisor and does not interact with it. The agent works inside the guest OS and fetches data from VSS snapshots of the volumes whose data it wants to process, please refer to this page for more information. The "Virtual Machine" job works at the level of the hypervisor, the Source Data Mover is running on the proxy server and reads data in one of available transport modes. You may take a look at this page for vSphere workflow and this one for Hyper-V.
Agent-based backup for virtual machines should be used due to some host-based processing limitations on hypervisor side, for example RDM virtual disks in physical mode, independent disks on VMware or pass-through disks on Hyper-V.
Speaking about the error retrieved during "Virtual Machine" job, I strongly recommend to ask our support team to investigate the issue. Please share a support case ID with us.
Thanks!
There are too many differences but the main one is that "Windows Computer" job does not know about the hypervisor and does not interact with it. The agent works inside the guest OS and fetches data from VSS snapshots of the volumes whose data it wants to process, please refer to this page for more information. The "Virtual Machine" job works at the level of the hypervisor, the Source Data Mover is running on the proxy server and reads data in one of available transport modes. You may take a look at this page for vSphere workflow and this one for Hyper-V.
Agent-based backup for virtual machines should be used due to some host-based processing limitations on hypervisor side, for example RDM virtual disks in physical mode, independent disks on VMware or pass-through disks on Hyper-V.
Speaking about the error retrieved during "Virtual Machine" job, I strongly recommend to ask our support team to investigate the issue. Please share a support case ID with us.
Thanks!
Who is online
Users browsing this forum: CoLa and 16 guests