kengreg
asked on
Mailbox Recovery, MozyPro, SBS 2008, Exchange 2007
(1) Can MozyPro redirect a VSS restore to an alternate folder? I was asked to recover a single mailbox. My client asks that current Exchange services continue to run, and information stores must stay mounted. (The default instructions for MozyPro's VSS restore starts with dismounting the Information Stores, a bad sign.) Instead I want to restore VSS data from MozyPro for the purposes of creating a Recovery Storage Group in Exchange 2007 for SBS 2008 and simply merging one mailbox.
(2) From another angle, how do I test the VSS restore of MozyPro without putting the server at risk?
(3) Is there a light at the end of the tunnel of Jet errors? I've been through two lengthy restorations of this data already. I have the database .edb, and.log files, plus other scattered files. Data downloaded manually (not VSS) hasn't proved helpful. I downloaded via the regular Mozy restore process, but I may not have an accurate snapshot of Exchange logs. I can't repair with eseutil (eseutil /r E00). The best that I can say for my previous downloads of this data is that I can vary the eseutil errors by adding and subtracting different sets of logs, but I haven't found the magic set of logs that will complete the repair process.
(4) I spoke with four different MozyPro technicians. Has anyone been escalated higher?
Thanks,
-Ken
(2) From another angle, how do I test the VSS restore of MozyPro without putting the server at risk?
(3) Is there a light at the end of the tunnel of Jet errors? I've been through two lengthy restorations of this data already. I have the database .edb, and.log files, plus other scattered files. Data downloaded manually (not VSS) hasn't proved helpful. I downloaded via the regular Mozy restore process, but I may not have an accurate snapshot of Exchange logs. I can't repair with eseutil (eseutil /r E00). The best that I can say for my previous downloads of this data is that I can vary the eseutil errors by adding and subtracting different sets of logs, but I haven't found the magic set of logs that will complete the repair process.
(4) I spoke with four different MozyPro technicians. Has anyone been escalated higher?
Thanks,
-Ken
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Works2011,
Thanks for the good advice.
I agree that the ideal option involves restoring to an offline server. In this case, unfortunately no, we don't have an image. This kind of work would certainly add unapproved hours to the project. I would need to make an image and then deploy it to additional hardware or a virtual environment. It's a lot of work for a single mailbox.
Thanks for directing me back to eseutil /mh. I needed to investigate the "log required" parameter. The required log is actually 20 days earlier than the date on my edb file. I thought I accounted for for a huge date range by downloading logs for over a week before and after my edb date.
I didn't go back far enough. It might be that Mozy is taking too long to work with large edb files. I suppose it could take 20 days to backup the entire edb, though extremely unlikely.
It probably has more to do with the way that Mozy does incremental backups.
Making sense of the eseutil /mh command required me to look at decimal to hexadecimal conversion of log names, which is covered here. Additional info on checkpoints is helpful as well.
http://support.microsoft.com/kb/240145
I'm still waiting for my logcheck to finish.
ESEUTIL /ML E00 > LOGCHECK.TXT
I like the log better than screen output, as suggested here
http://technet.microsoft.com/en-us/library/aa998760(v=exchg.65).aspx
I'll wait to reward EE points until I know exactly where this is headed.
-Ken
Thanks for the good advice.
I agree that the ideal option involves restoring to an offline server. In this case, unfortunately no, we don't have an image. This kind of work would certainly add unapproved hours to the project. I would need to make an image and then deploy it to additional hardware or a virtual environment. It's a lot of work for a single mailbox.
Thanks for directing me back to eseutil /mh. I needed to investigate the "log required" parameter. The required log is actually 20 days earlier than the date on my edb file. I thought I accounted for for a huge date range by downloading logs for over a week before and after my edb date.
I didn't go back far enough. It might be that Mozy is taking too long to work with large edb files. I suppose it could take 20 days to backup the entire edb, though extremely unlikely.
It probably has more to do with the way that Mozy does incremental backups.
Making sense of the eseutil /mh command required me to look at decimal to hexadecimal conversion of log names, which is covered here. Additional info on checkpoints is helpful as well.
http://support.microsoft.com/kb/240145
I'm still waiting for my logcheck to finish.
ESEUTIL /ML E00 > LOGCHECK.TXT
I like the log better than screen output, as suggested here
http://technet.microsoft.com/en-us/library/aa998760(v=exchg.65).aspx
I'll wait to reward EE points until I know exactly where this is headed.
-Ken
ASKER
this command reports that all of my logs are ok
eseutil /ml E00 > logcheck.txt
Now I'm trying
eseutil /p "Mailbox Database.edb"
I can tell that it created a temp database and updated it
For the last half hour there have been no updates to the file
I think that I'm done with the Mozy portion of this question. I'll award points based on MozyPro problems. I'll continue on with known issues of eseutil /p
Like the following:
https://www.experts-exchange.com/questions/26870796/ESEUtil-p-and-database-damage.html
eseutil /ml E00 > logcheck.txt
Now I'm trying
eseutil /p "Mailbox Database.edb"
I can tell that it created a temp database and updated it
For the last half hour there have been no updates to the file
I think that I'm done with the Mozy portion of this question. I'll award points based on MozyPro problems. I'll continue on with known issues of eseutil /p
Like the following:
https://www.experts-exchange.com/questions/26870796/ESEUtil-p-and-database-damage.html
ASKER
eseutil /p "Mailbox Database.edb"
just hangs in the command prompt
the only way I know it's working is by viewing
Mailbox Database.integ.raw
which is a huge, verbose, file
just hangs in the command prompt
the only way I know it's working is by viewing
Mailbox Database.integ.raw
which is a huge, verbose, file
ASKER
MozyPro VSS restore for Exchange
http://docs.mozy.com/docs/en/user-pro-win/guide/tasks/restore_exchange_c.html
Entire MozyPro manual
http://www.mozypro.com/docs/MozyPro_Client_Manual.pdf
Jet errors lead me to sources like the following
http://msexchangeguru.com/2009/07/12/exchange-database-recovery-using-eseutil-commands/