The video linked to is a part of the NetBackup Support Screencast Demo Video series. It demonstrates Performing an Exchange 2007 Snapshot/Cluster Continuous Replication (CCR) Database Restore to a Recovery Storage Group (RSG) on an Alternate Client using NetBackup 7.0
TRANSCRIPT OF VIDEO:
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 http://education.symantec.com 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/Cluster Continuous Replication (CCR) Database Restore to a Recovery Storage Group (RSG) on an Alternate Client using NetBackup 7.0
Ffor this demonstration, we will be using a master/media server running NetBackup 7.0.1 on Windows 2003 R2 SP2. The backup was done from the passive node of an Exchange 2007 cluster configured for CCR, running NetBackup 7.0.1 on Windows 2008 R2, and we will be restoring to an Exchange 2007 stand alone server running NetBackup 7.0.1 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.
This video does not apply to:
NetBackup versions prior to 7.0
Restores to the original location/client
To start, we need to work on the Exchange 2007 server we are restoring to, 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.
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. This does not provide much information about each backup, fulls are green and differentials are blue. It is recommended to go to the View menu and deselecting 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 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 successive 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. 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 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 such as 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 586, 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 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. 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
Microsoft Exchange 2007 Management Shell Cmdlet reference: