HP OpenView Storage Data Protector

Transcription

1 HP OpenView Storage Data Protector Backup and Restore Of Tru64 Cluster Server Version 1.3 Backup and Restore of Tru64 Cluster 1

2 1. Introduction Overview of Tru64 Cluster Installing Data Protector Agents on Tru64 Cluster Local Installation Remote Installation Configuring Data Protector in a Tru64 Cluster Importing Cluster to the Data Protector Cell Configuring Media Agent for failover Backing Up & Restoring Data in the Cluster Backup Filesystem Backup: Oracle Online Backup: SAP Backup Restore Filesystem Restore: Oracle Restore: SAP Restore:...10 Backup and Restore of Tru64 Cluster 2

3 1. Introduction This Whitepaper provides a guideline for how to configure HP OpenView Storage Data Protector for backup/restore of a HP Tru64 Unix Cluster. The cluster software that we are addressing is TruCluster Server Version 5.x. It describes the steps necessary for the installation and configuration of Data Protector 5.1 and 5.5 in this type of an environment. It also provides basic guidelines in configuration of Tru64 Cluster as a Media Agent. Performance is not a focus of this Whitepaper as it only describes the concepts of this type of backup. The Whitepaper starts with an overview of a Tru64 Cluster. Then it covers the installation of HP OpenView Storage Data Protector 5.1 and 5.5 in a Tru64 Cluster. It explains the procedure used for configuring Data Protector to be able to perform backup/restore of the data on the cluster. Backup and Restore of Tru64 Cluster 3

4 2. Overview of Tru64 Cluster TruCluster Server Version 5.1 is a highly integrated synthesis of Tru64 UNIX software, AlphaServer systems, and storage devices that operate as a single virtual system. Members of the cluster can share resources, data storage, and clusterwide file systems under a single security and management domain, yet they can boot or shut down independently without disrupting the cluster s services to clients. A TruCluster Server environment can be as simple or as feature-rich as you require. You configure a cluster that fits your needs, from a two-node cluster up to an eightnode cluster running high availability applications such as transaction processing systems, servers for network client/server applications, data-sharing applications that require maximum uptime, and distributed parallel processing applications that take full advantage of the TruCluster Server application programming interfaces (APIs). TruCluster Server includes a cluster alias for the Internet protocol suite (TCP/IP) so that a cluster appears as a single system to its network clients and peers. The figure below shows a typical Tru64 Cluster setup involving two nodes: Backup and Restore of Tru64 Cluster 4

5 3. Installing Data Protector Agents on Tru64 Cluster To back up a Tru64 Cluster, Data Protector has to be installed one time on the shared disk and the cluster has to be imported to the Data Protector cell including the individual nodes in the cluster. NOTE: Data Protector has to be installed on the shared Disk (/usr/omni) within a cluster in order to import the cluster & nodes in the cell. Following are the steps that need to be followed in order to install Data Protector in a Tru64 Cluster: NOTE: You must have root permissions on every target system Local Installation In case there is no Unix Installation Server in the Data Protector cell then the Data Protector Agent(s) for Tru64 need to be installed locally on the shared disk (/usr/omni) using one of the nodes in the cluster. For installing the Data Protector Agent(s) locally, please refer to the topic Local installation of Unix Clients in Chapter 2 (Installing Data Protector on Your Network) of the HP OpenView Storage Data Protector Installation and Licensing Guide for detailed procedure Remote Installation Data Protector Agent(s) for Tru64 can also be installed remotely on the shared disk using any one of the Cluster nodes. You can install Agent(s) by distributing them from the UNIX Installation Server to the Tru64 system, using the Data Protector graphical user interface. At this point you should have the Installation Server for UNIX already installed in the Data Protector Cell. For installing the Data Protector Agent(s) remotely, please refer to Installing Data Protector Clients in Chapter 2 (Installing Data Protector on Your Network) of the HP OpenView Storage Data Protector Installation and Licensing Guide for detailed procedure. Backup and Restore of Tru64 Cluster 5

6 4. Configuring Data Protector in a Tru64 Cluster For Data Protector to be able to see all the systems (individual & cluster nodes), the nodes need to be imported into the Data Protector Cell. Following is the procedure for importing the individual & cluster nodes Importing Cluster to the Data Protector Cell Importing means manually adding a system to the cell after the Data Protector software has been installed on the system. Once the system is a member of the Data Protector cell, the information about the new system is written to the Data Protector database, which is located on the Cell Manager. After local/remote installation of the Data Protector Client on the cluster-shared disk, you need to import the other node(s) and cluster hostnames. Before importing node and cluster hostnames, make sure that: Data Protector is installed on the shared disk in the cluster All Tru64 Cluster nodes are running within the Tru64 cluster Data Protector Inetd process is running on each member The following is an example of importing member and cluster hostnames: A Tru64 Cluster, sawett1.domain.us is configured with two cluster Nodes: sawett2.domain.us and sawett3.domain.us. After you insure that Data Protector is installed on the shared disk and Data Protector is running on both cluster members (inetd process), you import sawett2.domain.us and sawett3.domain.us and cluster sawett1.domain.us hostnames. To import a member/cluster using the Data Protector Graphical User Interface perform the following steps: 1. In the Context List, click Clients. 2. In the Scoping Pane, right-click Client and then click Import Client to start the wizard for importing a client. 3. Follow the wizard to add (import) the Member/Cluster to the cell. See the online Help (Help Navigator) for details. Backup and Restore of Tru64 Cluster 6

7 4.2. Configuring Media Agent for failover Data protector Supports Media Agent in a Tru64 Cluster in two ways: 1. Data Protector Media Agent is installed in the Tru64 Cluster and devices are configured using the individual Node Names. In this case failover of the Media Agent is not supported. The user needs different Backup Specifications in case of a failover of the Media agent. 2. Data Protector Media Agent is installed in the Tru64 Cluster and Devices are configured using the Cluster Name/IP. In case a running backup/restore fails because of a failover in the Cluster, it can be started again after the failover. The same backup specification as before the failover can be used. This way a failover for Media Agent is also provided. In order to be able to configure the Media agent Failover, some variables need to be set in the /usr/omni/.omnirc file on the Tru64 Cluster. Following is a list of variables along with the values that need to be set for this purpose: OB2BMANET=1 OB2RMANET=1 OB2BDANET=1 OB2RDANET=1 Backup and Restore of Tru64 Cluster 7

8 5. Backing Up & Restoring Data in the Cluster 5.1. Backup Shared disks are accessible if the Tru64 Cluster shared disk is running. Therefore, a backup of shared disks will fail if the cluster is not running. To back up the shared disks: Filesystem Backup: 1. Install the Data Protector Disk Agent on the shared disk in the cluster. (as described above in section 3.0) 2. Import the cluster into the Data Protector Cell (as described above in section 3.1) Now Data Protector can access the data in the cluster on a clusterwide basis. 3. For the procedure to create a backup specification, please refer to the topic Creating a Backup Specification chapter 5 ( Backup ) in the HP OpenView Storage Data Protector Administrator s Guide. For Backing up the cluster use the hostname for the cluster while for backing up individual node information, please use the individual node name Oracle Online Backup: 1. Install the Data Protector Oracle Agent on the shared disk in the cluster. (as described above in section 3.0) 2. Import the Cluster into the Data Protector Cell (as described above in section 3.1) Now Data Protector can access the data in the cluster on a clusterwide basis. 3. Backing up Oracle Database would first involve configuring the Oracle Integration. For details of configuring and backing up Oracle, please refer to the Integrating Oracle8/9 and Data Protector chapter of the HP OpenView Storage Data Protector Unix Integration Guide. Please use the Cluster hostname while configuring the Oracle integration and the backup specifications. Backup and Restore of Tru64 Cluster 8

9 5.1.3 SAP Backup 1. Install the Data Protector Oracle Agent on the shared disk in the cluster. (as described above in section 3.0) 2. Add the cluster nodes in your Data Protector Cell Manager, and now you can add the Virtual Cluster Name using import client option and enabled Virtual host in the window. Now Data Protector can access the data in the cluster on a clusterwide basis using the Virtual hostname of the Cluster. 3. Create 3 additional links before starting the backup (assuming ORACLE_SID is in lower case). ln s /sapfiles/admin/dbs/initsap.dba initsap.dba ln s /sapfiles/admin/dbs/initsap.ora initsap.ora ln s /sapfiles/admin/dbs/initsap.sap init SAP.sap 4. Before taking a backup using RMAN Channels Integrate the Data Protector library with the Oracle library as described below: a. Shutdown the database b. Change directory to $ORACLE_HOME/lib c. Link the DP library to the Oracle library using the command: ln s /opt/omni/lib/ libob2oracle8_64bit.sl libobk.sl d. Startup the database instance 5. Data Protector is able to access the SAP database after the above configuration has done. Whenever you take a backup it actually connects the primary node and takes the backup of the Clusterwide database that resides in the shared disk. Backup and Restore of Tru64 Cluster 9

10 5.2. Restore Filesystem Restore: For details on how to restore filesystem data, please refer to the Restore chapter in the HP OpenView Storage Data Protector Administrator s Guide Oracle Restore: For details on how to restore Oracle data, please refer to the section Restoring Oracle8/9 Databases in the chapter Integrating Oracle8/9 and Data Protector of the HP OpenView Storage Data Protector Unix Integration Guide. Please use the Cluster hostname while restoring data SAP Restore: While restoring the SAP database, Data Protector actually restores it in the shared disk through primary node of the Cluster. If the primary node gets failed while restore, the job doesn t get aborted it connects secondary node as a primary node using Virtual hostname (taken care by the Cluster Architecture) and restore the database in the shared disk using the secondary node which actually now is a primary node. Backup and Restore of Tru64 Cluster 10