Page 1 of 1

Server 2012 R2 Hyper-V Merge

Posted: Thu Oct 30, 2014 10:27 am
by PMCS
I'm running version 8.1.1 on a Server 2012 R2 that was recently upgraded from Server 2008 R2.
It is clear that the System Protection backup has changed how VMs are backed up and it looks like they are snapshotted, backed up, then merged.

I had 3 successful backups without issue and then today's backup, during the merge, appeared to run out of space and paused-critical my VMs. I actually had to restart the physical server to bring them back up because they wouldn't resume. No disk activity after attempting to resume one of them and Hyper-V just had an endless progress bar while it was trying to do something. I gave it 30 minutes before rebooting.

I have 2 VMs I'm backing up: a DC and an Exchange Server spread over 2 data volumes (D: 1.9TB and E: 561GB with 114GB and 86.5GB free respectively).
The Exchange server takes up the majority of that.

Couple of questions:
1) Can I do something to limit the consumption of space during a backup?
2) Can BackupAssist on Server 2012 R2 now backup a GPT volume larger than 2TB?

Thanks,
Patrick

Re: Server 2012 R2 Hyper-V Merge

Posted: Thu Oct 30, 2014 2:49 pm
by gsohal
Hi Patrick

It's Gagan from the BackupAssist team. Thank you for posting on our forum.

Sorry to hear that you've issues with the backup software.

First of all, I would like to confirm that there are no changes made to the imaging engine. BackupAssist used and still uses the “Windows Backup” engine to perform its image backups, and this engine does delete older backups as needed to manage space.

With regards to your queries, please find my response inline.

1) Can I do something to limit the consumption of space during a backup?

As stated above BackupAssist uses Windows engine to perform its imaging operation and this engine performs an up-front check to ensure that the backup device has enough space to store the backup.
I am sorry to say there is no option in BackupAssist to manage space for imaging backups.
Microsoft recommends backup destination should be 1.5x to 2.5x the backup size, depending on where you look (eg. see this technet article: http://blogs.technet.com/b/sbs/archive/ ... ackup.aspx), and again, this is due to the dynamic nature of Windows Backup, which uses VSS snapshots to store past backups.

2) Can BackupAssist on Server 2012 R2 now backup a GPT volume larger than 2TB?
Yes, on Windows 2012R2 you will be able to backup drives larger than 2TB.


I hope I have answered your queries.

If you have any issues with the backups then you can contact the support team by submitting the diagnostic report from BackupAssist.
To submit the diagnostic report you will need to log in to BackupAssist > Help > Feedback and Support > Contact Support

Have a nice day ahead.

Regards
Gagan

Re: Server 2012 R2 Hyper-V Merge

Posted: Fri Oct 31, 2014 4:27 am
by PMCS
I'm submitting diagnostics now with the same subject as the title of this thread.
I can't have a backup shutdown VMs because of space issues introduced.
Also, last night's backup didn't even kick off because it says the backup media is out of space. The backup drive is managed by BackupAssist so it should be able to delete old backups as necessary.

Re: Server 2012 R2 Hyper-V Merge

Posted: Tue Nov 04, 2014 10:35 pm
by gregaker
We are experiencing the same issue with 8.1.1 and it also appears to us the backup process in HyperV somehow changed in 8.1.1. Most troubling is that I receive a completely successful backup notification, but not all of the components will be available from the restore console when the issue occurs. Most recent example was host running two vm's, one Exchange and one file server, host and guests all 2012 R2. The file server was in blue screen state and Exchange server was running but Exchange not functional. Had to shut both down to merge the avhdx files and then they come up fine. Again, no issues reported by backup job but servers left in unusable state. Most of the backup is available for restore but not the Exchange granular restore in this case. We can't continue with 8.1 upgrades until there is a better handle on what is happening here.