Hi,
I noticed by VM backup job size wasn't as large as I thought it would be. One of the VMs is the file server, and has C: and D: - with D: holding a large amount of data; the size is larger than the total VM backup job. So I clicked on the backup job and clicked Restore Files - and only C: is visible. This is true for all VMs in the backup job (where a D: should exist for some of them). No changes to the Exclusions... have been made; they are all set to 'All Disks'
What have I missed?
-
- Enthusiast
- Posts: 38
- Liked: 2 times
- Joined: Nov 06, 2017 1:47 pm
- Full Name: Michael
- Contact:
-
- Enthusiast
- Posts: 38
- Liked: 2 times
- Joined: Nov 06, 2017 1:47 pm
- Full Name: Michael
- Contact:
Re: All Disks Turned On, But Only System (C:) is Backed Up
Ahhh. It's because D: is an Independent Disk.
Not ideal... I'll have to have a read on possible workarounds.
Not ideal... I'll have to have a read on possible workarounds.
-
- VP, Product Management
- Posts: 7081
- Liked: 1511 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: All Disks Turned On, But Only System (C:) is Backed Up
Hi,
yes independant disks can not be backed up as you can not create a VMware snapshot for it.
The question is why it is an independant disk. Just change it and add it to the Veeam backup.
If you can not change it, you have the option to backup the VM from within the Operating System with the Veeam Agent for Windows.
yes independant disks can not be backed up as you can not create a VMware snapshot for it.
The question is why it is an independant disk. Just change it and add it to the Veeam backup.
If you can not change it, you have the option to backup the VM from within the Operating System with the Veeam Agent for Windows.
Who is online
Users browsing this forum: Google [Bot] and 49 guests