Image for Win - VSS problem with MS Exchange

User discussion and information resource forum for Image products.
Post Reply
wakatashi
Posts: 10
Joined: Mon Aug 19, 2013 5:05 pm

Image for Win - VSS problem with MS Exchange

Post by wakatashi »

We're running Exchange 2013 on Windows Server 2012. Creating a VSS-based backup using Image for Windows fails. Error 2044 is MSExchangeRepl is logged in the System Event Log with the following detail:

The Microsoft Exchange Replication service VSS Writer (Instance 627ad814-9a0f-4eeb-832f-bfe6b5d72c31) failed with error 80070015 when checking volume dependencies in preparation for backup.


I found an article at http://technet.microsoft.com/en-us/libr ... g.80).aspx which states:

Exchange database files, log files, and checkpoint files can be located on different disk volumes. VSS snapshot backups require all the volumes that hold these files to be in the backup set. When any of the volumes is not included in the backup set, this event will be logged and backups will fail.


Thing is, the database files, log files, and checkpoint files ARE on the same volume - the E: partition. And both C: and E: are included in the backup set.

My theory is that when two partitions are selected for backup, Image for Windows only "tells" VSS about the first partition until it's finished backing that up, and then "tells" VSS about the second one before backing that one up. So when VSS is preparing for the backup of the first partition, it "thinks" that the backup set as a whole doesn't include the second partition, which is necessary to get a consistent backup of Exchange. And so VSS fails, and the error above is logged.

How can I further troubleshoot this, please? And can anyone confirm or deny my theory above?
TeraByte Support
Posts: 3629
Joined: Thu May 05, 2011 10:37 pm

Re: Image for Win - VSS problem with MS Exchange

Post by TeraByte Support »

It adds all drives/volumes at the same time to the same snapshot set -
everything has to be done at the same time to keep it consistent.

Enable the option to skip / ignore unknown volumes in settings.

Also, ensure there isn't some other part (log files, database files, etc..)
that is keeping some exchange or sql files split up across different drive
letters or physical drives.

"wakatashi" wrote in message news:8548@public.image...

We're running Exchange 2013 on Windows Server 2012. Creating a VSS-based
backup using Image for Windows fails. Error 2044 is MSExchangeRepl is
logged in the System Event Log with the following detail:

The Microsoft Exchange Replication service VSS Writer (Instance
627ad814-9a0f-4eeb-832f-bfe6b5d72c31) failed with error 80070015 when
checking volume dependencies in preparation for backup.


I found an article at

[
http://technet.microsoft.com/en-us/libr ... v=exchg.80
](http://technet.microsoft.com/en-us/library/bb218863(v=exchg.80)

).aspx which states:

Exchange database files, log files, and checkpoint files can be located on
different disk volumes. VSS snapshot backups require all the volumes that
hold these files to be in the backup set. When any of the volumes is not
included in the backup set, this event will be logged and backups will fail.


Thing is, the database files, log files, and checkpoint files ARE on the
same volume - the E: partition. And both C: and E: are included in the
backup set.

My theory is that when two partitions are selected for backup, Image for
Windows only "tells" VSS about the first partition until it's finished
backing that up, and then "tells" VSS about the second one before backing
that one up. So when VSS is preparing for the backup of the first
partition, it "thinks" that the backup set as a whole doesn't include the
second partition, which is necessary to get a consistent backup of Exchange.
And so VSS fails, and the error above is logged.

How can I further troubleshoot this, please? And can anyone confirm or
deny my theory above?

wakatashi
Posts: 10
Joined: Mon Aug 19, 2013 5:05 pm

Re: Image for Win - VSS problem with MS Exchange

Post by wakatashi »

OK, thanks - will have a look.
Post Reply