IBM AIX Supplement - Cristie Software · PDF fileIBM Tivoli Storage Manager ... Cristie...

Cristie Software Ltd.

New Mill

Chestnut Lane

Stroud GL5 3EH

United Kingdom

Tel:+44(0)1453 847000

Fax:+44(0)1453 847001

[email protected]

Cristie Data Products GmbH

Nordring 53-55

63843 Niedernberg

Germany

Tel: +49 (0) 60 28/97 95-0

Fax: +49 (0) 60 28/97 95 7-99

[email protected]

Cristie Nordic AB

Knarrarnäsgatan 7

164 40 Kista

Sweden

Tel:+46(0)8 718 43 30

[email protected]

March 2015

IBM AIX Supplement

Version 2.2.2

Copyright © 2013-2015 Cristie Software Ltd.All rights reserved.

The software contains proprietary information of Cristie Software Ltd.; it is provided under a license agreementcontaining restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of thesoftware is prohibited.

Due to continued product development this information may change without notice. The information and intellectualproperty contained herein is confidential between Cristie Software Ltd. and the client and remains the exclusiveproperty of Cristie Software Ltd. If you find any problems in the documentation, please report them to us in writing.Cristie Software Ltd. does not warrant that this document is error-free.

No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by anymeans, electronic, mechanical, photocopying, recording or otherwise without the prior written permission of CristieSoftware Ltd.

IBM Tivoli Storage Manager (TSM), AIX and TIVOLI are trademarks of the IBM Corporation.

IBM Virtual I/O Server (VIOS) is a trademark of the IBM Corporation.

NetWorker and Avamar are trademarks of the EMC Corporation.

Simpana is a trademark of CommVault Inc.

vSphere, vCenter and vCloud are trademarks of VMware Inc.

Hyper-V is a trademark of Microsoft Corporation.

Azure is a trademark of Microsoft Corporation.

Amazon Web Services (AWS) and Amazon Elastic Compute Cloud (EC2) are trademarks of Amazon.com, Inc.

CloneManager® is a registered trademark of Cristie Software Ltd..

Cristie Management Console (CMC), PC-BaX, UBax, Cristie Connect, Cristie Storage Manager (CSM), SDB, ABMR(Bare Machine Recovery for EMC Avamar), EBMR (Bare Machine Recovery for EFi), EFi (Easy File backup), NBMR(Bare Machine Recovery for EMC NetWorker), SBMR (Bare Machine Recovery for CommVault Simpana), TBMR (BareMachine Recovery for TSM), CBMR (Cristie Bare Machine Recovery), Recovery Console (RC) and CRISP (CristieRecovery ISO Producer) are all trademarks of Cristie Software Ltd.

Cristie Software LtdNew Mill

Chestnut LaneStroud

GL5 3EHUK

Tel: +44 (0) 1453 847000Email: [email protected]

Website: http://www.cristie.com

3Contents

Copyright © 2013-2015 Cristie Software Ltd.

Contents

1 Introduction 4

................................................................................................................................... 41.1 Document conventions

2 Download the software 5

3 Licensing 6

4 Product installation 7

................................................................................................................................... 74.1 Dependencies

................................................................................................................................... 84.2 Create the CloneManager 'Live' Environment for AIX

5 Run a clone sequence 10

................................................................................................................................... 105.1 Create source configuration

................................................................................................................................... 105.2 Running the agent on the clone source

................................................................................................................................... 105.3 Running the clone from the clone target

4

Cristie CloneManager 2.2 AIX Supplement

1 Introduction

CloneManager for AIX enables a live copy (a clone) of a running IBM AIX machine to be made to aIBM VIOS virtual environment (Hypervisor) or to a new physical machine.

To accomplish this, an Agent is run on the source machine and a CloneManager 'Live'Environment for AIX is booted on the target machine. This arrangement allows an existingmachine to be migrated either directly to new hardware or virtualised to VIOS.

A clone target system maybe also used in warm standby mode. This is where a shortsynchronisation process is run to bring a previously cloned system up-to-date prior to booting intooperational mode. This process is called CloneSync.

This document describes the steps required to install, license, configure and use the CristieCloneManager for AIX product. Refer to the Readme for installation requirements and late breakinginformation associated with this release.

Note: It is only possible to clone AIX systems to a VIOS Hypervisor

Some components are used from the Windows CloneManager itself. These are the CM-Console andCristie Token Manager. They are required to provide and maintain a source of clone tokens. Refer tothe CM-Console and Cristie Token Manager discussion in the separate CloneManager User Guideversion 2.2 dated March 2015 for a full discussion.

The following assumes the reader is already familiar with CloneManager and VIOS concepts andterminology.

For this release of the software only IBM AIX versions 5.3, 6.1 and 7.1 are supported.

1.1 Document conventions

The following typographical conventions are used throughout this guide:

/etc/passwd represents command-line commands, options, parameters, directorynames and filenames

Next > used to signify clickable buttons on a GUI dialogue

Note: describes something of importance related to the current topic

5Download the software


2 Download the software

At the moment CloneManager for AIX is supplied upon request. Please contact [email protected] inthe first instance. After successful evaluation you will then be provided with an FTP download link forthe AIX installation RPM package.

mailto:[email protected]

6


3 Licensing

CloneManager for AIX uses token-based licensing. A token represents a license from Cristie toperform a clone or CloneSync operation as described in this document. Tokens are normally pre-paidfor by the customer. No free tokens are supplied with the product.

By default, a Windows based Cristie Token Manager must be installed and available at the time ofcloning. This can run stand-alone or as part of an installed CM-Console. However to add and managetokens a Windows based CM-Console must also be installed.

Therefore if an existing CM-Console and Cristie Token Manager are installed then they can be usedwith CloneManager for AIX. If not then both the CM-Console and Cristie Token Manager must beinstalled on a convenient Windows host system. Refer to the main CloneManager documentation fordetails.

Note: Currently only Windows versions of the Cristie Token Manager and CM-Consoleare available.

7Product installation


4 Product installation

This section describes how to install the CloneManager for AIX product component to provide AIXclone support.

AIX clone support is similar to Windows/Linux in that it requires an Agent program to be installed onthe clone source machine. Unlike Linux however, the clone target 'Live' environment ISO must becustom built for each machine to be cloned and created on that same machine for the version ofAIX in use.

Note: The AIX installation package rpm provides both the Agent installation files and ISOcreation tool.

The AIX installation package provides the following components:

CloneManager Agent (CDS) in rpm form - to be installed on the clone source machine. Thisallows the CloneManager 'Live' Environment for AIX to communicate with the source machine.

A tool to create the dr.iso (default name) ISO is also installed as part of the rpm installationpackage on the clone source machine. This ISO must then be booted on the AIX clone targetmachines in the VIOS environment or physical target and allows the source machine tocommunicate with the target. This ISO is termed the CloneManager for AIX 'Live' environmentISO. The ISO may be optionally burnt to CD for use with physical hardware if required.

Note: the two AIX components above are provided in the same rpm package.

Before installing clonemanager-release-2.2.2.aix5.1.ppc.rpm please refer to the Dependenciessection to determine what other software must be installed to provide full CloneManager for AIX/AIXclone support. The RPM package should be installed on the system to be cloned.

Note: To install CloneManager you must be logged on as the root user.

After satisfying all dependencies install CloneManager for AIX using the clonemanager-release-2.2.2.aix5.1.ppc.rpm installation package. Start a terminal session on the host AIX system and enter:

rpm -ivh clonemanager-release-2.2.2.aix5.1.ppc.rpm

When the installation is complete enter clonemanager to display the main menu.

4.1 Dependencies

Before installing CloneManager a number of dependencies may be required if they are not alreadyinstalled on your server.

These are:

SSH and SSL

OpenSSH_6.0.0.6101.taropenssl-fips-12.9.8.2400.tar

RSYNC

gettext-0.17-1.aix5.1.ppc.rpm may have to install with --nodepspopt-1.16-1.aix5.1.ppc.rpmrsync-3.1.0-1.aix5.1.ppc.rpm

8


CLONEMANAGER

ncurses-5.2.aix5.1.ppc.rpmlibxml2-2.6.21.aix5.1.ppc.rpm

FILESYSTEM

If when installing CloneManager for AIX you see a message asking for minimum space requirementsthen the filesystem size must be changed

chfs -a size=+1000000 /

chfs -a size=+1000000 /opt

Once the above dependencies have been satisfied you are now ready to install Product installation

4.2 Create the CloneManager 'Live' Environment for AIX

When running clones a CloneManager 'Live' Environment for AIX ISO is always first booted on thenew VM target. This allows the target machine to be seen by, and synchronise with, the clonesource machine for file transfer.

It is the responsibility of the User to create the bootable CloneManager 'Live' Environment for AIX ISOusing the tools provided as part of the installation package.This section describes how to create thisISO in preparation for upload to the VIOS Hypervisor or to be booted on the target physical machine.

First install the ISO build components. This must be performed on the machine to be cloned; i.e. themachine currently containing the CloneManager for AIX install.

The generated ISO should be uploaded to the IBM VIOS ISO/tape virtual storage to ensure it isavailable for an AIX clone. If cloning direct to an LPAR target then attach this ISO on the target as aboot device. If cloning to a physical machine boot it with this ISO.

The ISO generation step normally needs to be performed on every different AIX machine to becloned. However if multiple systems with the same AIX OS version and hardware configuration are tobe cloned then only one common ISO needs to be generated. So, for example, you would createone version of the ISO for version 5.3, another for 6.1 and a third for 7.1.

To create the ISO select Make Recovery CD option from the Main Menu.

9Product installation


ISO Location: The ISO can be created either on the source machine or on a mount share.The file size is about 400Mb so this space must be available if creating locally. Change theISO name from dr.iso as required, perhaps including the AIX OS version within the filename.

Temporary Storage: usually left as default setting, change as required

NFS Server: leave as default

Terminal Type: leave as default

To begin the ISO creation select OK followed by Enter.

An ISO creation successful message is displayed on completion. If created locally the ISO must becopied to a location for subsequent upload to the VIOS environment.

10


5 Run a clone sequence

This discussion assumes a suitable target VM or physical machine is available. If using a physicalmachine ensure it matches the network and disk configuration of the source. Disks must be thesame in number and be at least as large as the source but can be bigger. If using VIOS a target VMmust created to match the source RAM, network and disk configuration. As for physical machines,disks must be the same in number and be at least as large as the source but can be bigger.

To prepare the clone operation first start the Agent on the clone source machine. The clone is drivenfrom the the CloneManager 'Live' Environment for AIX running on the clone target.

Note: Ensure the machine configuration is created on the clone source prior to startingthe clone

5.1 Create source configuration

The machine to be cloned (i.e. the clone source machine) must contain a configuration. This iscreated automatically when the CloneManager for AIX is first installed. The configuration is createdin:

/CLONEMANAGERCFG/disrec.xml.

It is advisable not to change the location of this file. If however any hardware or filespace changesare made the configuration must be recreated - this is very important. This can be done from theSystem Configuration options or from a terminal session by entering the command clonemanagercfg directly.

5.2 Running the agent on the clone source

Before starting the clone operation ensure the Agent (CDS) is installed and running on the clonesource machine. To start enter the following in a command terminal:

/etc/cristie/cd/cds_cmv12

5.3 Running the clone from the clone target

To begin the clone sequence the target VM or physical machine should be booted from the pre-created machine specific ISO. After boot the following screen will appear. Press any key tocontinue, page up or down to scroll the window as required.

11Run a clone sequence


The target networking settings can be changed if required. If for example DHCP is not enabled onyour network Enter a static IP:

An example of a configured target machine is shown below:

12


The following screen indicates a successful network configuration:

Select Continue..:



Select Setup Source:

The next screen requires details of theCristie Token Manager (CTM) and the clone source machineto be supplied. The fields are:

Token Manager - the IP address of your CTM

Use Agent - default is set to enabled

Source IP - enter the IP address of the clone source machine

Use Encryption - default is not enabled. To enable select either up/down arrow orSPACEBAR, this will populate the field with 'X'

Username - usually root or user with root permissions

Password - if Encryption is disabled the password must be set to the text passWord. IfEncryption is enabled the password is the one used for the actual root login on the sourcemachine.

Throughput - enter a value to limit the bandwidth, say 100 (in KB/sec)

14


Clone Disk - usually enable, up/down arrow or SPACEBAR.

OK accepts the values entered. To leave this screen without making changed use the tab key tohighlight Cancel and then then select Enter

Note: To deselect the Use Agent field, tab to it and manually delete the [X] charactersleaving the field blank

In the example below:

Token Manager - the IP address of the CTM - 10.10.11.98

Use Agent - default is set to enabled

Source IP - enter the IP address of the clone source machine - 10.10.22.50

Use Encryption - not enabled

Username - root

Password - Encryption is disabled, so must set to the text passWord

Throughput - left blank using all available bandwidth

Clone Disk - enabled



After entering the source details select Scan Backup Location to test the connection betweensource and target.

A successful connection between source and target will produce an output like this.

16


If the connection test output indicates a problem then check the following:

the Agent (CDS) is running on the source, if not execute with /etc/cristie/cd/cds_cmv12

Ping the Source IP

If CDS is running telnet onto the source machine and find the PID for cds_cmv12 and k ill theprocess. Then restart as above.

Should the connection fail the source details must be re-entered. A successful connectionretains these values.

Prior to performing a recovery the source system configuration must be restored. First select Continue... and press Enter.



.

Then select Restore Configuration from Backup to retrieve the configuration:

The following dialogue is displayed after successfully restoring the configuration file. Select Enter toclose.

Note: The create configuration file must be regenerated after any hardware change

18


To begin the clone sequence select Start Recovery.

Follow the prompts and select OK in the following windows.



After a successful clone sequence you will be prompted to select Enter in the shell window. Onreturn to the user interface the following message is then displayed.

Should the clone fail a suitable message is displayed describing the failure. Prior to rebooting theclone you have the opportunity to view log files for the recovery. You may also mount a networkshare and copy the log files to this location for a permanent record. This is strongly recommendedfor problem diagnosis (you may be asked to submit these logs to Cristie support).

Finally select Exit and Reboot to boot the clone.

20


IBM AIX Supplement - Cristie Software · PDF fileIBM Tivoli Storage Manager ... Cristie...

Documents

Transcript of IBM AIX Supplement - Cristie Software · PDF fileIBM Tivoli Storage Manager ... Cristie...