janostlund
asked on
Exchange Restore to Recovery Storage Store
Trying a Brighstor Restore of a Exchange database to a Recovery Storage Store
Performing restore as of CA document 386271
Restore starts both fails directly with error:
E8603 2008-06-09 16:44:50 6529 4 Failed to write to database. (DBNAME=First Storage Group\F:\Exchsrvr\Mdbdata\
Found no information or solution from CA or Microsoft of the "Exceeded Maximum Memory Per Connection" error
Performing restore as of CA document 386271
Restore starts both fails directly with error:
E8603 2008-06-09 16:44:50 6529 4 Failed to write to database. (DBNAME=First Storage Group\F:\Exchsrvr\Mdbdata\
Found no information or solution from CA or Microsoft of the "Exceeded Maximum Memory Per Connection" error
Compaq_Engineer
From the error message it looks as if it is trying to recover the DB to the main email store not the recovery store?
ASKER
Yes, but the backup software doesn't see the recory store. The restore to the recovery storage group is all handled by Exchange automatically. If the RSG exists the restore is redirected by Exchange instead of the main storage
Just another thought, is the recovery storage group mounted and available to be overwritten?
ASKER
Yes, it's set to "can be overwritten", but it's not mounted. In MS instructions it says "leave it unmounted" when it's created. Can that be the case that it should be mounted when performing the restore ?
ASKER
Haven't found any solution yet, and are still testing/cjecking with both CA and MS
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi, I'm experiencing the exact same problem and don't see an update on CA's site. Before I downgrade to SP3 from SP4 (SP4 resolved other issues, so I'd rather not downgrade if I don't have to) I wanted to see if you got the patch for SP4 and test it and if so, can you tell me which patch it is ?
Thanks !
Thanks !
ASKER
Hi
I got a fix called Fix T59E029. Don't know if it's official or if it was a special for us.
I adwise you to contact CA (if you have a service agreement) and ask for the fix.
If you would like to refer to my support case with CA, it was case no. 17191901
Good luck
Regards Jan
I got a fix called Fix T59E029. Don't know if it's official or if it was a special for us.
I adwise you to contact CA (if you have a service agreement) and ask for the fix.
If you would like to refer to my support case with CA, it was case no. 17191901
Good luck
Regards Jan
Jan, THANK YOU VERY MUCH !
I called CA & opened a ticket with them. I referenced your ticket # and patch & they had me jump through a bunch of hoops (re-run the job 10 times, email them a gazillion logs etc etc) for a couple hours & then finally emailed me the patch after escalating it. I installed the patch and was able to restore a DB to the SRG.
Thanks very much !
LPC-IT
I called CA & opened a ticket with them. I referenced your ticket # and patch & they had me jump through a bunch of hoops (re-run the job 10 times, email them a gazillion logs etc etc) for a couple hours & then finally emailed me the patch after escalating it. I installed the patch and was able to restore a DB to the SRG.
Thanks very much !
LPC-IT
ASKER
Hi
Nice to hear that the problem was solved for you.
Glad that someone else was helped by this issue.
PS. Pitty thou that CA patch SP4 caused this problem.
We spent many our in this before we found the problem.
Regards Jan
Nice to hear that the problem was solved for you.
Glad that someone else was helped by this issue.
PS. Pitty thou that CA patch SP4 caused this problem.
We spent many our in this before we found the problem.
Regards Jan