Robb, I tested DigiScope from Lucid8 when trying to recover a PF and it worked extremely well. If you have some type of a backup or even an unmountable PF, it could very well work. I ran the evaluation against a corrupt PF to see what it could recover and it was impressive. In the end, we decided there was no important information in the PFs so we just started over.
http://www.lucid8.com/product/digiscope.asp -Jeff -----Original Message----- From: Robb Pickinpaugh [mailto:[email protected]] Sent: Tuesday, March 20, 2012 3:19 PM To: MS-Exchange Admin Issues Subject: Exchange 2010 DR PF DB We had one of those it shouldn't ever happen situations last week. An entire disk array was brought down by a single failing disk, which caused another disk in a raid to be detected as bad and an entire virtual disk was lost. As a result a mail store and PF store was lost. Our backups weren't as pristine as we would have liked due to several issues, and we are taking steps to prevent this particular set of circumstances from hitting us again. Fortunately are able to restore the majority of the users mail, the problem is that the PF store on that server wasn't backed up for whatever reason. I just discovered this little tidbit. So now, I am looking at how to get a PF DB back on that server. Right now the way I see it, I have two options. I just don't know which would be the correct path to take. Should I go ahead and mount the Database and have Exchange create an empty DB, make sure the replicas are all set and let it go? Should I create a new PF DB, set the replicas and remove the old DB? Obviously I will want to make sure I'm backing things up in the future, but for now I want to get a PF DB created to start getting things back to "normal" again. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe exchangelist
