Recover a deleted Exchange 2007 mailbox when the AD user has been deleted as well

I had a challenge this week.  I never played with Exchange's  Recovery Storage Groups (RSG) and I had to restore an Exchange mailbox that has been deleted.  The user left the organization a while ago and I don't know why, I couldn't find the .pst that we usually create before deleting the user and mailbox.

We use EMC Networker for our backups, but it cannot restore a mailbox if the mailbox has been deleted.  The answer from EMC: The user has to restore the information store (IS) to the RSG and from there, contact Microsoft to find how to export the mailbox out of the RSG.

Of course, I didn't contact Microsoft, but I found that:

http://technet.microsoft.com/en-us/library/bb795895.aspx

So here is what I did:

  • Following the EMC Networker module for exchange admin guide
    • Created the RSG in Exchange Management Shell (EMS)
    • Created the Mailbox Database in the RSG (in EMS
    • Restore the Mailbox Database using Networker (which restores it to the RSG)
Then, I just used this command (taken from the link above):

Restore-Mailbox -RSGMailbox 'John' -RSGDatabase 'RSG\DB11' -id 'Simon' -TargetFolder 'John E-mail'

That assumes that the mailbox to recover is "John", the RSG database is named DB11 and the RSG is called RSG.  It will restore the contents of John's mailbos to a folder called "John E-mail" in Simon's mailbox.

Unless you have spare space to keep the RSG, remove the DB and RSG http://technet.microsoft.com/en-us/library/bb125197%28v=exchg.80%29.aspx

Comments

Post a Comment

Popular posts from this blog

General linux performance troubleshooting

Here's a list of commands that you should execute and then share the output to someone who can help you figure out what resource is the bottleneck in your system. Note, it requires the  sysstat  and  procps  packages (ubuntu and RHEL and its derivatives): uptime vmstat 1 10 iostat -xN 2 10 mpstat -P ALL 3 10 pidstat 1 10 free -mw (or free -m, if your OS doesn't support -w)  uptime is to see the load averages on the system. vmstat is mostly used to tell if the system is swapping or not. If you see significant numbers in the 'si' and 'so' columns, your system is most likely swapping (using the hard drive as RAM), which usually slows performance a lot. iostat is mostly used to determine if your disk subsystem is not able to cope with the load. If you see one or more lines that shows 100 or close almost constantly, it is probably the case.  If it is your swap volume, you probably saw numbers in the 'si' and 'so' columns in the  vmsta...
Read more

Networker automated recovery testing using the REST API - introduction

One feature that is lacking from Networker, compared to some of its competitors, is the built-in automatic recovery testing. However, when there's an API, there is a way.  Networker's REST API is not perfect, but it allows the backup administrator to perform queries about Networker resources (objects). As my workload is going up, I realize that one of the tasks that I tend to skip the most is the periodical recovery tests.  Don't forget that a a backup that is not tested should be considered non-successful. I also found out that my recovery tests were not diverse enough. When I started this project, I knew a little bit about REST APIs, and nothing about JSON processing. With the Networker REST API documentation, and the help of a friend and Networker Support staff, I was able to create HTTP queries with Postman,  cURL and jq . Once I got the queries that I needed, I put them in a bash script that would somehow select one backup, and then restore it. My first attem...
Read more

Tips for being a better system administrator

Here are a few tips that I have discovered or implemented during my career, that can help anyone get better results: Follow the 3-2-1 backup strategy  or better 3 copies of the data 3 different media 1 copy offsite Test your backups regularly. Ideally, automate your recovery tests. Use Whatever-as-code as much as you can. IaC is the first that comes to my mind, but using code to define objects and their properties have several advantages: Auto-documentation of changes Ability to easily rollback (using source code management like Git) Makes it easier for standardization an compliance Ansible, Chef, Puppet, Salt, Terraform, Pulumi are good examples Maintain a changelog of all the major changes in your infrastructure (that isn't already "documented" because you're using IaC). Keep track of your hardware inventory and plan your renewals and warranty extension purchases. Build a spreadsheet with all the components that you manage and make sure that everyone on the sysadmi...
Read more