Veeam Agent (VAW) doesn't backup system drive

[JardaCZ]

Hi guys,

it looks like a worst Veeam fail I've ever seen. I setup Veeam Backup Agent for Windows like this:
Backup mode: Volume level backup
Volumes: System (C), System reserved
Destination: Veeam Backup Repository (VBR 9.5 Update 3)

Backup reports "successful", but there is only "System reserved" partition in it. The most important partition "system" is missiing at all !!!

Anyone knows what's wrong?

Many thanks for help.


Regards,
Jaroslav

[Vitaliy S.]

Hi Jaroslav,

Can you please tell us what is reported on this tab for the backup agent in question? Do you see all partitions?

Thanks!

[JardaCZ]

Hello Vitaliy, thanks for reply.

2. 9. 2018 10:38:48 :: Initializing
2. 9. 2018 10:38:52 :: Preparing for backup
2. 9. 2018 10:40:21 :: Creating VSS snapshot
2. 9. 2018 10:45:18 :: Calculating digests
2. 9. 2018 10:45:18 :: Getting list of local users
2. 9. 2018 10:45:23 :: Rezervováno systémem (disk 0) (350,0 MB) 350,0 MB read at 57 MB/s
2. 9. 2018 10:45:35 :: Saving GuestMembers.xml
2. 9. 2018 10:45:39 :: Finalizing
2. 9. 2018 10:45:46 :: Truncating transaction logs
2. 9. 2018 10:45:49 :: Truncating SQL server transaction logs
2. 9. 2018 10:46:14 :: Processing finished at 2. 9. 2018 10:46:14


Regards,
Jaroslav

[Vitaliy S.]

I meant to say, what is displayed in the backed up items field (just above the statistics), sorry for the confusion. Also can you share the screenshot of your job config where you've selected this volume?

[JardaCZ]

Oh sorry. There is "Backed up items: System reserved"
When I configure backup to include only "System" without "System Reserverd", the backup fails with "Error: nothing to backup".

I've just found this KB: https://www.veeam.com/kb2641
The only difference is, that my server is HP ProLinat ML 310e with B140i controller. There are two SATA drives in Windows RAID1. OS: Server 2012 Essentials.


Regards,
Jaroslav

[Vitaliy S.]

No worries. Since your backup job is configured to back up only system reserved, that's why you do not see it in the backup upon the restore. Now, the question is why your system volume cannot be recognized. It might relate to the controller type, so looking at the log files is required (there should be a clear message why your volume is skipped). Can you please contact our technical team and let them review your log files for this server?