cancel
Showing results for 
Search instead for 
Did you mean: 

Hyper-V Cluster VM Backup FAILED

Spiros_K_
Level 4
Certified

Hallo,

i give you first some System Informations:

- Backup Exec Server:

-- Windows 2008R2

-- Backup Exec 2014

- HyperV01

-- Windows Server 2012R2

- HyperV02

-- Windows Server 2012R2

- Cluster

-- Failover Cluster Manager Windows

-- Cluster Storage - Dell MD3600 SAN

 

We are trying to take a back up from our VM in Cluster to a tape.

The Error is :

Sichern- Cluster01.domain.localV-79-57344-34070 - Snapshot: Initialisierungsfehler auf: "VRTSRV::\\Cluster01.domain.local\Hyper-V?HA?VM\TestClient". Snapshot: Microsoft Volume Shadow Copy Service (VSS).

Scenarios already tried :

1. I create a new VM in Cluster. Backup . OK!

2. I take a backup from a VM that was already in Cluster and was failing before. OK!

3. I move the new created VM to the other Server and rerun the Job with both VM selected. FAIL!

Extra in Eventlogs : The job failed with the following error: The specified for the snapshot database was not saved because the database was not provided.

4. I moved back the newly created VM and rerun the Job. OK!

Error Codes : E0008516 and E0008526

I tried both on Tape and Disk.

Agents are on Hyper-V installiert and updated.

vssadmin list writers are all OK .

 

Verfassername: "Task Scheduler Writer"
   Verfasserkennung: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Verfasserinstanzkennung: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "VSS Metadata Store Writer"
   Verfasserkennung: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Verfasserinstanzkennung: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "Performance Counters Writer"
   Verfasserkennung: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Verfasserinstanzkennung: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "System Writer"
   Verfasserkennung: {e8132975-6f93-4464-a53e-1050253ae220}
   Verfasserinstanzkennung: {de2b49eb-473c-42e6-9736-3ad5c0d2a229}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "Cluster Shared Volume VSS Writer"
   Verfasserkennung: {1072ae1c-e5a7-4ea1-9e4a-6f7964656570}
   Verfasserinstanzkennung: {4415c94e-008b-4ad4-ac28-816169416b2a}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "Microsoft Hyper-V VSS Writer"
   Verfasserkennung: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Verfasserinstanzkennung: {13cb6e9a-b128-40fa-ab13-842878914a89}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "ASR Writer"
   Verfasserkennung: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Verfasserinstanzkennung: {4961618c-4b72-4ade-9321-9d74f69416ea}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "Shadow Copy Optimization Writer"
   Verfasserkennung: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Verfasserinstanzkennung: {69da5ff0-fc3d-41c3-858e-6b1fbbeac6aa}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "Registry Writer"
   Verfasserkennung: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Verfasserinstanzkennung: {48828796-33db-4bef-9d55-aa4f1d4a1024}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "COM+ REGDB Writer"
   Verfasserkennung: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Verfasserinstanzkennung: {b901bb68-9f22-4dc2-a089-3ae6c4cb22a3}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "WMI Writer"
   Verfasserkennung: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Verfasserinstanzkennung: {afc7763a-ae90-478e-b79f-aef965f817f4}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "Cluster Database"
   Verfasserkennung: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
   Verfasserinstanzkennung: {8788c82f-f733-4513-a3c3-8d6254acb71a}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

 

 

 

6 REPLIES 6

Spiros_K_
Level 4
Certified

Forgot to mention :

ADBO - OFF

AOFO - Snapshot-Provider - System Microsoft Software Provider

Process logical Volume - ON

Virtual Computer - Optionen

Backup Method - Full

Offline Computers - Backup

GRT - All Aktiv except SQL-Log backup and GRT for SharePoint

 

Spiros_K_
Level 4
Certified

We have the following Error msgs in Eventlogs on Hyper-V Servers

Error ID : 40962

 

ASR Error: Disk "# 4" could not be excluded. Cause: The disk contains a critical volume.

Error ID : 8193

Volume Shadow Copy Service error: Unexpected error calling routine "IVssAsrWriterBackup :: GetAsrMetadata" An unexpected error has occurred. hr = 0x8007000d, The data is invalid.
,

process:
    PrepareForBackup event

context:
    Execution Context: ASR Writer
    Execution Context: Writer
    Generator Class ID: {be000cbe-11fe-4426-9c58-531aa6355fc4}
    Generator Name: ASR Writer
    Generator Instance ID: {ddb6e4a1-540e-4323-ae5d-dae2fcfe6d36}

Error-specific details:
    ASR Writer: The data is invalid. (0x8007000D)

 

Ben_L_
Level 6
Employee

Can you change the AOFO setting from System to Automatic and see if that makes a difference?

CraigCorefleet
Level 3

Hi Spiros

I am getting the same ASR Writer error with Backup Exec. Had you been able to find a solution ?

 

Thannks Craig

Spiros_K_
Level 4
Certified

Unfortunately, no

 

Either with Ben L. change nothing happend.

 

 

ub40
Level 4
Partner Accredited

Spiro kalimera.

I have a similar problem. In my case backup some virtual machine call VSS errors on Hyper-V host.

I did some experiments and found that backup a one single virtual machine that crashes backup job is work fine. If in the backup job add one more virtual machine, the job is failed with ASR errors.

You can try to create a chained jobs for single virtual machine.

Maybe it will help you.

Regards,

     ub40