09 February 2019

Avamar Exchange VSS plugin - backup failing with error: avtar Error 7042: Failed to create snapview


Exchange Backup Failures

Exchange VSS plug-in DAG or individual Exchange node backup is failing (Failed to create snapview):

Avamar Exchange VSS plugin - backup failing with error: avtar Error <7042>: Failed to create snapview

2015-01-21 09:37:21 avtar Info <7209>: Finished reading makeview input
2015-01-21 09:37:21 avtar Info <7210>: Finished generating makeview tables
2015-01-21 09:37:21 avtar Info <16522>: Starting copy of paths in account '/clients/XXXXXXXX' label number 3
2015-01-21 09:37:21 avtar Error <7042>: Failed to create snapview, as one of the elements required for path "XXXXXXXXX.edb" not found in backup account '/XXXXXX' lablenum 3 (only found 'XXXX\E:' of path 'XXXX.edb').
2015-01-21 09:37:21 avtar Info <9772>: Starting graceful (staged) termination, unable to find paths in snapview (wrap-up stage)
2015-01-21 09:37:21 avtar Info <0000>: Entering the 'final' phase of termination, unable to find paths in snapview)
2015-01-21 09:37:21 avtar FATAL <5155>: Backup aborted due to earlier errors. No backup created on the server.
2015-01-21 09:37:21 avtar Info <7883>: Finished at 2015-01-21 09:37:21 Eastern Standard Time, Elapsed time: 0000h:00m:01s
2015-01-21 09:37:21 avtar Info <6149>: Error summary: 2 errors: 5155, 7042

This is a case-mismatch of Exchange Databases between two subsequent backups.
For example : If during Backup1, the database directory of the database was "C:\mailbox" and gets changed to "C:\MAILBOX", the next subsequent backup will fail with the above error message.

Resolution is to disable the use of case-sensitive paths

Setting the following flag inside "avexvss.cmd" filen in local VAR directory of all Exchange Servers as well as in shared VAR folder of the DAG client:

--use-case-sensitive-paths=false

If the above flag does not resolve the issue, then try backing up each Exchange database individually. The error happens when the snapview avtar process tries to consolidate the backups of each of the DBs into one single label number.

No comments:

Post a Comment

Popular