1-Touch for HP-UX

Prerequisites
License Requirements
Installations
Configuration

Overview

1-Touch for HP-UX allows you to recover systems with defective components (e.g., inaccessible root, crashed disk) quickly and efficiently. The feature can recover systems without requiring the reinstallation of operating system files that have been lost. 1-Touch uses file system restore capabilities. It restores the data backed up by the default backup set that is configured for 1-Touch.

The feature involves a 1-Touch server, specifically an HP-UX Ignite Server, which is used to boot the 1-Touch client. The 1-Touch server provides the Internet Protocol (IP) address, boot parameters, and files for the 1-Touch clients to be booted. In effect, the 1-Touch server secures the required information from the 1-Touch client's backup and then uses this information to recreate the client's environment. The 1-Touch server and the 1-Touch client need not be in the same subnet; if the client is in a different subnet, data can still be recovered over the network by using an Ignite Server with the help of a boot helper (provided by Hewlett-Packard).

The boot image provided by the Ignite server is called the Ignite-UX image. During a 1-Touch backup, the Ignite-UX image is backed up. During the 1-Touch recovery, the image is restored to the 1-Touch server and then used for the recovery.

Support

For the list of supported Operating Systems, see System Requirements - 1-Touch for Unix.
This feature is not supported when bootable partitions are on the disk arrays (snapable disk).

Setting up 1-Touch for HP-UX

Prerequisites

1-Touch Server and the client must have the same processor. For the list of supported processors, see System Requirements - 1-Touch for Unix.
The latest Ignite-UX software must be installed on both the 1-Touch servers and the 1-Touch clients. Ensure that the same version of this software is installed on both the servers and the clients.
Ensure that the remsh process is running on the 1-Touch client to enable a network boot from the 1-Touch server. If this process is not running, you must manually reboot the client and perform the network recovery.
Ensure that the same version of NFS PV3 is installed on the 1-Touch servers and 1-Touch clients.

License Requirements

This feature requires a Feature License to be available in the CommServe^® Server.

Review general license requirements included in License Administration. Also, View All Licenses provides step-by-step instructions on how to view the license information.

The 1-Touch feature requires the following licenses:

Boot Server on Unix
iDataAgent for Hewlett Packard HP-UX File System

Installations

Install the product 1-Touch server software (CVGx1Touch) on the 1-Touch server. See Install the 1-Touch Server Software for step-by-step instructions.

Install the HP-UX File System iDataAgent on the client computer. See Install the Unix File System iDataAgents for information on installing the HP-UX File System iDataAgent.

Configuration

Configure the Subclient for 1-Touch

The 1-Touch data is backed up by the default subclient of the default backup set. When you install the File System iDataAgent, you must configure the default subclient for 1-Touch.

Required Capability: See Capabilities and Permitted Actions

To configure the subclient for 1-Touch:

From the CommCell Browser, right-click the appropriate (usually the default) subclient and then click Properties from the shortcut menu.
From the Subclient Properties (1-Touch Recovery) tab, click 1-Touch Recovery.
If appropriate, from the same tab, accept or select the name of the 1-Touch server in the 1-Touch server field. Also, accept or type the path to the 1-Touch server directory in the 1-Touch server directory field.
Click OK.

While configuring the subclient, enter the location of the ignite server in the 1-Touch server directory field. Typically, the location of the the ignite server is as follows: /var/opt/ignite/clients/

Run a Backup

Start or Schedule regular full backups for default backup set that has been configured for 1-Touch. Ensure that you have run at least a full backup for default backup set that has been configured for 1-Touch.

To start a full backup see, Start a Backup.

To schedule a full backup see, Schedule Backups.

Recovering Data in Case of Disaster

Before you begin

If you replaced the 1-Touch client’s network card after the 1-Touch backup, be sure to update the 1-Touch server with the new MAC address before you start the 1-Touch recovery.
Try to avoid the unconditional overwrite of the root directory on a live file system. This is a mechanism that allows an unconditional overwrite of open files in the root directory (/) on a live file system. Performing such a restore can result in an inconsistent system that may also fail to boot. Use this option AT YOUR OWN RISK.

You can recover the system to a specific system state level based on an identified backup job or on data that was backed up before an identified date.

Use the following procedure to recover the system to a specific level.

Required Capability: See Capabilities and Permitted Actions

To recover the system to a specific level:

From the CommCell Console, right-click the appropriate backup set, click All Tasks, and then click 1-Touch Recovery to access the Submit 1-Touch Recovery Request wizard.
In the Select a Job step, select the backup job from which you want to restore the data and then click Next. The most recent backup job will be displayed at the top of the list. This information will be used to restore the operating system.
In the Select Recovery Options step, click the appropriate fields to select your options. If desired, click Advanced to set any additional restore options and then click OK. Then click Next. This information will be used to restore the data.
In the Summary step, review the options that you selected. As appropriate, use the Back and Next buttons to navigate to and change options in the affected dialog boxes.
When you are finished, go to the Summary dialog box and click Finish. The recovery should complete.

The 1-Touch client should typically be running the HP-UX operating system. However, if the client does not have this operating system, it can still be recovered by using an Ignite Server with the help of a boot helper (provided by Hewlett-Packard).