Backing up Exchange 2013 with NTFS-mountpoints as Storage Path for Mailboxdatabases ends into Backup Error/Warning.
Environment:
Exchange 2013 CU20 running a CNO-less DAG with two nodes
Database-Folderpaths:
d:\mnt\DB01 -> mountpoint to a gpt partitioned NTFS-volume
this mounted volumes includes the edb-File and the Trunk-Logs of the Mailboxdatabase
d:\mnt\DB02 -> mountpoint to a gpt partitioned NTFS-volume
this mounted volumes includes the edb-File and the Trunk-Logs of the Mailboxdatabase
Windows Server 2012 R2 (most current updates)
Circullar Logging for both Databases is disabled.
UrBackup Client (2.2.5) is configures to run in InternetOnly-mode.
UrBackup Server (2.2.8) on Windows 8.1
Content of debug.log (nonverbose):
2018-04-06 09:37:53: WARNING: Writer Cluster Shared Volume VSS Writer has failure state VSS_WS_FAILED_AT_PREPARE_SNAPSHOT with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2018-04-06 09:37:53: ERROR: Preparing change block tracking reset for volume failed: Falscher Parameter. (code: 87)
2018-04-06 09:37:53: ERROR: Preparing change block tracking reset for volume d:\db02 failed: Falscher Parameter. (code: 87)
2018-04-06 09:37:54: WARNING: Writer Cluster Shared Volume VSS Writer has failure state VSS_WS_FAILED_AT_PREPARE_SNAPSHOT with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2018-04-06 09:37:55: WARNING: Writer Cluster Shared Volume VSS Writer has failure state VSS_WS_FAILED_AT_PREPARE_SNAPSHOT with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2018-04-06 09:37:55: WARNING: Writer is in error state during snapshot creation. Writer data may not be consistent. This means the files open by this application (e.g. databases) will be backed up in a crash consistent state instead of a properly shutdown state. Properly written applications can recover from system crashes or power failures
2018-04-06 09:37:55: ERROR: Path “d:\db01” does not start with volume “d:\db01”
2018-04-06 09:37:55: ERROR: Error indexing files 0 of component “File” of writer “Microsoft Exchange Writer”.
2018-04-06 09:37:56: WARNING: Writer Cluster Shared Volume VSS Writer has failure state VSS_WS_FAILED_AT_PREPARE_SNAPSHOT with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2018-04-06 09:37:58: WARNING: Writer Cluster Shared Volume VSS Writer has failure state VSS_WS_FAILED_AT_PREPARE_SNAPSHOT with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2018-04-06 09:37:58: WARNING: Writer is in error state during snapshot creation. Writer data may not be consistent. This means the files open by this application (e.g. databases) will be backed up in a crash consistent state instead of a properly shutdown state. Properly written applications can recover from system crashes or power failures.
2018-04-06 09:37:58: ERROR: Could not open path in os_get_final_path for “D:\Volume{ffd2a9b1-98c5-49e8-beab-fc18e91d7391}”
2018-04-06 09:37:58: ERROR: Could not open path in os_get_final_path for “D:\Volume{22a85f6b-05fa-45e3-9292-d9dd7d328159}”
2018-04-06 09:38:00: WARNING: Writer Cluster Shared Volume VSS Writer has failure state VSS_WS_FAILED_AT_PREPARE_SNAPSHOT with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
If checking Backup-State from Exchange point of view (through Exchange Management Shell) i cannot see a successfull Backup, altghough all mailbox-databases and Trunk-Logs are backed up.
Get-MailboxDatabase -Status | FL Name,*Backup
The LastFullBackup Attribute is filled with an old date.
Currently paths d:\mnt\db01 and d:\mnt\db02 are configured to be backed up.
Both Mailbox-database paths are selected as components to be backed up.
If i use Windows Server Backup which also uses Exchange Server Writer to backup same databases (Drive d:) on same Exchange host, backup completes successfully and Exchange also recognize the backup (LastFullBackup has a current date)
In my opinion the error is here:
2018-04-06 09:37:55: ERROR: Path “d:\db01” does not start with volume “d:\db01”
seems to be an issue in client_winvss.cpp
This expression seems to compare the volume name and the target backup path
if (!next(path, 0, vol))
{
VSSLog(“Path “”+path+”" does not start with volume “” + vol + “”", LL_ERROR);
return false;
}
Any chance to get this fixed?
Regards,
Thomas