Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 24

Thread: Backup failure - logs emailed

  1. #11
    Join Date
    Sep 2006
    Posts
    72

    Default

    Hi Rob,

    Nice to hear that your backups are running fine.

    I also noticed VSS error event 8193 in the logs we received from you. Also some VSS writers are in inconsistent state ("vssadmin list writers" from command line gives VSS writers status).

    Writer name: 'System Writer'
    Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
    Writer Instance Id: {c71d1e9a-d21c-4e45-8525-99003172d161}
    State: [8] Failed
    Last error: Inconsistent shadow copy

    Pl. reboot your system so that all writers come into a consistent state. Also I guess it will help to get rid of event id 8193.

    About setup-debug_env.bat - it just asks "Windows Error Reporting" to save ZWCService crashdumps in ZCB folders so that "Collect logs" tools can collect it along with all other logs. "Collect logs" tool reset the settings made by setup-debug-env.bat.

    -Harsha

  2. #12

    Default

    Thanks for the replies Harsha.

    I've run it for a few days now, and it has been rebooted three times since. Once to update NIC drivers and twic

    The backups appear to be working, however I'm still seeing the error below in the Windows Event Logs.

    Further down is also the result of the "vssadmin list writers" command. Hopefully it will tell you what is needed.

    Regards,
    Rob


    =====================================
    Volume Shadow Copy Service error: Unexpected error calling routine IVssBackupComponents::SetContextInternal. hr = 0x80042301.
    Operation:
    Add a Volume to a Shadow Copy Set
    Context:
    Execution Context: Requestor
    ====================================

    I typed the command provided into the CMD prompt and it returned the following:

    Microsoft Windows [Version 6.0.6001]
    Copyright (c) 2006 Microsoft Corporation. All rights reserved.

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

    Writer name: 'System Writer'
    Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
    Writer Instance Id: {f38355e8-c33b-42fa-be03-b6605277cb16}
    State: [8] Failed
    Last error: Inconsistent shadow copy

    Writer name: 'SqlServerWriter'
    Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
    Writer Instance Id: {89eaf26e-bd84-4c95-a28e-a8715833918c}
    State: [1] Stable
    Last error: No error

    Writer name: 'IIS Config Writer'
    Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
    Writer Instance Id: {a5985910-b37d-4862-ace6-6d64b9b50aad}
    State: [8] Failed
    Last error: Inconsistent shadow copy

    Writer name: 'ASR Writer'
    Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
    Writer Instance Id: {7199a7a2-e834-4d81-956f-5baaf120efbc}
    State: [1] Stable
    Last error: No error

    Writer name: 'Registry Writer'
    Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
    Writer Instance Id: {8bfc043c-b103-4016-a962-b88ad73fc3b1}
    State: [1] Stable
    Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
    Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
    Writer Instance Id: {4ce52f17-2a3f-423a-b87d-47a9360a4804}
    State: [1] Stable
    Last error: No error

    Writer name: 'COM+ REGDB Writer'
    Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
    Writer Instance Id: {48135cc9-19c8-4843-a6ed-0574a05e137f}
    State: [1] Stable
    Last error: No error

    Writer name: 'IIS Metabase Writer'
    Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
    Writer Instance Id: {12bd4c43-9dbe-4891-841c-2e9834d34153}
    State: [8] Failed
    Last error: Inconsistent shadow copy

    Writer name: 'BITS Writer'
    Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
    Writer Instance Id: {9eefcfec-e64d-425a-8c77-b31eb45b3efd}
    State: [1] Stable
    Last error: No error

    Writer name: 'WMI Writer'
    Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
    Writer Instance Id: {0ad442b6-4246-49ec-976b-61b0d602e2b1}
    State: [8] Failed
    Last error: Inconsistent shadow copy

  3. #13
    Join Date
    Sep 2006
    Posts
    72

    Default

    Hi Rob,

    To nail down the problem. Pl. follow the steps.

    1. Reboot the machine to bring all the writers to a consistent state.
    2. Take a backup of backupsets one by one manually.
    3. After each backup check the writers status (using "vaaadmin list writers") and also check if there is a VSS error in application event log.
    4. If writers went into an inconsistent state or there is a VSS error, collect the logs immediately and send us.

    Actully I want to know exactly which backup set is cauing the problem.

    Also pl. let me know if this machine is on hyper-V.

    -Harsha

  4. #14

    Default

    That's going to be a bit of a job so I'll have to wait until the weekend to do it.

    In the meantime I've disabled all the backups and the ZCB services so that it's not active.

    I did this because the server has another backup system from r1soft

    That system does backups of the entire server for the purposes of a bare-metal restore should the server fail.

    I wanted the ZCB Backups to be an additional and very specific off-site backup of just my web folders plus the related MSSQL and MySQL databases. The features fit the bill perfectly.

    Now I believe that these two systems are conflicting. The other backup reports this in the event log:

    An error occured while executing VSS operation 'm_pVssObject->StartSnapshotSet(&m_latestSnapshotSetID)'. VSS_E_SNAPSHOT_SET_IN_PROGRESS - The creation of a shadow copy is in progress, and only one shadow copy creation operation can be in progress at a time. This can happen if multiple VSS-aware applications are running on the same machine.


    Do you think this is likely to be the source of the problems?
    Regards
    Rob

    p.s. the machine is not on HyperV. It is a standalone server running Server2008 SP1 natively. I had 5 backup sets defined. Three were of files and folders. One was a set of MySQL databases, adn the last one was the MSSQL databases.
    Last edited by zbackup; April 26th, 2010 at 04:33 PM.

  5. #15
    Join Date
    Sep 2006
    Posts
    72

    Default

    Yes Rob,

    Multiple backups (of different vendors or same vendor) should not be scheduled at the same time especially if they are using the VSS based backups. Otherwise conflicts like you mentioned in the earlier message happens.

    -Harsha

  6. #16

    Default

    Hi there,

    I'm afraid this has all turned into too much of a drama for me to deal with. I just can't find the time spare to troubleshoot this application and so I've cancelled the app on amazon and have removed everything from my web server.

    Apart from the problems getting ZCB working satisfactorily, I was also not very happy to discover I had to install JRE on the server. It just wasn't worth the extra footprint and hassle. In any case, it's all gone now and I'm fine with that.

    My next step was to try and get the files deleted from my S3 account. I was aware of the "jets3t' application made available for download and so I've been trying to set that up. I don't run Java on my local machine either, but I went ahead and installed it for this purpose.

    And nwo the problem: When I run the cockpit.bat file from Windows, a dommand window opens and closes immediately. So then I moved the cockpit-bundle file to the root of the C drive, opened a command prompt and ran the bat from there, but it says this:

    C:\cockpit-bundle\bin>cockpit.bat
    '"java"' is not recognized as an internal or external command,
    operable program or batch file.

    So then I went off to Sun to check the Java install and it tells me it is the latest and verifies that it is fine.

    All I want to do is get rid of the files stored on S3 so that I'm not paying for them for the rest of eternity.

    Is there any way I can do that without spending days on it?

    Thanks for any advice on this.
    Rob

    p.s. The ZCB specification is exactly what I wanted, but the entire process really needs to be more bulletproof, and preferably a native app.

  7. #17
    Join Date
    Jan 2010
    Location
    California
    Posts
    49

    Default

    Hi Rob,

    I have opened a support case on your behalf to handle closing your subscription and deleting the files on your S3 account. Could you please log into network.zmanda.com and click on the support link in the bottom right hand corner -> click open cases at the top -> and then select the single open case you have and just verify in there that this is what you want. This step is just to ensure that the real account owner is requesting this.

    Regards,
    Boris

  8. #18

    Default

    Thanks Boris, that's very much appreciated.
    Rob

  9. #19

    Default

    I know the original poster of this topic has given up on this issue, but we face the same root issue.

    ZCB 3.x is installed on a Win 2008 server without Hyper-V. We get the same error regarding remote host closing connection. We get the same error from VSS: "Volume Shadow Copy Service error: Unexpected error calling routine IVssBackupComponents::SetContextInternal. hr = 0x80042301"

    There is no other backup software running on this server.

    Microsoft Windows [Version 6.0.6002] Copyright (c) 2006 Microsoft Corporation. All rights reserved. C:\Users\admin>vssadmin list writers vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2005 Microsoft Corp. Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {64a21691-a215-4cfb-8071-b380713de3a4} State: [1] Stable Last error: No error Writer name: 'ASR Writer' Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4} Writer Instance Id: {8bd003de-de0e-454d-9177-6acce890528f} State: [1] Stable Last error: No error Writer name: 'Shadow Copy Optimization Writer' Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} Writer Instance Id: {e556637a-edff-40d1-951b-b2615b51b8cf} State: [1] Stable Last error: No error Writer name: 'BITS Writer' Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0} Writer Instance Id: {92f4a70c-ebab-4693-8ae7-4215e4380ece} State: [1] Stable Last error: No error Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {0bee9147-d37d-4e32-8766-6b20090e43b1} State: [1] Stable Last error: No error Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {5d3e5c22-a709-4870-8d00-eb20fcfc8f8b} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {575e8ad7-a122-4ee8-94f2-fc54cac662fb} State: [1] Stable Last error: No error

  10. #20
    Join Date
    Oct 2005
    Posts
    1,559

    Default

    Hi Saluki,

    can you open a customer support case at Zmanda Network? We will need logs to look at the problem. To understand this error message we need to see the system and application event information.

    Click on Support tab after logging to Zmanda Network.
    Paddy

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •