The video linked to is a part of the NetBackup Support Screencast Demo Video series. It discusses Configuring Information Store Backups for Exchange 2007 Cluster Continuous Replication (CCR) Systems with NetBackup 6.5
The video can be viewed by clicking on the following link: www.symantec.com/tv/products/details.jsp
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 Configuring Information Store Backups for Exchange 2007 Cluster Continuous Replication (CCR) Systems with NetBackup 6.5.
For this demonstration, we will be using a master/media server running NetBackup 6.5.6 on Windows 2003 R2 SP2 and an Exchange 2007 client running NetBackup 6.5.6 on Windows 2008 R2. The Exchange 2007 server is clustered and configured for CCR. For this demo will be focusing on backing up the database replicas on the Exchange 2007 cluster passive node.
This video does not apply to:
· Exchange 2010
· Exchange 2003
· Non-CCR systems
· NetBackup 7.0 or higher
· NetBackup versions prior to 6.5
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.
First, we need to make sure that the NetBackup client service running on each client node is running as an account that has the correct permissions to backup the Exchange Information Store databases. For this video, the NetBackup client service is running as the default installed Local System Account. If a specific service account is needed for the NetBackup client service, we would need to make sure that account has Local System Admin privileges, as well as the proper Admin privileges in Exchange in order to be able to backup IS databases.
Now we will go ahead and configure a policy for the Information Store backup of the Exchange 2007 client. We will bring up the NetBackup administration console, right click on Policies, and choose New Policy. This will bring up the Add a New Policy dialog and we will use the name "Exchange_CCR_IS_backup" for the purposes of this demonstration. We are going to keep the option to use the wizard unchecked, and click OK. This will bring up the Add New Policy window where we will configure the new policy.
We will start with the Attributes tab. We will choose MS-Exchange-Server under the Policy type. Under the Policy storage unit/lifecycle policy drop down, we will choose "DSU" for the Disk Storage Unit that had been configured earlier for this example. We will also check the check box for the Allow multiple data streams option, which will be explained further when going over the backup selection.
Under Snapshot Client we will check the check box for the Perform snapshot backups option, and then click the Snapshot Client Options button which will bring up the Snapshot Client Options dialog box. Under the Snapshot method dropdown, we will choose VSS. The default settings under Configuration Parameters should normally be sufficient. Depending on the storage used for the Exchange databases, the NetBackup client may have a hardware provider VSS writer. By default, the hardware provider VSS writer is used for the snapshot. If this is not desired, then the Provider Type setting under Configuration Parameters should be changed from 0, which is the "auto" setting, to 1, which specifies the "system" setting. We click OK to save the snapshot settings.
Next we will click on the Schedules tab to create the appropriate schedule for a full backup. We click the New button to bring up the Add New Schedule window. Under Name we are going to use "Full" as the name for this schedule for demonstration purposes. Under the Type of backup, we will leave the Full Backup type.
The four backup types are as follows:
· Full Backup which backs up the Exchange databases and transaction logs and will then have Exchange truncate the logs after a successful backup.
· Differential Incremental Backup which backs up Exchange transaction logs only and will then have Exchange truncate the logs after a successful backup.
· Cumulative Incremental Backup, which also backs up Exchange transaction logs only but will not have Exchange truncate the logs after a successful backup; and
· User Backup which will allow an Exchange backup to be initiated from the client during an open Start Window.
Please note that an Exchange 2007 CCR passive node backup cannot be done using a User Backup schedule.
We will leave the rest of the settings at their default, and will not be configuring a Start Window for the Full Backup schedule as we will be running the backup manually for this example. Both the Start Window and Exclude Dates settings do not need any Exchange specific settings, so those will not be covered further. Now we click OK to save the Schedule settings.
Next we will click on the Clients tab to add Exchange 2007 client to the policy. We click on New and then enter the client name. For the Exchange 2007 client, it is important to remember to use the clustered Exchange 2007 virtual host name and not the host name of the Windows 2008 active cluster node it is running on. If the node name is used instead of the virtual host name, NetBackup will use the node name when talking to the Exchange backup API. Since there is no Exchange 2007 server configured using that node name, the Exchange 2007 server will not be found and the backup will fail with a status code 69. After we enter the Exchange 2007 virtual host name, we hit the Enter key on the keyboard, and the Hardware and Operating System columns are automatically populated.
Next we click on the Backup Selections tab to configure the backup selection for the policy. We will click the New button to enter a backup selection, and then the button to the very right of the backup selection that looks like a hand pointing to the right. This will bring up the Select Directive dialog. Under the Directive set drop down we will leave the "MS_Exchange_200x" setting, and under the Directive drop down we will choose "Microsoft Information Store:\", and then click OK.
It is also recommended that an asterisk be entered at the end of the "Microsoft Information Store:\" directive. We will do that here, and then hit the Enter key. Using the asterisk wildcard in this way, along with the checked Allow multiple data streams under the Attributes tab, will allow each Storage Group to run as its own backup job. This is recommended because it may increase the overall performance of the Exchange backup. Since backup performance, however, is greatly dependant on the environment this can not be guaranteed. Now we click OK to save the policy.
Before we run the backup, we are going to go over some Exchange specific settings for the NetBackup client. In the NetBackup administration console, we click on Clients under Host Properties. We will need to check these settings on each node. For the active node, we double click on the Exchange 2007 virtual host name to bring up the Client Properties dialog. We expand the Windows Client settings and click on Exchange. Under Backup option for log files during full backups, we need to make sure that Back up all log files is selected, as that is the recommended setting for backing up replication environments such as CCR.
Under the Exchange 2007 replication backup setting, we will keep the default setting Backup the passive copy and if not available backup the active copy. There are also settings for Backup the passive copy only and Backup the active copy only if there is a backup scenario that calls for those specific settings. We click OK to save those settings.
We also need to confirm the same settings on the passive node. Since the passive node host name is not in the list of clients, we need to click on Actions and then Configure Client to bring up the Choose Client dialog. We enter the passive node host name and click OK to bring up the Client Properties dialog for the passive node. Once we have confirmed the same Exchange-specific settings for the passive node, we click OK to set the settings.
Now we will go ahead and run the backup. We right click on the newly created policy, and choose Manual Backup which brings up the Manual Backup dialog. Now we click OK to start the backup, and OK again for the popup notification that a backup has started. We click on Activity Monitor and can see a multiple stream parent job. When we double-click the parent job and then click the Detailed Status tab, we can see the snapshot activity.
After the snapshot completes on the client we will see a backup job for each Storage Group launch, although depending on the Exchange environment this can take several minutes.
Here we see the backup jobs have completed successfully, each with a blue man and a status 0. Any final status other than 0 should be considered an unsuccessful Exchange backup and the cause should be investigated. Such a backup cannot be relied upon for a restore.
This video can be viewed by clicking on the following link: www.symantec.com/tv/products/details.jsp