This afternoon, I got a report that 203-stu2dc was inaccessible. In checking out the server, and the host, I found that both of them were shut down uncleanly. For some reason, this seems to be quite a regular occurrence at this site.
After rebooting logging in to the host, I found that the 203-stu2dc database (lsass) was corrupt, and was forcing the server to shutdown, into Active Directory recovery mode. Unfortunately, no database recovery operations were succeeding in recovering the server.
At this point, the only option is to do some data recovery from the server, and reset up all the application on a new server.
Since we’re going in the direction of consolidating all the servers, and since I’m forced to move the data right now. I’m going to go ahead and move everything to 203-dc1, create a CNAME to 203-stu2dc, as to avoid having to go and reconfigure all the workstations with the new server paths.
Unfortunately, with everything else going on for me, I can only do my best to bring it up ASAP. I will keep you posted on the progress; unless someone would like volunteer to take this one on, and I can assist in the process.
If I don’t hear from anyone, I’m just assuming that responsibility, and proceeding with the recovery.
Helpdesk, I would appreciate if you can contact the site and inform them of the situation, and that we are doing our best to bring them back online as soon as possible.
- This issue presented itself on 03/09/2010 @ 4:00pm
No comments:
Post a Comment
Please make your comment. (GMK)
Note: Only a member of this blog may post a comment.