features - 1-touch - bull on-line support...

Features - 1-Touch

Table of Contents Overview

System Requirements

System Requirements - 1-Touch for Unix

System Requirements - 1-Touch for Windows

Installation

Install the 1-Touch Server Software - Unix

Install the 1-Touch Server Software - Windows

Setting Up 1-Touch

1-Touch for AIX

1-Touch for HP-UX

1-Touch for Linux

1-Touch for Solaris

1-Touch for Windows

Recovering Data

1-Touch for AIX

1-Touch for HP-UX

1-Touch for Linux

1-Touch for Solaris

1-Touch for Windows

Global File System Recovery (Clusters)

1-Touch for Solaris

Restoring the System to a Specific Level

1-Touch for Solaris

Features - 1-Touch

of 74

1-Touch - General Information

1-Touch is a highly-automated method for recovering your system in case of a disaster. 1-Touch is an enhanced variation of the Bare Metal Restore (BMR) procedure that is commonly used in industry to recover systems. 1-Touch allows you to recover systems without manually reinstalling individual software packages (including operating systems), and it is available on the Windows platform as well as on various Unix platforms. Depending on your 1-Touch version, you can use the CommCell Console or the appropriate wizard to set up and run a 1-Touch Recovery. 1-Touch tasks are centralized, highly-automated, and easy to perform.

For more information, see the following:

1-Touch for AIX

1-Touch for HP-UX

1-Touch for Linux

1-Touch for Solaris

1-Touch for Windows

1-Touch feature does not support Single Sign On.

Features - 1-Touch

of 74

System Requirements - 1-Touch for Unix

The following requirements are for 1-Touch Server and Client on:

Operating System Processor

AIX AIX 5.2 32-bit and 64-bit with technology level 10 (or higher) and runtime library xlC.rte 8.0.0.0 or higher

AIX 5.3 32-bit and 64-bit with technology level 6 (or higher) and runtime library xlC.rte 8.0.0.0 or higher

AIX 6.1 64-bit with technology level 2

Power PC (Includes IBM System p)

HP-UX HP-UX 11i v1 (11.11) with a minimum of OS patch PHCO29328 (contact Hewlett Packard to obtain the patch)

HP-UX 11i v2 (11.23)

HP-UX 11i v3 (11.31)

PA-RISC

HP-UX 11i v2 (11.23)

HP-UX 11i v3 (11.31)

Intel Itanium

Linux Red Hat Enterprise Linux

Red Hat Enterprise Linux 3.x with glibc 2.3.x



SuSE Linux

SuSE Linux 9.x with glibc 2.3.x

SuSE Linux 10.x with glibc 2.4.x

Intel Pentium, Intel Itanium, x64 or compatible processors

Solaris Solaris 8 32-bit with Service Packs 108434-09, 108435-09, and 109147-20

Solaris 8 64-bit with Service Packs 108434-09, 108435-09, and 109147-20

Solaris 9 4/04 32-bit

Solaris 9 4/04 64-bit

Solaris 9 32-bit

Solaris 9 64-bit

Solaris 10 64-bit

Sun Sparc5 or higher recommended

Cluster Support

See Clustering - Support

Hard Disk

Features - 1-Touch

of 74

AIX

The 1-Touch Server requires 2 GB of disk space per client for the 1-Touch client configuration files.

HP-UX

The 1-Touch Server requires 2 GB of disk space per client for the 1-Touch client configuration files.

The 1-Touch Client requires 2 GB of disk space per client.

Linux

The 1-Touch Server requires 2GB of disk space per client on 1-Touch server NFS share for 1-Touch client configuration files.

The 1-Touch Client requires 500 MB of disk space for 1-Touch client configuration files.

Solaris

The 1-Touch Server and client requires 500 MB of disk space.

Peripherals

A CD-ROM burner and software to convert the ISO image to a bootable CD-ROM are required for the 1-Touch Server.

A CD-ROM drive or ability to boot from an ISO image file is required to boot the 1-Touch client for recovery.

Miscellaneous

For Memory and other requirements, see System Requirements - Unix File System iDataAgent.

The File System iDataAgent will be automatically installed during installation of the 1-Touch server software, if it is not already installed. For System Requirements specific to the File System iDataAgent, refer to System Requirements - Unix File System iDataAgent.

If you have SELinux enabled on the client computer, create the SELinux policy module as a root user before performing a backup. The SELinux Development package must be installed on the client.

To create SELinux policy module, perform the following steps as user "root":

1. Create the following files in the /usr/share/selinux/devel directory:

File Name Content of the file<directory>/<file_name>.te

where:

<directory> is /usr/share/selinux/devel

<file_name> is the name of the Unix file, created to save the policy module statement. It is a good idea to use the same name for policy module and the file.

For example: When you are creating a policy module for backup_IDA application, you can use the following file name: backup_IDA.te

The content of the file should be as follows:

policy_module(<name>,<version>)

##############################

where:

<name> is the name of the policy module. You can give any unique name to the policy module, such as a process or application name.

<version> is the version of the policy module. It can be any number, such as 1.0.0.

For Example: While creating a policy module for the backup_IDA application, you can use the following content.

policy_module(backup_IDA,1.0.0)

Features - 1-Touch

of 74

2. Create the policy file from command line. Use the following command. Ensure that you give the following commands in the /usr/share/selinux/devel directory.

[root]# make backup_IDA.pp

Compiling targeted backup_IDA module

/usr/bin/checkmodule: loading policy configuration from tmp/backup_IDA.tmp

/usr/bin/checkmodule: policy configuration loaded

/usr/bin/checkmodule: writing binary representation (version 6) to tmp/backup_IDA.mod

<directory>/<file_name>.fc

where:

<directory> is /usr/share/selinux/devel

<file_name> is the name of the Unix file, created to save the policy module statement. It is a good idea to use the same name for policy module and the file.

For example: When you are creating a policy module for backup_IDA application, you can use the following file name: backup_IDA.fc

The content of the file should be as follows:

Note that the following list of files is not exhaustive. If the process fails to launch, check /var/log/messages. Also, if required, add it to the following list of files.

/opt/<software installation directory>/Base/libCTreeWrapper.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libCVMAGuiImplgso -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libdb2locale.so.1 -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libdb2osse.so.1 -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libDb2Sbt.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libdb2trcapi.so.1 -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libDrDatabase.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libIndexing.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libSnooper.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

Features - 1-Touch

of 74

DISCLAIMER

Minor revisions and/or service packs that are released by application and operating system vendors may, in some cases, affect the working of our

Creating targeted backup_IDA.pp policy package

rm tmp/backup_IDA.mod tmp/backup_IDA.mod.fc

[root]# semodule -i backup_IDA.pp

[root]#

3. Execute the policy module. Use the following command:

[root]# restorecon -R /opt/<software installation directory>

SELinux is now configured to work with this application.

Notes on Client Installations

The following packages are required for 1Touch clients on Linux:

mkisofs

syslinux 2.11 (syslinux-2.11-1 is the minimum version required)

1-Touch for Unix supports the following File system and volume manager types:

Operating System

Supported File system and volume manager types

Linux Linux Logical Volume Manager (LVM) Version 2

Extent 2 File System (ext2) (Red Hat Linux)

Extent 3 File System (ext3) (Red Hat Linux)

Reiser File System (reiserfs) (SuSE Linux)

No Software RAID support AIX AIX logical Volume Manager for Root and Non- root

Volumes (LVM)

VERITAS Volume Manager for Non root Volumes (VXVM)

Journal File System (JFS) (AIX)

Enhanced Journal File System (JFS2) (AIX) HP-UX HPUX Logical Volume Manager for Root and Non-Root

volumes (LVM)

VERITAS Volume Manager for Root and Non Root volumes (VxVM)

HFS File system (HFS)

VERITAS File System (VxFS) Solaris VERITAS Volume Manager (VxVM) (unencapsulated root

volume only)

Solaris Volume Manager (svm)

UNIX File System (UFS)

VERITAS File System (VxFS) Linux Boot loader elilo (Itanium-based computers)

Features - 1-Touch

of 74

software. Although we may list such revisions and/or service packs as “supported” in our System Requirements, changes to the behavior of our software resulting from an application or operating system revision/service pack may be beyond our control. However, we will make every effort to correct such disruption as quickly as possible. When in doubt, please contact your software provider to ensure support for a specific application or operating system.

Additional considerations regarding minimum requirements and End of Life policies from application and operating system vendors are also applicable.

Features - 1-Touch

of 74

System Requirements - 1-Touch for Windows

The following requirements are for 1-Touch for Windows:

Operating System

1-Touch Server on:

Windows XP

Microsoft Windows XP Professional 32-bit and x64 Editions

Windows Server 2003

Microsoft Windows Server 2003 32-bit and x64 Editions with a minimum of Service Pack 1

Windows Vista

Microsoft Windows Vista 32-bit and x64 Editions

Windows Server 2008

Microsoft Windows Server 2008 32-bit and x64 Editions*

Microsoft Windows Server 2008 R2 Editions

*Core Editions not supported

Windows 7

Microsoft Windows 7 32-bit and x64 Editions

1-Touch Client on:

Windows XP

Microsoft Windows XP Professional 32-bit and x64 Editions

Windows Server 2003

Microsoft Windows Server 2003 32-bit, 64-bit and x64 Editions* with a minimum of Service Pack 1

Windows Vista

Microsoft Windows Vista 32-bit and x64 Editions

Windows Server 2008

Microsoft Windows Server 2008 32-bit and x64 Editions*

Microsoft Windows Server 2008 R2 Editions

*Core Editions not supported

Processor

All Windows-compatible processors supported

Memory

32 MB RAM minimum required beyond the requirements of the operating system and running applications

Hard Disk 2.6 GB minimum of hard disk space for 1-Touch software installation/ 3.4 GB recommended

Features - 1-Touch

of 74

DISCLAIMER

Minor revisions and/or service packs that are released by application and operating system vendors may, in some cases, affect the working of our

110 MB for the required File System iDataAgent/ 448 recommended

100 MB of additional hard disk space for log file growth

134 MB of temp space required for install or upgrade (where the temp folder resides)

The Distribution folders in the 1-Touch server will require the following additional disk space:

525 MB for each Microsoft Windows Distribution folder (CD images) that will be imported for client recovery

10 MB per client prepared for recovery for the 1-Touch client configuration files

Localized versions of Windows can vary in size between 300 to 370 MB, depending on the language. Other factors that affect the size of the 1-Touch Boot CD can be the set of device drivers that you include and additional components in your Boot CD image.

Peripherals

A CD-ROM burner and software to convert the ISO image to a bootable CD-ROM are required for the 1-Touch Server.

A CD-ROM drive or ability to boot from an ISO image file is required to boot the 1-Touch client for recovery.

Notes on Client Installations

TCP/IP Services configured on the computer.

The File System iDataAgent will be automatically installed during installation of the 1-Touch server software, if it is not already installed. For System Requirements install information specific to the File System iDataAgent, refer to System Requirements - Microsoft Windows File Systems.

Microsoft Visual C++ 2008 Redistributable Package is automatically installed. Note that Visual C++ 2008 Redistributable Package can co-exist with other versions of this software.

For 1-Touch Client:

Data types File System and System State are supported.

The following configurations cannot be recovered using the 1-Touch process:

Multi-operating system boot systems, unless the primary active boot partition is the active partition in the backup

A CommServe

The 1-Touch client cannot serve as the MediaAgent for performing a 1-Touch restore. If the client was performing LAN Free Backups to the MediaAgent installed on the Client, a separate MediaAgent that has access to the data is required. If you do not have a separate MediaAgent, do the following:

Install MediaAgent on a standby server that has access to the secondary storage where the 1-Touch client's data is residing

Configure the secondary storage on the standby MediaAgent using the Library and Drive Configuration tool

Unattended installation for Microsoft Windows 2003 or higher does not support installing Windows to a drive other than C:\.

Features - 1-Touch

of 74

software. Although we may list such revisions and/or service packs as “supported” in our System Requirements, changes to the behavior of our software resulting from an application or operating system revision/service pack may be beyond our control. However, we will make every effort to correct such disruption as quickly as possible. When in doubt, please contact your software provider to ensure support for a specific application or operating system.

Additional considerations regarding minimum requirements and End of Life policies from application and operating system vendors are also applicable.

Features - 1-Touch

of 74

Install the 1-Touch Server Software - Unix

Click on a link below to go to a specific section of the software installation:

Install Requirements

Install Checklist

Before You Begin

Install Procedure

Getting Started

Select Components for Installation

Base Software Installation

Firewall Configuration

Kernel Parameters

Storage Policy Selection

Enable Global Filters

Client Group Selection

Setup Complete

Post-Install Considerations


The software installs the 1-Touch server software, and this software must be installed on each 1-Touch server that may be used for this feature. For more information, see the following as appropriate:

1-Touch for AIX

1-Touch for Linux

1-Touch for Solaris

Verify that the computer in which you wish to install the software satisfies the minimum requirements specified in System Requirements - 1-Touch for Unix.

The following procedure describes the steps involved in installing the 1-Touch Server software and Unix File System iDataAgents. If you choose to install multiple components simultaneously, refer to the appropriate procedures for installation requirements and steps specific to the component. Note that when you install multiple components, the sequence of the install steps may vary.

Review the following Install Requirements before installing the software:

General Agents should be installed only after the CommServe and at least one MediaAgent have been installed in the CommCell. Also, keep in mind that the CommServe and MediaAgent must be installed and running (but not necessarily on the same computer), before you can install the Agent.

This software should be installed in a CommCell with current versions of the CommServe and MediaAgent software.

Ensure there is an available license on the CommServe for the Agent.

Verify that you have the software installation disc that is appropriate to the destination computer’s operating system.

Make sure that you have the latest software installation disc before you start to install the software. If you are not sure, contact your software provider.

Firewall

If the CommServe® Server, MediaAgent and/or Clients communicate across two-way firewall(s):

Features - 1-Touch

of 74

Ensure port 8400 is allowed connections through the firewall.

In addition a range of bi-directional ports (consecutive or discrete) must also be allowed connections through the firewall.

For information on configuring the range of ports, see Port Requirements for Two-way Firewall.

If the CommServe Server, MediaAgent and/or Clients communicate across one-way firewall(s):

Identify a range of outbound ports (consecutive or discrete) for use by the software.

For information on configuring the range of ports, see Port Requirements for One-way Firewall.

If the MediaAgent/Client communicates with the CommServe Server across a one-way firewall, you must add the MediaAgent/Client host name (or the IP address) in the CommServe computer before installing the necessary software on the MediaAgent/Client computer.

Install Checklist

Collect the following information before installing the software. Use the space provided to record the information, and retain this information in your Disaster Recovery binder.

1. Network host name:____________________________________

Client name:____________________________________

For example, green.domainname.com and green.

See Step 5 for more information.

2. Install directory location:________________________________________________________________

The default is /opt, but you may designate any location you want.

See Base Software Installation for more information.

3. Log files directory location:________________________________________________________________

The default is /var/log, but you may designate any location you want.

See Base Software Installation for more information.

4. If the CommServe Server and the client computer communicate across a firewall:

Firewall ports: ______________________________________________________________________

Hostnames and/or IP Addresses and corresponding GxCVD port numbers of computers on the other side of the firewall:______________

Keep Alive Interval minutes:____________________________________________________________

Hostname for outgoing tunnel connections:_________________________________________________

Tunnel Initialization Interval seconds:_____________________________________________________

See Firewall Configuration for more information.

5. CommServe Name and the CommServe Host Name:______________________________________

For example, orange and orange.domainname.com.

Features - 1-Touch

of 74

See Base Software Installation (continued) for more information.

6. Job result directory location:________________________________________________________________

The default is /opt, but you may designate any location you want.

See Base Software Installation (continued) for more information.

7. Storage Policy used by the default subclient:________________________________________________

See Storage Policy Selection for more information.

8. Client Group to which this Client will be associated:_____________________________________________

See Client Group Selection for more information.

Before You Begin

Log on to the client as root.

The install package requires super-user permissions to execute.

Install Procedure

Getting Started

1. Place the software installation disc for the Unix platform into the disc drive.

You can also install the product using a disc drive mounted on another computer on the network.

On Solaris, double-click the cvpkgadd program from the File Manager window.

On other Unix platforms, open the Terminal window, navigate to the software installation disc and then enter cvpkgadd.

2. The product banner and other information is displayed.

Press Enter to continue.

3. Read the license agreement. Type y and press Enter to continue.

4. This prompt is displayed only when you are installing on AIX, HP-UX, Linux, or Solaris computers.

Press Enter to continue

NOTES

When you install on non-clustered computer, you must select the number associated with the option Install on a physical machine.

Certain Calypso packages can be associated with a virtual IP, or in other words, installed on a "virtual machine" belonging to some cluster. At any given time the virtual machine's services and IP address are active on only one of the cluster's servers. The virtual machine can "fail-over" from one server to another, which includes stopping services and deactivating IP address on the first server and activating the IP address/services on the other server.

Features - 1-Touch

of 74

You now have a choice of performing a regular Calypso install on the physical host or installing Calypso on a virtual machine for operation within a cluster.

Most users should select "Install on a physical machine" here.

1) Install on a physical machine

2) Install on a virtual machine

3) Exit

Your choice: [1]

5. If you have only one network interface, press Enter to accept the default network interface name and continue.

If you have multiple network interfaces, enter the number corresponding to the network interface that you wish to use as default, and then press Enter to continue.

NOTES

The interface name and IP addresses depend on the computer in which the software is installed and may be different from the example shown.

Network interface with the following IPs have been found available on your system. One of these interfaces should be associated with the physical machine being installed. It will also be used by the CommServe to initiate connections to the physical machine. Note that you will be able to additionally customize Datapipe Interface Pairs used for the backup data traffic later in the Calypso Java GUI.

Please select the correct network interface below. 1) client (201.42.33.598) 2) hk97::489:9glg:hk8d:9490 3) client.company.com (hr90:8842:2:78:013:8ghh:hg8k:9x54)

Interface number: [1]

Verify the default network interface name.

Press Enter to accept the default network interface name and continue, or Type the default network interface name, and then press Enter to continue.

NOTES

This prompt will be displayed only when you have multiple network interfaces for the computer.

Please verify the physical machine interface name below. Make it as complete (with fully qualified domain name) as possible:

Physical Machine Host Name: [angel.company.com]

6. Specify the client name for the computer.

Press Enter to accept the default name and continue, or Enter a new client name for the computer and then press Enter to continue.

Please specify the client name for this machine. It does not have to be the network host name: you can enter any word here without spaces. The only requirement is that it must be unique on the CommServe.

Client name: [angel]


7. Enter the number corresponding to the

Install Calypso on physical machine client.company.com

Select the Calypso module that you would like to install

Features - 1-Touch

of 74

CVGx1Touch module.

NOTES

Your screen may look different from the example shown.

Components that either have already been installed, or which cannot be installed, will not be shown.

In addition, the list of modules that appear depends on the specific Unix File System in which the package is installed. (e.g., CVGxWA will appear only when the installation package is run on a Solaris computer.)


1) Media Agent <= CVGxMA 2) FileSystem iDataAgent <= CVGxIDA 3) Exit this menu

Module number: [1]

Base Software Installation

8. Select from the following:

If this is the first package to be installed on the computer, press Enter to continue.

If this is NOT the first package to be installed on the computer, this screen will not be displayed. Skip to Storage Policy Selection.

It appears that <package_name> depends on package <package_name>, which has not been installed yet.

Press <ENTER> to install <package_name> ...

9. Press Enter to continue. Here is a list and status of the dependent modules:

1) Calypso Base0 Module NOT installed

2) Calypso Base Module NOT installed

If there are any modules listed as NOT installed/upgraded, they will be installed/upgraded first.

Press <ENTER> to proceed ...

10. Specify the location where you want to install the software.

NOTES

Please specify where you want us to install Calypso binaries.

It must be a local directory and there should be at least 98MB of free space available. All files will be installed in a "calypso" subdirectory, so if you enter "/opt", the

Features - 1-Touch

of 74

The amount of free space required depends on the components selected for install, and may look different from the example shown.

Press Enter to accept the default path and continue, or Enter a path and then press Enter to continue.

Press Enter again to confirm the path.

files will actually be placed into "/opt/calypso".

Installation Directory: [/opt]

..

Calypso will be installed in /opt/calypso. Press ENTER to continue ...

11. Specify the location for the log files.

NOTES

All the modules installed on the computer will store the log files in this directory.



Press Enter again to confirm the path.

Please specify where you want to keep Calypso log files.

It must be a local directory and there should be at least 100MB of free space available. All log files will be created in a "calypso/Log_Files" subdirectory, so if you enter "/var/log", the logs will actually be placed into "/var/log/calypso/Log_Files".

Log Directory: [/var/log]

..

Calypso log files will be created in /var/log/calypso/Log_Files. Press ENTER to continue ...

12. Indicate whether you would like to launch processes with inherent database access rights.

Press Enter to assign a new group, or Type No and then press Enter to continue.

Most of Calypso processes run with root privileges, but some are launched by databases and inherit database access rights. To make sure that registry and log files can be written to by both kinds of processes we can either make such files world-writeable or we can grant write access only to processes belonging to a particular group, e.g. a "calypso" or a "dba" group.

We highly recommend now that you create a new user group and enter its name in the next setup screen. If you choose not to assign a dedicated group to Calypso processes, all temporary and configuration files will be created with -rw-rw-rw permissions.

If you're planning to backup Oracle DB you should use "dba" group.

Would you like to assign a specific group to Calypso? [yes]

Features - 1-Touch

of 74

13. If you indicated Yes in the previous step, you will be prompted for the group name that must be used to launch processes.

Enter the group name and then press Enter to continue.

Press Enter again to continue.

Please enter the name of the group which will be assigned to all Calypso files and on behalf of which all Calypso processes will run.

In most of the cases it's a good idea to create a dedicated "calypso" group. However, if you're planning to use Oracle iDataAgent or SAP Agent, you should enter Oracle's "dba" group here.

Group name: dba

REMINDER

If you are planning to install Calypso Informix, DB2, Sybase or Lotus Notes iDataAgent, please make sure to include Informix, DB2, etc. users into group "dba". Press <ENTER> to continue ...


14. If this computer communicates with the CommServe, MediaAgent and/or other clients across a firewall, type Yes, and then press Enter to continue. Proceed to the next Step.

Press Enter, if you do not wish to configure the firewall services. Proceed to the next section.

Various Calypso components need to communicate with each other: iDataAgents and MediaAgents establish connections to CommServe and talk to each other as well. If any of the involved parties are situated on the opposite sides of a firewall, Calypso should be made aware of it so that it could bind its pipeline sockets to open ports and could establish tunnels for control traffic. You must configure Calypso firewall services if there are other Calypso machines, which are expected to communicate with this one. Do you want to configure Calypso firewall services? [no]

15. Enter the port range(s), and then press Enter to continue.

NOTES

Specify the range of ports that must be used for communication between the Client and CommServe and/or MediaAgent computers. For more information on the port requirements, see Port Requirements for Two-way Firewall or Port Requirements for One-way Firewall, as applicable.

Calypso needs to know which TCP ports of this machine are available for connections initiated by machines on the other side of the firewall.

If this machine is not reachable from the other side of the firewall at all (because the FW is one-way and allows only outgoing connections), enter any unused port number here (e.g. 8600). Otherwise please consult your FW configuration for the list of open incoming ports and enter all of them here (with the exception of port 8400).

Currently there are no ports configured. Please enter a single port number or a port range (like 8600-8620) to be added to the FW configuration:

Port range: [8600-8620]

16. Enter the number corresponding to the option you wish to perform.

NOTES

If you choose option 1,

What would you like to do:

1) Add another open port or a range of ports

2) Delete an existing port or a range of ports

3) Continue with the firewalled host setup

Your choice: [3]

Features - 1-Touch

of 74

refer the previous step.

If you choose option 3, proceed to the next step.

17. Enter the host name(s) of the computers that will need to be contacted through a firewall, and then press Enter to continue.

We need to know which Calypso hosts are located on the other side of the firewall, and whether the firewall will allow direct or reverse connections to/from those hosts.

You can specify hosts by either entering their names, IP addresses or name/IP wildcards. The wildcards are available only if the firewall is symmetrical, i.e. allows to open connections to certain ports both ways.

Currently there are no firewall hosts configured.

Please enter the name or IP address of a host on the other side of the firewall. If the firewall is symmetrical, you are allowed to use wildcards, i.e. things like 192.168.* or *.firewall.company.com:

Firewalled Host: lavender.company.com

18. Choose the option associated with type of firewall configuration based on the firewall setup in your environment.

NOTES

Choose Two-way (symmetrical) firewall if you can open certain ports as bi-directional ports.

Choose One-way firewall; <port> is reachable from here if this computer communicates with MediaAgent/Client on the other side of the firewall.

Choose One-way firewall; this machine is reachable from <port> when the CommServe and any Clients/MediaAgents) communicates with this computer.

Please specify the type of the firewall separating this machine from 172.19.61.89.

1) Two-way (symmetrical) firewall

2) One-way firewall, 172.19.61.89 is reachable from here

3) One-way firewall, this machine is reachable from 172.19.61.89

Your choice: [1]

19. Enter the number corresponding to the option you wish to perform.

NOTES

If you choose option 1,

What would you like to do:

1) Configure another host

2) Delete an existing host

3) Continue with the firewall keep-alive setup

Your choice: [3] 1

Features - 1-Touch

of 74

refer the previous two steps.

If you choose option 3, proceed to the next step.

20. If desired, modify the Keep Alive interval, and then press Enter to continue, or Press Enter to accept the default.

Please specify Keep Alive interval for Calypso firewall services.

Many firewalls disconnect idle Network connections after some period of time. Some of the Calypso Services need continuous connections. Calypso keeps such connections active by sending periodic "keep-alive" packets. Consult your firewall documentation, or contact your Network Administrator, for the exact value after which idle connections will be closed (snip time). Then enter a value, which is at least one minute less than the snip time.

Keep-alive interval, minutes [5]

21. To configure advanced firewall settings, type Yes, and then press Enter. Proceed to the next Step.

If you do not want to configure advanced firewall settings, type No, and then press Enter. Proceed to the next section.

The Generic part of the Calypso Firewall Config has been completed successfully. There are some additional advanced settings that you may want to review now. All of them can be customized later by editing the .properties file under /etc/CommVaultRegistry/Galaxy/Instance003/Firewall.

Would you like to review the advanced settings now? [no]

22. To bind the local end of tunnel connections to a specified interface, type Yes, and then press Enter. Proceed to the next Step.

If you do not want to bind the local end of tunnel connections to a specified interface, type No, and then press Enter. Skip the next Step.

Normally Calypso Firewall code doesn't bind local end of TCP/IP sockets when establishing outgoing tunnel connections relying on the OS to pick correct interface and arbitrary port automatically. Usually this doesn't cause connectivity problems because we require that the firewall must allow connections for as long as 1meither source or destination socket end is bound to one of the ports in the open range.

Sometimes, however, on hosts with several NICs it's important to force the OS to bind the local socket end to a specific network interface. There is a Calypso setting called 1mnBIND_BEFORE_CONNECT_IFACEm, which enables this behavior. If present, Calypso will bind the local end of tunnel connections to the specified interface.

Would you like to configure nBIND_BEFORE_CONNECT_IFACE? [no]

23. Type a number corresponding to one of the listed network interfaces, to use for outgoing tunnel connections through the firewall.


Please select network interface that should be used for all outgoing tunnel connections:

1) <ip_address>

Interface number: [1]

24. If desired, modify the When tunnel to a destination machine cannot be

Features - 1-Touch

of 74

Tunnel Initialization interval by typing a number.


established because the machine is down or is not accepting connections, Calypso will retry the connection after some time. Tunnels piercing one-way firewalls are 1mPERSISTENTm meaning that Calypso will keep on trying to initialize them until success. These attempts can generate a lot of network traffic if a central machine (e.g. CommServe) suddenly goes down.

Here you can adjust the interval (called 1mnTUNNEL_INIT_INTERVALm in registry) between tunnel init attempts.

Tunnel Init Interval, seconds, [5]

Base Software Installation (continued)

25. Type the name of the CommServe computer and press Enter to continue.

NOTES

Ensure that the CommServe is accessible before typing the name; otherwise the installation will fail.

If you enter a short name which resolves to the same IP address as the fully qualified CommServe name, you will be asked if you would prefer to use the fully qualified name.

Please enter the hostname of the Calypso CommServe. It can be either short or long; the only requirement is that it must be resolvable by the name services configured on this machine.

CommServe Name:

26. Enter the username and password information for an external domain user account or a CommCell user account. This authorizes the installation of an agent on the CommCell.

NOTES

This is only displayed when the Authentication for Agent feature is enabled in the CommCell Properties. Users must belong to a User Group with Agent Management capabilities to enable this feature. For more information, see

Enter your CommCell user name and password:

User Name :

Password :

Press <ENTER> to continue ...

Features - 1-Touch

of 74

Authentication for Agent Installs.

Click Enter to continue.

27. Specify the location of the job results directory.

NOTES

All the agent modules installed on the computer uses the job results directory to store the backup and restore job results.



Please specify the name for the JobResults directory.

It must be a local directory and there should be at least 20MB of free space available. It will be used to store intermediate data that should be passed from one backup phase to another.

JobResults Directory: [/test1]

Kernel Parameters

28. Enter the appropriate number of streams, and then press Enter to continue, or Press Enter to accept the default number of streams and continue.

NOTES

The number of streams specified ensures that concurrent backup/restore streams would have sufficient system resources. For more information on the subject, see Configuring Kernel Parameters (Unix/Macintosh).

This prompt is relevant only when you install/upgrade on a Macintosh or Solaris computer as appropriate.

Please enter the total number of streams that you plan to run at the same time. We need to make sure that you have enough semaphores and shared memory segments configured in /etc/system.

Number of streams: [10]

29. Indicate whether you We now need to modify the /etc/system configuration file

Features - 1-Touch

of 74

would like modifications to be made to the /etc/system configuration file.

Type Yes, and then press Enter to automatically update the file and continue, or Press Enter to accept the default No and continue (if you do not want to automatically update the file).

This prompt is displayed only when you install/upgrade on a Solaris or Macintosh computer.

on this computer. It is done to make sure that there will be enough shared memory and semaphores available for Calypso programs.

Please review the changes below and answer "yes" if you want us to apply them to the /etc/system file. Otherwise, the installation will proceed, the changes will be saved to some other file, and you will have to apply them manually.

set shmsys:shminfo_shmmni=8570 (was 7930) set shmsys:shminfo_shmseg=8420 (was 7780) set semsys:seminfo_semmns=10320 (was 9680) set semsys:seminfo_semmni=8570 (was 7930) set semsys:seminfo_semmsl=8570(was 7930)

Do you want us to apply these changes now? [no]

Changes saved into /etc/system.gal.1744

Press <ENTER> to continue.

30. If you indicated No in the previous step, the file to which the changes have been saved is displayed. Make sure that these values are established later to ensure that all the requirements for this setup is satisfied.

NOTES

The settings that are displayed are the maximum or minimum required settings. Value ’640’, which is provided for various shared memory segment or semaphore requirements, is a maximum value based on 10 streams.


This prompt is displayed only when you install/upgrade on a Solaris computer, in cases where the install detects that the computer does not have the maximum or minimum required shared memory settings.

Although a ’no’ answer can be selected to this question during install, the user should make sure the min requirements (below) for shared memory are met, otherwise the backups may fail (the message in logs is ’could not start the pipeline’).

set shmsys:shminfo_shmmax=4199304 set shmsys:shminfo_shmmin=1 set semsys:shminfo_shmmni=640 set semsys:shminfo_shmseg=640 set semsys:seminfo_semmns=640 set semsys:seminfo_semmni=640 set semsys:seminfo_semmsl=640 set maxusers=256


31. Enter the number corresponding to the storage policy through

Please select one storage policy for this IDA from the list below:

Features - 1-Touch

of 74

which you want to back up the File System iDataAgent and then press Enter to continue.

NOTES

A storage policy directs backup data to a media library. Each library has a default storage policy.

When you install an Agent, the install program creates a default subclient for most Agents.

If desired, you can change your storage policy selection at any time after you have installed the client software.

If this screen appears more than once, it is because you have selected multiple agents for installation and are configuring storage policy association for each of the installed agents.

1) SP_StandAloneLibrary2_2 2) SP_Library3_3 3) SP_MagLibrary4_4 4) fornax_fornax_HWCmp 5) ranger_ranger_HWCmp 6) fornax_fornax_ClntCmp 7) fornax_fornax_MACmp 8) fornax_fornax_NoCmp

Storage Policy: [3]

Enable Global Filters

32. Type the appropriate number for configuring Global Filters for the default subclient and press Enter to continue.

NOTES

Select Use Cell level Policy to inherit the global filter policy configuration set for the CommCell, i.e., if the Use Global Filters on All Subclients option is selected in the Global Filters dialog box (from the CommCell Console’s Control Panel), then this policy will be applied to the default subclient as well. If is not selected, then the global filters will not be

Commcell Level Global Filters are set through Calypso GUI's Control Panel in order to filter out certain directories or files from backup Commcell-widely. If you turn on the Global filters, they will be effective to the default subclient. There are three options you can choose to set the filters.

1) Use Cell level policy 2) Always use Global filters 3) Do not use Global filters

Please select how to set the Global Filters for the default subclient? [1]

Features - 1-Touch

of 74

applied to the default subclient.

Select Always use Global filters to always apply the global filters policy to the default subclient regardless of the policy set for the CommCell.

Select Do not use Global filters to disregard applying the global filters to the default subclient regardless of the policy set for the CommCell.


33. Type the number of a Client Group and press Enter.

A confirmation screen will mark your choice with an "X". Type the number for Done with the Selection, and press Enter to continue.

NOTES

This screen will be displayed only if Client Groups are configured for the CommCell. For more information, see Client Computer Groups.

For Solaris platforms, go to the next step; otherwise, skip the next step.

Client Group(s) is currently configured on CommServe cs.company.com. Please choose the group(s) that you want to add this client client.company.com to. The selected group(s) will be marked (X) and can be deselected if you enter the same number again. After you are finished with the selection, select "Done with the Selection". 1) Unix 2) DR 3) DKS 4) Done with the selection Please enter a number to select/deselect: [1]

Setup Complete

34. Press Enter to continue.

NOTES

Schedules help ensure that the data protection operations for the Agent are automatically performed on a regular basis without user intervention. For more information, see

+---------------------+

IMPORTANT:

In addition to installing Calypso on this computer, you will also need to create a Job Schedule for each iDataAgent that has been installed on this client computer.

Job Schedules are required to allow the Calypso iDataAgents to perform automated backup and restore operations.

Job Schedule creation can be accomplished through the Calypso CommCell Console administration interface.

Features - 1-Touch

of 74

Scheduling. +---------------------+

Successfully installed CVGxIDA. Press ENTER to continue ...

35. If this is the last package that you wish to install/upgrade, enter the number corresponding to the Return option and then press Enter to continue.

NOTES

Only modules that are not installed/upgraded appear in the list.

Your screen may appear different from the example shown.

If you are installing on AIX, FreeBSD, IRIX or Tru64 computers, if this module was the last possible module to install, you are automatically exited from the program. Otherwise, type the number for the Exit option and then press Enter. The installation is completed.

Select the Calypso module that you would like to install.

1) Proxy FileSystem iDataAgent <= CVGxProxyIDA 2) Oracle iDataAgent <= CVGxOrIDA 3) DB2 iDataAgent <= CVGxDB2 4) Return

Module number: [1]

If you are installing on Solaris, be sure to do the following before installing the post packs:

Prior to Exit option in the above step, press CTRL + z to suspend the installation.

Unmount the directory which contains the file system (mini-root) using the following command:

unmount -f /tmp/mnt18684

Remove the loopback file system (lofiadm) using the following command:

lofiadm -d /dev/lofi/1

Enter fg to continue the installation.

36. Enter Yes to download and install the latest service packs and post packs from the software provider.

NOTES

Internet connectivity is required to download updates.

This step is applicable for multi instancing.

Download and Install Latest Service Pack

If you choose to download the latest service pack from the software provider website now, please make sure you have internet connectivity at this time. This process may take some time depending on the internet connectivity.

Do you want to download the latest service pack now ? [no]

Press <ENTER> to continue ...

Features - 1-Touch

of 74


37. This prompt is displayed only when you are installing on HP-UX, Linux, or Solaris computers. Enter the number corresponding to the Exit option and then press Enter to continue.

The installation is now complete.

Certain Calypso packages can be associated with a virtual IP, or in other words, installed on a "virtual machine" belonging to some cluster. At any given time the virtual machine's services and IP address are active on only one of the cluster's servers. The virtual machine can "fail-over" from one server to another, which includes stopping services and deactivating IP address on the first server and activating the IP address/services on the other server.

Currently you have Calypso installed on physical node stone.company.com.

Now you have a choice of either adding another package to the existing installation or configure Calypso on a virtual machine for use in a cluster.

1) Add another package to stone.company.com 2) Install Calypso on a virtual machine 3) Exit

Your choice: [1]

If the 1-Touch server software is not installed on all the required 1-Touch servers, log on to the next 1-Touch server and repeat this procedure. Otherwise, your installation is complete.


General Install post-release updates or Service Packs that may have been released after the release of the software. If you are installing a Service Pack, verify and ensure that it is the same version as the one installed in the CommServe Server. Alternatively, you can enable Automatic Updates for quick and easy installation of updates in the CommCell component.

After installing the Agent, you may want to configure the Agent before running a data protection operation. The following list includes some of the most common features that can be configured:

Configure your subclients - see Subclients for more information.

Schedule your data protection operations - see Scheduling for more information.

Configure Alerts - See Alerts and Monitoring for more information.

Schedule Reports - See Reports for more information.

The software provides many more features that you will find useful. See the Index for a complete list of supported features.

Features - 1-Touch

of 74

Install the 1-Touch Server Software - Windows

Click on a link below to go to a specific section of the software installation:


Install Checklist

Before You Begin

Install Procedure

Getting Started



Configuration of Other Installation Options



1-Touch Server Distribution Folder Path

Verify Summary of Install Options

Schedule Automatic Update

Setup Complete


Install Requirements The software installs the 1-Touch server software. This software must be installed on the computer that is intended to function as the 1-Touch Server. The 1-Touch server software requires that the Windows File System iDataAgent be installed. However, if this iDataAgent is not already installed, a Windows File System license can be bundled and installed with the 1-Touch server software.

Verify that the computer in which you wish to install the software satisfies the minimum requirements specified in System Requirements - 1-Touch for Windows. Review the following Install Requirements before installing the software:

General Agents should be installed only after the CommServe and at least one MediaAgent have been installed in the CommCell. Also, keep in mind that the CommServe and MediaAgent must be installed and running (but not necessarily on the same computer), before you can install the Agent.

This software should be installed in a CommCell with current versions of the CommServe and MediaAgent software.

Ensure there is an available license on the CommServe for the Agent.

Verify that you have the software installation disc that is appropriate to the destination computer’s operating system.

Make sure that you have the latest software installation disc before you start to install the software. If you are not sure, contact your software provider.

Firewall

If the CommServe® Server, MediaAgent and/or Clients communicate across two-way firewall(s):

Ensure port 8400 is allowed connections through the firewall.

In addition a range of bi-directional ports (consecutive or discrete) must also be allowed connections through the firewall.

For information on configuring the range of ports, see Port Requirements for Two-way Firewall.

If the CommServe Server, MediaAgent and/or Clients communicate across one-way firewall(s):

Features - 1-Touch

of 74

Identify a range of outbound ports (consecutive or discrete) for use by the software.

For information on configuring the range of ports, see Port Requirements for One-way Firewall.

If the MediaAgent/Client communicates with the CommServe Server across a one-way firewall, you must add the MediaAgent/Client host name (or the IP address) in the CommServe computer before installing the necessary software on the MediaAgent/Client computer.

Install Checklist

Collect the following information before installing the software. Use the space provided to record the information, and retain this information in your Disaster Recovery binder.

1. Install folder location:________________________________________________________________

See Select Components for Installation for more information.

2. If the CommServe Server and the client computer communicate across a firewall:

Firewall ports: ______________________________________________________________________

Hostnames and/or IP Addresses and corresponding GxCVD port numbers of computers on the other side of the firewall:______________

Keep Alive Interval minutes:____________________________________________________________

Hostname for outgoing tunnel connections:_________________________________________________

Tunnel Initialization Interval seconds:_____________________________________________________

See Firewall Configuration for more information.

3. CommServe Host Name or the CommServe IP address:______________________________________

See Configuration of Other Installation Options for more information.

4. Client computer's Host name (NetBIOS name) or IP address____________________________________


5. Job result folder location:________________________________________________________________

If necessary, Name and Password for the specified folder:_______________________________________


6. Storage Policy used by the default subclient:________________________________________________

See Storage Policy Selection for more information.

7. Client Group to which this Client will be associated:_____________________________________________

See Client Group Selection for more information.

8. 1-Touch Server Distribution Folder Path: ________________________________________________________________

Features - 1-Touch

of 74

See 1-Touch Server Distribution Folder Path for more information.

9. Time and frequency for Install of Automatic Updates:_________________________________________

See Schedule Automatic Update for more information.

Before You Begin

Log on to the client as local Administrator or as a member of the Administrators group on that computer.

Install Procedure

Getting Started

1. Place the software installation disc for the Windows platform into the disc drive.

After a few seconds, the installation program is launched.

If the installation program does not launch automatically:

Click the Start button on the Windows task bar, and then click Run.

Browse to the installation disc drive, select Setup.exe, click Open, then click OK.

NOTES

If you are installing on a x64 version of Windows 2008 Server Core R2, go to the AMD64 folder and run Setup.exe.

2. In this screen, you choose the language you want to use during installation. Click the down arrow, select the desired language from the pull-down list, and click Next to continue.

3. Select the option to install software.

NOTES

This screen will only appear when the bAllow32BitInstallOn64Bit registry key has been created and enabled on this computer.

4. Select the option to install software on this computer.

NOTES

The options that appear on this screen depend on the computer in which the software is being installed.

5. Read the Welcome screen.

Click Next to continue, if no other applications are running.

6. Read the virus scanning software warning.

Features - 1-Touch

of 74

Click OK to continue, if virus scanning software is disabled.

7. Read the license agreement, then select I accept the terms in the license agreement.

Click Next to continue.


8. Select the component(s) to install.

NOTES

Your screen may look different from the example shown.

Components that either have already been installed, or which cannot be installed, will be dimmed. Hover over the component for additional details.

The Special Registry Keys In Use field will be enabled when GalaxyInstallerFlags registry keys have been enabled on this computer. Hover over the field to see which keys have been set, as well as their values. For more information, see Registry Keys.


To install the 1-Touch Server software, expand the Client Modules folder and the iDataAgent folder and select 1-Touch Server. This will automatically select the required File System iDataAgent.

9. Specify the location where you want to install the software.

NOTES

Do not install the software to a mapped network drive.

Do not use the following characters when specifying the destination path: / : * ? " < > | It is recommended that you use alphanumeric characters only.

If you intend to install other components on this computer, the selected installation directory will be automatically used for that software as well.

If a component has already been installed, this screen may not be displayed if the installer can use the same install location as previously used.

If you intend to use the SnapProtect™ feature for Windows File System iDataAgent, the agent should be installed on a non-system drive and not a filer volume.

Click Browse to change directories.


Features - 1-Touch

of 74


10. Select from the following:

If this Client communicates with the CommServe Server and/or MediaAgent across a firewall, select Yes, configure firewall services, and then click Next to continue. Proceed to the next Step.

If firewall configuration is not required, click No, do not configure firewall services and then click Next to continue. Proceed to the next section.

NOTES

Operating systems, such as Windows 2008 and Windows Vista, may have more than one profile present. When you select No to configure firewall services, verify that firewall settings are not enabled in the profile(s).

If the system detects firewall settings are present in the profile(s), you must select from the following:

Disable firewall for ALL profiles: Employ caution when choosing this option; firewall settings will be disabled in all profiles. This requires a system reboot; installation automatically resumes after reboot.

No, Firewall is not enabled: Select this option if your firewall settings allow communication with the CommServe computer. Click Back to configure firewall services.

11. Click the Specify list of machine across the firewall option and then specify the list of hosts separated from this computer by a firewall. Make sure you correctly describe whether the firewall allows two-way communication (but on a limited range of ports), or one-way communication (with either only remote host being able to make connections to this computer, or vice versa).

For all one-way firewalls allowing incoming connections and those one-way firewalls allowing outgoing connections without additional port filtering, skip this step.


NOTES

Consider the following:

On the CommServe Server, this list should include all the MediaAgents and Clients that are on the other side of the firewall.

On the MediaAgents/Clients this should include the CommServe computer, and any other Clients/MediaAgents on the other side of

Features - 1-Touch

of 74

the firewall with which communications will be established.

For each machine on the other side of the firewall that you want to configure, choose the type of firewall configuration based on the firewall setup in your environment. Choose from the following options:

Click on 2-way firewall if you can open certain ports as bi-directional ports.

Click 1-way firewall; host is reachable from this machine on the machine that is on the secure side of the firewall.

Click 1-way firewall; host is NOT reachable from this machine on the machine that is on the public / DMZ side of the firewall.

If you wish to communicate with computers in a clustered environment, ensure that you add the Host Name/IP Address of all physical nodes in the cluster (even if no CommCell components are installed) and all the virtual nodes in which CommCell components are installed.

Type the host name or the IP address and the GxCVD port number of the host name, and click Add to place it in the Host Name/IP Address List.

12. Click the Specify list of restricted open ports option and then specify the port range. Add the starting and ending port range and then click Add to place it in the Open Port List. Repeat as needed.

If firewall separating this computer from others allows incoming connections, but these connections can be made only on a limited set of ports, then configure the appropriate port range here. For all other scenarios, skip this step.

Note that if you do not specify hostname(s) as well as port number(s), then the firewall services will not be configured.

NOTES

Typically in a two-way firewall, the open ports must be indicated for all computers. In a one-way firewall, the ports must be specified on computers in the open side, if they are open in a restricted way. Note that the port ranges are not required for computers that are fully closed in the one-way firewall. For example, laptops which are configured as clients in the Workstation Backup Agent.

In a clustered environment, make sure the firewall ports specified here are open for communication on all the physical nodes as well as the virtual nodes.


Features - 1-Touch

of 74

13. If desired, modify the Keep Alive interval.


14. Optionally, select Advanced Firewall Configuration and specify a local host name interface to use for outgoing tunnel connections through the firewall. Otherwise, the interface and port is automatically selected for you by the OS.


15. If desired, modify the Tunnel Initialization interval.


Configuration of Other Installation Options

16. Enter the fully qualified domain name of the CommServe computer. (TCP/IP network name. e.g., computer.company.com)

NOTES

Do not use spaces when specifying a new name for the CommServe Host Name.

If a component has already been installed, this screen will not be displayed; instead, the installer will use the same Server Name as

Features - 1-Touch

of 74

previously specified.


17. Enter the username and password information for an external domain user account or a CommCell user account. This authorizes the installation of an agent on the CommCell.

NOTES

This window is only displayed when the Require Authentication for Agent Installation option is selected in the CommCell Properties. Users must belong to a User Group with Administrative Management capabilities to enable this feature. For more information, see Authentication for Agent Installs.


18. Enter the following:

The local (NetBIOS) name of the client computer.

The TCP/IP IP host name of the NIC that the client computer must use to communicate with the CommServe Server.

NOTES

Do not use spaces when specifying a new name for the Client.

The default network interface name of the client computer is displayed if the computer has only one network interface. If the computer has multiple network interfaces, enter the interface name that is preferred for communication with the CommServe Server.

If a component has already been installed, this screen will not be displayed; instead, the install program will use the same name as previously specified.


19. Specify the following and click Next to continue:

Type the location of the client's job results directory, or click Browse.

NOTES

Features - 1-Touch

of 74

The Agent uses the job results directory to store the client's backup and restore job results.


20. Select the storage policy through which you want to back up/archive the indicated component (subclient, instance, etc.)

NOTES

A storage policy directs backup data to a media library. Each library has a default storage policy.

When you install an Agent, the install program creates a default subclient for most Agents.

If desired, you can change your storage policy selection at any time after you have installed the client software.

If applicable, enable Global Filters for the default subclient.

If this screen appears more than once, it is because you have selected multiple agents for installation and are configuring storage policy association for each of the installed agents.



21. Select a Client Group from the list.


NOTES

This screen will be displayed only if Client Groups are configured in the CommCell Console. For more information, see Client Computer Groups.

1-Touch Server Distribution Folder Path

Features - 1-Touch

of 74

22. Enter the path for the distribution folder.

This folder will contain the following (when created):

Client Files share, which will contain client folders and recovery files

Image share, which will contain the File System iDataAgent to deploy on the 1-Touch Recovery client along with a Boot_image folder with 1touchBoot.iso for burning a bootable CD-ROM

WINDIST folder, which will contain shares housing the Microsoft Windows Distribution folders

23. Select Download Pack(s) and Install to download and install the latest service packs and post packs from the software provider.

NOTES

Internet connectivity is required to download updates.

This step is applicable when installing on the first instance.

Updates are downloaded to the following directory: <software installation>/Base/Temp/DownloadedPacks. They are launched silently and installed automatically for the first instance.


Verify Summary of Install Options

24. Verify the summary of selected options.

NOTES

The Summary on your screen should reflect the components you selected for install, and may look different from the example shown.

Click Next to continue or Back to change any of the options.

The install program now starts copying the software to the computer. This step may take several minutes to complete.

25. The System Reboot message may be displayed. If so, select one of the following:

Skip Reboot This option will be displayed if the install program finds any files belonging to other applications, that need to be replaced. As these files are not critical for this installation, you may skip the reboot and continue the installation and

Features - 1-Touch

of 74

reboot the computer at a later time.

Reboot Now If this option is displayed without the Skip Reboot option, the install program has found files required by the software that are in use and need to be replaced. If Reboot Now is displayed without the Skip Reboot option, reboot the computer at this point. The install program will automatically continue after the reboot.

Exit Setup If you want to exit the install program, click Exit Setup.

Schedule Automatic Update

26. If necessary, select this option to schedule an automatic installation of software updates.

NOTES

Install Updates Schedule allows automatic installation of the necessary software updates on the computer on a single or weekly basis. If you do not select this option, you can schedule these updates later from the CommCell Console.

To avoid conflict, do not schedule the automatic installation of software updates to occur at the same time as the automatic FTP downloading of software updates.

You may be prompted to reboot the computer before restarting services.

If a component has already been installed, this screen will not be displayed; instead, the installer will use the same option as previously specified.


Setup Complete

27. Click Next to continue.

NOTES

Schedules help ensure that the data protection operations for the Agent are automatically performed on a regular basis without user intervention. For more information, see Scheduling.

28. Decide whether you want to launch 1-Touch options now. If so, click the appropriate option in the 1-Touch Options area, click Next, and go to the next

Features - 1-Touch

of 74

step; if not, do the same and go to Schedule Automatic Update.

29. Click the desired option.

30. Setup displays the successfully installed components.

NOTES

The Setup Complete message displayed on your screen will reflect the components you installed, and may look different from the example shown.

If you install an Agent with the CommCell Console open, you need to refresh the CommCell Console (F5) to see the new Agents.

If Reboot Now button is displayed make sure to reboot the computer before performing any other operations from the computer.

Click Finish to close the install program.

The installation is now complete.


General Install post-release updates or Service Packs that may have been released after the release of the software. If you are installing a Service Pack, verify and ensure that it is the same version as the one installed in the CommServe Server. Alternatively, you can enable Automatic Updates for quick and easy installation of updates in the CommCell component.

Be sure to ensure security access for 1-Touch Server shares created on Windows XP.

Features - 1-Touch

of 74

1-Touch Server shares require that the logged-on user running OneTouch.exe have read, write, execute, create, modify, and delete rights to C:\<software installation path>\SystemRecovery\ClientFiles folders.

Confirm that the 1-Touch Server Shares created during installation have security access by using either the classic file sharing and security interface or the Simple Sharing User Interface (UI).

Windows XP Professional uses the Simple Sharing UI. The Simple Sharing UI appears if ForceGuest is turned on; the traditional sharing and security tabs are shown if ForceGuest is turned off. By default, Simple File Sharing is turned on in Windows XP Professional computers that are joined to a workgroup.

Windows XP Professional computers that are joined to a domain use only the classic file sharing and security interface. When you use the Simple File Sharing UI (that is located in the folder's properties), both share and file permissions are configured.

When simple sharing is in effect, permissions are automatically set on shared files and folders. The following permissions are added when using the Simple Sharing UI:

Share permissions

File permissions

Allow others to change my files

Dont allow others to change my files

When the Guest-only security model is used, the Sharing tab has only three options:

Share this folder on the network (this grants the Everyone group Read permissions on the folder and its contents)

Share name (i.e., the name of the share on the network)

Allow other users to change my files (this grants the Everyone group Full Control permissions on folders and Change permissions on files)

To turn Simple File Sharing on or off, perform the following steps:

Double-click My Computer on the desktop

Select Tools from the menu bar

Select Folder Options and select the View tab

Select or clear the Use Simple File Sharing (Recommended) check box.

Agent Specific A 1-Touch Recovery is not used to recover a 1-Touch Server. Thus it is important to configure the File System iDataAgent for data protection and recovery on the 1-Touch server.

Features - 1-Touch

of 74

1-Touch for AIX Topics | How To

Overview

Preventing Duplicate Data Backups

Setting up 1-Touch for AIX

Recovering Data in Case of Disaster

Recovering the System to a Specific Level

License Requirements

Overview

1-Touch for AIX 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, and it restores data backed up by the default backup set that is configured for 1-Touch.

The feature also involves a 1-Touch server, which is used to boot the client. A 1-Touch server is required for each subnet in a network that contains 1-Touch clients. 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.

Back To Top

Preventing Duplicate Data Backups

During a full backup for a client configured for 1-Touch for AIX, the default subclient uses the mksysb utility to back up the root volume group along with the information for all the affected volume groups. The mksysb utility backs up all the files on the root volume group including data files. Therefore, when a default subclient uses mksysb during a backup, and if data files are stored on the affected root file system, the same data will be backed up to the media twice unless you exclude the user data directories from mksysb. You can resolve this problem by following the appropriate step in Setting up 1-Touch for AIX.

Setting up 1-Touch for AIX

Complete the following tasks to set up 1-Touch for AIX:

1-Touch for AIX backups are not supported for a WPAR client.

1-Touch for AIX backups are supported for AIX 6.1 clients that have a System Workload Partitioning (WPAR) environment installed on the root volume. The WPAR environment creates a file system, and this file system has a mount option that is set to false by default. To enable 1-Touch for AIX backups, be sure to set this option to true.

This feature is not supported when bootable partitions are on the disk arrays (snapable disk).

For the 1-Touch clients with link aggregation or ether channel, ensure

Features - 1-Touch

of 74

1. Read the minimum requirements specified in System Requirements - 1-Touch for Unix.

2. Ensure that the 1-Touch Recovery Server is a dedicated AIX machine running the NIM Master server environment.

3. The 1-Touch server can be in the same subnet as the client computer, or it can be in a different subnet. However, if they are in different subnets, ensure that there is no network firewall between the server and the client.

4. Verify that the NIM master server and the CommServe names are resolved correctly using /etc/hosts or bind.

5. If necessary as discussed in Preventing Duplicate Data Backups, include a list of data folders to be excluded from mksysb in a text file located at <software_install_folder>/BASE/iDataAgent/srtarexcludes on the client machine .

6. 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.

7. Ensure that the AIX File System iDataAgent is installed on the client computer. See Install the Unix File System iDataAgents for information on installing the AIX File System iDataAgent.

8. Ensure that the data that you will be restoring has been backed up by the default backup set that has been configured for 1-Touch. As appropriate, see Configure the Subclient for 1-Touch and Start a Backup.

9. If the 1-Touch client host ID (mac address) has changed since the most recent 1-Touch backup, be sure to update the client's Ethernet address within the /etc/ethers file on the 1-Touch server. Otherwise, you will not be able to boot the 1-Touch client.

Back To Top


Use the following procedure to recover data in case of disaster.

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:

that the standard network adapter is configured for the communication with NIM server.

In the next two steps, be sure to install the 1-Touch server software and the AIX File System iDataAgent on the rootvg and to the same installation directory path on the appropriate computer.

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.

Restores to a read-only file system will result in the job completing with errors. These errors are usually the result of "failed" files that are produced for in-place restores to the read-only file system that could not be run.

Features - 1-Touch

of 74

1. 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.

2. 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.

3. 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.

4. 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.

5. When you are finished, go to the Summary dialog box and click Finish. The recovery should complete.


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.

Back To Top

Features - 1-Touch

of 74

1-Touch for HP-UX

Overview

Support

Setting up 1-Touch for HP-UX

Prerequisites


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.


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.



Features - 1-Touch

of 74


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.


To configure the subclient for 1-Touch:

1. From the CommCell Browser, right-click the appropriate (usually the default) subclient and then click Properties from the shortcut menu.

2. From the Subclient Properties (1-Touch Recovery) tab, click 1-Touch Recovery.

3. 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.

4. Click OK.

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.


Before you begin

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/

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.


Features - 1-Touch

of 74










Back To Top

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).

Features - 1-Touch

of 74

1-Touch for Linux Topics | How To

Overview

Setting up 1-Touch for Linux




Overview

1-Touch for Linux 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, and it restores data backed up by the default backup set that is configured for 1-Touch.

The feature also involves a 1-Touch server, which is used to boot the client. The 1-Touch server provides the 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.

Back To Top

Setting up 1-Touch for Linux

Complete the following tasks to set up 1-Touch for Linux:

1. Read the minimum requirements specified in System Requirements - 1-Touch for Unix.

2. Ensure that the 1-Touch Recovery Server is a dedicated Linux machine running an NFS server environment. Also, ensure that you configure and export an NFS directory to allow 1-Touch for Linux clients to mount this directory during the 1-Touch restore.

3. The 1-Touch server can be in the same subnet as the client computer, or it can be in a different subnet. However, if they are in different subnets, ensure that there is no network firewall between the server and the client.

4. 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.

5. Ensure that the Linux File System iDataAgent is installed on the client computer. See Install the Unix File System iDataAgents for information on installing the Linux File System iDataAgent.

6. Ensure that the data that you will be restoring has been backed up by the default backup set that has been configured for 1-Touch. As appropriate, see Configure the Subclient for 1-Touch and Start a Backup.

Back To Top



Features - 1-Touch

of 74

Use the following procedures to recover data in case of disaster.


To recover a system using 1-Touch:

1. Burn on the Linux boot CD the bootable ISO image that was restored to the 1-Touch Server.

2. Boot the client using the Linux boot CD.

3. Decide whether you want to interactively administer disk and file system restores and therefore provide more flexibility for the recovery. If so, type or accept the y default, press Enter and go to the next section in this procedure. If not, type n, press Enter and exit this procedure.

For each of the following interactive tasks that you choose to complete, 1-Touch performs the task per the details saved during the 1-Touch backup. For each of the following tasks that you choose not to complete, an automated recovery of the affected component will occur.

Partition Disks

4. If you want to partition specified disks, accept the y default, press Enter and go to the next step; if not, type n, press Enter and go to the next section in this procedure.

5. The path for a disk is displayed. If you want to partition this specific disk, accept the y default and press Enter; if not, type n and press Enter. If you chose to partition the disk, the appropriate messages are displayed.

6. Repeat the previous step for each disk until all disks are accounted for. Then go to the next section in this procedure.

Restore Physical Volumes

7. If you want to restore specified physical volumes, accept the y default, press Enter and go to the next step; if not, type n, press Enter and go to the next section in this procedure. Note that the physical volumes on any disk that you chose not to partition in the previous section will not be eligible for restore.

8. The path for a physical volume on a disk is displayed. If you want to restore this physical volume, accept the y default and press Enter; if not, type n and press Enter. If you chose to restore the physical volume, the appropriate messages are displayed.

9. Repeat the previous step for each physical volume per disk until all the volumes are accounted for. Then go to the next section in this procedure.

Restore Volume Groups

10. If you want to restore specified volume groups, accept the y default, press Enter and go to the next step; if not, type n, press Enter and go to the next section in this procedure.

11. A volume group is displayed. If you want to restore this volume group, accept the y default and press Enter; if not, type n and press Enter. If you chose to restore the volume group, the

1-Touch for Linux cannot restore to a different computer whose hardware configuration is dissimilar to that of the original computer.

If you are restoring to a different computer that has the same hardware configuration as the original computer, you must manually configure the network interface card (NIC) when the computer comes up after the first reboot. Once the NIC is configured, you should reboot to allow the second phase of the 1-Touch recovery to complete successfully.


Features - 1-Touch

of 74

appropriate messages are displayed.

12. Repeat the previous step for each physical volume group until all the volume groups are accounted for. Then go to the next section in this procedure.

Restore File Systems

13. If you want to restore file systems, accept the y default, press Enter and go to the next step; if not, type n, press Enter and exit this procedure.

14. A file system is displayed. To restore file systems interactively, you must restore at least the "/" file system as a matter of course. Therefore, if the "/" file system is displayed, accept the y default and press Enter. If another file system is displayed and you want to restore it, accept the y default and press Enter; if not, type n and press Enter. If you chose to restore the file system, the appropriate messages are displayed.

15. Repeat the previous step for each file system until all the file systems are accounted for.

Once you complete this procedure, the appropriate actions leading to a system reboot are completed. Once the reboot takes place, the services should be up in the system, and the product software should start a full data command line restore. Once this restore is completed, the system should be completely recovered.

Back To Top













Back To Top

Features - 1-Touch

of 74

1-Touch for Solaris

Overview

Support

Setting up 1-Touch for Solaris

Prerequisites


Installation

Configuration



Global File System Recovery (Clusters)

Perform a Full System Restore

Perform a Full System Restore for Solaris 10 Update 5 and Below

Perform a Full System Restore for Solaris 10 Update 6 and Above

Overview

1-Touch for Solaris 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 data backed up by the default backup set that is configured for 1-Touch.

The feature also involves a 1-Touch server, which is used to boot the client. A 1-Touch server is required for each subnet in a network that contains 1-Touch clients. 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.

Support For the list of supported Operating Systems, see System Requirements - 1-Touch for Unix.

1-Touch for Solaris backups do not work on Solaris local zones.


The following Solaris boot image versions are supported for 1-Touch for Solaris:

Solaris 9

Solaris 10

Setting up 1-Touch for Solaris

Prerequisites For 1-Touch Server, use any Solaris system that is configured as a JumpStart server and has the required networking services, which include RARP, bootp, and tftp.

The Solaris JumpStart server version (including updates such as, for example, Solaris 10 Update 7) should be greater than or equal to the version of the Solaris client targeted for recovery. A Solaris JumpStart server can recover Solaris client whose version is equal to or less than the server version.

Features - 1-Touch

of 74

For example, a Solaris 10 JumpStart server can recover Solaris 10 client, Solaris 9 client, etc. Similarly, a Solaris 9 JumpStart server cannot recover Solaris 10 client, but it can recover Solaris 9 client, Solaris 8 client, etc.

Ensure that the permissions setting for an NFS share on the JumpStart server is "ro" (read-only). Other settings may produce undesirable results. For example, a "rw" (read/write) setting will cause the client boot to hang.

Ensure that the 1-Touch server is in the same subnet as the client computer.

Ensure that the client Operating System root is not on the Zettabyte File System.




The 1-Touch feature requires the following licenses:

Boot Server on Unix

iDataAgent for Sun Solaris File System

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

Install the Solaris File System iDataAgent on the client computer. See Install the Unix File System iDataAgent for information on installing the Solaris File System iDataAgent.

Configuration

Configure the 1-Touch Server

Configure the 1-Touch server per the Solaris Advanced Installation Guide at http://docs.sun.com/db/doc/816-2411?q=jumpstart.

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.


To configure the subclient for 1-Touch:

1. From the CommCell Browser, right-click the appropriate (usually the default) subclient and then click Properties from the shortcut menu.

2. From the Subclient Properties (1-Touch Recovery) tab, click 1-Touch Recovery.

3. 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.

4. Click OK.

Run a Backup

Start or Schedule regular full backups of the default subclient. Unless you backup the system state, 1-Touch cannot restore the system configuration.

If Solaris 10 Update 6 or above jumpstart server is used as 1-touch server, please make sure that it has /boot/solaris/bin/root_archive. It is required for unpacking and repacking Solaris miniroot in jumpstart server.

Features - 1-Touch

of 74

To start a full backup see, Start a Full Backup.

To schedule a full backup see, Schedule Backups.

If the 1-Touch client host ID (mac address) has changed since the most recent 1-Touch backup, be sure to update the client's Ethernet address within the /etc/ethers file on the 1-Touch server. Otherwise, you will not be able to boot the 1-Touch client.












Use the following procedures to recover data in case of disaster.



1. Connect the client to network and switch on the power.

2. From the CommCell Console on the 1-Touch server, right-click the appropriate backup set, click All Tasks, and then click 1-Touch Recovery to access the Submit 1-Touch Recovery Request wizard.

3. At the boot prompt of the affected client, enter one of the following commands, as appropriate:

We also recommend that you set the primary mirror as the boot device. Otherwise (e.g., if the secondary mirror is set as the boot device), the 1-Touch restore may fail.


Features - 1-Touch

of 74

boot net – w recover u=<user_id> p=<passwd> (to implement a basic recovery of essential OS filesystems; Ex:/, /opt, /usr, /var are restored)

boot net – w recover newfs-changed-drives u=<user_id> p=<passwd> (recovery of OS and replaced disks)

boot net – w recover newfs-all u=<user_id> p=<passwd> (all disks partitioned and filesystems created regardless of state)

where <user_id> is Commcell console user id and <passwd> is Commcell console password.

This step starts the 1-Touch. All logging output for the recovery is redirected to the console and a file under the /tmp directory.

4. At this point, the recovery procedure should launch an automatic command line restore. If this is successful, go to the next step. If this is not successful, manually restore / to /a on the client. Rebooting with command: net - w recover =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ..... Phase 1 of 1-Touch starting ..... ..... Starting services Starting cvd service... done Starting EvMgrC service... done Starting cvfwd service, if installed... done Launching automatic restore. Hit return to continue...

5. Pause while the system completes some internal boots and performs some processing. No action is required on your part. ..... ..... =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Phase 2 of 1-Touch started Mounting '/opt/calypso' if on a separate file system...done ..... ..... ..... Phase 2 of 1-Touch is now complete =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

The 1-Touch client updates the sr.log log files on both the client and the 1-Touch server. If a 1-Touch client backup completed successfully and is somehow failing to boot, be sure to check the sr.log on the 1-Touch server for any warning.

If you are using a different 1-Touch server than that was used previously, remove the client’s name from the database of the previous 1-Touch server. Otherwise, the client will not be able to boot off the network because both servers will respond to the client’s RARP request. To do this, from the Tools directory (e.g., /database/jumpstart/Solaris_9/Tools, run the ./rm_install_client <clientname> command. For DHCP clients, run the following commands:

./rm_install_client <platform name>

./rm_install_client <ethernet address>

./rm_install_client -f <boot file name>

Sometimes, the RARP, bootparams and tftp daemons fail to re-read network information pertaining to the 1-Touch client. In such cases, you may have to restart the daemons.

Features - 1-Touch

of 74

Phase 3 of 1-Touch started Preserve not specified All file system will be created regardless of their state Phase 3 of 1-Touch is now completed Launching automatic restore. Hit return to continue...

6. At this point, you are advised that the system will reboot without any further user input. Job (28) is Completed ... Stopping services done Phase 4 of 1-Touch is now complete Any remaining 1-Touch actions will continue after the reboot! ..... ..... Rebooting with command: ..... ..... Phase 5 of 1-Touch started ..... =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Congratulations 1-Touch procedures have now been completed The system will now reboot to continue normal operation =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- #### Normal boot :-) rebooting... Resetting... SPARCstation 5, No Keyboard ROM Rev. 2.28, 128 MB memory installed, Serial #8856067. Ethernet address 8:0:20:87:22:3, Host ID: 80872203. ..... ..... Rebooting with command: Boot device: /iommu/sbus/espdma@5,8400000/esp@5,8800000/sd@3,0 File and args: SunOS Release 5.7 Version Generic_106541-12 [UNIX(R) System V Release 4.0] Copyright (c) 1983-1999, Sun Microsystems, Inc. configuring network interfaces: le0. Hostname: pluto3

Global File System Recovery (Clusters) Global File Systems will not be recovered during the 1-Touch for Solaris recovery. These file systems should be recovered after the failure to mount the Global File System becomes apparent. This will become apparent only during a full node recovery since this should be the only time any Global File System is not available. This ensures that a single node recovery will not delete Global File Systems.

Be sure to note the file system type and then recreate the file system as previously created. The initial Global File System restore should be started from the node that served as the Global File System controller at the time of the last 1-Touch backup. The 1-Touch restore directory contains the Global File System disk recovery commands. For example:

/database/jumpstart/files/arecibo/galaxy/iDataAgent/systemrecovery/disks/vxvm.vxmake.oracl

To debug boot problems, use the snoop and truss commands.

Features - 1-Touch

of 74

or

/database/jumpstart/files/arecibo/galaxy/iDataAgent/systemrecovery/disks/lvm.mk.commands

where :

arecibo is the client /database/jumpstart/ is the system's jumpstart directory vxvm.commands (with vxvm.vxmake.oracle_dg) is the Global File System volume group using VERITAS Volume Manager lvm.mk.commands is the Global File System volume group using Solaris Volume Manager

Perform a Full System Restore

The difference between a normal restore and a full system restore is the severity of the problem. Normally, if data is lost or removed, it is recovered from the archives using the normal restore procedures. However, when a normal restore operation cannot correct a software and/or hardware corruption problem, some additional changes may be required.

Also refer to Restore Data - Solaris File System iDataAgent - Full System Restore.

When the root file system is lost, a full system restore is required. Select the appropriate method to restore:



Before You Begin

On a Solaris system, you can use either the jump start server method or the miniroot method to perform a full system restore. The jump start server method is considered the easier of the two methods because you do not need to use an additional drive for rebooting purposes. The latter steps for both methods are identical.

The jump start server method includes the following general steps (detailed instructions are provided in the following section):

1. Copy the jump start software to your machine.

2. Add clients that will boot off of the jump start server

3. Create a new root directory, and add the required system hosts, shared memory, and system services.

4. Create and mount a root file system on the system that you want to restore.

5. If any additional file systems were lost, create and mount them as well.

6. Use the Solaris File System iDataAgent to restore your data.

The miniroot method includes the following general steps (detailed instructions are provided in the sections below):

1. Install a Core System Support partition on the system that you want to restore.

The following error messages may be displayed during a Sun Cluster 1-Touch recovery. However, you can ignore these messages as they are unintentional.

devfsadm: mkdir failed for /dev/md/shared/1/rdsk 0x1ed: No such file or directory devfsadm: cannot create link: /dev/md/shared/1/rdsk/d81 - > ../../../../../devices/pseudo/md@0:1,81,raw. max attenpts exceeded

Features - 1-Touch

of 74

2. If the whoami command is not available on your system, follow the workaround provided.

3. Install the Solaris File System iDataAgent on the Core System Support partition.

4. Create and mount a root file system on the system that you want to restore.

5. If any additional file systems were lost, create and mount them as well.

6. Use the Solaris File System iDataAgent to restore your data


Using the jump start server method:

1. From the appropriate Solaris CD-ROM (e.g., Solaris 8), navigate to the appropriate Tools directory (Example: s0/Solaris_8/Tools directory).

2. Enter the following command to copy the jump start software to your machine. ./setup_install_server -b /opt/boot

3. For each client that you want to boot off of the jump start server, enter the appropriate add command. For example, the following example implies that three such clients will be booted. ./add_* -i 172.19.71.226 -e 8:0:20:7c:89:1a -s pluto8:/jumpstart pluto6 sun4u ./add_* -i 172.19.71.227 -e 8:0:20:7d:e6:33 -s pluto8:/jumpstart pluto7 sun4m ./add_* -i 172.19.71.224 -e 8:0:20:7c:73:f -s pluto8:/jumpstart pluto4 sun4m

4. Copy <mnt_point>/Solaris_8/Tools/Boot from the CD-ROM to a shareable directory (Example: /jumpstart)

5. Modify /etc/bootparams to reflect the new root directory (i.e., not the CD-ROM slice)

6. Modify <mnt_point>/Solaris_8/Tools/Boot/.tmp_proto/root/etc/inet/hosts to add the hosts needed to communicate with the Solaris File System iDataAgent

7. Modify <mnt_point>/Solaris_8/Tools/Boot/etc/system to add shared memory information. For example: set shmsys:shminfo_shmmax=4199304 set shmsys:shminfo_shmmin=1 set shmsys:shminfo_shmmni=5824 set shmsys:shminfo_shmseg=5824 set semsys:seminfo_semmns=5824 set semsys:seminfo_semmni=5824 set semsys:seminfo_semmsl=5824

8. Modify <mnt_point>/Solaris_8/Tools/Boot/etc/services to add system services. For example: cvd 8400/tcp EvMgrS 8401/tcp

9. Create symbolic links for required writeable areas in <mnt_point>/Solaris_8/Tools/Boot/etc/. For example: ln -s ../tmp/root/etc/inet/Galaxy.pkg Galaxy.pkg ln -s /tmp/CommVaultRegistry CommVaultRegistry Then let the system boot.

10. Using an open slice, create and mount a /opt file system (e.g., swap slice).


Features - 1-Touch

of 74

11. Install the Solaris File System iDataAgent software. If the installer requests patches and the required patches have not been installed on the jump start server, skip the request to add the additional operating system patches. See Deployment - Unix File System iDataAgents for instructions. When the Solaris File System iDataAgent is installed, continue with the next step.

12. Create partitions/slices on the disk by entering the following command: format

13. Create the root file system by entering the command: newfs /dev/dsk/<DriveID>

where <DriveID> is the Drive Identifier of the partition where you want to create the root file system.

14. Mount the new root file system at /mnt by entering the following command: mount /dev/dsk/<DriveID> /mnt

where <DriveID> is the Drive Identifier of the partition containing the root file system.

15. Create an empty directory called proc on /mnt as follows: mkdir /mnt/proc

16. If any other file systems existed on the root disk before the system crash, you must recreate them as well. For each file system, enter the command newfs /dev/dsk/<DriveID>

where <DriveID> is the Drive Identifier of the partition containing the file system that was lost.

17. If you have recreated any file systems other than root, you must mount these as well. For each file system, enter the following commands: mkdir /mnt/<file_system_name>

mount /dev/dsk/<DriveID> /mnt/<file_system_name> where <file_system_name> is the name of the file system and <DriveID> is the Drive Identifier of the partition containing the file system.

1. From the CommCell Console, right-click on the backup set that contains the backup data of the root file system, click All Tasks, click Restore, type / as the path to restore from, and exclude from the content of the restore any file systems that were not affected by the system crash.

2. When restoring encrypted data, refer to Data Encryption.

3. Click OK to start the restore.

4. Verify that the restore operation has completed successfully, then reboot the computer. The system boots to the newly restored root.

This procedure is now complete.

Using the mini-root method:

1. When you perform a full system restore, the client computer must have a Core System Support partition with the Solaris File System iDataAgent installed on the Core System Support. Do not install the Core System Support on the disk that will contain the restored root file system. Install the Core System Support with the networking option enabled. The TCP/IP, hostname, and domain name settings of the Core System Support must match those of the system that you are restoring.

Do not select Unconditional Overwrite from the Restore Options dialog box.

If you install the Core System Support on an external drive, it can be used for other systems. However, you will have to remove and re-install the Solaris File System iDataAgent software for each client. In addition, you will have to reconfigure TCP/IP, hostname, and domain name settings for each system.

Features - 1-Touch

of 74

Load a Core System Support partition on your system. (You can get installation instructions from the Sun website.) Once the software is installed, boot your system.

2. From the eeprom console prompt ok: type the following command: boot <disk3>

where <disk3> is the path to the bootable core system.

3. Log in from the console.

4. After you log in to the system, if /usr/ucb/whoami does not exist, do the following: Enter these commands: cd /usr mkdir ucb cd ucb

Use the vi utility to create a file called whoami. Type the following in the whoami file: echo root Save the file and quit vi. Enter the following command: chmod 755 whoami

5. Install the Solaris File System iDataAgent software. See Deployment - Unix File System iDataAgents for instructions. When the Solaris File System iDataAgent is installed, continue with the next step.

6. Create partitions/slices on the disk by entering the following command: format





9. Create an empty directory called proc on /mnt as follows: mkdir /mnt/proc

10. If any other file systems existed on the root disk before the system crash, you must recreate them as well. For each file system, enter the command newfs /dev/dsk/<DriveID>

where <DriveID> is the Drive Identifier of the partition containing the file system that was lost.

11. If you have recreated any file systems other than root, you must mount these as well. For each file system, enter the following commands: mkdir /mnt/<file_system_name>

mount /dev/dsk/<DriveID> /mnt/<file_system_name> where <file_system_name> is the name of the file system and <DriveID> is the Drive Identifier of the partition containing the file system.

12. From the CommCell Console, right-click on the backup set that contains the backup data of the root file system, click All Tasks, click Restore, type / as the path to restore from, and exclude from the

For x86 systems, be sure to use the fdisk command to partition the disk before you format it. This will allow you to add a "Solaris2" partition to hold the Solaris "slices". For example: fdisk /dev/rdsk/c1d0p0

Features - 1-Touch

of 74

content of the restore any file systems that were not affected by the system crash.

13. When restoring encrypted data, refer to When restoring encrypted data, refer to Data Encryption.

14. Click OK to start the restore.

15. Verify that the restore operation has completed successfully, then reboot the computer. The system boots to the newly restored root.

16. Reinstall the boot block in the disk partition. For SPARC systems, use the installboot command.

For example: installboot /usr/platform/'uname -i' /lib/fs/ufs/bootblk/dev/rdsk/c0t3d0s0

For x86 systems, use the installgrub command. For example: installgrub - m /boot/grub/stage1 /boot/grub/stage2/dev/rdsk/c1d0s0

17. Create an empty directory called "Temp" in <install directory>/Base. For example: mkdir /opt/calypso/Base/Temp



Using the mini-root method:

1. On the boot server, perform the jump start method as explained above in the section 'Using the jump start server method'.

2. Install the jump start server on the Boot server

cd <jumpstart_install_directory>

3. Unpack miniroot (<miniroot_mnt_dir>=`pwd`/boot) by entering the following command:

/boot/solaris/bin/root_archive unpack sparc.miniroot `pwd`/boot

4. Follow the steps given below if, on the client, Calypso was installed at /opt:

cd <miniroot_mnt_dir>/etc/

ln –s /tmp/Calypso/CommVaultRegistry CommVaultRegistry

If Calypso was installed at a different directory, change the steps as follows:

cd <miniroot_mnt_dir>

ln –s /tmp/Calypso opt/Calypso

ln –s /tmp/Calypso var/log/Calypso

5. Pack Miniroot

pack miniroot /boot/solaris/bin/root_archive pack sparc.miniroot `pwd`/boot

6. NFS export a directory with RW (Read/Write) permissions for the client to be recovered.

/export/<mydir>

where <mydir> is the name of the directory.

7. Make sure the client gets all required permissions on this directory and its contents.

Do not select Unconditional Overwrite from the Restore Options dialog box.

Features - 1-Touch

of 74

8. From the Commcell console, restore CommVaultRegistry and /opt/Calypso/* into /export/<mydir>

cd to /export/<mydir>

mkdir Log_Files

mv Base32 Base

mv iDataAgent32 iDataAgent

9. On the Client side, perform the following steps:

10. Jumpstart the client using the boot server.

11. Follow the prompts and get to a shell. Bring up all the interfaces.

boot net -s

12. Configure a default route.

route add default <172.x.x.x>

where <172.x.x.x> is the Gateway address

13. Add the client IP address and hostname to:

/etc/hosts

14. Add the Media Agent and CommServe to:

/etc/hosts

15. Create partitions/slices on the disk by entering the command: format





18. If ZFS on Root partition, follow the steps given below to create zpools and file systems:

zpool create –R/a <pool name>

where <pool name> is the zpool name created during the initial Solaris install.

zfs create <pool name>/FS1

where <pool name> is the zpool name created during the initial Solaris install and FS1 is the file

If you are using x64 Solaris, then:

mv Base/Calypso Base32

rm –rf Base iDataAgent

For x86 systems, be sure to use the fdisk command to partition the disk before you format it. This will allow you to add a "Solaris2" partition to hold the Solaris "slices". For example: fdisk /dev/rdsk/c1d0p0

Features - 1-Touch

of 74

system name

zfs set mountpot=<first_mountpoint><pool name>/FS1

where <first_mountpoint> refers to its original mountpoint and FS1 is the file system name

fs create <pool name>/FS2

where <pool name> is the zpool name created during the initial Solaris install and FS2 is the file system name

zfs set mountpot=<first_mountpoint><pool name>/FS1

where <first_mountpoint> refers to its original mountpoint and <pool name> is the zpool name created during the initial Solaris install.

19. Continue the same steps to create all of the ZFS file systems

20. Create a dump and swap the file systems, using the following command:

zfs create –V <space required> <fsname>

where <fsname> is the filesystem name. Example: /export/home

21. One of the ZFS file system will have ‘/’ as the mount point, after creating this file system, follow the steps given below to export and re-import the Root Pool:

zpool export <rpool>

where <rpool> is the root pool name

zpool import –R /a <rpool>

where <rpool> is the root pool name

zpool set bootfs=<fs_mp> <rpool>

where <fs_mp> is the name of the file system that has the mount point = ‘/’ and <rpool> is the root pool name

mkdir /tmp/Calypso

mount bootserver:/NFS/exported/myfolder /tmp/Calypso

22. Check if: /var/log/Calypso is a link to /tmp/Calypso

23. If not, then use:

ln –s /tmp/Calypso /var/log/Calypso

24. To start the Recovery services, follow the steps given below: cd /opt/Calypso

mkdir /opt/Calypso/Base/Temp/

../galaxy_vm

../Base/cvprofile

svc_ctrl –focus $GALAXY_VM -start cvd

svc_ctrl –focus $GALAXY_VM -start EvMgrC

svc_ctrl –focus $GALAXY_VM -start cvfwd

25. From the CommCell console, launch the Restore operation.

26. Follow the steps given below to boot the client and restore all data:

27. Set the variable

platform=`uname –i`

Features - 1-Touch

of 74

28. Use the variable as directory, to map it to the correct Boot block.

Following command is for Solaris 10 Update 6 or above:

installboot –F zfs /a/usr/platform/$Platform/lib/fs/zfs/bootblk /dev/rdsk/<boot_disk>

where <boot_disk> is the name of the disk to be booted

Following command is for Solaris 10 Update 5 or below:

installboot /a/usr/platform/$Platform/lib/fs/ufs/bootblk /dev/rdsk/<boot_disk>

where <boot_disk> is the name of the disk to be booted


Back To Top

For x86 systems:

installgrub –fm /a/boot/grub/stage1/a/boot/grub/stage2 /dev/rdsk/<boot disk> bootadm update-archive –R /a init 6

Features - 1-Touch

of 74

1-Touch for Windows Topics | How To

Overview

Dissimilar Disk Restore

Setting up 1-Touch for Windows

Preparing 1-Touch Configuration and Answer Files/Profiles

Using Custom Scripts


Standard Procedure

Procedure on a Cluster


Overview

1-Touch for Windows provides the automated rebuilding and restoration of 1-Touch client computers. Automation includes the following options:

Silent disk partitioning and formatting.

Installation of the operating system fully unattended from a network share.

Full iDataAgent restore from a point in time selected by the administrator.

1-Touch requires that a 1-Touch server be installed within the CommCell. It also requires that the appropriate Windows File System iDataAgent be installed on the client and that a client boot CD-ROM be created. However, you need not install the iDataAgent individually since this software is bundled with the 1-Touch server software and is automatically installed when you install this server software.

1-Touch clients prepare information for an automated recovery each time the system state is backed up. This information includes the computer name, operating system, IP address(es), and disk partition/format information. In case of disaster, the information can be quickly restored in the format of several automated answer files for silent deployment and restoration of the computer. The 1-Touch server software provides a very simple program that allows you to select the most recent backup data or such data of a specified date to be automatically restored.

You can install multiple 1-Touch servers for a single CommServe; you must have a 1-Touch Server license for each installation. This method would allow, for instance, remote sites to install a 1-Touch server locally to minimize WAN traffic during the Windows installation portion of recovery.

A 1-Touch Recovery is not used to recover a 1-Touch Server. The 1-Touch Server should be backed up using the appropriate File System iDataAgent for data protection and recovery, which is installed with the 1-Touch software.

1-Touch for Windows does not support Single Sign On. Create a CommCell user with administrative privileges or use an existing CommCell user. For more information, see the Capabilities and Permitted Actions (By Feature).

A complete 1-Touch Recovery procedure that incorporates the Broadcom NetXtreme II network interface card (NIC) workaround for a successful Microsoft Windows unattended installation is provided in Perform 1-Touch Recovery with Broadcom's NetXtreme II Driver Workaround.

Features - 1-Touch

of 74

Dissimilar Disk Restore

1-Touch for Windows also provides a Dissimilar Disk Restore option. This option allows you to recover data to one or more target disks that differ from the source disk(s) in type or size. The option allows you to create partitions on the target disk that differ in size from those on the source disk in order to accommodate the volumes you are recovering.

Back To Top

Setting up 1-Touch for Windows

Complete the following tasks to set up 1-Touch for Windows:

Gather the following:

1-Touch Server for Windows Installation CD

All Versions of the Microsoft Windows CDs supported in the enterprise and their license numbers

All applicable Microsoft Service Packs and Security Updates/Hotfixes

All non-native network interface and mass storage drivers used in the enterprise

Create any Custom Scripts that are required for the 1-Touch Recovery.

Install the 1-Touch server software. See Install the 1-Touch Server Software - Windows for step-by-step instructions. Installing this software will also install the Windows File System iDataAgent.

Back up the system state subclient and the default subclient for your client. See Backup Data for more information.

For a standard recovery, complete the following post-install or preliminary activities where required.

1-Touch for Windows does not support client recoveries with the IPv6 protocol.

Do not move the boot partition to a new partition location on the target computer if the 1-Touch recovery computer is a domain controller. Filtering the boot.ini file during the recovery of a domain controller will not work because the process copies and reapplies the boot.ini file from the backup during the automated recovery.

Use the 1-Touch GUI to add or remove the listed items from the disk. Do not create or remove any items, folders or files manually. Each item is tagged by the 1-Touch Interface in order to be available in selected lists for use or removal.

Install Restore Updates on the Client

Manage the Windows Distribution Shares

Integrate Service Packs for non-X86 Windows Distribution Packages

Integrate Specific Hotfix for Windows 2000

Manage the Windows Device Drivers

Prepare the 1-Touch Configuration and Answer Files/Profiles on the 1-Touch Server

Create the 1-Touch Boot CD

The 1-Touch Administrator Password during recovery process is 1Touch as noted under Reboot the System

In addition, some degree of setup is required after you boot the client for 1-Touch if you have chosen to perform a dissimilar disk restore as discussed in the following sections:

Dissimilar Disk Restore: Initialize the Destination Disks

Features - 1-Touch

of 74

A full system restore of a Microsoft Windows 2008 Server requires the administrator to provide the product license key. The following message will appear on the Windows login screen after a full system recovery from a backup that contained an activated product key:

An unauthorized change was made to Windows. You must retype your Windows Server Product Key to activate the license.

In this release, you will be required to provide the activated product key again in order to log in to the recovered client.

When rebuilding an entire computer, it is required that the Windows service pack and hotfixes in the backup are also applied on the target computer. The service pack on the target must always match the backup prior to a restore.

The hotfixes can be restored without being applied to the target only by using the Overwrite files, unconditional overwrite restore option.

The hotfixes will not be restored if the Overwrite files, Overwrite if file on media is Newer restore option is selected, and this will produce the following Windows Vista or Server 2008 login error: An unauthorized change was made to Windows. The solution is to apply matching hotfixes to the target prior to the restore.

If the backed up computer had Internet Explorer 8.0 and the current computer has Internet Explorer 7.0, then the Overwrite files, unconditional overwrite restore option must be selected when performing a restore operation.

A restore of System State components requires that the Job_Results folder be on same drive as Microsoft Windows.

On the 1-Touch Server, to change the Job_Results path:

1. Edit the ..\SystemRecovery\ClientFiles\%ClientName%\Input.txt file.

2. Change the drive in this line: szNewJobResultDirectory=E:\Galaxy70b74\iDataAgent\JobResults

After restoring System State components, you can change the Job_Results folder back to the original location.

Determine whether the 1-Touch boot CD-ROM that you created in the preceding task will recognize the disk hardware in your computer. You may need to include one or more mass storage drivers in order to have access to all the disks and proceed with the recovery. It is well worth the effort to know this ahead of time before an actual disaster. See Test 1-Touch Boot CD-ROM for Mass Storage Recognition for step-by-step instructions.

Before you restore your client in a non-Storage Area Network (SAN) environment, ensure that the same disks that were available to the client during backup are also available during recovery. However, if storage is available via a SAN, 1-Touch attempts to access all the drives. Under this scenario, if the configuration is different from that when the system state backup was collecting the information, 1-Touch will fail when it attempts to access the unavailable drives. Therefore, ensure that the configuration is identical.

Preparing 1-Touch Configuration and Answer Files/Profiles

You can create or modify client preparation answer files or 1-Touch Recovery Profiles from either the 1-Touch Server or the 1-Touch client being recovered. Creation/modification can be done before the 1-Touch Recovery from the 1-Touch Server GUI and after the client has been booted for 1-Touch Recovery from the client boot CD. The associated processes are always run on the 1-Touch Server, and the associated files are always saved to the 1-Touch Server.

1-Touch Recovery Profile

Profile Manager allows the 1-Touch administrator or user to preselect computer recovery options for a specific group of computers. Profile selections include the Windows version to apply, mass storage

Dissimilar Disk Restore: Map, Create, and Unmap Volumes

Features - 1-Touch

of 74

drivers, NIC drivers and restore options. The profile can be selected for the client recovery rather than individually providing the same answers to each client. 1-Touch Recovery Profiles are saved under System Recovery\Profiles on the 1-Touch Server.

Using Custom Scripts

The Custom Scripts file feature in part allows you to customize the [guirunonce] section of the unattend.txt file to meet Windows deployment requirements for your environment. Custom scripts are incorporated into the recovery by selecting the Custom Scripts option in the 1-Touch Client Preparation Wizard. As customization requirements grow, the features for scripting will be enhanced. For more information, see Custom Scripts.

Back To Top


The following sections explain how to recover data in case of disaster.


Before You Begin

If you are Restoring to a Computer with a Different Hardware Configuration, review the procedure in this section before starting the recovery.

To recover data, use one of the following procedures, as appropriate:

Standard Procedure


Back To Top

Standard Procedure

By adding 1-Touch ISO images to a PXE server repository, you can configure the PXE server to boot a PXE client from the 1-Touch ISO image and then run the 1-Touch Recovery. See Boot and 1-Touch Recover a Client using the 1-Touch ISO Image on a PXE Server for step-by-step instructions.

If you need to manually restore the onetouchinfo.cvf file for troubleshooting purposes, you can restore the file out of place by providing an absolute restore path in the CommCell Console. However, be aware that additional registry files (which you can delete afterwards) will also be restored.

Use the following procedure to manually restore the onetouchinfo.cvf file:

1. At the backup set level, right-click and select Restore.

2. At the backup set level, right-click and select Restore.

3. Type an absolute restore path (e.g., \[System State]\Special Components\One Touch Files).

4. Deslect Restore to Same Paths and provide a path to which to restore the onetouchinfo.cvf file and the registry.

5. Click OK.

Features - 1-Touch

of 74


Install Restore Updates on the Client

1. Before you start the recovery, download the necessary restore updates to the 1-Touch Server's cache. See Run CopyToCache for step-by-step instructions. Note the following:

The \config\update.ini file for the selected update should include the following entry: [ONETOUCH]=Yes. Any Windows File System patch with this entry will be copied to the 1-Touch Server cache.

The location of the cache is determined by the following entry in the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Instance\SystemRecoveryServer\sZIMAGESSHARENAME=Images

The default Images is used by other processes and should not be changed.

Once copytocache is run successfully, it creates a CVUpdates folder and stores the update in the following directory: <software_install_directory>\SystemRecovery\Images\CVUpdates.

2. Continue with the following procedures. When you run the 1-Touch Client Preparation wizard (see Prepare the 1-Touch Configuration and Answer Files/Profiles on the 1-Touch Server), the command to deploy the updates after the software installation will be included in the fullida.bat file. The associated script in this file will deploy the updates silently.

3. Verify that the updates get applied after the Windows File System iDataAgent is installed.

Manage the Windows Distribution Shares

1. From the 1-Touch dialog box, click Windows Distribution Manager. Then click Next.

2. In the Manage Windows Distribution Shares dialog box, to administer your Windows Distribution shares, do one or more of the following as appropriate:

Click the appropriate Windows Distribution share type for the recovery from the Windows Distribution Share Name list if available. If you need to include a new share type for the recovery, click Add, provide a new folder name and description along with the Windows version, source location, and product license key in the Add Windows Distribution Share dialog box, and then click Add.

To delete a share type, click the appropriate Windows Distribution share type from the Windows Distribution Share Name list, click Remove, and then click OK from the Windows Distribution dialog box.

To apply Windows updates directly to the Windows Distribution image, click Updates and administer as appropriate.

3. Repeat the preceding step for each Windows Distribution type that you need to manage.

4. Click Done.

5. In the Hotfixes/Service Packs dialog box, to administer your Hotfixes and service packs, remove from the list Hotfixes/service packs by clicking Remove and administering as appropriate. Removing a Hotfix or service pack from the 1-Touch list of available Hotfixes does not remove the Hotfix from the Windows Distribution to which it has been applied. Once a service pack or Hotfix is applied/slipstreamed to a Windows Distribution, it cannot be removed. To apply Hotfixes/service packs to Windows Distributions, browse and/or select the appropriate Hotfixes/service packs from the first list, click the Windows Distributions to which you want to apply these items in the second list, and then click Apply.

Integrate Service Packs for non-X86 Windows Distribution Packages

Whenever you attempt to integrate a service pack into a Windows Distribution folder for a processor type (e.g., X64, IA64, etc.) that does not match the version of the 1-Touch Server where the distribution folders reside, the message "update.exe is valid, but is for a machine type other than the current machine" is displayed. The Windows Distribution will have to be copied to a computer with the matching processor type, slipstreamed with the Service Pack, and then imported using the 1-Touch Windows

Features - 1-Touch

of 74

Distribution Wizard. See Integrate Service Packs for non-X86 Windows Distribution Packages for step-by-step instructions.

Integrate Specific Hotfix for Windows 2000

1-Touch will restore the Updates (or Hotfixes) that were applied to the client at the time of the backup. There may be cases where interim security or restore Hotfixes are required.

For Windows 2000, if Hotfix KB828741 is in the backup, it must be applied to the target; otherwise, the system state restore will fail. Slipstream this fix into the Windows 2000 Distribution folder. KB828741 is also known as Microsoft Security Bulletin MS04-012, "Cumulative Update for Microsoft RPC/DCOM (828741)" at http://www.microsoft.com/technet/security/bulletin/ms04-012.mspx.

The 1-Touch option to integrate, or slipstream, Security Updates and Service Packs into Windows distribution shares supports Update.exe 5.4.15.0 or any later version. KB828741 is a lower version (5.4.1.0) and requires manual integration. Information about "How to integrate software updates into your Windows installation source files" can be found at http://support.microsoft.com/default.aspx?kbid=828930.

When integrating Updates in your distribution share(s), be sure to integrate the Service Pack first. Then integrate the Updates. If post-Service Pack Updates are integrated before the Service Pack, you will not be able to include the Service Pack in the Windows Distribution share.

Manage the Windows Device Drivers

Windows Driver Manager is used to import all third-party or vendor-supplied Windows mass storage and network interface drivers (NICS). When preparing drivers for 1-Touch recovery, keep in mind any non-native Windows mass storage and network interface drivers that the client may need and import them to the 1-Touch driver inventory.

The 1-Touch Client Preparation Wizard prepares the client for silent deployment of Windows; therefore, the drivers selected here would be the same drivers required during an interactive Windows installation. The 1-Touch Boot CD Wizard prepares a boot CD for the client to connect to the 1-Touch Server on the network.

In view of all of this, be sure to consider the following:

If third-party mass storage drivers are needed, they are standard vendor-supplied Windows drivers.

Vendors may supply both a Remote Installation Service (RIS) version and a native version for the Windows installation. If a RIS version is provided, the vendor usually recommends this driver be used for a WINPE (or 1-Touch) Boot process. If only a native Windows driver is provided, it is commonly supported for the 1-Touch boot process.

1. From the 1-Touch dialog box, click Windows Driver Manager. Then click Next.

2. In the Driver Manager dialog box, ensure that all the drivers for all the Windows operating systems are available for the recovery. To this purpose, click an operating system in the OS Family list, click the type of driver in the Driver Type list, and then view the Available Device Drivers field for the available drivers for that operating system.

3. To include a new driver for the operating system, click Add, populate the Add Device Driver dialog box as appropriate, and then click Add. If you want to remove a driver from the available list for the operating system, click the driver in the Available Device Drivers field and then click Remove.

4. Repeat the previous two steps for each operating system and driver type.

5. When you are finished, click Done.

Prepare the 1-Touch Configuration and Answer Files/Profiles on the 1-Touch Server

A successful restore requires CommCell user access, valid system state data to restore, and File System iDataAgent Services to be running on the 1-Touch Server to which the client information files are being restored.

A Hotfix or Service Pack that is slipstreamed into a Windows integrated install cannot be removed.

Features - 1-Touch

of 74

1. On the 1-Touch server, launch 1-Touch from the Start | Programs menu.

2. Click Next from the Welcome screen.

3. From the 1-Touch dialog box, click one of the following options:

1-Touch Client Preparation Wizard if you want to do either of the following:

Prepare your answer files without using a 1-Touch Profile

Use or modify and use a 1-Touch profile for your answer files

1-Touch Profile Wizard if you want to create or modify a 1-Touch Profile

If you click 1-Touch Client Preparation Wizard, skip the next step. If you click 1-Touch Profile Wizard, go to the next step.

4. Decide whether you want to create a new profile or modify an existing profile.

To create a new profile, click Select/Modify Existing Profile and type the name of the new profile in the list. Then click Next and go to Select Shares, Drivers, and Filters.

To change and use an existing profile, click Select/Modify Existing Profile and select the profile from the list. Then click Select All (to select all the Change options listed) or click one or more of the desired Change options, click Next, and go to the appropriate steps in Select Shares, Drivers, and Filters.

To use an existing profile without changing it, select it from the 1-Touch Client Preparation Wizard.

5. In the Client Information dialog box, select from the list the 1-Touch Client to prepare configuration files for recovery. Provide the CommCell Console user name and password. Then click Next.

Access 1-Touch Recovery Information

6. From the Client Configuration dialog box, do one of the following to access the 1-Touch Recovery information file for the recovery.

To select a backup set to restore from, click Restore the configuration information from backup of this client and then click a backup set from the list provided. Also, click the appropriate backup based on time considerations and, optionally, click the desired restore copy precedence.

To provide the path to a client OneTouchinfo.cvf file that was previously restored, click Retrieve the configuration information from the specified location and use the Use an existing 1-Touch configuration that has already been restored space to specify the appropriate path. Browse to the previously restored files located at %1-Touch Server install%\SystemRecovery\ClientFiles\InfoFiles.

Click Next.

7. If you selected to Restore the configuration information from backup of this client, the "Please wait while processing" progress bar appears while files are restored from the system state portion of the backup selected.

8. From the 1-Touch Server Share Information dialog box (if displayed), do the following:

Accept or modify the 1-Touch Server IP address/share name (these items should be correct if you are running on the 1-Touch server)

Type a user name and password with access to the identified share using the format domain\useror computer\user.

Click Next.

Select Method to Prepare Client Answer Files

9. In the 1-Touch Profile Information dialog box, do one of the following to prepare your client answer files (which will be restored to the 1-Touch Server\SystemRecovery\ClientFiles\%clientname% share).

Features - 1-Touch

of 74

To use an existing profile for the client answer files, click Select/Modify Existing Profile.

To use a profile without changing it, select a profile from the list, click Next, and go to Administer NIC Settings and Drives.

To modify a profile before you use it, click Select All (to select all the Change options listed) or click one or more of the desired Change options, click Next, and go to the appropriate steps for the items to be changed starting with the next step.

To create answer files without using a profile, click Create Client Answer Files. Then click Next and go to the next step.

Select Shares, Drivers, and Filters

10. In the Select a Windows Distribution Share dialog box, to populate the WINDIST folder, click the appropriate Windows Distribution share type for the recovery from the Share Name list. If you need to include a new share type for the recovery, click Add, enter the appropriate information in the Add Windows Distribution Share dialog box, and then click Add. Then click Next.

11. In the Select Windows Mass Storage Driver dialog box, determine if the mass storage driver that was detected at the time of backup is appropriate. If not, click the name of the mass storage driver for the client to be used during the recovery from the Select the mass storage driver list. If required, click Add and the appropriate mass storage driver name to include a new mass storage driver for the recovery. When you are ready, click Next.

12. In the Select Windows PnP Drivers dialog box, click the name of the plug and play device drivers for the client to be used during the recovery from the PnP Drivers for the Client lists. If required, click Add and the appropriate plug and play device driver name to include a new plug and play device driver for the recovery. When you are ready, click Next.

13. In the Restore Options dialog box, select as appropriate options to do the following: restore the system state, overwrite data during the restore, administer disk mapping, and add Custom Scripts. Then click Next.

14. In the Add Excluded Folders for Restore dialog box, include in the space any drives and/or folders to be filtered from the restore. Use Add and Remove as appropriate. Then click Next. If you are using the 1-Touch Profile Wizard, skip the next two steps.

Administer NIC Settings and Drives

15. In the Internet Protocol (TCP/IP) Properties dialog box if displayed, accept or modify the network interface card (NIC) settings for the client being recovered. Try to bind to the first network adapter that is displayed. Repeat this step for each additional NIC (if any) by using the list. Then click Next.

16. In the Disk Layout dialog box (if displayed), use the scroll bar to view all the drive information found at backup time for the client. Also, if you want to recreate the partitions of and format selected drives with this information, click the drives and Recreate partitions and format the selected drives. To perform a dissimilar disk restore, click Show partition layout during recovery on the target computer (you can start the dissimilar disk restore later). To leave the target drives intact, do not click this option. You can also format only the Windows system drive by clicking this drive and the Format the Windows system drive only option. Click Next.

Summary Screen

If you are booting the 1-Touch client for recovery, this step will be displayed later in the procedure.

If you select to Recreate partitions and format the selected drives, a warning will appear if OEM partitions were present during the backup. OEM partitions can be recreated but will be empty upon completion.

If you do NOT select Recreate partitions and format for selected drives, you must select to format the system disk.

Features - 1-Touch

of 74

17. Review the Summary Screen. Click Back as appropriate to make any changes. Then click Done.

18. To save a new profile, click Finish. To save a modified 1-Touch profile, click Save Profile As, provide a profile name in the space, and press Enter. To save an existing profile that you did not modify, click Finish. To save the client answers but not a profile, click Done.

Create the 1-Touch Boot CD

1. From the 1-Touch dialog box, click 1-Touch Boot CD Wizard. Then click Next.

2. In the Processor Type dialog box, click in the list the processor type of the affected client(s) for the 1-Touch Boot CD. Then click Next.

3. In the Mass Storage Drivers dialog box, click the mass storage drivers that you want to include in the 1-Touch Boot CD. The 1-Touch Boot CD requires Windows 2003-compatible drivers. To include a new mass storage driver, click Add, populate the Add Device Driver dialog box as appropriate, and then click Add. Once you have selected all the desired drivers, click Next.

4. In the Network Adapter Drivers dialog box, select the network adapter drivers that you want to include in the 1-Touch Boot CD. To include a new network adapter driver, click OK, populate the Add Device Driver dialog box as appropriate, and then click Add. Once you have selected all the desired drivers, click Next.

5. In the Boot CD ISO Output File dialog box, click in the Save in list the destination location for the 1-Touch Boot CD ISO image (e.g., D:\1-Touch_32.iso). Output including text similar to the following should be displayed. .......... Scanning source tree complete (1215 files in 47 directories) Computing directory information complete Image file is 189636608 bytes Writing 1215 files in 47 directories to D:\1-Touch_32.iso 5% complete

Upon completion, "The ISO file is created" message should be displayed. Click OK.

6. Once the wizard finishes, burn the ISO image to the 1-Touch Boot CD using any software that is ISO-9660-compliant.

Boot the 1-Touch Client for Recovery

1. Boot the 1-Touch client using the CD-ROM that you created from the 1-Touch boot image ISO file.

2. From the Welcome screen, click Next.

3. As prompted, indicate whether DiskPart recognizes all your hard disk devices based on the displayed list of devices. If so, select Yes, click Next, and go to the next step. If not, enter No and follow the procedure in Enable 1-Touch Boot CD-ROM for Mass Storage Recognition before continuing with this

To avoid network driver errors during a boot, verify that the network drivers imported to the boot CD are WINPE- or Remote Installation Service (RIS)-compatible if the vendor provides an RIS-compatible driver. Many vendors provide native Windows and RIS drivers with the hardware. If both drivers are provided, the RIS driver is provided for a WINPE or RIS boot process and the native version is provided for the Windows Installation. If only a native Windows driver is provided, you can use this driver for a WINPE or RIS boot process. For more information, see Perform 1-Touch Recovery with Broadcom NetXtreme II Driver Workaround.

During the Windows installation process of a 1-Touch Recovery, the Windows Administrator password is set as 1Touch. Upon completion of the 1-Touch Recovery, the Administrator's original password will be restored from the backup.

Features - 1-Touch

of 74

procedure.

4. In the Server Information dialog box, type the IP address of the 1-Touch Server along with your user name and password. Then click Next.

5. In the Client Information dialog box, select the name of the computer (i.e., the client name) to restore along with its IP address, subnet mask, and default gateway. Also, do one of the following:

If your answer files are already created, click Next. 1-Touch Recovery will now automatically connect to the 1-Touch ClientFiles\%clientname% share, and the automated recovery will begin. Go to the next step.

If you have never used the 1-Touch Client Preparation wizard to prepare answers for this client, click Create Client Files, click Next and go to Access 1-Touch Recovery Information in Prepare the 1-Touch Configuration and Answer Files/Profiles on the 1-Touch Server.

If your answer files are already created and you want to restore to different hardware and to modify disk targets (e.g., partitions sizes), click Dissimilar Map and go to Dissimilar Disk Restore: Initialize the Destination Disks.

6. Review the Summary screen. If no changes are required, click Next. The recovery is now completed.

Dissimilar Disk Restore: Initialize the Destination Disks

Use the following procedure to initialize the destination disk(s) to which you will be mapping the volumes you are recovering.

1. From the Customize the Disks dialog box, right-click the destination disk that you want to initialize. Destination disks are represented in the lower part of the dialog box

2. From the popup menu, click the disk type that you want to assign to the destination disk.

3. Wait a moment until some processing completes.

4. Repeat this procedure for each destination disk that you want to initialize. If you will be restoring mirror, span, stripe, or raid volumes, be sure to initialize at least one additional disk if you have not already done so. Then click Done.

5. The disks that you initialized will be displayed. If you want to initialize additional destination disks, click Cancel and repeat this procedure for the desired additional disks.

6. When you are finished, click Done. Your disk(s) should now be initialized. Only the disk(s) that you have initialized will now be displayed in the dialog box.

Dissimilar Disk Restore: Map, Create, and Unmap Volumes

Use the following procedure to map the volumes you are recovering to destination disks, create the volumes on these disks, and unmap the volumes from these disks. Note that you will be able to map volumes only to destination disks that have enough space to accommodate the volumes.

1. From the Map the Disks dialog box, click the source disk volume that you want to map to the destination disk. Source disk volumes are represented in the upper part of the dialog box.

2. If you are mapping a mirror, span, stripe, or raid volume, the Customize the Volumes dialog box will be displayed. In such a case, change as appropriate the properties for or items associated with the volume, including the type, format, target disk(s), size, and assigned letter. Then click OK.

3. Click the destination disk where you want to create the volume that you are mapping. The volume will be displayed in the destination disk, and it will be highlighted in the source disk. If you are mapping a mirror, span, stripe, or raid volume, be sure to click at least one additional destination disk.

4. The Customize the Volumes dialog box will be displayed if at least one of the following is true: partition style that you want to map on the destination disk is different from that on the source disk; or, size of the volume that you want to map is larger than the amount of space available on the destination disk. In such a case, change the affected items as appropriate, make any other desired changes, and then click OK.

Features - 1-Touch

of 74

5. If you want to customize the volume that you are mapping and have not already done so, go to the next step. Otherwise, skip the next two steps.

6. Right-click the source disk containing the volume that you are mapping.

7. In the Customize the Volumes dialog box, change as appropriate the properties for the volume as discussed in an earlier step in this procedure.

8. If you want to unmap a volume from the destination disk, right-click the volume on the disk ("Unmap" should be displayed). Repeat this step for each volume that you want to unmap.

9. Repeat the previous steps for each volume that you want to create on the destination disk.

10. Once you are done mapping, creating, and unmapping volumes, click OK. The 1-Touch Recovery will install the Operating System and the File System iDataAgent, and it will then automatically execute a full system rebuild of the client

Reboot the System

Following the rebuild, enter y for the prompt that asks you if you want to reboot. Also, if you re-created disk partitions, reboot the client again as prompted. This is necessary because of changes made to the Globally Unique Identifier (GUID) for each volume.

Top of Section


Windows Server 2000 and 2003

To recover a system on a cluster using 1-Touch:

Recover the Primary Cluster Node and Quorum Disk

1. Run the 1-Touch Client Preparation Wizard (see Prepare the 1-Touch Configuration and Answer Files/Profiles on the 1-Touch Server), and select to format and partition all disks that are owned by this cluster node. Select also the quorum disk.

2. Turn off all nodes except the primary node to be recovered.

3. Perform a 1-Touch Recovery on the primary node.

4. When the "Full iDataAgent Restore job completed. Do you want to reboot?" message appears, enter y (yes).

5. When the "New Hardware found. Windows has finished installing new devices.... Do you want to restart your computer now?" message appears, enter y (yes).

6. Restart the computer. Then go to the <install directory>\base folder and enter the following command at a command prompt: authorutil.exe -cluster

7. If a failure message appears, restart the computer to allow the cluster services to start.

8. If the cluster disks were repartitioned, a failure message may appear. This is because the disk GUIDs for the quorum have been changed. In such a case, restart the computer to allow the cluster services to start.

Restore Program Files for the Virtual Server

The cluster is now available. The Bull Calypso Communications Service (GxCVD) and Bull Calypso Client Event Manager (GxEvMgrC) cluster resources are restored; however, the program files required to start and run these resources must be restored to the virtual server's disk on which they resided. You must restore the program files for the virtual server to the physical node that owns the virtual disk since the virtual server's services are not yet running. You can either select all the virtual disk data and restore this data using this method, or you can restore only the program files to get the services started and then restore the rest of the data using the virtual server's File System iDataAgent.

Features - 1-Touch

of 74

1. Browse and select all the desired data for the virtual server disk(s) and restore this data to a different computer. The destination computer will be the physical node that currently owns the virtual disk(s). Select an in-place restore.

2. Using the Cluster Administrator, bring the cluster resources online.

Recover Passive Node(s)

1. Run the 1-Touch Client Preparation Wizard (see Prepare the 1-Touch Configuration and Answer Files/Profiles on the 1-Touch Server), and either select to format only the system disk or to recreate and partition selective disks that are owned by this passive node.

2. Perform 1-Touch Recovery on the passive node.

3. When the "Full iDataAgent Restore job completed. Do you want to reboot?" message appears, enter y (yes).

4. When the "New Hardware found. Windows has finished installing new devices.... Do you want to restart your computer now?" message appears, enter y (yes).

5. Restart the computer. Then go to the <install directory>\base folder and enter the following command at a command prompt: authorutil.exe -cluster

6. A failure message may appear if the disk GUIDs were changed during a reparation at any time. Allow several minutes for the cluster to correct itself and the cluster services should start.

Windows Server 2008

Perform an Authoritative Restore

An authoritative restore is performed only if the administrator accidentally alters the cluster configuration or deletes a large number of resources and therefore needs to revert to a previous cluster configuration. Before you perform an authoritative restore of the cluster configuration database, ensure that all cluster nodes and services are running.

Authoritative cluster restores are not supported using the 1-Touch recovery procedure. An authoritative restore requires that the cluster services are running. For more information, see Restoring Cluster Databases: Authoritative Restores.

Perform a Non-Authoritative Restore

A non-authoritative restore is performed for the scenarios listed below.

Single node in a cluster fails completely (no boot) and the shared disks are still functional

Complete loss of all nodes and storage

To perform a non-authoritative restore of the cluster configuration database:

When the entire cluster is down, perform a non-authoritative restore of the first node and then start adding nodes to the cluster. This is essentially a non-authoritative restore and the cluster service does not need to be running when this is performed.

1. Perform a 1-Touch Recovery on the cluster node. The default (non-authoritative restore) option for Cluster DB is always selected for a 1-Touch Recovery and this option cannot be changed.

2. Enter y (yes) when the following message appears:

Full iDataAgent Restore job completed. Do you want to reboot?

3. If the restored node shows 'unavailable' in the failover cluster, evict and add the restored node.

If the cluster disks were repartitioned, a failure message may appear because the disk GUIDs for the quorum have been changed. If the cluster service does not start, or if you see Event ID 1034 in the System Event Log, reference the KB 305793 and KB 280425 Microsoft Knowledge Base articles on http://support.microsoft.com/ to get the cluster service back online.

It is recommended that you do not perform an authoritative restore of the cluster

Features - 1-Touch

of 74

Top of Section




Back To Top

after this procedure without performing a full backup.

Features - 1-Touch

of 74

features - 1-touch - bull on-line support...

Documents