Cristie CloneManager® 2.2.3 User Guide€¦ · 6 Cristie CloneManager® 2.2.3 User Guide 1 I ntr oduc i CloneManager® enables a live copy (a clone) of a running Microsoft Windows

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]

April 2015

User Guide

For Windows and Linux

Version 2.2.3

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), NBMR (Bare Machine Recovery for EMC NetWorker), SBMR (Bare MachineRecovery for CommVault Simpana), TBMR (Bare Machine Recovery for TSM), CBMR (Cristie Bare Machine Recovery),Recovery Console (RC) and CRISP (Cristie Recovery 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 6

................................................................................................................................... 61.1 Document conventions

2 Download the software 7

3 Product installation 8

................................................................................................................................... 83.1 Windows

......................................................................................................................................................... 8Install the CloneManager® components 3.1.1.................................................................................................................................................. 10Install the CM-Agent

.................................................................................................................................................. 12Install the CM-Console

.................................................................................................................................................. 14Install CTM

.................................................................................................................................................. 15Install CRISP and the CloneManager® Filesets

.................................................................................................................................................. 17Silent Install/Upgrade

......................................................................................................................................................... 19Uninstalling CloneManager® 3.1.2.................................................................................................................................................. 19Uninstall all components

.................................................................................................................................................. 20Uninstalling selected components

.................................................................................................................................................. 21Silent uninstall

......................................................................................................................................................... 22Modify the installed CloneManager® components 3.1.3

................................................................................................................................... 243.2 Linux

......................................................................................................................................................... 25Install the CM-Agent 3.2.1

......................................................................................................................................................... 26Configure the CM-Agent 3.2.2

......................................................................................................................................................... 27Run the CM-Agent 3.2.3

......................................................................................................................................................... 27Uninstall the CM-Agent 3.2.4

4 Licensing 29

................................................................................................................................... 294.1 Codes required for cloning

................................................................................................................................... 314.2 The Cristie Licensing Portal

......................................................................................................................................................... 32Setting up a Cristie Licensing Portal account 4.2.1

......................................................................................................................................................... 34Accessing contract and token codes 4.2.2.................................................................................................................................................. 34Contract activation code

.................................................................................................................................................. 35Token codes

................................................................................................................................... 354.3 The Cristie Token Manager

................................................................................................................................... 374.4 How license tokens are consumed

5 Create the bootable Liveenvironment 38

................................................................................................................................... 385.1 CloneManager 'Live' Environment for Windows

6 Preparing the bootable Liveenvironment for cloud targets 39

7 Run a clone sequence 40

................................................................................................................................... 407.1 Using the CM-Console

User Guide4


......................................................................................................................................................... 44Settings 7.1.1.................................................................................................................................................. 44vCenter/vSphere Hypervisor settings

.................................................................................................................................................. 46vCloud settings

.................................................................................................................................................. 47Hyper-V settings

.................................................................................................................................................. 49Azure settings

.................................................................................................................................................. 51AWS EC2 settings

.................................................................................................................................................. 52SoftLayer settings

.................................................................................................................................................. 54VIOS settings

.................................................................................................................................................. 56IP range settings

.................................................................................................................................................. 58Configure default clone settings

.................................................................................................................................................. 59Licensing settings

.................................................................................................................................................. 61Notif ication settings

.................................................................................................................................................. 62Agentless discovery settings

.................................................................................................................................................. 64Schedule settings

.................................................................................................................................................. 67Create batch

.................................................................................................................................................. 68Batch settings

......................................................................................................................................................... 69Help 7.1.2.................................................................................................................................................. 70Trace level

.................................................................................................................................................. 71Export Azure Certif icate

.................................................................................................................................................. 71Export Console Logs

.................................................................................................................................................. 72Enable advanced options

.................................................................................................................................................. 72User guide

.................................................................................................................................................. 73Log f ile

.................................................................................................................................................. 73About

......................................................................................................................................................... 74Event log 7.1.3

......................................................................................................................................................... 74Clone to a physical machine 7.1.4

......................................................................................................................................................... 79Clone to VMware vCenter™/vSphere 7.1.5

......................................................................................................................................................... 80Clone to VMware vCloud™ 7.1.6.................................................................................................................................................. 82IP allocation mode

......................................................................................................................................................... 83Clone to Microsoft Hyper-V™ 7.1.7

......................................................................................................................................................... 85Clone to Microsoft Azure™ 7.1.8

......................................................................................................................................................... 90Clone to Amazon Web Services™ (AWS) - Elastic Compute Cloud (EC2) 7.1.9

......................................................................................................................................................... 94Clone to IBM SoftLayer 7.1.10

......................................................................................................................................................... 99Clone Summary 7.1.11.................................................................................................................................................. 100Log details tab

.................................................................................................................................................. 100Source configuration tab

.................................................................................................................................................. 102Target configuration tab

.................................................................................................................................................. 103Disk configuration tab

........................................................................................................................................... 104Deselecting Window s dynamic disks

.................................................................................................................................................. 105Dissimilar hardw are tab

.................................................................................................................................................. 107Transport configuration tab

.................................................................................................................................................. 109Hypervisor configuration tab

.................................................................................................................................................. 110Schedule configuration tab

......................................................................................................................................................... 112Using CloneSync 7.1.12

8 Network setup 115

9 Clone target menu options 116

10 Agentless clones 118

11 Generating reports 121

5Contents


12 Cloning a batch 122

13 Tailor target VM configuration 123

14 Cristie Support 125

15 Appendices 126

................................................................................................................................... 12715.1 Windows Network Configuration

................................................................................................................................... 12815.2 Linux Network Configuration

16 Glossary 129

6

Cristie CloneManager® 2.2.3 User Guide

1 Introduction

CloneManager® enables a live copy (a clone) of a running Microsoft Windows or Linux machine tobe made to a supported virtual environment (Hypervisor), public cloud or to a new physical machine.

To accomplish this, an optional Agent is run on the source machine and a CloneManager 'Live'Environment for Linux/Windows/AIX is booted on the target machine. A third machine can thenbe used to host the CloneManager Console (CM-Console) to manage the complete cloningprocess for one or many machines concurrently. This arrangement allows an existing machine to bemigrated either directly to new hardware or virtualised to any of the supported Hypervisors or clouds.

The CM-Console allows all clone operations to be controlled via a simple drag & drop graphicalinterface. This action drives the cloning process by sending commands to the CloneManager 'Live'Environment for Linux/Windows/AIX running on the target system. The CloneManager 'Live'Environment for Linux/Windows/AIX then calls the CloneManager Agent (CM-Agent) running on thesource machine to create a snapshot of it's file systems and to create a machine configuration.

The CloneManager 'Live' Environment for Linux/Windows/AIX on the target machine then remotelymounts the snapshot, re-creates the file systems according to the configuration, tailors the cloneenvironment and transfers the files to the target machine.

Options are provided to allow the hostname, IP address and other system parameters to be tailoredfor the clone. If the target hardware requires additional drivers they may also be injected as part ofthe cloning process. These actions are performed before the clone is booted for the first time.

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® product. Refer to the Readme for installation requirements and late breakinginformation associated with this release.

At the time of release support for cloning IBM AIX systems to IBM VIOS target VMenvironments is not documented in this User Guide. However separate documentationwill be provided at a later date.

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

7Download the software


2 Download the software

At the moment CloneManager® is supplied upon request. Please contact [email protected] in thefirst instance. After successful evaluation you will then be provided with an FTP download link for theinstallation package.

mailto:[email protected]

8


3 Product installation

Windows

The Windows setup program allows all components of CloneManager® to be selectively installed orun-installed. This group of components is referred to here as the CloneManager® Suite.

It is possible to install individual components using dedicated setup programs. For example this maybe required at a later date to update individual suite components. However, in normal practice, it isrecommended to use the suite installer as discussed in the following sections.

The Windows installation suite consists of the following components:

CloneManager Agent (CM-Agent) - Optionally install on the clone source machine. Thisallows the CloneManager 'Live' Environment for Windows to communicate with the target andCM-Console machine. As an alternative CloneManager® also supports Agentless cloning.

CloneManager Console (CM-Console) - Install on any suitable host machine. Used tomanage and report progress of all clone operations for both Windows and Linux.

Cristie Token Manager (CTM) - Install on any suitable host machine but normally on thesame host as the CM-Console. Used to manage clone and sync tokens.

CRISP (Cristie Recovery ISO Producer) - Install on any suitable host machine. A tool usedto create the bootable WinPE4 or WinPE5 based CloneManager 'Live' Environment forWindows environment in conjunction with the CloneManager® fileset below.

CRISP WinPE4 or WinPE5 Fileset for the CloneManager 'Live' Environment forWindows. Install on the same machine as CRISP above. Used in conjunction with CRISP tocreate the CloneManager 'Live' Environment for Windows ISO. Boot this ISO on Windowsclone targets. Unfortunately Cristie Software Ltd. is unable to provide the CloneManager 'Live'Environment for Windows ISO directly to Customers because of Microsoft WinPE4 or WinPE5Licensing restrictions.

Linux

The Linux installation package provides the following additional components:

CloneManager Agent (CM-Agent) - provided as an rpm package to be installed on the clonesource machine. This allows the CloneManager 'Live' Environment for Linux to communicatewith the source and CM-Console machines.

Clonemanager-2.2.2.linux.xxx.iso (where xxx denotes the bit level). This is pre-built byCristie Software Ltd. and should be booted on Linux clone target machines.

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

3.1 Windows

This section describes how to install CloneManager® product components on Windows. Refer tothe Readme document to see the versions of Windows supported in this release.

3.1.1 Install the CloneManager® components

To install CloneManager® components run the suite setup program SetupCloneManagerSuite223.exe from the command line or click on the setup program from within Windows Explorer. This willthen display the opening dialogue of the installation sequence.

9Product installation


Note: The CloneManager® installation requires that the User login account running theinstallation has local Administrator privilege.

Click on Show Quick Start Guide to display a guide describing installation and basic product usage.Click Show Readme to display product release notes and installation requirements specific to thisrelease.

Click on Install CloneManager Suite to commence product installation. The License Agreement willthen be displayed.

If you are happy to accept the terms and conditions in the license agreement, select I accept theterms in the license agreement and then Next >. You will then be prompted to choose whichmajor component of the suite to install - the CM-Agent, CRISP and the CloneManager® Fileset orthe CM-Console.

10


Note: You may also print the license if you wish and have a suitable printer available.

Each install option is now discussed in more detail.

3.1.1.1 Install the CM-Agent

Selecting Install Agent results in the following dialogue being displayed:

Enter the root folder for the CM-Agent installation. Use the Change... button to create or choose adifferent installation folder.

Note: Cristie Software Ltd. strongly recommends the default folder location is used.

Note: The CM-Agent can only be installed on the same partition as the Windows OSitself.



The CDS service account credentials are only required if the standard service account (LocalSystem) is not suitable. For example you may wish to run the CDS service under a domainaccount. In this case specify the username in the form DOMAIN\Username with the appropriatepassword. The account selected will be automatically given Logon as a Service right during theinstallation of CDS.

Finally click Install to begin the installation of the CM-Agent components.

Successful completion is confirmed by the following dialogue. Select Finish to exit.

Note: CM-Agent requires certain Windows firewall ports to be opened for correctoperation. These will be opened automatically at the end of installation process.

12


3.1.1.2 Install the CM-Console

Selecting Install Console results in the following dialogue being displayed:

Enter the root folder for the CM-Console installation. Use the Change... button to create or choose adifferent installation folder.


Deselect Create a desktop shortcut to start the Console if a desktop shortcut is not required.

By default the Cristie Token Manager will be installed along with the CM-Console. If you want toinstall the Cristie Token Manager separately to a different host deselect the Install the CristieToken Manager with the Console field.

Finally click Install to begin the installation of the CM-Console components.



Successful completion is confirmed by the following dialogue. Tick Start the CM-Console on exittick-box if you wish to run the CloneManager Console immediately after closing the installationdialogue.

Finally, select Finish to exit.

Note: CM-Console requires certain Windows firewall ports to be opened for correctoperation. These will be opened automatically at the end of installation process.

Note: Full product documentation is installed along with the CM-Console

14


3.1.1.3 Install CTM

Selecting Install Token Manager results in the following dialogue being displayed:

Enter the root folder for the CTM installation. Use the Change... button to create or choose a differentinstallation folder.


The CTM service account credentials are only required if the standard service account (LocalSystem) is not suitable. For example you may wish to run the CTM service under a domainaccount. In this case specify the username in the form DOMAIN\Username with the appropriatepassword. The account selected will be automatically given Logon as a Service right during theinstallation of CTM.

Finally click Install to begin the installation of the CTM components.




Note: CTM requires certain Windows firewall ports to be opened for correct operation.These will be opened automatically at the end of installation process.

3.1.1.4 Install CRISP and the CloneManager® Filesets

Selecting Install CRISP and the Filesets results in the following dialogue being displayed:

Enter the root folder for the CM-Agent and fileset installation. Use the Change... button to create orchoose a different installation folder. CRISP is a 64-bit application and will only install to a 64-bithost OS.


16


Finally click Install to begin the installation of the CRISP and the WinPE4/WinPE5 Filesetcomponents.


Note: CRISP requires the either the Microsoft Windows Assessment and DeploymentKit (WADK) version 8 for Win8/Win2012 or Microsoft Windows Assessment andDeployment Kit (WADK) version 8.1 for Win8.1/Win2012R2 to be installed before it canbe used to create the CloneManager 'Live' Environment for Windows ISO.



3.1.1.5 Silent Install/Upgrade

Note: This is for advanced users only.

If you need to install CloneManager® components repeatedly with the same options, you can installit from the command line without operator interaction.

There are 2 approaches to this. Either run the suite installer silently (the recommended method) orextract the stand-alone component installers and run those individually and silently.

Running the Suite Installer Silently

This is the recommended method because it ensures the components are installed in the correctsequence with the correct options.The CloneManager® suite contains 5 components:

Component name Component feature name Description

CM-Agent CloneManagerAgent22 Clone agent components.

Cristie Token Manager CristieTokenManager22 Provides license and token support.

CM-Console CloneManagerConsole22 Used to manage and report progress ofall clone operations for both Windowsand Linux.

CRISP CRISP723 Used in conjunction with the CRISP PE4or PE5 Fileset for CloneManager 2.2.3 tocreate the CloneManager 'Live'Environment for Windows ISO.

CRISP PE4 or PE5 Fileset forCloneManager 2.2.3

CloneManagerFileset22 Used in conjunction with CRISP to createthe CloneManager 'Live' Environment forWindows ISO.

The following example illustrates the syntax for running the suite setup silently to install both theCM-Console and Cristie Token Manager on the same host system:

C:\SetupCloneManagerSuite223.exe /silent /ISFeatureInstall:CristieTokenManager22,CloneManagerConsole22 /SuiteInstallDir="C:\Program Files\Cristie" /debuglog"C:\setup.log"

This installs all the components to the root folder Program Files\Cristie and creates an installationlog in the specified folder. Obviously you may change the installation folder path as required.

Note: All the command-line switches must be specified (except for the /debuglog switchwhich is optional) or the silent install will fail.

To install other components change ISFeatureInstall to one or more of the feature names shown inthe table. Always separate multiple features with commas; space characters between the namesare not allowed.

The CRISP and CRISP PE4 or PE5 Fileset for CloneManager 2.2.3 components must always beinstalled together. Use this variation of the above command line in this case:

C:\SetupCloneManagerSuite223.exe /silent /ISFeatureInstall:CRISP723,CloneManagerFileset22 /SuiteInstallDir="C:\Program Files\Cristie" /CRISPInstallDir="C:\Program Files\Cristie"/debuglog"C:\setup.log"

If any earlier versions of the components are detected during the silent install process they will beupgraded silently without prompt.

18


Running the Component Installers Silently

You should only choose this method of installing CloneManager® features when running the suiteinstaller silently is, for example, not compatible with any deployment software in use.

There are 6 stand-alone features that must be first extracted and then installed in the correctsequence. These are:

the CM-Agent

the Cristie Deployment Service (CDS)

the Cristie Token Manager

the CM-Console

the CRISP

the CRISP PE4 or PE5 Fileset for CloneManager 2.2.3

This example shows how to install the CloneManager Agent components. To prepare for this eachcomponent's stand-alone setup program SetupCMPlugin223-x86.exe and SetupCDS4-x86.exe mustbe first extracted from the suite installer. Only the relevant bit version for your operating system willbe extracted. Note the following discussion shows a 32-bit example and the GUIDs shown are onlyexamples. The 64-bit equivalent will have been extracted if running on x64 systems. If you are notconfident in doing this please consult Cristie Support who will be able to supply the files directly.

After copying SetupCloneManagerSuite223.exe to a suitable location (C:\ in this example) extractall the setup files from the suite installer by running this command (on the command line or fromStart/Run):

C:\SetupCloneManagerSuite223.exe /silent /stage_only ISRootStagePath="c:\temp"

where c:\temp is the folder to where you want to extract the setup programs. This will place all thesetups available into separate folders under c:\temp in their own different GUID folder. In theexample shown here look for the folders containing the setup files SetupCMPlugin223-x86.exe andSetupCDS4-x86.exe.

Now run each of the silent setups in turn on the command line, for example:

C:\temp\{A279EC27-E6C6-47AF-ACBB-7C6662CC03CB}\SetupCMPlugin223-x86.exe /s /v"/qn /l*v c:\setup.log ALLUSERS=1"

followed by:

C:\temp\<%CP_CDS_SUITE_GUID%>\SetupCDS4-x86.exe /s /v"/qn /l*v c:\setup.logALLUSERS=1"

This example installs all the CM-Agent components and creates an install log in c:\setup.log.

The command will select all of the default values that have been specified for the installation. Youmay change some of the default values by adding parameters to the command line. For example,

C:\temp\{A279EC27-E6C6-47AF-ACBB-7C6662CC03CB}\SetupCMPlugin223-x86.exe /s /v"/qnADDLOCAL=CloneManager® INSTALLDIR="%systemdrive%\Cristie\CloneManager®"

The ADDLOCAL and INSTALLDIR properties in the above example are overridden from their defaultvalues. Note that the ADDLOCAL setting in the above example installs the main CloneManager®program only. It does not install any optional components.



Please refer to the Microsoft Windows Installer (MSIEXEC) Property Reference for a full listingof the properties and switches that can be applied to the stand-alone installation.

3.1.2 Uninstalling CloneManager®

There are two options available for uninstalling CloneManager®. You can choose to either uninstallall or selected components.

3.1.2.1 Uninstall all components

To remove all installed components select CloneManager® Suite from the Windows Control Panel -> Programs and Features option.

Then select Uninstall as shown.

Select Remove and all installed components will be uninstalled.

20


Successful uninstall is signified with this dialogue.

Press Finish to exit.

Note: On Windows 2003 use the Add/Remove Program option in the Control Panel toachieve the same effect.

3.1.2.2 Uninstalling selected components

To remove a selected component only choose the required item from the list of installed programs inthe Windows Control Panel -> Programs and Features option. In the following example the CM-Console is going to be uninstalled in this example, but all other components will be left installed.



Click Uninstall and a confirmation message will be displayed.

Select Yes to begin the uninstall process.

If you want to install the same or a different component use the main suite program as discussed inthe previous section.

Note: On Windows 2003 use the Add/Remove Program option in the Control Panel toachieve the same effect.

3.1.2.3 Silent uninstall

Note: This is for advanced users only.

If you need to uninstall CloneManager® repeatedly with the same options, you can uninstall it fromthe command line without operator interaction.

As for silent install there are 2 approaches to this. Either run the suite installer silently (therecommended method) or extract the stand-alone component installers and run those individuallyand silently.

Running the Suite Uninstaller Silently

22


This is the recommended method because it ensures the components are uninstalled in the correctsequence and with the correct options. The syntax for running the suite setup silently in uninstallmode is:

C:\SetupCloneManagerSuite223.exe /silent /remove /debuglog"C:\uninstall.log"

This uninstalls all the installed CloneManager® components and creates an uninstall log in thespecified folder. The installation must have been previously performed by the suite.

Note: All the command-line switches must be specified (except for the /debuglog switchwhich is optional) or the silent uninstall will fail.

Running the Component Uninstallers Silently

To silently uninstall an existing CloneManager Agent installation from the command line (assumingthe component setup files have already been extracted - see section Silent Install/Upgrade) and havebeen not been installed from the suite. Enter the following commands:

C:\temp\{A279EC27-E6C6-47AF-ACBB-7C6662CC03CB}\SetupCMPlugin223-x86.exe /s /v"/qn /l*v C:\uninstall.log REMOVE=ALL"

followed by:

C:\temp\{A279EC27-E6C6-47AF-ACBB-7C6662CC03CB}\SetupCDS4-x86.exe /s /v"/qn /l*v C:\uninstall.log REMOVE=ALL"

This example uninstalls all the CM-Agent components and creates an uninstall log in the specifiedfolder.

3.1.3 Modify the installed CloneManager® components

To remove all installed components select CloneManager® from the Windows Control Panel ->Programs and Features option.

Then select Change as shown. This will then display the setup maintenance menu.

Note: The CloneManager® installation requires that the User login account running theinstallation has local Administrator privilege.



Select Modify to display the list of installed components. The ticked items represent the currentlyinstalled components. In this example the CM-Agent is already installed.

Tick the new items that you wish to install (CTM and the CM-Console in this example).

24


Now select Install.

This will begin the installation of the new components.

3.2 Linux

This section describes how to install the CloneManager® product component to provide Linux clonesupport.

Linux clone support differs from Windows in two ways. Firstly it requires a different CM-Agentprogram and secondly there is no need to manually create a CloneManager 'Live' Environment forLinux ISO. Unlike the Windows equivalent this is provided pre-built by Cristie Software Ltd..

The Windows version of CM-Console can be used to manage Windows and Linux clone operations.It is possible to run CM-Console on a Linux host since it is Java based, but this is not currently



supported.

Note: The Linux install ISO provides both the Agent installation files and can also bebooted as the CloneManager 'Live' Environment for Linux.

3.2.1 Install the CM-Agent

The Linux version of the CM-Agent is installed as follows.

1. On your Linux source machine host, mount the Linux CloneManager® release ISO. Theexample below shows a 64-bit SLES 11 SP3 64-bit installation. Use the 32-bit version of theISO if your Linux OS is 32-bit.

2. An RPM and install script installer for the Linux CM-Agent can be found in /media/CLONEMANAGER/linux/install/main called clonemanager-2.2.2.linux.x86_64.tar.gz orclonemanager-2.2.2.x86_64.rpm. Run the RPM installer directly or decompress, unzip andrun the install script file in (say) a Terminal window. Ensure you are running this as root.

An RPM installation follows this sequence:

Click Install to start the installation. Click Install anyway if an Unable to verifyclonemanager package warning is displayed. The package should install with no errors, butpossibly with a final warning regarding that a trial licence for the CM-Agent has been installed.

26


To install via the supplied script extract the gz package contents to /tmp/clonemanager(say). Then simply run ./install. A script install follows this sequence:

3. Please apply your full licence if you have one.

Note: CM-Agent requires certain Linux firewall ports to be opened for correct operation.Please refer to the next section.

3.2.2 Configure the CM-Agent

For correct operation with the CM-Console some limited configuration must be performed on theLinux CM-Agent (i.e. clone source) machine.

RHEL/Centos

1. Open a terminal Window and edit the iptables file to open port 4001 for TCP/UDP.

2. Add these lines to /etc/sysconfig/iptables:

-A RH-Firewall-1-INPUT –m state --state NEW –m udp –p udp --dport 4001 –jACCEPT



-A RH-Firewall-1-INPUT –m state --state NEW –m tcp –p tcp --dport 4001 –jACCEPT

3. Then run service iptables restart to reset the firewall. Check the new settings with thecommand iptables -L -n.

4. Ensure rsync and ssh are available and configured correctly. Ensure that the ssh port (22) isopen if a firewall is in use.

SUSE/SE Linux

1. Open a terminal Window and edit the SuSEfirewall2 file to open port 4001 for TCP/UDP.

2. Add these lines to /etc/sysconfig/SuSEfirewall2:

FW_SERVICES_EXT_TCP="4001"FW_SERVICES_EXT_UDP="4001"

3. Then run /etc/init.d/SuSEfirewall2_init restart. Sometimes a machine re-boot may berequired as well.

4. Ensure rsync and ssh are available and configured correctly. Ensure that the ssh port (22) isopen if a firewall is in use.

5. With SuSE 11 you may also need to configure ssh. Set PasswordAuthentication andPermitRootLogin to yes in /etc/ssh/sshd_config and then run /etc/init.d/sshd restart.

Note: Ensure the configuration is done before running the CM-Agent.

3.2.3 Run the CM-Agent

To run the CM-Agent on the Clone source machine simply run CDS (or CDS& to run in background) ina terminal window.

If you require the CM-Agent to be available permanently you should consider installing to a non-temporary folder and add the start of the CM-Agent process (CDS) to a suitable boot script.

1. Run a clone target machine (using a Linux template). Boot the CloneManager 'Live'Environment for Linux environment from the release ISO. When active make sure network ingis running and it has an IP address.

2. Make sure you are using CloneManager® 2.2.2 or later.

3.2.4 Uninstall the CM-Agent

To uninstall the CM-Agent package if required after the clone is complete enter either:

rpm -e clonemanager-2.2-2

Or if the install files are still available enter:

./install -u

For example:

28


29Licensing


4 Licensing

This section describes the licensing model used to support CloneManager®. CloneManager® usestoken-based licensing. A token represents a license from Cristie to perform a clone operation asdescribed in this document. Tokens are normally pre-paid for by the customer. No free tokens aresupplied with the product.

The Cristie Token Manager provides the tokens for clones as a web service. By default, the CristieToken Manager runs from within the CM-Console, but run stand-alone on a separate host if required.

The sequence of events required to setup licensing within CloneManager® is summarised in thistable:

Download CloneManager® from the Cristie FTP site. Customer action

Create 'Live' clone environment using CRISP and the fileset(Windows)

Customer action

Install the CM-Console (note the license signature of thismachine) and optionally install the CM-Agent on themachines to be cloned. Note it is possible to run a cloningoperation without installing an Agent.

Note: installing the CM-Console optionally installs the CristieToken Manager on the same host. This is the recommendedconfiguration when only one CM-Console is being used.

Customer action

Contact Cristie to register the Cristie Token Manager andpurchase clone token codes. You will need: your customer Contract ID the license host system signature number of tokens and type (clone or sync) required payment

Customer action

Cristie contacts customer with Contract Code codes. Cristie action

Customer creates a Cristie Licensing Portal account.Contract Activation and Token codes can then be obtainedfrom the Cristie Licensing Portal for the Contract Codesupplied above.

Customer action

Use the CM-Console to add the 3 (4 if both clone and synctokens are purchased) license codes to the Cristie TokenManager.

Customer action

You are now ready to start a licensed clone operation.

4.1 Codes required for cloning

An installation of CloneManager® requires activation and the purchase of tokens before any cloningoperations can be performed.

In order to use CloneManager® to clone machines the following license codes are required:

1. Your 4-digit Contract ID (also known as the Agreement Number).

30


2. The License signature of the machine running Cristie Token Manager. Use the Cristie TokenManager menu option Edit -> Licensing Settings -> File -> Generate Signature to do this.

3. Relevant payment, dependant on the number of tokens and token type required.

Note: If the Cristie Token Manager is run remotely then the hostname provided to CristieSoftware Ltd. Support should be the hostname of the remote machine. If the CristieToken Manager is run within the CM-Console the hostname of the machine runningCristie Token Manager is the same as that running CM-Console and this is the hostnameCristie Software Ltd. Support needs to generate your codes.

The following information is returned to you by Cristie Software Ltd.:

1. A Contract Code (to enter this select Edit > Licensing Settings > Contract > Assign Contract).

2. An Activation Code (to enter this select Edit > Licensing Settings > Contract > ActivateContract).

3. A Token Code (to enter this select Edit > Licensing Settings > Tokens > Add tokens). Thecode identifies whether the token is either Clone or Sync type.

These codes have the following meanings:

Contract Code - A unique code provided to identify you as a customer and your purchase of tokens.You make buy further tokens using the code at a later date.

Activation Code - A code that activates the Cristie Token Manager. This code sets the Expiry Datefor your contract and your License Type.

Token Code - A code which allows CloneManager® to run a limited number of clone operations.Clone operations are of 2 types: Clone or Sync. Without a valid token it will not be possible to runany clone operations. The Token Code is provided by Cristie Software Ltd. Support and is set toreflect the tokens and token type you have purchased from Cristie Software Ltd.. You can purchasemore Token Codes for your Contract as you require.

Prior to obtaining and entering these codes, when accessing Cristie Token Manager (via Edit >License Settings) the following is displayed in Cristie Token Manager:

Note this example assumes a local CTM is in use, but licensing a remote CTM followsthe same steps.

31Licensing


Entering the Contract code (from Contract -> Assign Contract on the menu) sets the Licensed?field to Yes and License Type to Trial:

Licensed? = YesLicense Type: = TrialContract ID: = Your Contract IDCurrent Token/Sync Count: = 0

Entering the Activation Code sets the License Type to Full, Expiry Date to the full duration of yourContract:

Licensed? = YesLicense Type: = FullContract ID: = Your Contract IDCurrent Token/Sync Count: = 0

Entering a Token Code sets the Current Token Code and type for your contract:

Licensed? = YesLicense Type: = FullContract ID: = Your Contract IDCurrent Clone Token Count: A number of clone tokens (depends on your requirement and payment).Current Sync Token Count: A number of sync tokens (depends on your requirement and payment).

For example, after entering a valid Contract Code, Activation Code and Token Codes (some Clone,some Sync) when selecting Settings > License Settings the following is seen in the Cristie TokenManager settings:

The contract activation and token codes can be obtained from the web-based Cristie LicensingPortal. Refer to section The Cristie Licensing Portal for a full discussion of how to accomplish this.

4.2 The Cristie Licensing Portal

The Cristie Licensing Portal is a web application that will allow Customers to manage all theirproduct licensing requirements including access to pre-purchased CloneManager® full andCloneSync clone tokens.

It is located at https://portal.cristie.com/login.

32


4.2.1 Setting up a Cristie Licensing Portal account

To setup a new account on the Cristie Licensing Portal follow the following steps. To do this you willneed your 4-digit Contract ID and contract setup password. These will be provided by email fromCristie Software Ltd. when you purchase a product license.

Note: Your Contract ID may have been supplied to you as your contract AgreementNumber. In that case please use your Agreement number in place of the Contract IDthroughout.

1. On a machine that has Internet access run a suitable browser such as Microsoft Internet Explorerand navigate to the Cristie Licensing Portal web page at https://portal.cristie.com/login.

Select Register to create a new account. Enter your new account details (note this is anexample):

33Licensing


Then click Create. If successful the following is shown.

At this point you may now log in to the Cristie Licensing Portal using the E-mail ID and passwordsetup in the previous step.

34


4.2.2 Accessing contract and token codes

After creating a Cristie Licensing Portal account you can now access your Contract activation andtoken codes.

First login using the account setup earlier.

4.2.2.1 Contract activation code

Select Activate License from the menu options shown in the left column.

Select the correct contract and enter the IP address, hostname and signature of your CM-Consolehost system. Add a suitable comment if required.

Clicking Activate License button will display the Contract activation code for the CM-Console.

35Licensing


4.2.2.2 Token codes

Select Request Tokens from the menu options shown in the left column.

Select the correct contract and then enter the IP address, hostname, number of tokens requiredand signature of your CM-Console host system.

Clicking Request Tokens button will display the token code for the CM-Console.

4.3 The Cristie Token Manager

The Cristie Token Manager keeps track of your product activation codes and loaded clone and synctokens. It runs as a service and is normally installed along with the CloneManager Console bydefault on the same host machine. The CM-Console in fact provides the User interface to CTM.

In an environment where perhaps multiple CM-Consoles are going to be run you may prefer to installthe CTM on a dedicated host visible by all.

The default install of Cristie Token Manager can be disabled by unticking the Install the CristieToken Manager (CTM) with the Console tick box (see below).

36


If you do this the CTM must then be installed separately on a different host. In this case the CM-Console must be configured use the remote CTM. To do this select Edit > Licensing Settings >File > New Token Manager:

Enter the IP for the New Token Manager in the dialogue that appears:

Enter the IP address of the remote Cristie Token Manager and click OK.

37Licensing


If you decide later that you want to revert to using a CTM on the same host as the CM-Console youcan re-run the suite installation in Modify mode to achieve this. Once a local CTM is installed youwill then need to configure the CM-Console to use the new CTM (now residing on localhost). Select Edit > Licensing Settings > File > New Token Manager and enter the IP address (127.0.0.1) oflocalhost.

If a remote CTM is used then the CM-Console effectively becomes a pass-through for license control.So all new tokens are stored in the remote CTM host, but managed via the local CM-Console licenseinterface.

Note: The license/token signature is derived from the local CM-Console host unless aremote CTM is being used. In that case the signature is derived from the CTM hostinstead.

4.4 How license tokens are consumed

As soon as the clone operation starts the current available Clone Token Count is decremented.

If a clone operation fails for any reason the current available Clone Token Count remainsdecremented, but the token for the clone is still available for retries on the same Cristie TokenManager for a further 7 days. After 7 days have elapsed the token expires and any clone retryattempt is disallowed. In this case a new token will be consumed if available.

If a clone operation is aborted the current available Clone Token Count is not decremented and thetoken is immediately made available for reuse.

A clone token is only totally consumed once a machine has been cloned and successfully rebooted(subject to the 7 day expiry period for failed clones described above). Therefore you may clone asmany times as you wish from the same source and target pairing without consuming a new token aslong as you don't reboot the target.

Sync token consumption is different - there is no 7-day grace period for retries during a failure orabort sync sequence. They are immediately consumed.

38


5 Create the bootable Live environment

When running clones to any of the supported Hypervisors or clouds, a 'Live' environment is alwaysfirst booted on the new VM target, i.e. the CloneManager 'Live' Environment for Linux/Windows. Thisallows the target machine to be seen by the CM-Console and synchronise with the clone sourcemachine for file transfer.

For Windows clones it is the responsibility of the User to create the bootable ISO using the toolsprovided as part of the installation package. For Windows, both WinPE4 and WinPE5 basedversions are available. Use the WinPE4 version to support the cloning of all versions of Windows upto and including Windows 2012. Use the WinPE5 version for Windows 2012R2 or later.

The CloneManager 'Live' Environment for Linux is different in that it is supplied pre-built as a dual-purpose distribution ISO package. This ISO can be booted directly as the Live environment ormounted on a clone source to allow the installation RPM to be extracted or run directly. Nothingfurther is required in this case.

5.1 CloneManager 'Live' Environment for Windows

First install the ISO build components as described in Install CRISP and the CloneManager® filesets. This can be performed on any suitable host machine and does not need to be the machine to becloned.

The Cristie Recovery ISO Producer (CRISP) User Guide is a separate document and is installed onthe CRISP host machine. Please consult this document for a full discussion of how the ISO iscreated.

The generated ISO should be uploaded to the Hypervisor ISO datastore to ensure it is available for aWindows clone. If cloning direct to a physical machine target then boot this ISO on the target.

This is a one-time process and only needs to be performed once for all Windows clones.

39Preparing the bootable Live environment for cloud targets


6 Preparing the bootable Live environment for cloudtargets

Azure and AWS EC2

No action is required by the User to upload any of the Live boot ISOs to these cloud environments.Whenever a new release of CloneManager® is made the ISOs will be uploaded by Cristie SoftwareLtd. to all the cloud Datacenters.

The User simply needs to select the required Live environment ISO when configuring the cloneoperation.

SoftLayer

For SoftLayer support the User is required to manually upload the required Live ISOs to objectstorage on the required Datacenter. These are the steps:

1. Create the CloneManager 'Live' Environment for Windows ISO (refer to the topic Create thebootable Live environment for Windows). The CloneManager 'Live' Environment for Linux isdifferent in that it is supplied pre-built. Nothing needs to be created in this case.

2. Download the free CloudBerry Explorer for OpenStack Storage from this link : http://www.cloudberrylab.com/download-thanks.aspx?prod=cbosfree

3. Use this article to configure CloudBerry Explorer to connect to your Softlayer ObjectStorage: http://www.cloudberrylab.com/blog/how-to-sign-up-and-start-using-softlayer-object-storage-with-cloudberry-backup/

4. Use CloudBerry to upload the CloneManager 'Live' Environment for Windows and/or theCloneManager 'Live' Environment for Linux ISO file(s) to your Softlayer Object Storage.

5. Once the required Live environment ISOs are uploaded; run the Softlayer ManagementConsole and go to Devices - Manage - Images and import the ISOs from your ObjectStorage.

Once the upload is complete the User simply needs to select the required Live environment ISOwhen configuring the SoftLayer clone operation.

40


7 Run a clone sequence

Normally the preferred method of managing a clone sequence is to use the CM-Console. However,there is an alternative method that does not use the CM-Console just the CloneManager 'Live'Environment for Windows or CloneManager 'Live' Environment for Linux ISO. In the latter case theclone target is booted into the ISO and the clone operation controlled manually from the bootedinterface. However, the latter method is not recommended for general use.

A clone sequence may be run using any one of the following as source or target:

a physical machine

a virtual machine on a Microsoft Azure™ cloud

a virtual machine on a VMware vCenter™ server

a virtual machine on a VMware vSphere™ server

a virtual machine on a VMware vCloud™ cloud

a virtual machine on a Microsoft Hyper-V™ server

a virtual machine on a Amazon Web Services™ (AWS) - Elastic Compute Cloud (EC2) cloud

a virtual machine on a IBM SoftLayer cloud

a virtual machine running on VMware Workstation system

7.1 Using the CM-Console

The CM-Console is the primary interface used to remotely control the complete cloning processacross multiple machines and virtual environments. The console can be used to control bothWindows and Linux clone operations.

It can be used to perform the following:

Automatic search for clone Source and Target machines.

Management of live clone operations (create, schedule, batch, abort or CloneSync for example)

Configuration of target hypervisor environments, IP Range, Clone settings, Tailoring andgenerate migration reports.

Initial Preparation

Before attempting a clone the following initial preparation steps must be carried out. Note that, ingeneral, this only needs to be done once.

1. To enable automatic detection of the system to be cloned (i.e. the source system) run theCloneManager® setup to install the agent . This process installs a service called CristieDeployment Service (CDS) and a further small plug-in providing the specific cloningfunctionality. This installation only needs to be performed once to allow the source system tobe cloned multiple times.

If automatic detection of the source system to be cloned is not required then the cloningoperation can be performed in an agent-less manner (currently restricted to Windows only).This feature negates the requirement to manually install any programs on the source system.

41Run a clone sequence


Either option above should be performed on all Windows or Linux source machines required tobe cloned.

2. Install the Cristie Recovery ISO Producer (CRISP) tool and the CRISP PE4 or PE5 Filesetfor CloneManager 2.2.3 together on a suitable host system. Run CRISP to create theCloneManager 'Live' Environment for Windows WinPE4 or WinPE5 based bootable cloningenvironment. This only needs to be done once. Refer to the CRISP User Guide for details onhow to do this. This document is installed along with the CRISP tool. This only needs to bedone to create the Windows version of the ISO. The Linux version is provided pre-built.

3. If cloning to a physical target machine, boot the WinPE4 or WinPE5 based CloneManager'Live' Environment for Windows on a Windows clone machine target. Boot the CloneManager'Live' Environment for Linux on a Linux clone target. If cloning to a Hypervisor copy the ISO tothe required ISO datastore.

4. Install the CloneManager Console (CM-Console) onto a suitable host system. Run CM-Consolefrom the desktop shortcut if present or from the Start menu\All Programs\Cristie foldershortcut as an alternative.

Use the CM-Console Edit -> Default Settings menu option to create a default path for storingclone logs. Similarly use the Edit -> Licensing Settings menu option to configure a CTM andadd licenses and clone tokens. Refer to Default clone settings and Licensing settingsrespectively for more information.

5. Use the File -> New Hypevisor menu option to detect and configure your Hypervisors. Oncethis is detected an icon for the Hypervisor will appear in Target Systems. Right-click on theicon and configure the default settings. Refer to vCenter settings, vCloud settings, Hyper-Vsettings and Azure settings for further details of this process.

Typical Clone Sequence

A typical CloneManager® cloning sequence, once the above preparation has been performed,comprises the following steps.

1. Use CM-Console to drag & drop a selected source machine onto a selected target (or targets).

2. Optionally boot the cloned system at the end of the clone operation.

3. Optionally sync a clone after the initial clone sequence.

Once installed the console will detect any machines on the network currently running the CM-Agent(i.e. the source machine) and those booted into the cloning environment (i.e. the target machine).An example is shown below.

42


The console provides the ability to drag & drop a source machine onto a target machine to initiate acloning operation. Simply click on a source machine icon and drag it over the target machine andrelease the mouse. The same technique is used whether the target is a physical machine, orresident in a vCenter, vSphere, vCloud, Hyper-V or Azure Hypervisor environment.

If the target machine is not currently in use the CM-Console will prompt for the target properties (e.g.hostname, IP address, dissimilar driver path etc.) and start the cloning process from source to targetmachine.

The console will also show the progress and overall success of active cloning operations. The sourceand target icons vary according to the current state of machine as summarised below.



CloneManager® Icons

- Machine is online - (ready to clone)

- Machine is disconnected, a re-connection attempt is in progress

- Machine is offline. Such systems will remain on display until a manualrefresh is run

- Machine is busy

- vCenter/vSphere server

- vCloud cloud

- Hyper-V server

- Azure cloud

- AWS EC2 cloud

- SoftLayer cloud

- VIOS server

After CM-Console has performed its initial search, it is possible to start cloning your systems.Instructions on achieving this are discussed in the next following sections. Further options relating tothe search functionality of CM-Console are documented below.

Once initiated, CM-Console will continue its search, (as indicated by the search icon in the bottomright-hand corner) updating the display every eight seconds.

When the icon above is shown rotating it indicates that network auto-discovery is active. The rotationwill cease when auto-discovery is disabled. This is controlled from the IP Range Configurationdialogue.

If required, it is possible for the user to perform a manual update of the displayed information, byselecting File > Refresh from the menu bar. Alternatively press F5 on the keyboard to have thesame effect.

44


A more detailed description of the CM-Console including how clones can be targeted to VMwarevCenter™/vSphere, VMware vCloud™, Hyper-V, Azure, AWS EC2 and SoftLayer is discussedin the following sections.

7.1.1 Settings

There are various default settings under the File and Edit main menu options that must beconfigured before you can commence practical clone operations.

7.1.1.1 vCenter/vSphere Hypervisor settings

Note: The following discussion assumes the reader is conversant with VMwarevCenter™, vSphere terminology and operation. It is also assumed that theCloneManager 'Live' Environment for Windows and CloneManager 'Live' Environmentfor Linux ISOs have already been uploaded to the relevant ISO datastores.

To configure CM-Console so that it has the functionality to create clones on an VMware vCenter™/vSphere target environments, first select File -> New Hypervisor .. from the menu bar:

Then select vSphere from the resulting dialogue drop-down Hypervisor Type box:

Enter the IP address of the vSphere environment you wish to utilise, along with the credentialsrequired to access the vSphere IP and click Search to begin the discovery process. In the exampleabove the IP address of a vSphere host is specified, but a vCenter host could be used instead.

At this point you may Close the dialogue if required. The discovery process will continueasynchronously in the background. When discovery completes successfully a vSphere icon will bedisplayed in the CM-Console target region.



The user must then further configure CloneManager® with the required vSphere environment by right-clicking on the vSphere icon and selecting Settings.

This displays the vSphere Settings dialogue:

Use the drop-down selection boxes to configure the settings. In particular make sure you select thecorrect boot ISO for the VM - CloneManager2.2.3-pe4.iso or CloneManager2.2.3-pe5.iso in thisexample.

Server Selected vSphere server

Datacenter Select the DataCenter you require.

Host Select the hostname of the Host you wish to use.

ISO Datastore Used to specify which Datastore contains your ISO's.

VM Datastore Allows you to select the Datastore you require your VM's to be created in.

ISO Specify the CloneManager 'Live' Environment for Windows or CloneManager'Live' Environment for Linux ISO to be used to during the cloning stage.

Network Specify a Network that will enable connectivity between CloneManager® andthe source machine during the clone.

Make sure you select OK and the vSphere settings will be saved.

You may repeat this procedure to create as many vCenter or vSphere objects as required.

Note: Click Refresh at any time to re-run the vCenter or vSphere discovery process.

Note: It is possible to delete a vCenter or vSphere object by right-clicking on the icon and

selecting Remove Target Hypervisor.

46


7.1.1.2 vCloud settings

Note: The following discussion assumes the reader is conversant with VMwarevCloud™ terminology and operation. It is also assumed that the CloneManager 'Live'Environment for Windows and CloneManager 'Live' Environment for Linux ISOs areavailable in the vCloud ISO Catalog.

To configure CM-Console so that it has the functionality to create clones on vCloud targetenvironments, first select File -> New Hypervisor .. from the menu bar:

Then select vCloud from the resulting dialogue drop-down Hypervisor Type box:

Enter the IP address of the VMware vCloud™ environment you wish to utilise, along with thecredentials required to access the vCloud IP and click Search to begin the discovery process. Notethe syntax of the Username - User@System where User is the username of the required vCloudorganisation and System is the name of the corresponding vCloud organisation. The "https://"component is optional an will be pre-fixed automatically if not supplied.

At this point you may Close the dialogue if required. The discovery process will continueasynchronously in the background. When discovery completes successfully a vSphere icon will bedisplayed in the CM-Console target region.

The user can then further configure CloneManager® with the required VMware vCloud™ environmentby right-clicking on the vCloud icon and selecting Settings.

This displays the vCloud Settings dialogue:



Use the drop-down selection boxes to configure the default settings. In particular make sure youselect the correct boot ISO for the VM - CloneManager2.2.3-pe4.iso or CloneManager2.2.3-pe5.isoin this example.

Server Selected vCloud server

Organization Select the organization you require

Datacenter Select the Datacenter you require.

ISO Catalog Used to specify which Datastore contains your ISO's.

VM Catalog Allows you to select the Datastore you require your VM's to be created in.

ISO Specify the CloneManager 'Live' Environment for Windows or CloneManager'Live' Environment for Linux ISO to be used to during the cloning stage. Youcan upload a new ISO once the new vCloud is defined if you wish.

Network Specify a Network that will enable connectivity between CloneManager® andthe source machine during the clone.

vApps Select an existing vApp for the clone from the selection in the drop-down list orcreate a new vApp for the clone

Make sure you select OK and the vCloud settings will be saved.

You may repeat this procedure to create as many vCloud objects as required.

Note: Click Refresh at any time to re-run the vCloud discovery process.

Note: It is possible to delete a vCloud object by right-clicking on the icon and selectingRemove Target Hypervisor.

7.1.1.3 Hyper-V settings

Note: The following discussion assumes the reader is conversant with Hyper-Vterminology and operation. It is also assumed that the CloneManager 'Live' Environmentfor Windows and CloneManager 'Live' Environment for Linux ISOs are available in theHyper-V ISO Catalog.

To configure CM-Console so that it has the functionality to create clones on Hyper-V targetenvironments, first select File -> New Hypervisor .. from the menu bar:

48


Then select Hyper-V from the resulting dialogue drop-down Hypervisor Type box:

Enter the IP address of the Hyper-V environment you wish to utilise, along with the credentialsrequired to access the Hyper-V IP and click Search to begin the discovery process.

At this point you may Close the dialogue if required. The discovery process will continueasynchronously in the background. When discovery completes successfully a Hyper-V icon will bedisplayed in the CM-Console target region.

The user can then further configure CloneManager® with the required Hyper-V environment by right-clicking on the Hyper-V icon and selecting Settings.

This displays the Hyper-V Settings dialogue:




Server Selected Hyper-V server

ISO Drive Select driver letter of the disk partition or network share holding theCloneManager 'Live' Environment for Windows or CloneManager 'Live'Environment for Linux ISO

ISO Specify the CloneManager 'Live' Environment for Windows or CloneManager'Live' Environment for Linux ISO to be used to during the cloning stage.

Virtual Switch Specify a virtual network switch that will enable connectivity betweenCloneManager® and the source machine during the clone.

Make sure you select OK and the Hyper-V settings will be saved.

You may repeat this procedure to create as many Hyper-V objects as required.

Note: Click Refresh at any time to re-run the Hyper-V discovery process.

Note: It is possible to delete a Hyper-V object by right-clicking on the icon and selectingRemove Target Hypervisor.

7.1.1.4 Azure settings

Note: The following discussion assumes the reader is conversant with Azureterminology and operation. It is also assumed that the CloneManager 'Live' Environmentfor Windows and CloneManager 'Live' Environment for Linux VHDs are available inAzure storage.

To configure CM-Console so that it has the functionality to create clones on Azure targetenvironments, first select File -> New Hypervisor .. from the menu bar:

Then select Azure from the resulting dialogue drop-down Hypervisor Type box:

Enter your access credentials to the Azure environment you wish to utilise. This is your MicrosoftAzure™ account Subscription ID. Click Search to begin the discovery process. Note the screenshotabove uses example credentials.

At this point you may Close the dialogue if required. The discovery process will continueasynchronously in the background. When discovery completes successfully a Azure icon will be

50


displayed in the CM-Console target region.

The user must then configure CloneManager® with the required Azure environment by right-clickingon the Azure icon and selecting Settings.

This displays the Azure Settings dialogue:

Use the drop-down selection boxes to configure the settings. In particular make sure you select thecorrect boot Image for the VM - CloneManager2.2.3-pe4.iso or CloneManager2.2.3-pe5.iso in thisexample.

Storage Select available storage.This must be first created by the User in Azure.

Container Always set to vhds (virtual hard-disks).

Affinity Group Set as required.

Location Set the geographical location of your Azure cloud.

Virtual Network Select the required VPN. This must be first created by the User in Azure.

Cloud Services Normally select Clone to a new Cloud Service. This will create a new machinein the Azure cloud. This drop-down will also show other cloud servicesavailable. Select an existing service if you wish to create the clone in anexisting cloud service.

Images Specify the CloneManager 'Live' Environment for Windows or CloneManager'Live' Environment for Linux disk image to be used to during the cloning stage.

Make sure you select OK and the Azure settings will be saved.

You may repeat this procedure to create as many Azure cloud objects as required.



Note: The settings 'Affinity Group' and 'Location' are mutually exclusive. Therefore it isonly possible to configure one of these settings.

Note: Click Refresh at any time to re-run the Azure discovery process.

Note: It is possible to delete an Azure object by right-clicking on the icon and selectingRemove Target Hypervisor.

7.1.1.5 AWS EC2 settings

Note: The following discussion assumes the reader is conversant with AWS EC2terminology and operation. It is also assumed that the CloneManager 'Live' Environmentfor Windows and CloneManager 'Live' Environment for Linux VMDKs are available inAWS EC2 storage.

To configure CM-Console so that it has the functionality to create clones on AWS EC2 targetenvironments, first select File -> New Hypervisor .. from the menu bar:

Then select AWS EC2 from the resulting dialogue drop-down Hypervisor Type box:

Enter your access credentials to the AWS EC2 environment you wish to utilise. This is your AWSEC2 account Access and 'Secret' Keys. Click Search to begin the discovery process. Note thescreenshot above uses example credentials.

At this point you may Close the dialogue if required. The discovery process will continueasynchronously in the background. When discovery completes successfully a AWS EC2 icon willbe displayed in the CM-Console target region.

The user must then configure CloneManager® with the required AWS EC2 environment by right-clicking on the AWS EC2 icon and selecting Settings.

52



Use the drop-down selection boxes to configure the settings. In particular make sure you select thecorrect boot VMDK Image - CloneManager2.2.3-pe4.vmdk or CloneManager2.2.3-pe5.vmdk in thisexample.

Region Set the geographical location of your AWS EC2 cloud.

VPC Identify the virtual private cloud (VPC) to be used in your AWS EC2 account.

Subnet Identify the subnet to be used within your selected VPC.

Security Group Specify the security group to be used with your VPC. The 'default' securitygroup can be selected if required.

Image Select the CloneManager 'Live' Environment for Windows or CloneManager'Live' Environment for Linux disk image to be used to during the cloning stage.

Key Pair Select the public/private key-pair used to encrypt/decrypt login information forthe VPC.

Make sure you select OK and the AWS EC2 settings will be saved.

You may repeat this procedure to create as many AWS EC2 cloud objects as required.

Note: Click Refresh at any time to re-run the AWS EC2 discovery process.

Note: It is possible to delete an AWS EC2 object by right-clicking on the icon andselecting Remove Target Hypervisor.

7.1.1.6 SoftLayer settings

Note: The following discussion assumes the reader is conversant with SoftLayerterminology and operation. It is also assumed that the CloneManager 'Live' Environmentfor Windows and CloneManager 'Live' Environment for Linux VHDs are available inSoftLayer storage.

To configure CM-Console so that it has the functionality to create clones on SoftLayer targetenvironments, first select File -> New Hypervisor .. from the menu bar:



Then select SoftLayer from the resulting dialogue drop-down Hypervisor Type box:

Enter your access credentials to the SoftLayer environment you wish to utilise. This is yourSoftLayer account Username and API key. Click Search to begin the discovery process. Note thescreenshot above uses example credentials.

At this point you may Close the dialogue if required. The discovery process will continueasynchronously in the background. When discovery completes successfully a SoftLayer icon will bedisplayed in the CM-Console target region.

The user must then configure CloneManager® with the required SoftLayer environment by right-clicking on the SoftLayer icon and selecting Settings.


54


Use the drop-down selection boxes to configure the settings. In particular make sure you select thecorrect boot ISO Image - CloneManager2.2.3-pe4.iso or CloneManager2.2.3-pe5.iso in this example.

Data Center Set the geographical location of your SoftLayer cloud.

Image Select the CloneManager 'Live' Environment for Windows or CloneManager'Live' Environment for Linux ISO image to be used to during the cloning stage.

Private VLAN Select the private VLAN to be used for the clone.

Public VLAN Select the public VLAN to be used for the clone.

Domain Specify the default domain you wish to use for the clone. If you leave this fieldblank you will be prompted during the clone operation itself.

Hourly billing Tick to enable hourly billing for the clone. Untick to select monthly billing.

Make sure you select OK and the SoftLayer settings will be saved.

You may repeat this procedure to create as many SoftLayer cloud objects as required.

Note: Click Refresh at any time to re-run the SoftLayer discovery process.

Note: It is possible to delete an SoftLayer object by right-clicking on the icon andselecting Remove Target Hypervisor.

7.1.1.7 VIOS settings

Note: The following discussion assumes the reader is conversant with IBM VIOSterminology and operation. It is also assumed that the CloneManager 'Live' Environmentfor AIX ISO is available in the VIOS ISO Catalog.

To configure CM-Console so that it has the functionality to create AIX clones on VIOS targetenvironments, first select File -> New Hypervisor .. from the menu bar:

Then select VIOS from the resulting dialogue drop-down Hypervisor Type box:



Enter the IP address of the VIOS environment you wish to utilise, along with the credentials requiredto access the VIOS IP and click Search to begin the discovery process.

At this point you may Close the dialogue if required. The discovery process will continueasynchronously in the background. When discovery completes successfully a VIOS icon will bedisplayed in the CM-Console target region.

The user can then further configure CloneManager® with the required VIOS environment by right-clicking on the VIOS icon and selecting Settings.

This displays the Hyper-V Settings dialogue:


Server Selected VIOS server

Host Normally set to the VIOS host address

Storage Pool Allows you to select the storage pool you require your VM's to be created in.

ISO Specify the CloneManager 'Live' Environment for AIX ISO to be used to duringthe cloning stage.

VLAN ID Specify the ID of a virtual ethernet switch that will enable connectivity betweenCloneManager® and the source machine during the clone.

56


Make sure you select OK and the VIOS settings will be saved.

You may repeat this procedure to create as many VIOS objects as required.

Note: Click Refresh at any time to re-run the VIOS discovery process.

Note: It is possible to delete a VIOS object by right-clicking on the icon and selectingRemove Target Hypervisor.

7.1.1.8 IP range settings

To configure CM-Console so that it only works within specific IP ranges, you need to select Edit ->IP Range Settings from the menu bar.

To add a new IP range, right-click on the screen and select Add range from the pop up menu. Notethe IP range Mask field uses the IPv4 'slash' notation. The size of the prefix, in bits, is written afterthe oblique. This is called “slash notation”. There is a total of 32 bits in IPv4 address space. Forexample, if a network has the address “192.0.2.0/24”, the number “24” refers to how many bits arecontained in the network. From this, the number of bits left for address space can be calculated. Asall IPv4 networks have 32 bits, and each “section” of the address denoted by the decimal pointscontains eight bits, “192.0.2.0/24” leaves eight bits to contain host addresses. This is enough spacefor 256 host addresses. These host addresses are the IP addresses that are necessary to connectyour machine to the Internet.

A network numbered “10.0.0.0/8” (which is one of those reserved for private use) is a network witheight bits of network prefix, denoted by “/8” after the oblique. The “8” denotes that there are 24 bitsleft over in the network to contain IPv4 host addresses:16,777,216 addresses to be exact.



This will add a new blank row to the bottom of the table, allowing you to enter the IP Range andMask you require. Ticking the Monitored? tick box, results in CM-Console actively scanning withinthe selected ranges.

To remove an IP range, highlight the range you wish to remove. Then right-click on the screen andselect Remove range from the pop up menu.

58


To restrict CM-Console so that it only scans specific IP ranges, you need to select the Monitored?tick-box for the required IP ranges and de-select the Enable Auto-Discovery tick-box.

Click OK to save the settings.

Note: When the Enable Auto-Discovery tick-box is selected, CM-Console will scanacross all IP ranges that are accessible to CM-Console. Currently the bit mask isrestricted to a minimum of /24 to reduce the number of IP addresses to scan tomanageable levels. Otherwise IP address range scan time becomes excessive.

7.1.1.9 Configure default clone settings

This section describes how to configure the CM-Console so that your clones always behave in therequired manner during a clone operation. To achieve this, select the Edit -> Default CloneSettings from the menu bar.

This will display the Default Clone Settings screen where you can configure your clones to performspecific actions during their creation.



UNC Path for Logs Enter the details of the location where you require the logs createdduring the cloning period to be stored. Note that both the CM-Consoleand the clone target system must have network connectivity to this UNCpath.

Domain\Username Domain and Username access credentials for the UNC Path specifiedfor storing the logs created during the clone process.

Password Password access credentials for the UNC Path specified for storing thelogs created during the clone process.

Detailed Logs Select if you require the software to implement more detail in the logs itproduces.

Reboot after clone Tick ing this box will force your cloned system to automatically rebootafter the clone operation is complete (success or failure).

Click OK to save the settings.

7.1.1.10 Licensing settings

This section describes how to setup the Cristie Token Manager licensing so that you are authorisedto run clone operations. The following discussion assumes you have already applied to Cristie toregister CloneManager® and have purchased clone tokens.

Select the Edit -> Licensing Settings from the menu bar.

In this example the CTM is installed on the same system as the CM-Console. The following dialogueis displayed.

60


First you will need to retrieve the license signature for the system the CM-Console is installed on.Select File -> Generate Signature. An example is shown below.

Note: The license and token codes used in the following examples are for illustrationonly. They will not work in your environment.

This signature code is unique to the installed system. You will need to supply this code to CristieSoftware Ltd. during the licensing process.

By default the Cristie Token Manager used is the one installed locally as part of the standard CM-Console installation. See Changing the Cristie Token Manager if you wish to use a remote CristieToken Manager.

Assuming you have obtained the license code from Cristie Software Ltd., to initialise licensingcorrectly first add your contract code by selecting Contract -> Assign Contract:

Then activate your license using Contract -> Activate Contract:



Token codes are purchased from Cristie Software Ltd.. There are 2 token types available: Clone andSync. Select Token -> Add Tokens to add your purchased token codes:

Successful licensing is indicated by a Licensed? value of Yes and non-zero Current Clone/SyncToken counts.

Select Close to exit the dialogue.

7.1.1.11 Notification settings

This section describes how to setup CM-Console email notifications so that you can be keptinformed of clone progress and events. This is in addition to the list of events summarised in theEvent Log section of the CM-Console interface.

Select the Edit -> Notification Settings from the menu bar.

By default only the Event Log is enabled, so select the Enable E-Mail Notifications tick-box anddefine the email settings:

62


Select a suitable email frequency specified in minutes. You will then receive progress emails of anyclones in progress or scheduled to be run later.

To check your email settings are correct click Test Email. This will send a test email to the specifiedEmail Address. Click OK to save the settings.

7.1.1.12 Agentless discovery settings

Remote discovery

Once the clone source is configured for remote administration (see section Agentless clones), beginthe Agentless clone process by selecting the Edit -> Agentless Discovery Settings from the menubar.

This displays the configuration dialogue:



Firstly provide credentials for a local Administrator account that has sufficient privilege to allowremote machines to access a share on the local CM-Console host machine. This account will thenbe used by the Agentless source systems to remotely access the Agentless components on theCM-Console host.

Then add the IP address of all the machines to be cloned in Agentless mode and the credentials ofan Administrator account that will be used to run Agentless components.

Select Discover? to include a machine in the validate or discovery operation. Deselect Discover? toexclude a machine from the validate or discovery process.

Click Validate to check all the credentials supplied. This will be applied to all machines set toDiscover? If the validation run returns success (indicated by an entry "Finished performingAgentless handshake" in the Event Log), then click Discover to begin the discovery process for thespecified hosts. At this point the CM-Console will begin the process of preparing the specified hostmachines for the Agentless clone procedure.

An event will be logged for each successful or failed discovery operation.

Finally, when the discovery process is completes successfully, use the standard drag & dropprocedure to begin the clone or clones.

To add further systems for Agentless discovery simply right-click on the dialogue and select Addsource.

64


Then enter the new IP and access credentials as required. Similarly, to remove a system, right-clickon an entry in the list and select Remove source.

Note: Only Windows source systems are currently supported for Agentless cloning.

7.1.1.13 Schedule settings

This section describes how to modify previously created clone schedules. A schedule is initiallycreated during a drag & drop clone sequence. It cannot be created but only modified via this option.

Select the Edit -> Schedule Settings from the menu bar.



If at least 1 schedule exists a View/Modify Schedules dialogue will be displayed:

Untick the Enabled tick-box to temporarily disable a schedule.

You may modify any of the schedule settings by right-clicking on a schedule and selecting EditSchedule.

This displays the Clone Summary dialogue opened at the Schedule Configuration tab.

66


You may modify any of the schedule settings as required. Please refer to the topic Scheduleconfiguration tab for a definition of these settings.

Right-click a schedule and select Delete to remove a schedule completely:

Click Close when finished.

Note: If a scheduled clone or CloneSync operation is triggered when the target is busy (i.e. a clone or CloneSync is currently running), then it will be postponed until the targetbecomes free. This activity will be recorded in the CM-Console event log.



7.1.1.14 Create batch

This section describes how to create a new clone batch. Select the Edit -> New Batch ... from themenu bar.

This will show a new dialogue presenting a list of all the machines currently discoverable by the <%CP_CONSOLE_SHORTNAME% at this point in time:

This list will include both Windows and Linux systems. Click the Batch? tick-box for each systemyou want to include in this clone batch:

68


Note: A batch must include all Windows or all Linux systems only. It is not possible tomix Windows and Linux systems in a single batch.

Finally, give the batch a name and click Create. At this point the dialogue will remain open allowingyou to create a new batch with a different set of clone source machines. Click Cancel to close thedialogue when you're finished.

A batch is displayed in the CM-Console Source Systems region of the User interface like this:

Use the Batch Settings menu option to later modify members of the batch.

7.1.1.15 Batch settings

This section describes how to setup batch cloning.

Select the Edit -> Batch Settings from the menu bar.

You may also select View/Modify by right-clicking on the batch icon shown in the SourceSystems region of the User interface:

This displays the View/Modify Batch dialogue:



First select a pre-defined batch from the drop-down menu box. You may now add new or removeexisting members to/from the clone batch as required. Click Close when done.

Note: A batch must include either all Windows or all Linux systems. It is not possible tomix Windows and Linux systems in a single batch.

To delete a batch right-click on its corresponding icon from the Source Systems region of the Userinterface and select Delete batch.

7.1.2 Help

To change the trace level, enable/disable Advanced options, display the User Guide or displaythe current CM-Console Log file, select Help from the menu bar.

70


7.1.2.1 Trace level

Tracing will allow you to change the default tracing level for various CM-Console internal 'modules'. Ithas no affect upon the level of tracing on the source or target systems.

You may configure the following components:

CloneManager module: contains information for the CM-Console itself; output can be found inCCM.log.AWS module: contains AWS EC2 access information; output can be found in aws.logHyper-V module: contains Hyper-V access information; output can be found in hyperv.logMS-Azure module: contains Azure access information; output can be found in azure.logSoftLayer module: contains SoftLayer access information; output can be found in softlayer.logTokenManager Client module: contains all token and licensing information; output can be found intokenclient.log.Utilities module: contains miscellaneous information; output can be found in Utils.log. DHCP module: contains DHCP networking information; output can be found in DHCP.log.Disk module: contains clone disk configuration information; output can be found in disk.log

The log files can be found in <InstallDir>\Cristie\CMConsole\Logfiles where <InstallDir> is the rootof the CM-Console installation (typically C:\Program Files).

Each trace module can be set to increasing levels of detail from None through to Debug. Bewarethat the Debug level could have a detrimental affect upon clone performance.

Note: Leave the trace settings at the installed default values unless instructed to changethem by Cristie Support.



7.1.2.2 Export Azure Certificate

This option allows you to save the Azure certificate to be used in conjunction with your MicrosoftAzure™ subscription.

This certificate then needs to be imported into your Azure subscription using the Azure portal.

7.1.2.3 Export Console Logs

Select this option to gather all the CM-Console log files into a single ZIP file. Use of this feature isessential if Cristie Support request the logs to help diagnose cloning issues.

You will be prompted with a browse dialogue box for a location to save the zipped log files.

Accept the default filename and location or modify as required.

Note: Any clone target logfiles previously downloaded will also be included in this ZIPfile. You will then just need to send this single ZIP file to Cristie Support.

72


7.1.2.4 Enable advanced options

When first installed Advanced Options are off by default. When enabled, Advanced options will giveyou an extra Clone Summary Transport Configuration tab when initiating a clone operation.

You will then be able to configure network bandwidth and other transport parameters as required foreach clone or clone batch.

7.1.2.5 User guide

Select User Guide to display a full User Guide for CloneManager®.

This is presented in the form of an e-Book. The e-Book is fully searchable and contains detailedinformation for the product. There is also a PDF version of this document available in the Start menushortcut Cristie \ Documentation folder.

The shortcut also provides links to the Quick Start Guide and the Readme PDF documents. Youwill need a tool like Adobe Viewer however to display these PDF documents.



7.1.2.6 Log file

This link displays the current contents of the CM-Console system log.

An example log file is shown below:

Default: You will only need to refer to this log when instructed to by Cristie Support.

7.1.2.7 About

This displays a summary of the CM-Console release. An example is shown below.

74


This shows the Java Runtime Environment (JRE) version currently in use, the CM-Console productversion and the host OS type. You may be asked by Cristie Support to supply this informationduring a support case.

It also shows links to the Cristie Knowledge Base and the Cristie Support websites (Internetaccess required).

7.1.3 Event log

While the CM-Console is running all clone events are recorded. These include the following:

auto discovery of source/target machines

clone start time

clone progress

clone end time

clone success/failure

clone abort

clone-sync start

settings change

vSphere, vCenter, vCloud, Hyper-V or VIOS Hypervisor discovery

An example is shown below:

7.1.4 Clone to a physical machine

Note: Before commencing a clone, it is recommended that you configure your clone Settings. If this is not done the default clone settings dialogue will be displayed on yourfirst clone operation. As a minimum you should specify the log file location, associatednetwork share access credentials and Licensing setup.

A physical machine also includes existing VMs manually created in VMware vCenter™, vSphere,Microsoft Hyper-V™ or VMware Workstation running either the CloneManager 'Live' Environment forWindows or CloneManager 'Live' Environment for Linux.

To commence a clone of an available source machine, select the icon of the system you require toclone. Then drag the icon from the Source Systems panel, across to the Target Systems panel,dropping the icon onto the machine icon that you wish to clone to. The following screenshot,illustrates a source machine being "dragged" on to the target icon.



This will result in a confirmation box being displayed.

If the details are correct for the clone operation you wish to perform, click Yes to continue. (ClickingNo will cancel the clone operation). Next a Clone Summary dialogue will be shown. This dialoguehas multiple tabs and you should examine each one in turn to check the settings.

76


Note: The user (on the source) specified at this point must have local Administratorrights (root on Linux). On Windows User Account Control (where applicable) must be setno higher (restrictive) than the default setting.

Note: In Linux it is not possible to change either the clone target's hostname or IP via theCM-Console – although the Console allows you to set these.

After reviewing the summary to determine the correct settings have been configured, click Confirm toinitiate your clone. This will return you to the CloneManager® console, which will now update in real-time to indicate how the clone is progressing.



While the clone is running the Event Log will show a real-time summary of:

a count of the number of current files copied out of the total number of files to be copied

the current throughput of data from source to target in MB/s (Megabytes per second)

the remaining time to complete the clone - note there are many factors that affect this value(e.g. network bandwidth) and it will change during the clone process; it will, however, becomemore accurate as more files are copied to the target

Once the cloning process has finished, the progress bar of the target machine will confirm the clonehas completed successfully and the event log entry for the clone will update with the time that theclone completed.

78


Note: When cloning to supported hypervisors and clouds (by dragging a Source onto theHypervisor Server icon in the Target Machines panel), then a brand new virtual machinewill be created on that <%CP_HYPERVISOR%.

Note: If you create a new (target) VM on the Hypervisor server manually and boot it witheither the CloneManager 'Live' Environment for Linux or the CloneManager 'Live'Environment for Windows - it will appear as a conventional target machine in the TargetMachines panel.

Completion of the clone operation is indicated on both the clone source and target machine icons:

Source

The clone count represents the total clone operations completed for this source machine. It could bethat this source machine is being cloned multiple times.

Clone and CloneSync counts are displayed on the source icon when the machine is not beingcloned. Note however that counts only relate to clone/sync operations that have occurred since theCM-Console was started.

Target

At this point you may boot the clone target or retain it in its current state ready for a futureCloneSync.



7.1.5 Clone to VMware vCenter™/vSphere

The CM-Console allows you to clone a source machine to a new VM located on a VMwarevSphere™ server. In this case the new VM is created with a new template which does not need tobe pre-defined.

Note: Before running a clone sequence to vSphere, make sure the basic environmentsettings are defined. To do this right-click on the appropriate vSphere icon in the CloneTarget region of the screen and select Settings... Choose the appropriate defaults fromthe drop-down options.

To start a clone to vCenter or vSphere it is now a simple matter to drag a source machine onto theicon just like a physical machine clone. The VM will be created and the progress of this initialoperation will be displayed under the vCenter/vSphere target icon. Once the new target VM has beencreated a new icon will be displayed in the Target panel to represent this new machine. Remainingclone progress will then be displayed against this icon and not the vCenter/vSphere environment itresides on.

The following screenshot, shows a source machine being "dragged" on to a vCenter icon.

Upon dropping the source on the target the following prompt will be displayed.

Click Yes to begin the clone operation to the vCenter/vSphere target. Click No to abandon the

80


operation at this point.

A new tab called vSphere Configuration will be shown as part of the Clone Summary dialogue.

You may change any of the default vSphere options shown.

The rest of the Clone Summary settings are identical to that for physical clones.

A new machine representing the clone will appear in the Target Systems panel if you proceed withthe clone. Any errors in the clone process are reported in the event log.

Note1: Ensure you configure the boot options correctly in vCenter/vSphere for the newVM. For example make sure you set the correct boot disk. Disk 0 will be set as thedefault boot disk.

Note2: You may need to reboot the clone target system a few times to ensure that a newHostname and any IP address(s) change(s) are applied correctly. This will also ensurethat any dynamic volumes are imported correctly.

7.1.6 Clone to VMware vCloud™

The CM-Console allows you to clone a source machine to a new VM located on a VMware vCloud™server. In this case the new VM is created with a new template.

Note: Before running a clone sequence to vCloud, make sure the basic environmentsettings are defined. To do this right-click on the appropriate vCloud icon in the CloneTarget region of the screen and select Settings... Choose the appropriate defaults fromthe drop-down options.

To start a clone to vCloud it is now a simple matter to drag a source machine onto the icon just likea physical machine clone. The VM will be created and the progress of this initial operation will be



displayed under the vCloud target icon. Once the new target VM has been created a new icon will bedisplayed in the Target panel to represent this new machine. Remaining clone progress will then bedisplayed against this icon and not the vCloud environment it resides on.

The following screenshot, shows a source machine being "dragged" on to a vCloud icon.


Click Yes to begin the clone operation to the vCloud target. Click No to abandon the operation at thispoint.

A new tab called vCloud Configuration will be shown as part of the Clone Summary dialogue.

82


You may change any of the default vCloud options shown. The rest of the Clone Summary settingsare identical to that for physical clones.


The rest of the clone operation is identical to that for physical clones. However please refer to thesection below titled IP allocation mode.

Note: Ensure you configure the boot options correctly in vCloud for the new VM. Forexample make sure you set the correct boot disk. Disk 0 will be set as the default bootdisk in vCloud.

Note: You may need to reboot the clone target system a few times to ensure that a newHostname and any IP address(s) change(s) are applied correctly. This will also ensurethat any dynamic volumes are imported correctly.

7.1.6.1 IP allocation mode

To perform a clone operation the CloneManager 'Live' Environment for Windows or CloneManager'Live' Environment for Linux ISO's must be booted on the clone target. Normally CloneManager®expects these environments to boot with one or more IP addresses using DHCP so that they arevisible to the CloneManager Console.

For those customers who are unable to use the standard DHCP server feature in vCloud analternative mechanism has been provided in the CM-Console. This feature allows IP addresses to beautomatically provided to these target machines from a user defined range (pool) setup on the VMhosting the CloneManager Console. In this case the CM-Console must be installed in the samevCloud environment as the proposed target.

To select the desired IP allocation mode run a clone sequence to a vCloud target Hypervisor as



normal and on the Clone Summary dialogue select the IP Allocation Mode drop-down box.

The options are:

1. DHCP: select to use a DHCP server. This is the default.

2. Static - IP Pool: select a static IP address from a pre-defined vCloud Network IP pool. TheCM-Console follows the IP allocation policy of the IP pool configured for the virtual networkselected. To setup the IP pool use VMware vCloud Director to configure a new Network in the Administration tab. Make sure you use this same Network when configuring the vCloudtarget.

3. Static - Manual: select to use the static IP address defined in the Target Configuration tabof the Clone Summary dialogue.

Note: To use this feature the CloneManager Console must have network connectivity toboth the source and target machines at the time of clone.

7.1.7 Clone to Microsoft Hyper-V™

The CM-Console allows you to clone a source machine to a new VM located on a Microsoft Hyper-V™ server. In this case the new VM is created with a new template which does not need to be pre-defined.

Note: Before running a clone sequence to Hyper-V, make sure the basic environmentsettings are defined. To do this right-click on the appropriate Hyper-V icon in the CloneTarget region of the screen and select Settings... Choose the appropriate defaults fromthe drop-down options.

Note: The OS boot disk MUST be disk 0

84


To start a clone to Hyper-V it is now a simple matter to drag a source machine onto the icon justlike a physical machine clone. The VM will be created and the progress of this initial operation willbe displayed under the Hyper-V target icon. Once the new target VM has been created a new iconwill be displayed in the Target panel to represent this new machine. Remaining clone progress willthen be displayed against this icon and not the Hyper-V environment it resides on.

The following screenshot, shows a source machine being "dragged" on to a Hyper-V icon.


Click Yes to begin the clone operation to the Hyper-V target. Click No to abandon the operation atthis point.

A new tab called Hyper-V Configuration will be shown as part of the Clone Summary dialogue.



You may change any of the default Hyper-V options shown. Additionally, selecting CreateTemplate will allow the clone to become a template and will create multiple copies of the samesource machine on the Hyper-V server.

The rest of the Clone Summary settings are identical to that for physical clones.

Note: It is recommended that disk mapping be enabled in the Target Configuration tab forHyper-V clones.


Note: Ensure you configure the boot options correctly in Hyper-V for the new VM. Forexample make sure you set the correct boot disk. Disk 0 will be set as the default bootdisk.

Note: You may need to reboot the clone target system a few times to ensure that a newHostname and any IP address(s) change(s) are applied correctly. This will also ensurethat any dynamic volumes are imported correctly.

Note: Please do not shutdown the CM-Console before the clone sequence has begun thefile copy stage.

7.1.8 Clone to Microsoft Azure™

The CM-Console allows you to clone a source machine to a new VM located on your Azureenvironment.

Note: Before running a clone sequence to Azure, make sure that the source system hasRemote Desktop (Windows) or SSH (Linux) enabled. Otherwise it will not be possible toaccess the cloned system on Azure.

86


Note: Before running a clone of a Windows system to Azure, make sure that the firewallon the source system is configured to allow 'Remote Desktop' and 'File and Printer Sharing' communications. If Remote Desktop is not allowed through the firewall, it willnot be possible to RDP into the cloned system. If 'File and Printer Sharing' is not allowedon the firewall settings, then it will not be possible to successfully 'ping' the clonedsystem.

Note: Before running a clone sequence to Azure, make sure the basic environmentsettings are defined. To do this right-click on the appropriate Azure icon in the CloneTarget region of the screen and select Settings... Choose the appropriate defaults fromthe drop-down options.

Note: The OS boot disk MUST be disk 0

Note: No disk can be larger than 1TB. Also there can be no more than 16 disks in total.These restrictions are imposed by Azure not CloneManager®.

To start a clone to Azure it is now a simple matter to drag a source machine onto the icon just like aphysical machine clone. The VM will be created and the progress of this initial operation will bedisplayed under the Azure target icon. Once the new target VM has been created a new icon will bedisplayed in the Target panel to represent this new machine. Remaining clone progress will then bedisplayed against this icon and not the Azure environment it resides on.

The following screenshot, shows a source machine being "dragged" on to an Azure icon.




Click Yes to begin the clone operation to the Azure target. Click No to abandon the operation at thispoint.

A new tab called Azure Configuration will be shown as part of the Clone Summary dialogue.

You may change any of the default Azure options shown. The rest of the Clone Summary settingsare identical to that for physical clones.

Note: For a successful clone, DHCP needs to be enabled, therefore it is not possible todisable this feature on the Target Configuration tab.

A new machine representing the clone will appear in the Target Systems panel. If you proceed withthe clone. Any errors in the clone process are reported in the event log.

Post Clone (or CloneSync) Requirements

After a successful clone (or CloneSync), there are some further steps that need to be implementedso that the cloned or synced system can be accessed.

Firstly, the CM-Console needs to be made aware of the cloned system on the Azure environment.This is achieved by right-clicking on the Azure target icon and selecting the option Refresh.

88


The next step is to remove the Live Image from the cloned system. To do this, first right-click on theAzure target icon and the select the option Attach/Detach Live Image...

Configure the Attach/Detach Live Image screen, so that the option Operation is set to Detach. Theother settings relate to the Azure environment you require to detach the Live image from.

Click OK to start the detachment process.

On the resulting confirmation window, click Yes to detach the Live Image from the Azure target.Click No to abandon the operation at this point.

Once the Live Image has been detached, the Azure target will be shut down and rebooted to the



cloned operating system.

Attaching the Live Image to an Azure system in order to perform a CloneSync

In order to perform a sync on an Azure system that has had the Live Image detached, the followingsteps must be undertaken.

Right-click on the Azure target icon and selecting the option Attach/Detach Live Image...

Configure the Attach/Detach Live Image screen, so that the option Operation is set to Attach andImage is set to the required CloneManager® VHD. The other settings relate to the Azure systemyou require the Live Image to be attached to.

Click OK to start the attachment process.

On the resulting confirmation window, click Yes to attach the Live Image to the Azure system. ClickNo to abandon the operation at this point.

Once the Live Image has been attached, the Azure system will be shut down and rebooted to theselected CloneManager® environment.

90


An icon representing this system will appear in the Target Systems panel.

Note: Azure imposes a restriction of 1023GB maximum disk size.


The Azure Temporary Storage Drive

At the end of the simulation test the recovered system will have an extra disk created by Azurewhich is used for local temporary storage. It is recommended this disk is retained and not deleted.

This temporary storage drive is a local drive on the physical box that should only serve as scratchspace. For example, you could put the paging file onto this drive to save on transaction costs foreach Windows page-in - but nothing else. It is recommended that nothing of importance is placed onthis drive as it will be deleted upon any hardware failure. The OS disk and any data disks attachedwill be preserved on hardware failure.

For general guidance, you should consider putting anything requiring high IOp's, low latency ortransactional durability onto an attached data disk (details here: http://www.windowsazure.com/en-us/manage/windows/how-to-guides/attach-a-disk/). You should leave your OS disk for just your OS.This will give you the highest durability and performance when running in Microsoft Azure™.

7.1.9 Clone to Amazon Web Services™ (AWS) - Elastic Compute Cloud (EC2)

The CM-Console allows you to clone a source machine to a new VM located on your AWS EC2environment.

Note: Before running a clone sequence to AWS EC2, make sure that the source systemhas Remote Desktop (Windows) or SSH (Linux) enabled. Otherwise it will not bepossible to access the cloned system on AWS EC2.

Note: Before running a clone of a Windows system to AWS EC2, make sure that thefirewall on the source system is configured to allow 'Remote Desktop' and 'File andPrinter Sharing' communications. If Remote Desktop is not allowed through the firewall,it will not be possible to RDP into the cloned system. If 'File and Printer Sharing' is notallowed on the firewall settings, then it will not be possible to successfully 'ping' thecloned system.

Note: Before running a clone sequence to AWS EC2, make sure the basic environmentsettings are defined. To do this right-click on the appropriate AWS EC2 icon in the CloneTarget region of the screen and select Settings... Choose the appropriate defaults fromthe drop-down options.

Note: The AWS EC2 environment itself (i.e. not CloneManager®) imposes certain

restrictions on any cloned system:

- the OS boot disk MUST be disk 0.

- each disk must be between 1 GB and 1024 GB in size.

To start a clone to AWS EC2 it is now a simple matter to drag a source machine onto the icon justlike a physical machine clone. The VM will be created and the progress of this initial operation willbe displayed under the AWS EC2 target icon. Once the new target VM has been created a new iconwill be displayed in the Target panel to represent this new machine. Remaining clone progress willthen be displayed against this icon and not the AWS EC2 environment it resides on.

The following screenshot, shows a source machine being "dragged" on to an AWS EC2 icon.

http://www.windowsazure.com/en-us/manage/windows/how-to-guides/attach-a-disk/

http://www.windowsazure.com/en-us/manage/windows/how-to-guides/attach-a-disk/




Click Yes to begin the clone operation to the AWS EC2 target. Click No to abandon the operation atthis point.

A new tab called AWS EC2 Configuration will be shown as part of the Clone Summary dialogue.

92


You may change any of the default AWS EC2 options shown. The rest of the Clone Summarysettings are identical to that for physical clones.





Firstly, the CM-Console needs to be made aware of the cloned system on the AWS EC2environment. This is achieved by right-clicking on the AWS EC2 target icon and selecting the option Refresh.

The next step is to remove the Live Image from the cloned system. To do this, first right-click on theAWS EC2 target icon and the select the option Attach/Detach Live Image...



Configure the Attach/Detach Live Image screen, so that the option Operation is set to Detach. Theother settings relate to the AWS EC2 environment you require to detach the Live image from.


On the resulting confirmation window, click Yes to detach the Live Image from the AWS EC2 target.Click No to abandon the operation at this point.

Once the Live Image has been detached, the AWS EC2 target will be shut down and rebooted to thecloned operating system.

Attaching the Live Image to an AWS EC2 system in order to perform a CloneSync

In order to perform a sync on an Azure system that has had the Live Image detached, the followingsteps must be undertaken.

Right-click on the AWS EC2 target icon and select the option Attach/Detach Live Image...

94


Configure the Attach/Detach Live Image screen, so that the option Operation is set to Attach andImage is set to the required CloneManager® VHD. The other settings relate to the AWS EC2system you require the Live Image to be attached to.


On the resulting confirmation window, click Yes to attach the Live Image to the AWS EC2 system.Click No to abandon the operation at this point.

Once the Live Image has been attached, the AWS EC2 system will be shut down and rebooted tothe selected CloneManager® environment.


7.1.10 Clone to IBM SoftLayer

The CM-Console allows you to clone a source machine to a new VM located on your SoftLayerenvironment. Cloning to SoftLayer must be performed with the following pre-requisites:

1. The CM-Console must be installed and run on a suitable host system already available withinthe same SoftLayer environment where the clone target is going to be created. It is notpossible to manage the clone operation using a CM-Console running external to thisenvironment. However, the clone source will normally be available external to this



environment. Note: Please stop the World Wide Web Publishing service on this CM-Console host system (if running) prior to installing the CM-Console.

2. Similarly the CTM must be installed and run on the same machine as the CM-Console above.

3. Configure the default location for log files (in CM-Console) to be a shared folder on the samesystem as above.

4. The IP(s) of the source machine need to be mapped to static NAT subnets within SoftLayer.

5. Use the Edit -> IP Range Settings option in the CM-Console to set the same IP subnets inorder for the CM-Console to connect to the clone source system.

Note: Before running a clone of a Windows system to SoftLayer, make sure that thefirewall on the source system is configured to allow 'Remote Desktop' and 'File andPrinter Sharing' communications. If Remote Desktop is not allowed through the firewall,it will not be possible to RDP into the cloned system. If 'File and Printer Sharing' is notallowed on the firewall settings, then it will not be possible to successfully 'ping' thecloned system.

Note: Before running a clone sequence to SoftLayer, make sure the basic environmentsettings are defined. To do this right-click on the appropriate SoftLayer icon in the CloneTarget region of the screen and select Settings... Choose the appropriate defaults fromthe drop-down options.

Note: The IBM SoftLayer environment itself (i.e. not CloneManager®) imposes certain

restrictions on any cloned system:

- restricted to systems with up to 5 local disks.

- disk 0 must be no larger than 100GB, the remaining disk(s) must be no larger than 2TB

in size.

- only 1 NIC is supported.

- only 4 clone operations can run concurrently (including members of a batch).

- the OS boot disk MUST be disk 0.

- it is not possible to clone to a manually created clone target already running in

SoftLayer. Only CloneManager® can set up the correct NIC and route configuration.

To start a clone to SoftLayer it is now a simple matter to drag a source machine onto the icon justlike a physical machine clone. The VM will be created and the progress of this initial operation willbe displayed under the SoftLayer target icon. Once the new target VM has been created a new iconwill be displayed in the Target panel to represent this new machine. Remaining clone progress willthen be displayed against this icon and not the SoftLayer environment it resides on.

The following screenshot, shows a source machine being "dragged" on to an SoftLayer icon.

96



Click Yes to begin the clone operation to the SoftLayer target. Click No to abandon the operation atthis point.

A new tab called SoftLayer Configuration will be shown as part of the Clone Summary dialogue.



You may change any of the default SoftLayer options shown. The rest of the Clone Summarysettings are identical to that for physical clones.




Firstly, the CM-Console needs to be made aware of the cloned system on the SoftLayerenvironment. This is achieved by right-clicking on the SoftLayer target icon and selecting the option Refresh.

The next step is to remove the Live Image from the cloned system. To do this, first right-click on theSoftLayer target icon and the select the option Attach/Detach Live Image...

98


Configure the Attach/Detach Live Image screen, so that the option Operation is set to Detach. Theother settings relate to the SoftLayer environment you require to detach the Live image from.


On the resulting confirmation window, click Yes to detach the Live Image from the SoftLayer target.Click No to abandon the operation at this point.

Once the Live Image has been detached, the SoftLayer target will be shut down and rebooted to thecloned operating system.

Attaching the Live Image to an SoftLayer system in order to perform a CloneSync

In order to perform a sync on an SoftLayer system that has had the Live Image detached, thefollowing steps must be undertaken.

Right-click on the SoftLayer target icon and select the option Attach/Detach Live Image...



Configure the Attach/Detach Live Image screen, so that the option Operation is set to Attach andImage is set to the required CloneManager® ISO. The other settings relate to the SoftLayersystem you require the Live Image to be attached to.


On the resulting confirmation window, click Yes to attach the Live Image to the SoftLayer system.Click No to abandon the operation at this point.

Once the Live Image has been attached, the SoftLayer system will be shut down and rebooted to theselected CloneManager® environment.


Note: CloneManager® enforces a minimum RAM requirement of 2GB on the clone targetregardless of the RAM size on the clone source.


7.1.11 Clone Summary

The tabbed Clone Summary dialogue is used by all the different clone target types. It is displayedafter confirming that a drag & drop sequence should start. It consists of up to 8 tab sections whichshould all be examined in turn before selecting Confirm.

100


7.1.11.1 Log details tab

Defines the location and access credentials of the folder to hold the clone log files. This ismandatory but may already be preset with details from the previous clone operation. See examplebelow.

If you wish more detailed logging information select the Detailed Logs tick box. This may berequired by Cristie Support for example.

7.1.11.2 Source configuration tab

Defines the source system access credentials, for example the local source machine Administrator.Also supply the corresponding account password. This is used by the target machine to remotelyaccess the source machine.



Note: A domain Administrator account may be also used for this instead of a localAdministrator if required.

102


7.1.11.3 Target configuration tab

This allows certain system parameters of the clone to be automatically changed at the end of theclone process.

Change any of the network parameters as required. These are values that the clone target machinewill boot with. It is possible to change one or more of the network interfaces as required.

Note: If any network fields are left blank, then the corresponding value from the sourcemachine will be used instead. So, for example, if the IP address is not changed, thenwhen the target machine boots and the source machine is still running, there could benetwork issues because the clone will have the same IP address.

Reboot After Clone: Select if the clone target should be automatically booted at the end of theclone sequence (success or failure).

Disable HP Services: Select if you wish to disable the startup of HP services on the clone target atthe end of a successful clone sequence. When cloning from an HP physical system to non-HPhardware these services can sometimes cause boot failure on the clone. However, this is notnormally required. Only select if recommended by Cristie Support.

Map Disks: Select if you wish to automatically enforce disk mapping of source to target disks basedupon exact disk size. This is not normally required or recommended by Cristie. Only select ifrecommended by Cristie Support.

Note: If Map Disks is selected for a clone then it must also be selected for anysubsequent CloneSync, otherwise the CloneSync will probably fail.

Tailor Target Resources: Select if you wish to tailor the target number of CPUs and RAM size fortargets resident on a Hypervisor. Refer to section Tailor target VM configuration for more details.



Note: If the IP addresses on the clone source are static values they will not be retainedon the clone target. DHCP addresses will be allocated to the clone instead.

7.1.11.4 Disk configuration tab

In some clone operations you may want to exclude certain disks and/or disk volumes from beingcopied to the clone target. For example you may have a large database hosted in a SANenvironment. You would not normally want to clone this.

Note: The target machine must have sufficient disks and be of a sufficient size toaccommodate the selected clone disk configuration. If the target disks are of differentsize to the source they must be at least big enough to accommodate the original total filesize in use. If not the clone will fail.

The Disk Configuration tab provides the following options:

Clone All Volumes

This is the default setting. In this mode all disks and volumes are copied to the target machine.

Choose Volumes to Clone Manually

Select this option to choose the disks and volumes manually. The boot/system/reserved diskvolumes will always be copied regardless of other disks/volumes selected and it will not be possibleto deselect them.

104


Use the Clone? tick box to select/deselect each disk or volume as required.

Note: If there are any dynamic volume RAIDs, mirrors or extended partitions defined itwill not be possible to deselect any of their individual elements. So for example it will notbe possible to deselect one half of a two volume mirror. If this example is attempteddeselecting one half will automatically result in the deselection of both volumes.Currently only all or no dynamic disks can be cloned.

Deselecting Windows dynamic disks

CloneManager® allows you to deselect certain disks or volumes during a clone sequence. ForWindows dynamic disks there are certain rules about how the equivalent disks on the target arepartitioned.

1. If you ignore all the volumes (i.e. on every dynamic disk) on the source machineCloneManager® will still need to partition all the dynamic disks on the clone target machine.

2. If you ignore one dynamic disk then you must ignore all of them. In this case the dynamicdisks on the target do not need to be partitioned.

3. Note if you ignore a basic partition (i.e. not a dynamic volume) then the corresponding targetdisk must be re-partitioned.

You may need to turn on the disk mapping option if the target has fewer disks than the sourcemachine. This is where the CloneManager 'Live' Environment for Linux/Windows/AIX will attempt tomatch disks from the source to the target based upon criteria such as disk controller type, diskgeometry, disk signature, disk size and partition configuration. By default it will map the WindowsOS drive and then map naively (i.e. INI disk 0 -> ACT disk 0) until it runs out of target disks. This isso the Windows OS drive is always recovered.

Disk mapping is automatically enabled if:



1. A USB drive is detected.

2. Multi-pathing (i.e. SAN) is detected.

3. The number of target disks is greater than the number of source disks.

Turn on disk mapping from the Clone Summary -> Target Configuration tab when beginning aclone sequence. Select the "Map Disks" option.

7.1.11.5 Dissimilar hardware tab

If the clone target uses identical disk controllers and Network Interface Card (NIC) devices to thesource machine then it is considered to be a similar clone sequence. In this case the DissimilarHardware tab can be ignored.

However, if the disk controllers and/or NICs are different then it is likely that the clone target willrequire new drivers to be installed during the clone process. This is referred to as a dissimilar clonesequence. If this is not configured then missing disk controller drivers will cause the clone to BlueScreen of Death (BSOD) at boot. Different NICs will not stop the clone booting, but could causeissues unless new drivers can be injected locally (say via a USB key) after the target is booted. Thisfeature allows the new drivers to be injected automatically during the clone sequence.

Note: The drivers used here must be compatible with the OS being cloned.

This tab provides the ability to provide the location of the new hardware drivers in one of three cases.

Manual/Physical Dissimilar Clone

106


In this case select a folder and access credentials containing the new disk and NIC drivers. Thisfolder must be visible to the clone target machine.

Clone to Virtual Machine



Select this option when cloning to a VM booted into the CloneManager 'Live' Environment for Linux/Windows/AIX where the source machine is either:

a physical machine

running on a different type of Hypervisor

the same type of Hypervisor, but using different virtual hardware (i.e. NIC or disk controller).

In these cases the VM drivers are already provided by CloneManager® and therefore no path isrequired.

7.1.11.6 Transport configuration tab

This tab will only be shown if Enable Advanced Options is selected under Main Menu Help.

This tab allows certain clone configuration parameters (for the current clone only) to be changed.

108


Most of these parameters should only be changed from their default values on advice from CristieSoftware Ltd.. However, bandwidth throttling is something that may be useful in production.

Bandwidth Throttling

Change Bandwidth Throttling if you wish to set a particular throughput in kB/s (Kilobytes persecond) for the clone operation. For example, the dialogue below shows the bandwidth being set toa custom value.



If Bandwidth Throttling is not changed then the clone operation will run with no bandwidth restriction.

Note: Setting a bandwidth value of 0 is interpreted as meaning no bandwidth restrictionshould be applied.

Compression

Set the Compression Level to a non-zero value to compress all data transfer exchanges betweenclone source and target. The compression level is expressed as a value 0 to 9. Level 0 means nocompression, level 1 is minimum compression and level 9 is maximum compression. Dependingupon the network environment in use this may enhance clone performance.

Encryption

Set SSL Enabled to force all data transfer exchanges between source and target to be securedusing SSL encryption. SSL encryption has minimal effect upon clone performance in terms ofbandwidth, but

7.1.11.7 Hypervisor configuration tab

This tab allows the current default settings of the selected Hypervisor target environment to bechanged. The contents of this tab varies according to the target environment selected for the cloneoperation. The following example shows vSphere:

110


Any parameters modified on this tab affect the current clone operation only. To change the defaultsettings of an Hypervisor refer to section Settings.

7.1.11.8 Schedule configuration tab

It is possible to define a schedule for a clone rather than run the clone immediately. For exampleyou could run an initial full clone followed by CloneSync operations at regular intervals.

To do this select the Schedule Configuration tab on the Clone Summary dialogue.



Select Yes to create a new schedule for the clone.

In the example shown the initial clone will run as soon as Confirm is clicked. SubsequentCloneSyncs will run 4-hourly starting at 12:30. Leave the Run the job when I click Confirm tick-box unticked if you want the initial clone to run at the scheduled time first. Detailed definitions foreach field are summarised below.

112


Start Time andDate

The start date/time for the initial clone or subsequent CloneSync operations.Note that the trigger time of the schedule is always set to run 30 secondsafter the time specified here to check that the target is ready.

Run Hourly/Daily/Weekly/Monthly/Once

The frequency of regular clone or CloneSync operations relative to midnightfor hourly or daily schedules. More information below.

Clone repeat count The number of times the clone should be repeated. A value of zero indicatesan indefinite number of repetitions.

CloneSync repeatcount

The number of times the CloneSync should be repeated. A value of zeroindicates an indefinite number of repetitions. Note this option will be disabled(greyed out) if the clone repeat count is set to indefinite (0).

Run the job when Iclick Confirm

The initial operation is run immediately Confirm is selected. Leave thisunticked if you wish the initial clone to run at the schedule date/time instead.

Once a schedule has been created you may modify its definition from the Edit -> ScheduleSettings menu option.

Understanding Schedule Start Time and Interval

CloneManager® uses an implementation of 'cron' to handle the timing of clones and CloneSyncs.'cron' is only able to schedule at fixed interval times past midnight and the initial start time is'rounded up' to the next valid interval time. Therefore the specified start time isn't always the timethe first scheduled clone runs.

Some examples will help to clarify this.

Example 1: A defined schedule configured say to run every 5 hours starting at 11:00 will first run at15:00 when the 'current' time is say 10:30. This is the first valid interval after midnight that resides inthe future. Subsequent clones will run at 20:00, 5:00 (next day), 10:00 (next day) and 15:00 (nextday) and so on.

Example 2: A defined schedule configured say to run every 6 hours starting at 11:00 will first run at12:00 when the 'current' time is say 10:30. This is the first valid interval after midnight that resides inthe future. Subsequent clones will run at 18:00, 0:00 (next day), 6:00 (next day), 12:00 (next day)and 18:00 (next day) and so on.

7.1.12 Using CloneSync

A clone target system maybe also used in warm standby mode. This is where a finalsynchronisation process is run to bring a previously cloned system up-to-date prior to booting intooperational mode. The CloneSync process is intended for use on slow or low bandwidth networksonly where it makes more sense to run an incremental update rather than repeat a full cloneoperation.

To prepare for this, an initial clone sequence must be run and the same clone target left booted intothe Live environment. It is up to the user to decide whether to leave the clone machine booted orunbooted. Obviously leaving it booted means the clone can be made operational slightly quicker.When booted the clone target must be running the CloneManager 'Live' Environment for Windows orCloneManager 'Live' Environment for Linux.

Note: When a Windows system is left in a booted state the CloneManager 'Live'Environment for Windows will re-boot every 72 hours. This is a restriction of theMicrosoft Windows PE4 or PE5 operating environment which forms the basis of theCloneManager 'Live' Environment for Windows.

When the clone target needs to be made operational a final synchronisation step is run to bring the



machine up-to-date. This updates the clone with any changes made to the original source machinesince the original clone. This is significantly quicker than repeating the full clone process from thebeginning. This process is called CloneSync and is supported on both Windows and Linuxsystems.

CloneSync compares timestamps and file sizes on all files/folders between source/target machinesand only copies modified or new files. Any files/folders deleted from the source machine since theclone operation will also be removed from the clone target machine. CloneSync can only be usedunder certain conditions, otherwise the full clone process will need to be repeated. The followingitems must still be the same as they were in the original clone:

1. The disk configuration; i.e. number of disks and partitions including their corresponding typeand size.

2. The network interface(s) type and number.

3. The IP address(es) and hostname of the original source machine.

4. CloneSync must be synced to the original clone source.

The following discussion summarises how to perform the CloneSync process from within the CM-Console. It is assumed that an initial clone has already been made.

On the CM-Console right-click on the clone target machine and select the CloneSync option asshown in the example below:

You will then be prompted to confirm the CloneSync operation thus:

Select Yes to continue No to cancel the operation. The Clone Summary dialogue will then bedisplayed.

114


Check the parameters on each tab in the dialogue and when the configuration is set as requiredclick Confirm to begin the CloneSync sequence. The synchronisation process will be displayed inthe CM-Console GUI as in the following example:

CloneSync completion is indicated like this:

At this point the clone target is up-to-date with any changes made to the source machine since theoriginal clone. It may now be booted if required or kept in a warm standby state ready for anotherCloneSync sequence.

CloneSync for Linux machines follows the same principles outlined above. In this case of course theCloneManager 'Live' Environment for Linux is run on the clone target machine.

115Network setup


8 Network setup

CloneManager® normally uses IP multicast discovery to automatically detect remote clone sourceand target machines (i.e. clients running CM-Agent). This works even across different subnets. Thisgenerally means ensuring all managed routers and/or switches within the network are configured topass through multicast transmissions.

Note broadcast will be used if multicast is not available as a fall-back, but this will only work on thelocal subnet.

However, if enabling multicast in your network is not possible and you wish to traverse subnets youwill need to manually enter the hostnames or IP addresses of your client machines. This can beachieved using the Manual IP Range Configuration option in the CM-Console. This method usesIP unicast messaging and therefore the network must be configured to pass through unicasttransmissions.

Important: If neither IP multicast or unicast is enabled on your network CM-Console willnot be able to detect and communicate with any remote clone source or targetmachines!

The following ports are used by CloneManager® components during the cloning process:

1. UDP 4000 - CDS request port

2. UDP 4001 - CDS response port

3. TCP 4000 - CDS request port TCP

4. Multicast group 239.1.1.4 on port 4000 - only required if Multicast is used

5. HTTP port 80 is used by the CM-Console to communicate with the CM-Agent

Please ensure all network devices located between source, console and target machines allow trafficto pass on these ports.

Refer to Appendices - Network Configuration for further details.

116


9 Clone target menu options

Some useful features are provided on a mouse right-click menu for clone target systems visible inthe CM-Console. Select the appropriate system in the Target Systems section and right-click withthe mouse.

Abort Current Operation

If a clone or CloneSync is in progress use this option to abort the operation. This may take a fewmoments to take effect.

CloneSync

Click on this option to begin a CloneSync sequence. This is only possible after an initial clone hasbeen successfully performed.

Download Logs

Select to remotely download the current target logs to a folder on the CM-Console host. This is onlypossible while a clone or CloneSync is in progress or just completed. Note logs are downloadedfrom the clone target as a single ZIP file. This file is always downloaded to the CM-Console LogFiles folder. Please make careful note of the filename given to the ZIP file, minint-nga82aj inthis example:

Note network connectivity from the CM-Console to the selected target is required forthis option to work.

Use of this option is essential if Cristie Support request the log files to help diagnose cloningissues.

Reboot

Use this option to remotely reboot the selected clone target. This will only be possible if the target isin a re-bootable state and contactable on the network.

Remove System

Use this option to remove the selected target system from the CM-Console Target Systemsdisplay. This is cosmetic only - the machine still exists on the network. Note performing a Refreshoperation will restore the removed system.

117Clone target menu options


Start VNC

Starts a remote VNC server on the selected clone target whilst it's booted into the CloneManager'Live' Environment for Windows. This enables you to connect a suitable VNC client to display andinteract with the remote console screen.

VNC Notes:1. This is a Windows clone feature only.2. The VNC client does not need to be installed on the same host as the CM-Console.3. Cristie do not supply the VNC client.4. Network connectivity from the VNC client and the clone target is required for asuccessful connection.5. Please contact Cristie Support for the server login password.

118


10 Agentless clones

This section describes how to setup a source system for cloning using Cristie Software Ltd.'s Agentless technology. Agentless allows you to clone a source system without the need topermanently install any software on the system to be cloned.

To run an Agentless clone follow this sequence:

1. On the system to be cloned (i.e. the clone source) enable remote administration (see below)

2. Setup the source machine for remote discovery (see below) and run discovery. The sourcemachine now appears as a source machine in the main CM-Console dialogue.

3. Run a normal drag & drop clone sequence. At the end of the sequence the clone sourcemachine will no longer be available for cloning again until another discovery is performed. Infact, under certain conditions, it may disappear from the Clone Source window at the end ofthe clone. If the source is still displayed please remove it by right-click ing and click Removesystem. Once this is done re-run the discovery operation and start the CloneSync.

Enable remote administration

Although Agentless mode requires no software to be permanently installed on the clone sourcemachine, certain components are temporarily pushed to the source machine. For this to workremotely it is important the the clone source machine is enabled for remote administration -assuming this hasn't already been configured.

To do this on Windows 2003 run the following commands directly on the clone source machine:

netsh firewall set service type=remoteadmin mode=enable

netsh firewall set service type = fileandprint mode = ENABLE

The above command can also be used on Windows 2008 or later, however, the command isdeprecated and will generate a warning (it will still work correctly). Microsoft recommend using theadvanced firewall commands on Windows 2008 or later. Run the following commands directly on theclone source machine:

netsh advfirewall firewall set rule group="windows management instrumentation(wmi)" new enable=yes

netsh advfirewall firewall set rule group="remote administration" new enable=yes

netsh advfirewall firewall set rule group="Network Discovery" new enable=Yes

netsh advfirewall firewall set rule group="File and Printer Sharing" newenable=Yes

Note you must be logged in as Administrator to run these commands.

Remote discovery

Once the clone source is configured for remote administration, begin the Agentless clone processby selecting the Edit -> Agentless Discovery Settings from the menu bar (refer to sectionAgentless discovery settings for further detail).

119Agentless clones


This displays the configuration dialogue:

Firstly provide credentials for a local Administrator account that has sufficient privilege to allowremote machines to access a share on the local CM-Console host machine. This account will thenbe used by the Agentless source systems to remotely access the Agentless components on theCM-Console host.

Then add the IP address of all the machines to be cloned in Agentless mode and the credentials ofan Administrator account that will be used to run Agentless components.

Select Discover? to include a machine in the validate or discovery operation. Deselect Discover? toexclude a machine from the validate or discovery process.

Click Validate to check all the credentials supplied. This will be applied to all machines set toDiscover? If the validation run returns success (indicated by an entry "Finished performingAgentless handshake" in the Event Log), then click Discover to begin the discovery process for thespecified hosts. At this point the CM-Console will begin the process of preparing the specified hostmachines for the Agentless clone procedure.

An event will be logged for each successful or failed discovery operation.

Finally, when the discovery process is completes successfully, use the standard drag & dropprocedure to begin the clone or clones.

120


Note: Only Windows source systems are currently supported for Agentless cloning.

121Generating reports


11 Generating reports

Create a migration report using the main menu option File -> Run Migration Report:

This then creates and shows a summary report of all the clone migrations and correspondingstatistics as run by the CM-Console up to the current point in time. An example is shown below:

Note: Any migrations still in progress will be shown with incomplete statistics.

122


12 Cloning a batch

Cloning a batch is very similar to cloning a single machine. Simply drag & drop the batch icon onto asuitable Hypervisor target.

Note1: If very few tokens are available and a clone batch is scheduled containingmachines that have been previously cloned, then the schedule may not run for as manyiterations as expected.

Note2: It is only possible to clone a batch onto a supported Hypervisor target.

123Tailor target VM configuration


13 Tailor target VM configuration

Tailoring a clone target VM means monitoring the run-time behaviour of a clone source system overa period of time to derive optimised values for the target number of CPUs and RAM size.

These optimised values are then used to configure the clone target VM on the selected Hypervisorenvironment.

Note: It is only possible to use tailoring with Hypervisor targets only.

Monitoring a system for tailoring starts automatically and as soon as a source system is discoveredand appears in the CM-Console. No further User input is required.

To run a clone using the tailoring analysis results is a simple matter. Begin a new clone using theusual drag & drop technique. When the Clone Summary dialogue appears click on the TargetConfiguration tab. Enter the clone target information as required and tick Tailor TargetResources.

A warning is displayed if monitoring has not yet run for 24 hours. Click OK. This then displays thecurrent results of the monitoring process.

124


In the example shown analysis has run for a short period of time only and so the suggested CPUcount and RAM size matches that of the source system. Cristie Software Ltd. suggests thatmonitoring is run for at least 24 hours on the source system before attempting the clone to get anaccurate assessment of these values.

Click Yes to accept the recommendation No to reject. Selecting No will result in the clone using thecurrent source values instead.

Select Confirm on the Clone Summary dialogue to start the clone process as normal.

Note 1: It is not currently possible to manually override the tailored CPU and RAM sizevalues.

Note 2: Both the CM-Agent and the CM-Console must be run continuously for 24 hoursotherwise the tailoring period restarts.

Note 3: For clone targets resident on web based clouds such as Azure, AWS EC2 andSoftLayer the created VM CPU and RAM sizes may not correspond exactly with thesuggested tailored values. This is because such environments can only create VMswithin certain bands where the CPU count, RAM size and disk size are fixed and varyaccording to cost.

125Cristie Support


14 Cristie Support

If you have any queries or problems concerning your product, please contact Cristie TechnicalSupport. To assist us in helping with your enquiry, make sure you have the following informationavailable for the person dealing with your call:

CloneManager® Version Number

Installed OS type and version

Any error message information (if appropriate)

Description of when the error occurs

All Cristie log files relating to the source or clone target machine. This is very important to help us

provide a quick diagnosis of your problem

Contact Numbers - Cristie Software (UK) Limited

Technical Support +44 (0) 1453 847 009

Toll-Free US Number 1-866-TEC-CBMR (1-866-832-2267)

Knowledgebase kb.cristie.com

Sales Enquiries [email protected]

Email [email protected]

Web www.cristie.com

Support Hours

05:00 to 17:00 Eastern Standard Time (EST) Monday to Friday

Out-of-Hours support available to customers with a valid Support Agreement - Severity 1 issues* only

UK Bank Holidays** classed as Out-of-Hours - Severity 1 issues only.

*Severity 1 issues are defined as: a production server failure, cannot perform recovery or actual lossof data occurring.**For details on dates of UK Bank Holidays, please see www.cristie.com/support/

Cristie Software Limited are continually expanding their product range in line with the latesttechnologies. Please contact the Cristie Sales Office for the latest product range. Should you havespecific requirements for data storage and backup devices, then Cristie's product specialists canprovide expert advice for a solution to suit your needs.

mailto:[email protected]

http://www.cristie.com

http://www.cristie.com/support/

126


15 Appendices

The following 2 diagrams illustrate how a network must be configured when cloning to a vCloud targetenvironment. In particular it shows which ports need to be opened for each component to allowsuccessful network interoperability during the clone process.

Other target Hypervisor environments will be similar.

127Appendices


15.1 Windows Network Configuration

128


15.2 Linux Network Configuration

129Glossary


16 Glossary

CloneManager Agent (CM-Agent)

Used to allow machines to become 'discoverable' as a clone source to the CM-Console. Install onthe system to be the clone source. It installs the CDS and a small plug-in module.

CloneManager Console (CM-Console)

The CM-Console is available as an optional install to remotely control the complete cloning processacross multiple machines. This component is not essential, but is a useful tool if you want to runconcurrent clone operations and monitor their progress. The console provides the ability to drag anddrop a source machine onto a target machine to initiate a cloning operation.

Cristie Token Manager (CTM)

Used to manage clone and sync tokens. Installs as a service along with the CM-Console or stand-alone on a remote system as required.

Cristie Deployment Service (CDS)Cristie Deployment Service (CDS) must be installed on the host within an enterprise that is to becloned by the CloneManager® product. The installation of this service is accomplished via a localinstall from the CloneManager® installation setup program. It may also be run remotely when usingAgent-less mode.This service provides a communication link with the cloning environment running onthe target machine.

Cristie Recovery ISO Producer (CRISP)

A tool provided by Cristie Software Ltd. to create bootable WinPE 4 based environments from theMicrosoft WADK and a custom fileset (the latter also provided by Cristie Software Ltd.).

Hypervisor

A supported clone target virtual environment such as VMware vCloud™ for example.

LPAR

A Logical Partition on an IBM VIOS host server.

VIOS

IBM Virtual I/O server.

VSS

The Volume Shadow Copy Service provides the backup infrastructure for the Microsoft Windowsoperating systems, as well as a mechanism for creating consistent point-in-time copies of dataknown as shadow copies. CloneManager® makes use of this technology.

Windows Assessment and Deployment Kit (WADK)

A Microsoft tool that allows a WinPE 4 environment to be built. Use in conjunction with CRISP.

WinPE

The Microsoft Windows Pre-installation Environment (Windows PE or WinPE) is a powerfulreplacement for the Microsoft MS-DOS operating system in OS deployment processes, test andtools development and system recovery processes. Windows PE is a minimal Windows system thatprovides limited services based on a Windows Server 2012 kernel. It also provides the minimal set of

130


features required to run Windows Setup, access and install operating systems from the network,script basic repetitive tasks, and validate hardware. In CloneManager® it is used to form the basis ofthe cloning environment. Because of Microsoft licensing restrictions WinPE is not available fordistribution by Cristie Software Ltd., but is freely available for download from Microsoft.

Documents

Cristie CloneManager® 2.2.3 User Guide€¦ · 6 Cristie CloneManager® 2.2.3 User Guide 1 I ntr oduc i CloneManager® enables a live copy (a clone) of a running Microsoft Windows