X2V fails with error "Virtual machine not configured according to rules specified in /etc/vmware/configrules"

Administrator — Tue, 19 Jan 2010 07:41:21 GMT

Abstract:

Overview

This article provides an overview with conversions hanging on an ESX host with “RequiresUserIntervention.” Diagnostics from the failed job will reveal the following:

Applies to: PowerConvert

Details

Error Recovery Information:

Starting Virtual Machine (top)

Fdisk on target Linux machine shows ''Partition # does not end on cylinder boundary''

Administrator — Thu, 14 Jan 2010 06:12:21 GMT

Abstract:

Overview

This article explains the reason for message 'Partition X does not end on cylinder boundary' in Fdisk output on target Linux machine.

Details

The above mentioned message in Fdisk output appears on a target Linux machine due to the way PortabilitySuite partitions the Linux volumes on target. Portabilitysuite calculates the disk size based on sectors and not cylinders. It then uses Fdisk to partition the disk based on sector information. Hence, the message in Fdisk output is displayed sometimes.

This behavior is by design.

If you have questions about this article please contact PlateSpin Support at support@platespin.com.

Linux driver injection to ramdisk ISO, X2P Driver package and Source take control package creation

Administrator — Mon, 21 Dec 2009 10:05:53 GMT

Abstract:

Overview

This article provides instructions on how to inject Linux drivers into linux boot ISO file, source take control package and X2P driver manager in PortabilitySuite.

Applies to: PortabilitySuite

Details

Linux Drivers are in the following formats,
1. For kernel 2.4, .o files.
2. For kernel 2.6, .ko files.

Ramdisk Driver Injection Procedure

Note: Bootofxx2p.iso, the Linux boot ISO which supports both 32bit and 64bit architecture is based on SLES10 GA kernel, 2.6.16.21-0.8-default. A Linux driver ties to a specific Linux kernel version. Therefore, in order to inject dr

Inventory of Windows 2003 server does not list disk type for SAN disks

Administrator — Thu, 03 Dec 2009 06:46:46 GMT

Abstract:

Overview

This article provides information about SAN disks on Windows 2003 server not being determined as Fiber Channel in inventory data.

Applies to: Platespin Recon 3.7

Details

One of the new features of Platespin Recon 3.7 is the ability to identify the disk type (Local, SAN) for inventoried machines. This includes all supported platforms except IBM AIX.

As this account is a local account on the machine hosting Portability Suite server, it is unable to authenticate against the domain. This can cause warning logs in security event logs of a domain controller if the machine hosting Portability Suite server is joined to a domain. There will also be instances when use of local accounts is not permitted in highly secure or locked down IT environments.

Resolution

We can change the logon account for PlateSpin services to another account (domain or local) as long as the account is a part of local administrators group on the machine. This will also require similar changes to accounts in IIS which is used by the product.

Note: Please ensure that no jobs are running when the changes are made to switch accounts for PlateSpin services. The account used to replace PortabilitySuite account MUST have local administrator rights on the machine.

Instructions on changing the accounts for services installed by Portability Suite server:

1. Open computer management console and click Services under Services & Applications in right panel to list all services in the left panel. (Alternatively, "Start > Run > Ser

Minimum system requirements for a source machine?

Administrator — Wed, 18 Nov 2009 05:51:39 GMT

Abstract:

Overview

This article outlines the minimum system requirements for the source machines that will be converted by PowerConvert (applies to Windows source systems and Linux source systems).

Applies to: PowerConvert and PortabilitySuite

Details

Minimum Source Hardware Requirements:

For Windows:

Intel and AMD compatible systems
166 MHz or higher processor
256 MB or higher RAM (512 MB recommended*)
300 MB available disk space on the system drive (500 MB recommended)
*Extra 256 MB of free disk space is required if memory is less than 512 MB

For Linux:

Intel and AMD compatible systems
166 MHz or higher processor
128 MB RAM or higher for Linux
50 MB available disk space (25 MB in /tmp & 25 MB in /usr)

If you have questions about this article please contact PlateSpin Support at support@platespin.com

How does Powerconvert/PortabilitySuite handle teamed NICs on source workloads

Administrator — Wed, 28 Oct 2009 12:18:30 GMT

Abstract:

Overview

This article explains how Powerconvert/PortabilitySuite handles teamed NICs on source workloads during conversion jobs.

Applies to: Powerconvert/PortabilitySuite/Forge

Details

Powerconvert/PortabilitySuite discovers all NICs that bind to TCP/IP, be it teamed or not. If all physical NICs are teamed on the source machine, then the teamed interface (also called virtual interface) is discovered as the only interface. If there are some NICs in a team and ot

How to perform a test restore to bring up the target VM in production

Administrator — Wed, 28 Oct 2009 09:36:59 GMT

Abstract:

Overview

This article outlines the recommended steps if running a Test Restore in a production environment is required.

Applies to: PowerConvert & Portability Suite

Details

It is recommended to run Test Restores for DR contracts in an isolated network to prevent adverse effects to the production environment.

If a Test Restore is run in a production environment without following the steps in solution section, there is a possibility that the source server's computer account in Active Directory (AD) will be moved to the target virtual machine being restored. This can cause problems in a production domain.

Solution

Steps to follow while performing a test restore to bring up the target VM in production:

1. Specify a hostname, within the Network Identification section, that is different from the source hostname when setting up the protection contract. This hostname will be used by the target VM for testing.

2. Run incremental conversions as normal.

3. Run a Test Restore. At this point the target VM will contact the domain with the new hostname set in Step 1. This new hostname will appear in AD as a new computer account.

4. Power off VM to finish the Test Restore. The newly created computer

[Internal] How to failback to original physical hardware (X2P) using Server Sync option

Administrator — Tue, 20 Oct 2009 12:18:41 GMT

Abstract:

Overview

This article explains the method (Server sync) used to failback to original physical machine (X2P).

Applies to: PowerConvert, Portability Suite and Forge.

Details

Administrator — Wed, 09 Sep 2009 13:27:55 GMT

Abstract:

Overview

This article discusses mounting the winperamdisk.iso file for a target physical server migration and it freezing during startup. The screen may read “Starting Windows Preinstallation Environment,” however it will not progress. The screenshot below may be similar to the issue discussed in this article.

Applies to: PowerConvert 7.0 and above

Installing PostgreSQL to a different volume when installing PowerRecon/Platespin Recon

Administrator — Tue, 04 Aug 2009 09:40:18 GMT

Abstract:

Overview

This article discusses the steps required to install PostreSQL to a volume different than the one specified for the PowerRecon 3.0 installation.

Applies to: PowerRecon v3.0 and higher

Details

The steps are different based on the version of PowerRecon which in turn uses different versions of PostgreSQL.

PowerRecon 3.0 - 3.3 (PostgreSQL 8.2)

1. Execute PowerRecon installation executable (PlatespinPowerRecon.exe) file and extract the contents to a local folder. By default, it extracts to "C:\Documents and Settings\<UserProfile>\Local Settings\Temp\".

2. Locate "Powerrecon2_0.hta" file in the path above and edit it in notepad.

3. Change the installation path in the following string to the desired one:

strCmdLine = strCmdLine & " BASEDIR=" & """" & "%ProgramFiles%\PostgreSQL 8.2" &

For e.g., path to E: will be "E:\Program Files\PostgreSQL 8.2"

4. Run "PowerRecon2_0.hta" from extraced files and perform the installation normally.

PowerRecon 3.5 and higher (PostgreSQL 8.3)

1. Execute PowerRecon installation executable (PlatespinRecon-<version.build>.exe) file and extract the contents to a local folder. By default, it extracts to "C:\Documents and Settings\<UserProfile>\Local Settings\Temp\".

2. Explore the folder named "PostgreSQL" and locate "SETUP.bat" and edit it in notepad. Change the installation locat

Installation error "System.Exception: Enforce FIPS enabled but the machine.config is missing the machineKey element"

Administrator — Fri, 31 Jul 2009 05:18:53 GMT

Abstract:

Overview

During the installation of PowerConvert, the following error may be found in the PowerConvert_CustomActions.log file.

Error: System.Exception: Enforce FIPS enabled but the machine.config is missing the machineKey element

Applies to: PowerConvert 6.8.0 and higher

Details

The above error "error running a custom action” is caused when FIPS security is enabled on the server, but the .NET machine.config file does not reflect this.

To resolve this issue:

If FIPS encryption is&nb

Unable to protect a windows source with volume mounted to a folder

Administrator — Mon, 27 Jul 2009 07:18:03 GMT
Abstract:
Overview

When protecting a Windows source machine with a volume that is mounted to a folder without a drive letter assigned, the validation under drive configuration section fails and prevents the job from starting.

Applies to: Portability Suite 8.1

Details

Mounted volumes are not supported for Snapshot or Block-based protection contracts. However, these are supported for one-time conversions.

If you have questions about this article please contact PlateSpin Support at support@platespin.com

I2P of Windows Vista 64-bit gives recoverable error when configuring target OS

Administrator — Mon, 27 Jul 2009 07:16:45 GMT
Abstract:
Overview

When deploying Windows Vista 64-bit Platespin image to target physical machine, job goes into recoverable error at step 6.1, "Configure Operating System". The error info displayed is as under:
ConfigurationServiceNotStarted
The Configuration service in the target machine does not seem to have started

Details

The conifguration service on target VM has not started because the VM cannot boot. The status of the target VM could be either of the following:

1. It goes to the Windows advanced boot options screen where any boot option (normal boot, last good, safe mode, etc) can be selected. When any option is selected (or 30 seconds expire) it tries to load Windows, but instead restarts and returns to the same screen again.
2. It starts up and shows a blue screen with stop 7B error.
The issue is specific to a particular device controller (Broadcom HT1000 SATA) on target physical machine. The underlying cause is that the installation of driver for Broadcom HT1000 SATA Controller failed.

Resolution

Awaited

Conversion to target host Xen Server throws error when creating target virtual machine

Administrator — Wed, 22 Jul 2009 06:08:50 GMT
Abstract:
Overview

Conversion to a target XenServer host machine with teamed NIC will go into recoverable error state if the target VM was configured with teamed NIC interface.

Applies to: Portability Suite 8.1.0

Details

This issue will occur if both the following conditions are true:
1. Configure an X2V conversion job to a target host Xen Server with 2 or more teamed NICs.
2. During configuration of target VM's network, map the virtual NIC to the teamed network of host XenServer.
Start the conversion job and let it progress till target VM is created and configured. The job will go to recoverable error state with following error:
Virtual Machine 'VM Name' could not be started, either because no host is available or its configuration is invalid. Internal message: 'Failure in XenDotNetLibrary: NO_HOSTS_AVAILABLE ()'.
This error message is not specific though. When you try to reproduce the issue by manually creating a VM with it's virtual NIC mapped to teamed virtual network and then start it, the error is more descriptive (as below):

Host cannot attach network. This may be because attaching the network on this host would require other networks that are currently active to be taken down.

Solution

The solution to this problem is to power down one or more VMs using either of the networks specified in the team network. This will allow the VMs using either of the networks in the teamed network to be turned on then.

Post conversion action on Windows 2000 does not return batch script's exit code

Administrator — Tue, 21 Jul 2009 05:17:10 GMT
Abstract:
Overview

When running post conversion batch files/scripts on a windows 2000 operating system, expected exit code is not being returned.

Applies to: Portability Suite 8.1

Details

This issue occurs only when running batch files that return exit codes using the following syntax on Windows 2000 as part of post conversion:

EXIT /B n (where 'n' represents the exit code and is a numerical value)
Instead of the expected exit code as specified in the batch file, it always returns a 0 (zero)
This issue happens on Windows 2000 because of some peculiarities in the default command shell that executes batch files. It works fine in Windows 2003 & 2008 versions.

Workaround

Use following syntax to return exit codes:
EXIT n (where 'n' is a numerical value)

If you have questions about this article please contact PlateSpin Support at support@platespin.com.

Conversion of Windows 2003 x64 virtual machine stalls during configuration or target OS

Administrator — Thu, 16 Jul 2009 11:12:57 GMT
Abstract:
Overview
Conversion of Windows 2003 x64 virtual machine stalls during configuration of target OS

Applies to: Portability Suite 8.1.0

Details
This issue occurs when the source operating system is a Windows 2003 64-bit (German) virtual machine hosted on Xen on SLES 10 and is being migrated to target host XenServer 4.1
Check the target VM and it will show a dialog box requesting user permission to reboot like in the screehshot:

Block Based Transfer Bandwidth Throttling and Compression

Administrator — Fri, 26 Jun 2009 05:54:52 GMT
Abstract:
Overview
This article provides information about Bandwidth Throttling and Compression when used for Block Based Transfer conversions.
Applies to: PowerConvert 7 and above

Details
When performing Block Based conversion using PlateSpin PowerConvert / Portability Suite the option to set Compression and Bandwidth Throttling of the Block Based data is a value which applies per volume being converted and not to the entire conversion.
For example:
· If you set the value for Throttling is set to ‘1024’ which means that you want to throttle the Block Based data transfer to 1 Mbps this will actually place a throttle limit of 1 Mbps p

Symantec Endpoint Protection - Network Threat Protection prevents discovery

Administrator — Thu, 18 Jun 2009 12:00:07 GMT
Abstract:
Overview

This article explains the reason for discovery failure when Symantec Endpoint Protection is running on the machine being discovered.

Applies to: Portability Suite 8.0 and above

Details

Discovery will sometimes not start and throw an error as seen in the screenshot below:

The machine being discovered is running Symantec Endpoint Protection. Network Threat Protection logs show that connections from the Portability Suite Server were blocked.

Solution

Turn off Network Threat Protection in Symantec Endpoint Protection and discover the machine. Alternatively, Symantec Endpoint Protection can be configured to allow traffic (inbound & outbound) from the PortabilitySuite server. This will require adding a rule in "Configure Firewall Rules" option in Network Threat Protection.

/export/home/<sudo user>) and executes it to find out host machine's OS platform by running uname command. Once this info is retrieved, the script is deleted from the directory.
2. Create a directory under /tmp (/tmp/<recon server name + unique id>/bin) and copy binary files for discovered OS platform from PowerRecon server.
3. Execute binaries for inventorying the machine. The output is returned in an XML file that is streamed back to PowerRecon server.

(B) Actions performed by PowerRecon server during montioring:

1. Copy "solinfo.sh" script to user's home directory (/export/home/<sudo user>) using scp and executed. This queries the performance counters using various commands (See Table 1 below).

2. Data being collected is streamed back via SSH and no data is written to any files on the host.

(C) Directories accessed by PowerRecon when inventoring or monitoring Solaris machines:

Read Only access: /etc/, /usr/lib/, /usr/share/, /usr/local/, /lib/, /dev/, /proc/

Write access: /export/home/<sudo user>

Change the IP address of machine hosting PowerConvert/PortabilitySuite server

Administrator — Tue, 14 Apr 2009 05:40:00 GMT
Abstract:
Overview
This article is intended as a guide on the steps required to ensure proper functionality for PlateSpin PowerConvert/PortabilitySuite if the IP address of the machine hosting the application has changed.
Applies to: PowerConvert 6.0 to 7.0, PortabilitySuite 8.0 & higher.

Details
For PowerConvert version 6.0 - 7.0
When changing the IP address of PowerConvert Server, following steps are required to ensure that PowerConvert continues to operate properly:
Close the PowerConvert Client console.
Stop PlateSpin Operations Framework Controller service.
Open following file in Notepad: "C:\Program Files\PlateSpin PowerConvert Server\Web\Web.config".
Ensure that the following string indeed refers to the server as 'localhost':

<add key="OperationsFrameworkServer" value="http://localhost:80/ofxweb" />

Ensure that the following string refers to the correct server name or IP without brackets:

<add key="ConnectionString" value="server=[SERVER-NAME-OR-IP]\PLATESPINCONVERT;database=powerconvert;user id=sa;password=bourne" />

Open following file in Notepad: C:\Program Files\PlateSpin PowerConvert Server\OfxWeb\Web.config
Ensure that the following string refers to the correct hostname or IP address of PowerConvert server (without brackets):

<add key="ConnectionString" value="server=[HOSTNAME-OR-IPAddress]\PLATESPINCONVERT;database=ofx;user id=sa;password=bourne" />

Open the following file in Notepad: "C:\Program Files\PlateSpin PowerConvert Server\Controller\OfxController.exe.config".
Ensure tha

Portability Suite - X2V conversion fails with HttpsFailedToPutFile when preparing files on target

Administrator — Wed, 08 Apr 2009 13:22:01 GMT
Abstract:
Overview
This article outlines how to resolve the error below when taking control of the target virtual machine:
Preparing Files
Type RequiresUserIntervention
ReportCode HttpsFailedToPutFile
KB Link http://support.platespin.com/kb2/login.aspx?errorCodes=HttpsFailedToPutFile
Name Failed to put file from C:\Program Files\PlateSpin Portability Suite Server\Controller\Packages\0\c5506436-36fd-44df-860c-156284138bd5\1\winpe.iso to https://<ESX SERVER>/folder/platespin/portabilitysuite/<ESX USER>/<PLATESPIN SERVER>/<PLATESPIN GUID>/packages/c5506436-36fd-44df-860c-156284138bd5/1/winpe.iso?dsName=<ESX SERVER>
Reason The operation has timed out
Message Https put file failed: Failed to put file from C:\Program Files\PlateSpin Portability Suite Server\Controller\Packages\0\c5506436-36fd-44df-860c-156284138bd5\1\winpe.iso to https://<ESX SERVER>/folder/platespin/portabilitysuite/<ESX USER>/<PLATESPIN SERVER&

What process does PowerRecon use to identify unique machines

Administrator — Thu, 02 Oct 2008 16:13:51 GMT
Abstract:
Overview
This article discusses how machines are determined to be unique within PowerRecon inventory.
Details
In the inventory process for PowerRecon, machine-uniqueness is based on serial number and SMBIOS UUID.

This information is stored in the BIOS, and may be susceptible to change after a firmware upgrade/update on the BIOS.
This is important to note, because if the SMBIOS UUID or Serial Number change on a server during it’s monitoring lifetime, a re-inventory of this machine will cause it to be inventoried as a new machine. This can consume more licenses than required as well as split the monitoring data, thus making it difficult for charting and reporting.

Last incremental snapshot remains after the target is restored

Administrator — Wed, 24 Sep 2008 12:56:50 GMT
Abstract:
Overview:

Snapshot from last incremental job is not deleted after restoring the target VM. It is listed in virtual host

Details:

After setting up a protection contract and running incremental synchronization jobs, a snapshot from the last incremental is saved. When we restore the target to end the protection contract, the last snapshot should be removed if the target restoration completed. However, the last snapshot is not deleted and remains on the target virtual host.

<

How to run PowerConvert diagnostics and what information it gathers

Administrator — Thu, 10 Apr 2008 11:51:26 GMT
Abstract: Overview
This article discusses how to run PowerConvert diagnostics against a failed, recoverable, or completed job and send the resulting files to support.
Details
PowerConvert allows for diagnostics to be run against any job in PowerConvert. The PowerConvert diagnostics are used by PlateSpin Support to help diagnose issues with conversion jobs. They collect information regarding the source, target and PowerConvert server along with the specifics of how the job was configured. The information is then packaged into a ZIP or DIG file which should be sent to PlateSpin Support when opening a new case.
The PowerConvert diagnostics gathers the following information.
Windows Source Server
Manufacture of Hardware
Model
SMBIOS UUID

Where are the KB Articles?

Administrator — Wed, 24 Aug 2005 05:47:40 GMT
Abstract:
To access the PlateSpin KB articles please select the login tab at the top of the page and enter the knowledge base credentials that were provided to you with your license key. If you do not have your credentials please contact support@platespin.com.

InstantKB.NET v1.3 Knowledge Base

How to run PowerRecon Diagnostics and what information it gathers.

Unable to start Virtual Machine

X2V fails with error "Virtual machine not configured according to rules specified in /etc/vmware/configrules"

Fdisk on target Linux machine shows ''Partition # does not end on cylinder boundary''

Overview

Details

Linux driver injection to ramdisk ISO, X2P Driver package and Source take control package creation

Overview

Details

Ramdisk Driver Injection Procedure

Note: Bootofxx2p.iso, the Linux boot ISO which supports both 32bit and 64bit architecture is based on SLES10 GA kernel, 2.6.16.21-0.8-default. A Linux driver ties to a specific Linux kernel version. Therefore, in order to inject dr

Inventory of Windows 2003 server does not list disk type for SAN disks

Resolution

Minimum system requirements for a source machine?

How does Powerconvert/PortabilitySuite handle teamed NICs on source workloads

How to perform a test restore to bring up the target VM in production

Overview

Applies to: PowerConvert & Portability Suite

Details

Solution

[Internal] How to failback to original physical hardware (X2P) using Server Sync option

Installing PostgreSQL to a different volume when installing PowerRecon/Platespin Recon

Overview

Applies to: PowerRecon v3.0 and higher

Details

Installation error "System.Exception: Enforce FIPS enabled but the machine.config is missing the machineKey element"

Overview

Details

Unable to protect a windows source with volume mounted to a folder

Overview

Applies to: Portability Suite 8.1

Details

I2P of Windows Vista 64-bit gives recoverable error when configuring target OS

Overview

Details

Resolution

Conversion to target host Xen Server throws error when creating target virtual machine

Overview

Applies to: Portability Suite 8.1.0

Details

Solution

Post conversion action on Windows 2000 does not return batch script's exit code

Overview

Applies to: Portability Suite 8.1

Details

Workaround

Conversion of Windows 2003 x64 virtual machine stalls during configuration or target OS

Overview

Applies to: Portability Suite 8.1.0

Details

Block Based Transfer Bandwidth Throttling and Compression

Overview

Details

When performing Block Based conversion using PlateSpin PowerConvert / Portability Suite the option to set Compression and Bandwidth Throttling of the Block Based data is a value which applies per volume being converted and not to the entire conversion.

Symantec Endpoint Protection - Network Threat Protection prevents discovery

Overview

Details

Solution

Change the IP address of machine hosting PowerConvert/PortabilitySuite server

Overview

Details

Portability Suite - X2V conversion fails with HttpsFailedToPutFile when preparing files on target

Overview

What process does PowerRecon use to identify unique machines

Last incremental snapshot remains after the target is restored

How to run PowerConvert diagnostics and what information it gathers

Where are the KB Articles?