vConverter® 5.1.
© 2011 Quest Software, Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement.
Table of Contents Introduction to this Guide ...................................................................................................7 About vConverter ........................................................................................................................... 8 About this Guide ............................................................................................................................. 8 vConverter Documentation Suite ...............................................
Table of Contents 4 Synchronized Cutover........................................................................................................... 25 Different Destinations Cutover .............................................................................................. 26 64k Alignment ....................................................................................................................... 26 Support for RDM .............................................................................
Table of Contents 5 Email Notifications................................................................................................................. 48 ESX Servers.......................................................................................................................... 53 Hyper-V Servers.................................................................................................................... 56 Target Folder.....................................................................
Table of Contents 6 Continuous Protection Overview ................................................................................................ 115 Licensing .................................................................................................................................... 116 Configuring Continuous Protection............................................................................................. 118 Basic Configurations ...........................................................
Introduction to this Guide This chapter provides information about what is contained in the vConverter User Guide. It also provides information about the vConverter documentation suite and Quest Software. This chapter contains the following sections: About vConverter............................................................................................... 8 About this Guide ................................................................................................ 8 vConverter Documentation Suite.
Introduction to this Guide About vConverter 8 About vConverter vConverter is a complete workload migration platform. It provides the functionality, flexibility, and speed needed for high-volume migrations of Windows or Linux servers within the datacenter. vConverter provides numerous features for medium to large server consolidation initiatives, as well as options for ongoing disaster recovery. Multiple conversion modes and target options ensure data consistency with minimal downtime.
Introduction to this Guide vConverter Documentation Suite 9 Chapter 7, Linux P2V Conversions — this chapter provides information on configuring P2V conversions of Linux source servers. Chapter 8, Windows V2P Conversions — this chapter provides information on configuring V2P conversions of Windows source servers. Appendix — the appendix provides information about how to configure networking in the VistaPE environment, as well as what drivers are supported.
Introduction to this Guide About Quest Software, Inc. 10 documentation? All comments are welcome. Please submit your feedback to the following email address: info@vizioncore.com Note Please do not submit Technical Support related issues to this email address. Text Conventions The following table summarizes how text styles are used in this guide: Convention Description Code Monospace text represents code, code objects, and commandline input.
Introduction to this Guide About Quest Software, Inc. 11 Contacting Quest Software Email info@quest.com Mail Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA Web site www.quest.com Refer to our web site for regional and international office information.
vConverter Functional Overview This chapter describes the features and functions available in vConverter. This chapter contains the following sections: vConverter Overview ....................................................................................... 13 Conversion Process......................................................................................... 17 Features and Functions ...................................................................................
vConverter Functional Overview vConverter Overview 13 vConverter Overview vConverter is an enterprise-class Physical-to-Virtual (P2V), Virtual-to-Virtual (V2V), and Virtual-to-Physical (V2P) converter that significantly reduces the time, cost and effort required to convert physical and virtual machines to VMware, and Microsoft virtual machines, as well as deploy virtual machines to a physical environment. It offers simple conversions, together with complex disaster recovery plans.
vConverter Functional Overview vConverter Overview 14 Source Server Components Drive Capture Tool This tool reads disk data and transfers it to the target server. The Drive Capture tool includes the Image Consistency Driver. The Drive Capture Tool can operate in both block and file modes. Block mode is faster and gives exact binary copy of source volumes, but file is required for volume resizing operations.
vConverter Functional Overview vConverter Overview 15 vConverter Client Components UI Client UI Client (the Client) helps user to configure conversions, to control the conversions, and indicates conversion process progress. License Service A program unit which maintains user license information, such as counter of systems to migrate, time restriction information, etc.
vConverter Functional Overview vConverter Overview Remote Launch Tool 16 A tool intended for executing processes on a remote Windows system. It requires having the administrative credentials for a remote system to run. Target Components Target Server Agent for ESX Used for creating and writing to VMDKs on VMware ESX Server 3.x and 4.x. The Target Server Agent has to be run in the Service Console of the target VMware ESX server.
vConverter Functional Overview Conversion Process 17 Conversion Process There are several different types of conversions available with vConverter. Each type of conversion follows a slightly different process, and offers different options. The main types of conversions available are: • Windows P2V • Linux P2V • Windows V2P Windows P2V The primary use case for vConverter is to migrate a workload from physical Windows servers to a virtual machine on one of the supported platforms.
vConverter Functional Overview Conversion Process 18 The main components of the conversion process are the Drive Capture Tool (which sends the data) and the Target Server Agent (which receives the data). After the job is executed and the Drive Capture Tool (DCT) starts sending data to ESX, it is detected by the Target Server Agent (TSA) service running. This starts the server component particular to that job. Multiple jobs can run at the same time and each job will use its own server component instance.
vConverter Functional Overview Conversion Process 19 Linux P2V The Linux P2V process follows the basic workflow described below: The main components of the Linux conversion process are the Migration Tool Package (MTP) and the Post Processing Service (PPS). The MTP is uploaded to the Linux source server, and prepares and sends the data. The PPS resides in the vConverter Virtual Appliance running on VMware vMA – it receives data from vConverter and the MTP and creates VMs and write VMDKs.
vConverter Functional Overview Conversion Process 20 Once the job has been configured and started, the vConverter client starts a new migration session and invokes the Post Processing Service that is running within the VMware vMA on the target system. The PPS creates virtual disks and makes some additional preparations to receive the data from the source MTP. When all preparations on the PPS site have been done, the vConverter client invokes MTP to start streaming the source data.
vConverter Functional Overview Conversion Process Note 21 A P2V conversion using the VA as a target may fail if the resulting VM will have the same name as another VM within the vCenter infrastructure. The error message "Can't find proper disk-name amount attached disks to VA” will be displayed. Additionally, several indexed VM copies may be created on the target ESX host. Windows V2P vConverter offers the ability to convert Windows VMs back to a physical target.
vConverter Functional Overview Conversion Process An architectural representation of the Windows V2P process is shown below: 22
vConverter Functional Overview Features and Functions 23 Features and Functions P2V for Windows Servers vConverter is a task, enterprise-level consolidation/migration application. It allows you to capture a live physical or virtual Windows system and transfer its data directly to a Windows shared folder, Microsoft Hyper-V, or ESX host. vConverter's physical to virtual (P2V) and virtual to virtual (V2V) approaches ensure consistent results: the converted image will mirror the source.
vConverter Functional Overview Features and Functions 24 Hot Conversions Hot cloning is the process of taking a live source system and creating a complete copy of it in the form of a VM. To yield a data-consistent image, the vConverter Consistency Driver (VCD) and MS VSS assist in the process. VCD captures write requests from the file system and retains the former state of the updated disk blocks. VCD is unaware of running applications on the source and therefore cannot save associated data for backup.
vConverter Functional Overview Features and Functions 25 1 vConverter sends a new boot loader to the source. 2 vConverter sends the VistaPE boot image file directly to the source and initiates a reboot. 3 The source boots into the vConverter boot image and instantiates the network stack. 4 vConverter establishes contact with the conversion monitor and initiates the conversion process.
vConverter Functional Overview Features and Functions 26 intervals (for example, every 15 minutes). Synchronized Cutover uses the hot cloning method for initial and subsequent synchronizations. While cold cloning is used for the final synchronization, you can also trigger a hot (live) final synchronization. Note Synchronized Cutover is only available for Windows conversions.
vConverter Functional Overview Features and Functions 27 Support for RDMs requires two specific settings in the Advanced Task Properties. Conversions to RDMs need to be configured to create a flat (non-growable) disk, and all source volumes should be converted to a single device. For more information, please see “Task Profiles - Properties” on page 60. Note P2V Conversions to an RDM are disabled when using the Virtual Appliance for VMware.
vConverter Functional Overview Features and Functions 28 Disable Task Running Disabling a Task would be useful if a disaster occurs and Protection Site becomes unavailable. Executing a predefined recovery plan, while leaving configured backups/ replications/conversions unaltered would be useful. Conversion could be postponed using the Disable option. Task will be disabled and will not be run. Later conversions could be enabled by using the Enabling command.
vConverter User Interface This chapter provides an overview of the main functions of the vConverter User Interface. This chapter contains the following sections: User Interface Overview .................................................................................. 30 Menus .............................................................................................................. 31 Toolbars...........................................................................................................
vConverter User Interface User Interface Overview 30 User Interface Overview The vConverter window is the central navigational area of the software. This is where you can view the main components of the system. Through this window you can access the commands that allow you to configure and execute conversion jobs. Now that the software is installed, launch it through its desktop icon or the Start menu.
vConverter User Interface Menus Menus The Menu Bar contains the following options: 31
vConverter User Interface Menus File Export>Tasks Displays the Save as dialog from which you can export your configured conversion tasks. This allows vConverter to be installed on multiple systems, maintaining the same configurations. Export>Settings Displays the Save as dialog from which you can export the settings that you defined through Tools>Preferences. This allows you to maintain the same preferences on multiple systems and instances of vConverter.
vConverter User Interface Menus 33 View View properties The Task Properties tab is the area in which conversion tasks area configured. View Live Log Each conversion task consists of several steps, depending on the task type. Live Log displays all these steps in an expandable tree view form, with nice graphics. View Scheduler This tab displays all scheduled conversion jobs in a calendar format. View Statistics The Statistics tab shows a historical record of activity for the selected task.
vConverter User Interface Toolbars Clear logs Deletes all application logs. Caution About 34 Deleted logs will not be available for Support. Use this feature selectively. Displays information about vConverter, including: • Software version • Name of the person to whom the software is registered • License number The About window also includes a View License Details link that will show the current licensing status, as well as the license agreement link.
vConverter User Interface Task List 35 Disable Task – for more information, see “Disable Task Running” on page 28 Enable Task – for more information, see “Disable Task Running” on page 28 Save Task Cancel Task Editing Start Task Stop Task Run Conversion Wizard Open the About Window Task List In vConverter, each task has to be placed into corresponding container, or folder. Folders are a way to put similar conversion tasks together.
vConverter User Interface Task List 36 Folders and tasks are managed via the Task List pane of the vConverter UI. Tasks can also be Started, Edited, Removed and Enabled/Disabled by right clicking a Task.
vConverter User Interface Conversion Tasks Pane 37 Conversion Tasks Pane The Conversion Tasks Pane includes four tabs: • • • • the Properties tab the Live Log tab the Scheduler tab the Statistics tab Each of these is described below. Properties The Task Properties tab is the area in which conversion tasks area configured. The Task Properties pane consists of Source and Target hotspots, the Source Drive section, the Target section, and the Source Section.
vConverter User Interface Conversion Tasks Pane 38 LiveLog Each conversion task consists of several steps, depending on the task type. Live Log displays all these steps in an expandable tree view form, with nice graphics. If inner step fails, it lifts fail state to the top level, so users can easily locate failed task runs. Available information about error reason is displayed below the failed entry, to make troubleshooting easier.
vConverter User Interface Conversion Wizards 39 Statistics The Statistics tab shows a historical record of activity for the selected task. Conversion Wizards The Conversion Wizard offers a step-by-step approach to configuring a conversion task. The same wizard is used for all types of conversions. The first screen allows you to select the type of conversion you want to perform.
vConverter User Interface Conversion Wizards 40 The Conversion Wizard will walk you through the task configuration steps.
Configuring vConverter This chapter details the processes for configuring the basic connections required by vConverter. In addition, the procedures for completing the basic backup and restore wizards will be documented. This chapter contains the following sections: Configuration Overview ................................................................................... 42 Licensing..........................................................................................................
Configuring vConverter Configuration Overview 42 Configuration Overview Now that vConverter is installed, you can launch it by double-clicking the desktop icon or by accessing it through the Start menu. The software requires a number of application and environment configurations to ensure that it functions properly. They are described in detail below. Note Most of the content in this chapter is also in the vConverter Installation and Setup Guide.
Configuring vConverter Licensing 43 License Overwriting An instance of vConverter can have only one license installed at a time. Trial licenses can only be installed on an unlicensed instance of vConverter, or on a vConverter instance that has a trial license (expired or not). Installing a new trial license over a previously installed license will overwrite all settings, in particular, expiration date and number of systems.
Configuring vConverter Configuring vConverter 44 Configuring vConverter Now that vConverter is installed, you can configure the universal settings and preferences for the application. The initial configurations can be made with the vConverter Preferences dialog. The vConverter Preferences dialog is available by selecting Tools > Preferences from the vConverter toolbar.
Configuring vConverter Configuring vConverter 45 General o Figure 1 View Show quick tips: Tips are enabled by default. This will show pop-up windows as you change tabs or open the application. Show balloon help: Balloon help is enabled by default. This will show specific, task-oriented suggestions.
Configuring vConverter Configuring vConverter Network Settings 46 Limitation of total simultaneous conversions: The value you enter in this field will restrict the number of conversions that you can run simultaneously. Limitation of simultaneous conversions to the same target server: The value you enter in this field will restrict the number of conversions that you can run simultaneously to the same target server.
Configuring vConverter Configuring vConverter 47 Conversion Figure 2 Windows P2V conversion using vConverter rules: Software appends an underscore and drive letter or volume GUID (for hidden partitions) to the server name (e.g., ABC_C.vmdk). using VMware rules: Software appends an underscore and number to the server name (e.g., ABC.vmdk, ABC_1.vmdk, ABC_2.vmdk) for multiple VMDKs. Linux P2V conversion Allows you to configure time out values.
Configuring vConverter Configuring vConverter 48 Cold P2V conversion vConverter will wait for the source system to respond before beginning the conversion process. The wait interval can be configured here - either infinite or a defined value. If there is no response received from the source system during the timeout interval, the conversion will fail. Having large timeout value may be useful when booting source systems with limited resources, where booting to the VistaPE may require additional time.
Configuring vConverter Configuring vConverter 49 Figure 3 Notification Method The Mail Notification feature can be configured to use either a MAPI compliant mail client or an SMTP server. MAPI Client: This mail client, such as Microsoft Outlook needs to be installed on the same machine as vConverter. SMTP: You will need the name or IP address of the SMTP server, as well as credentials with access to send mail via the SMTP server.
Configuring vConverter Configuring vConverter “Conversion started” notification 50 Select the Enable check box to activate these fields: Email addresses to send: Use this field to enter email addresses for those who should receive alerts when conversion jobs are initiated. Email subject: Populate this field with the text that you want to display in the Subject line of the alerts sent to the recipients listed in the Email addresses to send field.
Configuring vConverter Configuring vConverter 51 Server Name or IP The name of the SMTP server or its IP address. Server Port The port for the SMTP server. The default value is 25. Email Address The address from which email notifications about this server will be sent. Email Username The user account from which email notifications about this server will be sent. Email Password The password of the user account used above. Repeat Email Password The password of the user account used above.
Configuring vConverter Configuring vConverter 52 Email Notifications – Configure MAPI Using MAPI Email Notifications, vConverter will use the current default email account. You should check your email accounts in OS Window settings. Note Some mail clients, such as Microsoft Outlook, must be installed on the same machine as vConverter. MAPI is available of x86 OS only. If you select MAPI on the Email Notifications tab of the Program Preferences window, the Configure button is enabled.
Configuring vConverter Configuring vConverter 53 ESX Servers Figure 4 Servers Lists all of the ESX Servers — by IP address or name — that are available for conversion. Allows you to add, edit, delete, and test connectivity.
Configuring vConverter Configuring vConverter Server Info 54 The fields on this tab include general properties for the ESX Servers in the system: • • • • • • Host name or IP Username Password Verify password Root password Verify root password Use these options to configure individual ESX Servers: Create User if doesn’t exist, and Enable VA feature check boxes. Note The username and password entered above are used only to connect to the Service Console of the ESX Server.
Configuring vConverter Configuring vConverter 55 ESX Servers - VA Configuration If you click the VA Config button on the ESX Server tab, the VA Configuration dialog is displayed. On this dialog, you can configure VA, including the number of disks it has.
Configuring vConverter Configuring vConverter 56 2 Use Help->Support feature to generate a whole logs package to send to support. Note Once an ESX server is configured, and tasks added to it, a change in the server configuration will break any tasks configured for that server. Hyper-V Servers Servers Lists all of the Hyper-V Servers — by IP address or name — that are available for conversion. Allows you to add, edit, delete, and test connectivity.
Configuring vConverter Configuring vConverter Server Info The fields on this tab include general properties for the Hyper-V Servers in the system: • Host name or IP • Username • Password • Verify password Note The Username and Password should match the credentials used when configuring the Hyper-V target share. See “Target Folder” on page 57 for more information. Target Folder Conversions to Hyper-V servers require a shared folder to store the VM files.
Configuring vConverter Configuring vConverter 58 Profiles Lists the configured user profiles. The default profile is in bold. It allows you to add, delete, and edit user profiles, and to set a default profile. Settings Always query for credentials: This option will require credentials or a user profile to be provided during job configuration. Use default user profile: This will use the default profile for all configured jobs. You will have the option to override this during job configuration.
Configuring vConverter Configuring vConverter 59 Task Profiles A Task Profile is a set of conversion task settings that can be saved independent of conversion type. If you set a default profile, this will be applied to all new conversion jobs that you create. Settings that do not apply to the current conversion type (i.e., P2V settings for a V2P task) will be ignored.
Configuring vConverter Configuring vConverter 60 Task Profiles - Properties Access this dialog through Tools >Preferences >Task Profiles >Add. The settings that are used to build these profiles are not tied to specific source or target server types. Note The Name field in the Task profile info area is a required field.
Configuring vConverter Configuring vConverter 61 Disk tab Create flat disk image (Non Growable): De-selecting this checkbox will enable the creation of thinly provisioned disks for vSphere (ESX 4) targets. Flat format is required for ESX Server 3.x / 3i, but enabling this option can slow the conversion process. Note This must be enabled in order to resize volumes during conversion. Note This option should be selected when converting to an RDM.
Configuring vConverter Configuring vConverter Adapter type: 62 Adapter type for created VM and captured disks. Affects the VM configuration file and set of drivers added to the converted OS during migration. The Adapter type drop-down contains a list of virtual disk adapter types for VMs and captured disks. If a target VM platform supports a particular adapter type, it will be listed in this field. Available types include: • IDE • LSI Logic • Bus Logic Note VM tab For Windows 2000, select Bus Logic.
Configuring vConverter Configuring vConverter Create Virtual Machine 63 Instructs vConverter to create a VM descriptor file and registers the VM in the target environment (ESX Server/Hyper-V). Otherwise, only a set of disk image files is created, which you must attach to the VM manually.
Configuring vConverter Configuring vConverter X Window 64 Opens the X Window Options dialogue that allows you to configure vConverter behavior towards source servers running X Window System. VM tab - VM Options Dialog Create Floppy Drive This option to configure the target to feature a floppy drive. Note When the target server is Hyper-V, will be checked and disabled. The floppy will be created by vConverter (Hyper-V will not support a VM with no floppy drive).
Configuring vConverter Configuring vConverter 65 Migration tab Uninstall Conflicting Hotfixes Microsoft occasionally releases a hotfix with an updated HAL.DLL that supersedes the file of the source format included in the current SP. This can cause a VM not to boot. To prevent this, keep the Uninstall Conflicting Hotfixes option enabled. This uninstalls hotfixes that could otherwise impact kernel files during system migration. This option is enabled by default.
Configuring vConverter Configuring vConverter Script Settings 66 Opens the Scripts Settings dialog. Use this dialog to insert scripts (.cmd, .bat) and dependent applications (.exe, .dll) into a target VM to run on the first boot. Login tab vConverter can also use network shares as a conversion target and as a source for V2P conversions. The credentials used to login to the shared folder are displayed here. To configure or change the credentials, click Change Login.
Configuring vConverter Configuring Setup Files 67 Login tab - Change Credentials Dialog Use credentials from profile Select this option to use a configured User Profile. Select a profile from the menu. Specify credentials manually Select this option if you do not want to use or configure a user profile. Select Save as a new user profile to create a user profile based on the credentials entered.
Configuring vConverter Configuring Setup Files 68 To configure Setup Files: The procedure below needs to be completed for each OS type. For the purposes of Setup Files, the 32-bit version of a given OS is a separate OS type than the 64-bit version of the same OS. Step 1: General Tab 1 From the vConverter UI, click Tools, then Preferences. 2 The Program Preferences dialog opens to the General tab. Step 2: Add New Record 1 In the Setup Folders section, click Add. A new entry is created.
Configuring vConverter Configuring Setup Files 69 5 In the Location for OS setup files column, browse to the location of the setup files for the correct OS. Note Setup files can be located on a network share or on a computer running the vConverter. Service Pack files can be extracted to a single location for easy access. The network share should be available to be read by the current logged on user. 6 Click OK.
Adding Source Content This chapter details the different ways in which you can add source content to vConverter. This chapter contains the following sections: Source Content................................................................................................ 71 Network Browser ............................................................................................. 71 Importing Source Systems............................................................................... 72 Adding Linux Hosts.
Adding Source Content Source Content 71 Source Content The first step in the conversion process is to add source content - physical or virtual servers that are to be converted by vConverter. Network Browser The Network Browser is available on the left side of the vConverter interface. The Network Browser pane displays the domains and workgroups that include all servers available for conversion.
Adding Source Content Importing Source Systems 72 systems from the rest of the network. You may do this by moving them to the Systems to Convert tab. To add source content with the Systems to Convert tab: 1 In the Network Browser pane, click the All Systems tab. 2 Right-click the desired server. Select Add to Systems to Convert. Note Only one server may be selected at a time. 3 Click the Systems to Convert tab. The selected server will appear on the Systems to Convert tab.
Adding Source Content Importing Source Systems 73 • Confirm that the CSV file contents include the appropriate columns. Different source systems require different information to be properly imported. Note The CSV file fields should not contain leading or trailing spaces. Any leading or trailing spaces will be incorporated into vConverter files, and may create import failures. The table below shows the fields available in the CSV, and lists which source systems use which heading.
Adding Source Content Adding Linux Hosts 74 Adding Linux Hosts Linux servers are not automatically discovered and must be added manually prior to configuring a conversion task. To add a Linux host: 1 In the Network Browser pane, right-click on the Linux Hosts node. 2 Click Add Linux source. 3 Complete the Add a new Linux source system dialogue. Quest recommends using the Secure Connectivity option. vConverter will connect with this alternate login, then SU to gain appropriate authority. 4 Click OK.
Adding Source Content Adding Physical Targets 75 2 Once booted, the target server will appear under the Cold Cloning ready (under WinPE) node. Adding Physical Targets Adding a physical target is very similar to preparing a physical server for cold conversion. Physical servers (targets for V2P conversions) need to be booted into the VistaPE environment before they can be selected as a target. To add a physical target: 1 Boot the target server using the vConverter VistaPE boot environment.
Windows P2V Conversions This chapter provides information on creating P2V conversion This chapter contains the following sections: Conversion Overview....................................................................................... 77 Hot Conversions .......................................................................................... 78 Converting with Remote Cold Cloning (RCC) .............................................. 79 Converting with Synchronized Cutover ................................
Windows P2V Conversions Conversion Overview 77 Conversion Overview The standard Windows P2V process follows the basic workflow described below. The main components of the conversion process are the Drive Capture Tool (which sends the data) and the Target Server Agent (which receives the data). After the job is executed and the Drive Capture Tool (DCT) starts sending data to ESX, it is detected by the Target Server Agent (TSA) service running. This starts the server component particular to that job.
Windows P2V Conversions Conversion Overview 78 assignment. The server component terminates and enters a wait state controlled through the TSA to anticipate the next job. An architectural representation of the Windows P2V process is shown below. Note A P2V conversion using the VA as a target will not finish successfully if the resulting VM will have the same name as another VM within the vCenter infrastructure. The error message "Can't find proper disk-name amount attached disks to VA” will be displayed.
Windows P2V Conversions Conversion Overview 79 former state of the updated disk sectors. VCD is unaware of running applications on the source and therefore cannot save associated data for backup. This is where MS VSS steps in-telling databases, application servers, and so forth to flush uncached data to disk so that backup can proceed. Converting with Remote Cold Cloning (RCC) Cold cloning requires a reboot of the source into vConverter's boot image.
Windows P2V Conversions Conversion Overview 80 For procedures specific to RCC, see Additional Task Procedures at the end of this chapter. • Hardware Adaption Wizard utility will help install the drivers externally if you cannot boot your Windows operating system due to missing drivers. Note The VistaPE will assign the volume letter “X” to it’s own RAM drive volume. If the VistaPE is used to convert a physical volume with the same volume label, the PE environment will become unavailable to vConverter.
Windows P2V Conversions Conversion Overview 81 synchronizations, is not complete and is not bootable. The final synchronization performs necessary OS corrections and upgrades the file system to a consistent state. Only after the final synchronization is the target VM bootable. Moreover, until the final synchronization finishes, the target VM must not be modified in any way. The final synchronization is only performed in file mode.
Windows P2V Conversions Creating Conversions 82 The Different Destinations Cutover P2V process is described in the flowchart below and in the sections that follow. Note that there are multiple optional configurations available. This document is intended only to illustrate the basic functionality. The process of configuring a Different Destinations Cutover conversion is very similar to configuring a basic P2V conversion. The tasks represented by the red boxes are unique to Different Destinations Cutover.
Windows P2V Conversions Creating Conversions 83 • Saving and Running a Task Each of these operations can be performed in several ways, and have a variety of configuration options. The sections below explain the options and configurations in each operation. Most of the information below is applicable to all conversion types. Where a given conversion type requires a change from the standard or more information, this information will be called out separately.
Windows P2V Conversions Creating Conversions Enter the criteria by which you wish to filter in this text box. Filtering is case-sensitive and applies system names or IP addresses. The asterisk (*) can be used as a wild card. Click this button to filter the results of the active table. Note This button is not enabled when the Filter toggle is off.
Windows P2V Conversions Creating Conversions Drag and Drop 85 This option is only available if you have an active configuration task open. You may drag a selected server to the Source Server hotspot: Using this option will set the selected system as the source server for the active configuration task, using the settings in the default task profile. Systems to Convert tab The Network Browser pane includes a Systems To Convert tab.
Windows P2V Conversions Creating Conversions 86 the appropriate columns. Different source systems require different information to be properly imported. Note The CSV file fields should not contain leading or trailing spaces. Any leading or trailing spaces will be incorporated into vConverter files, and may create import failures. The table below shows the fields available in the CSV, and lists which source systems use which heading.
Windows P2V Conversions Creating Conversions 87 Synchronized Cutover. It may make sense to create a folder for each of these conversion methods, with a remaining folder for the standard conversions. • By Schedule - Given the length of most virtualization projects, it may aid project management to create folders for each unit of your project timeline (Week 1, Week 2, etc). Creating a Folder Folders and tasks are managed via the Task List pane of the vConverter UI.
Windows P2V Conversions Creating Conversions 88 Configuring Source and Target Settings Source and target configuration is done through the Task Properties pane of the vConverter UI. With the exception of the Advanced Options dialogue, all of the configuration options are viewable on the same pane. Source Options Most of the configuration required relates to target settings, but there are some key source specific settings that can help you get the most out of your conversions.
Windows P2V Conversions Creating Conversions The table below describes the actions available in the Source Drives section. Select Drives: Each drive in the source system will be listed. Use the checkbox in this column to select (or de-select) which drives in the source system to convert. Select the checkbox in the header row to select (or de-select) all of the drives at once. Volume: The available drives are described in this column. File system: Identifies the file system type of the listed volume.
Windows P2V Conversions Creating Conversions Folder: Each volume may be converted to a separate datastore location. Once a target server has been selected, click the browse icon to view the datastores or network shares available to the target server. Note If you do not make a selection here, the target selected in the Target Folder field of the Target section will be used.
Windows P2V Conversions Creating Conversions 91 Volume Mapping Type For each Windows P2V task, the kind of disk mapping is selectable from the Task list pane. This feature is available when target is Shared folder, Hyper-V or ESX (with no VA). By specifying the desired disk mapping, VMDK file creation methods and source disk mapping can specified. The following options are available: • Create one virtual disk for each volume -- each source volume should be placed in separate VMDK file.
Windows P2V Conversions Creating Conversions 92 VM Options In the VM Options sections you may configure the VM type and name, as well as the type of conversion. VM Type Use this menu to select the type of VM you want to create. Supported options are: • VMware ESX Server (3.x, 4.x) • Microsoft® Hyper-V Server VM Name Enter the name for your VM. By default, this field populates with the machine name when a source is added to the task. You may change it as desired.
Windows P2V Conversions Creating Conversions Conversion Type 93 Use this menu to select the conversion type. Available options are: • • • • • Single Remote Cold Cloning Synchronized Cutover Different Destinations Cutover Continuous Protection Note For V2P Windows and P2V Linux conversions, only Remote Cold Cloning is available as a conversion type. For more information about conversion types, see “Features and Functions” on page 23 or “Conversion Overview” on page 77.
Windows P2V Conversions Creating Conversions 94 Network Browser pane, and drag it to the Target Server hotspot. You may also rightclick and select Set as Target. The table below describes the actions available in the Targets section. Target • When converting to a hypervisor host, use this field to select that host as a target. Note The server can be specified manually or could be added via Tools>Preferences. Use the appropriate tab for the chosen virtualization platform.
Windows P2V Conversions Creating Conversions Transfer mode There are two available transfer modes: block and file. Use this menu to select the desired transfer mode. • Block: Block cloning uses an Application Programming Interface (API) from the source OS that allows you to skip unused sectors. This is the default transfer mode, yielding an exact binary copy of a source volume. • File: File cloning of a source occurs on the file system level.
Windows P2V Conversions Creating Conversions Disk Tab 96 This tab features these settings: • Create Flat Disk Image (Non Growable) • Skip Bad Sectors where Possible • Overwrite file if it exists The Adapter type dropdown contains a list of virtual disk adapter types for VMs and captured disks. If a target VM platform supports a particular adapter type, it will be listed in this field. Available types include: • IDE • LSI Logic • Bus Logic Note For Windows 2000, select Bus Logic.
Windows P2V Conversions Creating Conversions Migration Tab 97 This tab features these settings: • Uninstall conflicting hotfixes only • Use Live Final Sync if Possible • Uninstall Software • Service Manager • Script Settings Note The Use Live Final Sync if Possible option applies only to Synchronized Cutover and DDC conversions. You may also configure HAL type and Setup file location from this tab. For a more detailed description of these options, please see “Migration tab” on page 65.
Windows P2V Conversions Creating Conversions Note 98 Different Destination Cutover conversions are not scheduled differently than standard conversions. The pausing of the task and movement of the target VM are manual tasks performed at will and communicated to vConverter through the Current Activity field. See Configuring a Conversion with Different Destination Cutover for more information. Once set, the task will be shown in the daily schedule on the right side of the Scheduler tab.
Windows P2V Conversions Creating Conversions 99 Workflow 1 1 Create a CP/SC/DDC task. 2 Set Start at = tomorrow, 12.30. 3 Set Run every = 1h. 4 Save the task. 5 Run the task immediately. 6 The initial step will be performed: • Next intermediate sync step will be started tomorrow, 12.30 • Start at field will not be changed to meet real initial step start time Workflow 2 1 Create and configure the CP/SC/DDC task. 2 Save CP/SC/DDC task. 3 Run initial conversion as planned in Start at.
Windows P2V Conversions Conversion Tutorial 100 Conversion Tutorial Note The procedures in this section are for a standard single conversion. Most of these procedures do not change for different conversion types. Please see “Additional Task Procedures” on page 104 for information on how the procedures change for each conversion type. The configuration of target servers and setup folders is usually done independently of task configuration.
Windows P2V Conversions Conversion Tutorial 101 • "%windir%\Driver Cache • "%windir%\ServicePackFiles Occasionally, an administrator will have to remove the files from these locations manually or programmatically by running the SFC /PURGECACHE command. If this has happened to a source server, vConverter will display a message stating that “Required files for this server . . . are missing . . .”.
Windows P2V Conversions Conversion Tutorial 102 Step 2: Create P2V/V2V Task 1 Right-click the task folder, and select Create P2V/V2V task. The Task Properties pane is enabled. Step 3: Select Target Server 1 In the Task Properties pane, select the appropriate type of VM from the VM type field. The value selected here is determined by the target server to which you are converting. In the example below, we are creating a VM on a VMware ESX Server.
Windows P2V Conversions Conversion Tutorial 103 • File: File cloning of a source occurs on the file system level. The target is mounted to the source and a full file synchronization occurs-directory structure from the source and all file content are updated to the target. File cloning is ideal for capturing large source volumes to a target with limited storage capacity. To ensure consistency during hot cloning, use the file method with MS VSS.
Windows P2V Conversions Additional Task Procedures 104 3 The task will run at the scheduled time. To execute the task manually, click the Start icon. Additional Task Procedures The Conversion Tutorial section described procedures for a standard P2V conversion. While many of the steps will not change for the other conversion types, some clearly will. The procedures for each conversion type are documented below.
Windows P2V Conversions Additional Task Procedures 105 Step 3: Select Target Server 1 In the Task Properties pane, select the appropriate type of VM from the VM type field. The value selected here is determined by the target server to which you are converting. In the example below, we are creating a VM on a VMware ESX Server. 2 When the VM type field is selected, suitable targets will be displayed in the Target menu. Select the desired target server. 3 Click Browse to configure the Target folder field.
Windows P2V Conversions Additional Task Procedures 106 Step 4: Select Source Server In the Network Browser pane, select the server to convert. Right-click the server, and select Set as source. 7 In the Source Drives section, select the volumes to convert. Configure Resize and Target Folder values as needed. Note VistaPE will assign the volume letter “X” to it’s own RAM drive volume.
Windows P2V Conversions Additional Task Procedures 107 Configuring a Conversion with Synchronized Cutover The process of configuring a Synchronized Cutover conversion is very similar to configuring a basic P2V conversion. Two key differences are: • Conversion type must be set to Synchronized Cutover • A cutover time must be scheduled. The tasks represented by the red boxes are unique to Synchronized Cutover.
Windows P2V Conversions Additional Task Procedures 108 Step 3: Select Target Server 1 In the Task Properties pane, select the appropriate type of VM from the VM type field. The value selected here is determined by the target server to which you are converting. In the example below, we are creating a VM on a VMware ESX Server. 2 When the VM type field is selected, suitable targets will be displayed in the Target menu. Select the desired target server. 3 Click Browse to configure the Target folder field.
Windows P2V Conversions Additional Task Procedures 109 Step 4: Select Source Server 1 In the Network Browser pane, select the server to convert. Right-click the server, and select Set as source. 2 In the Source Drives section, select the volumes to convert. Step 5: Schedule and Save 1 Click the Scheduler tab to set a schedule for this task. • Select a starting date and time. • Select a synchronization interval. • Select a Cutover time.
Windows P2V Conversions Additional Task Procedures 110 Configuring a Conversion with Different Destination Cutover The process of configuring a Different Destinations Cutover conversion is very similar to configuring a basic P2V conversion. Two key differences are: • After the initial conversion(s), the target VM is moved to a different location. • Conversion activity is managed using the Current Activity field The tasks represented by the red boxes are unique to Different Destinations Cutover.
Windows P2V Conversions Additional Task Procedures 111 Step 2: Create P2V/V2V Task 1 Right-click the task folder, and select Create P2V/V2V task. The Task Properties pane is enabled. Note At this point, the DDC VM is created. Step 3: Select Source Server 1 In the Network Browser pane, select the server to convert. Right-click the server, and select Set as source. 2 In the Source Drives section, select the volumes to convert.
Windows P2V Conversions Additional Task Procedures 112 5 In the VM name field, enter the desired name. Caution To avoid errors, please ensure that the VM name is unique within your environment 6 Select Different Destinations Cutover as the Conversion Type. 7 Set the Current Activity field to Initial Conversion - active. 8 In the Transfer mode field, select Block or File. • Block: Block cloning uses an Application Programming Interface (API) from the source OS that allows you to skip unused sectors.
Windows P2V Conversions Additional Task Procedures 113 Step 7: Final Synchronization After the VM has been moved, you will be able to edit the task. 1 In the vConverter Task Pane, select the P2V task. Click the Edit icon . 2 Change the Current Activity field to Final Synchronization- Active. 3 In the Target field, select the new target server. 4 Click Browse to configure the Target folder field. The datastores available to the selected target server will be displayed.
Continuous Protection This chapter guides you through the process of performing Continuous Protection conversions with vConverter. This chapter contains the following sections: Continuous Protection Overview ................................................................... 115 Licensing........................................................................................................ 116 Configuring Continuous Protection ................................................................
Continuous Protection Continuous Protection Overview 115 Continuous Protection Overview You can protect datacenter workloads by addressing disaster recovery (DR) through virtualization. Taking a P2V approach, vConverter preserves a virtual backup copy of a physical machine. When you select Continuous Protection as the conversion type, incremental replication is used. During this process, network usage is minimized because only changes to source data files are transferred to the target.
Continuous Protection Licensing 116 Licensing Continuous protection (Windows only) features are available with a valid license (either a Trial or Perpetual license). There are no features available without a license (either Trial or Perpetual).
Continuous Protection Licensing 117 License Types Supported in vConverter 5.1.1 Support is available for the following: • Trial licenses with 30-day demo period. • Perpetual license (QLL type Ongoing) with no expiration date. No support is available for installations with: • Trial license with an expiration date (no demo period). • Term license (QLL type Ongoing) with a stated expiration date. Overwriting an Existing License An instance of vConverter can have only one license installed at a time.
Continuous Protection Configuring Continuous Protection 118 2 Click Next. 3 Click the Browse icon and browse to the location of the license file. 4 Click Open, then click Next. 5 The Congratulations screen appears. Click Finish. Configuring Continuous Protection The Continuous Protection process is described in the sections that follow. Note that there are multiple optional configurations available. This document is intended only to illustrate the basic functionality.
Continuous Protection Configuring Continuous Protection 119 3 Enter the server information as appropriate. Note If you will be using a Virtual Appliance as a conversion target, you will need to complete the VA Config dialogue. 4 Click Save and Install to save your server configuration. Step 2: Create Setup Folders To convert a Windows system, vConverter requires access to certain files from the Windows installation.
Continuous Protection Configuring Continuous Protection 120 Task Configuration Step 1: Create a Task Folder 1 In the Task List pane of the vConverter interface, right-click and select Create Folder. 2 Right-click on the folder, and click Rename folder. Enter a descriptive name. Step 2: Create P2V/V2V Task 1 Right-click on the task folder, and select Create P2V/V2V task. The Task Properties pane is enabled.
Continuous Protection Configuring Continuous Protection 121 5 In the VM name field, enter the desired name. Note The target VM name can contain upper and lower case letters from the latin alphabet (a-z, A-Z), numbers from 0-9, and the characters "-" and "_". Caution To avoid errors, please ensure that the VM name is unique within your environment. 6 In the Conversion Type field, select Continuous Protection. 7 In the Transfer mode field, select Block or File.
Continuous Protection Configuring Continuous Protection 122 • Select a starting date and time. • Select a synchronization interval. • Select an End by time. To run tasks indefinitely, leave the End by checkbox unchecked. 2 Once scheduled, click the Save icon to save the task. 3 The task will run at the scheduled time. To execute the task manually, click the Start icon.
Linux P2V Conversions This chapter provides information on creating P2V conversions for Linux source systems. A conversion tutorial is provided as an example. This chapter contains the following sections: Linux Conversion Overview ........................................................................... 124 Important Information About Linux Conversions ........................................ 125 Configurations for Linux Conversions............................................................
Linux P2V Conversions Linux Conversion Overview 124 Linux Conversion Overview The Linux P2V process follows the basic workflow described below. The main components of the Linux conversion process are the Migration Tool Package (MTP) and the Post Processing Service (PPS). The MTP is uploaded to the Linux source server, where it prepares and sends the data. The PPS is part of the vConverter Virtual Appliance components installed on the VMware vMA.
Linux P2V Conversions Linux Conversion Overview 125 When a user configures a task and specifies the source server, the Conversion Service receives a command from the GUI Application to collect some needed system information. This is done by uploading into the source server some special daemon programs and executing them. The programs are called Migration Tool Package (MTP). Once the information is collected, the GUI is updated, so user can fill in some specific system settings, e.g.
Linux P2V Conversions Linux Conversion Overview 126 • Cold Mode Conversions: Linux systems may be converted in Cold mode only. The source server is captured in the Cold mode. MTP component runs there remotely, replaces the boot loader and then reboots the host. After rebooting, there are no processes that could change the source disk data, and those data are then passed to the target one-for-one. Therefore, the image is 100% consistent.
Linux P2V Conversions Linux Conversion Overview • 127 ESX Servers simulates a video card device. To enable X Server you need to ensure there is an appropriate video driver. Configurations for Linux Conversions There are several conversion options specific to Linux conversions. These options can be configured in the Conversion tab of the vConverter Program Preferences (Tools>Preferences).
Linux P2V Conversions Creating a Conversion 128 Advanced Linux Conversion Options The Advanced Linux P2V Conversion Options dialogue is shown below. Note This dialogue differs from the Advanced Properties dialogue found on the Task Properties pane. For information on Advanced Task Properties, see “Step 5: Advanced Task Properties” on page 132.
Linux P2V Conversions Creating a Conversion 129 • Setup Folders are not required for Linux P2V. The tasks represented by the red boxes are unique to Linux P2V. Note In the interest of clarity, the entire process is described below. Some steps, such as adding target servers, may not be necessary if you have previously performed basic conversions. The basic configuration tasks are performed via the vConverter Program Preferences dialogue, available at Tools > Preferences.
Linux P2V Conversions Creating a Conversion 130 7 Click Save and Install. Step 3: Add Linux Source Servers Linux servers are not automatically discovered and must be added manually prior to configuring a conversion task. 1 In the Network Browser pane, right-click the Linux Hosts node. 2 Click Add Linux source. 3 Complete the Add a new Linux source system dialogue. Quest recommends using the Secure Connectivity option.
Linux P2V Conversions Creating a Conversion 131 2 Right-click the folder, and click Rename folder. Enter a descriptive name. Step 2: Create P2V/V2V Task 1 Right-click the task folder, and select Create P2V/V2V task. The Task Properties pane is enabled. Step 3: Add Source 1 In the Linux Hosts node of the Network Browser pane, right-click the Linux server you wish to convert. 2 Select Set as source. 3 In the Source Drives section, select the volumes to convert.
Linux P2V Conversions Creating a Conversion 132 3 Click Browse to configure the Target folder field. The datastores available to the selected target server will be displayed. Note When using the Virtual Appliance for VMware as a target, the Use RDM option will be disabled. 4 Select a datastore, and click OK. 5 In the VM name field, enter the desired name. Caution To avoid errors, please ensure that the VM name is unique within your environment.
Linux P2V Conversions Creating a Conversion 133 The VM tab contains several options: Create Virtual Machine Instructs vConverter to create a VM descriptor file and registers the VM in the target environment (ESX Server). Otherwise, only a set of disk image files is created, which you must attach to the VM manually. Power virtual machine ON Runs the VM after the conversion is complete. Applicable only for ESX Server.
Linux P2V Conversions Creating a Conversion 134 VM Options Dialogue Create Floppy Drive This option is disabled for Linux P2V. Create CD/DVD Drive Select this option to create a CD/DVD drive on the target. RAM, MB Configure RAM on the target through this field. Notes This field it auto-populated with “Created by vConverter 5.x.” (text box) You can alter this and include additional text. CPU Count Configure the number of CPUs on the target VM through this field.
Linux P2V Conversions Creating a Conversion 135 X Window Options Dialogue Disable X Window System After conversion, vConverter will disable the X Window System on the target server by setting the runlevel to 3. The VM will boot in the console mode. Leave X Window System enabled and adapt its settings to the Target vConverter will attempt to adapt X Window System settings to the target hardware.
Windows V2P Conversions This chapter guides you through the process of performing V2P conversions with vConverter. This chapter contains the following sections: Windows V2P Overview ................................................................................ 137 Preparing the Target System for V2P............................................................ 139 Creating a V2P Conversion ...........................................................................
Windows V2P Conversions Windows V2P Overview 137 Windows V2P Overview vConverter offers the ability to convert Windows VMs back to a physical target. vConverter uses a VistaPE boot image to boot the physical system, so the target server does not need to have an OS. Once you configure a task and specify the source VM, vConverter obtains the essential information about it using the Conversion Service.
Windows V2P Conversions Windows V2P Overview 138 Important Notes about Windows V2P • Each disk image file from the source VM can be restored to separate physical drive only. Restoring multiple disk images into single target device is not supported. • The V2P conversion overwrites all the data and disk formatting on the target physical device. • Restoring of any kind of dynamic disks is not supported. The Source disk image must have only basic Windows disks.
Windows V2P Conversions Windows V2P Overview 139 Video drivers. Other less critical plug-and-play devices such as USB controllers or video cards are detected by the converted OS after conversion. • When a V2P conversion task finishes, the target system is not powered off automatically. You will need to reboot it manually, either via the Power button or using the VistaPE console window by typing “reboot”. • Volume resizing is not supported with V2P conversions.
Windows V2P Conversions Windows V2P Overview 140 information, see “Adding Drivers to the vConverter PE Image- Device Installer” on page 146. • For NIC and SCSI drivers, modify the VistaPE image to permanently add the desired drivers. For more information, see “Adding Drivers to the vConverter PE Image - Using the WAIK” on page 151. Creating a V2P Conversion The basic Windows V2P configuration process is described in the flowchart below and in the sections that follow.
Windows V2P Conversions Windows V2P Overview 141 Step 2: Create Driver Folder To have a successful conversion, you must supply the appropriate hardware drivers for the target platform. 1 Compile the appropriate hardware drivers for the target platform. You may use the Windows startup disk, or collected drivers (in .INF format). Drivers may be compressed in CAB files. 2 Place the drivers in a network share accessible to the vConverter machine.
Windows V2P Conversions Windows V2P Overview 142 3 Select the desired target server, and right-click. Select Add to systems to convert. or Drag the target server to the Target Server hot spot. 4 The Target field will populate with the target server information. Step 4: Select Source VM 1 In the Network Browser pane, select the Virtual Machines tab. 2 In the Virtual Machines tab, find the VM you wish to convert. Right-click the VM and select Set as source. or Drag the VM to the Source Server hot spot.
Windows V2P Conversions Windows V2P Overview 143 • Select a starting date and time. • Select a synchronization interval. • Select an End By time. 2 Once scheduled, click the Save icon to save the task. 3 The task will run at the scheduled time. To execute the task manually, click the Start icon.
Appendix 1: ISO Image Instructions Using the vConverter VistaPE ISO Image ..................................................... 145 Configuring the vConverter PE Image ........................................................... 146 Adding Drivers to the vConverter PE Image- Device Installer.................... 146 Compatible Drivers ........................................................................................
Appendix 1: ISO Image Instructions Using the vConverter VistaPE ISO Image 145 Using the vConverter VistaPE ISO Image vConverter’s Remote Cold Cloning (RCC) feature automates the cold cloning process by booting the source server using vConverter’s boot image. vConverter sends a boot loader and its boot image over the network and loads them on the source system. vConverter uses these to reboot the source at a time that you designate, and the conversion begins.
Appendix 1: ISO Image Instructions Configuring the vConverter PE Image 146 Obtaining the vConverter PE Image ISO The vConverter PE Image ISO cannot be freely downloaded. To download the PE Image ISO, please contact Quest Server Virtualization support at: support@vizioncore.com Booting to the vConverter PE Image The vConverter PE Image ISO image must be burned to a CD/DVD prior to use. There are many software utilities available, both freely and commercially, for burning an ISO image.
Appendix 1: ISO Image Instructions Configuring the vConverter PE Image 147 install needed drivers from a CD or floppy, or directly from the host’s hard drive. Step 1: Device Installer 1 Connect directly to the host to view the boot environment. 2 Click Start, then Device Installer. Step 2: Network Adapters 3 In either the Network Adapters or Unknown Devices group, select your network adapter. Click Install. The Device Installation dialog appears. 4 Click Ok. 5 Specify the path to the driver.
Appendix 1: ISO Image Instructions Configuring the vConverter PE Image 148 Step 3: Network Configurator 6 Click the whirl icon Note , then PE Network Configurator. If this process fails, then you are using an incompatible driver. For a list of compatible drivers, see Compatible Drivers. Configuring Networking for the vConverter PE Image The Network Configuration Utility is displayed upon booting the vConverter PE image. The utility can also be started from the Whirl .
Appendix 1: ISO Image Instructions Configuring the vConverter PE Image 149 Step 2: Ethernet Adapters The Ethernet Adapters section is shown below: 1 In the network adapters field, select the appropriate NIC. 2 In the Link Speed/Duplex Mode field, select the appropriate mode. Step 3: IP Addresses The IP Addresses section is shown below: 1 If using DHCP, select Obtain an IP address automatically. To configure a static IP, select Use the following IP address.
Appendix 1: ISO Image Instructions Configuring the vConverter PE Image 3 150 If using a static IP, populate the fields as appropriate for your network. Step 4: DNS and WINS Servers The DNS and WINS Servers section is shown below: 1 Select either Obtain DNS Server Address automatically or Use the following DNS Server address. Note 2 If you are using a static IP configuration in Step 2, Obtain DNS Server Address automatically will not be an available selection.
Appendix 1: ISO Image Instructions Configuring the vConverter PE Image 151 Step 5: Network Identification The Network Identification section is shown below: 1 Populate the Computer Name, Workgroup, and Primary DNS Suffix fields as appropriate. Click Set next to each field to save the configuration. Step 6: Save 1 Click Ok. Your network configuration should now be properly set.
Appendix 1: ISO Image Instructions Configuring the vConverter PE Image 152 http://www.microsoft.com/downloads/details.aspx?FamilyID=94bb6e34-d8904932-81a5-5b50c657de08&DisplayLang=en a Click Save or Save this program to your computer. Windows AIK is distributed as an .img file. b Burn the saved img to a DVD. c Insert the DVD into the machine. d Click Windows AIK Setup to begin the installation. 3 Open the Windows command prompt by clicking Start>Run. At the Run line, enter cmd.exe, then click OK.
Appendix 1: ISO Image Instructions Compatible Drivers 153 Step 3: Loading Drivers The VistaPE ISO image has been extracted to the WIM_Mounted_Folder directory and is now available to you for modification. Install necessary drivers using the following command: %WAIKHOME%\Tools\PETools\Peimg.exe" /inf= /image="%WIM_MOUNTED_FOLDER% Where is replaced with the correct path.
Appendix 1: ISO Image Instructions Compatible Drivers Network SiS SiS SiS SiS IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM SONY SONY Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Amertek VIA Technologies, Inc. VIA Technologies, Inc. VIA Technologies, Inc. VIA Technologies, Inc. VIA Technologies, Inc.
Appendix 1: ISO Image Instructions Compatible Drivers VIA Technologies, Inc. VIA Technologies, Inc. VIA Technologies, Inc. VIA Technologies, Inc. VIA Technologies, Inc. VIA Technologies, Inc. VIA Technologies, Inc. D-Link D-Link D-Link D-Link D-Link D-Link D-Link D-Link D-Link D-Link D-Link D-Link D-Link D-Link D-Link D-Link D-Link D-Link D-Link D-Link D-Link D-Link D-Link D-Link D-Link D-Link Corega K.K. Corega K.K. Corega K.K. corega K.K. corega K.K. corega K.K. corega K.K.
Appendix 1: ISO Image Instructions Compatible Drivers 156 GIGA-BYTE TECHNOLOGY CO., GN-FE605 Fast Ethernet Adapter LTD GIGA-BYTE TECHNOLOGY CO., GN-FE605M Management Ethernet Adapter LTD The Linksys Group Inc. EtherFast 10/100 Managed Network Adapter The Linksys Group Inc.
Appendix 1: ISO Image Instructions Compatible Drivers Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel 157 Intel(R) PRO/1000 MT Quad Port Network Connection Intel(R) PRO/1000 MT Server Connection Intel(R) PRO/1000 GT Server Adapter Int
Appendix 1: ISO Image Instructions Compatible Drivers 158 Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Hewlett Packard NEC NEC NEC NEC NEC Acer Acer Acer Acer Fujitsu Siemens Fujitsu Siemens Fujitsu Siemens Intel(R) PRO/100 VM Network Connection Intel(R) PRO/100 P Mobile Combo Adapter Intel(R) PRO/100 P Mobile Adapter Intel(R) 825
Appendix 1: ISO Image Instructions Compatible Drivers Toshiba Toshiba Toshiba Fujitsu Fujitsu Samsung Samsung Trigem Dell Atheros Communications Inc. Atheros Communications Inc. Atheros Communications Inc. Atheros Communications Inc. Atheros Communications Inc. Atheros Communications Inc. Atheros Communications Inc. Atheros Communications Inc. Atheros Communications Inc. Atheros Communications Inc. Atheros Communications Inc. Atheros Communications Inc. Atheros Communications Inc.
Appendix 1: ISO Image Instructions Compatible Drivers Marvell Marvell Marvell Marvell Marvell Marvell Marvell Marvell Marvell Marvell Marvell Marvell Marvell Marvell Marvell Marvell Marvell Marvell Marvell Marvell Marvell Marvell Marvell Marvell Marvell 160 SysKonnect SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter, PCI64, Fiber SX/SC SysKonnect SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter, PCI64, Fiber LX/SC SysKonnect SK-9821 V2.
Appendix 1: ISO Image Instructions Compatible Drivers Marvell Marvell Marvell Marvell Marvell Marvell Marvell Marvell Marvell NVIDIA Realtek Semiconductor Corp. Realtek Semiconductor Corp. Realtek Semiconductor Corp. Realtek Semiconductor Corp. Realtek Semiconductor Corp. Realtek Semiconductor Corp. Realtek Semiconductor Corp. Realtek Semiconductor Corp. Realtek Semiconductor Corp. Realtek Semiconductor Corp. Realtek Semiconductor Corp. Realtek Semiconductor Corp. Realtek Semiconductor Corp.
Appendix 1: ISO Image Instructions Compatible Drivers Broadcom Broadcom Broadcom Broadcom Broadcom Broadcom Broadcom Broadcom Broadcom Broadcom Broadcom Broadcom Broadcom Broadcom Broadcom Broadcom Broadcom Realtek Realtek Realtek Realtek Realtek VIA Networking Technologies Inc ULi Electronics Inc. ULi Electronics Inc.
Appendix 1: ISO Image Instructions Compatible Drivers 3Com 3Com 3Com 3Com 3Com 3Com 3Com 3Com Corporation. 3Com Corporation. Accton Accton Accton Accton Accton Accton Accton Accton Accton Accton Accton Accton Accton Accton Accton Accton Accton Accton Accton Accton Accton Accton Accton Accton Accton Technology Corp. Accton Technology Corp.
Appendix 1: ISO Image Instructions Compatible Drivers Netgear Netgear Netgear Netgear NETGEAR NETGEAR NETGEAR NETGEAR Netgear Netgear NETGEAR NETGEAR Netgear NETGEAR Racore SMC SMC SMC SMC SMC SMC SMC SMC SMC SMC SMC SMC SMC SMC SMC SMC SMC TDK CHEETAH ASIX Electronics ASIX Electronics ASIX Electronics ASIX Electronics ASIX Electronics PCMCIA Technology Inc. PCMCIA Technology Inc.
Appendix 1: ISO Image Instructions Compatible Drivers ADMtek Incorporated AmbiCom Conceptronic D-Link Corporation. Hewlett-Packard Company Hewlett-Packard Company Hewlett-Packard Company Hewlett-Packard Company Hewlett-Packard Company Hewlett-Packard Company Hewlett-Packard Company Hewlett-Packard Company Hewlett-Packard Company Hewlett-Packard Company Hewlett-Packard Company Hewlett-Packard Company Altima Altima Altima Altima Altima Atheros Atheros Atheros Atheros Nobrand AMD Inc.
Appendix 1: ISO Image Instructions Compatible Drivers DAVICOM Semiconductor, Inc. DAVICOM Semiconductor, Inc. DAVICOM Semiconductor, Inc. DAVICOM Semiconductor, Inc. DAVICOM Semiconductor, Inc. DAVICOM Semiconductor, Inc. DAVICOM Semiconductor, Inc. DAVICOM Semiconductor, Inc. DAVICOM Semiconductor, Inc. DAVICOM Semiconductor, Inc. Madge Madge Madge Madge Madge Madge Madge Madge Madge Madge Madge Olicom Olicom Olicom Olicom Olicom Olicom Olicom Olicom CNet Technology, Inc. CNet Technology, Inc.
Appendix 1: ISO Image Instructions Compatible Drivers SURECOM Technology Corp. SURECOM Technology Corp. SURECOM Technology Corp. SURECOM Technology Corp. SURECOM Technology Corp. SURECOM Technology Corp. SURECOM Technology Corp. SURECOM Technology Corp. SURECOM Technology Corp. SURECOM SURECOM Surecom Surecom TRENDware Corp. Silicon Integrated Systems Corp. Silicon Integrated Systems Corp. Silicon Integrated Systems Corp. Silicon Integrated Systems Corp. SMC Networks, Inc. SMC Networks, Inc. U.S.
Appendix 1: ISO Image Instructions Compatible Drivers SCSI / RAID Adapters Promise Technology Promise Technology Promise Technology Promise Technology Promise Technology Promise Technology Promise Technology Promise Technology ULi Electronics Inc. ULi Electronics Inc. DELL DELL DELL DELL DELL DELL DELL DELL DELL DELL DELL DELL DELL DELL DELL DELL DELL DELL Dell Dell Dell Dell Dell Dell Dell Dell Dell Dell LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp.
Appendix 1: ISO Image Instructions Compatible Drivers LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp., LSI Logic Corp.
Appendix 1: ISO Image Instructions Compatible Drivers LSI Logic LSI Logic LSI Logic LSI Logic LSI Logic LSI Logic LSI Logic LSI Logic LSI Logic LSI Logic LSI Logic LSI Logic LSI Logic LSI Logic LSI Logic Intel(R) Corporation Intel(R) Corporation Intel(R) Corporation Intel(R) Corporation Intel(R) Corporation Intel(R) Corporation Intel(R) Corporation VIA Technologies, Inc. VIA Technologies, Inc. VIA Technologies, Inc.
Appendix 1: ISO Image Instructions Compatible Drivers QLogic Broadcom Corporation Mylex Mylex Mylex Mylex Mylex Mylex Mylex LSI Logic Corporation. LSI Logic Corporation. LSI Logic Corporation. LSI Logic Corporation. LSI Logic Corporation. LSI Logic Corporation. LSI Logic Corporation. LSI Logic Corporation.
Appendix 1: ISO Image Instructions Compatible Drivers CMD Technology CMD Technology CMD Technology Compaq Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel Intel PC Technology Silicon Integrated System Symphony Labs VIA Technologies, Inc. VIA Technologies, Inc. VIA Technologies, Inc. VIA Technologies, Inc. VIA Technologies, Inc. VIA Technologies, Inc. VIA Technologies, Inc.
Appendix 1: ISO Image Instructions Compatible Drivers Micron ServerWorks ServerWorks Advanced Micro Devices Advanced Micro Devices Advanced Micro Devices Advanced Micro Devices NVIDIA NVIDIA Standard AHCI 1.
Appendix 2: Third Party Contributions Third Party Contributions ...............................................................................
Appendix 2: Third Party Contributions Third Party Contributions 175 Third Party Contributions This product contains third party components. Copies of their licenses may be found here: http://www.quest.com/legal/third-party-licenses.aspx. Component License or Acknowledgement libxm2.7.3 MIT Log4Net 1.2.10 Apache 2.0 OpenSSH 4.5 Open_SSH SharpSSH 1.1.1.13 SharpSSH 1.0 SharpZipLib 0.85.1.271 SharpZipLib License TinyXml 2.5.3 zlib/libpng license 1.
Index Remote Cold Cloning 24 Support for RDM 26 Synchronized Cutover 25 Task Folders 27 Task Profiles 27 User Profiles 27 V2P for Windows 23 Virtual Appliances 23 A About 10 Quest Software 10 C Continuous Protection licensing 116 overview 115 procedures 118 Conversion Procedures Continuous Protection 118 V2P 137 D Different Destinations Cutover overview 81 procedures 110 P P2V creating a conversion 82 Linux configurations 127 overview 19 procedures 128 procedures 100 Windows overview 17 F Features and
Index S support 11 supported characters P2V 92 V2P 139 Synchronized Cutover overview 80 procedures 107 Systems to Convert tab 85 T technical support 11 text conventions 10 V V2P important notes 138 overview 21 preparing target system 139 procedures 137 vConverter 13 about 8 architecture 13 configuration Conversion tab 47 Email Notifications 48 ESX Servers 53 Task Profiles 59 User Profiles 57 overview 13 user interface 30 Volume Mapping 91 177
