none
DPM 2012 R2 protecting a SQL 2008 Cluster/Vss Writer problems on SQL Server RRS feed

  • Question

  • Hola,

    I am running DPM 2012 R2 rollup 4. My Server OS is 2012 Datacenter. I have a SQL 2008 Active/Passive cluster  and MS support has kicked this to the SQL team for review. OK hear we go ..When I run the vssadmin list writer I do see the SQL Writer. Also says no errors. When I run diskshadow /l c:a.txt from an admin command prompt the output does show the SQL Writer information but under that should display all the meta data for each connection to the database so DPM can expand the SQL database to be chosen for protection. I am already confused.

    I am going to include a snippet from the vssadmin and the diskshadow command:

    vssadmin list writers:

    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {8d773b6f-0196-4c34-9943-f258f99c2d9a}
       State: [1] Stable
       Last error: No error

    Diskshadow /l c:a.txt


     * WRITER "SqlServerWriter"
      - Writer ID   = {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
      - Writer instance ID = {8d773b6f-0196-4c34-9943-f258f99c2d9a}
      - Supports restore events = TRUE
      - Writer restore conditions = VSS_WRE_ALWAYS
      - Restore method = VSS_RME_RESTORE_IF_CAN_REPLACE
      - Requires reboot after restore = FALSE
      - Excluded files:

     * WRITER "BITS Writer"
      - Writer ID   = {4969d978-be47-48b0-b100-f328f07ac1e0}
      - Writer instance ID = {5ad5c4f7-5f68-4c1d-a4fc-92d5ef898881}
      - Supports restore events = TRUE
      - Writer restore conditions = VSS_WRE_UNDEFINED
      - Restore method = VSS_RME_UNDEFINED
      - Requires reboot after restore = FALSE
      - Excluded files:
       - Exclude: Path = C:\Windows\System32, Filespec = bits.log
       - Exclude: Path = C:\Windows\System32, Filespec = bits.bak
       - Exclude: Path = C:\ProgramData\Microsoft\Net

    As you can see this did not return the expected results. I should see the meta data for each database. This is why DPM can't list the databases for backup in my 2008 production SQL cluster. Any thoughts? This has not been working for quite sometime. I was hoping the update to rollup 4 would have fixed the problem. I know this is a SQL problem but has anyone had this experience?

    Thanks

    Steve J.

    Sunday, February 1, 2015 3:48 AM