none
VSS Backup with ASR Writer reference data from unavailable volume RRS feed

  • Question

  • Hi!

    We currently have the issue that we cannot create backups (with our backup software which uses VSS). Each time we create a VSS snapshot we get a eventlog error on EndPrepareSnapshots hr=0x80070015 -> The Device is not ready.

    So I have checked the output of the DISKSHADOW program (list writers detailed) and the output of MOUNTVOL and I found a volume which has no mountpoint but should be backed up with the ASR Writer.

    Diskshadow Output (sorry it is in german):

    + Komponente "ASR Writer:\Volumes\Volume{fca06481-23ff-4a24-b76a-9bf9bd589449}"
    			- Name: Volume{fca06481-23ff-4a24-b76a-9bf9bd589449}
    			- Logischer Pfad: Volumes
    			- Vollst„ndiger Pfad: \Volumes\Volume{fca06481-23ff-4a24-b76a-9bf9bd589449}
    			- Beschriftung: W„hlen Sie dieses Volume (\??\Volume{fca06481-23ff-4a24-b76a-9bf9bd589449}) aus, wenn es sich um ein kritisches Volume handelt.
    Kritische Volumes sind solche, die durch ASR wiederhergestellt werden mssen.
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist ausw„hlbar: FALSE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Komponenten:
    			- Von dieser Komponente betroffene Pfade:
    			- Von dieser Komponente betroffene Volumes:
    			- Komponentenabh„ngigkeiten:

    Mountvol Output:

    \\?\Volume{598275de-7181-4a95-b991-84bceb1a6b73}\
        C:\
    
    \\?\Volume{7cb70391-b8d4-42dc-a8c7-e51a8ce1a7dd}\
        H:\
    
    \\?\Volume{fca06481-23ff-4a24-b76a-9bf9bd589449}\
    *** KANN NICHT BEREITGESTELLT WERDEN BIS EIN VOLUMEBEREITSTELLUNGSPUNKT
                                                         ERSTELLT WURDE ***

    ----

    So now I have the problem that I do not know anything about this volume. I cant find anything about it in the disk management program or through WMI (WMI lists it but without any information). Here we talk about HyperV (Windows Server 2016) Servers so I do not want to delete a Volume when I do not know anything about it (maybe it is relevant for Hyper V but without mountpoint..?).

    So

    • did anyone know a way how I can find out informations about this mysterious volume (or maybe know what it is in a hyper v environment. We have this issue on all our hyper v servers)?
    • if it is not needed (what I need to find out first) is there a way to remove this volume or maybe exclude it from VSS?

    Thursday, March 7, 2019 9:20 AM

All replies

  • Hi,

    Which backup software are you using?

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, March 7, 2019 12:31 PM
  • Hi (and thank you for your response!),

    we use IBM Spectrum Protect (8.1.5).

    I also have found a IBM related topic to this problem (unfortunatly without a real solution...)

    Here is the link: https://www-01.ibm.com/support/docview.wss?uid=swg22014162

    It describes exactly our problem we have the not mounted volume and the ASR writer wants to snapshot it but of course is not able to do it.

    Thursday, March 7, 2019 12:41 PM
  • Thank you for clarifying! As this is a third party backup software (not a Microsoft product), I would advise you to ask in the IBM forums for help, the experts there might be able to help you out more with your issue.

    You can ask in the link below:
    https://developer.ibm.com/answers/index.html


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, March 7, 2019 12:48 PM
  • But this is not an IBM issue this is an VSS issue :)

    If I try to create a VSS snapshot without the IBM Backupsoftware the VSS snapshot cant be created eather.

    So in other words if I do this (without IBM) I have the same error.

    diskshadow
    
    set verbose
    set volatile
    
    add volume c:
    add volume \\?\Volume{fca06481-23ff-4a24-b76a-9bf9bd589449}\
    begin backup
    create
    end backup

    Verbose diskshadow result:

    Fehler beim letzten Vorgang.
            - HRESULT (zurückgegeben): 8004230f
            - Fehlertext: VSS_E_UNEXPECTED_PROVIDER_ERROR

    Eventlog (translated by myself sorry):

    Error while EndPrepareSnapshots() hr=0x80070015, the device is not ready
    
    Event-Id: 12293
    Source:   VSS

    I can try to ask IBM if it is possible to exclude a special volume in a VSS snapshot but this is not the source of the problem just (maybe) a workaround.

    Thursday, March 7, 2019 1:37 PM
  • What is your output of the following two commands?

    vssadmin list writers

    vssadmin list providers


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, March 7, 2019 1:40 PM
  • Hi!

    Output of vssadmin list writers:

    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: {c7c19b9e-7153-4092-aca1-9999b84dec5f}
       Status: [1] Stabil
       Letzter Fehler: Kein Fehler
    
    Verfassername: "Microsoft Hyper-V VSS Writer"
       Verfasserkennung: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
       Verfasserinstanzkennung: {dd8dab6a-5c42-4db1-a31a-f5663246efd8}
       Status: [1] Stabil
       Letzter Fehler: Kein Fehler
    
    Verfassername: "ASR Writer"
       Verfasserkennung: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Verfasserinstanzkennung: {c18331ad-3d3f-4fe0-992d-6e7d037b8b40}
       Status: [1] Stabil
       Letzter Fehler: Kein Fehler
    
    Verfassername: "Registry Writer"
       Verfasserkennung: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Verfasserinstanzkennung: {1d14084f-211d-45d4-89bc-a69f4060ab9e}
       Status: [1] Stabil
       Letzter Fehler: Kein Fehler
    
    Verfassername: "Shadow Copy Optimization Writer"
       Verfasserkennung: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Verfasserinstanzkennung: {21a2f6bc-07d0-41ed-a06e-e7e37809e9a1}
       Status: [1] Stabil
       Letzter Fehler: Kein Fehler
    
    Verfassername: "COM+ REGDB Writer"
       Verfasserkennung: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Verfasserinstanzkennung: {9cb2cb57-19d3-419a-8a06-d9b95190e520}
       Status: [1] Stabil
       Letzter Fehler: Kein Fehler
    
    Verfassername: "WMI Writer"
       Verfasserkennung: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Verfasserinstanzkennung: {459b2a18-525d-4463-a094-ec11bc9639c3}
       Status: [1] Stabil
       Letzter Fehler: Kein Fehler

    and output of vssadmin list providers:

    Anbietername: "Microsoft File Share Shadow Copy provider"
       Anbietertyp: Dateifreigabe
       Anbieterkennung: {89300202-3cec-4981-9171-19f59559e0f2}
       Version: 1.0.0.1
    
    Anbietername: "Microsoft Software Shadow Copy provider 1.0"
       Anbietertyp: System
       Anbieterkennung: {b5946137-7b9f-4925-af80-51abd60b20d5}
       Version: 1.0.0.7

    Sorry it is german but I think the relevant parts are english anyway.

    Thank you again for your help!





    Thursday, March 7, 2019 2:19 PM
  • Everything looks OK to me, did you check the Windows event logs for any clues?

    Blog: https://thesystemcenterblog.com LinkedIn:

    Friday, March 8, 2019 12:12 AM
  • Yes for me to, except the fact it want to create a snapshot from a device which is not ready. :)

    ---

    Everytime when I want to create a VSS snapshot this event occurs

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="VSS" /> 
      <EventID Qualifiers="0">12293</EventID> 
      <Level>2</Level> 
      <Task>0</Task> 
      <Keywords>0x80000000000000</Keywords> 
      <TimeCreated SystemTime="2019-03-07T13:16:26.092243300Z" /> 
      <EventRecordID>30457</EventRecordID> 
      <Channel>Application</Channel> 
      <Computer>xxx</Computer> 
      <Security /> 
      </System>
    - <EventData>
      <Data>{b5946137-7b9f-4925-af80-51abd60b20d5}</Data> 
      <Data>EndPrepareSnapshots({241b5b02-e393-470c-95b4-de01eaf6067e})</Data> 
      <Data>0x80070015, Das Gerät ist nicht bereit.</Data> 
      <Data>Vorgang: Asynchroner Vorgang wird ausgeführt Kontext: Aktueller Status: DoSnapshotSet</Data> 
      <Binary>2D20436F64653A20434F52534E50534330303030313736322D2043616C6C3A20434F52534E50534330303030313734332D205049443A202030303031303536302D205449443A202030303031313734342D20434D443A2020433A5C57696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E616D653A204E542D4155544F524954C4545C53595354454D2C205349443A532D312D352D313820</Binary> 
      </EventData>
      </Event>

    I havent mentiond yet that there is a second event (see it now)

    - <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="2019-03-07T13:16:17.373359000Z" /> 
      <EventRecordID>30455</EventRecordID> 
      <Correlation /> 
      <Execution ProcessID="2812" ThreadID="9276" /> 
      <Channel>Application</Channel> 
      <Computer>xxx</Computer> 
      <Security /> 
      </System>
    - <EventData>
      <Data>Details: AddLegacyDriverFiles: Unable to back up image of binary Microsoft-Verbindungsschichterkennungsprotokoll. System Error: Zugriff verweigert</Data> 
      </EventData>
      </Event>
    For the second one we already have tried to restart the Cryptographieservice.
    Friday, March 8, 2019 8:21 AM