Readme. For Windows. August Version Cristie Data Products GmbH Nordring 53-55

Transcription

1 Readme For Windows August 2014 Version Cristie Software Ltd. New Mill Chestnut Lane Stroud GL5 3EH United Kingdom Tel:+44(0) Fax:+44(0) Cristie Data Products GmbH Nordring Cristie Nordic AB Gamla Värmdövägen Niedernberg Germany Tel: +49 (0) 60 28/ Fax: +49 (0) 60 28/ cbmr@cristie.de SE Nacka Sweden Tel:+46(0) Fax:+46(0) cbmr@cristie.se

2 Copyright Cristie Software Ltd. All rights reserved. The software contains proprietary information of Cristie Software Ltd.; it is provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited. Due to continued product development this information may change without notice. The information and intellectual property contained herein is confidential between Cristie Software Ltd. and the client and remains the exclusive property 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 any means, electronic, mechanical, photocopying, recording or otherwise without the prior written permission of Cristie Software 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. Cristie Software Ltd New Mill Chestnut Lane Stroud GL5 3EH UK Tel: +44 (0) cbmr@cristie.com Website:

3 Contents 3 Contents 1 CloneManager Readme Copyright Cristie Software Ltd.

4 4 1 CloneManager Readme Welcome to the Cristie CloneManager software. This file contains product installation requirements, a summary of product enhancements, a summary of bug fixes and late breaking information. If any statement here conflicts with any information in other documents supplied with the product, 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 August August May April March October September August June 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, Hyper-V or Azure virtual machine environments (Hypervisor or cloud). a cloned target system maybe also used in warm standby mode. This is where a short synchronisation process is run to bring a previously cloned system up-to-date prior to booting the clone into operational mode. This process is called CloneSync. The product comprises a suite of components: CloneManager Agent version 2.1 Windows - Install on the clone source machine (Windows). CloneManager 2.1 Readme

5 CloneManager Readme 5 This allows the CloneManager "Live" Environment for Windows to communicate with the source machine. CloneManager Agent version 2.1 Linux - Install on the clone source machine (Linux). This allows the CloneManager "Live" Environment for Linux to communicate with the source machine. CloneManager Console version Windows - Install on any suitable host machine. Used to manage and report progress of all clone operations (both Windows and Linux). Full documentation is installed with this component. Cristie Token Manager 2.1 Windows - Install on any suitable host machine. Used to manage the licensing and consumption of clone/sync tok ens for all clone operations (both Windows and Linux). Normally installed on the same machine as the CM-Console host, but may be installed on a separate host if required. Cristie ISO Producer (CRISP) version Windows - Install on any suitable Windows host machine. A tool used to create the bootable WinPE 4 based CloneManager "Live" Environment for Windows in conjunction with the CloneManager fileset below. CRISP WinPE 4 Fileset for CloneManager version Windows - Install on the same machine 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 suitable Windows host target machine or upload to a supported Hypervisor environment. CloneManager "Live" Environment for Linux version Boot this image on any suitable Linux host target machine or upload to a supported Hypervisor environment. This is provided prebuilt. Cristie Software Ltd. will upload the CloneManager "Live" Environment for Windows and the CloneManager "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 installer package. On Linux a dual purpose ISO provides both the Agent installation and the bootable CloneManager "Live" Environment for Linux. Current limitations i) Windows XP is not supported (x86 or x64). ii) Agentless mode is only supported on Windows source systems - not Linux. iii) On Windows 2003 the OS must be installed to an NTFS partition. Windows 2003 installed to a FAT or FAT32 partition cannot be cloned. This is because CloneManager needs to quiesce the OS partition (i.e. take a consistent snapshot). This is not possible on FAT or FAT32. iv) The target machine must have sufficient disks and be of a sufficient size to accommodate the selected clone disk configuration. If a target disk is of a different size to the corresponding disk on the source, then it must be at least big enough to accommodate the original total file size in use. If not the clone will fail. v) 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 - all must be cloned together. Any dynamic disks de-selected during the clone will still be formatted, but the contents will not be transferred to the clone. vi) On Red Hat Enterprise Linux version 4.x, ACL's are not copied by default to the clone target. vii) Hosting the CloneManager Console on a Linux platform is not currently supported. viii) Hosting the CloneManager Console on a Windows 'Core' type OS is not currently supported. Copyright Cristie Software Ltd.

6 6 ix) On Windows, partitions mounted on folders are not currently supported. x) Currently it is not possible to clone folders containing a mix of encrypted and non-encrypted files. Only the encrypted files will be copied. xi) This release does not support cloning direct from the either the CloneManager "Live" Environment for Windows or CloneManager "Live" Environment for Linux. The CM-Console must always be used to start and manage clone operations. xii) The cloned system (Windows or Linux) may show minor differences in file system sizes and space as compared to the original. xiii) A clone sync operation will only modify files and not disk structures. So, for example, any new disks added since the clone operation will not be replicated to the target. xiv) Although multiple vclouds can be defined only 1 vcloud organisation on each can be configured at any one time. Attempts to define a new organisation on the same vcloud will replace an existing definition. xv) On Windows 2012 (only) any changes to a local User profile are not saved until a User logs out. 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. xvi) It is not possible to schedule Agentless clones with this release. xvii) Hostname and IP address change support is for Linux is restricted to RHEL/Centos 6.x and SuSE 11 SP3. Both 32 and 64-bit versions are supported. Requirements i) Supports clones of either Windows Vista, 7, 8, Server 2003, Server 2008, Server 2008 R2 or Server 2012 (including Core) both 32 and 64-bit versions where appropriate. Note Windows XP, Windows 8.1 and Server 2012 R2 are specifically not supported (x86 or x64) in this release. Some Hypervisor target environments only support a subset of this list. This is highlighted below. ii) Linux distributions supported are: Red Hat Enterprise Linux (RHEL)/Centos 4, 5 and 6, SuSE Linux Enterprise Server (SLES) 10 and 11. Both 32 and 64-bit versions are supported where appropriate. Some Hypervisor target environments only support a subset of this list. This is highlighted below. For certain RHEL/Centos/Hyper-V clone support the Microsoft 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) Supports VMware vsphere version 5 and later. vii) Supports VMware vcloud versions 1.5 and 5.1. viii) Supports Microsoft Hyper-V installed on Server 2008, 2008 R2, 2012 and 2012 R2 versions. ix) Supports Microsoft Azure as available to end users in August 2014 and later. CloneManager only supports the cloning of Windows 2008, 2008 R2 and 2012 (all 32/64-bit and Core versions where applicable) to Azure. Windows 2003 is specifically excluded. x) Supports the cloning of Linux RHEL/Centos 6.4/6.5 x86/x64 and SLES 11 SP3 x64 only to Azure. Note only systems that are booted from the first disk are supported. CloneManager 2.1 Readme

7 CloneManager Readme 7 xi) On Windows about 9MB of free disk space is required to install the CloneManager Agent on the source system to be cloned. If installed, the Windows CRISP package requires11mb plus a further 250MB for the CloneManager fileset (required to generate the CloneManager "Live" Environment for Windows). xii) On Linux about 3MB of free disk space is required to install the CloneManager Agent on the Linux source system to be cloned. xiii) A minimum of 1GB of RAM is required to run the CloneManager components on the clone source system; 2GB is recommended. On Windows at least 2GB of RAM is required to boot and run the WinPE 4 based 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. xiv) Requires local administrator (Windows) or root (Linux) privilege to install and run. This is checked during installation. Known Issues i) When cloning to dissimilar hardware in Windows you may need to enter a path to new driver files to support new Mass Storage or Network devices. If this is the case you will need to enter 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 set to the default setting and no higher, otherwise it will not be possible to start the cloning process. iii) On rare occasions the Windows OS may create the pagefile on a different disk to the source machine. iv) During a clone or sync sequence you must use an account which is a member of the local Administrators group of the source machine. v) For UAC enabled systems only: remote access restrictions will be temporarily removed during the clone or sync operation. If you are concerned about this, refer to the relevant Cristie Knowledgebase article or contact Cristie support. vi) Clones may fail on Windows 2008 R2 when compression is enabled. Please do not enable compression on this OS. vii) To allow the discovery of SuSE 11 SP3 systems in the CM-Console, please configure the IP tables to allow multicast or alternatively disable the firewall on the source for the duration of the clone operation. xviii) When cloning to Azure the CM-Console will occasionally report incorrectly a clone as failed if the IP assigned to the target uses an IP that had been allocated to a previous clone target. Copyright Cristie Software Ltd.

8 8 OS Support Matrix The following table summarises OS clone support in CloneManager for each of the target Hypervisor environments. Windows 2003 x86/ 2008 x86/ 2008 R x86/ x64 x64 x64 x R2 x64 vcloud vsphere Hyper-V Azure Linux RHEL 4.x RHEL 5.x RHEL RHEL 6.4 SLES 10 x86/x64 x86/x to 6.3 to 6.5 x86/x64 x86/ x64 x86/x64 SLES 11 x86/x64 vcloud vsphere Hyper-V LIS LIS Azure AIX (SP3 x64 only) (SP3 x64 only) VIOS - supported configuration - unsupported configuration LIS - requires Linux Integration Services (LIS) 3.5 for Hyper-V to be installed on the source prior to starting the clone CloneManager 2.1 Readme

9 CloneManager Readme None. i) Fixed a problem where the detachment of VMs in the Azure cloud would fail for Linux systems only 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 address during the clone process. iii) It is now possible to retrieve the log files from a clone target machine at any point during the clone/sync operation. Cristie Support may request use of this feature when diagnosing clone issues. 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 when diagnosing clone issues. v) Now detects pending reboot states during the installation of the CM-Agent and allows the installation to be optionally cancelled to allow a reboot. vi) Before a CloneSync is performed Chkdsk is now automatically run against all the disks to check for potential disk errors. vii)it is now possible to change the IP and/or the system hostname for supported Linux clones. viii) Documentation updated for this release. i) Fixed a problem where enabling compression during a Windows clone caused the clone target Live environment to crash. This is now fixed except for Windows 2008 R2. Please do not enable compression for that OS. ii) Fixed an issue whereby a silent install using the suite setup program displayed an upgrade warning message if a previous installation was found. This is now fixed and a fully silent upgrade will be performed by default in this case. iii) Events are now permanently recorded, so if the CM-Console is closed and restarted historical events will be displayed. iv) A drive marked as the boot drive is given the 'A:' drive letter by the configuration program on the source machine. Because A: is ignored in the recovery environment the recovery/clone using this configuration fails because it cannot assign a drive letter to the boot partition. This is now fixed. Copyright Cristie Software Ltd.

10 10 v) Amount of RAM in Target VM does not match the original machine. This was observed in several Windows and Linux clones with larger amounts of RAM (> 12GB). This is now corrected. vi) The message "TGT Disk 1 must be repartitoned" even though disk is de-selected in the Clone Summary dialogue. This occurs if the target has the same or more disks than the source, and you try to deselect one or more of the source disks. If the target has less disks than the target, the deselect option works. If you don't, it incorrectly warns you to check the disk configuration before proceeding. This is now corrected. vii)when running the suite installation in silent mode, the upgrade warning dialogue is still displayed. This is now suppressed. viii) CM-Agent install was allowed on Windows 2012 R2 even though it is not supported. This is now 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 IP address for a booted target, the target was not detected. This is now corrected i) The Event Log now shows 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 or CloneSync process; it will, however, become more accurate as more files are copied to the target. 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 average data 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 now fixed. v) Documentation updated for this release i) Added 'Agentless' support for Microsoft Windows server OS's. None. CloneManager 2.1 Readme

11 CloneManager Readme i) Added clone support for Microsoft Windows 2012 (including Core versions) on all supported Hypervisors. ii) Added support for batched cloning. iii) Added support for scheduled cloning. iv) Added support for event 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 the CloneManager 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' now installed separately. xi) The vcloud VM "Computer Name" is now saved and synced to that of the original source machine's hostname. xii) Settings persistence has been enhanced to use an internal SQL-Lite database instead of a flat XML file. xiii) When syncing a system, the original source machine is now automatically restored from the settings database xiv) When syncing/cloning a system that has been synced/cloned before, the credentials for the source 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 Hypervisor target environments. xix) Removed automatic deletion of systems from the CloneManager Console GUI - this is now user 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 target systems. xxiii) Added further validation around incompatible disk configurations between source and target. xxiv) Added support for "refreshing" a target Hypervisor after it has been defined to 'say' pick up new ISO's. xxv) Enhanced the reporting of clone and sync operations. Copyright Cristie Software Ltd.

12 12 xxvi) Added backwards compatibility, the console will now recognise clients separately from clients and act appropriately. xxvii) Added support for saving all information about a clone (source system details, target system details, clone configuration, clone metrics etc.). xxviii) Improved the performance of the clone validation procedure. i) Fixed various logging issues. ii) Fixed an issue where ignoring disks would cause the wrong disk to be ignored in the recovery environment. 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 vapps correctly. 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 to communicate using the wrong IP addresses. viii) Fixed an issue where every NIC created in a vsphere clone would be called "Network Adapter 1". ix)fixed an issue where an incorrect DNS server would be shown for a particular NIC in the network settings display in the Clone Summary dialogue. x) Fixed an issue where an error associated with failure to connect to a CTM would be shown multiple 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 displayed filesystems 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" when undergoing 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 to stall 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 which would cause the whole operation to fail. CloneManager 2.1 Readme

13 CloneManager Readme 13 xxiii) Fixed an issue where a very quick sync would cause the WinPE 4 Live environment to crash None. - CloneManager Console Only (i) In Windows corrected a problem where, in a group of source disks, one or more disks were deselected for cloning in the middle of the group. The effect of this was to create disks on the target 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) None. (i) The disk drive mapping mechanism in the CloneManager Console has been corrected so that virtual targets are created with the correct number of drives, and mapped correctly. This is to fix a problem where disks on the source were deselected for the clone operation resulting in disk allocation errors (i) Now allows any User account with local Administrator credentials to both install and run clone operations. (ii) Now allows the vcloud Live environment to boot with an IP address obtained from either DHCP, 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 already exists 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 Token Manager. 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. Copyright Cristie Software Ltd.

14 14 (vii) Minor improvements to Token Manager error handling. (i) It was possible to sync a clone to itself. This is no longer possible. (ii) Upgrading the CM-Agent 1.2 to on Windows 2003 x86 or x64 caused the machine to reboot. This has now been fixed. (iii) Upgrading the CloneManager PE4 Fileset 1.2 to on Windows 2003 x86 or x64 and when run with CRISP resulted in an ISO that when booted showed incorrect fonts. This has now been fixed. iv) It is now possible to clone a Windows or Linux system with 8 or more disks to targets on VMware vsphere (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 when cloning 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 the program exits. (i) None First release. First release. CloneManager 2.1 Readme