Acronis Backup & Recovery 11.5 for MS SQL: Backing up Machine with MS SQL Server 2005 Fails with “Failed to Create Volume Snapshot”

October 12, 2012, 6:16 am

≫ Next: Acronis Backup & Recovery 11.5: Backup Fails after Upgrade with "Failed to Set the Snapshot Bitmap"

You are running a single-pass backup of SQL instances that fails with the error. To fix this issue, re-register the VSS service

This article applies to:

Acronis Backup & Recovery 11.5 for MS SQL

Symptoms

You have defined a single-pass backup of a SQL instance that fails with the following error:

An error occurred while executing the command.
Error code: 0x1510008
Tag: 0x7A8E520180FDC06F
ProtectCommand: Failed to execute the command.
Error code: 0x1330029
$module = "C:\Program Files (x86)\Acronis\BackupAndRecovery\mms.exe"
Tag: 0xE6792A5EE190DD9D
Step '{0}' has failed.
Error code: 0x1490002
TraceLevel = 1 (0x1),
$module = "C:\Program Files (x86)\Acronis\BackupAndRecovery\mms.exe"
Tag: 0x8EDC81EA38FAB93A
TOL: Failed to execute the command. The 'Backing up' command backs up the specif
ied data to the specified location.
Error code: 0x1350016
TraceLevel = 1 (0x1),
$module = "C:\Program Files (x86)\Common Files\Acronis\BackupAndRecovery\Com
mon\service_process.exe"
Tag: 0x8D165E86FB819624
Failed to back up the Microsoft SQL server.
Error code: 0x57000F
IsReturnCode = 1 (0x1)
Tag: 0x248C811650C646A0
Failed to request shadow copy operation.
Error code: 0x5702CB
$module = "C:\Program Files (x86)\Acronis\BackupAndRecovery\ArsDbBackupProvi
der64.exe"
Tag: 0x14FEB4C2D30AB725
Failed to create volume snapshot.
Error code: 0x70021
Tag: 0xE24F93D0B8D8C950
Failed to set snapshot bitmap.
Error code: 0x10C44E
blocks = 10485247 (0x9FFDFF)
Tag: 0x14181C22EF45ADD2
Not locked.
Error code: 0x9
code = 3758096392 (0xE0000008)
Tag: 0xABF5B651C7D88E41

Cause

There is a known issue in VSS functionality of MS SQL 2005, which is fixed in later a service pack. Or the VSS provider is broken and needs to be re-registered.

Solution

Make sure you have the latest MS SQL service packs installed for all instances on the machines.
Re-register the VSS provider using following batch file:
(!)Do not attempt this solution on Windows 2008 R2 or newer operating systems
(!) We recommend doing a partition backup before re-registering the VSS components.
1. Download and unpack this file: reregistervss.zip;
2. Go to Start -> Run -> cmd -> OK;
3. Run the batchfile.

More information

See Acronis Backup & Recovery 11.5.

Components:

Products:

Acronis Backup & Recovery 11.5

Segments:

日本語

↧

Acronis Backup & Recovery 11.5: Backup Fails after Upgrade with "Failed to Set the Snapshot Bitmap"

November 21, 2012, 4:52 am

≫ Next: MSI Installation eines Acronis Products schlägt im MSI Log mit SnapVSSProvider Fehler fehl

≪ Previous: Acronis Backup & Recovery 11.5 for MS SQL: Backing up Machine with MS SQL Server 2005 Fails with “Failed to Create Volume Snapshot”

After upgrading, the backups fails with "Failed to set the snapshot bitmap". To solve this issue, remove the Acronis VSS Provider from Windows registry

This article applies to:

Acronis Backup & Recovery 11.5

Symptoms

You have successfully upgraded from a previous Acronis Backup & Recovery version to Acronis Backup & Recovery 11.5;
You attempt to run a partition or disk backup operation and receive an error similar to this:

10 Information 15/11/2012 23:49:52 Pending Action 155 started: 'Creating partition image'.
11 Information 15/11/2012 23:50:18 Take a snapshot of volume '\ Device \ HarddiskVolume1' failed.
Additional info:
--------------------
Error Code: 50247
Modules: 16
Info Line: 14181c22ef45b0dd
Fields: $ module: disk_bundle_vs_32266
Message: Take a snapshot of volume '\ Device \ HarddiskVolume1' failed.
--------------------
Error code: 9
Modules: 0
Info Line: 2aacb7b2ab852ac
Fields: code: 50, $ module: disk_bundle_vs_32266
Message: Unknown status.
--------------------
Error Code: 65520
Modules: 0
Info Line: bd28fdbd64edb8e0
Fields: code: 2147942450, $ module: disk_bundle_vs_32266
Message: The request is not supported
--------------------
12 Information 15/11/2012 23:50:18 Volume 0-0 is blocked ...
13 Error 11/15/2012 23:50:29 Action with partition '0 -0 'was terminated.
Details:
Creating the volume snapshots failed.
Error code: 0x70021
$ Module = "disk_bundle_vs_32266"
Day 0xDF81DA2C74EC50B7
Failed to set the snapshot bitmap.
Error code: 0x10C44E
blocks = 25599 (0x63FF)
$ Module = "disk_bundle_vs_32266"
Day 0x14181C22EF45AE20
Not locked.
Error Code: 0x9
code = 3758096392 (0xE0000008)
$ Module = "disk_bundle_vs_32266"
Day 0x2AACB7B2AB852AC
Additional info:
--------------------
Error Code: 502
Modules: 1
Info Line: a164035b3ff39287
Fields: $ module: disk_bundle_vs_32266
Message: Action with partition '0 -0 'was terminated.
--------------------
Task 'Full backup' has failed on machine 'xxx'.

Cause

During the upgrade, the Acronis installer does not delete its old VSS provider from the registry. This key is causing the error, because of failing VSS operation.

Solution

To solve this issue, please follow these steps:

Open Windows registry editor. Go to Start -> Run -> regedit.exe -> hit Enter;
Navigate to this key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VSS\Providers\
Click then on Providers and delete the following entry below:

{f782463b-33bb-4043-ad8d-60b728d26a6c}

(!) Keep the green marked entry! Otherwise the Windows VSS provider will no longer operate.

↧

MSI Installation eines Acronis Products schlägt im MSI Log mit SnapVSSProvider Fehler fehl

November 22, 2012, 5:00 am

≫ Next: MSI Installation eines Acronis Products schlägt im MSI Log mit einem VSS Registrierungsfehler fehl

≪ Previous: Acronis Backup & Recovery 11.5: Backup Fails after Upgrade with "Failed to Set the Snapshot Bitmap"

Die Installation eines Acronis Produkts schlägt mit einem SnapVSSProvider Fehler im MSI Log fehl. Dieser Artikel enthält Informationen darüber, wie typische Fehler im MSI Log von Acronis Produkten gefunden, identifiziert und gelöst werden können.

Einleitung

Wenn die Log Datei in den Zeilen vor dem "Rückgabewert 3" den SnapVssProvider aufführt, meint das der Acronis VSS Provider nicht installiert werden konnte.

Lösung

Die Analyse des MSI Logs basiert im Grunde auf den Fehlermeldung(en) der letzten Operation, die in der Log Datei gefunden wurde. Bitte betrachten Sie die beiden Beispiele weiter unten:

SnapVssProvider Beispiel aus MSI log:

MSI Log Ausschnitt

...
[CUSTOMACTION]: Creating a new COM+ application:
[CUSTOMACTION]: - Creating the catalog object
[CUSTOMACTION]: - Get the Applications collection
[CUSTOMACTION]: - Populate...
[CUSTOMACTION]: - Add new application object
[CUSTOMACTION]: - Set app name = Acronis VSS Provider
[CUSTOMACTION]: - Set app description = VSS Provider
[CUSTOMACTION]: - Set app access check = true
[CUSTOMACTION]: - Set encrypted COM communication = true
[CUSTOMACTION]: - Set secure references = true
[CUSTOMACTION]: - Set impersonation = false
[CUSTOMACTION]: - Save changes...
[CUSTOMACTION]: - Create Windows service running as Local System
[CUSTOMACTION]: - Add the DLL component
[CUSTOMACTION]: ERROR:
[CUSTOMACTION]: - Error code: -2146368511 [0x80110401]
[CUSTOMACTION]: - Exit code: 113
[CUSTOMACTION]: - Description:
[CUSTOMACTION]: - Source:
[CUSTOMACTION]: - Help file:
[CUSTOMACTION]: - Help context: 0
[CUSTOMACTION]: - COM+ Errors detected: (2)
[CUSTOMACTION]: * (COM+ ERROR 0) on C:\WINDOWS\system32\snapapivss.dll
[CUSTOMACTION]: ErrorCode: -2146368486 [0x8011041A]
[CUSTOMACTION]: MajorRef: C:\WINDOWS\system32\snapapivss.dll
[CUSTOMACTION]: MinorRef:
[CUSTOMACTION]: * (COM+ ERROR 1) on SnapVssProvider
[CUSTOMACTION]: ErrorCode: -2146368486 [0x8011041A]
[CUSTOMACTION]: MajorRef: {5FC845EB-F299-40F0-9725-34045F7EA8BA}
[CUSTOMACTION]: MinorRef:
Action ended 7:52:24: InstallFinalize. Rückgabewert 3
...

Hier können Sie zwei COM+ Fehler sehen. Einer der Fehler deutet auf den SnapVSSProvider und der zweite auf die snapapivss.dll. Das deutet auf ein Problem mit der Installation des Acronis VSS Providers hin.

Hier sind die beiden Fehler Codes, die im Log zu finden sind:

0x80110401 - Fehler beim Zugriff auf ein oder mehrere Objekte - die Fehler Information kann mehr Details enthalten.
0x8011041A - Die Komponenten Installation des DllRegisterServer schlägt fehl

Die häufigste Ursache für diesen Fehler ist, dass der Volume Shadow Copy Dienst deaktiviert oder nicht gestartet ist. Sie sollten sicherstellen, dass der Dienst nicht deaktiviert ist und den Dienst zum Test starten. Falls der Dienst aus irgend einem Grund scheitert, meint das es ein Problem mit dem VSS Subsystem selbst gibt.

Falls das Starten des Volume Shadow Copy Dienstes nicht hilft, fahren Sie bitte wie folgt fort:

Löschen Sie den Acronis VSS Provider aus der Systemsteuerung -> Verwaltung -> Komponentendienste -> Computers -> Mein Computer -> COM+ Anwendungen -> System Anwendungen
Löschen Sie die Datei \Windows\System32\snapapivss.dll, falls es existiert
Finden und löschen Sie alle Registry Schlüssel (Start -> Ausführen-> Regedit -> Enter), welche folgenden GUID's enthalten:
- F5DBCC43-B847-494e-8083-F030501DA611
- 89CDAF20-82B6-42cd-A4B4-573C81999C35
- 5FC845EB-F299-40f0-9725-34045F7EA8BA
  Es wird Schlüssel geben, die mit SnapVSSProvider beginnen, wenn Sie nach 5FC845EB-F299-40f0-9725-34045F7EA8BA suchen. Diese Schlüssel sollten auch gelöscht werden.
Wiederholen Sie die Installation des Produkts
Starten Sie das System neu

Weitere Information

Siehe Analyse der Installations-Logs von Acronis Produkten basierend auf MSI Technologie

MSI Installation eines Acronis Products schlägt im MSI Log mit einem VSS Registrierungsfehler fehl

November 30, 2012, 7:01 am

≫ Next: MSI Installation von Acronis Backup & Recovery 10 oder Acronis True Image Echo schlägt mit VSS Registrierung im MSI Log fehl

≪ Previous: MSI Installation eines Acronis Products schlägt im MSI Log mit SnapVSSProvider Fehler fehl

Die Installation eines Acronis Produkts schlägt mit einem VSS Registrierungsfehler im MSI Log fehl. Dieser Artikel enthält Informationen darüber, wie typische Fehler im MSI Log von Acronis Produkten gefunden, identifiziert und gelöst werden können.

Einleitung

Während der Installation, versucht das Acronis Produkt den Acronis VSS Provider zu registrieren. Dieser Artikel enthält Informationen darüber, wie typische Fehler im MSI Log von Acronis Produkten gefunden, identifiziert und gelöst werden können.

Lösung

VSS Registrierungsfehler 1 aus dem MSI Log:

MSI Log Ausschnitt:

...
1: MSIGEN:MsiVSSInstall: execution started.
1: MSIGEN:MsiVSSInstall: Removed registry key
SYSTEM\CurrentControlSet\Services\VSS\Providers\{F5DBCC43-B847-494E-8083-F030501DA611}, result 0
1: MSIGEN:MsiVSSInstall: Path to snapapivss.dll: C:\Program Files\Common
Files\Acronis\SnapAPI\snapapivss.dll
1: MSIGEN:MsiVSSInstall: Short path to snapapivss.dll:
C:\PROGRA~1\COMMON~1\Acronis\SnapAPI\snapapivss.dll
1: MSIGEN:MsiVSSInstall: Unregistered VSS provider
(C:\WINDOWS\system32\snapapivss.dll), error 1
Action ended at 17:26:45: InstallFinalize. Rückgabewert 3.
..

Das ist ein seltenes Windows basiertes Problem. Während der Installation verwendet das Acronis Produkt ein Microsoft Visual Basic Script um den Acronis VSS Provider zu registrieren. Es gibt ein Problem mit dem Microsoft CScript, das einen falschen Wert zurückliefert, was zu einem Rollback führt.

Um das Problem zu lösen, installieren Sie den Acronis Agent (Acronis Backup & Recovery 10 Build 11345 oder höher) mit folgendem Befehl, der den Fehler ignoriert:

msiexec.exe /i [PATH]AcronisAgentWindows.msi IGNORE_VSS_REGISTRATION_ERRORS=1

Wo [PATH] der Pfad zur AcronisAgentWindows.msi Datei ist.

Zum Beispiel:

msiexec.exe /i C:\AcronisAgentWindows.msi IGNORE_VSS_REGISTRATION_ERRORS=1

(!) Acronis Backup & Recovery 11 und höher ignorieren diesen Fehler automatisch.

VSS Registrierungsfehler 2 aus dem MSI Log:

MSI Log Ausschnitt:

...
1: MSIGEN:MsiVSSInstall: Registered VSS provider (C:\PROGRA~1\COMMON~1\Acronis\SnapAPI\SNAPAP~1.DLL), error 113
MSI (s) (CC:E8) [20:00:29:494]: User policy value 'DisableRollback' is 0
MSI (s) (CC:E8) [20:00:29:494]: Machine policy value 'DisableRollback' is 0
Action ended at 20:00:29: InstallFinalize. Rückgabewert 3.
...

Die Installation schlägt fehl durch Reste der vorherigen Installationsversuche. Entfernen Sie diese Spuren, indem Sie die folgenden Registry Schlüssel löschen und die Installation erneut starten:

HKEY_LOCAL_MACHINE\SOFTWARE\Acronis
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3\SelfReg\CLSID\{79079D5C-EF20-4952-B9FC-CFD443B38641}
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3\SelfReg\SnapVssProvider.SnapVssProvider
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3\SelfReg\SnapVssProvider.SnapVssProvider.1
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{f782463b-33bb-4043-ad8d-60b728d26a6c}

Weitere Information

Siehe Analyse der Installations-Logs von Acronis Produkten basierend auf MSI Technologie

MSI Installation von Acronis Backup & Recovery 10 oder Acronis True Image Echo schlägt mit VSS Registrierung im MSI Log fehl

December 4, 2012, 6:06 am

≫ Next: Acronis Backup & Recovery 11.5: Backup on Windows XP Fails with Error 'Failed to Create Volume Snapshot' If MS SQL Server is Installed

≪ Previous: MSI Installation eines Acronis Products schlägt im MSI Log mit einem VSS Registrierungsfehler fehl

Installation von Acronis Backup & Recovery 10 oder Acronis True Image Echo schlägt mit VSS Registrierung im MSI Log fehl. Das Problem liegt im COM+ Subsystem.

Einführung

Die Installation eines Acronis Backup & Recovery 10 oder Acronis True Image Echo Produkts schlägt bei der VSS Registrierung fehl. Dieser Artikel enthält Informationen darüber, wie typische Fehler im MSI Log von Acronis Produkten gefunden, identifiziert und gelöst werden können.

Lösung

Die Analyse des MSI Logs basiert auf den Fehlermeldung(en) der letzten Operation, die in der Log Datei gefunden wurde:

MSI Log Ausschnitt:

...
[CUSTOMACTION]: - Error code: -2146367487 [0x80110801]
[CUSTOMACTION]: - Exit code: 205
[CUSTOMACTION]: - Description:
[CUSTOMACTION]: - Source:
[CUSTOMACTION]: - Help file:
[CUSTOMACTION]: - Help context: 0
Action ended 7:01:46: InstallFinalize. Rückgabewert 3.
...

Ursache: ERROR CODE = 0x80110801 Setup konnte den COM+ Katalog nicht initialisieren. COM+ wird ohne Katalog nicht korrekt arbeiten.

Das ist ein Problem mit dem COM+ Subsystem.

Um das Problem zu lösen, müssen Sie den COM+ reparieren oder erneut installieren, wie im Microsoft Knowledge Base Article 318731 beschrieben.

Weitere Information

Siehe Analyse der Installations-Logs von Acronis Produkten basierend auf MSI Technologie

Products:

English

↧

Acronis Backup & Recovery 11.5: Backup on Windows XP Fails with Error 'Failed to Create Volume Snapshot' If MS SQL Server is Installed

March 21, 2013, 3:26 am

≫ Next: Acronis Backup & Recovery 11.5: Recovery of MS Exchange Database/Storage Group Fails If Committed Transaction Log Is Missing in the Backup

≪ Previous: MSI Installation von Acronis Backup & Recovery 10 oder Acronis True Image Echo schlägt mit VSS Registrierung im MSI Log fehl

Backup on Windows XP fails with error "Failed to create volume snapshot" if MS SQL Server is installed.

This article applies to:

Acronis Backup & Recovery 11.5 (Build 11.5.37588 or higher)

Symptoms

You have installed Acronis Backup & Recovery 11.5 on a Windows XP System;
On this system MS SQL Server is installed and running;
(!) MS SQL Express 2008 is automatically installed along the installation of Acronis Management Server component.
You run a disk or volume backup with the default settings:
1. Use VSS option = enabled (default backup option value);
2. Software-System provider or Software-Select automatically selected (default backup option value);
3. Enable VSS Full Backup is disabled (default backup option value);
This backup fails with:
Failed to create volume snapshot.
See a complete sample error message:
Command 'Running backup plan 'Backup 3/1/2013 8:24:23 PM'' has failed.
Additional info:
--------------------
Error code: 61
Module: 309
LineInfo: 4a8728dc8a1c950f
Fields: $module: mms_vs_37588
Message: Command 'Running backup plan 'Backup 3/1/2013 8:24:23 PM'' has failed.
--------------------
Error code: 41
Module: 307
LineInfo: e6792a5ee190dda7
Fields: $module: agent_protection_addon_vs_37588
Message: ProtectCommand: Failed to execute the command.
--------------------
Error code: 3
Module: 329
LineInfo: 1cd98aae889424f9
Fields: $module: disk_bundle_vs_37588
Message: Backup has failed.
--------------------
Error code: 1060
Module: 1
LineInfo: b43e776571144dec
Fields: $module: disk_bundle_vs_37588
Message: Failed to commit operations.
--------------------
Error code: 33
Module: 7
LineInfo: a5695862aaf8e69b
Fields: $module: disk_bundle_vs_37588
Message: Failed to create volume snapshot.
--------------------
Error code: 50242
Module: 16
LineInfo: 14181c22ef45b0f6
Fields: $module : disk_bundle_vs_37588
Message: Failed to start creating the volume snapshot.
--------------------
Error code: 50281
Module: 16
LineInfo: 14181c22ef45a9e9
Fields: $module : disk_bundle_vs_37588
Message: VSS writer 'SqlServerWriter' with class ID 'A65FAA63-5EA8-4EBC-9DBD-A0C4DB26912A' has failed to process the snapshot.
--------------------
Error code: 65520
Module: 0
LineInfo: bd28fdbd64edb8ea
Fields: code: 2147754996, $module : disk_bundle_vs_37588
Message: Unknown Win32 error
--------------------
ProtectCommand : Échec de l'exécution de la commande.
Informations additionnelles :
--------------------
Code d'erreurs : 41
Module : 307
LineInfo : e6792a5ee190dda7
Champs : $module : agent_protection_addon_vs_37613
Message : ProtectCommand : Échec de l'exécution de la commande.
--------------------
Code d'erreurs : 3
Module : 329
LineInfo : 1cd98aae889424f9
Champs : $module : disk_bundle_vs_37613
Message : La sauvegarde a échoué.
--------------------
Code d'erreurs : 1060
Module : 1
LineInfo : b43e776571144dec
Champs : $module : disk_bundle_vs_37613
Message : Échec de la validation des opérations.
--------------------
Code d'erreurs : 33
Module : 7
LineInfo : a5695862aaf8e69b
Champs : $module : disk_bundle_vs_37613
Message : Impossible de créer une image statique du volume.
--------------------
Code d'erreurs : 50242
Module : 16
LineInfo : 14181c22ef45b0f6
Champs : $module : disk_bundle_vs_37613
Message : Échec du démarrage de la création de l'instané du volume.
--------------------
Code d'erreurs : 50281
Module : 16
LineInfo : 14181c22ef45a9e9
Champs : $module : disk_bundle_vs_37613
Message : L'enregistreur VSS « SqlServerWriter » avec l'ID de classe « A65FAA63-5EA8-4EBC-9DBD-A0C4DB26912A » a échoué le traitement de l'instantané.
--------------------
Code d'erreurs : 65520
Module : 0
LineInfo : bd28fdbd64edb8ea
Champs : code : 2147754996, $module : disk_bundle_vs_37613
Message : Unknown Win32 error

Cause

This is an issue in the product

Solution

To work around this issue, please enable the VSS Full backup option.

Navigate to the backup plan options or to the default backup options -> Volume Shadow Copy Service and enable the VSS Full backup option. See Enabling VSS Full backup in user guide.

More information

See also:

Acronis Backup & Recovery 11.5
User guide: Enabling VSS Full backup

Operating Systems:

Components:

Products:

Segments:

↧

Acronis Backup & Recovery 11.5: Recovery of MS Exchange Database/Storage Group Fails If Committed Transaction Log Is Missing in the Backup

March 21, 2013, 5:56 am

≫ Next: Acronis Backup & Recovery 11.5: Backup schlägt nach Upgrade fehl mit "Snapshot Bitmap konnte nicht gesetzt werden"

≪ Previous: Acronis Backup & Recovery 11.5: Backup on Windows XP Fails with Error 'Failed to Create Volume Snapshot' If MS SQL Server is Installed

Recovery of MS Exchange database/storage group fails if committed transaction log is missing in the backup

This article applies to:

Acronis Backup & Recovery 11.5 Agent for Exchange

Symptoms

You have installed Acronis Backup & Recovery 11.5 with Agent for Exchange;
A recovery operation of a database or storage group fails for one of these three symptoms:

Case 1: Database or storage group recovery to MS Exchange fails in the end of operation:

You run database-level recovery task and it fails at the end of the task with VSS error similar to the following:

Message: A Volume Shadow Copy Service (VSS) API error has occurred. Failed to notify Microsoft Exchange Server VSS Writer that the current recovery has completed.

See a complete sample error message:

Also the following error may be shown in the Event Viewer:

Information Store (2356) Second Storage Group: Database C:\Program Files\Microsoft\Exchange Server\Mailbox\Second Storage Group\Public Folder Database.edb requires log files 2886-2887 in order to recover all committed data. Recovery could only locate up to log file C:\Program Files\Microsoft\Exchange Server\Mailbox\Second Storage Group\E01.log, and could not locate log generation 2887. If the log file cannot be found, the database(s) can be recovered manually, but this will result in losing committed data.

Case 2: Database or storage group recovery to MS Exchange fails at the beginning of operation.

You run database-level recovery task and it fails at the end of the task with VSS error similar to the following:

Message: A Volume Shadow Copy Service (VSS) API error has occurred. Failed to notify Microsoft Exchange Server VSS Writer to prepare for recovery.

See a complete sample error message:

Case 3: Recovered MS Exchange database or storage group cannot be mounted

You have recovered database or storage group to a separate folder and try to mount it - operation fails because of database dirty shutdown state.

After that you launch "eseutil /r <Enn>" to bring the database to Clean Shutdown state, but it fails with the error message:

Operation terminated with error -582 (JET_errCommittedLogFilesMissing, One or more logs that were committed to this database, are missing. These log files are required to maintain durable ACID semantics, but not required to maintain consistency if the JET_bitReplayIgnoreLostLogs bit is specified during recovery.) after 0.250 seconds.

Cause

Some transaction logs are missing (or corrupted) in the backup.

It is possible to recover such database with some additional steps, but data committed from missing transaction log will be lost.

Solution

Database in the target location may be in inconsistent state after failed recovery with VSS error.

In order to recover database from the backup to the target location successfully, it is necessary restore database files to temporary location and repair the database manually.

After that you can move extracted database files to the target location.

Please follow the steps below:

Recover database or storage group to some temporary folder;
Open a command line; Go to Start -> run -> cmd (when UAC activated, right click and start as administrator);
Navigate to temporary folder where database or storage group was extracted (using CD command), for example:

CD c:\<PATH_TO_FOLDER>\
Repair extracted database using command:

eseutil /r Enn /a /i /D <DB Catalog>
(!) Enn is transaction log files prefix - for example, E00.
(!)<DB Catalog> - folder with extracted .edb file
Make sure that database is healthy (for healthy database "State" field value is "Clean Shutdown"):

eseutil /m <EDB-file>
(!) .EDB file name in the target folder where target database\storage group (which should be restored with data from the backup) is located.
Delete contents of target folder (after failed recovery database may be inconsistent);
Move contents of the temporary folder to target folder location;
Make sure that .EDB file name is the same as you noted on step 5. Rename it if necessary;
Mount Exchange database in target location folder.

More information

See Acronis Backup & Recovery 11.5.

Components:

Products:

Segments:

↧

Acronis Backup & Recovery 11.5: Backup schlägt nach Upgrade fehl mit "Snapshot Bitmap konnte nicht gesetzt werden"

March 27, 2013, 3:28 am

≫ Next: Acronis Backup & Recovery: Disk Backup mit Acronis VSS Provider schlägt auf Windows SBS und Domain Controller fehl

≪ Previous: Acronis Backup & Recovery 11.5: Recovery of MS Exchange Database/Storage Group Fails If Committed Transaction Log Is Missing in the Backup

Nach einem Upgrade schlägt ein Backup fehl mit "Snapshot Bitmap konnte nicht gesetzt werden". Um dieses Problem zu lösen, entfernen Sie den Acronis VSS Provider aus der Windows Registry.

Dieser Artikel betrifft:

Acronis Backup & Recovery 11.5

Symptome

Sie haben erfolreich von einer vorhergehenden Acronis Backup & Recovery Version auf Acronis Backup & Recovery 11.5 aktualisiert;
Sie versuchen ein Partitions- oder Disk Backup zu erstellen und erhalten einen Fehler, ähnlich wie diesen:

Ursache

Während der Aktualisierung hat der Acronis Installer nicht den alten VSS Provider aus der Registry gelöscht. Wegen dieses Schlüssels scheitert die VSS Operation.

Lösung

Um das Problem zu lösen, folgen Sie diesen Schritten:

Öffnen Sie den Windows Registry Editor. Gehen Sie auf Start -> Ausführen -> regedit.exe -> drücken Sie Enter;
Navigieren Sie zu diesem Schlüssel:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VSS\Providers\
Klicken Sie auf Providers und löschen Sie diesen Schlüssel:

{f782463b-33bb-4043-ad8d-60b728d26a6c}

(!) Behalten Sie den grün markierten Eintrag! Anderenfalls wird der Windows VSS Provider nicht mehr funktionieren.

Weitere Information

Siehe Acronis Backup & Recovery 11.5.

Products:

Acronis Backup & Recovery 11.5

Segments:

English

↧

Acronis Backup & Recovery: Disk Backup mit Acronis VSS Provider schlägt auf Windows SBS und Domain Controller fehl

March 28, 2013, 6:18 am

≫ Next: Acronis Backup & Recovery 11.5: Backup of Windows Small Business Server 2011 Fails with "Unknown Win32 Error"

≪ Previous: Acronis Backup & Recovery 11.5: Backup schlägt nach Upgrade fehl mit "Snapshot Bitmap konnte nicht gesetzt werden"

Event Codes:

0x000101F6+0x00070021+0x0010C442+0x0010C469+0x0000FFF0+0x800423F0

0x0135003D+0x01490003+0x00010424+0x00070021+0x0010C442+0x0010C469+0x0000FFF0+0x800423F0

Als Workaround verwenden Sie den Microsoft VSS statt den Acronis VSS Provider

Dieser Artikel betrifft:

Acronis Backup & Recovery 10
Acronis Backup & Recovery 11
Acronis Backup & Recovery 11.5

Symptome

1. Sie haben einen Windows Server mit einer Active Directory Rolle (ein SBS oder Domain Controller) und der NTDS VSS Writer ist im System vorhanden.
(!) Sie können die Liste der Writer im System prüfen, indem Sie das Kommando "vssadmin list writers" via Start -> Ausführen -> cmd ausführen.

Sehen Sie eine Beispiel Fehlermeldung:

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {2c1835fd-ea22-430e-ab0c-6ce37430d3d2}
State: [5] Waiting for completion
Last error: No error

Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {a9d9c7f7-b201-4d4b-8cff-8e6899ce4f63}
State: [5] Waiting for completion
Last error: No error

Writer name: 'FRS Writer'
Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
Writer Instance Id: {53ab51c5-acef-4451-a224-c7b1fbf15b10}
State: [5] Waiting for completion
Last error: No error

Writer name: 'FSRM Writer'
Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
Writer Instance Id: {48edb3d3-d652-44ec-bb72-ac26a0c7d595}
State: [5] Waiting for completion
Last error: No error

Writer name: 'NPS VSS Writer'
Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
Writer Instance Id: {0e8bb704-019a-45ff-99dd-c20dc0783a88}
State: [5] Waiting for completion
Last error: No error

Writer name: 'Certificate Authority'
Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
Writer Instance Id: {7c23598a-50a5-4166-9186-35162c8e5ce5}
State: [5] Waiting for completion
Last error: No error

Writer name: 'SPSearch4 VSS Writer'
Writer Id: {35500004-0201-0000-0000-000000000000}
Writer Instance Id: {7b4cb07b-da62-4039-b85d-6d2431906366}
State: [8] Failed
Last error: Inconsistent shadow copy

Writer name: 'MSSearch Service Writer'
Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
Writer Instance Id: {2af63699-a25d-4aa2-8d8c-3d26a170d81e}
State: [5] Waiting for completion
Last error: No error

Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {2a5a9421-41d8-488d-a888-0d110ee7aacb}
State: [5] Waiting for completion
Last error: No error

Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {3fd61b6f-d660-4c98-ac0d-48d3c281b31c}
State: [5] Waiting for completion
Last error: No error

Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {751c23a9-ca49-4be4-b76c-7cfde340b9ce}
State: [5] Waiting for completion
Last error: No error

Writer name: 'TS Gateway Writer'
Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
Writer Instance Id: {fcb91c9e-b4b6-4490-8fd0-a3edada84aa1}
State: [5] Waiting for completion
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {a0dfcc13-0ec4-48bf-8ad5-a854b34fe439}
State: [5] Waiting for completion
Last error: No error

Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {789322e9-9901-462c-a92e-05d70bcdf6ae}
State: [5] Waiting for completion
Last error: No error

2. Sie erstellen ein Disk Backup von diesem Server. Die Option Verwende Volume Shadow Copy service (VSS) ist ausgewählt und der Snapshot Provider ist Software - Acronis VSS Provider.

3. Das Backup schlägt mit einem Snapshot Fehler fehl, ähnlich diesem:

Erstellen des Volumen Snapshots ist fehlgeschlagen

4. Das Windows Anwendungs-Event-Log zeigt einen Fehler, ähnlich diesem:

Log Name: Application
Source: ESENT
Event ID: 455
Task Category: Logging/Recovery
Level: Error
Description:
lsass (616) Error -1023 (0xfffffc01) occurred while opening logfile C:\Device\snapman\Windows\ntds\edb.log.

5. Error log shows an error similar to this:

Unknown Win32 error

Event code: 0x000101F6+0x00070021+0x0010C442+0x0010C469+0x0000FFF0+0x800423F0

oder:

Event code: 0x0135003D+0x01490003+0x00010424+0x00070021+0x0010C442+0x0010C469+0x0000FFF0+0x800423F0

Sehen Sie eine Beispiel Fehlermeldung:

Message: Command 'Backing up' has failed.

Additional info:
--------------------
Error code: 61
Module: 309
LineInfo: 4a8728dc8a1c950f
Fields: $module : service_process_vs_37608
Message: Command 'Backing up' has failed.
--------------------
Error code: 3
Module: 329
LineInfo: 1cd98aae889424f9
Fields: $module : disk_bundle_vs_37608
Message: Backup has failed.
--------------------
Error code: 1060
Module: 1
LineInfo: b43e776571144dec
Fields: $module : disk_bundle_vs_37608
Message: Failed to commit operations.
--------------------
Error code: 33
Module: 7
LineInfo: a5695862aaf8e69b
Fields: $module : disk_bundle_vs_37608
Message: Failed to create volume snapshot.
--------------------
Error code: 50242
Module: 16
LineInfo: 14181c22ef45b0f6
Fields: $module : disk_bundle_vs_37608
Message: Failed to start creating the volume snapshot.
--------------------
Error code: 50281
Module: 16
LineInfo: 14181c22ef45a9e9
Fields: $module : disk_bundle_vs_37608
Message: VSS writer 'SPSearch4 VSS Writer' with class ID '35500004-0201-0000-0000-000000000000' has failed to process the snapshot.
--------------------
Error code: 65520
Module: 0
LineInfo: bd28fdbd64edb8ea
Fields: code : 2147754992, $module : disk_bundle_vs_37608
Message: Unknown Win32 error
--------------------
Acronis Knowledge Base: http://kb.acronis.com/errorcode/

Event code: 0x0135003D+0x01490003+0x00010424+0x00070021+0x0010C442+0x0010C469+0x0000FFF0+0x800423F0

Message: Operation with partition '0-0' was terminated.
Details: Failed to create volume snapshot.
Error code: 0x70021
$module = "disk_bundle_vs_37608"
Tag: 0xA5695862AAF8E69B
Failed to start creating the volume snapshot.
Error code: 0x10C442
$module = "disk_bundle_vs_37608"
Tag: 0x14181C22EF45B0F6
VSS writer 'SPSearch4 VSS Writer' with class ID '35500004-0201-0000-0000-000000000000' has failed to process the snapshot.
Error code: 0x10C469
$module = "disk_bundle_vs_37608"
Tag: 0x14181C22EF45A9E9
Unknown Win32 error
Error code: 0xFFF0
code = 2,147,754,992 (0x800423F0),
$module = "disk_bundle_vs_37608"
Tag: 0xBD28FDBD64EDB8EA

Additional info:
--------------------
Error code: 502
Module: 1
LineInfo: a164035b3ff39289
Fields: $module : disk_bundle_vs_37608
Message: Operation with partition '0-0' was terminated.
Details: Failed to create volume snapshot.

Error code: 0x70021
$module = "disk_bundle_vs_37608"
Tag: 0xA5695862AAF8E69B
Failed to start creating the volume snapshot.

Error code: 0x10C442
$module = "disk_bundle_vs_37608"
Tag: 0x14181C22EF45B0F6
VSS writer 'SPSearch4 VSS Writer' with class ID '35500004-0201-0000-0000-000000000000' has failed to process the snapshot.

Error code: 0x10C469
$module = "disk_bundle_vs_37608"
Tag: 0x14181C22EF45A9E9
Unknown Win32 error

Error code: 0xFFF0
code = 2,147,754,992 (0x800423F0),
$module = "disk_bundle_vs_37608"
Tag: 0xBD28FDBD64EDB8EA
--------------------
Error code: 33
Module: 7
LineInfo: a5695862aaf8e69b
Fields: $module : disk_bundle_vs_37608
Message: Failed to create volume snapshot.
--------------------
Error code: 50242
Module: 16
LineInfo: 14181c22ef45b0f6
Fields: $module : disk_bundle_vs_37608
Message: Failed to start creating the volume snapshot.
--------------------
Error code: 50281
Module: 16
LineInfo: 14181c22ef45a9e9
Fields: $module : disk_bundle_vs_37608
Message: VSS writer 'SPSearch4 VSS Writer' with class ID '35500004-0201-0000-0000-000000000000' has failed to process the snapshot.
--------------------
Error code: 65520
Module: 0
LineInfo: bd28fdbd64edb8ea
Fields: code : 2147754992, $module : disk_bundle_vs_37608
Message: Unknown Win32 error
--------------------
Acronis Knowledge Base: http://kb.acronis.com/errorcode/

Event code: 0x000101F6+0x00070021+0x0010C442+0x0010C469+0x0000FFF0+0x800423F0

Ursache

Die Ursache der Probleme liegt in der Kommunikation zwischen dem Acronis VSS Provider und dem NTDS Writer, verursacht durch Acronis VSS Provider Limitationen. Wenn der Acronis VSS Provider für die VSS Unterstützung verwendet wird, erfolgt der finale Snapshot durch die Acronis SnapAPI Treiber Technologie. Der NTDS Writer benötigt den Snapshot Pfad, der durch die Besonderheiten der SnapAPI Snapshot Spezifikationen und den Acronis VSS Provider Funktionen nicht geliefert werden kann.

Lösung

Als Workaround verwenden Sie den Microsoft VSS Provider statt dem Acronis VSS Provider. Sie müssen die Änderung in der Option Volume Shadow Copy Service umstellen. Stellen Sie sicher, dass die Option VSS verwenden ausgewählt ist. Als Snapshot Provider stellen Sie folgendes ein: Software - System Provider.

Siehe Acronis Backup & Recovery 11: Microsoft VSS anstelle von Acronis VSS verwenden.

(!) Es kann ein separates Problem mit Backups unter Verwendung des Microsoft VSS Providers auf Windows Small Business Server 2011 Systemen geben, nachdem das Microsoft SharePoint Foundation 2010 Service Pack 1 (SP1) installiert wurde.

There may be a separate issue where backups with Microsoft VSS provider on may not work correctly after installation.

Um die SharePoint Datenbanken zu aktualisieren, lassen Sie das PSconfig Dienstprogramm manuell laufen

Operating Systems:

Components:

Products:

Segments:

↧

Acronis Backup & Recovery 11.5: Backup of Windows Small Business Server 2011 Fails with "Unknown Win32 Error"

April 19, 2013, 3:31 pm

≫ Next: Acronis Backup Software: Troubleshooting Snapshot Issues

≪ Previous: Acronis Backup & Recovery: Disk Backup mit Acronis VSS Provider schlägt auf Windows SBS und Domain Controller fehl

Event Codes:

0x0135003D+0x01490003+0x00010424+0x00070021+0x0010C442+0x0010C469+0x0000FFF0+0x800423F4

0x000101F6+0x00070021+0x0010C442+0x0010C469+0x0000FFF0+0x800423F4

Backup of Windows Small Business Server 2011 fails with "Unknown Win32 error"

This article applies to:

Acronis Backup & Recovery 11.5 Server for Windows
Acronis Backup & Recovery 11.5 Advanced Server Windows
Acronis Backup & Recovery 11.5 Advanced Server SBS Edition

Symptoms

You are running Acronis Backup & Recovery 11.5 on a Windows Small Business Server 2011 machine;
The backup fails with:
Unknown Win32 error
Event code: 0x0135003D+0x01490003+0x00010424+0x00070021+0x0010C442+0x0010C469+0x0000FFF0+0x800423F4
Event code: 0x000101F6+0x00070021+0x0010C442+0x0010C469+0x0000FFF0+0x800423F4

See the complete example error message:

Error code: 0xFFF0
code = 2,147,754,996 (0x800423F4),
$module = "disk_bundle_vs_37608"
Tag: 0xBD28FDBD64EDB8EA
--------------------
Error code: 33
Module: 7
LineInfo: a5695862aaf8e69b
Fields: $module : disk_bundle_vs_37608
Message: Failed to create volume snapshot.
--------------------
Error code: 50242
Module: 16
LineInfo: 14181c22ef45b0f6
Fields: $module : disk_bundle_vs_37608
Message: Failed to start creating the volume snapshot.
--------------------
Error code: 50281
Module: 16
LineInfo: 14181c22ef45a9e9
Fields: $module : disk_bundle_vs_37608
Message: VSS writer 'SqlServerWriter' with class ID 'A65FAA63-5EA8-4EBC-9DBD-A0C4DB26912A' has failed to process the snapshot.
--------------------
Error code: 65520
Module: 0
LineInfo: bd28fdbd64edb8ea
Fields: code : 2147754996, $module : disk_bundle_vs_37608
Message: Unknown Win32 error
--------------------
Acronis Knowledge Base: http://kb.acronis.com/errorcode/

Event code: 0x000101F6+0x00070021+0x0010C442+0x0010C469+0x0000FFF0+0x800423F4

============================================================

Message: Command 'Backing up' has failed.

Additional info:
--------------------
Error code: 61
Module: 309
LineInfo: 4a8728dc8a1c950f
Fields: $module : service_process_vs_37608
Message: Command 'Backing up' has failed.
--------------------
Error code: 3
Module: 329
LineInfo: 1cd98aae889424f9
Fields: $module : disk_bundle_vs_37608
Message: Backup has failed.
--------------------
Error code: 1060
Module: 1
LineInfo: b43e776571144dec
Fields: $module : disk_bundle_vs_37608
Message: Failed to commit operations.
--------------------
Error code: 33
Module: 7
LineInfo: a5695862aaf8e69b
Fields: $module : disk_bundle_vs_37608
Message: Failed to create volume snapshot.
--------------------
Error code: 50242
Module: 16
LineInfo: 14181c22ef45b0f6
Fields: $module : disk_bundle_vs_37608
Message: Failed to start creating the volume snapshot.
--------------------
Error code: 50281
Module: 16
LineInfo: 14181c22ef45a9e9
Fields: $module : disk_bundle_vs_37608
Message: VSS writer 'SqlServerWriter' with class ID 'A65FAA63-5EA8-4EBC-9DBD-A0C4DB26912A' has failed to process the snapshot.
--------------------
Error code: 65520
Module: 0
LineInfo: bd28fdbd64edb8ea
Fields: code : 2147754996, $module : disk_bundle_vs_37608
Message: Unknown Win32 error
--------------------
Acronis Knowledge Base: http://kb.acronis.com/errorcode/

Event code: 0x0135003D+0x01490003+0x00010424+0x00070021+0x0010C442+0x0010C469+0x0000FFF0+0x800423F4

Cause

The Acronis Managed Machine service user does not have appropriate rights for running this operation with VSS Service for SQL Server. As a result the snapshot of the SqlServerWriter fails.

You can check if the SqlServerWriter fails with the command vssadmin list writers.

Open command prompt (Win+R -> cmd -> Enter):
Enter this command: vssadmin list writers:
The output should contain this:
....
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {ac3d731f-6a0f-4537-8d6f-1ffad6dd9d8f}
State: [8] Failed
Last error: Non-retryable error
....

Solution

Please check what user is used for running the Acronis Managed Machine service:

Open command prompt (Win+R -> cmd -> Enter);
Enter this command: services.msc:
Navigate in the overview to Acronis Managed Machine service:

In this example the Acronis Agent User 5 is set to start this service.

It is preferred that the user of the Acronis Managed Machine service is member of the domain admin group. If you need to add the appropriate rights manually, please see Acronis Backup & Recovery: Adding Necessary Rights.

More information

See also:

Operating Systems:

Components:

Products:

Segments:

↧

Acronis Backup Software: Troubleshooting Snapshot Issues

December 24, 2013, 12:51 am

≫ Next: MSI Installation eines Acronis Products schlägt im MSI Log mit SnapVSSProvider Fehler fehl

≪ Previous: Acronis Backup & Recovery 11.5: Backup of Windows Small Business Server 2011 Fails with "Unknown Win32 Error"

Instructions on how to resolve and troubleshoot snapshot issues.

This article applies to:

Acronis Backup & Recovery 11.5
Acronis Backup & Recovery 11
Acronis Backup & Recovery 10
Acronis True Image 2014
True Image 2013 by Acronis

This article describes how to resolve and troubleshoot the error "Error creating snapshot" encountered while backing up a physical or virtual machine. Generally following snapshot errors may occur:

Failed to create volume snapshot
Failed to create VSS snapshot
Failed to start creating the volume snapshot
Awaiting task 'CreateSnapshot' has failed. Reason: Response timed out
There Is Not Enough Free Space on the Drive Where the Snapshot Cache File Is Located.
Failed to Set Snapshot Bitmap. Not Locked
Creating a quiesced snapshot failed
Failed to Read the Snapshot

Solution

Follow these steps to troubleshoot snapshot issues:

Get familiar with technology of snapshot creation in the Aboutpart.
Check for known issues in the Known issuespart.
Follow to Troubleshootingpart to troubleshoot and resolve the issue.

Title	Related to
15725: Acronis Backup Software: "Failed to create volume snapshot"	Hardware issues
11124: ABR10: Troubleshooting Acronis virtual appliance issues for ESX	Acronis Agent for ESX/ESXi (Virtual Appliance)
45472: Using DiskShadow to Determine Issues with VSS	VSS service
46155: Acronis Backup & Recovery: Troubleshooting Disk/Partition Backup	disk/partition backup
45632: Acronis Backup & Recovery: Virtual Machine Backup Troubleshooting Guide	VM backup
8032: Acronis Backup & Recovery Creates a Temporary File During Snapshot	SnapAPI
1512: SnapAPI	SnapAPI
1620: Removing Acronis SnapAPI Drivers	SnapAPI
41283: Updating SnapAPI Module in Linux	SnapAPI
36200: Acronis Backup & Recovery: VSS Troubleshooting Guide	VSS

About:

Title	Error Message/Code	Related to
17027: Acronis Backup & Recovery 10: VSS Backup Fails with "Failed to create volume snapshot" on a Machine with Microsoft SQL Server 2000	Event Type: Error Event Source: VSS Event ID: 6004 Time: TIME User: N/A Computer: COMPUTERNAME Description: Sqllib error: Database NAME is not simple.	Microsoft SQL Server 2000
15897: Acronis Backup & Recovery 10 Agent for ESX/ESXi: "Creating a quiesced snapshot failed"	Message: Awaiting task 'CreateSnapshot' has failed. Reason: Cannot create a quiesced snapshot because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine.	Acronis Agent for ESX/ESXi (Virtual Appliance)
8913: Acronis Backup & Recovery 10 Advanced: Backup with VSS Fails with "Failed to read data from sector 2,048" in Windows 7	Failed to read data from sector ‘--‘	Managed Machine Service
37470: Acronis Backup & Recovery: Backup Fails with "Cannot Continue Backup. There Is Not Enough Free Space on the Drive Where the Snapshot Cache File Is Located."	Message: Cannot continue backup. There is not enough free space on the drive where the snapshot cache file is located. 0x00010421	temporary File during Snapshot
41152: Acronis Backup & Recovery 11.5: Backup Fails with "Failed to Read the Snapshot"	Message: The parameter is incorrect 0x0010C45A+0x00000009+0x00000057+0x0000FFF0+0x80070057	drive errors
37472: Acronis Backup & Recovery 11.5: Backup Fails after Upgrade with "Failed to Set the Snapshot Bitmap"	Message: The request is not supported	VSS provider
4559: Acronis Product Fails to Back Up a VMware ESX/ESXi Virtual Machine with "Creating a quiesced snapshot failed" or "An error occurred while quiescing the virtual machine"	Awaiting task has failed (Cannot create a quiesced snapshot because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine) Creating a quiesced snapshot failed Creating a quiesced snapshot failed because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine An error occurred while quiescing the virtual machine. See the virtual machine's event log for details. VMware failed to create a quiesced snapshot of the selected virtual machine. To back up the machine, power off the machine before the process or uninstall the Volume Shadow Copy Services Support feature of VMware Tools from the VM. Awaiting task 'CreateSnapshot' has failed. Reason: Cannot create a quiesced snapshot because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine. Protocol error from VMX	quiesced snapshot
36360: Acronis Backup & Recovery 11.5 for MS SQL: Backing up Machine with MS SQL Server 2005 Fails with “Failed to Create Volume Snapshot”	Failed to create volume snapshot. Failed to set snapshot bitmap. Not locked.	VSS functionality of MS SQL 2005
29014: Acronis Backup & Recovery 11: Backup Fails with "Failed to read the snapshot" and 0x0010C45A+0x0000FFF0	Failed to read the snapshot. The device is not ready. 0x0010C45A+0x0000FFF0	VSS service
40845: Acronis Backup & Recovery 11.5: Backup on Windows XP Fails with Error 'Failed to Create Volume Snapshot' If MS SQL Server is Installed	Failed to create volume snapshot	Windows XP MS SQL Server
31418: Acronis Backup & Recovery: Backup Fails with ''Insufficient storage available to create either the shadow copy storage file or other shadow copy data"	Failed to start creating the volume snapshot Insufficient storage available to create either the shadow copy storage file or other shadow copy data	snapshot storage
31362: Acronis Backup & Recovery and Acronis vmProtect: Virtual machine backup fails with "Awaiting task 'CreateSnapshot' has failed. Reason: File is larger than the maximum size supported by datastore"	Awaiting task 'CreateSnapshot' has failed. Reason: File <unspecified filename> is larger than the maximum size supported by datastore '<unspecified datastore>	VMDK
36273: Acronis Backup & Recovery 11.5 for Microsoft Exchange Server: Database Backup Fails with 'Insufficient storage available to create either the shadow copy storage file or other shadow copy data'	Failed to start creating the volume snapshot. Insufficient storage available to create either the shadow copy storage file or other shadow copy data.	Microsoft Exchange
26550: Acronis Backup & Recovery 11: Backup Displays the "Failed to get VSS metadata for backup" Warning	Failed to get VSS metadata for backup	VSS
40623: True Image 2013 by Acronis: Backup Fails with "Failed to Set Snapshot Bitmap. Not Locked"	Failed to set snapshot bitmap. Not locked	system resources
20350: Acronis Product Errors Out with "Unable to initialize snapshot manager library"	Unable to open (initialize) computer. Unable to initialize snapshot manager library. The system cannot find the file specified.	Low-level Acronis drivers
25370: True Image 2013 by Acronis and Acronis True Image Home 2012: Error “Failed to open (initialize) the computer: Failed to initialize the snapshot manager library.(0x100005)”	Failed to open (initialize) the computer: Failed to initialize the snapshot manager library.	SnapAPI module
38229: True Image 2013 by Acronis: Backup Fails with "Failed to Read the Snapshot Manager Drive"	Failed to read the snapshot manager drive 0x000101FE+0x001000D7+0x00100155	defect sectors
25370: True Image 2013 by Acronis and Acronis True Image Home 2012: Error “Failed to open (initialize) the computer: Failed to initialize the snapshot manager library.(0x100005)”	0x000101F4+0x00100005+0x00000009+0x0000FFF0+0x80070002	SnapAPI

Known Issues

Troubleshooting steps

Follow step-by-step instructions below to troubleshoot the issue. Complete prerequisites step before proceeding to error troubleshooting step.

1. Prerequisites

Complete all steps before proceeding to error troubleshooting step.

1.1 Backup user

1.2 Supported File Systems

1.3 Multi-volume snapshot

1.4 Snapshot options for file-level backup

1.5 Volume Shadow Copy Service (VSS)

These options are effective only for Windows operating systems and Acronis Backup & Recovery products. The option defines whether a Volume Shadow Copy Service (VSS) provider has to notify VSS-aware applications that the backup is about to start. This ensures the consistent state of all data used by the applications; in particular, completion of all database transactions at the moment of taking the data snapshot by Acronis Backup & Recovery 11.5. Data consistency, in turn, ensures that the application will be recovered in the correct state and become operational immediately after recovery.

The preset is: Use Volume Shadow Copy Service

If you select Do not use VSS, the data snapshot will be taken by Acronis Backup & Recovery 11.5.

Choose Do not use VSS if your database is incompatible with VSS. Backup process is fastest, but data consistency of the applications whose transactions are not completed at the time of taking a snapshot cannot be guaranteed. You may use Pre/Post data capture commandsto indicate which commands should be performed before and after taking the snapshot. This ensures that the data is being backed up in a consistent state. For instance, specify pre-data capture commands that will suspend the database and flush all caches to ensure that all transactions are completed; and specify post-data capture commands that will resume the database operations after the snapshot is taken.

Enabling VSS Full backup

The preset is: Disabled.

This option can be useful when you protect Microsoft Exchange Server with a disk-level backup.

If enabled, logs of Microsoft Exchange Server and of other VSS-aware applications (except for Microsoft SQL Server) will be truncated after each successful full, incremental or differential backup.

Leave this option disabled in the following cases:

If you use Acronis Backup & Recovery 11.5 Agent for Microsoft Exchange Server or third-party software for backing up the Exchange Server data. This is because the log truncation will interfere with the consecutive transaction log backups.

If you use third-party software for backing up the SQL Server data. The reason for this is that the third-party software will take the resulting disk-level backup for its "own" full backup. As a result, the next differential backup of the SQL Server data will fail. The backups will continue failing until the third-party software creates the next "own" full backup.

If other VSS-aware applications are running on the machine and you need to keep their logs for any reason.

Enabling this option does not result in the truncation of Microsoft SQL Server logs. To truncate the SQL Server log after a single-pass backup, enable the Log truncation setting in the Single-pass disk and application backup section of the Create backup planor Back up now page.

Enable this option when using VSS on a machine that has Windows XP and runs Microsoft SQL Server. If you leave the option disabled, the backup may fail.

Generally, proceed with VSS troubleshooting if snapshot issue is caused by VSS: 36200: Acronis Backup & Recovery: VSS Troubleshooting Guide

If all steps above have been executed and issue still persists, go to error troubleshooting step.

2. Error troubleshooting

Complete all following steps to localize the issue before proceeding to collect information step.

2.1 Disk Errors:

2.2 VSS Issues

2.3 SnapAPI Update:

2.4 VssRequestor Settings:

If all steps above have been executed and issue still persists, go to error troubleshooting step.

3. Collect information

Collect following information and contact Acronis Customer Central. Note that all logs should be collected on the machine which is performing backup. In case a virtual machine is being backed up over host logs from the host as well as from the guest system should be collected.

3.1 VSS logs:

3.2 SnapAPI Logs:

3.3 VssRequestor Tracing Logs:

3.4 AcronisInfo with Debug Trace:

3.5 Backup settings:

3.6 Dump:

Operating Systems:

Products:

Build:

Segments:

↧

MSI Installation eines Acronis Products schlägt im MSI Log mit SnapVSSProvider Fehler fehl

November 22, 2012, 5:00 am

≫ Next: MSI Installation eines Acronis Products schlägt im MSI Log mit einem VSS Registrierungsfehler fehl

≪ Previous: Acronis Backup Software: Troubleshooting Snapshot Issues

Einleitung

Wenn die Log Datei in den Zeilen vor dem "Rückgabewert 3" den SnapVssProvider aufführt, meint das der Acronis VSS Provider nicht installiert werden konnte.

Lösung

Die Analyse des MSI Logs basiert im Grunde auf den Fehlermeldung(en) der letzten Operation, die in der Log Datei gefunden wurde. Bitte betrachten Sie die beiden Beispiele weiter unten:

SnapVssProvider Beispiel aus MSI log:

MSI Log Ausschnitt

Hier sind die beiden Fehler Codes, die im Log zu finden sind:

0x80110401 - Fehler beim Zugriff auf ein oder mehrere Objekte - die Fehler Information kann mehr Details enthalten.
0x8011041A - Die Komponenten Installation des DllRegisterServer schlägt fehl

Falls das Starten des Volume Shadow Copy Dienstes nicht hilft, fahren Sie bitte wie folgt fort:

Löschen Sie den Acronis VSS Provider aus der Systemsteuerung -> Verwaltung -> Komponentendienste -> Computers -> Mein Computer -> COM+ Anwendungen -> System Anwendungen
Löschen Sie die Datei \Windows\System32\snapapivss.dll, falls es existiert
Finden und löschen Sie alle Registry Schlüssel (Start -> Ausführen-> Regedit -> Enter), welche folgenden GUID's enthalten:
- F5DBCC43-B847-494e-8083-F030501DA611
- 89CDAF20-82B6-42cd-A4B4-573C81999C35
- 5FC845EB-F299-40f0-9725-34045F7EA8BA
  Es wird Schlüssel geben, die mit SnapVSSProvider beginnen, wenn Sie nach 5FC845EB-F299-40f0-9725-34045F7EA8BA suchen. Diese Schlüssel sollten auch gelöscht werden.
Wiederholen Sie die Installation des Produkts
Starten Sie das System neu

Weitere Information

Siehe Analyse der Installations-Logs von Acronis Produkten basierend auf MSI Technologie

MSI Installation eines Acronis Products schlägt im MSI Log mit einem VSS Registrierungsfehler fehl

November 30, 2012, 7:01 am

≫ Next: MSI Installation von Acronis Backup & Recovery 10 oder Acronis True Image Echo schlägt mit VSS Registrierung im MSI Log fehl

≪ Previous: MSI Installation eines Acronis Products schlägt im MSI Log mit SnapVSSProvider Fehler fehl

Einleitung

Lösung

VSS Registrierungsfehler 1 aus dem MSI Log:

MSI Log Ausschnitt:

Um das Problem zu lösen, installieren Sie den Acronis Agent (Acronis Backup & Recovery 10 Build 11345 oder höher) mit folgendem Befehl, der den Fehler ignoriert:

msiexec.exe /i [PATH]AcronisAgentWindows.msi IGNORE_VSS_REGISTRATION_ERRORS=1

Wo [PATH] der Pfad zur AcronisAgentWindows.msi Datei ist.

Zum Beispiel:

msiexec.exe /i C:\AcronisAgentWindows.msi IGNORE_VSS_REGISTRATION_ERRORS=1

(!) Acronis Backup & Recovery 11 und höher ignorieren diesen Fehler automatisch.

VSS Registrierungsfehler 2 aus dem MSI Log:

MSI Log Ausschnitt:

Die Installation schlägt fehl durch Reste der vorherigen Installationsversuche. Entfernen Sie diese Spuren, indem Sie die folgenden Registry Schlüssel löschen und die Installation erneut starten:

HKEY_LOCAL_MACHINE\SOFTWARE\Acronis
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3\SelfReg\CLSID\{79079D5C-EF20-4952-B9FC-CFD443B38641}
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3\SelfReg\SnapVssProvider.SnapVssProvider
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3\SelfReg\SnapVssProvider.SnapVssProvider.1
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{f782463b-33bb-4043-ad8d-60b728d26a6c}

Weitere Information

Siehe Analyse der Installations-Logs von Acronis Produkten basierend auf MSI Technologie

MSI Installation von Acronis Backup & Recovery 10 oder Acronis True Image Echo schlägt mit VSS Registrierung im MSI Log fehl

December 4, 2012, 6:06 am

≫ Next: Acronis Backup & Recovery 11.5: Backup on Windows XP Fails with Error 'Failed to Create Volume Snapshot' If MS SQL Server is Installed

≪ Previous: MSI Installation eines Acronis Products schlägt im MSI Log mit einem VSS Registrierungsfehler fehl

Installation von Acronis Backup & Recovery 10 oder Acronis True Image Echo schlägt mit VSS Registrierung im MSI Log fehl. Das Problem liegt im COM+ Subsystem.

Einführung

Lösung

Die Analyse des MSI Logs basiert auf den Fehlermeldung(en) der letzten Operation, die in der Log Datei gefunden wurde:

MSI Log Ausschnitt:

Ursache: ERROR CODE = 0x80110801 Setup konnte den COM+ Katalog nicht initialisieren. COM+ wird ohne Katalog nicht korrekt arbeiten.

Das ist ein Problem mit dem COM+ Subsystem.

Um das Problem zu lösen, müssen Sie den COM+ reparieren oder erneut installieren, wie im Microsoft Knowledge Base Article 318731 beschrieben.

Weitere Information

Siehe Analyse der Installations-Logs von Acronis Produkten basierend auf MSI Technologie

Products:

English

↧

Acronis Backup & Recovery 11.5: Backup on Windows XP Fails with Error 'Failed to Create Volume Snapshot' If MS SQL Server is Installed

March 21, 2013, 3:26 am

≫ Next: Acronis Backup & Recovery 11.5: Recovery of MS Exchange Database/Storage Group Fails If Committed Transaction Log Is Missing in the Backup

≪ Previous: MSI Installation von Acronis Backup & Recovery 10 oder Acronis True Image Echo schlägt mit VSS Registrierung im MSI Log fehl

Backup on Windows XP fails with error "Failed to create volume snapshot" if MS SQL Server is installed.

This article applies to:

Acronis Backup & Recovery 11.5 (Build 11.5.37588 or higher)

Symptoms

You have installed Acronis Backup & Recovery 11.5 on a Windows XP System;
On this system MS SQL Server is installed and running;
(!) MS SQL Express 2008 is automatically installed along the installation of Acronis Management Server component.
You run a disk or volume backup with the default settings:
1. Use VSS option = enabled (default backup option value);
2. Software-System provider or Software-Select automatically selected (default backup option value);
3. Enable VSS Full Backup is disabled (default backup option value);
This backup fails with:
Failed to create volume snapshot.
See a complete sample error message:
Command 'Running backup plan 'Backup 3/1/2013 8:24:23 PM'' has failed.
Additional info:
--------------------
Error code: 61
Module: 309
LineInfo: 4a8728dc8a1c950f
Fields: $module: mms_vs_37588
Message: Command 'Running backup plan 'Backup 3/1/2013 8:24:23 PM'' has failed.
--------------------
Error code: 41
Module: 307
LineInfo: e6792a5ee190dda7
Fields: $module: agent_protection_addon_vs_37588
Message: ProtectCommand: Failed to execute the command.
--------------------
Error code: 3
Module: 329
LineInfo: 1cd98aae889424f9
Fields: $module: disk_bundle_vs_37588
Message: Backup has failed.
--------------------
Error code: 1060
Module: 1
LineInfo: b43e776571144dec
Fields: $module: disk_bundle_vs_37588
Message: Failed to commit operations.
--------------------
Error code: 33
Module: 7
LineInfo: a5695862aaf8e69b
Fields: $module: disk_bundle_vs_37588
Message: Failed to create volume snapshot.
--------------------
Error code: 50242
Module: 16
LineInfo: 14181c22ef45b0f6
Fields: $module : disk_bundle_vs_37588
Message: Failed to start creating the volume snapshot.
--------------------
Error code: 50281
Module: 16
LineInfo: 14181c22ef45a9e9
Fields: $module : disk_bundle_vs_37588
Message: VSS writer 'SqlServerWriter' with class ID 'A65FAA63-5EA8-4EBC-9DBD-A0C4DB26912A' has failed to process the snapshot.
--------------------
Error code: 65520
Module: 0
LineInfo: bd28fdbd64edb8ea
Fields: code: 2147754996, $module : disk_bundle_vs_37588
Message: Unknown Win32 error
--------------------

ProtectCommand : Échec de l'exécution de la commande.
Informations additionnelles :
--------------------
Code d'erreurs : 41
Module : 307
LineInfo : e6792a5ee190dda7
Champs : $module : agent_protection_addon_vs_37613
Message : ProtectCommand : Échec de l'exécution de la commande.
--------------------
Code d'erreurs : 3
Module : 329
LineInfo : 1cd98aae889424f9
Champs : $module : disk_bundle_vs_37613
Message : La sauvegarde a échoué.
--------------------
Code d'erreurs : 1060
Module : 1
LineInfo : b43e776571144dec
Champs : $module : disk_bundle_vs_37613
Message : Échec de la validation des opérations.
--------------------
Code d'erreurs : 33
Module : 7
LineInfo : a5695862aaf8e69b
Champs : $module : disk_bundle_vs_37613
Message : Impossible de créer une image statique du volume.
--------------------
Code d'erreurs : 50242
Module : 16
LineInfo : 14181c22ef45b0f6
Champs : $module : disk_bundle_vs_37613
Message : Échec du démarrage de la création de l'instané du volume.
--------------------
Code d'erreurs : 50281
Module : 16
LineInfo : 14181c22ef45a9e9
Champs : $module : disk_bundle_vs_37613
Message : L'enregistreur VSS « SqlServerWriter » avec l'ID de classe « A65FAA63-5EA8-4EBC-9DBD-A0C4DB26912A » a échoué le traitement de l'instantané.
--------------------
Code d'erreurs : 65520
Module : 0
LineInfo : bd28fdbd64edb8ea
Champs : code : 2147754996, $module : disk_bundle_vs_37613
Message : Unknown Win32 error

Cause

By default the product uses COPY method of VSS snapshotting. However, Microsoft 'SqlServerWriter' VSS Writer doesn't support VSS COPY method on Windows XP - and thus VSS snapshot can't be created successfully in this OS. The workaround is to switch to VSS Full backup option (see below) which will switch the VSS snapshot method to FULL - and it is supported properly by SqlServerWriter in Windows XP.

Solution

To work around this issue, please enable the VSS Full backup option.

Navigate to the backup plan options or to the default backup options -> Volume Shadow Copy Service and enable the VSS Full backup option. See Enabling VSS Full backup in user guide.

More information

(!) Ifthe issue happens NOT on Windows XP, or the above workaround implemented on Windows XP machine doesn't help - then there must be some other Microsoft VSS corruption (e.g. another component of Microsoft VSS subsystem malfunctions). You'll need to investigate this VSS issue separately, e.g. as described in Acronis Backup & Recovery: VSS Troubleshooting Guide

See also:

Acronis Backup & Recovery 11.5
User guide: Enabling VSS Full backup

Operating Systems:

Components:

Products:

Segments:

↧

Acronis Backup & Recovery 11.5: Recovery of MS Exchange Database/Storage Group Fails If Committed Transaction Log Is Missing in the Backup

March 21, 2013, 5:56 am

≫ Next: Acronis Backup & Recovery 11.5: Backup schlägt fehl mit 'Der Shadow Copy Provider hat einen unerwarteten Fehler beim Versuch, die spezifizierte Aktion durchzuführen'

≪ Previous: Acronis Backup & Recovery 11.5: Backup on Windows XP Fails with Error 'Failed to Create Volume Snapshot' If MS SQL Server is Installed

Recovery of MS Exchange database/storage group fails if committed transaction log is missing in the backup

This article applies to:

Acronis Backup & Recovery 11.5 Agent for Exchange

Symptoms

You have installed Acronis Backup & Recovery 11.5 with Agent for Exchange;
A recovery operation of a database or storage group fails for one of these three symptoms:

Case 1: Database or storage group recovery to MS Exchange fails in the end of operation:

You run database-level recovery task and it fails at the end of the task with VSS error similar to the following:

Message: A Volume Shadow Copy Service (VSS) API error has occurred. Failed to notify Microsoft Exchange Server VSS Writer that the current recovery has completed.

See a complete sample error message:

Also the following error may be shown in the Event Viewer:

Case 2: Database or storage group recovery to MS Exchange fails at the beginning of operation.

You run database-level recovery task and it fails at the end of the task with VSS error similar to the following:

Message: A Volume Shadow Copy Service (VSS) API error has occurred. Failed to notify Microsoft Exchange Server VSS Writer to prepare for recovery.

See a complete sample error message:

Case 3: Recovered MS Exchange database or storage group cannot be mounted

You have recovered database or storage group to a separate folder and try to mount it - operation fails because of database dirty shutdown state.

After that you launch "eseutil /r <Enn>" to bring the database to Clean Shutdown state, but it fails with the error message:

Cause

Some transaction logs are missing (or corrupted) in the backup.

It is possible to recover such database with some additional steps, but data committed from missing transaction log will be lost.

Solution

Database in the target location may be in inconsistent state after failed recovery with VSS error.

In order to recover database from the backup to the target location successfully, it is necessary restore database files to temporary location and repair the database manually.

After that you can move extracted database files to the target location.

Please follow the steps below:

Recover database or storage group to some temporary folder;
Open a command line; Go to Start -> run -> cmd (when UAC activated, right click and start as administrator);
Navigate to temporary folder where database or storage group was extracted (using CD command), for example:

CD c:\<PATH_TO_FOLDER>\
Repair extracted database using command:

eseutil /r Enn /a /i /D <DB Catalog>
(!) Enn is transaction log files prefix - for example, E00.
(!)<DB Catalog> - folder with extracted .edb file
Make sure that database is healthy (for healthy database "State" field value is "Clean Shutdown"):

eseutil /m <EDB-file>
(!) .EDB file name in the target folder where target database\storage group (which should be restored with data from the backup) is located.
Delete contents of target folder (after failed recovery database may be inconsistent);
Move contents of the temporary folder to target folder location;
Make sure that .EDB file name is the same as you noted on step 5. Rename it if necessary;
Mount Exchange database in target location folder.

More information

See Acronis Backup & Recovery 11.5.

Components:

Products:

Segments:

↧

Acronis Backup & Recovery 11.5: Backup schlägt fehl mit 'Der Shadow Copy Provider hat einen unerwarteten Fehler beim Versuch, die spezifizierte Aktion durchzuführen'

March 27, 2013, 3:28 am

≫ Next: Acronis Backup & Recovery: Disk Backup mit Acronis VSS Provider schlägt auf Windows SBS und Domain Controller fehl

≪ Previous: Acronis Backup & Recovery 11.5: Recovery of MS Exchange Database/Storage Group Fails If Committed Transaction Log Is Missing in the Backup

VSS-Backup schlägt mit 'Der Shadow Copy Provider hat einen unerwarteten Fehler beim Versuch, die spezifizierte Aktion durchzuführen' fehl. Um dieses Problem zu lösen, beheben Sie den entsprechenden VSS Provider Fehler.

Dieser Artikel betrifft:

Acronis Backup & Recovery 11.5

Symptome

Sie aktivieren VSS-Snapshot für Backup und starten ein Partitions- oder Diskbackup;
Backup schlägt mit einer solchen Meldung fehl:

Der Shadow Copy Provider hat einen unerwarteten Fehler beim Versuch, die spezifizierte Aktion durchzuführen.

Volle Fehlermeldung

Die Anforderung wird nicht unterstützt

Volle Fehlermeldung

Lösung

Prüfen Sie Windows Applikation-Ereignisanzeige.

In der Windows Applikation-Ereignisanzeige sind Ereignisse ID 12292 und ID 22 aufgelistet

In der Windows Applikation-Ereignisanzeige sind Ereignisse ID 12292 und ID 22 aufgelistet.

Volle Fehlermeldung

In der Applikation-Ereignisanzeige auf einem Hyper-V Server sind Ereignisse ID 12292 und ID 13 aufgelistet.

Volle Fehlermeldung

Ursache

VSS Provider mit CLSID angegeben in der Ereignisanzeige-Fehlermeldung schlägt bei der Initializierung des Snapshots fehl und verursacht Fehlschlagen von Snapshot.

Lösung

Um das Problem zu lösen, reparieren Sie den fehlerhaften VSS-Provider:

Prüfen Sie, ob der fehlerhafte Provider registriert ist:
vssadmin list providers
Prüfen Sie, ob der entsprechende Dienst existiert und aktiviert ist:

Finden Sie den entsprechenden Dienst unter den Diensten. Stellen Sie den Starttyp auf manuell.
Navigieren Sie zu der Registry und finden Sie den Dienst. Stellen Sie sicher, der Schlüssel ist nicht leer:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services[VSS Provider Name]

Wenn eine der Voraussetzungen nicht getroffen ist, führen Sie die Reparaturinstallation von der Provider durch. Starten Sie die Installationdatei von der entsprechenden Software und führen Sie die Reparaturinstallation durch. Für Acronis VSS Provider starten Sie die Installationsdatei von Acronis Backup & Recovery, wählen Sie "Acronis Backup & Recovery installieren", weiter wählen Sie "Reparieren". Kontaktieren Sie den Softwarehersteller von einer Drittparteisoftware.

Soll die Reparaturinstallation das Problem nicht beheben bzw. nicht möglich sein, entfernen Sie den fehlerhaften VSS Provider:

Öffnen Sie die Registry Start -> Ausführen -> regedit.exe -> Enter;
Navigieren Sie zu diesem Schlüssel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VSS\Providers\
Clicken Sie auf Providers und löschen Sie den Unterschlüssel mit CLSID angegeben in der Fehlermeldung (zur Sicherheit den Unterschlüssel vorher exportieren)
(!)Behalten Sie den grün markierten Eintrag! Anderenfalls wird der Windows VSS Provider nicht mehr funktionieren.

In der Windows Applikation-Ereignisanzeige sind Ereignisse ID 8193 und ID 12293 aufgelistet

In der Windows Applikation-Ereignisanzeige sind Ereignisse ID 8193 und ID 12293 aufgelistet.

Siehe volle Fehlermeldung

Ursache

Nicht genügend Speicher, um Volumenschattenkopie zu erstellen oder Schattenkopie ist für die Volume nicht aktiviert.

Lösung

Um prüfen zu können, ob die Volume genügend Speicher für eine Schattenkopie hat, erstellen Sie eine Schattenkopie mit Windows nativen Mitteln und stellen Sie sicher, dass die Schattenkopie erfolgreich erstellt werden kann. Falls notwendig, verschieben Sie Schattenspeicher zu einer anderen Volume oder machen Sie Platz frei.

Wählen Sie, auf welchem Betriebssystem das Backup ausgeführt wird:: Server OS or Workstation OS.

Server OS:

Workstation OS:

Weitere Information

Siehe auch Microsoft: Creating protection for Hyper-V VMs on Windows Server 2012 fails with Internal error code 0x809909E2
Microsoft: Error events are generated when you try to perform a system state backup on a Windows Server 2003-based computer

Products:

Acronis Backup & Recovery 11.5

Segments:

English

↧

Acronis Backup & Recovery: Disk Backup mit Acronis VSS Provider schlägt auf Windows SBS und Domain Controller fehl

March 28, 2013, 6:18 am

≫ Next: Acronis Backup & Recovery 11.5: Backup of Windows Small Business Server 2011 Fails with "Unknown Win32 Error"

≪ Previous: Acronis Backup & Recovery 11.5: Backup schlägt fehl mit 'Der Shadow Copy Provider hat einen unerwarteten Fehler beim Versuch, die spezifizierte Aktion durchzuführen'

Event Codes:

0x000101F6+0x00070021+0x0010C442+0x0010C469+0x0000FFF0+0x800423F0

0x0135003D+0x01490003+0x00010424+0x00070021+0x0010C442+0x0010C469+0x0000FFF0+0x800423F0

Als Workaround verwenden Sie den Microsoft VSS statt den Acronis VSS Provider

Dieser Artikel betrifft:

Acronis Backup & Recovery 10
Acronis Backup & Recovery 11
Acronis Backup & Recovery 11.5