The video linked to is a part of the NetBackup Support Screencast Demo Video series. It demonstrates Configuring Stream-Based Backups on Exchange 2003 and 2007 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 Configuring Stream-Based Backups on Exchange 2003 and 2007 using NetBackup 7.0.
Please note that for this demonstration, we will be using a master/media server running NetBackup 7.0.1 on Windows 2003 R2 SP2. We have a client that is an Exchange 2003 server running NetBackup 7.0.1 on Windows 2003 R2 SP2, and a second client running Exchange 2007 with NetBackup 7.0.1 on Windows 2008 R2. The Exchange 2003 server is a stand-alone server, and the Exchange 2007 server is clustered and configured for CCR. Since this is a stream-based backup, we will be backing up the active node of the Exchange 2007 cluster.
This video does not apply to:
· Exchange 2010
· Snapshot-based Backups
· NetBackup versions lower than 7.0
First, we need to make sure that the client service running on the client 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 Information Store databases.
Now we will go ahead and configure a policy for the Information Store backup of the Exchange 2003 client and 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 "Exchange_IS_backup" as the policy name. 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 choose "MS-Exchange-Server" under Policy type. Under the Policy storage drop down, we will choose "DSU" for the Disk Storage Unit that has 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.
We will also leave the Perform snapshot backups option unchecked under the Snapshot Client portion of the dialog, as we are configuring a streams-based backup.
Now 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 of this schedule. 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 then will 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 does 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.
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 the Exchange 2003 and Exchange 2007 clients to the policy. We click on New... and then enter the client name. The Exchange 2003 stand alone server is configured as the same host name as the Windows 2003 server it is running on, so we will use that host name here. After we enter the host name, we hit the <Enter> key on the keyboard, and the Hardware and Operating System columns are automatically populated.
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 the node name, the Exchange 2007 server would not be found and the backup will fail. We hit the <Enter> key again after entering the Exchange 2007 virtual host name and the operating system and hardware are automatically populated.
Now we will 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 at 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_Database" 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 if a single Storage Group backup fails for any reason, the other Storage Group backups can still run successfully and the transaction logs for those Storage Groups should still be truncated. NetBackup will not have Exchange truncate logs for any Storage Group backup that fails, and if more than one Storage Group are in a backup job, all Storage Groups will be affected, even if only one of the Storage Group backups had failed. Having each Storage Group in its own backup job may also increase the overall performance of the Exchange backup. However, since backup performance is greatly dependant on the environment factors, this cannot be guaranteed. Now we click OK to save the policy.
With the policy created, it is time to 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 starting for each Exchange server, as well as a backup job for each Storage Group on each Exchange server.
And here we see the backup jobs have completed successfully, each with a blue man and a status code 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.
The video can be viewed by clicking on this link: www.symantec.com/tv/products/details.jsp