VIDEO: NetBackup Support Screencast Demo: Configuring Exchange 2010 Granular Restore Technology (GRT) Backups with NetBackup 7.0

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


Subject


The video linked to is a part of the NetBackup Support Screencast Demo Video series.  It demonstrates Configuring Exchange 2010 Granular Restore Technology (GRT) Backups with NetBackup 7.0.

 
The video can be viewed by clicking on the following link: Configuring Exchange 2010 Granular Restore Technology (GRT) Backups with 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 Exchange 2010 Granular Restore Technology (GRT) Backups with NetBackup 7.0.
 
For this demonstration, we will be using a master/media server running NetBackup 7.0.1 on Windows 2003 R2 SP2, a media server running NetBackup 7.0.1 on Windows 2008 R2, an Exchange 2010 stand-alone server running NetBackup 7.0.1 on Windows 2008 R2 SP2, and an Exchange 2010 DAG whose members are running NetBackup 7.0.1 on Windows 2008 R2.
 
The Exchange 2010 stand alone server is also the Client Access Server (CAS) server for this environment. If the CAS server were a separate Exchange 2010 server, however, the same client host changes described in this demonstration would also need to be made on that server.
 
This video does not apply to:
Exchange 2003
Exchange 2007
NetBackup versions prior to 7.0
 
NFS and GRT
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 listed 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.
 
In order for GRT to work correctly, the storage unit configured on the media server must be disk based. The types of storages units that support GRT and that do not support GRT are shown here:
 
Disk storage unit      Granular Recovery supported
-----------------   ---------------------------
BasicDisk                  Yes
AdvancedDisk                      Yes
NearStore                  No
OpenStorage                        No
PureDisk                   No
SharedDisk               No
SnapVault                 No
 
Service Accounts for NetBackup
By default, the NetBackup Client Service and NetBackup Legacy Network Service both use Local System as the account on which to log on. A different account is required on the clients to perform backups or restores of individual mailboxes and folders and items in the public folders.
 
Thus, we will 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. For this example, the Exchange 2010 stand alone server and Exchange 2010 DAG members have been configured such that both NetBackup client services are running as a service account called "backupadmin".
 
We also need to make sure the clients are configured with the service account mailbox. In the NetBackup administration console on the master server, we click on Clients under Host Properties. This will need to be done for each client host. For this demonstration, we will configure the service account mailbox for the Exchange 2010 stand alone server, as the Exchange 2010 DAG members have already been configured by us.
 
We double-click on the client host to bring up the Client Properties dialog. We expand the Windows Client settings and click on Exchange. Under Mailbox for message level backup and restore, we will enter the name of the service account mailbox. We click OK to save those settings.
 
NFS configuration on the Windows 2003 master/media server
Next, we will work on the NFS configuration on the master/media 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 and click on Other Network File and Print Services to highlight it, and then click on the Details button. Then, click on Microsoft Services for NFS and click Details. Under Subcomponents of Microsoft Services for NFS we check the checkboxes for both RPC External Data Representation and RPC Port Mapper. We click OK, then OK again, then 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. To configure the portmap service to start automatically at server restart we issue the following from the command prompt:
sc config portmap start= auto
This command should return the status "[SC] ChangeServiceConfig SUCCESS".
 
Configuring NFS on the Clients
Next, we will configure the Windows 2008 R2 hosts, starting with the Exchange 2010 servers. For this example, the NFS configuration is already done on the DAG members, so we will demonstrate the install on the stand alone server.
 
We click on the Windows Start menu, then Administrative Tools, and then Server Manager. Under Server Manager we click on Roles on the left. 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, 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 that service and choose 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.
 
Configuring NFS on the Windows 2008 Media Server
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, and then Add Roles in the right pane which brings up the Add Roles Wizard. We click the Next button, then check the checkbox for File Services, and then 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. 
 
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 2010 servers 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 following from the command prompt:
sc config portmap start= auto
This command should return the status "[SC] ChangeServiceConfig SUCCESS".
 
NetBackup Distributed Application Restore Mapping
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 2010 DAG, we need to make sure that each DAG member can access the backup image under the Exchange 2010 DAG name. We can be done by configuring Distributed Application Restore Mapping on the master server to create a relationship between the DAG virtual host name, and the physical Exchange server host names of the DAG members.
 
On the master server, we open the NetBackup admin console, go to Host Properties, then Master Servers. In the right pane, we double-click on the master server to bring up the Master Server Properties dialog. We click on Distributed Application Restore Mapping and then click the Add button. Under Application host we put the DAG virtual host name, and under Component host we put the physical host name of the DAG member, and then click the Add button. We do this for both DAG members, then click the Close button, and then the OK button to close the Properties dialog. We see a popup message that the NetBackup services may need to be restarted, but for this change a restart is not necessary.
 
Policy Configuration
The last step is to configure the policies for GRT. In the NetBackup admin 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 the backup
For each policy, we right-click on the 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 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 code 1. If GRT is found to be the cause of the status code 1, the backup will be usuable for database restores, but not for granular restores.
 
Any other final status codes should be considered an unsuccessful Exchange backup and should not be relied upon for a restore.
 
Length: 11:24
 
The video can be viewed by clicking on the following link: Configuring Exchange 2010 Granular Restore Technology (GRT) Backups with NetBackup 7.0



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


Terms of use for this information are found in Legal Notices