VIDEO: NetBackup Support Screencast Demo: Performing an Exchange 2007 Snapshot/CCR Database Restore to a Recovery Storage Group (RSG) on an Alternate Client Using NetBackup 6.5


The video linked to is a part of the NetBackup Support Screencast Demo Video series.  It demonstrates Performing an Exchange 2007 Snapshot/CCR Database Restore to a Recovery Storage Group (RSG) on an Alternate Client Using NetBackup 6.5.

The video can be viewed by clicking on the following link:
Welcome to the NetBackup Support Screencast Demo Video series.
These videos deliver how to demonstrations in a variety of NetBackup functions.
They assume fundamental NetBackup knowledge.
If you need basic NetBackup training, please go to where you will be able to find a listing of instructor-led classroom training as well as self-paced computer-based courses for NetBackup.
This video is Performing an Exchange 2007 Snapshot/CCR Database Restore to a Recovery Storage Group (RSG) on an Alternate Client Using NetBackup 6.5.
For this demonstration, we will be using a master/media server running NetBackup 6.5.6 on Windows 2003 R2 SP2. The backup was done from the passive node of an Exchange 2007 cluster configured for CCR, running NetBackup 6.5.6 on Windows 2008 R2, and we will be restoring to an Exchange 2007 stand-alone server running NetBackup 6.5.5 on Windows 2008 R2. Both Exchange 2007 servers are in the same domain. We will not be working directly with the Exchange 2007 cluster for this demonstration. We will only be working with the backup image via the NetBackup master/media server, and the Exchange 2007 stand alone server we are restoring to. We will also be using a separate hard drive on the destination Exchange server for the storage of the restored Exchange database and transaction logs.
Please also note that for NetBackup version 6.5, there have been numerous features added, as well as streamlined, regarding backups and restores of Exchange 2007 throughout the NetBackup 6.5 update releases. For the demonstration in this video, we will be covering the configuration as it relates to NetBackup 6.5.4 and later. It is also highly recommended that NetBackup 6.5 be at update release 6.5.4 or later for Exchange backups and restores.
This video does not apply to:
Exchange 2010
Exchange 2003
Stream-based backups
NetBackup versions 7.0 and higher
NetBackup versions lower than 6.5.3
To start, we need to work on the Exchange 2007 server we are restoring to, in order to create the Recovery Storage Group (RSG). Because we are creating the RSG on an alternate client, we cannot use the Exchange Management Console to create it. Instead we need to run a series of commands from the Exchange Management Shell. Your syntax will vary from that used here. To find the correct syntax for your environment, please see your Exchange administrator.
First we run the New-StorageGroup command to create the RSG:
New-StorageGroup -Server "<destination server>" -Name "<name of RSG>" -LogFolderPath "<valid path on destination server>" -SystemFolderPath "<valid path on destination server>" –Recovery
Then we run the New-MailboxDatabase command to add the mailbox database we want to restore
New-MailboxDatabase -MailboxDatabaseToRecover "<original storage group>\<mailbox database name>" -StorageGroup "<destination server>\<name of RSG>" -EdbFilePath "<file path for the *.edb file including the file name itself>"
The database in the RSG should already be dismounted, and the flag to allow the database to be overwritten by a restore, should already be set. We can confirm the RSG database status by running the following command in the Exchange Management Shell:
Get-MailboxDatabase -Identity "<Name of RSG>\<Mailbox Database Name>" -Status | format-table Name,Recovery,Mounted,AllowFileRestore
No other steps should be required, and Exchange is now ready for the restore.
After preparing the client, we will bring up the master/media server for this demonstration and go into the Backup, Archive, Restore (or BAR) GUI. We start by going to the File menu and click on Specify NetBackup Machines and Policy Type   
In the resulting window, we set the source as the Exchange 2007 cluster and the destination as the Exchange 2007 stand alone server. In this example, we are restoring to an Exchange 2007 stand alone server, however, if we were restoring to a different Exchange 2007 cluster we would need to be sure to use the Exchange 2007 cluster virtual host name of the alternate server as the destination. We also set the policy type to MS-Exchange-Server. We click OK on the Specify NetBackup Machines and Policy Type window.
Next, we click on the Select for Restore button. Initially, we see the backup images in a Timeline view. It doesn't provide much information about each backup, fulls are green and differentials are blue. It is recommended to go to the View menu and deselect the Show NetBackup History as a Timeline setting as we are doing here to get more information about each backup, including the specific time backed up. To select multiple images for restore, we click on the full backup we want to restore and then, holding down the <shift> key, we select the differential image up through which we want to restore. This will select the full image and all differential images we want to restore through.
Next, in the All Folders pane in the BAR GUI, we drill into the Information Store and click on the storage group that we want to restore the database from.
It is important to note that with NetBackup 6.5, there is a caveat regarding how to select the files for restore, when restoring a snapshot backup to an RSG for Exchange 2007. This also only applies for a restore that contains a full backup image, as well as one or more incremental backup images. Instead of selecting the individual database and log files in the right pane, we should select the checkbox for the original storage group itself in the All Folders pane. We can see that there is a visual difference in how the selection looks, depending on how we select the files. If we select individually in the right pane, each item has a checkmark and the storage group shows a slash next to it. When we select the storage group itself in the left-hand pane, the storage groups has a checkmark next to it instead of a slash. The individual items appear the same as before and again show checkmarks. If the selection is done incorrectly for this type of restore in NetBackup 6.5, the restore will be successful for the full backup image, but will fail when trying to restore from subsequent incremental images. 
This is the error we would see in both, the Detailed Status tab of the restore job in the Activity Monitor, as well as in the View Status output from the BAR GUI. In another Exchange 2007 environment, the storage group name and ctime stamp in the file representing the transaction log files will, of course, differ. The BEDS error code and error message will be the same, however.
"ERR - error writing Exchange object: Microsoft Information Store:\Admin Storage Group\Logs_1286381760 Error: BEDS 0xE000FEE5: A failure occurred restoring because the files cannot be replaced and no alternate location was specified."
Once we've marked all the files we want restored, we click on the second icon down on the left-hand toolbar, which is the Start Restore of Marked Files   This brings up the Restore Marked Files dialog. We click on the Microsoft Exchange tab. We see two options for replaying log files, Roll-Forward Recovery and Point-in-time recovery   With the Point in Time recovery option, only the logs being restored are replayed. The Roll-Forward recovery option will replay all restored logs, but will then continue to roll forward any other log files that may exist on the system since logs were last truncated. Since we are restoring to an RSG, there will be no other log files on the Exchange server to roll forward, so we will do just the point-in-time recovery.
The Temporary location for log files setting is unavailable, as it is unnecessary for an Exchange 2007 database restored from a snapshot backup.
We see a Dismount database prior to restore option. The database in the RSG is dismounted by default, so this option should remain deselected. Please note that anytime a database needs to be dismounted, it is recommended that dismounting be done from either the Exchange Management Console or Exchange Management Shell. This ensures that the correct database is dismounted. Using the option here only could result in the wrong database being dismounted and overwritten, if the restore does not use the intended storage group and database destination.
The next two options are Commit after last backup set is restored which tells Exchange to recover the database after we restore the full and all log files, and Mount Database after restore  which will actually mount the database after it is recovered. These are both selected by default. However, please check with your Exchange Administrator to ensure they are appropriate actions at the end of your restore. 
The last option, Redirect to Recovery Storage Group (Only for Exchange 2007)  as the name implies, is for Exchange 2007. It is only available for a restore from a snapshot backup, such as the CCR passive node backup in this example so we will go ahead and check it. 
With the last option checked, there are no applicable settings under the General tab so we will click the Start Restore button. A message will appear indicating the restore has successfully initiated. We click Yes to see the View Status window.
In the Activity Monitor of the NetBackup admin console, we see the restore job and can double-click on it to see detailed status. In the Detailed Status tab, we can see some further information about the progress: connecting to the client, starting the bptm process to read from the images. For this demonstration, we should see 3 sub-jobs start as part of Job ID 367, namely we should see 3 different restores, one for the full and two for the two differentials.
If we go back to the BAR GUI’s view status window, we will see similar information. We also see that there are messages about remaining jobs. After the first job, it said there were two jobs remaining and, therefore, recovery would be deferred. When we had one job remaining, recovery was still being deferred. After the last differential, it says there were no jobs remaining and recovery will be performed. We can see here after the last differential, there is a status 0. 
Looking in Activity Monitor, we also see the job with a blue man and a status 0. On a restore, any final status other than 0 should be considered an unsuccessful restore and the cause should be investigated and the restore retried.
We go back to the destination client and confirm that the database in the RSG is now mounted after the successful restore, by running the following command in the Exchange Management Shell:
Get-MailboxDatabase -Identity "<Name of RSG>\<Mailbox Database Name>" -Status | format-table Name,Recovery,Mounted,AllowFileRestore
Length: 10:51
The video can be viewed by clicking on the following link:


Microsoft Exchange 2007 Management Shell Cmdlet reference:



Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)