Planning the Destination for a Physical Server to Virtual Server Project

For a P2V project:

1. Choose destination server candidates using either of the following options:

   • Click Use New (Phantom) Servers if you plan to use destination servers that have yet to be provisioned or purchased, then select either of the following options:

     • Use Oracle Engineered System and click the search icon to select an appropriate configuration type for an Exalogic Elastic Cloud system.

     • Use Generic Servers and provide the estimated CPU capacity if available; otherwise, click the search icon next to the CPU capacity input field, then select a server configuration that most closely matches your needs.

       Adjust the memory and storage estimates as necessary.

       In a virtual environment, you can also specify a quantity of the resource to be set aside (reserved) for use by supervisory software in the database machine. This quantity is subtracted from the total capacity of the destination before consolidating source servers into the remaining resource. For example, if your estimated memory requirement is 12 GB and you specify a reserve of 2 GB, only 10 GB is available for consolidation.

       Host Consolidation Planner will determine how many destination servers are required as part of the consolidation results.

   • Click Use Existing Servers to specify a set of existing managed servers to use as destinations.

     These are the servers you specified when defining the scope for the consolidation project. Host Consolidation Planner will determine the available hardware resources based on collected usage data.

     By default, the consolidation process will try to use as few destination servers as possible. If you prefer, choose to balance the source load across all destinations.

2. Accept the defaults or edit the percentages for Maximum Allowed Resource Utilization on Destination Servers. Contrast these allowances, which provide headroom on destination servers, with the scale factor, which provides headroom for individual source servers.
3. Click Next to map the source servers to the destination servers.