Well I answered my question. Any missing log files during hard recovery it will fail and report in the log what the missing log file is. Cut all the files out after that spot and went to the restore temp location that the .env file is located, ran eseutil /cc and good night sally its working. Its also WAY SLOW. Very exciting first time I have had to actually replay log files from a failed backup to get it up to its most current possible data. I know a client who is going to be very happy. :)
Now I get to figure out how to purposely break our 2003 test box and our 2010 box so I can get the guys some experience doing this. Lord knows in Florida this year we may have a few of these. Off to bed so I can deliver this bad boy early in the morning. From: [email protected] [mailto:[email protected]] Sent: Thursday, August 05, 2010 12:48 AM To: MS-Exchange Admin Issues Subject: Exchange 2003 Restore and Log replay Hey Exchange guru's Question, new client called asking for some help. Onsite turns out 2/3 drives were poof in their raid, but the raid card could see all the HDD's as available. Had this happen a few times on the CERC raid cards. Forced raid online and system saw logical volumes. Yeah..not quite. Several folders were completely gone including the C:\windows folder.. empty... After getting an image of the volumes, and mounting to pull critical data files off the drives, I ran a chkdsk..Where it went meandering for hours finding orphaned files, redoing checkpoints, deleting and recreating mount points...Poof all of the files were back. Bad news...AD gone by by. All the ESE databases are gone, DHCP, WINS, AD. Exchange..yep..poof. and the SQL monitoring for SBS. Not worried about the SQL at the moment. Well, what else did I get..A full server backup about a week old. Able to restore System state and Exchange with that. REAL QUESTION BELOW: So I am up to my current point...I have a whole list of transaction logs that I was able to get up to the failure and I want to replay them. It looks like I might be missing 2 as the last 7 log files for the day of the failure are missing section xxxxx8 and the xxxxxxA and xxxxxxC of the logs. Can I just remove those last sections of the log files and let it replay all the way up to where I have them contiguous? Placing them in the original exchangeDB folder is what the docs say and let it replay. If I leave the ones in there that are missing will it replay up to the last contiguous file and ignore the rest or do I need to remove them before it starts it replay? Otherwise the server is up and kicking. Thx Greg
