Jump to content

radamo

Members
  • Content count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About radamo

  • Rank
    Newbie
  1. Restoring to recovery storage groups in Retrospect 7.6.123 Does NOT work. Overwriting the live storage groups work just fine. But RSG's fail every time with the following error. + Executing Restore database from Backup at 2/10/2009 3:30 PM (Execution unit 1) 2/10/2009 3:30:36 PM: Connected to ntexchange-test To volume First Storage Group on ntexchange-test... - 2/10/2009 3:30:36 PM: Restoring from Test-Restore Restore type: Full T-8: >>>HrESERestoreAddDatabase(0c7fe1f42) -- Database not found. Trouble writing files, error -3619 (Database not found) 2/10/2009 3:30:55 PM: Execution incomplete Remaining: 2 files, 11.1 MB Completed: 1 files, 38.1 MB Performance: 380.2 MB/minute Duration: 00:00:19 (00:00:12 idle/loading/preparing) Unless someone can Test this and show otherwise I'd really like everyone to know this doesn't work. I cant get contact with the support people to save my life so hopefully someone else with a valid support contract can send this in as a bug.
  2. Here's the event logs from the exchange server after running a restore. Event Type: Error Event Source: ESE BACKUP Event Category: Callback Event ID: 904 Date: 1/23/2009 Time: 4:18:19 PM User: N/A Computer: NTEXCHANGE-TEST Description: Information Store (2392) Callback function call ErrESECBRestoreGetDestination ended with error 0xC7FE1F42 Database not found. . For more information, click http://www.microsoft.com/contentredirect.asp.'>http://www.microsoft.com/contentredirect.asp.'>http://www.microsoft.com/contentredirect.asp.'>http://www.microsoft.com/contentredirect.asp.'>http://www.microsoft.com/contentredirect.asp.'>http://www.microsoft.com/contentredirect.asp. Event Type: Error Event Source: MSExchangeIS Event Category: Exchange Backup Restore Event ID: 9635 Date: 1/23/2009 Time: 4:18:19 PM User: N/A Computer: NTEXCHANGE-TEST Description: Failed to find a database to restore to from the Microsoft Active Directory. Storage Group specified on the backup media is eb07904b-8119-4ce1-b014-2621530f8f48. Database specified on backup media is Public Folder Store (NTEXCHANGE-TEST), error is 0xc7fe1f42. For more information, click http://www.microsoft.com/contentredirect.asp. Event Type: Information Event Source: ESE Event Category: General Event ID: 101 Date: 1/23/2009 Time: 4:18:08 PM User: N/A Computer: NTEXCHANGE-TEST Description: Information Store (2392) The database engine stopped. For more information, click http://www.microsoft.com/contentredirect.asp. Event Type: Information Event Source: ESE Event Category: General Event ID: 103 Date: 1/23/2009 Time: 4:18:08 PM User: N/A Computer: NTEXCHANGE-TEST Description: Information Store (2392) First Storage Group: The database engine stopped the instance (1). For more information, click http://www.microsoft.com/contentredirect.asp. Event Type: Information Event Source: MSExchangeIS Public Store Event Category: General Event ID: 9539 Date: 1/23/2009 Time: 4:18:08 PM User: N/A Computer: NTEXCHANGE-TEST Description: The Microsoft Exchange Information Store database "First Storage Group\Public Folder Store (NTEXCHANGE-TEST)" was stopped. For more information, click http://www.microsoft.com/contentredirect.asp. Event Type: Information Event Source: MSExchangeIS Mailbox Store Event Category: General Event ID: 9539 Date: 1/23/2009 Time: 4:18:07 PM User: N/A Computer: NTEXCHANGE-TEST Description: The Microsoft Exchange Information Store database "First Storage Group\Mailbox Store (NTEXCHANGE-TEST)" was stopped. For more information, click http://www.microsoft.com/contentredirect.asp.
  3. Ok I'm at my wits end here, This isnt an emergency to bring up a down production system. I was just making some how to guides for the recovery process for recovering exchange with our various backup apps. So were using Server 2003 sp2 Exchange 2003 sp2 Server 2003 sp2 Retrospect 7.7.123 all updates done Long story short we create RSG assign the storage group to be recovered to it. Then go into retrospect and walk through the database recovery steps. After starting the recovery we get the following errors. Executing Restore database from Backup at 1/23/2009 3:16 PM (Execution unit 1) 1/23/2009 3:16:51 PM: Connected to ntexchange-test To volume First Storage Group on ntexchange-test... 1/23/2009 3:16:51 PM: Restoring from ntexchange-test Restore type: Full T-8: >>>HrESERestoreAddDatabase(0c7fe1f42) -- Database not found. Trouble writing files, error -3619 (Database not found) 1/23/2009 3:17:15 PM: Execution incomplete Remaining: 2 files, 11.1 MB Completed: 1 files, 105.1 MB Performance: 525.1 MB/minute Duration: 00:00:23 (00:00:11 idle/loading/preparing) So even if we try to restore without using a recovery storage group it still fails with the same error. There's a long list of errors in the exchange servers event log i'd be happy to post if anyone wants to see them. But when we do a restore using either backup exec 10d or ntbackup the exact same RSG works without any issue and regular recovery of a storage group works without any issues. I have tried everything i can think of here, To be honest this is the first time we've tried to restore using retrospect so we dont even know if it works. Can anybody verify that restoring storage groups even works with the current rev of the software? Retrospect has no problems restoring the brick level backups BTW. I'd be happy to go into more detail if anyone has any ideas
  4. radamo

    Roaming users? (behind NAT)

    I dont think retrospect works that way, In that the client polls the server for jobs. You'll need to setup a vpn service so that the server can talk directly to the client through the vpn.
  5. radamo

    Roaming users? (behind NAT)

    VPN would be my first thought, Your not going to be able to tunnel through nat from the server side. Look at openvpn or Hamachi
  6. We've got 2 Windows 2003 sp2 Enterprise Servers in a MSCS cluster running the retrospect client 7.6.106. The shared storage is provided by a compellent SAN via iscsi. The backup's per retrospect are running and finishing just fine, But we just noticed that the event viewer is filled with the following error's during the backup window Event Type: Error Event Source: VSS Event Category: None Event ID: 8194 Date: 1/5/2009 Time: 8:19:17 PM User: N/A Computer: NTCLUSTER1 Description: Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005. When i query VSS the writer, it lists the following error. [color:blue]vssadmin list writers (after full retrospect backup)[/color] Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {f13aad24-a31f-4901-aad5-0decc54a80b1} State: [5] Waiting for completion Last error: No error Writer name: 'Dhcp Jet Writer' Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad} Writer Instance Id: {9004f70a-2c17-453e-b121-dd9477bbe39d} State: [1] Stable Last error: No error Writer name: 'WINS Jet Writer' Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741} Writer Instance Id: {d556052f-da63-4f0e-b889-e49ecce3f105} State: [1] Stable Last error: No error Writer name: 'MSDEWriter' Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277} Writer Instance Id: {21c55267-f8c9-4af7-8000-c5f7e3f2e290} State: [1] Stable Last error: No error [color:red]Writer name: 'Cluster Service Writer' Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e} Writer Instance Id: {07a2c5ce-571c-4ea6-bc77-c06f56de168e} State: [5] Waiting for completion Last error: Non-retryable error[/color] Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {88a4972a-cf38-4fd5-a5e3-54560130e4ed} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {7ff14b3a-b140-4b56-9f64-dc806b19eee9} State: [1] Stable Last error: No error Writer name: 'Event Log Writer' Writer Id: {eee8c692-67ed-4250-8d86-390603070d00} Writer Instance Id: {27ac61a9-afb5-4875-a39a-b0dda88f4346} State: [1] Stable Last error: No error Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {2a17d10c-dc63-4cb1-8c63-43367ad52e39} State: [1] Stable Last error: No error There are some posts on the web that point fingers at the backup application not handling a callback function properly. http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/Q_23289902.html http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/dddb05c3-dfdb-4c13-88de-e6549d3f8ea6/ When we run a backup with ntbackup the Cluster Service Writer exits with a "Stable" "No error" code. [color:blue]vssadmin list writers (after full ntbackup)[/color] vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool © Copyright 2001 Microsoft Corp. Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {f13aad24-a31f-4901-aad5-0decc54a80b1} State: [5] Waiting for completion Last error: No error Writer name: 'WINS Jet Writer' Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741} Writer Instance Id: {d556052f-da63-4f0e-b889-e49ecce3f105} State: [5] Waiting for completion Last error: No error Writer name: 'Event Log Writer' Writer Id: {eee8c692-67ed-4250-8d86-390603070d00} Writer Instance Id: {6700bb83-5b4b-4e52-867e-4f20269b422e} State: [5] Waiting for completion Last error: No error [color:red]Writer name: 'Cluster Service Writer' Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e} Writer Instance Id: {07a2c5ce-571c-4ea6-bc77-c06f56de168e} State: [5] Waiting for completion Last error: No error[/color] Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {51a4dc07-089e-4c2a-a261-7689293500a3} State: [5] Waiting for completion Last error: No error Writer name: 'MSDEWriter' Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277} Writer Instance Id: {0165dc85-bee1-4c3e-89ff-fbbb2cf46962} State: [5] Waiting for completion Last error: No error Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {7c14ddd8-fb77-430f-a273-7f5f308c2b2a} State: [5] Waiting for completion Last error: No error Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {2a17d10c-dc63-4cb1-8c63-43367ad52e39} State: [5] Waiting for completion Last error: No error Writer name: 'Removable Storage Manager' Writer Id: {5d3c3e01-0297-445b-aa81-a48d7151e235} Writer Instance Id: {debd4cd7-1065-46a7-af3f-2ff80bb8a825} State: [5] Waiting for completion Last error: No error Writer name: 'Dhcp Jet Writer' Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad} Writer Instance Id: {9004f70a-2c17-453e-b121-dd9477bbe39d} State: [5] Waiting for completion Last error: No error Were not sure if this is causing issues with the backup, We've never done a test restore of one of the cluster nodes, but it appears to be grabbing the cluster db correctly from the active node. Any information you could share would be very helpful. Thanks Rob
×