VIDEO: NetBackup Support Screencast Demo: Restoring an Exchange 2007 Snapshot/Cluster Continuous Replication (CCR) Backup Using NetBackup 6.5 and 7.0


The video linked to is a part of the NetBackup Support Screencast Demo Video series.  It demonstrates Restoring an Exchange 2007 Snapshot/Cluster Continuous Replication (CCR) Backup Using NetBackup 6.5 and 7.0.

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 Restoring an Exchange 2007 Snapshot/Cluster Continuous Replication (CCR) Backup Using NetBackup 6.5 and 7.0.
For this demonstration, we will be using a master/media server running NetBackup 7.0.1 on Windows 2003 R2 SP2. The Exchange 2007 is client running NetBackup 7.0.1 on Windows 2008 R2. The Exchange 2007 server is clustered and configured for CCR. Although we will be using NetBackup 7.0.1, the interface and configuration settings are the same for NetBackup 6.5, so the information presented here can be applied to a NetBackup 6.5 environment as well.
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
·         Stream-based backups
·         NetBackup versions prior to 6.5
To start, we need to work on the Exchange 2007 cluster active node to suspend replication and dismount the database we are going to restore. In the Exchange Management Console, we click on Mailbox under Server Configuration and click on the mailbox server in the upper middle pane that contains the Storage Group and database we want to restore. Now we click on the Storage Group in the lower middle pane that contains the database we want to restore, and then click Suspend Storage Group Copy under actions.
We click Yes to confirm suspending replication. The copy status will then change from Healthy to Suspended. Now we click on the database and click on Dismount Database under actions. We click Yes to confirm dismounting the database and we see the copy status of the database is now Dismounted. We then click Properties under actions for the dismounted database, and under the General tab we click the checkbox for This database can be overwritten by a restore setting and then click OK. 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 and the destination to be the Exchange 2007 cluster virtual host name. We also set the policy type to MS-Exchange-Server.
We using the BAR GUI on the master server, although we could also be using it on a NetBackup remote administration console host. With either method, we can see the destination client field is available to be set to a specific host. However, if we were using the BAR GUI on the active node of the Exchange 2007 cluster, the destination client field would not be visible and the hostname of that cluster node is automatically used as the destination client name. The destination client name used by NetBackup for the restore would then be the physical node name of the client. If the physical node name is used by NetBackup when talking to the Exchange restore API, no Exchange server will be found and the restore will fail. However, to properly perform the restore, the virtual name of the Exchange cluster is the one that needs to be specified for the restore within NetBackup. Therefore, if you are restoring a database on a clustered Exchange server, you must use the BAR GUI on a master server or Remote Administration Console and specify the virtual name of the Exchange cluster as the destination client.
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. This 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 in order 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 database that we want to restore. Then, in the lower right-hand pane, we click the checkboxes for the database and log files we want to restore. Differential backups will back up the transaction logs and then truncate. Thus, they only contain the logs since the most recent full or differential backup. This is why we selected 2 log file backups in addition to the logs from the full backup, because each one was a differential backup and truncated the logs after it was complete. No cumulative backups are shown here, but note that they do not truncate logs. Because of this, they contain all log files since the last full backup. They have the disadvantage of each successful cumulative backup being larger because it includes all logs since the last full, whether those logs had been backed up before or not. However, the benefit is that in a restore, you only need to select the full backup and the most recent cumulative backup.
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 with rolling forward any other log files that may exist on the system since logs were last truncated. For this demo, we will choose 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. We have already dismounted the database we are restoring, 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. Since we are restoring the database back to its original location, and not to a Recovery Storage Group, we will leave this unchecked. 
Since we are restoring back to the original storage group and database we do not need to change any 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 administration console, we see the restore job and can double-click on it to see detailed status. In the Job Overview tab we can see our database and the log files from the full and two differentials. In the Detailed Status tab, we can see some further information about the progress: connecting to the client and starting the bptm process to read from the images. For this demonstration, we should see 3 sub-jobs start as part of Job ID 583, 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. For instance we can see that we have a status 0 on the full with 4 of 4 files successful. The next job is the differential with a status 0 and 3 of 3 files successful and we see that the final differential has completed as well. 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. And 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 that the job has 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 client and look at the Exchange Management Console. The restored database appears to be dismounted, but when we click on Refresh under Actions, the status is updated to reflect that the database is mounted. We also click on the storage group for the database in a Suspended status, then resume replication by clicking on Resume Storage Group Copy under actions, and then clicking Yes on the confirmation dialog. We also click on Refresh again under Actions to see the copy status updated. Depending on the restore scenario, it may be necessary to update the database copy instead of resuming replication, although we are not doing that here. Again, please check with your Exchange Administrator to ensure the appropriate actions at the end of your restore.
Time: 11:02

The video can be viewed by clicking on the following link:

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)