none
SQL 2008 R2 Active / Active Cluster Recovery Point Creation Failed

    Question

  • Hello Guys,

    We are running two Node Active / Active SQL Cluster on Win2008r2 SP1 and the SQL version is SQL2008R2.

    We have DPM 2010 which was happy till day before yesterday backing up everything files, dbs, system states & VMs.

    All of a sudden the backups started failing for one of the SQL Instance on the Cluster.

    

    i am getting the above error i even restarted the SQL Node which was running this Instance but still the same.

    Please suggest.


    Maqsood Mohammed Senior Systems Engineer MCITP-Enterprise Admin & ITILv3 Foundation Certified

    Monday, May 07, 2012 1:36 PM

Answers

  • Guys,

    I found that DPM can't even see this SQL Instance in the protection group where the backups are failing.

    Problem: trailing space at the end of database file names.

    Solution: remove the space from the database file names and DPM starts backing up.

    Regards,

    Maqsood


    Maqsood Mohammed Senior Systems Engineer MCITP-Enterprise Admin & ITILv3 Foundation Certified

    Tuesday, May 08, 2012 11:24 AM

All replies

  • I dont find any errors in VSSAdmin list writhers output.

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

    Waiting for responses.
    These may be delayed if a shadow copy is being prepared.

    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: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {bf8efc23-0145-4c69-9115-4c059f7a3668}
       State: [1] Stable
       Last error: No error

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {de3a4a6f-132a-40c4-b168-7ed21ed11e31}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {1625fe2d-2105-4bff-a2de-f9298afdc04e}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {b3482cd0-43dd-42ad-9d1b-91053b8c4140}
       State: [1] Stable
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {4538d9f7-4da3-4b9b-8ef1-3a9e15f1864d}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {df4f8a22-0920-49c9-91ec-073cda23c178}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {928aeceb-b2fd-4e92-89a5-6e8caa02a4a8}
       State: [1] Stable
       Last error: No error

    Writer name: 'Cluster Database'
       Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
       Writer Instance Id: {ab87e7a9-094a-488a-916e-18840935aa41}
       State: [1] Stable
       Last error: No error


    Maqsood Mohammed Senior Systems Engineer MCITP-Enterprise Admin & ITILv3 Foundation Certified

    Tuesday, May 08, 2012 6:45 AM
  • Guys,

    I found that DPM can't even see this SQL Instance in the protection group where the backups are failing.

    Problem: trailing space at the end of database file names.

    Solution: remove the space from the database file names and DPM starts backing up.

    Regards,

    Maqsood


    Maqsood Mohammed Senior Systems Engineer MCITP-Enterprise Admin & ITILv3 Foundation Certified

    Tuesday, May 08, 2012 11:24 AM