VIDEO: NetBackup Support Screencast Demo: Configuring Exchange 2003 and Exchange 2007 Granular Restore Technology (GRT) backups with NetBackup 6.5 and 7.0

Article:HOWTO41843  |  Created: 2011-01-19  |  Updated: 2013-10-24  |  Article URL http://www.symantec.com/docs/HOWTO41843
Article Type
How To



The video linked to is a part of the NetBackup Support Screencast Demo Video series.  It demonstrates Configuring Exchange 2003 and Exchange 2007 Granular Restore Technology (GRT) backups with NetBackup 6.5 and 7.0
 
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 Exchange 2003 and Exchange 2007 Granular Restore Technology (GRT) backups with 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 and another media server running NetBackup 7.0.1 on Windows 2008 R2. We have an Exchange 2003 client running NetBackup 7.0.1 on Windows 2003 R2 SP2. It is not clustered. We also have an Exchange 2007 client running NetBackup 7.0.1 on Windows 2008 R2. It 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.
 
This video does not apply to:
Exchange 2010
 
This demonstration has a prerequisite that the Exchange Information Store backup has already been configured.
 
Also, please note that Exchange GRT backups only support a Full backup schedule type. Incremental backups, such as Differential and Cumulative, are not currently supported.
 
The GRT process also utilizes MAPI for Exchange 2003 and Exchange 2007. While Exchange 2003 does have MAPI already installed, Exchange 2007 does not have MAPI installed by default. It may be necessary to download and install the latest Microsoft Exchange Server MAPI Client and Collaboration Data Objects package. This can be obtained from the following link for Microsoft downloads:
http://www.microsoft.com/downloads/
 
Since Exchange 2007 is running on a cluster for this example, the MAPI package has been installed on each cluster node.
 
In order for GRT to work correctly, the storage unit configured on the media server must be disk based. This table shows disk based storage unit compatibility with GRT:
Disk storage unit                            Granular Recovery supported
-----------------                                     ---------------------------
BasicDisk                                                    Yes
AdvancedDisk                                            Yes
NearStore                                                     No
OpenStorage                                               No
PureDisk                                                      No
SharedDisk                                                  No
SnapVault                                                    No
 
By default, the NetBackup Client Service uses the Local System account to log on. NetBackup requires a different account on the clients to perform backups or restores of individual mailboxes and folders and items in the public folders. We need to change the service account to a Windows domain account that was previously created. This account must have local administrative privileges, as well as top-level administrative rights in Exchange. It must also have a mailbox that has been initialized and is not hidden. For this example, the Exchange 2003 server and Exchange 2007 cluster nodes have been configured so that the NetBackup client service is running as a service account called "netbackup".
 
We also need to make sure the clients are configured with the service account mailbox. This needs to be done for each client host and cluster node. For this example, we will configure the service account mailbox for the Exchange 2003 server, as the Exchange 2007 cluster nodes have already been configured. In the NetBackup administration console on the master server, we click on Clients under Host Properties. We double-click on the Exchange 2003 client to bring up the Client Properties dialog. We expand Windows Client settings and click on Exchange. Under Mailbox for message level backup and restore, we enter the name of the service account mailbox. We click OK to save those settings.
 
For GRT to work properly, we need to install and configure certain NFS components on the Windows media servers being used for the backup, as well as the clients. On Windows platforms for either the media server or the client, the Windows version must be 2003 R2 SP2 minimum for NFS stability and compatibility with GRT. Other supported media server platforms are shown here:
* AIX 5L
* HP-UX HP 9000 PA-RISC
* HP-UX HP Integrity (IA-64)
* RedHat Enterprise Linux
* Solaris SPARC
* SUSE Linux Enterprise Server
 
For these platforms, we will not be covering the specifics of NFS configuration. Although NFS is typically setup for these operating systems already, it is recommended that this be confirmed by your system administrator.
 
NFS Configuration on the Exchange 2003 client
We will work on the NFS configuration on the Windows 2003 R2 hosts. First, we will look at the Exchange 2003 server running on Windows 2003 R2 SP2. 
We click on the Windows Start menu, then Control Panel, and then Add or Remove Programs
Under the Add or Remove Programs dialog, we click on the Add/Remove Windows Components button and this will bring up the Windows Components Wizard dialog. 
Under Components we scroll down, click on Other Network File and Print Services to highlight it, and then click on the Details button. 
Under Subcomponents of Other Network File and Print Services we click on Microsoft Services for NFS and then click the Details button again. 
Under Subcomponents of Microsoft Services for NFS we check the checkboxes for Client for NFS, Microsoft Services for NFS Administration, and RPC External Data Representation
We then click OK, then OK again, then click Next
 
For the NFS components to install properly, it may be necessary to have the Windows 2003 R2 media loaded in the CD-ROM drive. After the NFS components install, we click Finish and then close the Add or Remove Programs dialog.
For the Windows 2003 R2 SP2 client hosts, it is also necessary to install the Microsoft hotfix for Client for NFS. The hotfix information is shown here.
 
NFS Configuration on the Windows 2003 master/media server
Next, we will configure NFS on the master/media server running on Windows 2003 R2 SP2. We will perform the same actions on the master/media server for the NFS components install, however we will select different components. Under Subcomponents of Microsoft Services for NFS we check the checkboxes for both RPC External Data Representation and RPC Port Mapper. We then click OK, then OK again, then Next. After the NFS components install, we click Finish and then close the Add or Remove Programs dialog. To configure the portmap service to start automatically at server restart, open a command prompt and issue the command shown:
sc config portmap start= auto
This command should return the status "[SC] ChangeServiceConfig SUCCESS".
 
NFS Configuration on the Windows 2008 R2 Exchange client
Next, we will configure the Windows 2008 R2 hosts, starting with the Exchange 2007 server. Since Exchange 2007 is clustered, this will need to be done on both nodes. For this example, the NFS configuration has already been done on the passive node, so we will demonstrate the install on the active node. 
We click on the Windows Start menu, then Administrative Tools, and then Server Manager
Under Server Manager we click on Roles on the left-hand side. 
Under Role Services, we see the File Server is already installed so we click on Add Role Services to bring up the Select Role Services dialog. 
We check the checkbox for Services for Network File System, then click Next, and then click Install
After the service install, we click Close
For the NFS services on the client, we need to disable the Server for NFS service. 
In the System Manager, we expand Configuration and click on Services
We scroll down to find Server for NFS
We right-click on the service and select Stop
We right-click on the service again and choose Properties
Under the General tab we change Startup type to Disabled and then click OK
Now we close Server Manager.
 
Next, we will configure NFS on the media server running on Windows 2008 R2. 
We click on the Windows Start menu, then Administrative Tools, and then Server Manager
Under Server Manager we click on Roles on the left-hand side, and then Add Roles in the right-hand pane which brings up the Add Roles Wizard
We click the Next button, then check the checkbox for File Services, and click Next two more times. 
Under Select Role Services, we check the checkbox for Services for Network File System
We can also uncheck File Server since it was previously uninstalled and we do not need to install it for this configuration. 
We then click Next, and then click Install
 
After the service install, we click Close
 
NFS Configuration on the Windows 2008 R2 Media Server
For the NFS services on the media server, we need to disable both the Client for NFS and Server for NFS services as only the portmap service component of the NFS services is required on the NetBackup media server. In the System Manager, we expand Configuration and click on Services. We perform the same steps as we did on the Exchange 2007 server to disable these services. Now we close Server Manager. Once again, to configure the portmap service to start automatically at server restart we issue the command shown from the command prompt:
sc config portmap start= auto
This command should return the status "[SC] ChangeServiceConfig SUCCESS".
 
Altnames File Creation
A necessary step in GRT processing is the client mounting the backup image via NFS on the media server. Since we are backing up an Exchange 2007 cluster, we need to make sure that either cluster node can access the backup image under the Exchange 2007 virtual host name. This is done by creating simple text based files in a specific directory on the NetBackup master server. For this example the path in which to create these files is:
C:\Program Files\Veritas\NetBackup\db\altnames
The altnames directory does not exist by default, so you may need to create it. The contents of the altnames directory are simple text files, whose file names are the hosts that need permission to access NetBackup backup images other than their own. The file names of these files should not have any file extensions. The contents of each file are one or more hosts to whom the backup images belong. For this example, we create two files, one for each Exchange 2007 cluster node. The contents of each file will be the same, the Exchange 2007 virtual host name. If you create these files with a text editor, the text editor may append an extension such as .txt to the filename. This extension must be removed in order for NetBackup to recognize the file. Please be aware that for most Windows installations, the default configuration is to have file extensions hidden for known file types. This will cause some file extensions such as .txt or .doc to not appear in the file name. If you have this configured, please unhide file extensions and delete the file extensions associated with these files.
 
Policy modification to enable GRT
The last step is to configure the policies for GRT. In the NetBackup administration console, under Policies, we double click on the policy we want to enable GRT for. Under the Attributes tab of the Change Policy dialog, we check the checkbox for Enable granular recovery, and then click OK to save the changes. Once this is done for each policy we want to modify, we will run a manual backup for each policy.
 
Running a backup
For each policy, we right click on the policy, and choose Manual Backup which brings up the Manual Backup dialog box. Then 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 activity for the Information Store backups. 
 
And 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 investigated.
 
If the Information Store backup was successful, but the GRT portion of the backup had a problem, the backup job will end with a status 1. If GRT is found to be the cause of the status 1, the backup may be usable for database restores, but not granular restores. Any other final status should be considered an unsuccessful Exchange backup and should not be relied upon for a restore.
 
Time:13:17
 
The video can be viewed by clicking on the following link: www.symantec.com/tv/products/details.jsp



Article URL http://www.symantec.com/docs/HOWTO41843


Terms of use for this information are found in Legal Notices