none
Backup of MSSQL 2008 with DPM 2012 fails.

    Frage

  • I was able to backup W2008 Servers without any problems.

    Now I try to backup with DPM 2012 a MSSQL 2008 Database Enterprise Edition 10.04.4000 on a W2008 Host.

    A. Backup of the SQL Server stops with error.
    B. When I try to backup the Databasefiles under the Volume C:, the database files are not visible.

    Andreas

    Dienstag, 12. Juni 2012 04:35

Alle Antworten

  • what is the error that you are recieving?

    ITLAAL

    Dienstag, 12. Juni 2012 05:37
  • The Database has about 200 GB size. After Creating a Group for backup SQL Data has Protection Status OK after one Minute.

    Disk allocation: Replica volume (co-located): 241,49 GB allocated, 97,27 MB used
    Recovery point volume (co-located): 74,18 GB allocated, 92,05 MB used

    Total Recorvery Points: 0

    After waiting for another 5 minutes I get Protection status: Replica is inconsistent.

    Andreas

    Dienstag, 12. Juni 2012 08:16
  • I only see the Directory of the Database files AND the Directories DPM2012 created for Backup.

    I`m not able to select the DATABASE Files and do not SEE (Auto).

    Andreas

    Dienstag, 12. Juni 2012 08:39
  • Hi,

    On your SQL server, could you verify that VSS SQLServer writers is in "stable" state ?

    Open command prompt and type :

    VSSADMIN LIST WRITERS

    Stephane.

    Dienstag, 12. Juni 2012 09:28
  • Microsoft Windows [Version 6.0.6002]
    Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

    C:\Users\administrator.000>VSSADMIN LIST WRITERS
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-li
    (C) Copyright 2001-2005 Microsoft Corp.

    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {db9c3db9-f084-4f1b-84d7-6619874bc4af}
       State: [1] Stable
       Last error: No error

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {92189663-dd87-48e1-b62a-af6d7270665e}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {3d00fd6f-71ae-4c68-bdeb-76614f5c45e2}
       State: [1] Stable
       Last error: No error

    Writer name: 'Microsoft Hyper-V VSS Writer'
       Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
       Writer Instance Id: {9ed794d8-bb72-4284-aaea-8f02c565f470}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {1910ed48-c951-4e74-bdd1-f34098534898}
       State: [1] Stable
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {1496255f-1c09-4c94-a094-13da39b5eb71}
       State: [1] Stable
       Last error: No error

    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {f9c0f8b0-0706-4c8a-914a-fccbdcb32cc0}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {31457f2b-8dc2-439c-8ee5-c400a1776d28}
       State: [1] Stable
       Last error: No error

    C:\Users\administrator.000>

    Andreas

    Dienstag, 12. Juni 2012 10:57
  • Ok VSS writers seems to be fine.

    As said by Laith_it, Could you give us your error message ?

    Could you verify that you have allocated enought space for that PG.

    Stephane

    Dienstag, 12. Juni 2012 11:30
  • Where can I find the error Message?

    What is PG?

    Andreas

    Dienstag, 12. Juni 2012 11:52
  • Hi

    Errors message are found on DPM monitoring tab.

    PG = Protection Group

    Stephane

    Dienstag, 12. Juni 2012 12:30
  • The replica of SQL Server 2008 database LUCAS\H14 on lucas.serviceone.de.local is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent.

    ....

    An unexpected error occurred while the job was running. (ID 104 Details: Unknown error (0x80040e37) (0x80040E37))
    That means: This error can appear if you are trying to protect a SQL Server database that has files on a remote share. This is not supported by DPM.

    A. The files of the SQL Server Database are not shared.
    B. There is enough space in PG: Co-located Protection Data Source 193,65 Replica Volume 300 GB Recovery Point Volume 100 GB
    C. There is enough spce in the file system of the Host with the database

    When creating the PG I´m not able to select the files of the database, no "AUTO".
    Synchronization  with consistency check fails after short time .

    Andreas 

    Dienstag, 12. Juni 2012 12:55
  • Is there a solution to this issue yet as we are experiencing the same problem. Event ID 104 for all SQL databases on this server. How do I check if there are remote shares on the database files as I don't see any? The databases I am trying to protect used to backup just fine with DPM 2010. The only thing that has changed is that this SQL Server was converted from Physical to Virtual and added to the Cluster, but there are 8 more SQL servers that was also converted and added to the Cluster, no issue are expierenced with them doing SQL backups with DPM 2012.

    The databases just shows as inconsistent. It has does not want to create the intial replica creation of the databases.

    Theo

    Mittwoch, 20. Juni 2012 14:39
  • Hi,

    This is a regresssion in DPM 2012 - see this article:

    You receive "Unknown error (0x80040e37)" in System Center Data Protection Manager 2012 when you try to create recovery points for SQL Server or SharePoint databases
    http://support.microsoft.com/kb/2711168

    We have a private fix available until the formal fix is released in July.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Sonntag, 24. Juni 2012 18:39
  • Hi Mike,

    Was this patch released in the newest DMP 2012 Rollup 2 on July 24, 2012.  I installed this rollup and still getting the same message of Replica is inconsistent.  All was working fine in DPM 2010 and after upgrading I started to get this error for two SQL servers. 

    Freitag, 10. August 2012 15:58
  • Hi,

    Yes, the fix for http://support.microsoft.com/kb/2711168 is included in the RU2 rollup http://support.microsoft.com/kb/2706783 as item 1. under DPM fixes.  If you are still receiving the 0x80040e37 error, then it's a different cause.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Freitag, 10. August 2012 21:45