Planning the Destination for a Physical Server to Physical Server Project

For a P2P 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 one of the following options:
     • Use Oracle Engineered System and select either Exadata Database Machine or Exalogic Elastic Cloud. Click the search icon and select a configuration type appropriate to either choice.
     • 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.
     • Use Oracle Compute Cloud and select the cloud computing configuration, or shape, to use as the destination.

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

     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. If you did not explicitly specify destination candidates, all source servers are potential destinations for consolidation.

     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.