Hi all,

I have inherited a cluster of exchange 2003 server, I am ware that it is EOL but the business still chooses to stick with it for now. Anyhow my query is that the server is setup with a full backup that takes places mon-fri and this is backed up to tape using a third party application. 

I have recently had a request to restore a mailbox and application was setup with database level backups, therefore I am planning to restore relevant mail store to the recovery storage group. The server has 3 administrative groups each with 4 mail stores, from my understanding all the transaction logs get written to the same directory therefore if I just restore the single mailbox that is needed will all these logs get restored as well (obviously to a different file path)?

Also the restore wizard on the backup software has an option to "Commit After Restore" I understand that this will replay the logs into the restored database, is this the case?

I can't answer the questions on 2003.

What I will ask is  you have provided a written statement of risk to the business?

Exchange 2003 is out of support

Windows 2003 will be out of support in July.

If this is a critical restore request where will you get help with this? 

I'd request a written confirmation from management stating that they will be held accountable for all risks.  How do you plan to protect the OS come July 16th for example?  Do you have access to security patches?  Don't assume that file system AV will protect you.....

Hi Mika,

As Rhoderick mentioned, Exchange 2003 has been out of support. I suggest upgrade to Exchange 2010/2013 or Office 365.

About "Commit After Restore", do you use Symantec for backup? If it is the case, "Commit After Restore" will commit the logs to the database if selected.

Thanks

Hi,

I know the ex03 is EOL and w3k is going to be EOL come July 2015, however there still businesses running legacy software and obviously take the risks that come with it.

Mavis you have answered one of my queries, as I suspected the  "Commit After Restore" replays restored logs into the restored database