Forum Discussion

Anandha_Kannan_'s avatar
Anandha_Kannan_
Level 4
12 years ago

Exchange Server 2007 Passive node backup failed

Hi All,

Exchange server backup for the active node is running fine but am aware it is not a best practice to run on that. But while running backup in passive node the backup is getting failed. I raised case with symantec and they suggest that Microsoft Exchange Replica should be available in the passive when view by using the CMD VSS list writers.

Can anyone tell who to enable the MS Exchange replica service.

Note: we could see MS Exchange replication services is in running state.(services.msc)

7.5
Backing Up
Backup and Recovery
Best Practice
NetBackup
Windows Server (2003-2008)
  • V4's avatar
    V4
    12 years ago

    if i'm not mistaken, there are no replica writers as such seen in your output (neither active or passive)

    i do see there is retryable error on Passive note exchange writers.. Did you checked if subsequent reboot brought VSS writers back to normal state., if post reboot also they are not stable , then time to sync with MS support for VSS fixes if any available. (There are VSS fixes , you can surf through Technet for that)

    What error does it logs in event viewer during backup failure. Check it should also report on exchange writers which should give you hint on cause and suspects

     

10 Replies

Sort By
  • RamNagalla's avatar
    RamNagalla
    Moderator
    12 years ago

    looks like, its time to go for exchange admin....

    please check with your exchage admins and understand how your enviornment did setup.. and the possiblities...

  • Anandha_Kannan_'s avatar
    Anandha_Kannan_
    Level 4
    12 years ago

    Hi All,

    ERROR CODE is 1542.

    My Active note vssadmin list writers output

     

    C:\Documents and Settings\sifybackup>vssadmin list writers
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line t
    (C) Copyright 2001 Microsoft Corp.
     
    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {fcbdf39a-351d-4313-9595-428e4be570b6}
       State: [1] Stable
       Last error: No error
     
    Writer name: 'MSDEWriter'
       Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
       Writer Instance Id: {a849f4d7-4a6f-4f34-8c88-2116043e5a00}
       State: [1] Stable
       Last error: No error
     
    Writer name: 'Event Log Writer'
       Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
       Writer Instance Id: {ea611de3-aafd-4c01-b185-9030eaa23b48}
       State: [1] Stable
       Last error: No error
     
    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {cff0dc8f-281e-4d21-a483-df2abd2f85ce}
       State: [1] Stable
       Last error: No error
     
    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {3e9208b8-a976-4712-8ee7-a46425ed3783}
       State: [1] Stable
       Last error: No error
     
    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {6230a62b-06f7-400e-9410-c228c6272055}
       State: [1] Stable
       Last error: No error
     
    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {5b59fc62-85d5-4b3e-b6da-a5bc00da1202}
       State: [1] Stable
       Last error: No error
     
    Writer name: 'Microsoft Exchange Writer'
       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
       Writer Instance Id: {d0883929-892c-46e4-942f-cbf1e8784c8f}
       State: [1] Stable
       Last error: No error
     
    Writer name: 'Cluster Service Writer'
       Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
       Writer Instance Id: {0c59e162-c1e4-480b-983d-4c81ffe82d60}
       State: [1] Stable
       Last error: No error
     
    My Passive note vssadmin list writers output
     
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001 Microsoft Corp.
     
    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {ec8b0f97-5b35-43bd-8917-3774b89a40ee}
       State: [1] Stable
       Last error: No error
     
    Writer name: 'Microsoft Exchange Writer'
       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
       Writer Instance Id: {9240721f-78ee-408d-9947-aa76500e7e9f}
       State: [7] Failed
       Last error: Retryable error
     
    Writer name: 'MSDEWriter'
       Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
       Writer Instance Id: {c71847d7-33f4-49ba-bcba-cfb7cbf61de5}
       State: [1] Stable
       Last error: No error
     
    Writer name: 'Cluster Service Writer'
       Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
       Writer Instance Id: {cd56293c-589e-4560-bb70-6884f72d8e09}
       State: [1] Stable
       Last error: No error
     
    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {0028dead-c191-4ecf-8b9f-f69051840d35}
       State: [1] Stable
       Last error: No error
     
    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {81cceb3b-e7bb-4165-b2c7-589463e067ed}
       State: [1] Stable
       Last error: No error
     
    Writer name: 'Event Log Writer'
       Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
       Writer Instance Id: {38c8c9fc-0106-4d0c-a07e-d1601e4f4752}
       State: [1] Stable
       Last error: No error
     
    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {be45ff2b-c4cc-4e61-81c4-49cc095632f6}
       State: [1] Stable
       Last error: No error
     
    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {335599cf-bcc2-4860-8b5e-ae4e901df879}
       State: [1] Stable
       Last error: No error
     
    =================================================================
     
    In passive vssadmin cmd output i could see the replica writer... so i think that is creating the problem.. please provide me ur solutions.
     
     
     
     
  • V4's avatar
    V4
    Level 6
    12 years ago

    if i'm not mistaken, there are no replica writers as such seen in your output (neither active or passive)

    i do see there is retryable error on Passive note exchange writers.. Did you checked if subsequent reboot brought VSS writers back to normal state., if post reboot also they are not stable , then time to sync with MS support for VSS fixes if any available. (There are VSS fixes , you can surf through Technet for that)

    What error does it logs in event viewer during backup failure. Check it should also report on exchange writers which should give you hint on cause and suspects

     

  • Ankit_Maheshwar's avatar
    Ankit_Maheshwar
    Level 5
    12 years ago

     

    Writer name: 'Microsoft Exchange Writer'
       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
       Writer Instance Id: {9240721f-78ee-408d-9947-aa76500e7e9f}
       State: [7] Failed
       Last error: Retryable error
     
     
    so this is the problem...
    Kindly check with MS vendor they will fix this.. numerous of time i have this reboot is only solution to resolve this..
    Also check buffer size where the data reside.
     
     
     
     
    Ankit Maheshwari

     

  • RLeon's avatar
    RLeon
    Level 6
    12 years ago

    Someone might have set the following registry key to 0 in the past; Windows Server Backup needs it to be set to 0, so this could be the reason.

    HKEY_LOCAL_MACHINE\Software\Microsoft\ExchangeServer\v14\Replay\Parameters
    DWORD value : EnableVSSWriter

     

    For NetBackup, you should set it to 1, and have the Microsoft Exchange Replication Service restarted.
    After that, you should be able to see the writer again when you list writers.

     

    Symantec reference (applies to Exchange 2007 too):
    http://www.symantec.com/business/support/index?page=content&id=TECH171234

    MS TechNet reference (confirms that this registry key also applies to Exchange 2007):
    http://blogs.technet.com/b/dhardin/archive/2009/10/21/vss-backup-using-windows-server-backup-on-exchange-server-2007-sp2-fails-when-lcr-or-scr-is-enabled.aspx

     

  • Anandha_Kannan_'s avatar
    Anandha_Kannan_
    Level 4
    12 years ago

    Hi RLeon,

    I done the changes in registery but still am getting the  backup failure with same error code 1542. And also after the changes in registery i viewed the Output of cmd VSS writers in passive node  but replica writers is missing still.

     

    Any other solutions??