CloneManager® 3.2 Readme - Cristie Software Agent version 3.2 Linux - Install on the clone source machine (Linux). This

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]

November 2015

Readme

For Windows

Version 3.2

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

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

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

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

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

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

NetWorker and Avamar are trademarks of the EMC Corporation.

Simpana is a trademark of CommVault Inc.

vSphere, vCenter and vCloud are trademarks of VMware Inc.

Hyper-V is a trademark of Microsoft Corporation.

Azure is a trademark of Microsoft Corporation.

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

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

Cristie Management Console (CMC), PC-BaX, UBax, Cristie Connect, Cristie Storage Manager (CSM), SDB, ABMR(Bare Machine Recovery for EMC Avamar), 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 CloneManager® Readme 4

................................................................................................................................... 101.1 3.2

................................................................................................................................... 101.2 3.1

................................................................................................................................... 111.3 2.2.4

................................................................................................................................... 111.4 2.2.3

................................................................................................................................... 121.5 2.2.2

................................................................................................................................... 121.6 2.2

................................................................................................................................... 131.7 2.1.2

................................................................................................................................... 131.8 2.1

................................................................................................................................... 141.9 1.4.3

................................................................................................................................... 151.10 1.4.2

................................................................................................................................... 151.11 1.4

................................................................................................................................... 171.12 1.3.3

................................................................................................................................... 171.13 1.3.2

................................................................................................................................... 181.14 1.3

................................................................................................................................... 181.15 1.2.2

................................................................................................................................... 191.16 1.2

4

CloneManager® 3.2 Readme

1 CloneManager® Readme

Welcome to the Cristie CloneManager® software. This file contains product installationrequirements, a summary of product enhancements, a summary of bug fixes and late breakinginformation. If any statement here conflicts with any information in other documents supplied with theproduct, this should be deemed as the more accurate.

It contains the following sections:

What's new?

Overview

Current Limitations

Requirements

Known Issues

What's new?

Select product version to see what's new:

Version Release Date

3.2 30 November 2015

3.1 28 September 2015

2.2.4 21 August 2015

2.2.3 27 April 2015

2.2.2 6 March 2015

2.2 13 November 2014

2.1.2 30 August 2014

2.1 8 August 2014

1.4.3 8 May 2014

1.4.2 25 April 2014

1.4 21 March 2014

1.3.3 3 October 2013

1.3.2 23 September 2013

1.3 23 August 2013

1.2.2 14 June 2013

1.2 24 May 2013

Overview

Cristie CloneManager® allows customers to create a clone of a running system. CloneManager®provides:

the ability to create a live clone of a running system

the cloned system may be targeted to physical dissimilar hardware

the cloned system may also be targeted at VMware vCenter/vSphere/vCloud, Microsoft Hyper-V/Azure, Amazon Web Services EC2™ or IBM SoftLayer™ virtual machine environments(Hypervisor or cloud).

5CloneManager® Readme


a cloned 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 bootingthe clone into operational mode. This process is called CloneSync.

The product comprises a suite of components:

CloneManager Agent version 3.2 Windows - Install on the clone source machine (Windows).This allows the CloneManager "Live" Environment for Windows to communicate with the sourcemachine.

CloneManager Agent version 3.2 Linux - Install on the clone source machine (Linux). Thisallows the CloneManager "Live" Environment for Linux to communicate with the source machine.

CloneManager Console version 3.2 Windows - Install on any suitable host machine. Used tomanage and report progress of all clone operations (both Windows and Linux). Fulldocumentation is installed with this component.

Cristie Token Manager 3.2 Windows - Install on any suitable host machine. Used to managethe licensing and consumption of clone/sync tokens for all clone operations (both Windows andLinux). Normally installed on the same machine as the CM-Console host, but may be installedon a separate host if required.

Cristie ISO Producer (CRISP) version 7.3.1 Windows - Install on any suitable Windows hostmachine. A tool used to create the bootable WinPE5 based CloneManager "Live" Environmentfor Windows in conjunction with the CloneManager® fileset below.

CRISP WinPE5 Fileset for CloneManager® version 3.2 Windows - Install on the samemachine as CRISP above. Used in conjunction with CRISP to create the CloneManager "Live"Environment for Windows ISO. After creation of the ISO boot this image on any suitableWindows host target machine or upload to a supported Hypervisor environment.

CloneManager "Live" Environment for Linux version 3.2 - Boot this image on any suitableLinux host target machine or upload to a supported Hypervisor environment. This is provided pre-built.

Cristie Software Ltd. will upload the CloneManager "Live" Environment for Windows and theCloneManager "Live" Environment for Linux directly to Microsoft Azure™ prior to release.

On Windows all of the above components can be selectively installed from a single suite installerpackage. On Linux a dual purpose ISO provides both the Agent installation and the bootableCloneManager "Live" Environment for Linux.

Current limitations

i) Windows XP is not supported (in both 32 or 64-bit forms) for cloning or hosting any of theCloneManager® components.

ii) Windows Desktop systems (i.e. Windows Vista, Win7, Win8 or Win8.1 in both 32 and 64-bitforms) are not supported for cloning.

iii)Agentless mode is only supported on Windows and Linux source systems.

iv) On Windows 2003 the OS must be installed to an NTFS partition. Windows 2003 installed toa FAT or FAT32 partition cannot be cloned. This is because CloneManager® needs toquiesce the OS partition (i.e. take a consistent snapshot). This is not possible on FAT orFAT32.

v) The target machine must have sufficient disks and be of a sufficient size to accommodate theselected clone disk configuration. If a target disk is of a different size to the corresponding

6


disk on the source, then it must be at least big enough to accommodate the original total filesize in use. If not the clone will fail.

vi) On Windows it is not possible to selectively restore volumes from disks created in Microsoft'dynamic' format. So, for example, you cannot deselect individual elements of a mirror - allmust be cloned together. Any dynamic disks de-selected during the clone will still beformatted, but the contents will not be transferred to the clone.

vii)On Red Hat Enterprise Linux version 4.x, ACL's are not copied by default to the clone target.

viii) Hosting the CloneManager Console on a Linux platform is not currently supported.

ix) Hosting the CloneManager Console on a Windows 'Core' type OS is not currently supported.

x) On Windows, partitions mounted on folders are not currently supported.

xi) Currently it is not possible to clone folders containing a mix of encrypted and non-encryptedfiles. Only the encrypted files will be copied.

xii) This release does not support cloning direct from the either the CloneManager "Live"Environment for Windows or CloneManager "Live" Environment for Linux. The CM-Consolemust always be used to start and manage clone operations.

xiii) The cloned system (Windows or Linux) may show minor differences in file system sizes andspace as compared to the original.

xiv) A CloneSync operation will only modify files and not disk structures. So, for example, anynew disks added since the clone operation will not be replicated to the target.

xv) Although multiple VMware vClouds can be defined only one vCloud organisation on each canbe configured at any one time. Attempts to define a new organisation on the same vCloud willreplace an existing definition.

xvi) On Windows 2012 or later any changes to a local User profile are not saved until a User logsout. Such changes are not therefore detected by the CM-Agent during sync operations.Therefore the User must log out of the source system before starting the sync.

xvii) It is no longer possible to order VM templates for Windows 2003 on IBM SoftLayer™.Therefore CloneManager® no longer supports Windows 2003 on IBM SoftLayer™ cloudtargets.

xviii) Agentless clones of Windows 2003 x86 and x64 are not supported to any targetenvironment.

xix) Agentless clones to IBM SoftLayer are not supported in this release.

xx) The conversion of split boot (i.e. those with separate boot and system partitions) EFI basedsystems to MBR form is only supported for Windows 2008R2 or later.

xxi) Cloning of a split boot system across multiple disks to a Microsoft Hyper-V™ target is notsupported for any OS.

xxii) Hostname and IP address change support is for Linux is restricted to RHEL/Centos 6.x/7and SuSE 11 SP3/SP4. Both 32 and 64-bit versions are supported.

Requirements

i) Supports clones of either Windows Server 2003, Server 2008, Server 2008 R2, Server 2012 orServer 2012 R2 (excluding Core) both 32 and 64-bit versions where appropriate. NoteWindows XP is specifically not supported (x86 or x64) in this release. Some Hypervisor targetenvironments only support a subset of this list. This is highlighted below.



ii) Linux distributions supported are: Red Hat Enterprise Linux (RHEL)/Centos 4, 5, 6 and 7 (withexceptions), SuSE Linux Enterprise Server (SLES) 10 and 11. Both 32 and 64-bit versions aresupported where appropriate. Some Hypervisor target environments only support a subset ofthis list. This is highlighted below. For certain RHEL/Centos/Hyper-V clone support theMicrosoft Linux Integration Services must be installed prior to starting the clone process.Refer to the OS Support Matrix section below for exact details.

iii)For Linux "rsync" must be installed prior to the installation of CloneManager®.

iv) The CM-Console program requires Oracle JRE for Windows version 1.7 or later to be installed(either 32- or 64-bit version). The JRE will be automatically installed if not detected.

v) The CM-Console is not supported on Windows Core OS's.

vi) Cloning of Windows Core OS's (i.e. Server 2008 x86/x64, Server 2008 R2, Server 2012 andServer 2012 R2) is not supported.

vii) Supports VMware vSphere™ version 5.1 and 5.5.

viii) Supports VMware vCloud™ versions 5.1 to 5.7.

ix) Supports Microsoft Hyper-V™ installed on Server 2008, 2008 R2, 2012 and 2012 R2versions.

x) Supports Microsoft Azure™ as available to end users in November 2015 and later.CloneManager® only supports the cloning of Windows 2008, 2008 R2, 2012 and 2012 R2 (all32/64-bit versions where applicable) to Azure. Windows 2003 is specifically excluded.

xi) Supports the cloning of Linux RHEL/Centos 6.4/6.5 x86/x64 and SLES 11 SP3/SP4 x64 onlyto Microsoft Azure™. Note only systems that are booted from the first disk are supported.

xii) On Windows about 11MB of free disk space is required to install the CloneManager® Agenton the source system to be cloned. If installed, the Windows CRISP package requires13MBplus a further 380MB for the CloneManager® fileset (required to generate the CloneManager"Live" Environment for Windows).

xiii) On Windows about 110MB of free disk space is required to install the CloneManager®Console plus a further 5MB to install the Token Manager.

xiv) On Linux about 3MB of free disk space is required to install the CloneManager® Agent onthe Linux source system to be cloned.

xv) A minimum of 2GB of RAM is required to run the CloneManager® components on the clonesource system; On Windows at least 2GB of RAM is required to boot and run the WinPE5based CloneManager "Live" Environment for Windows on the clone target system.

Similarly at least 1GB of RAM is required to boot and run the based CloneManager "Live"Environment for Linux on the clone target system.

xvi) Requires local administrator (Windows) or root (Linux) privilege to install and run. This ischecked during installation.

Known Issues

i) When cloning to dissimilar hardware in Windows you may need to enter a path to new driverfiles to support new Mass Storage or Network devices. If this is the case you will need toenter the same path during a CloneSync operation otherwise the new drivers will be removed.

ii) On Windows Vista/2008 or later OS's please ensure that User Account Control (UAC) is setto the default setting and no higher, otherwise it will not be possible to start the cloningprocess.

8


iii)On rare occasions the Windows OS may create the pagefile on a different disk to the sourcemachine.

iv) During a clone or sync sequence you must use an account which is a member of the localAdministrators group of the source machine.

v) For UAC enabled systems only: remote access restrictions will be temporarily removedduring the clone or sync operation. If you are concerned about this, refer to the relevant CristieKnowledgebase article or contact Cristie support.

vi) Clones may fail on Windows 2008 R2 when compression is enabled. Please do not enablecompression on this OS.

vii) To allow the discovery of SuSE 11 SP3/SP4 systems in the CM-Console, please configurethe IP tables to allow multicast or alternatively disable the firewall on the source for theduration of the clone operation.

xxiii) When cloning to Microsoft Azure™ the CM-Console will occasionally report incorrectly aclone as ‘failed’ if the IP assigned to the target uses an IP that had been allocated to aprevious clone target.

xxiv) When cloning a Windows system to a Microsoft Hyper-V™ target environment it is notpossible to remotely re-boot the clone target from the CM-Console. Please use the MicrosoftHyper-V™ Management Console instead to reboot.

xxv) When cloning Windows 2008 x86 and x64 systems to IBM SoftLayer™ you may beprompted to install a new SCSI driver when the cloned system is rebooted. At the momentthis driver must must located and installed by the customer. This issue will be addressed in alater release of CloneManager®.



OS Support Matrix

The following table summarises OS clone support in CloneManager® for each of the targetHypervisor environments.

Windows 2003x86/x64

2008x86/x64

2008 R2x64

2012 x64 2012 R2x64

vCloud (PE4only)

(PE4only)

(PE4only)

(PE4only)

(PE5only)

vSphere (PE4only)

(PE4only)

(PE4only)

(PE4only)

(PE5only)

Hyper-V (PE4only)

(PE4only)

(PE4only)

(PE4only)

(PE5only)

Azure (PE4only)

(PE4only)

(PE4only)

(PE5only)

AWS (PE4only)

(PE4only)

(PE4only)

(PE4only)

(PE5only)

SoftLayer

(PE4only)

(PE4only)

(PE4only)

(PE4only)

(PE5only)

Linux RHEL 4.x x86/

x64

RHEL 5.x x86/

x64

RHEL6.0 to

6.3 x86/x64

RHEL6.4 to

6.6 x86/x64

RHEL7.0 x86/

x64

SLES10 x86/

x64

SLES 11x86/x64

vCloud

vSphere

Hyper-V LIS LIS (SP3x64 only)

Azure (SP3x64 only)

AWS Contact

Cristie

SoftLayer

Contact

Cristie

AIX 5.3 6.1 7.1

VIOS

- supported configuration - unsupported configuration

LIS - requires Linux Integration Services (LIS) 3.5 for Hyper-V to be installed on the sourceprior to starting the clone

10


1.1 3.2

Enhancements

i) Added a rental licensing schema for Hot Standby CloneSync operations.

ii) Now supports VMware vCloud™ up to 5.7.

iii)Now supports btfs file systems for Linux clones (with CloneManager "Live" Environment forLinux version 3.2 and later).

iv) A change to a source system configuration (i.e. adding a new disk volume or disk) is nowdetected prior to a CloneSync operation and the User is warned via email (an email recipientmust be configured for this to work) and an event log entry.

v) The CloneManager "Live" Environment for Windows now supports EFI(GPT) to BIOS(MBR)and BIOS to EFI boot conversion.

vi) The Windows PE4 based Live environment is no longer required and has been removed fromthe product distribution.

vii) The suite installer now checks for the installed service pack level and disallows installs onWindows OS's without the required minimum service pack.

viii) The CloneManager "Live" Environment for Windows and CloneManager "Live" Environmentfor Linux recovery images are now automatically uploaded to supported cloud environmentsdirect from Cristie Software Ltd..

ix)All CloneManager® installers and file components are now digitally signed with a SHA-256based digital certificate.

x) The End User License has been amended to cover rental licenses.

xi) Documentation updated for this release.

Bug Fixes

i) None.

1.2 3.1

Enhancements

i) Added a new Hot Standby mode of operation.

ii) CloneManager® now supports Agentless discovery for Linux source systems.

iii)The Linux CM-Agent and CloneManager "Live" Environment for Linux have been upgraded toversion 3.1.

iv) Clones to IBM SoftLayer™ now support up to 5 disks.

v) CloneSync operations no longer consume a token if the sync fails.

vi) Enhanced the clone retry mechanism if outages are encountered during a clone.

vii)Documentation updated for this release.



Bug Fixes

i) Windows 'Core' servers are now identified as such in the CM-Console clone source and targetsystem viewing panels.

ii) Occasionally booting a system after multiple consecutive clones would report "Missing OS".This is now fixed.

iii)Using incorrect access credentials or if other run-time errors occured during Agentlessdiscovery, then this caused persistent clone errors. This is now fixed.

iv) Corrected date on footer of Migration Reports to 2015.

1.3 2.2.4

Enhancements

i) Added support for VMware vCloud Air™ cloud targets.

ii) Improved compatibility with IBM SoftLayer™ cloud targets.

iii)Microsoft Security Update KB2918614 (issued August 2014) no longer prevents the

CloneManager® Agent, the CM-Console and the Cristie Token Manager from upgrading(mostly observed on Windows 2003).

iv) Documentation updated for this release.

Bug Fixes

None.

1.4 2.2.3

Enhancements

i) Updated the Java Runtime Environment (JRE) to version 1.8.0_25 for the CM-Console. Thiswill be automatically installed if not detected.

ii) Documentation updated for this release.

Bug Fixes

i) In certain scenarios Agentless clones could fail. This has been fixed and Agentless clonesare now fully working.

ii) An occasional timeout was reported when the CM-Console attempted to contact a locallyinstalled Cristie Token Manager. This has now been fixed.

12


1.5 2.2.2

Enhancements

i) Support for cloning Windows 2012 R2 (in both Core and non-Core forms) has been added. Toachieve this a new version of the CloneManager "Live" Environment for Windows has beenadded based upon WinPE5. The WinPE4 version is still provided however for use with all OS'sprior to Windows 2012 R2.

ii) Support for RHEL/Centos 6.6 and 7.0 has been added (refer to exceptions in the OS SupportMatrix).

iii)Added support for VMware vCenter™ and VMware vCloud™ version 5.5.

iv) Added support in the CloneManager "Live" Environment for Linux for using Hostnames insteadof IP addresses for the clone source and the Cristie Token Manager (CTM).

v) Added support in the CloneManager "Live" Environment for Linux to set the CTM from thecurses interface.

vi) It is now possible to schedule Agentless clones and syncs with this release.

vii) Documentation updated for this release.

Bug Fixes

i) The CM-Agent component CDS created unnecessary internal socket connections. This hasnow been fixed.

1.6 2.2

Enhancements

i) Amazon Web Services EC2™ support has been added as a target virtual environment (cloud)for Windows/Linux systems.

ii) IBM SoftLayer™ support has been added as a target virtual environment (cloud) for Windows/Linux systems.

iii) Security enhancements have been made within the Windows/Linux cloning environment toprevent unauthorised access.

iv) RDP is automatically enabled in clones to Microsoft Azure™ and Amazon Web ServicesEC2™. This enables access to cloned machines where it is not possible to access via aproduct console.

v) Added a feature which activates a remote VNC connection on a Windows clone target whilstbooted into the CloneManager "Live" Environment for Windows.

vi) The Cristie Token Manager (CTM) uses port 80 for communication with other parts ofCloneManager®. The installation of CTM sometimes failed because port 80 was already inuse by a third party program. The installation now detects that port 80 is in use, displays awarning and disables the CTM install option in the setup program.

vii) Improved the reliability of the attach/detach mechanism in Microsoft Azure™.

viii) Install of the CM-Console on Windows Core type OS's is now actively disabled. A warningmessage is displayed.



ix) The Java version used in the CloneManager "Live" Environment for Linux environment hasbeen updated.

x) Added Swedish keyboard support to the CloneManager "Live" Environment for Linuxenvironment when used directly.

xi) Updated the Broadcom bnx2x NIC driver for Linux clone targets.

xii) Documentation updated for this release.

Bug Fixes

i) Linux clones now continue if rsync error 23 is detected when copying '/dev'. This errorstopped the clone before.

ii) Fixed a problem with '/dev/vd*' disk mapping on Linux clone targets.

iii)Fixed a bug with user defined paths (e.g. for log files and driver injection) containing spacecharacters for Linux clone targets.

iv) Fixed the problem where a maximum of 16 disks only could be cloned to vCloud.

v) Fixed a problem where a CloneSync operation would not actually ignore any disks tagged toignore.

vi) Fixed URL to Cristie Knowledgebase in CM-Console 'About' page.

1.7 2.1.2

Enhancements

None.

Bug Fixes

i) Fixed a problem where the detachment of VMs in the Azure cloud would fail for Linuxsystems only.

1.8 2.1

Enhancements

i) Microsoft Azure support has been added as a target virtual environment (cloud) for Windows/Linux systems.

ii) On a Linux clone it is now possible to change either the hostname or a static IP addressduring the clone process.

iii) It is now possible to retrieve the log files from a clone target machine at any point during theclone/sync operation. Cristie Support may request use of this feature when diagnosing cloneissues.

iv) It is now possible to gather all the CM-Console log files into a single ZIP file from a single"Export Console Logs" option. Cristie Support may request use of this feature whendiagnosing clone issues.

14


v) Now detects pending reboot states during the installation of the CM-Agent and allows theinstallation to be optionally cancelled to allow a reboot.

vi) Before a CloneSync is performed Chkdsk is now automatically run against all the disks tocheck for potential disk errors.

vii) Documentation updated for this release.

Bug Fixes

i) Fixed a problem where enabling compression during a Windows clone caused the clonetarget Live environment to crash. This is now fixed except for Windows 2008 R2. Please donot enable compression for that OS.

ii) Fixed an issue whereby a silent install using the suite setup program displayed an upgradewarning message if a previous installation was found. This is now fixed and a fully silentupgrade will be performed by default in this case.

iii)Events are now permanently recorded, so if the CM-Console is closed and restarted historicalevents will be displayed.

iv) A drive marked as the boot drive is given the 'A:' drive letter by the configuration program onthe source machine. Because A: is ignored in the recovery environment the recovery/cloneusing this configuration fails because it cannot assign a drive letter to the boot partition. Thisis now fixed.

v) Amount of RAM in Target VM does not match the original machine. This was observed inseveral Windows and Linux clones with larger amounts of RAM (> 12GB). This is nowcorrected.

vi) The message "TGT Disk 1 must be repartitoned" even though disk is de-selected in the CloneSummary dialogue. This occurs if the target has the same or more disks than the source, andyou try to deselect one or more of the source disks. If the target has less disks than thetarget, the deselect option works. If you don't, it incorrectly warns you to check the diskconfiguration before proceeding. This is now corrected.

vii)When running the suite installation in silent mode, the upgrade warning dialogue is stilldisplayed. This is now suppressed.

viii) CM-Agent install was allowed on Windows 2012 R2 even though it is not supported. This isnow detected and a suitable warning message is displayed.

ix) When using the IP Range settings option in the Clone Summary dialogue to set a static IPaddress for a booted target, the target was not detected. This is now corrected.

1.9 1.4.3

Enhancements

i) The Event Log now shows the remaining time to complete the clone - note there are manyfactors that affect this value (e.g. network bandwidth) and it will change during the clone orCloneSync process; it will, however, become more accurate as more files are copied to thetarget.

Bug Fixes

ii) Sometimes an Agentless CloneSync would fail with "Error: failed to initialise the disk



management service" displayed in the CM-Console. This is now fixed.

iii)Where the CM-Console and CloneManager "Live" Environment for Windows or CloneManager"Live" Environment for Linux are configured to operate in different timezones then the averagedata throughput shown in the CM-Console Event Log was displayed as a negative number.This is now fixed.

iv) Sometimes more CloneSyncs were being executed than had been scheduled. This is nowfixed.

v) Documentation updated for this release.

1.10 1.4.2

Enhancements

i) Added 'Agentless' support for Microsoft Windows server OS's.

Bug Fixes

None.

1.11 1.4

Enhancements

i) Added clone support for Microsoft Windows 2012 (including Core versions) on all supportedHypervisors.

ii) Added support for batched cloning.

iii) Added support for scheduled cloning.

iv) Added support for event email notifications.

v) Added support for toggling event log notifications.

vi) Added support for "tailoring" target Hypervisor VM's.

vii) Enhanced clone progress monitoring to show percentage, files done/total files, bytes done/total bytes and the average observed throughput.

viii) "Advanced options" (transport configuration) is now provided and can be enabled from theCloneManager Console.

ix) Improved the file transfer time of a clone.

x) Removed the internal token manager in favour of 'Cristie Token Manager as a service' nowinstalled separately.

xi) The vCloud VM "Computer Name" is now saved and synced to that of the original sourcemachine's hostname.

xii) Settings persistence has been enhanced to use an internal SQL-Lite database instead of aflat XML file.

xiii) When syncing a system, the original source machine is now automatically restored from thesettings database

16


xiv) When syncing/cloning a system that has been synced/cloned before, the credentials for thesource are now automatically restored from the settings database.

xv) Event logs now persist across sessions of the CloneManager Console.

xvi) Debug tracing can now be enabled from the CloneManager Console.

xvii) Tracing for all independent modules can now be modified from the CloneManager Console.

xviii) Added support for Microsoft Hyper-V 2008, 2008R2, 2012 and 2012R2 based Hypervisortarget environments.

xix) Removed automatic deletion of systems from the CloneManager Console GUI - this is nowuser initiated.

xx) Simplified the Hypervisor discovery mechanism.

xxi) Multiple concurrent Hypervisor discoveries are now possible.

xxii) Improved the performance of the retrieval of disk information from source and targetsystems.

xxiii) Added further validation around incompatible disk configurations between source andtarget.

xxiv) Added support for "refreshing" a target Hypervisor after it has been defined to 'say' pick upnew ISO's.

xxv) Enhanced the reporting of clone and sync operations.

xxvi) Added backwards compatibility, the console will now recognise 1.3.3 clients separatelyfrom 1.4.1 clients and act appropriately.

xxvii) Added support for saving all information about a clone (source system details, targetsystem details, clone configuration, clone metrics etc.).

xxviii) Improved the performance of the clone validation procedure.

Bug Fixes

i) Fixed various logging issues.

ii) Fixed an issue where ignoring disks would cause the wrong disk to be ignored in the recoveryenvironment.

iii)Fixed various issues surrounding CTMs not being available or not being connected.

iv) Fixed an error where sorting by date in the event log wasn't sorting correctly.

v) Fixed an error where multiple selected networks weren't being attached to new vAppscorrectly.

vi) Fixed an error with IP validations in the Clone Summary dialogue.

vii) Fixed an issue where source and target systems with multiple NICs would attempt tocommunicate using the wrong IP addresses.

viii) Fixed an issue where every NIC created in a vSphere clone would be called "NetworkAdapter 1".

ix)Fixed an issue where an incorrect DNS server would be shown for a particular NIC in thenetwork settings display in the Clone Summary dialogue.

x) Fixed an issue where an error associated with failure to connect to a CTM would be shownmultiple times.



xi) Fixed an issue where an incorrect CTM endpoint would be sent to a source system.

xii) Fixed an issue where NFSv4 shares weren't being excluded from the list of displayedfilesystems for Linux source systems.

xiii) Fixed an issue where the wrong event might be updated in some situations.

xiv) Fixed an issue where the source system would show "Preparing system for cloning" whenundergoing a sync operation.

xv) Fixed an issue where a sync would have the wrong event type.

xvi) Fixed an issue where cloning/syncing very large systems would cause the clone/sync tostall beyond the 72 hour timeout window.

xvii) Fixed an issue where files would be created but never populated with data.

xviii) Fixed an issue where a clone operation retry wouldn't populate incomplete files.

xix) Fixed an issue where compressed files would be uncompressed on the target system.

xx) Fixed an issue where sparse files would not be sparse on the target system.

xxi) Fixed an issue where the retry mechanism would trigger a failure at the end of the clone/sync even when it was successful.

xxii) Fixed an issue where the database not being detached at the end of a clone/sync whichwould cause the whole operation to fail.

xxiii) Fixed an issue where a very quick sync would cause the WinPE5 Live environment tocrash.

1.12 1.3.3

Enhancements

None.

Bug Fixes - CloneManager Console Only

(i) In Windows corrected a problem where, in a group of source disks, one or more disks weredeselected for cloning in the middle of the group. The effect of this was to create disks on thetarget with incorrect sizes.

(ii) In Windows now supports disks greater than 1 TB in size when cloning.

(iii) Now correctly configures Windows clones with more than 1 Network Interface (NIC).

1.13 1.3.2

Enhancements

None.

18


Bug Fixes

(i) The disk drive mapping mechanism in the CloneManager Console has been corrected so thatvirtual targets are created with the correct number of drives, and mapped correctly. This is tofix a problem where disks on the source were deselected for the clone operation resulting indisk allocation errors.

1.14 1.3

Enhancements

(i) Now allows any User account with local Administrator credentials to both install and run cloneoperations.

(ii) Now allows the vCloud Live environment to boot with an IP address obtained from eitherDHCP, static or selected from a pre-defined pool attached to a virtual network interface.

(iii) Now prompts for a new vApp name when attempting a clone if one with the same alreadyexists on a target vCloud server.

(iv)Enhanced the CM-Console to provide clarification as to whether a machine is undergoing a"sync" or "clone" operation.

(v) Updated documentation particularly with respect to "Licensing" and the Cristie TokenManager. Licensing now requires the use of a machine signature rather than the hostname.

(vi) Enhanced the validation of License/Token activation codes in the Token Manager.

(vii) Minor improvements to Token Manager error handling.

Bug Fixes

(i) It was possible to sync a clone to itself. This is no longer possible.

(ii) Upgrading the CM-Agent 1.2 to 1.2.2 on Windows 2003 x86 or x64 caused the machine toreboot. This has now been fixed.

(iii) Upgrading the CloneManager PE5 Fileset 1.2 to 1.2.2 on Windows 2003 x86 or x64 andwhen run with CRISP resulted in an ISO that when booted showed incorrect fonts. This hasnow been fixed.

iv) It is now possible to clone a Windows or Linux system with 8 or more disks to targets onVMware vSphere.

1.15 1.2.2

Enhancements

(i) Enhanced the CM-Console to provide clarification as to whether a machine is undergoing a"sync" or "clone" operation.

(ii) General enhancement to speed up detection of machines in enterprise environments.

(iii) Enhancement made to provide specifically named datastore folders for new VMs whencloning to VMware vSphere targets.



(iv) Enhanced error reporting for license token issues.

(v) Settings changed in the CM-Console are now saved immediately rather than when theprogram exits.

Bug Fixes

(i) None.

1.16 1.2

Enhancements

First release.

Bug Fixes

First release.

Documents

CloneManager® 3.2 Readme - Cristie Software Agent version 3.2 Linux - Install on the clone source machine (Linux). This