Avamar: Exchange Plugin – Why backup change ratio jumps from 0.5% to over 20% in one day if we failover the DB in a DAG cluster

Article Number: 499650 Article Version: 3 Article Type: Break Fix



Avamar Plug-in for Exchange VSS

Case Scenario:

We observe that Exchange DAG backup change-ratio presents a huge change ratio if we perform a failover of a database in a DAG environment “moving one DB from one exchange node to another”

We see the % value spiking up from the usual daily value of ~0.5% going up to ~20%/~30% and depending on which DB is being failed-over we even see ~60% of change ratio.

The DB is exactly the same before and after the failover, the only difference is that after the failover it is being backed up from a different node of the DAG cluster.

This behavior gives the impression that the backup data is being sent twice to the avamar storage, the expectation is that it should only send the usual ~0.5 of data which reflects average the daily change ratio for all the DBs under this DAG cluster environment.

The result of this inconsistency is that the avamar capacity is being unnecessarily over-utilized.

Explanation:

This is an expected behavior.

The logical structure of the Exchange database is the same but Avamar uses the *physical* layout of the database when performing the de-duplication.

In DAG environments, Exchange performs log shipping from the active copy of the database to the passive copy and replays the transactions against this passive copy.

Each Exchange server is responsible for applying the transaction logs against its copy of the database and there is no guarantee that it will use the same physical database layout as the other servers in the DAG.

Here is an example to better explain this concept:

  • Imagine we have two copies of the same picture and we cut each one into a puzzle using a different pattern.
  • While the picture looks the same once assembled, the physical layout of the puzzle is completely different.

Since Avamar only looks at the shape of the pieces, it has no way to know that the data is the same logical data, therefore the data is being sent to the server again however.

The DB failover was performed in the DAG cluster.

As per above explanation we learned that this is the normal behavior of the product.

Related:

  • No Related Posts

Re: EMC NetWorker 9.1: Can’t get exchange 2010 backups to work

Hi guys,

I’ve been spending a few hours reading docs and trying to get Exchange backups going without success.

From the Exchange server, I correctly configured a NMM Exchange Admin, I can validate an existing admin successfully.

Also when I run nsrnmmsv -P, I get successful message (no errors) -> Successfully listed supported save sets.

From the NetWorker console, I configured a client with Microsoft Exchange Server application enabled, I left most settings default.

From the Objects window, I selected all available:

APPLICATIONS:Microsoft Exchange 2010

APPLICATIONS:Microsoft Exchange 2010Database-Name1



Backup Objects: APPLICATIONS:Microsoft Exchange 2010

backup command: nsrnmmsv

application information:

NSR_EXCH_CHECK=yes

NSR_ESE_CC_METHOD=DB_AND_LOGS

NSR_ESE_UTIL_SEQUENTIAL=False

NSR_ESE_UTIL_THROTTLE=False

Name: Exchange-Server.domain.local

Backup Type: Microsoft Exchange Server

Snapshot Management: false

Priority: 100

Parallelism: 6

Block based backup: true

Client direct: true

Parallel save streams: false

Data Domain interface: IP



Actually I can do a Filesystem backup successfully..

But when I try an Application: Exchange backup (to backup the Exchange database), I get the errors you see below.



I believe it has to do with my storage pool, I currently use local, adv_file media type..



After reading some posts on this forum, I can confirm that save -b POOL_NAME -a DIRECT_ACCESS=yes C:” is working well from the client computer.



Is it related to the fact that I didn’t configure a Remote user in the Device properties? If so, I don’t understand how to do it, please help.



Thank you!

Victor

——————————–

107092:nsrnmmsv: Version information for C:Program FilesEMC NetWorkernsrbinnsrnmmsv.exe: Original file name: nsrnmmsv.exe Version: 9.1.0 (ntx64) Comments: Supporting Microsoft Volume Shadow Copy Service

127159:nsrnmmsv: Created temp path C:Program FilesEMC NetWorkernsrtmpnmm2018-08-16_15-00-12_5564-6044.

nsrnmmsv: multithreaded save set parallelism==6

145369:nsrnmmsv: Initialization success — Exchange shell successfully initialized. Required for Exchange.

133296 1534446013 0 0 0 6044 5564 0 Exchange-Server.domain.local nsrnmmsv NSR info 26 Starting backup operation. 0

145369 1534446014 0 0 0 6044 5564 0 Exchange-Server.domain.local nsrnmmsv NSR info 89 Initialization success — Exchange shell successfully initialized. Required for Exchange. 0

132558 1534446016 0 0 0 6044 5564 0 Exchange-Server.domain.local nsrnmmsv NSR info 75 Initialization process successful. Required for getting required log range. 0

115938 1534446016 0 0 0 6044 5564 0 Exchange-Server.domain.local nsrnmmsv NSR info 71 The maximum number of Consistency Check process threads is set to ‘%d’. 1 1 1 4

129273 1534446016 0 0 0 6044 5564 0 Exchange-Server.domain.local nsrnmmsv NSR info 41 Consistency Check Throttling is disabled. 0

114457 1534446017 0 0 0 6044 5564 0 Exchange-Server.domain.local nsrnmmsv NSR info 89 ‘%s’: adding to the file list with the minimum range as = %d and the maximum range as %d. 3 0 52 APPLICATIONS:Microsoft Exchange 2010Database-Name1 1 3 109 1 3 110

98519 1534446018 2 5 0 6116 5564 0 Exchange-Server.domain.local nsrnmmsv NSR warning 47 Unable to setup direct save with server %s: %s. 2 12 33 Backup-Server.domain.local 49 294 86929 125 %s:%s: Unable to perform backup for save-set ID ‘%s’ with %s=%s, check device and pool configuration to enable Client direct. 5 12 33 Exchange-Server.domain.local 51 66 APPLICATIONS:Microsoft Exchange 2010Database-Name1DatabaseFiles 0 10 4269132226 11 13 DIRECT_ACCESS 0 3 Yes

90018 1534446018 5 5 0 6116 5564 0 Exchange-Server.domain.local nsrnmmsv NSR critical 55 Cannot open a %s session with NetWorker server ‘%s’: %s 3 20 8 nsrnmmsv 12 33 Backup-Server.domain.local 49 294 86929 125 %s:%s: Unable to perform backup for save-set ID ‘%s’ with %s=%s, check device and pool configuration to enable Client direct. 5 12 33 Exchange-Server.domain.local 51 66 APPLICATIONS:Microsoft Exchange 2010Database-Name1DatabaseFiles 0 10 4269132226 11 13 DIRECT_ACCESS 0 3 Yes

0 1534446018 1 5 0 6116 5564 0 Exchange-Server.domain.local nsrnmmsv NSR notice 50 %s%s%s: %-*s%s%s%s %*s %2.2ld:%2.2ld:%2.2ld %6s %s 15 0 0 0 0 20 8 nsrnmmsv 1 1 0 23 66 APPLICATIONS:Microsoft Exchange 2010Database-Name1DatabaseFiles 0 7 level= 0 4 full 0 1 , 1 1 0 0 4 0 KB 30 1 0 30 1 0 30 1 0 36 1 0 0 5 files

110812 1534446018 5 0 0 6116 5564 0 Exchange-Server.domain.local nsrnmmsv NSR critical 44 Backup of Saveset ‘%s’ failed with error %s. 2 51 66 APPLICATIONS:Microsoft Exchange 2010Database-Name1DatabaseFiles 24 240 Exchange-Server.domain.local:APPLICATIONS:Microsoft Exchange 2010Database-Name1DatabaseFiles: Unable to perform backup for save-set ID ‘4269132226’ with DIRECT_ACCESS=Yes, check device and pool configuration to enable Client direct.

98519 1534446018 2 5 0 5828 5564 0 Exchange-Server.domain.local nsrnmmsv NSR warning 47 Unable to setup direct save with server %s: %s. 2 12 33 Backup-Server.domain.local 49 289 86929 125 %s:%s: Unable to perform backup for save-set ID ‘%s’ with %s=%s, check device and pool configuration to enable Client direct. 5 12 33 Exchange-Server.domain.local 51 61 APPLICATIONS:Microsoft Exchange 2010Database-Name1LogFiles 0 10 4252355010 11 13 DIRECT_ACCESS 0 3 Yes

90018 1534446018 5 5 0 5828 5564 0 Exchange-Server.domain.local nsrnmmsv NSR critical 55 Cannot open a %s session with NetWorker server ‘%s’: %s 3 20 8 nsrnmmsv 12 33 Backup-Server.domain.local 49 289 86929 125 %s:%s: Unable to perform backup for save-set ID ‘%s’ with %s=%s, check device and pool configuration to enable Client direct. 5 12 33 Exchange-Server.domain.local 51 61 APPLICATIONS:Microsoft Exchange 2010Database-Name1LogFiles 0 10 4252355010 11 13 DIRECT_ACCESS 0 3 Yes

0 1534446018 1 5 0 5828 5564 0 Exchange-Server.domain.local nsrnmmsv NSR notice 50 %s%s%s: %-*s%s%s%s %*s %2.2ld:%2.2ld:%2.2ld %6s %s 15 0 0 0 0 20 8 nsrnmmsv 1 1 0 23 61 APPLICATIONS:Microsoft Exchange 2010Database-Name1LogFiles 0 7 level= 0 4 full 0 1 , 1 1 0 0 4 0 KB 30 1 0 30 1 0 30 1 0 36 1 0 0 5 files

110812 1534446018 5 0 0 5828 5564 0 Exchange-Server.domain.local nsrnmmsv NSR critical 44 Backup of Saveset ‘%s’ failed with error %s. 2 51 61 APPLICATIONS:Microsoft Exchange 2010Database-Name1LogFiles 24 235 Exchange-Server.domain.local:APPLICATIONS:Microsoft Exchange 2010Database-Name1LogFiles: Unable to perform backup for save-set ID ‘4252355010’ with DIRECT_ACCESS=Yes, check device and pool configuration to enable Client direct.

140124 1534446020 0 0 0 6076 5564 0 Exchange-Server.domain.local nsrnmmsv NSR info 89 Performing the cleanup of ‘%s’ to avoid inconsistency in the indexes for child save sets. 1 51 52 APPLICATIONS:Microsoft Exchange 2010Database-Name1

139527 1534446027 3 0 0 6044 5564 0 Exchange-Server.domain.local nsrnmmsv NSR error 51 The backup operation did not complete successfully. 0

102333 1534446027 3 0 0 6044 5564 0 Exchange-Server.domain.local nsrnmmsv NSR error 21 Exiting with failure. 0

2018-08-16 3:00:27 PM Removing files under temp path C:Program FilesEMC NetWorkernsrtmpnmm2018-08-16_15-00-12_5564-6044.

Related:

  • No Related Posts

Home tab displays no data, Reports not working

I need a solution

I upgraded Symantec Mail Security for Microsoft Exchange from version 7.5 to 7.9 and have several problems.

It is running on Windows server 2008 R2, using Exchange Server 2010 SP2.

Symptoms:

  • When I open the SMSMSE console (to the Home tab), a message box titled “An error occurred”, says “The report response is invalid.” (I Googled this but the pages I found did not seem relevant. I also copied cmaf_db.mdb from the server (at: C:Program FilesSymantecSMSMSE7.9ServerReports), opened it in Microsoft Access, compacted and repaired it, then replaced it. Its size is 732 KB. I could open all tables in the database and read data, so the database is not corrupt.)
    The Home tab lists all of the labels but there is no data displayed. For example, “Server name:” label is displayed but it does not show the server name.

  • When I generate a report from a template, it says it was successful, but the status of the report says Failed, and it cannot be opened.

  • When I go to the Reports tab and “Reset database statistics” (or reset any of the other statistics), a message box titled “An error occurred”, says “The error occurred reading from the pipe.”

  • I can go to other tabs and they seem to work correctly. Anti-spam seems to be working correctly; X-Brightmail is in messages received, and email is going thru to users.

  • On the Monitors tab, Server Status shows:

    • Auto-Protect state: Started, Enabled

    • Installed version: 7.9.0.30

    • Virus definitions date: 7/29/2018 Rev 2

    • Virus definitions license status: Valid

    • SMSMSE service state: Started

Immediately after installing the upgrade, neither the Symantec Mail Security for Microsoft Exchange or Symantec Mail Security Utility services were running. I manually started them and could see data in the Home tab a couple times. The services seemed to stop a couple times, so I rebooted the server. Since then no data has appeared on the Home tab.

The event log within SMSMSE is filed with the following 2 errors and warnings (These are also in the Windows event log):

  • Error: The process SAVFMSELog.EXE terminated unexpectedly.

  • Warning: The process SAVFMSELog.EXE was restarted

These events occur in pairs; the error and warning have the same time stamp and each pair occurs within a couple seconds to several minutes apart.

When I look at log entries from before I installed the new version, there are thousands of entries saying: Failed to load Symantec Premium AntiSpam engine.
This entry has not appeared after installing the new version.

The Windows event log shows the following error occurring at the same time go to the Home tab in the SMSMSE console:

———————————-

Log Name:      Application

Source:        Symantec Mail Security Managed Components

Event ID:      0

Level:         Error

Computer:      zzzzz.xxxxx.local

Description:

 Time : Monday, July 30, 2018 9:45:27 AM

 Outer Exception Type: System.Runtime.InteropServices.SEHException

 Outer Exception Message: External component has thrown an exception.

 Outer Exception Source: System.Data

 —Outer Exception Stack Trace—

Server stack trace:

   at Symantec.Cmaf.Reporting.DataAccess.ReportingDBAccess.SelectChartData(ChartData& chartData)

   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)

   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:

   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

   at Symantec.Cmaf.Reporting.DataAccess.ReportingDBAccess.SelectChartData(ChartData& chartData)

   at Symantec.Cmaf.Reporting.Management.ReportingManager.ProcessAndGenerateCharts(ReportingDBAccess reportingDB, ReportBase reportData, ChartData& chartData, Boolean bGenerate)

   at Symantec.Cmaf.Reporting.Management.ReportingManager.GenerateSummaryReport(String templateName, ReportTemplates reportTemplate)

Source : Symantec.Cmaf.Reporting.Management.ReportingManager::ProcessTemplateAndGenReport Thread:8

ProcessTemplateAndGenReport at offset 694 in file:line:column <filename unknown>:0:0

———————————

I’m also getting many other (Windows event viewer) events that may pertain to my problem:

Many Event ID 24 errors saying: The Exchange certificate expired.

1 Event ID 101 from Automatic LiveUpdate Scheduler, saying: Failed unregistering service.

Many Event ID 1000, Application Error, saying: Faulting application name: SAVFMSELog.EXE, …, Faulting module name: KERNELBASE.dll…

Does anyone have a clue?

0

Related:

  • No Related Posts

Intensive use of OWA crashes IIS on the Exchange 2016 servers

Hi,

This is an environment with 20,000+ mailboxes and OWA is used to access the mailboxes (Outlook is almost not used). Now, this environment consists on 8 Exchange 2016 servers with mailbox and CAS roles ach of them and of course SourceOne extensions for OWA version 7.24.4058 are installed. on all Exchange servers and had been working good, or… That´s what it seems.

Issue: Exchange servers are experiencing high user processor at peak hours because the OWA App pool takes 90+% of processor, when this happens in one server, the issue replicates to other Exchange servers as well and the only workaround is restarting the affected Exchange servers.

Microsoft has been working on this for two weeks and now they wonder if ES1 extensions may be impacting, since ES1 and Exchange App pools are related (I ask myself if ES1 may be impacting too).

I know this intensive OWA usage is unusual but, Has anyone experienced this before? Has anybody idea of what to check from the SourceOne perspective on the Exchange server when this happens?

I´d really appreciate any tips or feedback.

Thanks in advance

Related:

  • No Related Posts

Connection Reset – Cannot send emails to messagelabs customers

I need a solution

We cannot send emails to messagelabs customers, our exchange queue shows a 421 4.4.2 Connection dropped due to ConnectionReset error. I confirmed our sending IP 205.157.157.155 does not have a negative reputation and I can telnet to cluster1.us.messagelabs.com and cluster4.us.messagelabs.com from the exchange server.

How can this be cleared up? Our client cannot communicate with their bank and one of their main customers….

Thank you

0

Related:

  • No Related Posts

Recovering Exchange Data with NMM 9

This article will cover restore options for Exchange in NMM 9. The demo in the article is with NMM 9.2.1.3 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.

pic1.png

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’

pic2.png

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

pic3.png

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.

pic4.png

This can be done either using the PowerShell command as mentioned in the message window or using ECP / EAC GUI as below:

pic5.png

****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



pic6.png

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:

  1. 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:

  1. 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.
  2. 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
  3. Install Networker client 9.2.x & NMM 9.2.x. For this article I’m using NMM 9.2.1.3
  4. Create a client resource for this host on the Networker server.

pic7.png

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.

pic8.png

Method 2: Add the user to a user group that has ‘remote access’ privilege.

pic9.png

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’

pic11.png

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:



pic12.png



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:

pic13.png

Click ‘Finish’ and ItemPoint starts processing the log files and edb file:

pic14.png





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.



pic15.png



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’







pic16.png







ItemPoint shows the number of mailboxes in the Target. Review and click ‘Close’

pic17.png

pic18.png

This output shows copy of mailbox ‘nmm_svc’ to the mailbox ‘blee’

pic19.png

If you need to restore a mailbox or mailbox items to a PST file, right click the mailbox / mail items and select ‘Export…’

pic20.png

(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.

  1. 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
  2. The service account used with NMM, should have ‘send-as, receive-as’ rights on the Exchange Server
  3. 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.
  4. The service account used with NMM should be a member of the Exchange Organization Management security group.
  5. 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.

  1. Start the NMM GUI as ‘administrator’.
  2. Select the correct client from the ‘client’ drop down. Change ‘Recover Browse Time’ if required.
  3. Click ‘Recover’ -> Exchange 2013 Recover Session -> Granular Level Recover

pic21.png

4. Select the desired database. Then click ‘Recover…’

pic22.png

5. Click ‘Recover Options…’ if you want to modify the recovery behavior.

    1. Under General Tab, set the diagnostic level. This normally would be used by support to troubleshoot a restore failure

pic23.png

b. Under ‘Exchange’ tab below are the options. The defaults are fine for GLR restore.

pic24.png

6. Click start recover

pic25.png

7. Once the restore completes, the following message window is seen:



pic26.png

Review the monitor window for logging of the restore:

pic27.png

8. Click on the ‘recover’ tab to browse the GLR database and expand to the desired mailbox.

pic28.png

9. Select the mailbox or mailbox items

pic29.png

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.

pic31.png

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

pic32.png

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’

pic33.png

Check recovering Exchange backups in NMM 8 for details on recovery with NMM 8.

Related:

  • No Related Posts

How to Restore Emails from OST file Outlook 2013?

MS Outlook 2013, like earlier Outlook versions, uses OST file to save a local replica of Exchange mailbox data. This file comes handy when user wishes to work on his mailbox even if Exchange isn’t available. But, it can’t be opened directly in Outlook if its parent account gets disconnected from Exchange. In such a case the OST file is called an ‘orphan’ file and extracting emails and other data from it can become a real pain.



Although Microsoft came up with the concept of using data files to save mailbox data locally in order to make backing up and archiving more convenient, OST and PST files have in some ways complicated mailbox management; and that holds especially true for OSTs. If you access an Exchange mailbox through Outlook, a local OST file is created to save a replica of mailbox data which the user can access and work with even if the mail server isn’t available. However, the basic nature of OST files makes managing mailbox data quite tricky for users.



The need to Restore mails from OST File

OST files have several shortcomings because of which, users often face the need to extract emails and other data stored within these files and save them in some other format:

  • OSTs cannot be transferred between different machines. If users need to access their mailbox data saved within OST files on another machine, it cannot be done directly through a simple copy-paste mechanism.
  • If the account that originally created an OST file gets deleted from the mail server, it cannot be opened directly from within Outlook.
  • In Outlook 2013 and 2016, data locally edited and saved within critical folders like Contacts, Calendars, Sent Items, etc. is not synced with the mail server and is thus not backed up there. In the event of damage to OST file, there’s no direct way to regain access to that local data since it doesn’t exist on the server.

Users who faced the need to extract OST file data because of any of the above-mentioned reasons make use of manual as well as automated ways to achieve it. For your reference, we’ve compiled a list of the most widely used and accepted techniques you can use to restore OST files if you’re sailing in the same boat.



Manual techniques to Restore OST files



In no specific order, these techniques can help you regain access to all your Exchange or other IMAP account data depending upon your exact problem scenario:



Scenario 1: If your Exchange account is intact but OST file gets corrupted



This is one of the most frequently encountered problems by Exchange users. OST files get damaged easily but if your Exchange profile is intact and you are in the habit of regularly syncing your local data with your server mailbox, regaining access to all your data should simply be a matter of manually creating a new OST file and downloading your mailbox data from the server again. Here are the steps:



  1. Quit all running instances of Outlook and open Control Panel
  2. Open the “Mail” option and in the ‘Mail Setup’ dialog box that opens, click on “Email Accounts”
  3. The next dialog that opens will display all your Outlook profiles / accounts. Here, click on the “Data Files” tab and choose the respective OST file from the list
  4. Now click on “Open File Location” to open the Windows Explorer window with the OST file’s location
  5. Close the ‘Account Settings’ and ‘Mail Setup’ windows
  6. In the Explorer window, create a copy (backup) of the OST file. Thereafter, right-click on it and click on “Delete”
  7. Start the Outlook application again to automatically create a new OST file for that account (doing so will download all the data from the Exchange server into the newly created OST file)

You should remember that if you’re using Outlook 2013 / 2016, only the data residing on the mail server will be downloaded into the new OST file. This will include your emails and the folders you have manually synced with the Exchange account. Any local data will not be downloaded since it doesn’t exist on the server. To get access to any such data you will need to convert the old OST to PST format and then open it directly within Outlook. You can either use the Outlook “Import & Export wizard” to convert OST to PST or take the help of reliable software Stellar OST to PST Converter to do so (skip to last section to discover how this product can help).



Scenario 2: If your Exchange account has been deleted or lost



If this happens, your “orphaned” OST file will most likely become useless since you won’t be able to open it directly unless you reconnect to Exchange and re-sync it. For this you will need a unique MAPI address to act as a bridge between Outlook and the Exchange server. However if this isn’t an option, the only way to access the data contained within the orphaned OST file is to convert it to PST format using Stellar OST to PST Converter. (Here you won’t have the option to use Outlook Import Export Wizard since you’ll need to open the OST file from within Outlook and without Exchange that won’t be possible).



Best Automated Solution to restore mails from OST file



If the manual technique doesn’t work or if you are dealing with an orphaned OST file, converting it to PST format is a task best handled by a professional product like Stellar OST to PST Converter. The advanced software is equipped with some very powerful algorithms that allow it to convert even the most severely damaged OST files to PST format files that can be used to access all mailbox contents including emails, attachments, contacts, calendars, notes, journals, etc. This software is your best bet if you wish to perform conversion of encrypted OST files or wish to extract only selected emails from within OST files and save them in MSG, EML, RTF, HTML, or PDF formats.



Final Thoughts…



So should a user completely shun the usage of OST files? Well obviously that isn’t an option since OST files are the Microsoft norm for saving Exchange data locally. What is needed is for users to stay aware of the techniques they can use to regain all their mailbox data if any disaster like virus infection or accidental deletion or severe corruption befalls their OST files. Converting OST files to PST format is the best way to salvage all the data stored within them and thus, having a product like Stellar OST to PST Converter handy goes a long way.

Related:

Recovering ‘Deleted Mailbox’ with NMM

Recovering ‘Deleted Mailbox’ with NMM

This article covers the scenario of recovering a ‘deleted’ mailbox from NMM. The procedure documented in this article applies both to NMM 8 and NMM 9. Exchange server 2010 is used in this demo.

Before I cover this procedure in NMM, below is background on how the need for this restore may arise.

In Exchange 2010 a user mailbox can either be ‘Removed’ or ‘Disabled’.

1-EMC-Console.jpg

Difference between ‘Remove’ and Disable’ mailbox choice in EMC:

Disable: Will remove the Exchange attributes from the user account but will leave the user account in Active Directory. The mailbox for the user will still exists on the mailbox database and it gets purged when the retention time elapses (default of 30 days)

Remove: Remove will remove both the user mailbox and user account from Active directory. The mailbox will still be there on the mailbox database till the retention time has elapses.

If the mailbox was either ‘deleted’ or ‘removed’ (for some reason, like employee leaving a company), there may be a need to restore this mailbox in future. If the deleted mailbox retention time has not expired, it could be recovered as below:

  1. If the mailbox was ‘Disabled’. This mailbox will show in the ‘Exchange Management Console’ under ‘Disconnected Mailbox’ as shown below:

a.

2-EMC-Console.jpg

b. To recover this mailbox, Right click the mailbox and select ‘Connect…’

3-console.jpg

c. Select ‘User Mailbox’ , then ‘Next’

4-console.jpg

d. Click ‘Browse’ Under ‘matching user’ and then select the user to connect this mailbox to

5console.jpg

e. Provide the ‘Alias’, then select ‘next’



6-console.jpg



f. Review Summary and select ‘Connect’





7-console.jpg

g. Review and select ‘Finish’. This will ‘reconnect’ the disconnected mailbox to the user in Active directory.



2. If the mailbox was ‘removed’ and is still within the retention period, create a new ‘user’ in Active Directory with the same name as the original user and then follow the above steps to ‘connect’ the user to the mailbox on the database.



The following exchange shell command is useful to get a list of ‘Disabled’ or ‘Removed’ mailbox users that are still within the retention period:



Get-MailboxDatabase | Get-MailboxStatistics | where {$_.DisconnectReason -ne $null} | ft displayname,database,disconnectreason,*guid*,*server* -auto

DisplayName Database DisconnectReason MailboxGuid ServerName OriginatingServer

———– ——– —————- ———– ———- —————–

charlu carydb3 Disabled 3f91bda9-453c-4752-8b88-423d2f4ccc53 APPHOST1 apphost1.spring.local

Once the retention period expires and the mailbox is purged from the database, it will not show up in the above output.

Once the mailbox data is purged from the mailbox database, if a restore is required after the retention period, then you would need to depend on your backups for restore.

Restoring a deleted mailbox using NMM:

I have used NMM 8.2.4 to demo this procedure. It likely will work as is, with NMM 8.2.3 or NMM 8.2.2. Also the same procedure applies to NMM 9. The first step in performing mailbox restore of mailbox (deleted or otherwise) is to perform GLR or restore to RDB. Refer to the post https://community.emc.com/people/fpinto/blog/2018/05/14/recovering-exchange-data-with-nmm-8

  1. Once the initial phase of GLR or RDB restore is complete, the mailboxes can be browsed from NMM GUI:

8-console.jpg

2. When you click the ‘deleted’ mailbox it generates this error message (shown below). Note, because there is no user associated with this mailbox or the associated user has its mailbox properties removed, MAPI is not able to show the contents of this mailbox. You can only recover the ‘Entire’ mailbox and not individual folders or mail items within it.



9-console.jpg

3. Acknowledge the message window by click ‘ok’. When you switch to the ‘Monitor’ tab, you will notice the same message there:

Selecting Exchange RDB view

Mailbox SystemMailbox{18d1f726-3cd7-48cd-8983-12ec40779e8b} is a ArbitrationMailbox and is not browsable nor can it be recovered.

Error getting item list: Error browsing folders — Failed to fetch mailbox items. Please see libmapibrowse.raw for more information. [exch_get_mbx_list].

Error browsing folders — Failed to fetch mailbox items. Please see libmapibrowse.raw for more information. [exch_get_mbx_list].

4. Select the mailbox for ‘restore’. Once you select the mailbox for restore, there are 2 types of restores that can be done:

  1. Restore the mailbox to itself

If you want to restore the mailbox to itself, create the mailbox with the same name (you would do this before you do the restore with NMM. You can do this with Exchange Management Console or Exchange powershell and then come back to the NMM GUI and select ‘Recover..’ as shown below:

(Note: If you have disabled the mailbox, connect the mailbox shown under ‘Disconnected Mailbox in EMC to the original user. If the mailbox was removed, then connect, under ‘Disconnected mailbox’ to a new mailbox and a new AD user with the same name. If the mailbox was deleted from the database, due expiry of retention time or the mailbox was manually deleted from the database, using the ‘remove-storemailbox’, then create a new user and new mailbox with the same name and proceed with the restore. In all variations of deletions, the mailbox can be restored to the original mailbox name)

10-console.jpg

b. Restore the mailbox to another mailbox. (Alternate mailbox)

To restore this mailbox to another mailbox, you would choose ‘Advance Recover..’. Then in the ‘Select Alternate Mailbox User’ box, specify the user to which you want to restore to and click ‘Search’ to locate the user. Then select this user and click ‘Next’

11-console.jpg

Here we are performing the restore to an alternate mailbox ‘Andy’ and ‘Start Restore’

12-console.jpg

5. When the restore is complete, switch to the ‘Monitor’ tab to check on the progress.

13-console.jpg

6. Verify the restore by logging into the mailbox of the target user, in our case ‘Andy’ :



14-console.jpg

Restore using Exchange PowerShell:

This mailbox restore can also be done using Exchange Powershell:

  1. First get the GLR database name:

Get-mailboxdatabase



15-console.jpg



b. Issue the new-mailboxrestorerequest command:

new-mailboxrestorerequest -sourcedatabase GLR20180516163434 -sourcestoremailbox “charlu” -targetmailbox “Andy” -TargetRootFolder Restore201805161717 –AllowLegacyDNMismatch



16-console.jpg





Summary:

This article covered the procedure involved in restoring a deleted mailbox from NMM 8.2.4 backups. The procedure also applies to NMM 9. Key point to remember is that the deleted mailbox cannot be browsed for individual mail items recovery from the NMM GUI. The entire mailbox can be recovered from NMM GUI or using powershell. Powershell command can be further refined to recover individual folders within the mailbox if desired.

Related:

Recovering Exchange Data with NMM 8

This article aims to describe the Restore options available for recovering Exchange backups performed with NMM (Networker Module for Microsoft) 8.2.4. While the procedure is shown with NMM 8.2.4 and Exchange 2010, it would also be applicable with other versions of NMM 8.x, like 8.2.3 and 8.2.2 with minor differences and also would apply to Exchange 2013. Exchange 2007 is not covered here. Exchange 2007 uses Storage groups and has some differences in the restore procedure. If recovery of NMM backups of Exchange 2007 Server is required, follow the NMM User guide for Exchange available at support site https://support.emc.com/products/1136_NetWorker-Module-for-Microsoft/Documentation/.

The goal of this article is to help someone who maybe performing restores with NMM for the first time and also for someone who may have not done the restores for a long time and could use a refresher. While this article covers the different types of restores, its not exhaustive and is not a replacement for the information in the NMM user guide. It compliments the user guide, by being more descriptive of the process.

Types of Restores

There are 3 types of restores. They are covered in the order of their popularity, i.e the most common type of restore is covered first:

Granular Level Restore (GLR).

GLR allows restoring mailbox or mailbox items without having to restore the entire database from backup media. It uses ‘Networker Virtual File system (NwFS)’ to mount the backups on a Data Domain Device or Advance File Type Device.

Following is the advantage of performing GLR:

  1. Restore of the entire database to Exchange server is not required. This means if you have 1 TB Exchange database to restore, you do not need to allocate 1 TB+ of disk space on the Exchange server to perform the restore. GLR virtually mounts the backup on to the Exchange server, creating a recovery database within Exchange in the process. Once this GLR database is created, one can proceed with the browse and restore of mailbox/mailbox items.

Disadvantages of performing GLR:

  1. GLR can be slow for restore of large mailboxes that contains 10’s of thousands of mail items. If GLR is get extremely slow for large mailbox restores then restoring the database to the exchange server and then performing mailbox restore may be beneficial from a performance point of view.
  2. GLR can only be performed from a level FULL backup. GLR from incremental backups is not supported.
  3. GLR can only be performed from backups done to disk type media, i.e from AFTD (Advanced File Type Device) and from Data domain devices. If backups to tape exists, then GLR from tapes cannot be done. Tape backups can be cloned to a disk media (AFTD or Data Domain) and GLR can then be performed from the disk media.

Prerequisites for GLR



Before GLR can be done, there are certain prerequisites that need to be met

1. Backups are done to either AFTD device or Data domain device.

2. Backups to be restored from must be at level FULL.

3. During NMM install, the GLR feature should be chosen to be installed. Note all Full level backups are GLR enabled, even if GLR was not chosen ding install. Even backups to Tapes are GLR enabled. If GLR was not enabled during backup, GLR is still possible. The GLR feature can be added before performing the restore, to allow for GLR.

Below are the Pre-requisites that are common for both ‘GLR’ and ‘Restore from RDB’ options from NMM GUI:

4. The service account used with NMM, should have the following permissions set:

    1. The ‘send-as’ and ‘receive-as’ rights need to be set to the Exchange server where the restore is being performed. Following is an example of how to set this permission. Execute this from a elevated Exchange powershell and replace environment specific information:

get-ExchangeServer Apphost2 | Add-AdPermission -user administrator@spring -extendedrights Receive-As, Send-As, ms-Exch-Store-Admin



b. The service account should have a mailbox on a database that’s mounted and it should be initialized with mail. I.e this mailbox should have either sent or received some mail.

5. The MAPI/CDO software needs to be installed. In the NMM user guide for Exchange the following versions are documented for Exchange 2010 and Exchange 2013.

    1. For Exchange 2010, MAPI/CDO 1.2.1 version 6.5.8244.0 or earlier. Note here that build 8244 or higher does work and you can safely use it. But if you are troubleshooting a GLR browse issue, you can choose to use adhere to this requirement.

b. For Exchange 2013 MAPI/CDO 1.2.1 version 6.5.8320.0 or later.

6. The service account needs to be a member of the following domain groups.

    1. Domain users
    2. Exchange Organization Management.

By default Exchange Organization Management group is a member of the local ‘administrators’ group on the Exchange server. If this not the case, then make sure it is.

If there is a requirement to get more granular with rights for the service account, i.e give it no more rights that needed, then create a Exchange role group and assign it the following roles:

Database Copies

Databases

Disaster Recovery

Mailbox Import Export

Mail Recipient Creation

Mail Recipients

View-Only Configuration

View-Only Recipients

Make the service account a member of the role group created above and also ensure this account is a member of the local administrators group on each Exchange server in the cluster.

***Note: if you choose not to get granular with regards to role assignments, in addition to the user being a member of Organization Management group, you would need to assign the ‘Mailbox Import Export’ role to the user performing the restore, when doing restore to ‘PST’.

How do to check if a save set is GLR enabled?:

mminfo -S -s vmmsrv -q ssid=1324416600

ssid=1324416600 savetime=5/7/2018 9:34:02 PM (1525743242) dag-2010.spring.local:APPLICATIONS:Microsoft Exchange 2010carydb3

level=full sflags=vF size=172065988 files=37 insert=5/7/2018

create=5/7/2018 complete=5/7/2018 browse=6/7/2018 11:59:59 PM retent=6/7/2018 11:59:59 PM

clientid=41c107ea-00000004-5add6330-5add6342-00025000-6064a456

*ACTUAL_HOST: apphost2;

*ACTUAL_PATH:

“C:\Program Files\EMC NetWorker\nsr\tmp\7140-1525743109-0”;

*appid: 1;

*backup start time: 1525743242;

*coverid: 1341193800;

*De-duplication: No;

*EXCHANGE_DATABASE_NAME: carydb3;

*GLR_HINT: “E:\Exchangedb\carydb3\”;

*GLR_OFFSET_MAP: Yes; ===> The GLR attributes are seen for GLR enabled save set

*GLR_OFFSET_MAP_FILENAME:

“C:\Program Files\EMC NetWorker\nsr\tmp\1324416600_om.bin”;

*policy action jobid: 128671;

*policy action name: “exchange2010-action: 1525743244”;

*policy name: “Exchange2010: 1525743244”;

*policy workflow name: “Exchange2010-wkfl: 1525743244”;

*snap_sessionid: 1525742832;

*ss data domain backup cloneid: 1525743244;

*ss data domain dedup statistics: “v1:1525743244:172465188:2157958:2157958”;

group: Exchange2010-grp;

Clone #1: cloneid=1525743244 time=5/7/2018 9:34:04 PM retent=6/7/2018 flags=F

frag@ 0 volid=1508963247 file/rec= 0/0 rn=0 last=5/7/2018

Now that we have covered the prerquisites for GLR, let’s review the procedure to perform GLR.

  1. Launch Networker User for Microsoft user GUI as ‘administrator’
  2. Select the client to restore from. In a DAG setup, this would be the DAG name. In the standalone setup, this would be the hostname of the Exchange server

1-NMM-GUI-Select-Client.JPG.jpg

3. Select GLR (Granular Level Recovery) option:

2-NMM-GUI-Select-GLR.JPG.jpg

4. Select the desired database and browse time for restore:

3-NMM-GUI-select-DB.JPG.jpg

5. Choose ‘Recover Options’. If you are troubleshooting a GLR restore issue and need to increase debug setting, you can set the debug setting here. This step is optional:



4-NMM-GUI-Select-DB-choose-recover-options-debug.JPG.jpg

6. Select ‘Start Recover’

5-NMM-GUI-Select-DB-start-recover.JPG.jpg

7. Click on ‘Monitor’ to follow the progress of the restore:



6-NMM-GUI-Select-DB-GLR-DB-Created.JPG.jpg

Notice it creates a RDB database. The name of the database starts with ‘GLR’ and the date and time of restore is appended to this to form the database name



8. When the restore is complete it, you will receive a pop up windows. Be careful, this window may be behind the main NMM window, so look out for this:

7-NMM-GUI-Recover-completion-status.JPG.jpg

7-NMM-GUI-Recovered-RDB-Pop-up.JPG.jpg

9. Once you click ‘ok’ to the above, the GUI will switch to the ‘recover’ section. Be patient over here as it may take some time for the GUI to refresh and show new information:

8-NMM-GUI-Switch-Recover.JPG.jpg

10. If after some time the GUI does not refresh, you can press ‘F5’ to manually refresh and then you can navigate to the mailboxes by click on the ‘+’ to expand the GLR db and then the mailboxes:



9-NMM-GUI-Showing-mailboxes.JPG.jpg

11. Select the desired mailbox or mailbox folders or individual items and the click ‘Recover’ to start recover of mailbox items. By default the recover will place the recovered items back into the original mailbox. In this case it’s the mailbox of ‘roger’



12. Look to the ‘Monitor’ pane to check for progress and completion:



11-mailitems-restore-complete.JPG.jpg



13. Verify the restore by logging into the mailbox of the user. You will see the mail items recovered under a new folder labelled with date and time of restore. Expand to find the recovered items:



12-Mailitems-recovered.JPG.jpg



This concludes the procedure for GLR Restore.





Restore to RDB:



If GLR is not an option, e.g if the backup data resides on tape or if GLR is not fast enough, then restoring the database to RDB is the next option. Following are the advantages of restoring to RDB:

  1. Once the restore is completed, recovering mailbox items from RDB is faster than restoring from GLR.
  2. Restore can be done from Full and incremental backups. GLRs can be done only from FULL level backup.

Disadvantage of restore to RDB:

  1. Requires free disk space to restore the full database. If you are restoring a 1 TB database, you need 1 TB+ free disk space. Restore cannot be done to a Network share. It needs to be done to a local disk.

2. May take a long time to do the restore as its restoring Full database.

Procedure for RDB restore.

  1. Launch the ‘Networker Module for Microsoft’ GUI as ‘administrator’
  2. Select ‘Database Recover’. Note, the selection of ‘RDB Data Recover’ implies recover mailbox data from RDB. This can only done after recover to RDB has been complete. So the first step to recover from RDB is to recover the database to RDB and this is done through ‘Database recover’

1-NMM-GUI-RDB-restore.JPG.jpg



3. Select the desired database from the desired browse time. Change browse time if needed. Then choose ‘Advance Recover’. From ‘Advanced Recovery’ window, select ‘Recovery Database (RDB) Recovery’



2-NMM-GUI-RDB-restore.JPG.jpg





4. If you are troubleshooting a restore failure and what to run the restore in Debug, select ‘Recover Options’ and then choose the debug level. We will perform this restore in normal level.





3-NMM-GUI-RDB-restore.JPG.jpg





5. In ‘Manage RDB’ window, select ‘Create’. Note if you have a previously created RDB, either select that RDB for ‘RDB overwrite’ or delete the previous RDB and ‘Create’ a new one. Deletion and creation of RDB can all be done from ‘Manage RDB’. Having more than one RDB will cause browsing issues.

4-NMM-GUI-RDB-restore.JPG.jpg

6. Specify a name for RDB and specify file paths for EDB and logs:



5-NMM-GUI-RDB-restore.JPG.jpg

7. Click ‘Create’

6-NMM-GUI-RDB-restore.JPG.jpg

8. Select the RDB and click ‘Next’

7-NMM-GUI-RDB-restore.JPG.jpg

9. Review the selections and click ‘Next’

8-NMM-GUI-RDB-restore.JPG.jpg

10. Click ‘Recover Options..’ and select Debug level, if you want to run the restore in debug mode for troubleshooting. Click ‘Next’ to proceed with restore



9-NMM-GUI-RDB-restore.JPG.jpg

11. Switch to the ‘Monitor’ view to monitor the progress of the restore. Once the restore has completed successfully, you will see this pop up window tilted ‘Recovered RDB Mailbox Items’. Look out for this window. Sometimes, this may get hidden behind the main NMM GUI. Click ‘ok’ to continue

10-NMM-GUI-RDB-restore.JPG.jpg

12. Once you click ‘ok’ above, then click ‘recover’ -> Exchange 2010 Recover Session -> ‘RDB Data Recover’. This will allow you to browse the contents of the RDB database.

11-NMM-GUI-RDB-restore.JPG.jpg

13. Depending on the size of the DB, it may take some time for the RDB DB to show. Expand to see the listing of mailboxes.

12-NMM-GUI-RDB-restore.JPG.jpg

14. The process of recovering mail items from RDB from this point on is identical to the restore of mail items from GLR.





The third type of restore is not a very common type of restore: Recovering a database and overwriting it. Disaster Recovery Situation

If there is a need to perform Disaster Recovery of the Exchange databases, due to data corruption or some other DR situation, then use the procedure below: (Note this is a destructive process as it will overwrite the existing database. So be sure this is what you want to do)

For Standalone Exchange servers:

1. Start the ‘Networker Module for Microsoft’ GUI as ‘administrator’

2. Choose ‘Database Recovery’

1-NMM-GUI-DB-restore.JPG.jpg

3. Choose the database that need to be restored and the required browse time. Then click ‘Recover’

2-NMM-GUI-DB-restore.JPG.jpg

4. The above message indicates that the ‘This database can be overwritten by a restore’ property on the database needs to be set. This can be done through Exchange PowerShell as or through Exchange Management Console. Once this is done. Try the restore again.

5. As usual, you get to choose to enable ‘Debug’ logging under ‘Recover options..’

3-NMM-GUI-DB-restore.JPG.jpg

6. Under ‘Exchange’ Tab, you get to pick a few options that are relevant to this type of restore. These options have bee explained below. The default choices are shown below:

4-NMM-GUI-DB-restore.JPG.jpg

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 restores the ‘edb’ and ‘logs’ as files to the target directory. Further processing is required to mount the database.g. Once the desired options are selected, click ‘Start Recover’ to start the restore. Progress of the restore can be monitored under the ‘monitor’ tab

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:

NMM … Using client name APPHOST1, the version of the Exchange server is Exchange 2010.

96585:nsrsnap_vss_recover:NMM .. Initialization success — Exchange shell successfully initialized. Required for Exchange 2010 or Exchange 2013.

NMM .. MailboxStore [carydb3] is in replicated state, please suspend the replication on all DAG nodes and perform restore after that.



Once the replication is suspended, then the rest of the procedure to restore the database is same as in the standalone Exchange server. Also note, the restore cannot be done on the server hosting the passive copy. It has to be done on the server hosting the active copy of the database. Once the restore is successful, you will see this message below:



5-database-restore.png





Recovering Public Folder Database



Public folder Databases are implemented differently in Exchange 2010 vs Exchange 2013. In Exchange 2010, public folders databases are just like mailbox database’s but are identified separately as Public Folder database. They are not replicated through the DAG mechanism, but can use ‘Public Folder Replication’ for high availability. Public folder database cannot be recovered to an RDB



In Exchange 2013 and Exchange 2016 public folders are supported through public folder mailbox. This mailbox is stored in a regular mailbox database that allows support for high availability through DAG. This means Public folder database can be restored to RDB.



In Exchange 2010, NMM considers public folder databases as ‘Standalone Databases’ and backs them up as part of the DAG, if configured to include Standalone Database. The backups are indexed to the ‘DAG’ client index.



In Exchange 2016, since public folders are part of regular mailbox database (you could have a database dedicated to public folders), the backups for this follows the same workflow as regular mailbox database.



To restore Public Folder database for Exchange 2010, the method for restore would be same as restoring a mailbox database (Overwrite existing database). However they cannot be recovered to RDB and GLR cannot be done on them. The only choice is to overwrite the database. Note public folder databases belong to a specific Exchange server and restore can only done back to that server. So if a public folder resides on Server-A, it cannot be restored to Server-B, it has to be restored to Server-A. When you bring up the NMM GUI, if you see a ‘X’ on the database name as below:



Public-Folder-1.png



This means that the Public folder database ‘Public_Folder01’ is not owned by the Exchange server on which the NMM GUI is opened and was not backed up from this server and is not available for recovery. If the database is browsed from the server that owns it, it would show as below:



Public-Folder-2.png



What if you want to restore a Public Folder Database, but do not want to overwrite the existing database?. Flat file restore comes to the rescue. I will not be covering Flat File restore in this post.



Recovering a mailbox/mailbox items to PST file



1. NMM supports the restore of a mailbox /mailbox items to a PST file. The most important thing to remember here is that an additional ‘role’ is required for the NMM service account to allow for this restore. And this role is ‘Mailbox Import Export’ Role. By default this role is not assigned to the role group ‘Exchange Organization Management’.

Below command will list the roles assigned to the custom role group ‘nmm-backup-group’. Note the role ‘Mailbox Import Export’ is assigned to this role group. If this role and the others mentioned below are assigned to the service account of NMM, then you are all set to do restore to PST. If not assign this role manually:

Get-ManagementRoleAssignment -roleassignee nmm-backup-group | select name,role

Name Role

—- —-

Database Copies-NMM-Backup-Group Database Copies

Databases-NMM-Backup-Group Databases

Disaster Recovery-NMM-Backup-Group Disaster Recovery

Mail Recipient Creation-NMM-Backup-Group Mail Recipient Creation

Mail Recipients-NMM-Backup-Group Mail Recipients

Mailbox Import Export-NMM-Backup-Group Mailbox Import Export

View-Only Configuration-NMM-Backup-Group View-Only Configuration

View-Only Recipients-NMM-Backup-Group View-Only Recipients

2. Another prerequisite for restore to PST is a UNC path for the target location. The restore cannot be done to a local path. Create a UNC path. This share can be local or on a different server. Below is a share that’s been created on C:pst-restore. This share has read/write permission for ‘Everyone’

[PS] C:Windowssystem32>net share

Share name Resource Remark

——————————————————————————-

ADMIN$ C:Windows Remote Admin

C$ C: Default share

E$ E: Default share

IPC$ Remote IPC

Address E:Program FilesMicrosoftExchange ServerV14Mailboxaddress

“Access to address objects”

PST-Restore C:PST-Restore

The command completed successfully.

3. Perform GLR as explained before or Restore to RDB and then restore from RDB. Select the required mailbox or mail items, then under ‘Recover Options..’ , ‘Exchange’ Tab, specify path to PST Target. Notice the UNC path “\apphost1pst-restorerogerpstroger.pst”

PST-Restore.JPG.jpg

4. Review the selection and then click ‘Start Recover’

2-PST-Restore.JPG.jpg

5. Check the ‘Monitor’ tab to review the status of the restore.

6. When the restore is complete, the PST file can be found under the UNC path:

6-PST-restore.png

Related:

  • No Related Posts