davids355
asked on
How can I mount an EDB file in recovery storage group, exchange 2010?
I am trying to restore an EDB file (public folders) from backup to recovery storage group to restore a single contact (grr).
But its not working, I am getting an error.
My procedure is as follows:
restore the EDB and log files
check state of EDB file.
get it into clean shutdown state.
create recovery storage group pointing to that EDB file.
try to mount, and it fails.
I thought it might be the backup, so I dismounted the live store and copied the stores EDB and log files to another location, mounted the store again, tehn started working with that live copy of files.
I go through the same procedure and get the same error:
Couldn't mount the database that you specified. Specified database: RecoveryDB; Error code: An Active Manager operation
failed. Error The database action failed. Error: Operation failed with message: MapiExceptionNotFound: Unable to mount
database. (hr=0x80004005, ec=-1305)
. [Database: RecoveryDB, Server: DC.parentscon.local].
+ CategoryInfo : InvalidOperation: (RecoveryDB:ADObjectId) [Mount-Database], InvalidOperationException
+ FullyQualifiedErrorId : 7CA7B047,Microsoft.Exchang e.Manageme nt.SystemC onfigurati onTasks.Mo untDatabas e
So I dont think it is anything wrong with my backup, my procedure for mounting must be wrong somewhere...
Can anyone help?
But its not working, I am getting an error.
My procedure is as follows:
restore the EDB and log files
check state of EDB file.
get it into clean shutdown state.
create recovery storage group pointing to that EDB file.
try to mount, and it fails.
I thought it might be the backup, so I dismounted the live store and copied the stores EDB and log files to another location, mounted the store again, tehn started working with that live copy of files.
I go through the same procedure and get the same error:
Couldn't mount the database that you specified. Specified database: RecoveryDB; Error code: An Active Manager operation
failed. Error The database action failed. Error: Operation failed with message: MapiExceptionNotFound: Unable to mount
database. (hr=0x80004005, ec=-1305)
. [Database: RecoveryDB, Server: DC.parentscon.local].
+ CategoryInfo : InvalidOperation: (RecoveryDB:ADObjectId) [Mount-Database], InvalidOperationException
+ FullyQualifiedErrorId : 7CA7B047,Microsoft.Exchang
So I dont think it is anything wrong with my backup, my procedure for mounting must be wrong somewhere...
Can anyone help?
Pardon me for asking, but why are you doing all of this for a mail contact? Just recreate the contact.
ASKER
Sorry, when I said contact, its not, its a contact group - its probably about 30 addresses in there.
I could probably get out of doing it, but seeing as the issue arose I thought it would be a good time to do a test restore...
Now its annoying me that it wont work.
I could probably get out of doing it, but seeing as the issue arose I thought it would be a good time to do a test restore...
Now its annoying me that it wont work.
What backup software do you have?
ASKER
I use backup assist backup software and Rsync technology.
At first I thought that was quite likely the problem (maybe corruption during transfer), but afterwards I tried copying the live EDB files, just as an experiment, and I couldn't mount them either, same error.
At first I thought that was quite likely the problem (maybe corruption during transfer), but afterwards I tried copying the live EDB files, just as an experiment, and I couldn't mount them either, same error.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hmm. Looks like this thread vanished from my queue. My apologies.
Correct. You are limited to only one Public Folder Database.
Glad you got it resolved.
And/or maybe because apparently you can only have one public mailbox in exchange 2010 standard?
Correct. You are limited to only one Public Folder Database.
Glad you got it resolved.
ASKER
question didn't get answered.
to be fair the question wasn't that sensible.
to be fair the question wasn't that sensible.