Exchange VSS Writer failed restoring a backup because the database GUID '%1' was illegally mapped to GUID '%2' in the Restore Options string. The backup set is being restored to an alternate location, so if a database mapping is provided, the target database GUID must be the null GUID (ie. all zeroes).
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 database '%1' in '%2' of storage group '%3' is targeted for restore, ...
Exchange VSS Writer failed restoring a backup because the database GUID '%1' was illegally mapped multiple times in the Restore ...
Exchange VSS Writer failed restoring a backup because the database GUID '%1' was illegally mapped to GUID '%2' in the 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' 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 logfile base name ('%1') in the backup set does not match the logfile ...