none
Windows server backup 2016 - Backup VM RRS feed

  • Domanda

  • Buongiorno,

    ho un host su Hyper-V su Windows 2016 STD con diverse vm con Windows 2016 STD. Di una di queste (tutte di generazione 2), non è possibile nè fare il backup con Windows Server Backup con la macchina accesa nè creare degli snapshot dalla consolle di Hyper-V.

    La macchina virtuale in questione contiene un database SQL che non posso reinstallare in quanto in produzione.
    La macchina virtuale è stata restorata completamente da un backup.

    Ho fatto diverse prove:

    1- backup con WBS da dentro la macchina e funziona

    2- backup dall'host: non funziona solo su quella VM.

    3- snapshot: la percentuale arriva al 9% poi non riesce a proseguire e fa' il merge e ritorma l'errore "An error occured while attempting to checkpoint the selected virtual machine(s). Checkpoint operation failed. 'name-server' could not initiate a checkpoint operation.

    4- i log riportano quanto sotto.

    Grazie per le risposte



    Log Name:      Application
    Source:        SPP
    Date:          11/8/2018 4:10:54 PM
    Event ID:      16387
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      HOST-01
    Description:
    Writer Microsoft Hyper-V VSS Writer experienced some error during snapshot creation.  More info: .
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SPP" />
        <EventID Qualifiers="0">16387</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2018-11-08T15:10:54.244744100Z" />
        <EventRecordID>14044</EventRecordID>
        <Channel>Application</Channel>
        <Computer>HOST-01</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Microsoft Hyper-V VSS Writer</Data>
        <Data>
        </Data>
        <Data>The writer experienced a partial failure. Check the component level error state for more information. (0x80042336)</Data>
        <Data>Unspecified error (0x80004005)</Data>
        <Binary>01000000B8120000991200000000000042BEB7C511CAC619E59C92030000000000000000</Binary>
      </EventData>
    </Event>
    ---------------------------------------------------------------
    Log Name:      Application
    Source:        Microsoft-Windows-CAPI2
    Date:          11/8/2018 4:11:14 PM
    Event ID:      513
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      HOST-01
    Description:
    Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.

    Details:
    AddLegacyDriverFiles: Unable to back up image of binary Microsoft Link-Layer Discovery Protocol.

    System Error:
    Access is denied.
    .
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-CAPI2" Guid="{5bbca4a8-b209-48dc-a8c7-b23d3e5216fb}" EventSourceName="Microsoft-Windows-CAPI2" />
        <EventID Qualifiers="0">513</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2018-11-08T15:11:14.750629800Z" />
        <EventRecordID>14045</EventRecordID>
        <Correlation />
        <Execution ProcessID="196" ThreadID="12328" />
        <Channel>Application</Channel>
        <Computer>HOST-01</Computer>
        <Security />
      </System>
      <EventData>
        <Data>

    Details:
    AddLegacyDriverFiles: Unable to back up image of binary Microsoft Link-Layer Discovery Protocol.

    System Error:
    Access is denied.
    </Data>
      </EventData>
    </Event>

    -----------------------------------------------------------------
    Log Name:      Microsoft-Windows-Hyper-V-Worker-Admin
    Source:        Microsoft-Windows-Hyper-V-Worker
    Date:          11/9/2018 1:39:46 PM
    Event ID:      3280
    Task Category: None
    Level:         Error
    Keywords:      
    User:          NT VIRTUAL MACHINE\7678E467-1F7C-4A09-917B-0185D26A2013
    Computer:      HOST-01
    Description:
    The description for Event ID 3280 from source Microsoft-Windows-Hyper-V-Worker cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    E-SERVER
    7678E467-1F7C-4A09-917B-0185D26A2013
    %%2147754992
    0x800423F0

    The locale specific resource for the desired message is not present

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Hyper-V-Worker" Guid="{51DDFA29-D5C8-4803-BE4B-2ECB715570FE}" />
        <EventID>3280</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2018-11-09T12:39:46.102010600Z" />
        <EventRecordID>53283036</EventRecordID>
        <Correlation />
        <Execution ProcessID="12304" ThreadID="15276" />
        <Channel>Microsoft-Windows-Hyper-V-Worker-Admin</Channel>
        <Computer>Saman-01</Computer>
        <Security UserID="S-1-5-83-1-1987634279-1242111868-2231466897-320891602" />
      </System>
      <UserData>
        <VmlEventLog xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
          <VmName>E-SERVER</VmName>
          <VmId>7678E467-1F7C-4A09-917B-0185D26A2013</VmId>
          <ErrorCode>%%2147754992</ErrorCode>
          <HResult>0x800423F0</HResult>
        </VmlEventLog>
      </UserData>
    </Event>
    -------------------------------------------------------------------------------------------------------------------
    Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
    Source:        Microsoft-Windows-Hyper-V-VMMS
    Date:          11/9/2018 1:39:46 PM
    Event ID:      18012
    Task Category: None
    Level:         Error
    Keywords:      
    User:          SYSTEM
    Computer:      HOST-01
    Description:
    Checkpoint operation for 'E-SERVER' failed. (Virtual machine ID 7678E467-1F7C-4A09-917B-0185D26A2013)
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
        <EventID>18012</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2018-11-09T12:39:46.106329100Z" />
        <EventRecordID>4278</EventRecordID>
        <Correlation />
        <Execution ProcessID="3188" ThreadID="12788" />
        <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
        <Computer>Saman-01</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <UserData>
        <VmlEventLog xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
          <VmName>E-SERVER</VmName>
          <VmId>7678E467-1F7C-4A09-917B-0185D26A2013</VmId>
        </VmlEventLog>
      </UserData>
    </Event>


    • Modificato Enrico Adami venerdì 9 novembre 2018 12:52 titolo
    venerdì 9 novembre 2018 12:51

Tutte le risposte

  • Potresti inserire l'output di questo comando avviato come amministratore?
    vssadmin list writers
    venerdì 9 novembre 2018 15:56
    Moderatore
  • vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2013 Microsoft Corp.

    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error

    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error

    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {e8b43fd7-941f-40bc-ab78-3f237ff3081e}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'Microsoft Hyper-V VSS Writer'
       Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
       Writer Instance Id: {dda07c38-831d-4886-81e8-3e3da569632e}
       State: [5] Waiting for completion
       Last error: Unexpected error

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {41286cc5-5de3-46ce-bd2f-e860bbd6c7fe}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {ad198b8a-0cd1-4deb-9a55-2fb3848a2592}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {c401e588-1024-4533-a3c5-2bb8970efb5b}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {7b94c563-1f06-4959-b178-0aff7b712bc2}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {c3828ed9-4941-4678-a662-c80b14ecbea4}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {15b68016-4368-4687-beaa-22a140a04008}
       State: [5] Waiting for completion
       Last error: No error
    venerdì 9 novembre 2018 16:02
  • lunedì 12 novembre 2018 09:22
    Moderatore
  • Grazie per la risposta. Anche io avevo trovato questo thread ed ho provato ad applicarlo senza fortuna. 

    Il problema permane.

    Non capisco perchè a VM spenta il backup avviene mentre a VM accesa va' in errore.

    Grazie

    Enrico Adami

    lunedì 12 novembre 2018 16:23
  • quando tenti di fare uno snapshot quale errore ti viene restituito o scritto in registro eventi ?

    Edoardo Benussi
    Microsoft MVP - Cloud and Datacenter Management
    e[dot]benussi[at]outlook[dot]it

    martedì 13 novembre 2018 09:43
    Moderatore