| copyright | lastupdated | keywords | subcollection | content-type | ||
|---|---|---|---|---|---|---|
|
2021-02-25 |
migration FAQs, data centers |
account |
faq |
{:shortdesc: .shortdesc} {:codeblock: .codeblock} {:screen: .screen} {:tip: .tip} {:faq: data-hd-content-type='faq'}
{: #faqs-dc-closure}
FAQs about migrating resources between data centers might include questions about migration requirements, timing, gathering information about your current or new configuration. {: shortdesc}
{: #dc-required-move} {: faq}
To continue bringing you the best service, hardware, and connectivity, data centers are continually evaluated to ensure that they meet networking, electrical, and other infrastructure standards. The closing data centers no longer meet the ongoing standards.
{: #dc-fully-migrated} {: faq}
Yes. To ensure that you have no interruption in service, we try to allow as much lead time as possible to make the transition easier.
{: #dc-move-again} {: faq}
We constantly evaluate the quality of our sites to bring you the best and most dependable service. It's possible that we might have other moves as we continue to evaluate some of the older sites.
{: #dc-select-deploy} {: faq}
The following factors might influence which data center you select:
- Proximity to the users of the systems
- Proximity to any other systems that this server needs to communicate with
- Any data policies or regulations that require data to be stored in a specific location
For the list of available data centers, see Locations for resource deployment.
{: #dc-transition-sites} {: faq}
You can use any worldwide {{site.data.keyword.cloud_notm}} data center during your transition period, which lasts up to 60 days. See Locations for resource deployment for more information.
{: #dc-free-months} {: faq}
Yes. You can contact an appropriate support representative{: external} to help you through the process of acquiring your transition period servers.
{: #dc-determine-config} {: faq}
You can find your system configuration details by selecting your device from your list of resources{: external} in the {{site.data.keyword.cloud_notm}} console.
{: #dc-determine-utilization} {: faq}
In general, you need to understand which specific resources within the system are required regarding things like the processor, memory, disk, and network. Having this information can help you better size your new system. For example, a system where memory capacity is frequently overcommitted is likely to benefit from larger memory sizes in the target system that you migrate to.
Most operating systems provide tools that you can use to understand the utilization of your system, for example, vmstat and iostat on Linux or Windows System Performance Monitor. Performance monitoring and tuning is something that you might invest significant time and effort in.
For more information, contact the Client Success team{: external}.
{: #dc-compare-processor} {: faq}
To compare the specifications of old and new Intel processors, go to Intel processors product specifications page{: external}. Newer processors tend to have more processor cores and typically run at slower clock speeds than older variants.
If you have a workload that is processor-bound, meaning that the performance is limited by the speed of the processor, choose a processor that has fewer cores and a higher clock speed. If you run many workloads that aren't constrained by processor speed, choose a processor with more cores and a similar, or slower, clock speed.
{: #dc-choose-os} {: faq}
Compatibility and functionality are two of the main influencers when you choose a new operating system. Older versions of operating systems can present challenges with migration. Installation media might not be compatible and the server hardware might not be supported by the older operating system. The best course of action is to compare specs and ensure that the operating system is compatible. You must verify that the necessary development tools and operating system or middleware functions are available on the new platform. In general, Linux type systems are better at supporting older applications on newer versions of the operating system than Windows.
For more information, contact the Client Success team{: external}.
{: #dc-bandwidth-rate} {: faq}
You receive a current bandwidth package that is most closely related to the package you currently have. The rate for that package is whatever your current rate or package includes.
{: #dc-copy-data} {: faq}
You can copy applications and application data from your old server to your new one. For more information, see Migrating resources to a different data center.
{: #dc-setup-networking} {: faq}
Most likely, your networking needs to change to work with the new servers and site. For more information about setting up your network, see Setting up a virtual machine network.
{: #dc-ip-addresses}
Your new servers come with new primary IP subnets. Your current IP addresses cannot be transferred. If you need additional IP addresses, you can request those directly from the console. Specify that you're migrating your resources to a new data center.
- For more information about VPC subnets, see Bring your own subnet.
- For more information about classic infrastructure subnets, see Getting started with subnets and IPs.