Exchange Server 2010
- Exchange VSS Writer (instance %1) failed with error code %2 when checking volume dependencies for storage group '%3' in preparation ...
- Exchange VSS Writer (instance %1) failed with error code %2 when checking volume dependencies for storage group '%3' in preparation ...
- Exchange VSS Writer (instance %1) failed with error code %2 when checking volume dependencies in preparation for backup. ...
- Exchange VSS Writer (instance %1) failed with error code %2 when collecting component (database) information for '%3' in ...
- Exchange VSS Writer (instance %1) failed with error code %2 when collecting component (database) information for '%3' in ...
- Exchange VSS Writer (instance %1) failed with error code %2 when collecting component (database) information in preparation ...
- Exchange VSS Writer (instance %1) failed with error code %2 when collecting component (database) information in preparation ...
- Exchange VSS Writer (instance %1) failed with error code %2 when collecting database file information for '%3' in preparation ...
- Exchange VSS Writer (instance %1) failed with error code %2 when collecting database file information for '%3' in preparation ...
- Exchange VSS Writer (instance %1) failed with error code %2 when collecting private metadata information for database '%3' ...
- Exchange VSS Writer (instance %1) failed with error code %2 when collecting private metadata information for database '%3' ...
- Exchange VSS Writer (instance %1) failed with error code %2 when preparing the database engine for backup of database '%3'. ...
- Exchange VSS Writer (instance %1) failed with error code %2 when preparing the database engine for backup of database '%3'. ...
- Exchange VSS Writer (instance %1) failed with error code %2 when retrieving the snapshot identifier of the backup set (for ...
- Exchange VSS Writer (instance %1) failed with error code %2 when retrieving the snapshot identifier of the backup set (for ...
- Exchange VSS Writer (instance %1) has completed the backup of database '%2' with errors. The backup did not complete successfully, ...
- Exchange VSS Writer (instance %1) has completed the backup of database '%2' with errors. The backup did not complete successfully, ...
- Exchange VSS Writer (instance %1) has completed the backup of the database with GUID '%2' with errors. In addition, this ...
- Exchange VSS Writer (instance %1) has completed the backup of the database with GUID '%2' with errors. In addition, this ...
- Exchange VSS Writer (instance %1) has detected an orphaned backup instance (%2). This means that the instance successfully ...
- Exchange VSS Writer (instance %1) has detected an orphaned backup instance (%2). This means that the instance successfully ...
- Exchange VSS Writer (instance %1) has successfully completed the backup of a database with GUID '%2', but was unable to match ...
- Exchange VSS Writer (instance %1) has successfully completed the backup of a database with GUID '%2', but was unable to match ...
- Exchange VSS Writer (instance %1) has successfully completed the copy or differential backup of database '%2'. No logfiles ...
- Exchange VSS Writer (instance %1) has successfully completed the copy or differential backup of database '%2'. No logfiles ...
- Exchange VSS Writer (instance %1) has successfully completed the full or incremental backup of database '%2'. The database ...
- Exchange VSS Writer (instance %1) has successfully completed the full or incremental backup of database '%2'. The database ...
- Exchange VSS Writer (instance %1) has successfully completed the full or incremental backup of replicated database '%2'. ...
- Exchange VSS Writer (instance %1) has successfully completed the full or incremental backup of replicated database '%2'. ...
- Exchange VSS Writer (instance %1) has successfully prepared the database engine for a full or copy backup of database '%2'. ...
- Exchange VSS Writer (instance %1) has successfully prepared the database engine for a full or copy backup of database '%2'. ...
- Exchange VSS Writer (instance %1) has successfully prepared the database engine for an incremental or differential backup ...
- Exchange VSS Writer (instance %1) has successfully prepared the database engine for an incremental or differential backup ...
- Exchange VSS Writer (instance %1) has successfully prepared the database engine for backup of database '%2'. The backup is ...
- Exchange VSS Writer (instance %1) has successfully prepared the database engine for backup of database '%2'. The backup is ...
- Exchange VSS Writer failed restoring a backup because a Private Database vs. Public Database mismatch has been detected for ...
- Exchange VSS Writer failed restoring a backup because a Private Database vs. Public Database mismatch has been detected for ...
- Exchange VSS Writer failed restoring a backup because a prohibited attempt was made to add additional restores to a previous ...
- Exchange VSS Writer failed restoring a backup because a prohibited attempt was made to add additional restores to a previous ...
- Exchange VSS Writer failed restoring a backup because an illegal attempt was made to add additional restores to a previous ...
- Exchange VSS Writer failed restoring a backup because an illegal attempt was made to add additional restores to a previous ...
- Exchange VSS Writer failed restoring a backup because circular logging is enabled, either in the backup set or in the target ...
- Exchange VSS Writer failed restoring a backup because circular logging is enabled, either in the backup set or in the target ...
- Exchange VSS Writer failed restoring a backup because of a target database location mismatch. The file '%1' is targeted for ...
- Exchange VSS Writer failed restoring a backup because of a target database location mismatch. The file '%1' is targeted for ...
- Exchange VSS Writer failed restoring a backup because the backup set to be restored has an invalid version stamp ("%1") in ...
- Exchange VSS Writer failed restoring a backup because the backup set to be restored has an invalid version stamp ("%1") in ...
- Exchange VSS Writer failed restoring a backup because the backup set to be restored is missing a version stamp in its private ...
- Exchange VSS Writer failed restoring a backup because the backup set to be restored is missing a version stamp in its private ...
- Exchange VSS Writer failed restoring a backup because the base name ('%1') of the logfiles in the backup set being restored ...
- Exchange VSS Writer failed restoring a backup because the base name ('%1') of the logfiles in the backup set being restored ...
- Exchange VSS Writer failed restoring a backup because the database '%1' in '%2' of database '%3' is targeted for restore, ...
- Exchange VSS Writer failed restoring a backup because the database '%1' in '%2' of database '%3' is targeted for restore, ...
- Exchange VSS Writer failed restoring a backup because the file '%1' already exists. Since the backup set is being restored ...
- Exchange VSS Writer failed restoring a backup because the file '%1' already exists. Since the backup set is being restored ...
- Exchange VSS Writer failed restoring a backup because the file '%1' in '%2' specified for re-targetting on restore could ...
- Exchange VSS Writer failed restoring a backup because the file '%1' in '%2' specified for re-targetting on restore could ...
- Exchange VSS Writer failed restoring a backup because the file '%1' in '%2' was incorrectly re-targeted multiple times for ...
- Exchange VSS Writer failed restoring a backup because the file '%1' in '%2' was incorrectly re-targeted multiple times for ...
- Exchange VSS Writer failed restoring a backup because the logfile base name ('%1') in the backup set does not match the logfile ...
- Exchange VSS Writer failed restoring a backup because the logfile base name ('%1') in the backup set does not match the logfile ...
- Exchange VSS Writer failed restoring a backup because the logfile path ('%1') specified for re-targetting on restore does ...
- Exchange VSS Writer failed restoring a backup because the logfile path ('%1') specified for re-targetting on restore does ...
- Exchange VSS Writer failed restoring a backup because the Restore Options string contains a database GUID ('%1') which does ...
- Exchange VSS Writer failed restoring a backup because the Restore Options string contains a database GUID ('%1') which does ...
- Exchange VSS Writer failed restoring a backup because the signature (%1) of the log files in the backup set being restored ...
- Exchange VSS Writer failed restoring a backup because the signature (%1) of the log files in the backup set being restored ...
- Exchange VSS Writer failed restoring a backup because the signature (%1) of the log files in the backup set does not match ...
- Exchange VSS Writer failed restoring a backup because the signature (%1) of the log files in the backup set does not match ...
- Exchange VSS Writer failed restoring a backup because the system path ('%1') specified for re-targetting on restore does ...
- Exchange VSS Writer failed restoring a backup because the system path ('%1') specified for re-targetting on restore does ...
- Exchange VSS Writer failed restoring a backup because the target database GUID ('%1') does not match the database GUID ('%2') ...
- Exchange VSS Writer failed restoring a backup because the target database GUID ('%1') does not match the database GUID ('%2') ...
- Exchange VSS Writer failed restoring a backup because the target log file path ('%1') does not match the log file path ('%2') ...
- Exchange VSS Writer failed restoring a backup because the target log file path ('%1') does not match the log file path ('%2') ...