When there are identified scenarios and servers to deploy, you can implement the consolidation and protection by using PlateSpin Portability Suite. You can implement an entire scenario, separate containers within the scenario, or individual servers in the scenario.
PlateSpin Recon supports PlateSpin Migrate 9.1, 9.0.1, 9.0.2, and 9.0.0 in addition to PlateSpin Portability Suite 8.0.0, 8.1.2, and 8.1.3.
PlateSpin Recon supports ESXi 5.0, however PlateSpin Migrate does not support it. If you use PlateSpin Recon to create a job for ESXi 5.0 target machine, the job cannot be executed on the PlateSpin Migrate server.
PlateSpin Recon 64-bit applications supports only PS migrate 9.1 for job creations.
To implement a scenario:
In the Project Explorer, right-click the scenario, then select.
The Implementing scenario <name> using Portability Suite Step 1 of 2 dialog box is displayed.
Confirm theand .
Use the drop-down list to select or create the credentials that Portability Suite uses to discover and convert the servers within the scenario or container.
Specify the directory where the Portability Suite jobs must be saved.
The Step 2 of 2 dialog box is displayed.
A table drops down where a match column is displayed.
If you are attempting to consolidate multiple containers, the mapping of container to target server is one-to-one. Unavailable containers that are already mapped to a server are dimmed. When they are either unmapped or the scenario they are in is deleted, they are once again made available.
When the job is initiated, PlateSpin Recon:
Authenticates the servers.
Creates and runs server discoveries for Portability Suite.
Creates and saves conversion jobs in the file location specified in Step 1. The default location is c:\temp.
When the job completes, you can copy the saved conversion jobs to the Portability Suite machine and load it by using PlateSpin Portability Suite Client window (> ).
The steps to implement at the “phantom” (server template), or existing target server level, are identical to implementing a scenario: right-click the phantom or existing target virtual machine server and select.
If a phantom server represents an existing target virtual machine server, you can map it to that existing server. When the job is created through Portability Suite, the source and target servers are auto-configured.
To map a phantom to a target virtual machine server and deploy it:
Right-click the phantom and select.
The Server Mapping dialog box is displayed, listing the available servers that contain virtual machines. Data is listed for each machine, and the match column indicates whether or not the machine is a match to the phantom.
Failure: The processing power of the destination server is less than the processing power of the source server.
Warning: The destination server has more processing power than is necessary. A warning is displayed if the processing power of the destination server is 500 Mhz greater than the processing power of the source server.
Pass: The CPU match is acceptable.
Failure: The disk space on the destination server is less than the disk space on the source server.
Warning: The disk space on the destination server is higher than necessary. A warning is displayed if the destination server has more than 50 GB of surplus space compared to the source server.
Pass: The disk match is acceptable.
Failure: The destination server has less memory than the source server.
Warning: The destination server has more memory than is necessary. A warning is displayed if the memory on the destination server is 512 MB greater than the memory on the source server.
Pass: The memory match is acceptable.
In the Server Mapping dialog box, select the target virtual machine server to map the phantom to, then click.
Right-click the newly mapped phantom and select.