Restoring Entire Mailbox Exchange 2010 Database using Backup Exec 2012 #Symantec #backupexec #msexchange

In previous posts we have seen how to backup Mailbox database and restore single item from the backup.

In this post we will explore how to restore the entire database to its original location, although you might ask why would I do that when I can restore the item that I want directly from my backup set, Well there might be some scenarios where you want to restore an entire database:

– Database corruption either physically or logically.

– reseed operation.

– restoring to restore database for finer search and extraction.

we will use the same backup we did last time to restore the entire database, let us start:

User one received 2 emails (Diff 1 and Diff2):

[sociallocker id=”1891″]


It looks that those emails some how caused a Database corruption, and the database is dismounted and can’t be mounted again (this simulates a logical or physical corruption at the database level):


If I try to mount it I get the error:


Also there is an error in the event viewer:


Now I need to restore the entire database, from the Backup Exec management console Select the Exchange server and click restore, in the restore type, select Microsoft Exchange databases or storage groups:


In the Resource view, select the backup job you want to restore:


In the restore location, I will choose the original location since I want to restore it on top of the current one since the current one is corrupted, you might want to restore it to another location or the recovery database or to another server in case of dial-tone recovery.


In the overwrite page, I will choose to overwrite existing DB and logs, if you trust that logs are ok and your DB is having troubles due to a corrupted harddisk for example you can restore the database set and keep exiting logs and when the replay starts it will restore the database into the most recent status, however in my case there is a logical corruption caused by bad emails thus bad logs, so I don’t want these and I will overwrite them:


In the Temporary location, I will chose the default location, but you need to make sure that the selected location has enough space to hold the restored data:


In the next screen, you have the option to wait to start mounting the database, if you are restoring from differential backup or you want to run eseutil before mounting the database for example you might want not to mount the database otherwise, the backup exec will mount the database and start playing the logs directly, in my case I will choose to mount the database:


In the job name and schedule, set your options and click next:


on done, go to the Job list, select the restore job and click run now, the job will start restoring your database:


after the restore completes, the DB is mounted and everything is back to track :


User1 can login now to his mailbox, but you will note that Diff1 and Diff2 emails (the problematic ones) are not restored since they are weren’t backed up:



In the next post we will see how to restore differential backup, we have been talking about the full backups and we will see how to configure and restore differential backups.


#Kemp hardware load balancer sizing guide

I just spotted a very cool sizing calculator for Kemp Hardware load balancer, this is a very awesome tool for Exchange and Windows administrators who are looking for sizing guides for their HLB ordered from Kemp. you can access it from here.

an awesome tool and must see.

Is it ok to remove Exchange Server objects using ADSIEDIT #Exchange #Exchange2010

usually when people facing a failed exchange server or failed installation, admins/consultants were using the ADSIEDIT tool to remove the Exchange server object from active directory, people were using this article

I have seen an internal discussion that shocked me, for years I was using this article to remove failed Exchange2010/2007 Servers from AD, I know that I can use the recover option but it was fast and easy to use ADSIEDIT and as long it is ok to use it.

The discussion was about how safe it is using ADSIEDIT to remove Exchange server object from AD, surprisingly the response was that it is not recommended for Exchange 2007/2010 to use that method, also the above KB only applies for Exchange 2003, and there is no documented way to manually remove Exchange 2007/2010 and the only way to do it is using the setup /m:recoverserver, Thus using ADSIEDIT is not recommended nor supported.

Microsoft recommends only using ADSIEDIT only as a last resort if nothing works.

I know that it was popular even on the forums to use ADSIEDIT, from now and on use it only if server recovery failed.

more references:

Recover an Exchange Server