HP Application Recovery Manager software A.06.
Legal and notice information © Copyright 2006, 2008 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents Publication history .............................................................. 11 About this guide ................................................................. 13 Intended audience ............................................................................................. 13 Documentation set ............................................................................................. 13 Guides ..............................................................................................
The installed directory structure ............................................................... Configuring automatic startup and shutdown ............................................ Setting environment variables ................................................................. Allocating more disk space for the Cell Manager installation ..................... What’s next? ....................................................................................... Installing a Windows Cell Manager ............
Client security ...................................................................................... 98 Application Recovery Manager users ...................................................... 99 Cell Manager security ......................................................................... 100 Other security aspects ......................................................................... 100 Securing clients ........................................................................................
Producing a license report on demand ......................................................... Which licenses are available? ........................................................................... Password considerations ............................................................................ Application Recovery Manager passwords ......................................................... Obtaining and installing permanent passwords using HP OpenView AutoPass .........................................
Installing a Cell Manager using swinstall ...................................................... Installing an Installation Server .................................................................... Installing the clients ................................................................................... Setting up the TCP/IP protocol on Windows systems ............................................ Installing and configuring the TCP/IP protocol on Windows ............................
Figures 1 Application Recovery Manager graphical user interface ....................... 18 2 Application Recovery Manager Cell ................................................... 24 3 Application Recovery Manager installation concept ............................. 25 4 Application Recovery Manager graphical user interface ....................... 29 5 Installation procedure ....................................................................... 32 6 Selecting the installation type ............................
25 Application Recovery Manager user account ...................................... 88 26 Application Recovery Manager user account ...................................... 90 27 Importing a client to the cell .............................................................. 93 28 Importing a Microsoft Cluster Server client to a cell .............................. 95 29 Exporting a client system .................................................................. 97 30 Securing a client ...........................
Tables 1 Edition history ................................................................................. 11 2 Documentation map ......................................................................... 15 3 Document conventions ...................................................................... 16 4 Application Recovery Manager CD-ROM list ....................................... 26 5 Installing integrations .......................................................................
Publication history Guide updates may be issued between editions to correct errors or document product changes. To ensure that you receive updated or new editions, subscribe to the appropriate product support service. See your HP sales representative for details. Table 1 Edition history Part number Guide edition Product T4395-96002 October 2006 Application Recovery Manager Release A.06.00 N/A March 2008 Application Recovery Manager Release A.06.
Publication history
About this guide This guide provides information about: • installing the Application Recovery Manager network product • prerequisites that must be met before starting the installation procedure • upgrading and licensing Intended audience This guide is intended for administrators responsible for installing and maintaining the environment and backup administrators responsible for planning, installing, and managing the backup environment.
• HP Application Recovery Manager software installation and licensing guide This guide describes how to install the Application Recovery Manager software, taking into account the operating system and architecture of your environment. This guide also gives details on how to upgrade Application Recovery Manager, as well as how to obtain the proper licenses for your environment.
Online help Application Recovery Manager provides context-sensitive (F1) Help and Help Topics for Windows and UNIX platforms. You can access the online help from the top-level directory on the installation CD without installing Application Recovery Manager: • Windows: Unzip AppRM_help.zip and open AppRM_help.chm. • UNIX: Unpack the zipped tar file AppRM_help.tar.gz, and access the online help system through AppRM_help.htm.
X Recommendations X Requirements X X X X X Support matrices X X X X X X X X X Supported configurations Troubleshooting X CLI reference Concepts guide X Integration guide Procedures/Tasks X Administrator's guide X Product announcements Planning strategy Installation guide X Getting started Online Help Limitations X X X X X Document conventions and symbols Table 3 Document conventions Convention Element Blue text: Table 3 on page 16 Cross-reference links and e-mail add
Convention Element text Emphasized monospace text CAUTION: Indicates that failure to follow directions could result in damage to equipment or data. IMPORTANT: Provides clarifying information or specific instructions. NOTE: Provides additional information. TIP: Provides helpful hints and shortcuts. Application Recovery Manager graphical user interface Application Recovery Manager provides a cross-platform (Windows and UNIX) graphical user interface.
Figure 1 Application Recovery Manager graphical user interface General Information General information about Application Recovery Manager can be found at http:// www.hp.com/go/apprm. HP technical support For worldwide technical support information, see the HP support website: http://www.hp.
• Detailed questions Subscription service HP recommends that you register your product at the Subscriber's Choice for Business website: http://www.hp.com/go/e-updates After registering, you will receive e-mail notification of product enhancements, new driver versions, firmware updates, and other product resources. HP websites For additional information, see the following HP websites: • • • • • http://www.hp.com http://www.hp.com/go/software http://www.hp.com/service_locator http://www.hp.
About this guide
1 Overview of the installation procedure In this chapter This chapter provides an overview of the Application Recovery Manager installation procedure and introduces concepts that apply to the installation. The chapter also introduces Application Recovery Manager Cell Manager and Application Recovery Manager. Overview of the installation procedure An Application Recovery Manager backup environment is a set of systems with a common backup policy located in the same time zone and existing on the same LAN/SAN.
The User Interface component is needed to access the Application Recovery Manager functionality and is used to perform all configuration and administration tasks. It must be installed on systems used for backup administration. Application Recovery Manager provides a graphical user interface (GUI) and command-line interface (CLI).
NOTE: The Installation Server for Windows must be installed on a Windows system. The Installation Server for UNIX must be installed on an HP-UX system. Refer to the HP Application Recovery Manager software product announcements, software notes, and references for the supported operating system versions. After you have defined the roles of the systems in your future Application Recovery Manager cell, the installation procedure comprises the following general steps: 1.
Figure 2 Application Recovery Manager Cell The remote installation concept Once you have installed the Application Recovery Manager Cell Manager, User Interface, and Installation Server(s) (at least one Installation Server is needed for each platform, UNIX and Windows), you can distribute Application Recovery Manager software to clients using remote installation. See Figure 3 on page 25. Every time you perform a remote installation, you access the Installation Server through the GUI.
Figure 3 Application Recovery Manager installation concept Application Recovery Manager installation CD-ROMs Application Recovery Manager supports various operating systems and several processor architectures. Consequently, 2 CD-ROMs are required to cover all platforms. Table 4 lists the components found on the CD-ROMs.
NOTE: The preferred installation media for Application Recovery Manager are CD-ROMs. Table 4 Application Recovery Manager CD-ROM list CD Num.
• Supported platforms The Cell Manager can be installed on either the Windows or HP-UX platform. See http://www.hp.com/support/manuals for details on supported versions/releases of these platforms. • Reliability of the Cell Manager system Since the Cell Manager contains the IDB and since backup and restore cannot be performed if the Cell Manager is down, it is important to choose a very reliable system in your environment for the installation.
The Application Recovery Manager GUI is simple to handle in heterogeneous environments, because changing the locale is not necessary. To use the Application Recovery Manager GUI functionality on HP-UX IA-64 Cell Manager platform on which the Application Recovery Manager GUI is not supported, you can use the omniusers command to create a remote user account on the Cell Manager.
Figure 4 Application Recovery Manager graphical user interface See also Figure 1 on page 18 in the Preface, which defines the most important areas of the Application Recovery Manager GUI. NOTE: On UNIX, specific local settings are required on the system on which the Application Recovery Manager GUI is running, before starting the GUI. This will enable you to switch character encoding in GUI and thus choose the right encoding to correctly display non-ASCII characters in filenames and session messages.
Overview of the installation procedure
2 Installing Application Recovery Manager on your network In this chapter This chapter contains detailed instructions about: • Installing the Application Recovery Manager Cell Manager (CM) and Installation Servers (IS). Refer to “InstallingtheApplicationRecoveryManagerCellManager(CM)andInstallationServer(s)(IS)”onpage31. • Installing the Application Recovery Manager clients. Refer to “Installing Application Recovery Manager clients” on page 57.
Figure 5 Installation procedure If you install the Cell Manager and the Installation Server on the same system, you can perform this task in one step. IMPORTANT: All configuration and session information files in an Application Recovery Manager cell are stored on the Cell Manager. It is difficult to transfer this information to another system. Therefore, ensure that the Cell Manager is a reliable system in a stable, controlled environment.
Installing a UNIX Cell Manager This section provides step-by-step instructions on how to install a UNIX Cell Manager. If you want to install the Windows Cell Manager only, refer to “Installing a Windows Cell Manager” on page 39. Prerequisites • The HP-UX system that will become the Cell Manager must: • Have sufficient disk space for the Application Recovery Manager software. Refer to the HP Application Recovery Manager software product announcements, software notes, and references for details.
Installation procedure TIP: If you install the Cell Manager and Installation Server on the same system, you can perform the installation in one step by running omnisetup.sh -CM -IS. For a description of the omnisetup.sh command, refer to the README file located in the Mount_point/LOCAL_INSTALL directory on the CD-ROM or to the HP Application Recovery Manager software command line interface reference located in the Mount_point/DOCS/C/MAN directory on the CD-ROM.
2. Run the omnisetup.sh command. To run this command from the CD-ROM, type: cd /cdrom/LOCAL_INSTALL ./omnisetup.sh -CM To start the installation from disk: • If you have copied the APPRM_DEPOT, AUTOPASS, and LOCAL_INSTALL directories to your local disk in the directory, run: cd directory/LOCAL_INSTALL ./omnisetup.sh -source directory -CM • If you have copied the whole CD-ROM to cd_image_dir, run the omnisetup.sh command with the -CM parameter: cd cd_image_dir/LOCAL_INSTALL ./omnisetup.sh -CM 3. omnisetup.
IMPORTANT: If you want to install Application Recovery Manager to linked directories, for instance: /opt/omni/ -> /prefix/opt/omni/ /var/opt/omni/ -> /prefix/var/opt/omni/ /etc/opt/omni/ -> /prefix/etc/opt/omni/ you must create the links before the installation and ensure that the destination directories exist. Refer to “Allocating more disk space for the Cell Manager installation” on page 38 for more information.
/var/opt/omni/tmp Temporary files /var/opt/omni/server/db40 IDB files. Refer to the online Help index: “IDB, location of directories” for details. Configuring automatic startup and shutdown The Application Recovery Manager installation procedure configures an automatic startup and shutdown of all Application Recovery Manager processes whenever a system is restarted. Some of this configuration is operating system dependent. The following files are automatically configured: /sbin/init.
When the installation is finished, the following processes are running on the Cell Manager: /opt/omni/lbin/crs The Application Recovery Manager Cell Request Server (CRS) service runs on the Cell Manager system and is started when the Cell Manager software is installed on the system. CRS starts and controls backup and restore sessions in the cell.
announcements, software notes, and references for details on the required disk space. If you do not have enough disk space, you can use linked directories, but you must create the links before the installation and ensure that the destination directories exist. What’s next? At this stage, the Cell Manager is installed and – if it was selected – also the Installation Server for UNIX. Your next tasks are: 1.
hostname must be the same. Refer to “Setting up the TCP/IP protocol on Windows systems” on page 170 for information on installation and configuration of the TCP/IP protocol. • Have access to a CD-ROM drive. • Ensure, that HP OpenView Storage Data Protector is not installed on your system. If Data Protector is detected during the installation procedure, the installation of the Application Recovery Manager will be aborted.
HP StorageWorks Disk Array XP hardware provider limitation Application Recovery Manager and FRS require different versions of HP StorageWorks Disk Array XP hardware provider. However, only one version of the hardware provider can be installed on the same system. If you install the Application Recovery Manager and FRS on the same system that is connected to the HP StorageWorks Disk Array XP, you can use only one of these products.
3. In the Installation Type page, select Cell Manager and then click Next to install Application Recovery Manager Cell Manager software. Figure 6 Selecting the installation type 4. Provide the username and password for the account under which the Application Recovery Manager services will run. Click Next to continue. 5. Click Next to install Application Recovery Manager in the default folder. Otherwise, click Change to open the Change Current Destination Folder window and enter a new path.
6. In the Component Selection page, select the components you want to install. For a list and descriptions of the Application Recovery Manager components, see “Application Recovery Manager components” on page 64. Figure 7 Selecting software components User Interface, Installation Server, and Microsoft Volume Shadow Copy Integration are selected by default. Click Next.
7. The component summary list is displayed. Click Install to start installing the selected components. This may take several minutes.
8. The Installation status page is displayed. Click Next.
9. On operating systems other than 64-bit Windows (x64, IA-64), the Setup Wizard enables you to install or upgrade the HP OpenView AutoPass utility if you want to download and install passwords for the purchased licenses directly through the internet from the HP password delivery center web server. For more information on the AutoPass utility, refer to “Obtaining and installing permanent passwords using HP OpenView AutoPass” on page 141.
Figure 10 Selecting AutoPass for installation Click Finish. After the installation As soon as the setup is finished, the Cell Manager files are located in the AppRM_home directory and the software depot located in the AppRM_home\Depot directory. When the installation is finished, the following processes will be running on the Cell Manager system: crs.
• NSLookup, so that Application Recovery Manager is able to expand hostnames • Disk Space • Administrative Rights What’s next? At this stage, the Cell Manager is installed and – if it was selected – also the Installation Server. Your next tasks are: 1. Install the Installation Server, if you have not installed it on the same system as the Cell Manager. Refer to “Installing Installation Servers” on page 48. 2. Distribute the software to clients.
• Have enough disk space for the complete Application Recovery Manager software depot. Refer to the HP Application Recovery Manager software product announcements, software notes, and references for details. • Have a CD-ROM drive. • The Cell Manager in the Application Recovery Manager cell must be of the A.06.10 version.
1. Insert and mount the UNIX installation CD-ROM to a mount point.
When the installation is finished, the software depot for UNIX is located in the /opt/omni/databases/vendor directory. The omnisetup.sh command installs the Installation Server with all packages. To install only a subset of the packages, use swinstall. Refer to “Installing on HP-UX systems using native tools” on page 167. IMPORTANT: If you do not install the Installation Server for UNIX on your network, you will have to install every UNIX client locally from the UNIX installation CD-ROM.
1. If you installed the Installation Server on a different system than the Cell Manager, you must manually add (import) the system to the Application Recovery Manager cell. Refer to “Importing an installation server to a cell ” on page 93. NOTE: When an Installation Server is imported, the file /etc/opt/omni/server/cell/installation_servers on the Cell Manager is updated to list the installed push-packets. This can be used from the CLI to check the available push-packets.
Limitation Due to the security restrictions imposed by the Windows operating system, Installation Server can be used to remotely install clients only in the same domain. IMPORTANT: If you do not install the Installation Server for Windows on your network, you will have to install every Windows client locally from the CD-ROM. NOTE: You cannot remotely install an Application Recovery Manager client on the system after an Installation Server has been installed on this system.
3. In the Installation Type page, select Installation Server and then click Next to install Application Recovery Manager software depot. Figure 11 Selecting the installation type 4. Click Next to install Application Recovery Manager on the default folder. Otherwise, click Change to open the Change Current Destination Folder window and enter a new path. 5. Windows 2003 SP1: If Application Recovery Manager detects Windows Firewall on your system, the Windows Firewall configuration page is displayed.
6. The component summary list is displayed. Click Install to start installing the selected components. This may take several minutes.
7. The Installation status page is displayed. Click Next. Figure 13 Installation status page 8. Click Finish. As soon as the installation is finished, the software is, by default, installed in the AppRM_home\Depot directory, which is shared so that it can be accessed from the network. What’s next? At this point, you should have Installation Server installed on your network. Now you should perform the following tasks: 1. If you have set up an independent Installation Server (i.e.
Installing Application Recovery Manager clients You can install Application Recovery Manager clients remotely, by distributing them using the Installation Server, or locally, from the installation CD-ROM. For the list of Application Recovery Manager installation CD-ROMs, refer to “Application Recovery Manager installation CD-ROMs” on page 25.
Application Reference HP StorageWorks Disk Array XP See “HP StorageWorks Disk Array XP integration” on page 79. HP StorageWorks Enterprise Virtual Array See “HP StorageWorks Enterprise Virtual Array integration” on page 79. Remote installation of Application Recovery Manager clients This section describes the procedure for distributing the Application Recovery Manager software to clients using the Installation Server (remote installation). Prerequisites • See the http://www.hp.
Adding clients to the cell To distribute the Application Recovery Manager software to the clients that are not in the Application Recovery Manager cell yet, proceed as follows: 1. Start the Application Recovery Manager GUI: • Original Application Recovery Manager GUI: • On Windows: Select Start > Programs > HP Application Recovery Manager software > Application Recovery Manager.
5. Type the names of the clients or search for the clients (on Windows GUI only) you want to install as shown in and Figure 14 on page 60. Click Next.
6. Select the Application Recovery Manager components you want to install as shown in and Figure 15 on page 61. See “Application Recovery Manager components” on page 64. Figure 15 Selecting components To change the default user account and target directory for the installation, click Options. If you selected more than one client and you would like to install different components on each client, click I want to customize this option for client systems independently and then click Next.
NOTE: Before you start using the Application Recovery Manager GUI on the client system, add a user from that system to an appropriate Application Recovery Manager user group. For the procedure and the descriptions of available user rights, refer to the online Help. Troubleshooting When the remote installation is finished, you can restart any failed installation procedures using the GUI by clicking Actions and Restart Failed Clients. If the installation fails again, see Chapter 6 on page 149.
4. Select the clients on which you want to install the components as shown in and Figure 16 on page 63. Click Next.
5. Select the Application Recovery Manager components you want to install as shown in Figure 17 on page 64. See “Application Recovery Manager components” on page 64. Figure 17 Selecting components If you selected more than one client and you want to install different components on each client, click I want to customize this option for client systems independently and then click Next. Select the components for each client independently. Click Finish to start the installation.
User Interface The User Interface includes the Application Recovery Manager graphical user interface and the command-line interface. The software is needed to access the Application Recovery Manager Cell Manager and must be installed at least on the system that is used for managing the cell. English Documentation and Help This is the Application Recovery Manager English Language Documentation and online Help (OLH) file set.
Installing Windows clients For details on supported platforms and components for a particular Windows operating system, see the http://www.hp.com/support/manuals. Prerequisites To install a Windows client, you must have the Administrator rights. The Windows system that will become your future Application Recovery Manager client system must meet the following requirements: • Have Microsoft Internet Explorer 5.0 or higher. • Have sufficient disk space for the Application Recovery Manager client software.
HP StorageWorks Fast Recovery Solution You can install Application Recovery Manager on the same system where you have the HP StorageWorks Fast Recovery Solution (FRS) installed. These two products can coexist on the same system as long as they use different disk array volumes. During the Application Recovery Manager setup, an existing FRS installation is detected. If you install a client locally, choose one of the three options: Continue with installation, Cancel installation, or Deinstall FRS.
3. Enter the name of the Cell Manager. Refer to Figure 18 on page 68. If your Cell Manager uses a different port then the default 5555, change the port number. You can test if the Cell Manager is active and uses the selected port by clicking Check response... Click Next. Figure 18 Choosing the Cell Manager 4. Click Next to install Application Recovery Manager on the default folder. Otherwise, click Change to open the Change Current Destination Folder page and enter the path. 5.
6. Windows 2003 SP2: If Application Recovery Manager detects Windows Firewall on your system, the Windows Firewall configuration page is displayed. Application Recovery Manager setup will register all necessary Application Recovery Manager executables. By default, the selected option is Initially, enable newly registered Application Recovery Manager binaries to open ports as needed. If you do not want to enable Application Recovery Manager to open ports at the moment, deselect the option.
7. The component selection summary page is displayed. Click Install to install the selected components. Figure 19 Component selection summary page 8. The Installation status page is displayed. Click Next.
9. To start using Application Recovery Manager immediately after setup, select Launch Application Recovery Manager GUI. To view the HP Application Recovery Manager software product announcements, software notes, and references, select Open the Product Announcements. Click Finish. Installing HP-UX clients HP-UX clients can be installed locally from the UNIX installation CD-ROM, or remotely using the Installation Server for UNIX.
After the remote installation, the client system automatically becomes a member of the Application Recovery Manager cell. Cluster-aware clients Additional prerequisites and steps are required for installing cluster-aware clients. Refer to “Installing a cluster-aware client” on page 81 for more details.
2. From the Mount_Point/LOCAL_INSTALL directory run the omnisetup.sh command. The syntax of the command is as follows: omnisetup.sh [-source directory] [-server name] [-install component_list] where: • directory is the location where the installation CD is mounted. If not specified, the current directory is used. • name is a full hostname of the Cell Manager of the cell to which you want to import the client. If not specified, the client will not be automatically imported to the cell.
automatically imported to the cell with the Cell Manager computer.company.com: ./omnisetup.sh -server computer.company.com -install smisa,cc 3. Setup informs you if the installation was completed and if the client was imported to the Application Recovery Manager cell. The CORE component is installed the first time any software component is selected for installation. The CORE-INTEG component is installed the first time any integration software component is selected for installation or reinstallation.
Installing the Application Recovery Manager integration clients Microsoft Volume Shadow Copy Service clients To perform backups of VSS writers (Microsoft Exchange Server and Microsoft SQL Server) or only filesystem backup using VSS, install the following Application Recovery Manager software components on both the application and backup systems or, in case of local backup, on the application system only: • Depending on the disk array used, HP StorageWorks XP Agent or HP StorageWorks EVA SMI-S Agent.
variables. For more information, see the HP Application Recovery Manager software integration guide. The Oracle archive redo log files do not have to reside on source volumes. Installation procedure • Install the following Application Recovery Manager software components: • Depending on the disk array used, HP StorageWorks XP Agent or HP StorageWorks EVA SMI-S Agent - on both the application and backup systems. • Oracle Integration - on the application system only.
• The SAP R/3 software must be correctly installed on the application system. The following is a list of standard directories that must be installed on the application system after installing SAP R/3: NOTE: The location of the directories is dependent on the environment (UNIX systems) or registry (Windows system) variables. Refer to the SAP R/3 documentation for more information.
UNIX systems On UNIX systems, if the last six directories do not reside at the above specified destinations, create appropriate links to them. On UNIX systems, the directory /usr/sap/ORACLE_SID/SYS/exe/run must be owned by the UNIX user oraORACLE_SID. The owner of the SAP R/3 files must be the UNIX user oraORACLE_SID and the UNIX group dba with setuid bit set (chmod 4755 ...). The exception is the file BRRESTORE, which must be owned by the UNIX user ORACLE_SIDadm.
HP StorageWorks Disk Array XP integration To integrate HP StorageWorks Disk Array XP with Application Recovery Manager, install the HP StorageWorks XP Agent Application Recovery Manager software component on the application and backup systems. Installing in a cluster You can install the HP StorageWorks Disk Array XP integration in a cluster environment. For the supported cluster configurations and specific installation requirements, see HP Application Recovery Manager software administrator's guide.
Installing Application Recovery Manager on MC/ServiceGuard Application Recovery Manager supports MC/ServiceGuard (MC/SG) for HP-UX. For details on supported operating system versions, refer to the HP Application Recovery Manager software product announcements, software notes, and references. If your Cell Manager is to be cluster-aware, note that the virtual server IP address should be used for licenses.
Installing a cluster-aware client IMPORTANT: The Application Recovery Manager cluster-aware clients must be installed on all the cluster nodes. The installation procedure is standard procedure for installing Application Recovery Manager on an UNIX client. Refer to “Installing HP-UX clients” on page 71 for detailed instructions. What’s next? When the installation has been completed, you must import the virtual server (the hostname specified in the cluster package) to the Application Recovery Manager cell.
This can be done as follows: 1. Click Start > Programs >Administrative Tools > Cluster Administrator. 2. Check the resource list and delete or rename these resources, if necessary.
• If the virtual server does not exist in the same group as the File Share resource group, a new virtual server must be created using a free registered IP address and associating a network name with it. • The File Share resource where Application Recovery Manager is to be installed must have the IP Address, Network Name, and Physical Disk set among the File Share dependencies.
3. In the Installation Type page, select Cell Manager and then click Next to install Application Recovery Manager Cell Manager software.
4. Setup automatically detects that it is running in a cluster environment. Select Install cluster-aware Cell Manager to enable a cluster setup. Select the cluster group, the virtual hostname, and the cluster File Share resource on which Application Recovery Manager shared files and the database will reside. NOTE: If you select Install Cell Manager on this node only, the Cell Manager will not be cluster aware. Refer to “Installing a Windows Cell Manager” on page 39.
5. Enter the username and password for the account that will be used to start Application Recovery Manager services. Figure 23 Entering the account information 6. Click Next to install Application Recovery Manager on the default folder. Otherwise, click Change to open the Change Current Destination Folder window and enter a new path. 7. In the Component Selection window, select the components you want to install on all cluster nodes and cluster virtual servers. Click Next.
9. The Installation setup page is displayed. Click Next. Figure 24 Installation status page 10. To start Application Recovery Manager immediately after install, select Start the Application Recovery Manager GUI. To view the HP Application Recovery Manager software product announcements, software notes, and references, select Open the Product Announcements.
1. Check if the Cluster service account is assigned to the Application Recovery Manager Inet service on each cluster node. Make sure the same user is also added to the Application Recovery Manager admin user group. The logon account type should be set to This account as shown in and Figure 25 on page 88. Figure 25 Application Recovery Manager user account 2.
Installing cluster-aware clients Prerequisites Before you install a cluster-aware Application Recovery Manager client, the following prerequisites must be fulfilled: • A cluster must be installed properly with all of its functionality on all cluster nodes. For example, you must be able to move groups from one to another node as many times as needed, with no problems with shared disk(s). • Each system of the cluster should be up and running properly.
1. Check if the Cluster service account is assigned to the Application Recovery Manager Inet service on each cluster node. Make sure the same user is also added to the Application Recovery Manager admin user group. The logon account type should be set to This account as shown in Figure 26 on page 90. Figure 26 Application Recovery Manager user account 2. Switch to the AppRM_home\bin directory. 3. Run the following command: omnirsh host INFO_CLUS where host is the name of the cluster client system.
3 Maintaining the installation In this chapter This chapter describes the procedures most frequently performed to modify the configuration of your backup environment. The following sections provide information about: • How to import clients to a cell using the graphical user interface. Refer to “Importing clients to a cell ” on page 91. • How to import an Installation Server to a cell using the graphical user interface. Refer to “Importing an installation server to a cell ” on page 93.
after the Application Recovery Manager software has been installed. When added to an Application Recovery Manager cell, the system becomes an Application Recovery Manager client. Once the system is a member of the cell, information about the new client is written to the IDB, which is located on the Cell Manager. A client can only be a member of one cell. If you wish to move a client to a different cell, you first export it from its current cell and then import it to the new cell.
3. Type the name of the client or browse the network to select the client you want to import. See Figure 27 on page 93. Figure 27 Importing a client to the cell If you are importing a client configured with multiple LAN cards, select the Virtual Host option. With this option you must import all names of the same system. Click Finish to import the client. The name of the imported client is displayed in the Results Area.
Unlike a client, an Installation Server can be a member of more than one cell. Therefore it does not have to be deleted (exported) from one cell before it can be added (imported) to another cell. How to add? The process for importing an Installation Server is similar to that for importing a client. The task is performed using the Application Recovery Manager GUI (connected to the Cell Manager of the cell to which the Installation Server is to be added) by performing the following steps: 1.
3. Type the name of the virtual server representing the cluster client to be imported or browse the network to select the virtual server. See Figure 28 on page 95. Figure 28 Importing a Microsoft Cluster Server client to a cell 4. Click Finish to import the cluster client. TIP: To import a specific cluster node or a virtual server, right click its cluster in the Scoping Pane and click Import Cluster Node or Import Cluster Virtual Server.
• Want to remove a client from the Application Recovery Manager cell configuration which is no longer part of the network • Want to fix problems caused by insufficient licenses By exporting a client from a cell, the license becomes available to some other system. Prerequisites Before you export a client, check the following: • All the occurrences of the client have been removed from backup specifications.
2. In the Scoping Pane, click Clients, right-click the client system that you want to export, and then click Delete. See Figure 29 on page 97. Figure 29 Exporting a client system 3. You will be asked if you want to uninstall Application Recovery Manager software as well. Click No to export the client, and then click Finish. The client will be removed from the list in the Results Area.
1. In the Context List, click Clients. 2. In the Scoping Pane, expand MS Clusters, right-click the cluster client that you want to export, and then click Delete. 3. You are asked if you also want to uninstall the Application Recovery Manager software. Click No to only export the cluster client. The cluster client will be removed from the list in the Results Area. TIP: To export a specific cluster node or a virtual server, right-click the cluster node or virtual server in the Scoping Pane and click Delete.
these capabilities are available only to the processes running on cell authorities (Cell Manager and Installation Server), and that all other requests are rejected. Before securing clients, it is important to determine a list of trusted hosts. This list must include: • Cell Manager • Relevant Installation Servers • For some clients also a list of clients that will access the m remotely. IMPORTANT: The list must contain all possible hostnames (or IP addresses) where connections can come from.
to reduce these risks. These settings are described later on in this chapter. See also “Start backup specification user right” on page 108. • Application Recovery Manager comes with only a few predefined user groups. It is recommended to define specific groups for each type of user in the Application Recovery Manager environment to minimize the set of rights assigned to them. • The configuration of users is connected with user validation (see “Strict hostname checking” on page 106).
• Disk arrays (and the clients they are connected to) must be physically protected from unauthorized or untrusted personnel. • During backup or restore data is transferred via network. You should provide sufficient separation from the untrusted network. Refer also to the online Help for other security related aspects. Securing clients After you have installed Application Recovery Manager clients and imported them to a cell, it is highly recommended to protect the clients from access by unwanted clients.
The concept of allowing and denying access can be applied to all systems with Application Recovery Manager installed. For example, you can allow or deny access of Cell Managers to clients, Cell Managers to Cell Managers, Installation Servers to clients, or clients to clients. NOTE: If an Installation Server residing on a system other than the Cell Manager is not added to the list of allowed clients, it will not have access to a secured client.
2. In the Scoping Pane, expand Clients, right-click the client(s) you want to secure, and click Secure. See Figure 30 on page 103.
3. Type the names of the systems that will be allowed to access the selected client(s) or search for the systems using the Network (on Windows GUI only) or Search tabs. Click Add to add each system to the list. See Figure 31 on page 104. Figure 31 Enabling security on selected client(s) The Cell Manager is automatically provided with access and added to the list of trusted clients. You cannot exclude the Cell Manager from the list. 4. Click Finish to add the selected systems to the allow_hosts file.
2. In the Scoping Pane, right-click Clients and click Cell Secure. See Figure 32 on page 105. Figure 32 Securing a cell 3. Type the names of the systems that will be allowed to access all clients in the cell or search for the systems using the Network or Search tabs. Click Add to add each system to the list. See . 4. Click Finish to add the selected systems to the allow_hosts file.
How to remove security If you want to remove security from the selected system(s), perform the following steps in the Application Recovery Manager GUI: 1. In the Context List, click Clients. 2. In the Scoping Pane, right-click the client(s) from which you want to remove security and click Unsecure. 3. Click Yes to confirm that you allow access to the selected client(s). If you want to remove security from all the clients in the cell, proceed as follows: 1. In the Context List, click Clients. 2.
The strict hostname checking setting on the other hand, provides enhanced validation of users. The validation uses the hostname as it is resolved by the Cell Manager using the reverse DNS lookup from the IP obtained from the connection. This imposes the following limitations and considerations: Limitations • IP based validation of users can only be as strong as the anti-spoof protection in the network.
A prerequisite for a reliable reverse DNS lookup is a secure DNS server. You must prevent physical access and log on to all unauthorized personnel. By configuring users with IPs instead of hostnames, you can avoid some DNS related validation problems, but such configuration is more difficult to maintain. Requirement The enhanced validation does not automatically grant access for certain internal connections.
Allowing users to perform interactive backups may not always be desired. To allow interactive backups only for users who also have the right to save a backup specification, set the StrictSecurityFlags flag 0x0200 in the global options file. For more information on the global options file, refer to the online Help. Hiding the contents of backup specifications In a high security environment, the contents of saved backup specifications may be considered to be sensitive or even confidential information.
cluster.domain.com node1.domain.com node2.domain.com } GROUP="Bajo" { computer.domain.com anothercomputer.domain.com } Monitoring security events If you encounter problems using Application Recovery Manager, you can use the information in the log files to determine your problem. For example, logged events can help you to determine misconfigured users or clients. Client security events Client security events are logged in the inet.log file on every client in the cell AppRM_home\log directory.
To verify which Application Recovery Manager patches are installed on a particular system in a cell, use the Application Recovery Manager GUI or CLI. Limitations Below are the limitations for patch verification: • Patch verification can check which patches are installed only on members that belong to the same cell. Verifying Application Recovery Manager patches using the GUI 1. In the Context List, select Clients. 2.
Verifying Application Recovery Manager Patches Using the CLI To verify which patches are installed on a particular client using the Application Recovery Manager CLI, run the omnicheck -patches -host hostname command from the following directory: • On Windows: AppRM_home\bin • On UNIX:/opt/omni/bin where hostname is the name of the system to be verified. Refer to the omnicheck man page for more information on the omnicheck command.
Prerequisites Before you uninstall the Application Recovery Manager software from a computer, check the following: • Make sure that all references to the computer are removed from the backup specifications. Otherwise, Application Recovery Manager will try to back up unknown systems and this part of the backup specification will fail. Refer to online Help index: “modifying, backup specification” for instructions on how to modify backup specifications.
Cluster clients If you have cluster aware clients in your Application Recovery Manager environment and you want to uninstall them, you must do this locally. The procedure is the same as for uninstalling Cell Manager or Installation Server. Refer to “Uninstalling the Cell Manager and Installation Server” on page 114. The cluster client will be removed from the list in the Results Area and the Application Recovery Manager software will be deleted from its hard disk.
3. Depending on whether you installed HP OpenView AutoPass or not, and if you want to remove the Application Recovery Manager configuration data or not, different actions apply. IMPORTANT: If you leave the Application Recovery Manager configuration data on the system after the uninstallation, and you later install a lower version of the Application Recovery Manager Cell Manager than the uninstalled version was, note that the configuration data will be unusable.
Uninstalling from HP-UX system IMPORTANT: If you leave the Application Recovery Manager configuration data on the system after the uninstallation, and you later install a lower version of the Application Recovery Manager Cell Manager than the uninstalled version was, note that the configuration data will be unusable. To successfully install a lower version, after the uninstallation remove the remaining Application Recovery Manager directories from your system.
To manually remove the files from an HP-UX system, do the following: 1. Run /usr/sbin/swremove APPRM to remove the Application Recovery Manager software. 2. Remove the following directories using the rm command: rm -fr /var/opt/omni rm -fr /etc/opt/omni rm -fr /opt/omni At this stage, Application Recovery Manager references no longer reside on your system.
5. In the Custom Setup window, select the components you want to add and/or unselect the software components you want to remove. Click Next. 6. Click Install to start the installing or removing the software components. 7. When the installation is completed, click Finish. Cluster-Aware clients If you are changing the Application Recovery Manager software components on the cluster-aware clients, it must be done locally, from the CD-ROM, on each cluster node.
NOTE: When you mark the Application Recovery Manager components you want to remove, and if the remaining components cannot operate properly, the Dependency Message Dialog box appears with a list of dependent components.
Maintaining the installation
4 Upgrading to Application Recovery Manager A.06.10 In this chapter This chapter provides instructions for performing Application Recovery Manager upgrade and migration tasks. Upgrade overview Before you begin Before upgrading an existing product version to Application Recovery Manager A.06.10, consider the following: • Refer to the HP Application Recovery Manager software product announcements, software notes, and references for information about supported and discontinued platforms and versions.
Limitations • The upgrade to Application Recovery Manager A.06.10 is only supported for Application Recovery Manager A.06.00. • Changing the Cell Manager platform is not supported in the A.06.10 release of Application Recovery Manager. Upgrades are only supported on the same Cell Manager platform (Windows to Windows). • If you are upgrading to Application Recovery Manager A.06.10 on Windows and you have the version of Microsoft Installer (MSI) older than 2.
Licenses The existing Application Recovery Manager A.06.00 licenses are fully compatible and valid for use with Application Recovery Manager A.06.10. For details about licensing, refer to Chapter 5 on page 133. Before you begin Before you begin with the upgrade, refer to “Upgrade overview” on page 121 for information on limitations and the upgrade sequence.
Upgrade procedure To upgrade the Windows Cell Manager and Installation Server to Application Recovery Manager A.06.10, follow the procedure described below: 1. Insert the Windows installation CD-ROM and run the \i386\setup.exe command. Setup detects the old Application Recovery Manager installation. Click Next to start the upgrade. 2. In the Component Selection page, the components previously installed on the system are selected.
4. The component summary list is displayed. Click Install to perform the upgrade. Figure 34 Component selection summary page 5. The Installation status page is displayed. Click Next.
6. This step is performed only for a Cell Manager upgrade. If the Installation Server installed on a client other than the Cell Manager is being upgraded, this step does not occur. The Setup Wizard enables you to install or upgrade the HP OpenView AutoPass utility if you want to download and install passwords for the purchased licenses directly through the internet from the HP password delivery center web server.
• Check if you have to apply any modifications to your configuration files. Refer to “Checking configuration changes” on page 127.
• Comments are not transferred to the newly merged file. On Windows systems, the global options file is in the UNICODE format and can be edited using, for example, Notepad. After editing this file, make sure that you saved it in the UNICODE format. The description of new options is in the merged global options file: AppRM_home\Config\server\options\global on the Windows Cell Manager. For details on how to use global options, see the HP Application Recovery Manager software troubleshooting guide.
Upgrading clients remotely For the procedure on how to upgrade the clients using the Installation Server, refer to “Remote installation of Application Recovery Manager clients” on page 58. Upgrading clients locally If you do not have an Installation Server installed on your network, or if for some reason you cannot distribute the Application Recovery Manager software to a client system, Application Recovery Manager clients can be upgraded locally.
2. Application Recovery Manager automatically selects the components that were installed. Figure 37 Selecting the components 3. The component selection summary list is displayed. Click Install to perform the upgrade. Note that after the upgrade, every node has the same component set. Figure 38 Component selection summary page 130 Upgrading to Application Recovery Manager A.06.
4. The Installation status page is displayed. Click Next. Figure 39 Installation status page 5. To start using Application Recovery Manager immediately after setup, select Start the Application Recovery Manager Manager GUI. To view the HP Application Recovery Manager software product announcements, software notes, and references, select Open the Product Announcements.
Upgrading to Application Recovery Manager A.06.
5 Application Recovery Manager licensing In this chapter This chapter contains information about how Application Recovery Manager licenses are checked and reported, and about how to obtain and install Application Recovery Manager passwords. Introduction The Application Recovery Manager A.06.10 product structure and licensing consists of two main categories: 1. Cell Manager Pack 2. Functional Extensions Passwords are bound to the Cell Manager and are valid for the entire Application Recovery Manager cell.
• When the Application Recovery Manager User Interface is started, if there are any missing licenses reported in the Application Recovery Manager Event Log, an Event Log notification is displayed. For more information on Application Recovery Manager Event Log, see the online Help index: “Event Log, Application Recovery Manager“. • When an Application Recovery Manager session is started, the licenses are checked and, if missing, reported.
When a capacity based license is being checked, the amount of total disk space on logical units that have been backed up is compared to the capacity of licenses installed. License checking is done in such a way as not to prevent you from performing instant recovery or a backup even if you have run out of licensed capacity. In these circumstances a warning message appears during the backup session informing you that you have exceeded your licensed capacity.
Figure 40 Used capacity calculation scenario Calculations for instant recovery used capacity count source capacity for ZDB sessions that left data for instant recovery purposes. The same disk is only counted once 200 GB (App.1) + 150 GB (App.2)+ 120 GB (App.3) = 470 GB. Capacity based licensing examples This section provides examples of how capacity based licensing is calculated.
Example 1 and Figure 41 shows a situation where data from one 200 GB logical unit is backed up three times a day in a ZDB-to-disk session. Figure 41 ZDB-to-Disk sessions Three split mirror or snapclone copies (replicas) are rotated and kept for the purpose of instant recovery. The capacity based licensing is calculated as follows: One 200 GB logical unit is used for ZDB-to-disk sessions. Three replicas of the same 200 GB logical unit are kept for the purpose of instant recovery.
Producing a license report on demand To produce a license report, the Application Recovery Manager omnicc command is to be used. Enter the following command: omnicc -check_licenses [-detail] If the -detail option is not specified, the command returns information on whether the Application Recovery Manager licensing is covered or not. If the -detail option is specified, a detailed report is produced.
Figure 42 The HP Application Recovery Manager software product structure Application Recovery Manager leverages the product numbers of previous Application Recovery Manager versions. This is why existing Application Recovery Manager licenses remain valid after the migration. Refer to “Application Recovery Manager A.06.10 product structure and licenses” on page 161 for more information about available licenses. Password considerations Consider the following to help determine the right number of passwords.
• If the system on which the Cell Manager is installed has more than one IP address (multihomed systems, RAS-servers, clusters), you can bind the license to any of the IP addresses. NOTE: If you intend to change the IP address of the Cell Manager, to move the Cell Manager to another system or to move licenses from one cell to another, you must contact the HP Password Delivery Center (PDC) in order to update the licenses.
Emergency passwords are issued by the support organization. They must be requested by and are issued only to HP personnel. Please refer to your support contact or to the HP Licensing site at: http://webware.hp.com. The purpose of an emergency password is to enable the backup operation while the original system configuration gets reconstructed or until you move to a new permanent installation.
Limitations For HP OpenView AutoPass, the following limitations apply: • The HP OpenView AutoPass utility is not installed on Windows x64 operating systems. • It is not recommended to install the HP OpenView AutoPass utility in Microsoft Cluster, because it will be installed only on one node and not on all nodes. For additional prerequisites and limitations, refer to the HP OpenView AutoPass licensing guide. The passwords are installed on the Cell Manager and are valid for the entire cell.
1. Gather the information required in the Permanent Password Request Form. See “Application Recovery Manager licensing forms” on page 164 to find the location of the forms and get instructions on how to fill them out. 2. See “Application Recovery Manager A.06.10 product structure and licenses” on page 161 for more information about the product structure. The HP Password Delivery Center will send your permanent password using the same method that you used when you sent your request.
Prerequisite You must have received permanent passwords sent from the HP Password Delivery Center and the Application Recovery Manager user interface must be installed on the Cell Manager. The passwords are installed on the Cell Manager and are valid for the entire cell. Using the GUI To install the permanent password using the Application Recovery Manager GUI, proceed as follows: 1. In the Context List, click Clients. 2.
2. Run the following command: • On Windows: AppRM_home\bin\omnicc -install_license password • On UNIX: /opt/omni/bin/omnicc -install_license password The password string must be entered exactly as it appears on the Password Certificate. It must be formatted as a single line and must not contain any embedded carriage returns. The password must be in quotes. If the password includes also a description in quotes, the quotes in this description must be preceded with backslashes.
This command displays all installed licenses. If the password you entered is not correct, it is listed with the remark Password could not be decoded. Finding the number of installed licenses Using the GUI Once you have installed a permanent password, you can check how many licenses are currently installed on the Cell Manager: 1. Start the Application Recovery Manager GUI. 2. In the menu bar, click Help, and then About. The About Manager window will open, displaying the installed licenses.
1. Fill out one License Move Form for each new Cell Manager and send it to the HP Password Delivery Center. If you want to move licenses for products, which can no longer be purchased, then please use the License Move Forms delivered with the previous version of the product. Refer to “Application Recovery Manager licensing forms” on page 164. On the form, you must specify the number of licenses you want to move from the existing Cell Manager. 2.
Application Recovery Manager licensing
6 Troubleshooting installation In this chapter This chapter contains information specific to installation related problems. For general troubleshooting information, see the online Help .
• If you have not configured either DNS or LMHOSTS, you get a warning message to enable the DNS or the LMHOSTS resolution in the TCP/IP properties dialog. Action Check your DNS or LMHOSTS file configuration or activate it. See the “Verifying DNS connections within Application Recovery Manager cell” on page 150.
Using the omnicheck command Limitation • The command verifies connections among the cell members only; it does not verify DNS connections in general.
Table 8 on page 152 lists return messages for the omnicheck command. If the return message indicates a DNS resolution problem, see the online Help index: “troubleshooting, networking and communication“. Table 8 Return messages Return Message Meaning client_1 cannot connect to client_2 Timeout connecting to client_2.
Troubleshooting installation and upgrade of Application Recovery Manager Problem Cell Manager installation on a Windows system, which is not part of any Windows domain, fails The following error message is reported: Setup is unable to match the password with the given account name. Actions Two solutions are available: • Make the Windows system, on which you are installing the Cell Manager, part of a domain. • Use the local administrator account for the CRS service.
Action Manually uninstall already installed components after you cancelled the installation. Problems with remote installation of Windows clients Problem Error starting setup process When using Application Recovery Manager remote installation to update Windows clients, you get the following error: Error starting setup process, err=[1326] Logon failure: unknown user name or bad password.
For disk space requirements, see the HP Application Recovery Manager software product announcements, software notes, and references. Problem Problems with the installation of an HP-UX client When adding a new HP-UX client to a Application Recovery Manager cell, the following error message is displayed: /tmp/omni_tmp/packet: you do not have the required permissions to perform this SD function..... Access denied to root at to start agent on registered depot /tmp/omni_tmp/packet. No insert permission on host.
Troubleshooting installation of Windows XP clients Problem Remote installation of Windows clients fails When a Windows XP system is a member of a workgroup and the Simple File Sharing security policy setting is turned on, users attempting to access this system through the network are forced to use the Guest account.
Prerequisite An Installation Server must be available for the client system that you select. To verify an Application Recovery Manager installation using the Application Recovery Manager GUI: 1. In the Context List, click Clients. 2. In the Scoping Pane, expand Clients, right-click the Cell Manager system, and then click Check Installation to start the wizard. 3. Follow the wizard to verify the installation of the systems in the cell.
Which log files to check in case of installation problems depends on the type of the installation (local or remote) and on the operating system. Local installation In case of problems with local installation, check the following log files (on the client system where the setup is running): HP-UX Cell Manager: • /var/adm/sw/swinstall.log • /var/adm/sw/swagent.log (for more details) Windows clients (on the system where the setup is running): • Temp\SetupLog.
where Temp is a directory specified in the TEMP environment variable and SystemRoot is a directory specified in the SystemRoot environment variable. In case the setup log files are not created, run the remote installation with the debug option. See “Creating installation execution traces” on page 160.
Creating installation execution traces Run the installation with the debug option if this is requested by the HP Customer Support Service. For more information on debugging, including the debug options below, and preparing data to be sent to the HP Customer Support Service, see the online Help.
A Appendix A Application Recovery Manager A.06.10 product structure and licenses This appendix explains the Application Recovery Manager product structure in detail, so that product numbers to be ordered can be easily identified. The product structure is shown in Figure 43 on page 162. When ordering an Application Recovery Manager solution, go through the sections as follows: 1. Select a Cell Manager Pack. 2. Identify what other functionality you need.
Figure 43 HP Application Recovery Manager software product structure Cell Manager pack Table 9 HP Application Recovery Manager software starter pack license numbers T4395A CD and LTU for Windows T5404A CD and LTU for UNIX The Cell Manager Pack license-to-use (LTU) includes the license for: • one Cell Manager Media Application Recovery Manager A.06.10 is delivered with two CDs (UNIX and Windows). Manuals All manuals are available electronically on CDs and at http://www.hp.com/support/ manuals.
Functional extensions The tables in this section contain Application Recovery Manager A.06.10 Functional Extension license numbers. Table 10 HP Application Recovery Manager software on-line extension T5405A for UNIX T4396A for Windows The On-line Extension license-to-use (LTU) includes the license to perform on-line backup of databases and applications running on the specified platform. • If a system runs multiple partitions, this LTU is required for each partition.
License migration to Application Recovery Manager A.06.10 Migration from previous versions of Application Recovery Manager is as follows: Application Recovery Manager A.06.00 Migrate directly to Application Recovery Manager A.06.10. No license migration is required or any other kind of migration. Application Recovery Manager A.06.00 customers on support contract will receive Application Recovery Manager A.06.10 free of charge. Once you upgrade your environment to Application Recovery Manager A.06.
The common fields in the licensing forms that you are required to fill out are briefly described beneath: Personal Data This field contains customer information, including to whom the new password should be delivered. Licensing Data Provide licensing information about your Application Recovery Manager cell. Current Cell Manager Enter the required information about your current Cell Manager. New Cell Manager Enter the required information about your New Cell Manager.
Product License Type 166 Appendix A In the fields next to the Product Numbers, enter the quantity of licenses you want to install on this Cell Manager. The quantity can be all or a subset of the licenses purchased with the Order Number.
B Appendix B In this appendix This Appendix provides some additional information about tasks that are beyond the scope of this guide but strongly influence the installation procedure. Examples are given of system setup and configuration for Windows and HP-UX systems. Installing on HP-UX systems using native tools NOTE: The native installation procedure on HP-UX is only documented if you intend to install an Installation Server with a limited set of packages.
2. In the Specify Source window, select Network Directory/CDROM, and then enter: • On a PA-RISC based HP-UX: Mountpoint/APPRM_DEPOT/APPRM_A0610_UX11x.sd_depot • On a IA-64 based HP-UX: Mountpoint/APPRM_DEPOT/APPRM_A0610_UXia64.sd_depot in the Source Depot Path. Then click OK to open the SD Install - Software Selection window. 3. In the list of available software packages for the installation, the Application Recovery Manager product is displayed under the name T5404A.
Figure 44 SD install - software selection window NOTE: If you want to install software from a tape device across the network, you first need to mount the source directory on your computer. Installing an Installation Server 1. Insert and mount the UNIX installation CD-ROM. 2. At the command line, type /usr/sbin/swinstall to run the installation program. 3.
5. From the Actions menu, click Install (analysis). Click OK to proceed. When the installation is finished, the software depot for UNIX is located in the /opt/omni/databases/vendor directory. IMPORTANT: If you do not install the Installation Server for UNIX on your network, you will have to install every UNIX client locally from the UNIX installation CD-ROM. Installing the clients The clients are not installed during a Cell Manager or Installation Server installation.
• The Subnet mask for each network adapter card installed on the computer, which, combined with IP address, identifies the Network ID and the host ID. The Subnet mask is displayed in the same format as the IP address. • The Default Gateway address is required for the default local gateway (IP router) to enable Internet access.
2. Click Properties and double-click Internet Protocol (TCP/IP). You can then edit IP settings. Figure 45 The TCP/IP properties window on Windows To edit advanced settings, click Advanced.
Figure 46 Advanced TCP/IP settings on Windows DNS suffix To configure the DNS suffix, right-click the My Computer icon on the desktop and then click Computer Name > Change > More. The new DNS settings will take effect after the system is rebooted.
Figure 47 The DNS suffix and NetBIOS computer name on Windows Checking the TCP/IP setup An important aspect of the TCP/IP configuration process is the setup of a hostname resolution mechanism. • If using hosts files, located in the %SystemRoot%\system32\drivers\etc folder, each system in the cell must be able to resolve the address of the Cell Manager. The Cell Manager must be able to resolve the names of all systems in the cell.
4. If the previous steps have worked successfully, you are ready to test the name resolution. Enter the name of the system while running the ping command to test the hosts file and/or DNS. If your machine name was kesukozi, and the domain name was campo.com, you would enter: ping kesukozi.campo.com. If this does not work, refer to “Installing and configuring the TCP/IP protocol on Windows” on page 171, for steps required to access the TCP/IP Properties window. Here, verify that the domain name is correct.
5. After Application Recovery Manager has been installed and an Application Recovery Manager cell has been created, you can use the DNS check tool to check that the Cell Manager resolves DNS connections to all other clients in the cell properly and vice versa. You do that by running the omnicheck -dns command from the AppRM_home\bin directory. Failed checks and the total number of failed checks are listed. For details, see “Verifying DNS connections within Application Recovery Manager cell” on page 150.
On UNIX On a UNIX Cell Manager, do the following: 1. Change the Cell Manager hostname entries in the following files: /etc/opt/omni/client/cell_server /etc/opt/omni/server/users/UserList 2. Verify that Name Resolution works among the members of an Application Recovery Manager cell. 3. Change the Cell Manager name in the IDB by running: /opt/omni/sbin/omnidbutil -change_cell_name [old_host] On Windows On a Windows Cell Manager, do the following: 1.
UNIX Follow these steps to change the port number on a UNIX system: • Before you install the Cell Manager: Create the file with the required port number. • After you installed the Cell Manager: 1. Edit the /etc/services file. By default, this file should contain the entry: omni 5555/tcp # APPRM Replace the number 5555 with an unused port number. 2.
2. Expand HKEY_LOCAL_MACHINE, Software, Hewlett-Packard, OpenView, OmniBack, and select Common. 3. Double-click InetPort to open the Edit String dialog box. In the Value data text box, enter an unused port number. The same must be done in the Parameters subfolder of the Common folder. 4. In the Windows Control Panel, go to Administrative Tools, Services, then select the Application Recovery Manager Inet service, and restart the service (click the Restart icon on the toolbar).
Command Subcommand/option Status -put -get -init -check -show -purge -delete -reference -sync_check -exclude -include -namespace OBSOLETED OPTIONS –sap -appname –user –group -keep_files NEW OPTIONS FOR SAP INTEGRATION –recover –open –resetlogs –preview omnir -oracle -appname –user –group –recover –open –resetlogs –preview -parallelism 180 Appendix B NEW OPTIONS FOR ORACLE INTEGRATION
Command Subcommand/option Status -manual_restore -appsrv NEW OPTIONS FOR VSS INTEGRATION -target_tree -exch_RSG -target_dir NEW OPTIONS FOR ENTERPRISE VIRTUAL ARRAY VSS INTEGRATION -copy_back -diskarray_wait -no_retain_source –copyback –switch NEW OPTIONS FOR ENTERPRISE VIRTUAL ARRAY INTEGRATION -leave_source -no_leave_source -check_config -no_check_config -force_prp_replica -copy_back -no_retain_source -no_diskarray_wait -keep_version -check_config NEW OPTIONS FOR DISK ARRAY XP VSS INTEGRATION NEW
Appendix B
Glossary access rights See user rights. Active Directory (Windows specific term) The directory service in a Windows network. It contains information about resources on the network and makes them accessible to users and applications. The directory services provide a consistent way to name, describe, locate, access and manage resources regardless of the physical system they reside on. application agent A component needed on a client to back up or restore online database integrations.
Application Recovery Manager software. For backup and restore, SAP R/3 programs issue orders for the Application Recovery Manager backint interface. 184 backup object A backup unit that contains all items backed up from one disk volume (logical disk or mount point). The backed up items can be the entire disk or mount point. Additionally, a backup object can be a database/application entity or a disk image (rawdisk).
By Type - according to the type of data available for backups/templates. Default view. By Group - according to the group to which backup specifications/templates belong. By Name - according to the name of backup specifications/templates. BC (HP StorageWorks Disk Array XP specific term) The Business Copy XP allows to maintain internal copies of HP StorageWorks Disk Array XP LDEVs for purposes such as data backup or data duplication.
BRRESTORE (SAP R/3 specific term) An SAP R/3 tool that can be used to restore files of the following type: • Database data files, control files, and online redo log files saved with BRBACKUP • Redo log files archived with BRARCHIVE • Non-database files saved with BRBACKUP You can specify files, tablespaces, complete backups, log sequence numbers of redo log files, or the session ID of the backup. See also SAPDBA, BRBACKUP, and BRARCHIVE.
client or client system Any system configured with any Application Recovery Manager functionality and configured in a cell. cluster-aware application It is an application that supports the cluster Application Programming Interface. Each cluster-aware application declares its own critical resources (disk volumes (on Microsoft Cluster Server), volume groups (on MC/ServiceGuard), application services, IP names and addresses, and so on).
See also HP StorageWorks EVA SMI-S Agent and HP StorageWorks SMI-S EVA provider. 188 container (HP StorageWorks EVA specific term) Space on a disk array, which is pre-allocated for later use as a snapclone. control file (Oracle and SAP R/3 specific term) An Oracle data file that contains entries specifying the physical structure of the database. It provides database consistency information used for recovery.
DMZ The Demilitarized Zone (DMZ) is a network inserted as a "neutral zone" between a company's private network (intranet) and the outside public network (Internet). It prevents outside users from getting direct access to company servers in the intranet. DNS server In the DNS client-server model, this is the server containing information about a portion of the DNS database that makes computer names available to client resolvers querying for name resolution across the Internet.
nodes using three physical topologies: point-to-point, loop, and switched. 190 filesystem The organization of files on a hard disk. first-level mirror (HP StorageWorks Disk Array XP specific term) HP StorageWorks Disk Array XP allows up to three mirror copies of a primary volume and each of these copies can have additional two copies. The three mirror copies are called first-level mirrors. See also primary volume and MU number.
storage. This balances the need for fast retrieval from hard disk with the lower cost of optical platters. Holidays file A file that contains information about holidays. You can set different holidays by editing the Holidays file: /etc/opt/omni/server/Holidays on the UNIX Cell Manager and AppRM_home\Config\Server\holidays on the Windows Cell Manager. HP StorageWorks Disk Array XP LDEV A logical partition of a physical disk within an HP StorageWorks Disk Array XP.
restore. The Inet service is started as soon as Application Recovery Manager is installed on a system. The Inet process is started by the inetd daemon. 192 Information Store (Microsoft Exchange Server specific term) The Microsoft Exchange Server service that is responsible for storage management. Information Store in Microsoft Exchange Server manages two kinds of stores: mailbox stores and public folder stores. A mailbox store consists of mailboxes that belong to individual users.
operator. This implies that no operator personnel is present to work with the backup application. Local Continuous Replication (Microsoft Exchange Server specific term) Local continuous replication (LCR) is a single-server solution that creates and maintains an exact copy (LCR copy) of a storage group. An LCR copy is located on the same server as the original storage group. When an LCR copy is created, it is kept up to date through change propagation (log replay) technology.
• user_name is the name by which a user is known to Oracle Server and to other users. Every user name is associated with a password and both have to be entered to connect to an Oracle Target Database. This user must have Oracle SYSDBA or SYSOPER rights. • password must be the same as the password specified in the Oracle password file (orapwd), which is used for authentication of users performing database administration.
Microsoft Exchange Server A “client-server” messaging and a workgroup system that offers a transparent connection to many different communication systems. It provides users with an electronic mail system, individual and group scheduling, online forms, and workflow automation tools. It provides a developer with a platform on which to build custom information-sharing and messaging-service applications.
offline redo log See archived redo log. online backup A backup performed while a database application remains available for use. The database is placed into a special backup mode of operation for the time period that the backup application requires access to the original data objects. During this period, the database is fully operational, but there may be a small performance impact and log files may grow very quickly.
• COPY - The mirrored pair is currently re-synchronizing. Data is transferred from one disk to the other. The disks do not contain the same data. • PAIR - The mirrored pair is completely synchronized and both disks (the primary volume and the mirrored volume) contain identical data. • SUSPENDED - The link between the mirrored disks is suspended. That means that both disks are accessed and updated independently.
public folder store (Microsoft Exchange Server specific term) The part of the Information Store that maintains information in public folders. A public folder store consists of a binary rich-text .edb file and a streaming native internet content .stm file.
replica (ZDB specific term) An image, at a particular point in time, of the data in source volumes that contain user-specified backup objects. Depending on the hardware or software with which it is created, the image may be an independent exact duplicate (clone) of the storage blocks at the physical disk level (for example, a split mirror or snapclone), or a virtual copy (for example, a snapshot).
SAPDBA (SAP R/3 specific term) An SAP R/3 user interface that integrates the BRBACKUP, BRARCHIVE, and BRRESTORE tools. Scheduler A function that controls when and how often automatic backups occur. By setting up a schedule, you automate the start of backups. secondary volume (S-VOL) (HP StorageWorks Disk Array XP specific term) secondary volumes, or S-VOLs, are XP LDEVs that act as a secondary BC mirror of another LDEV (a P-VOL).
shared disks A Windows disk on another system that has been made available to other users on the network. SMBF The Session Messages Binary Files (SMBF) part of the IDB stores session messages generated during backup and restore sessions. One binary file is created per session. The files are grouped by year and month. snapshot (HP StorageWorks EVA specific term) A form of replica produced using snapshot creation techniques.
(the mirror is split) and a split mirror replica of the source volumes at the time of the split remains in the target volumes. See also split mirror. 202 SSE Agent (HP StorageWorks Disk Array XP specific term) An Application Recovery Manager software module that executes all tasks required for a split mirror backup integration. It communicates with the HP StorageWorks Disk Array XP storing system using the RAID Manager XP utility.
tablespace A part of a database structure. Each database is logically divided into one or more tablespaces. Each tablespace has data files or raw volumes exclusively associated with it. target volume (ZDB specific term) A storage volume to which data is replicated. Terminal Services (Windows specific term) Windows Terminal Services provide a multi-session environment that allows clients to access a virtual Windows desktop session and Windows-based programs running on the server.
transportable snapshot (Microsoft VSS specific term) A shadow copy that is created on the application system and can be presented to the backup system. See also Microsoft Volume Shadow Copy Service (VSS). unattended operation See lights-out operation.
Virtual disks are the entities that are replicated using the HP StorageWorks Enterprise Virtual Array snapshot functionality. See also source volume and target volume. virtual server A virtual machine in a cluster environment defined in a domain by a network IP name and address. Its address is cached by the cluster software and mapped to the cluster node that is currently running the virtual server resources. This way all requests for a particular virtual server are cached by a specific cluster node.
used in operating systems as a means of specifying more than one file by name. 206 Windows Registry A centralized database used by Windows to store configuration information for the operating system and the installed applications. WINS server A system running Windows Internet Name Service software that resolves Windows networking computer names to IP addresses. writer (Microsoft VSS specific term) A process that initiates change of data on the original volume.
Index Symbols Cell Manager troubleshooting, 38 A A.06.00 migrating licenses, 164 A.06.
Cell Manager automatically configured files, on UNIX, 37 Cell Request Server (CRS) service, 47 Cell Request Server (CRS) service, 38 changing the name, 176 changing software components, 117 checking configuration changes, 127 choosing the system, 26 choosing the system, 27 concepts, 21 directory structure, on UNIX, 35 functions, 26 installation prerequisites, on UNIX, 33 installation prerequisites, on Windows, 39 installation sequence, 31 installing, on HP-UX, 34 installing, on HP-UX, using native tools, 16
client, installing HP StorageWorks Disk Array XP integration, 79 HP StorageWorks EVA integration, 79 Microsoft Volume Shadow Copy integration, 75 on MC/ServiceGuard systems, 81 on Microsoft Cluster Server systems, 89 cluster changing software components, 118 changing software components, 118 importing to a cell, 94 installing Cell Manager, 81 installing clients, 89 Microsoft Cluster Server, exporting from a cell, 97 uninstalling, 114 command, 138, 177 command-line interface (CLI), 22, 27 commands CLI change
domain name system See DNS DVD-ROM list of installation DVD-ROMs, 25 E enabling access verification on a cell, 104 on a client, 102 environment variables, setting on UNIX Cell Manager, 38 execution trace files creating, 160 debug option, 160 exporting clients, 96 Microsoft Cluster Server client, 97 F Fast Recovery Solution (FRS), 40, 67 files allow_hosts, 104 allow_hosts, 105, 106 deny_hosts, 106 services, 177 FRS See Fast Recovery Solution (FRS) See Fast Recovery Solution (FRS) Functional Extensions, lic
installation client installation, overview, 57 components See installation components creating execution trace files, 160 debugging, 160 general steps, 23 log files, 157 overview, 21 remote installation, overview, 58 remote, concepts, 24 software component codes, 73 software components, 64 troubleshooting clients, on UNIX, 154 troubleshooting clients, on Windows, 156 troubleshooting, on Windows, 153 verifying clients, 156 installation components Installation Server, 21 Installation Server installation seque
installing clients on HP-UX systems, 71 on MC/ServiceGuard systems, 81 on Microsoft Cluster Server systems, 89 on UNIX systems, 72 on Windows systems, 66 installing Installation Server overview, 48 installing Installation Server on HP-UX systems, using native tools, 169 integrations, installing HP StorageWorks Disk Array XP integration, 79 HP StorageWorks EVA integration, 79 Microsoft Volume Shadow Copy integration, 75 IP address, TCP/IP, 170 L license-to-use.
log files checking, installation, 157 description, 159 inet.log, 104 location, 159 LTU, 138 M MC/ServiceGuard installing Cell Manager, 80 installing clients, 81 Microsoft Cluster Server exporting, 97 importing, 94 installing Cell Manager, 81 installing clients, 89 upgrading Cell Manager, 129 upgrading clients, 131 Microsoft Installer, 122, 129 Microsoft Terminal Services Client, 40 Microsoft Volume Shadow Copy integration, installing, 75 migrating licenses, 164 moving licenses, 146 MSI.
R Raima Database Server (RDS) service, 38 Raima Database Server (RDS) service, 47 RDS See Raima Database Server (RDS) service related licenses, 134 related documentation, 13 remote installation clients, 58 removing access verification on a client, 106 Application Recovery Manager software manually, from UNIX, 116 software components, from UNIX, 118 software components, from Windows, 117 software components, overview, 117 reporting licenses, 133 S SAP R/3 integration, 76 securing cell, 104 client, 102 secur
troubleshooting installation Application Recovery Manager software, on Windows, 153 Cell Manager, on UNIX, 38 Cell Manager, on Windows, 47 clients, on HP-UX, 155 debug option, 160 debugging, 160 log files, 157 omnicheck command, 150 remote installation, on UNIX, 154 remote installation, on Windows, 156 swagent daemon, 155 troubleshooting upgrade Application Recovery Manager software, on Windows, 153 Microsoft Installer problems, 153 U uninstallation Oracle integration specifics, 119 overview, 112 prerequis
V verifying client installation, 156 DNS connections in a cell, 150 licensing passwords, 145 patches, 110 views, graphical user interface, 28 virtual server, importing to a cell, 94 W websites HP Subscriber's Choice for Business, 19 HP , 19 product manuals, 13 Windows Cell Manager installing, 39 Windows Cell Manager installation prerequisites, 39 troubleshooting, 153, 157 troubleshooting installation, 47 uninstalling, 114 Windows client installing, 66 troubleshooting, 153, 156, 157 uninstalling, 113 216
