This article will cover restore options for Exchange in NMM 9. The demo in the article is with NMM 188.8.131.52 and Exchange 2013 DAG. NMM 9 offers the choice of using ItemPoint to perform mailbox/item level recovery. ItemPoint is the preferred method of GLR in NMM 9. However traditional GLR (Granular Level Restore) using NMM GUI is available for Exchange 2013 and Exchange 2010. For Exchange 2016 ItemPoint is the only method of GLR .
If you choose to use ItemPoint for mailbox/mail item recovery, then traditional GLR from NMM GUI is not available. So you can either use ItemPoint or traditional GLR restore but not both on a given host. This choice is made during NMM 9 install. Additionally if there is a requirement to restore backups done with NMM 8, then during install of NMM 9, select the option ‘Restore of NMM 8.2.x and earlier backups(VSS workflow)’
Below is the screen shot of the NMM 9 install process that shows the selection to restore backups from previous version and selecting ‘Exchange Granular Recovery’ (ItemPoint) as the preferred method of GLR.
Note, when you select to ‘Restore of NMM 8.2.x and earlier backups(VSS workflow)’, the install process installs the binaries for NMM 8.2.4, that will be used for the restore. The binaries are stored in the default folder:
C:Program FilesEMC NetWorkernsrrpvnmm
RPVNMM stands for ‘Restore Previous Version of NMM’
There is also a selection added in the ‘EMC Networker’ Program Group, under ‘NetWorker Tools’ for the Restore GUI that will read older backups done with NMM 8.2.x. The program name is ‘Restore previous NMM release backups’
In addition, the install also contains the binary ‘nsrsnap_vss_ssrecover’ that allows for flat file restore of the NMM 8 backups, if required.
On a Exchange host where ItemPoint was chosen for GLR, there are 2 restore choices available. ‘Database Recovery’ and ‘Granular Level Recover’. Note there is no ‘RDB data recover’. If you are used to seeing this option with previous versions of NMM, then note that ItemPoint restore is not handled through RDB, hence the choice of ‘RDB data recover’ is not available.
1. Database Recovery
Database Recovery provides the following options:
a. Overwrite the Database, if there is a need to recover the database to itself (overwriting it). Select the desired database and then click ‘Recover’. You will see the message window below advising to set the property ‘This database can be overwritten by a Restore’ of the database.
This can be done either using the PowerShell command as mentioned in the message window or using ECP / EAC GUI as below:
****Note this is a destructive action. Make sure this is the correct choice before you proceed. NMM does not let you set the ‘This database can be overwritten by a restore’ property from the NMM GUI, to ensure there is no accidental overwrites.
Once the property ‘This database can be overwritten by a restore’ is set, then NMM GUI allows you to proceed with restore. Click ‘recover…’ and then ‘Recover options…’ Under ‘Exchange’ tab there are certain choices to make that will determine how the ‘recover’ is done within Exchange
Below is a brief explanation of these choices:
‘Include Existing logs (Roll-forward Recovery)’. This option is useful if the database and logs were on separate volumes and the volume containing logs is still available, or even if both DB and logs are on the same volume and only the ‘edb’ file is corrupt and the logs are good, then you can do the restore of the backup and then perform a roll forward recovery using the logs on the disk. This will bring the database to the most recent state with minimum or no data loss.
‘Include only logs from this restore (Point-in-time recovery)’. Select this option when point in time restore is required, i.e the database will be recovered to the time of the last backup.
‘Put database online after restore’. By default the restore process will replay the logs and put the database online after restore. If this is not required, then click on this option again to deselect it and select ‘Do not replay the transaction logs’. If ‘Do not replay the transaction logs’ is selected then the logs are restored, but they will need to be manually replayed using ‘eseutil’
‘Deleted Database Target’, This is used if a flat file restore of database is required. This option bypasses VSS method of restore and simply restored the ‘edb’ and ‘logs’ as files to the target directory. Further processing is required to mount the database.
For Database Restore of a database that’s replicated in a DAG configuration, you first have to suspend the replication, otherwise the following error is seen in the Monitor tab:
The client name used NMMHOST2. The Exchange Server version used is Exchange 2013.
145369:nsrnmmrc: Initialization success — Exchange shell successfully initialized. Required for Exchange.
MailboxStore [DB01] is in replicated state, please suspend the replication on all DAG nodes and perform restore after that.
Also note that this restore can only be performed on the node that holds the active copy of the database.
2. GLR restore with ItemPoint:
Before trying GLR restore with ItemPoint, some preparatory steps have to be taken to meet all pre-requisites:
- Install 32 bit Outlook 2010/2013 on the server from where the restore will be performed. Outlook 2016 is currently not supported.
Microsoft does not recommend (or support) Outlook Installation on Exchange Server. Prior to NMM 9.2, ItemPoint could only be used on the Exchange server, which means outlook had to be installed on the Exchange server. However NMM 9.2 and greater allows ItemPoint GLR from a non-Exchange server (Proxy).
2. Ensure the user performing restore has send-as, receive-as permissions on the mailbox server to allow for browsing and restoring the mailboxes. Also make this user a member of the ‘Exchange Organization Management’ security group.
Also ItemPoint needs additional permission assignments to the user performing restore to allow for browsing and recovering mail items from any mailbox
Get-mailboxdatabase -identity db01 | add-adpermission -user nmm_svc -accessrights genericall
Get-mailbox | add-mailboxpermission -user nmm_svc -AccessRights FullAccess -InheritanceType All
For further information on this topic refer to ItemPoint documentation.
To perform ItemPoint GLR from a non-Exchange server ensure the following pre-requisites are met:
- The non-Exchange server would need to have same OS as the production Exchange server. You may be able to get away using a different OS on this host. Using the same OS will eliminate any complications. Check ItemPoint documentation on support for different OS.
- Install and configure a 32-bit Outlook 2010 or 32-bit Outlook 2013. Note outlook and MAPI/CDO [Messaging API and Collaboration Data Objects] software cannot co-exist on a host. If MAPI/CDO software is installed, uninstall it before installing outlook
- Install Networker client 9.2.x & NMM 9.2.x. For this article I’m using NMM 184.108.40.206
- Create a client resource for this host on the Networker server.
5. Grant remote access permissions to the user performing restore from this host. There are 2 ways to do this. Either add this user to a user group that has remote access privilege or add this user to the ‘remote access’ attribute of the DAG client resource.
Method 1: Adding the user performing the restore to the ‘Remote Access’ attribute of the client resource.
Method 2: Add the user to a user group that has ‘remote access’ privilege.
Once the above pre-requisites have been met, you are ready to perform GLR using itempoint.
To start the recovery, from NMM restore host, launch the NMM GUI as ‘administrator’. Then select the client from the drop down and then select ‘Exchange Recover Session’ => ‘Granular Level Recover’
Note this restore is being performed from a host that does not have Exchange server installed and as such NMM provides only the GLR option for restore. Since Exchange is not installed, Database Recovery or Restore to RDB cannot be performed.
From the browse window, select the desired client, browse time and database for restore and right click:
From the right click menu either choose ‘mount backup’ or ‘mount backup and run ItemPoint’. If you select ‘Mount backup’ then NMM will mount the backup and then you have to manually launch ItemPoint to restore from the mount points. ‘Mount backup and run ItemPoint’ is preferable as NMM GUI mounts the backup and then starts ItemPoint and auto fills the path for edb and log files:
Click ‘Finish’ and ItemPoint starts processing the log files and edb file:
Once the log and edb file is processed, ItemPoint GUI shows the content of the source database that was mounted. The next step is to open a target. This can be an Exchange server or a PST file. Here we open a target Exchange server, as we want to restore to a mailbox to the target server.
When you click ‘Open Target Exchange server’, you get the following choices. In ‘Select Target’ either choose to connect to a single mailbox or ‘All Mailboxes’. You would choose ‘All Mailboxes’ if you want to restore data to different mailboxes. Click ‘Next’
ItemPoint shows the number of mailboxes in the Target. Review and click ‘Close’
This output shows copy of mailbox ‘nmm_svc’ to the mailbox ‘blee’
If you need to restore a mailbox or mailbox items to a PST file, right click the mailbox / mail items and select ‘Export…’
(Only for Exchange server 2010 and Exchange Server 2013. With Exchange Server 2016 ItemPoint is the only choice for GLR)
If ItemPoint will not be used for GLR, then you can fall back on traditional GLR with NMM GUI. The recovery process here is very similar to the GLR in NMM 8, except that NMM uses ‘block based backup’ mechanism to mount the backup. In NMM 8, NwFS (Networker virtual file system) was used to perform the virtual mount of the backup.
Following are the pre-requisites for successful GLR using NMM GUI.
- Install “Messaging API and Collaboration Data Objects 1.2.1” on the Exchange server where the restore will be performed. Version 6.5.8353 is recommended
- The service account used with NMM, should have ‘send-as, receive-as’ rights on the Exchange Server
- The service account used with NMM should have a mailbox located on a database that’s mounted on the same version of Exchange server. If the environment has both Exchange Server 2010 and Exchange Server 2013, then the service account mailbox should be on a Exchange 2013 server if the GLR is being performed for Exchange Server 2013. If the GLR is being performed for Exchange server 2010, then the service account mailbox should be on a Exchange Server 2010.
- The service account used with NMM should be a member of the Exchange Organization Management security group.
- If restore to PST is required, then the service account needs to have the additional ‘Mailbox Import Export’ role
Once the above pre-requisites are met, you are ready to perform GLR restore with NMM.
- Start the NMM GUI as ‘administrator’.
- Select the correct client from the ‘client’ drop down. Change ‘Recover Browse Time’ if required.
- Click ‘Recover’ -> Exchange 2013 Recover Session -> Granular Level Recover
4. Select the desired database. Then click ‘Recover…’
5. Click ‘Recover Options…’ if you want to modify the recovery behavior.
- Under General Tab, set the diagnostic level. This normally would be used by support to troubleshoot a restore failure
b. Under ‘Exchange’ tab below are the options. The defaults are fine for GLR restore.
6. Click start recover
7. Once the restore completes, the following message window is seen:
Review the monitor window for logging of the restore:
8. Click on the ‘recover’ tab to browse the GLR database and expand to the desired mailbox.
9. Select the mailbox or mailbox items
10. If recovering the mailbox/mailbox items back to the original mailbox choose ‘Recover..’ If recovering to another mailbox choose ‘Advanced Recover..’
Here I’m recovering to the original mailbox, so I choose ‘Recover..’. The ‘monitor’ window shows the messages for the restore.
When the recover completes, you can login to the mailbox to confirm the recover was successful. The recovered items are placed under a folder ‘Recovered Items …’ as seen below
This completes GLR using NMM GUI.
Recovery from backups done with previous version
If there is a requirement to restore from backups done with NMM 8.2.x, and during install the choice ‘Restore of NMM 8.2.x and earlier backups(VSS workflow)’ was made, then NMM will install the software required to perform this restore.
Note this software is installed in “C:Program FilesEMC NetWorkernsrrpvnmm”.
NMM 9 GUI cannot be used to recover backups performed with NMM 8. To launch the NMM 8 GUI, from program group ‘EMC NetWorker -> NetWorker Tools -> ‘Restore previous NMM release backups’. Start this GUI as ‘administrator’
Check recovering Exchange backups in NMM 8 for details on recovery with NMM 8.