Hello. I have a store restored using veritas. I restored to an alternate location and now I am attempting to use RSG then exmerge the mailbox out that I need. When using exmerge I am prompted for the server, DC, and port. If I dont enter in the correct port I am prompted for the recovery store, however, if I put in the correct port 379 then I do not have the ability to choose the recovery story. The choice never even displays. I checked the state of the backed up store and it's in a dirty state. I ran a recovery replying the logs and this ran w/o issue, however, the state is still dirty. Could this be the issue? Thanks in advance. Exchange 2003 SP2. (mixed mode)

your using the exchange 2003 version of exmerge right? that's the only one that works. You can check your steps here: http://hellomate.typepad.com/exchange/2003/12/the_recovery_st.html

It does work on the active store. I can create a PST.I am not being presented with the option to choose the RSG. If I do not fill in the port then I can choice it, however, it will not run. The exmerge.log indicates "Error 8007203a opening an LDAP connection. ('LDAP://AUSEXCH:389/rootDSE') " - which is because the port is 379. If change the port then I am not presented with option to chose the recovery store. exmerge ver 6.5.7529 (latest) Thanks for the reply

the RSG is mounted right? Does exBPA dislike anything about your RSG other than having one in the first place?

no - it is not mounted. The current state is dirty shutdown. I didnt attempt to mount it after running a recovery but it failed at 66%. I didnt think it had to be mounted when using exmerge.

As far as i've ever done it, you'll have to get it mounted. eseutil time :-)

i've run eseutil /r successfully replying the logs from backup. Still dirty. I have read where exmerge will not work unless the state is consistent. Any ideas? I tried running /d immediatly after repair but the error indicated was that I needed to run recovery.

maybe ISINTEG? http://www.msexchange.org/tutorials/Exchange-ISINTEG-ESEUTIL.html Also, forgive me if you posted this already, but have you tried running the restore to the RSG again and make sure your restore procedure was S.O.P. ?