01-20-2010 06:43 AM
0xe000ff00 - Unable to restore some Microsoft Exchange components because one or more of the databases are currently mounted or because the Recovery Storage Group is not properly configured. Use the Exchange System Manager to check the configuration of the Recovery Storage Group and the mount status of the databases.
The database is not currently mounted, it's a clean /disasterrecovery installation. I have not done anything with the RSG as I have no experience with it and as far as I have read the RSG should not be used to restore public folders or complete Information Store Backups.
The crashed server had Exchange Standard, does it matter if I use Enterprise to restore?
Have I even done it the right way? As far as I have read of guides on the internet that is pretty much the way to do it.
Just ask if you need more information.
Thanks in advance.
01-25-2010 12:23 AM
01-25-2010 03:03 AM
https://www-secure.symantec.com/connect/articles/restoring-exchange-or-individual-mailboxesitems-using-backup-exec-howto |
01-27-2010 10:21 AM
01-28-2010 11:40 PM
01-29-2010 12:29 AM
01-29-2010 02:24 AM
01-29-2010 03:02 AM
01-29-2010 03:36 AM
01-29-2010 04:10 AM
01-29-2010 05:34 AM
01-29-2010 05:53 AM
02-01-2010 12:22 AM
02-01-2010 01:07 AM
0x80010119, which results in some follow up error messages. can verfiy the vss on that server ? additional Informatino is available here http://msexchangeteam.com/archive/2008/08/25/449684.aspx command vssadmin list writers it must contain something a Exchange Writer. Maybe its time for a workaround, install 2nd exchange server with a RSG, and redirect the restore. Or make a granular restore of the objects into a empty database. Regards
02-01-2010 02:32 AM
02-01-2010 02:50 AM
02-01-2010 03:03 AM
If you suspect your VSS writer, open up a command prompt and run:
vssadmin list writers
This will show an output like:
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {70e35b00-9921-434c-b886-013b6ea4d958}
State: [1] Stable
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {6894931d-9c22-4578-8f4b-f408dfd63767}
State: [1] Stable
Last error: No error
Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {850e1b49-3546-433a-8dde-536320cd250c}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {23222a01-3df0-492f-9e38-4b5cc67ad1e7}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {b2ec3364-2069-4daf-96f8-40893e04666e}
State: [1] Stable
Last error: No error
Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
Writer Instance Id: {02ed8110-65a6-4a62-8517-704bf1d41f9d}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {a5869bcd-67c3-43d5-bc65-9cb66d259d59}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {f2ac38e9-1344-47a3-8335-761223e1c090}
State: [1] Stable
Last error: No error
If there ARE any errors, it's going to state that. If so, give the tech article below a read on how to sort out VSS errors:
http://seer.entsupport.symantec.com/docs/261993.htm
02-05-2010 05:33 AM
02-10-2010 03:58 AM
[0000032812,0x0004c0:0x05f0:0xb42b5fc4] modules\sec\security.cxx(2200): CVssSidCollection::AddSid: Adding SID: SERVER2003\Administrator [0000032812,0x0004c0:0x05f0:0xb42b5fc4] EXIT {CVssSidCollection::AddSid}: hr: 0x00000000 [0000032812,0x0004c0:0x05f0:0xb42b5fc4] ENTER {CVssSidCollection::AddSid}: [0000032812,0x0004c0:0x05f0:0xb42b5fc4] modules\sec\security.cxx(2141): CVssSidCollection::AddSid: Adding SID S-1-5-21-4143271690-2742500164-1435389183-512 ... [0000035375,0x000340:0x05c8:0xa862afd4] modules\sec\security.cxx(2162): CVssSidCollection::AddSid: Unexpected error while mapping SID to a real account. [1789] Ignoring SID... [0000035375,0x000340:0x05c8:0xa862afd4] EXIT {CVssSidCollection::AddSid}: hr: 0x00000000 [0000035375,0x0004c0:0x05f0:0xb42b5fc4] modules\sec\security.cxx(2162): CVssSidCollection::AddSid: Unexpected error while mapping SID to a real account. [1789] Ignoring SID... [0000035390,0x0004c0:0x05f0:0xb42b5fc4] EXIT {CVssSidCollection::AddSid}: hr: 0x00000000 [0000035390,0x000340:0x05c8:0xa862afd4] ENTER {CAutoSid::CreateBasicSid}: [0000035390,0x000340:0x0488:0xa862afd4] modules\sec\security.cxx(2162): CVssSidCollection::AddSid: Unexpected error while mapping SID to a real account. [1789] Ignoring SID... [0000035390,0x000340:0x0488:0xa862afd4] EXIT {CVssSidCollection::AddSid}: hr: 0x00000000 [0000035390,0x0004c0:0x05f0:0xb42b5fc4] ENTER {CAutoSid::CreateBasicSid}: [0000035390,0x000340:0x05c8:0xa862afd4] EXIT {CAutoSid::CreateBasicSid}: hr: 0x00000000 [0000035390,0x0004c0:0x05f0:0xb42b5fc4] EXIT {CAutoSid::CreateBasicSid}: hr: 0x00000000 [0000035390,0x000340:0x05c8:0xa862afd4] ENTER {CAutoSid::CreateBasicSid}: [0000035390,0x0004c0:0x05f0:0xb42b5fc4] ENTER {CAutoSid::CreateBasicSid}: [0000035390,0x000340:0x05c8:0xa862afd4] EXIT {CAutoSid::CreateBasicSid}: hr: 0x00000000 [0000035390,0x0004c0:0x05f0:0xb42b5fc4] EXIT {CAutoSid::CreateBasicSid}: hr: 0x00000000 [0000035390,0x000340:0x05c8:0xa862afd4] ENTER {CVssRegistryKey::Close}: [0000035390,0x0004c0:0x05f0:0xb42b5fc4] ENTER {CVssRegistryKey::Close}: [0000035390,0x000340:0x05c8:0xa862afd4] EXIT {CVssRegistryKey::Close}: hr: 0x00000000 [0000035390,0x0004c0:0x05f0:0xb42b5fc4] EXIT {CVssRegistryKey::Close}: hr: 0x00000000
It seems like it has some problems with the SID on the Administrator user. I have no clue about why or what.
The pretty much same error shows up at the bottom of the logfile, you can read the whole thing here -> http://tocom.no/Files/logfiles/trace.txt
02-10-2010 04:28 AM