This page describes the availablemigration preferences for servers inMigration Center.

Google Cloud options

Specify the target product to which you would like to migrate yourinfrastructure. You can specify eitherNo preference, or one of thefollowing products:

• Google Compute Engine
• Google Cloud VMware Engine

If you selectNo preference, Migration Center provides you withrecommendations based on the internal default preference logic, which mightbe updated periodically.

The target product you select and the preferences you set are used to generatethe TCO report.Migration Center also lets you customize the preferences for the othernon-selected products, which are used to generate the license report.

Google Compute Engine preferences

If you select Compute Engine as your target product, first select fromone of the following tenancy preference modes:

• Multi-tenant (default)
• Sole-tenant (dedicated physical Compute Engine servers)

The following table summarizes the differences between multi-tenant andsole-tenant modes:

Select sole-tenant nodes if you need to keep your VMs physically separatedfrom VMs in other projects to meet security or compliance requirements, or forWindows bring-your-own-license (BYOL) scenarios that require per-core orper-processor licenses.

VM tenancy preferences

For more information, seeAbout VM tenancy.

After you select your tenancy preference, specify your preferencesfor machine series, disk types, and licensing options. These selections areused to generate your TCO reports.

Storage configuration

You can customize your VM configuration by configuring the followingoptions:

• ForStorage pool preference (Preview), select your preference for usingHyperdisk Storage Pools to provision storage capacity in a single pool for multiple Compute Engine VMs. This preference can help reduce cost and improve operational efficiencies for large-scale storage. Select one of the following options:
  • Automatic, cost balanced: let Migration Center automatically determine whether to include Hyperdisk Storage Pools or individual Hyperdisks to achieve a lower total cost of ownership (TCO) for your workloads. Migration Center recommends Hyperdisk Storage Pools only if the cost is not more than 25% higher than individual Hyperdisk volumes; otherwise, recommends individual Hyperdisk volumes. This is the default selection.

    If you selected sole-tenant nodes as the target, theAutomatic, cost balanced option recommends Hyperdisk Storage Pools even if they are more expensive than individual Hyperdisk volumes. If you are migrating to sole-tenant nodes, we recommend that you selectNever.

  • Always: always recommend Hyperdisk Storage Pools for all compatible VMs.
  • Never: don't recommend Hyperdisk Storage Pools.

  To account for storage savings achieved through compression and deduplication, adjust theStorage pool compression factor slider. Using a higher value for this setting helps lower your TCO when using Hyperdisk Storage Pools.

• ForDisk type, select your preferred disk type.

Depending on the machine series and disk type that you select,Migration Center might not recommend all of the machine anddisk combinations that you selected.For example, Google Cloud Hyperdisk volumes are only available in certainmachine series. If you select only Hyperdisk volumes asyour migration preferences, Migration Center only recommends machineseries that support Hyperdisk volumes.

If you select a machine series that is not available in yourpreferred region, Migration Center doesn't recommend it.If you don't see a machine or disk combination that you expected,review thepricing page to verify if thecombination is available in your preferred region.

OS license type and pricing track

Select your preferences for licensing and pricing track for Windows Serveror specific Linux distributions.

Windows Server

ForWindows Server, if you selected sole-tenant node forCompute Engine, you can bring your own licenses (BYOL), orselect pay-as-you-go (PAYG) licenses from Google Cloud. If youselected multi-tenant node for Compute Engine, you can only use PAYGlicenses. PAYG licenses are charged on-demand. If you select BYOL, you are notcharged for licenses in Migration Center.

By default, Compute Engine runs two vCPUs on each physical coreusing Simultaneous Multithreading (SMT).This means that for each physical core in your target environment runninga Windows workload, you pay for two Windows licenses, which are appliedper vCPU.

To reduce the costs of your target servers, you can choose to disableSMT. Migration Center lets you specify one of the followingoptions for SMT to balance license costs and performance:

• Auto: Let Migration Center choose the cheapest among the available options. This is the default.
• Enable: Leave SMT enabled as per default, and calculate the costs of two licenses per physical core.
• Disable: Disable SMT on the physical CPUs to save on the license costs. This might impact the performance of your servers.
• Disable with compensation: Disable SMT on the physical CPUs, but compensate for the missing vCPUs, for example by increasing the target number of CPUs, or by switching to a machine family with higher performance.
• No preference: Use Migration Center default preference algorithm.

When you apply this preference, consider the following:

• Your SMT preference is applied on top of rightsizing. Therefore, if you selectDisabled,Disabled with compensation orAuto, this might increase the target utilization above the target utilization that you set for rightsizing.
• If there is no target VM series that is compatible with the selected SMT preferences, then the SMT preference is ignored.

For more information about SMT in Compute Engine, seeSet the number ofthreads per core.

Linux distributions

For Red Hat Enterprise Linux (RHEL), SUSE Linux Enterprise Server (SLES),and SUSE Linux Enterprise Server (SLES) for SAP, you can bring your ownlicense (BYOL), or use pay-as-you-go (PAYG) licenses from Google Cloud.If you select BYOL, you are not charged for licenses.

If you use PAYG licenses, select one of the following pricing tracks:

• On demand: the standard pricing model where you pay for licenses that you consume without any long-term contract or commitment.
• 1-year committed use discount (CUD): a 1-year commitment, payable monthly in USD.
• 3-year committed use discount (CUD): a 3-year commitment, payable monthly in USD, with a higher discount than 1-year CUDs.

Google VMware Engine preferences

If you select VMware Engine as your target product,specify the requirements for the group of virtual machines allocated acrossVMware Engine nodes.

For more information about Committed use discounts for VMware Engine,seeCommitted use discounts.

VMware Engine service type

Choose how you plan to manage the license by selecting one of theavailable options:

• Fully licensed: The fully integrated VMware Engineservice, which includes all of the hardware, software, support,lifecycle management (such as patching and break fixes), as well as physicalhosting environment (power and cooling, rack/stack) for the fullVMware private cloud environment.This doesn't entitle the customer to a perpetual ownership of theVMware Cloud Foundation software, but rather, it is sold as a service,similar to other Google Cloud products.

• Portable License: Broadcom and Google Cloud support license portabilityof VMware Cloud Foundation to VMware Engine.In this model, customers can purchase subscriptions of the newVMware Cloud Foundation software from Broadcom and Broadcom partners,and flexibly use those subscriptions on VMware Engine,as well as on their own on-premises data centers.The remainder of the service (hardware, hosting environment, support,lifecycle management) is purchased directly from Google Cloud orGoogle Cloud partners.

VMware Engine Protected

Select if you want to useVMware Engine Protectedto enable backup and disaster recovery on your VMware Enginenodes.

VMware Engine Protected increases the costs in yourTCO report and might not be available in all regions. For more information,seeBackup and DR Service pricing.

vSAN FTT RAID policy

Select a vSAN storage policy. This policy defines the failures to tolerate (FTT)and the failure tolerance method. Select from one of the following options:

• No preference: a vSAN storage policy is not set.
• No Fault Tolerance: no replicas. Node failure might cause data loss.
• FTT=1, RAID=1: 1 replica. Can tolerate a single node failure. Minimum 3nodes per cluster.
• FTT=1, RAID=5: 1 replica. Can tolerate a single node failure with lowerdisk overhead. Minimum 4 nodes per cluster.
• FTT=2, RAID=1: 2 replicas. Can tolerate failures in 2 nodes. Minimum 5nodes per cluster.
• FTT=2, RAID=6: 2 replicas. Can tolerate failures in 2 nodes with lowerdisk overhead. Minimum 6 nodes per cluster.
• FTT=3, RAID=1: 3 replicas. Highest safety with high disk overhead.Minimum 7 nodes per cluster.

For more information, seevSAN storage policies.

Advanced settings

To further customize your VMware Engine migration preferences,you can configure settings such as CPU, memory, and storage optimization.

To configure compute settings, modify one or more of the following options:

• CPU core overcommit ratio: specify an overcommit ratiobetween1.0 and8.0, with0.1 increment. The default value is4.Overcommitment lets you allocate more memory and CPU cores on your VMsthan what is available in the physical nodes.

• Memory overcommit ratio: specify the following values:1.0,1.25,1.5,1.75 and2.0. The default value is1.

• Hyperthreading weight: specify the CPU performance boost appliedto this cluster nodes. The default is25%.

• HCX mesh: Increases the amount of management resources, CPU, memory,and storage required by the VMware HCX (Hybrid Cloud Extension) cluster.By default, HCX mesh is enabled.

• NSX-T Edge size: configure the CPU, memory, and storage resources allocatedin a VMware NSX-T environment.

  Large is recommended for most production deployments. Extra large isfor the most demanding throughput and latency requirements.

• Storage optimization: configure the storage optimization performance.

  We recommend that you selectCompression because it balances savings andoperational resiliency for most use cases.Deduplication and compressionmight yield cost savings, but you must consider performance implications beforeyou select this option.

  If you select deduplication and compression, theStorage savings ratiosetting lets you specify the amount of storage that you expect to save when youmigrate to Google Cloud, based on your current on-premises values. Thedefault value is1.7.

Sizing and network preferences

Configure sizing recommendations and network preferences for your migratedassets.

Target sizing strategy

ForSizing method, configure how Migration Center recommends VM sizesfor your migrated assets. You can set the sizing method, utilization targets,and defaults for assets that lack performance data.

• No rightsizing: choose a target VM size that closely match the sizeof your current machines.The algorithm doesn't apply rightsizing, which means that it doesn'tconsider the current performance data of your machines.
• Moderate (default): calculate your target VM size based on the currentperformance of your machines, and apply moderate rightsizing to your VMs.This approach balances between performance and cost.
• Aggressive: calculate your target VM size based on the currentperformance of your machines, and apply aggressive rightsizing to your VMs.For example, if you underutilize your machine CPU,your TCO report will suggest a VM with fewer CPUs.This approach maximizes the use of the VM's resources and reduces costs,but might also impact performance in the event of an unexpected load.
• Custom: manually configure the parameters that you want the algorithmto use for the calculations. When you choose the custom sizing optimization,you can change the following parameters:
  • Metrics baseline: the baseline for calculating memory, CPU, and disk IOPS.
  • Storage multiplier: the amount of storage that you want to provision in yourinfrastructure, as a proportion of the current storage utilization.
  • CPU usage: the CPU utilization that you want to have in your infrastructure,as a percentage of the current utilization.
  • Memory usage: the memory utilization that you want to have in yourinfrastructure, as a percentage of the current utilization.

The following table shows the calculation parameters for theModerateandAggressive optimization strategies.

Source utilization estimated defaults

Migration Center prioritizes actual performance data when generating sizingrecommendations. For assets where granular performance data is unavailable, youcan set utilization estimates that guide the target sizing strategy. If youselectedNo rightsizing as your target sizing strategy, you cannotset the utilization estimates.

• Base sizing strategy on utilization estimates: this option bases sizingrecommendations on utilization estimates for assets for which granularperformance data is unavailable. Migration Center applies theseestimates to the provisioned capacity to determine the appropriateGoogle Cloud resource size and cost. You can configure the defaultutilization percentages (between 1 and 100 percent) for the followingresources:

  • CPU utilization default: default value is 70%.
  • Memory utilization default: default value is 75%.
  • Disk utilization default: default value is 75%.

• Base sizing strategy on 100% provisioned shape: this option basessizing on the asset's 100% provisioned shape (CPU, memory, and disk).

Network data transfer out estimate

Specify the estimated percentage of network traffic that leaves theGoogle Cloud network (data transfer out). Migration Center uses thispercentage to estimate network costs in the TCO report. You are charged onlyfor data transfer out, and not for data transfers within Google Cloud.

• ForData transfer out estimate, set a value between 1 and 100 percent. Thedefault value is 5%.

Product pricing track

Specify your preferred pricing track for the VMs that you migrate toGoogle Cloud.

Choose between on demand pricing, resource-based committed use ofone or three years, or flexible committed use of one or three years.Committed use discounts (CUDs) apply when you choose a committed use,and appear in your TCO report.

What's next

• Learn more aboutcommitted use discounts for Compute Engine.
• Learn more aboutsole-tenant node pricing.
• Learn more aboutVMware Engine pricing.
• Learn about theavailable preferences for Microsoft SQL Server databases.