Unsolved
This post is more than 5 years old
5 Posts
0
1453
September 12th, 2014 11:00
avtar Error Causing Exchange Backup to Fail
I am currently trying to set up Avamar Exchange VSS for a customer.
The setup is as follows:
- Exchange 2007 SP2 - Single Copy Cluster (SCC)
- Two active nodes in a Microsoft Windows 2003 R2 cluster (ExchangeA & ExchangeB)
- One standby server that can take over functions of ExchangeA OR ExchangeB, but not both at once
- ExchangeA & ExchangeB cannot fail over to each other - they run completely separate mailboxes for users (so a user for this company will be configured either on ExchangeA or ExchangeB)
We are running into an issue where the backups on ExchangeA are completing successfully, but ExchangeB keep failing.
The avtar log shows this on ExchangeA:
2014-09-12 01:00:33 avtar Info <7324>: Volume Type for "\\?\C:\" is "NTFS", Supports Compression=1, Encryption=1, ACLS=1, DataStreams=1, Reparse=1, Sparse=1
2014-09-12 01:00:33 avtar Info <7324>: Volume Type for "\" is "", Supports Compression=0, Encryption=0, ACLS=0, DataStreams=0, Reparse=0, Sparse=0
2014-09-12 01:00:33 avtar Info <7324>: Volume Type for "C:\" is "NTFS", Supports Compression=1, Encryption=1, ACLS=1, DataStreams=1, Reparse=1, Sparse=1
2014-09-12 01:00:33 avtar Info <7324>: Volume Type for "D:\" is "", Supports Compression=0, Encryption=0, ACLS=0, DataStreams=0, Reparse=0, Sparse=0
2014-09-12 01:00:33 avtar Info <7324>: Volume Type for "F:\" is "NTFS", Supports Compression=0, Encryption=1, ACLS=1, DataStreams=1, Reparse=1, Sparse=1
2014-09-12 01:00:33 avtar Info <7324>: Volume Type for "G:\" is "NTFS", Supports Compression=0, Encryption=1, ACLS=1, DataStreams=1, Reparse=1, Sparse=1
2014-09-12 01:00:33 avtar Info <7324>: Volume Type for "H:\" is "NTFS", Supports Compression=0, Encryption=1, ACLS=1, DataStreams=1, Reparse=1, Sparse=1
2014-09-12 01:00:33 avtar Info <7324>: Volume Type for "I:\" is "NTFS", Supports Compression=0, Encryption=1, ACLS=1, DataStreams=1, Reparse=1, Sparse=1
2014-09-12 01:00:33 avtar Info <7324>: Volume Type for "J:\" is "NTFS", Supports Compression=0, Encryption=1, ACLS=1, DataStreams=1, Reparse=1, Sparse=1
2014-09-12 01:00:33 avtar Info <7324>: Volume Type for "Q:\" is "NTFS", Supports Compression=1, Encryption=1, ACLS=1, DataStreams=1, Reparse=1, Sparse=1
2014-09-12 01:00:33 avtar Info <8767>: Opened Cluster.
2014-09-12 01:02:31 avtar Info <8770>: Cluster drive(s) K:\ P:\ L:\ R:\ N:\ T:\ O:\ U:\ M:\ S:\ will not be available for backup.
2014-09-12 01:02:31 avtar Info <5811>: - Traversing drive 'C:' kind 'Local Fixed Disk'
2014-09-12 01:02:31 avtar Info <5810>: - Not traversing drive 'D:' kind 'CDROM'
2014-09-12 01:02:31 avtar Info <5811>: - Traversing drive 'F:' kind 'Local Fixed Disk'
2014-09-12 01:02:31 avtar Info <5811>: - Traversing drive 'G:' kind 'Local Fixed Disk'
2014-09-12 01:02:31 avtar Info <5811>: - Traversing drive 'H:' kind 'Local Fixed Disk'
2014-09-12 01:02:31 avtar Info <5811>: - Traversing drive 'I:' kind 'Local Fixed Disk'
2014-09-12 01:02:31 avtar Info <5811>: - Traversing drive 'J:' kind 'Local Fixed Disk'
2014-09-12 01:02:31 avtar Info <5811>: - Traversing drive 'Q:' kind 'Local Fixed Disk'
2014-09-12 01:02:31 avtar Info <5811>: - Traversing drive 'V:' kind 'Local Fixed Disk'
2014-09-12 01:02:31 avtar Info <5811>: - Traversing drive 'W:' kind 'Local Fixed Disk'
2014-09-12 01:02:31 avtar Info <5811>: - Traversing drive 'X:' kind 'Local Fixed Disk'
2014-09-12 01:02:31 avtar Info <5811>: - Traversing drive 'Y:' kind 'Local Fixed Disk'
2014-09-12 01:02:31 avtar Info <5811>: - Traversing drive 'Z:' kind 'Local Fixed Disk'
But when trying to do a backup on ExchangeB, the following shows up:
2014-09-12 02:22:48 avtar Info <7324>: Volume Type for "\\?\C:\" is "NTFS", Supports Compression=1, Encryption=1, ACLS=1, DataStreams=1, Reparse=1, Sparse=1
2014-09-12 02:22:48 avtar Info <7324>: Volume Type for "\" is "", Supports Compression=0, Encryption=0, ACLS=0, DataStreams=0, Reparse=0, Sparse=0
2014-09-12 02:22:48 avtar Info <7324>: Volume Type for "C:\" is "NTFS", Supports Compression=1, Encryption=1, ACLS=1, DataStreams=1, Reparse=1, Sparse=1
2014-09-12 02:22:48 avtar Info <7324>: Volume Type for "D:\" is "", Supports Compression=0, Encryption=0, ACLS=0, DataStreams=0, Reparse=0, Sparse=0
2014-09-12 02:22:48 avtar Info <7324>: Volume Type for "Q:\" is "", Supports Compression=0, Encryption=0, ACLS=0, DataStreams=0, Reparse=0, Sparse=0
2014-09-12 02:22:48 avtar Info <8767>: Opened Cluster.
2014-09-12 02:22:48 avtar Info <0000>: Cluster drive 'Q:\' is also a local drive, this will be available for backup
2014-09-12 02:22:48 avtar Info <8770>: Cluster drive(s) F:\ V:\ G:\ W:\ I:\ Y:\ H:\ X:\ J:\ Z:\ will not be available for backup.
2014-09-12 02:22:48 avtar Info <5811>: - Traversing drive 'C:' kind 'Local Fixed Disk'
2014-09-12 02:22:48 avtar Info <5810>: - Not traversing drive 'D:' kind 'CDROM'
2014-09-12 02:22:48 avtar Info <5811>: - Traversing drive 'K:' kind 'Local Fixed Disk'
2014-09-12 02:22:48 avtar Info <5811>: - Traversing drive 'L:' kind 'Local Fixed Disk'
2014-09-12 02:22:48 avtar Info <5811>: - Traversing drive 'M:' kind 'Local Fixed Disk'
2014-09-12 02:22:48 avtar Info <5811>: - Traversing drive 'N:' kind 'Local Fixed Disk'
2014-09-12 02:22:48 avtar Info <5811>: - Traversing drive 'O:' kind 'Local Fixed Disk'
2014-09-12 02:22:48 avtar Info <5811>: - Traversing drive 'P:' kind 'Local Fixed Disk'
2014-09-12 02:22:48 avtar Info <5811>: - Traversing drive 'Q:' kind 'Local Fixed Disk'
It's because of this Q: drive error that avtar is returning back to avexvss that my backup is failing. I need to find a way to exclude the Q: drive from being traversed by avtar. We tried putting in a specific exclude for Q: but it doesn't seem to have fixed the issue -- Q: still gets traversed by avtar.
Has anyone else experienced something like this?
Thanks.


J_H_
2 Intern
•
498 Posts
0
September 15th, 2014 15:00
you say this is a cluster
Q us usually the Quorum drive - you should only include drives that have the exchange on them
I never backup Quorum drive.
Check with your admin about the drive.
dmb1976
5 Posts
0
September 16th, 2014 09:00
It is not included in the backup. The avtar process tries scanning it even though it's not part of any backup set.
It turns out that this is a known bug. A hotfixed version of the avtar command was provided which adds a new option:
no-query-vols=Q:
This tells avtar to skip any physical drives that shouldn't be traversed.