We can now install the operating system from the Windows 2003 Server media, also remember to install the Windows Components required by Exchange Server 2003 that is ASP.NET, NNTP, SMTP and the World Wide Web Service. When you have received a replacement server or replacements for the failed hardware components, it’s important you configure and partition the disks in the new server, so they are identical to the way they were configured in the old one. Making a Copy of the Database and Log filesĭepending on the seriousness of the hardware crash and the time available for the restore, I highly recommend you try to make a copy of any accessible database and transaction log files from the server (these are good to have in hand should the databases we restore from backup later on fail), but of course this is only possible if the hard disks containing these files are in a useable state.īefore you can bring the Exchange Server to the state it was in just before the disaster occurred, you would need a copy of the most recent log files. There are also some good guides in the Microsoft Exchange Server 2000 Technical Documentation Library where much of the content also applies to Exchange Server 2003, so that’s definitely worth checking out too. If you’re the type of Exchange Admin who wants all the details, I suggest you start reading some of the splendid disaster recovery guides available at the Microsoft Exchange Server 2003 Technical Documentation Library. As I haven’t seen an easily digestive article covering this subject, I thought it was about time to write one.
In order to restore a failed Exchange 2003 Server, you can install a “new” one using the /DisasterRecovery switch, but there are several steps to it, and they need to be performed in the correct order.
0 kommentar(er)
