none
DPM 2007 Exchange backup error RRS feed

  • Question

  • Hi,

    I have a DPM 2007 server which is protecting Exchange cluster. There are a total of 15 storage groups. Recovery point is getting created for all storage groups except for one (SG07), which says "Can not perform creation of a recovery point because the replica is not idle. (ID : 141) Wait for the ongoing job to complete or cancel the job in the Monitoring task area."

    However when I go to jobs tab, I do not see any ongoing job for that particular data storage group.

    I checked the application logs on Exchange server, there was this VSS error:

    Log Name:      Application
    Source:        VSS
    Date:          6/18/2012 8:32:29 AM
    Event ID:      8193
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      exchange.corporateroot.net
    Description:
    Volume Shadow Copy Service error: Unexpected error calling routine ConvertStringSidToSid.  hr = 0x80070539.

    Operation:
       OnIdentify event
       Gathering Writer Data

    Context:
       Execution Context: Shadow Copy Optimization Writer
       Writer Class Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Name: Shadow Copy Optimization Writer
       Writer Instance ID: {24b48334-ea3f-4d88-af89-711f4ac3f9fa}
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="VSS" />
        <EventID Qualifiers="0">8193</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-06-18T06:32:29.000Z" />
        <EventRecordID>280389158</EventRecordID>
        <Channel>Application</Channel>
        <Computer>exchange.corporateroot.net</Computer>
        <Security />
      </System>
      <EventData>
        <Data>ConvertStringSidToSid</Data>
        <Data>0x80070539</Data>
        <Data>

    Operation:
       OnIdentify event
       Gathering Writer Data

    Context:
       Execution Context: Shadow Copy Optimization Writer
       Writer Class Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Name: Shadow Copy Optimization Writer
       Writer Instance ID: {24b48334-ea3f-4d88-af89-711f4ac3f9fa}</Data>
        <Binary>2D20436F64653A20534543534543524330303030303838322D2043616C6C3A20534543534543524330303030303837352D205049443A202030303031353436382D205449443A202030303031353836302D20434D443A2020433A5C57696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E5420415554484F524954595C53595354454D20202020202D205369643A2020532D312D352D3138</Binary>
      </EventData>
    </Event>

    On the Exchange server, all writers are stable, except this one :

    Writer name: 'Microsoft Exchange Writer'
       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
       Writer Instance Id: {58fb8dc1-5d47-4733-9d04-6aad0d070e67}
       State: [5] Waiting for completion
       Last error: No error

    Are these related by any chance? If yes, why is only SG07 not getting backed up while all other storage groups are? Please help.

    Regards,

    Pavit

    Monday, June 18, 2012 7:21 AM

Answers

All replies

  • Hi Pavit,

    Try re-registering VSS core components it may fix that VSS write state. You can run these commands.
    These can be put in a batch file and then just run the batch file. After you run it reboot your sever.

    cd /d %windir%\system32
    net stop vss
    net stop swprv
    regsvr32 /s ole32.dll
    regsvr32 /s oleaut32.dll
    regsvr32 /s vss_ps.dll
    vssvc /register
    regsvr32 /s /i swprv.dll
    regsvr32 /s /i eventcls.dll
    regsvr32 /s es.dll
    regsvr32 /s stdprov.dll
    regsvr32 /s vssui.dll
    regsvr32 /s msxml.dll
    regsvr32 /s msxml3.dll
    regsvr32 /s msxml4.dll
    vssvc /register
    net start swprv
    net start vss

    Let us know how things go.


    My Blog | www.buchatech.com | www.dpm2010.com

    If you found this post helpful, please give it a "Helpful" vote. If it answered your question, remember to mark it as an "Answer". This posting is provided "AS IS" with no warranties and confers no rights! Always test ANY suggestion in a test environment before implementing!



    Tuesday, June 19, 2012 2:42 PM
    Moderator
  • Pavit,

    There Exchange writer is what is responsible for taking Exchange backups and issues with the writer could cause issues. The failure is stating that there is SID that is invalid. 

    Please check the registry for any .bak entries

    Open regedit and locate 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList'

    Please reveiw the following sources:

    http://social.technet.microsoft.com/Forums/en/winserverfiles/thread/7b52f7c1-a783-409e-9af3-da64567676df

    Path for profile list:  http://blogs.technet.com/b/jonjor/archive/2010/02/18/scvmm-p2v-fails-with-at-40-percent-with-0x809933bb-or-0x80070539.aspx

    Event 8193 - http://technet.microsoft.com/en-us/library/ee264196(v=WS.10).aspx


    Regards, A.Nadar, This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, June 20, 2012 8:58 PM
    Moderator
  • Hi Andy,

    Deleting .bak entries and rebooting the exchange server afterwards solved the problem. Thanks for your help.

    Although I could not run the .bat file as suggested by buchatech.

    Regards,

    Pavit

    Thursday, June 28, 2012 10:40 AM