| copyright | lastupdated | keywords | subcollection | ||
|---|---|---|---|---|---|
|
2021-08-24 |
migrate, migrating data center, migrate resources, data center |
account |
{:shortdesc: .shortdesc} {:codeblock: .codeblock} {:screen: .screen} {:gif: data-image-type='gif'} {:tip: .tip} {:external: target="_blank" .external}
{: #migrate-data-center}
{{site.data.keyword.IBM}} continually updates and modernizes data centers to give you higher levels of performance. Some data centers aren't able to be upgraded, so they must be closed and you must migrate your resources to a different data center. {: shortdesc}
Throughout the data center migration process, help is available. To take advantage of special offers, or learn about recommended configurations, use one of the following options to contact the {{site.data.keyword.IBM_notm}} 24x7 Client Success team:
- Live chat{: external}
- Phone: (US) 866-597-9687; (EMEA) +31 20 308 0540; (APAC) +65 6622 2231
For information about which data centers are closing, see Data center closures. For a list of the data centers that are available, see Locations for resource deployment.
{: #migrating-your-resources}
Complete the following steps to migrate resources to a new data center:
-
Identify any virtual server instances or bare metal servers that are currently running on the data centers that are set to close.
- Begin by viewing all subnets.
- Filter the list of subnets by location, such as
Dallas 5. - In the resulting filtered list, click the name of the VLAN in the VLAN column. To identify a specific POD within a data center, check the VLAN name for a string like,
bcr02orfcr04.Bcr02= backend customer router, POD 2.Fcr04= frontend customer router, POD 4. - On the Instance detail page, locate the Devices section that identifies virtual server instances and bare metal servers that are provisioned in the VLAN.
- To identify all devices in the data center, complete these steps for each VLAN in the data center.
-
Order replacement servers in new data centers. For more information, see the following documentation:
- Planning for VPC instances
- Getting started with virtual servers
- Getting started with bare metal servers
- Comparing {{site.data.keyword.cloud_notm}} Classic and VPC infrastructure environments
- Copy your data to a new server by using the following methods. You must establish connectivity between the old and new servers and have sufficient storage in the new server.
- Use Secure Copy Protocol (SCP){: external} to securely copy a file from source to destination.
- Use rsync{: external} if you need to copy multiple files. Rsync also copies directory structures and preserves file permissions.
- Migrate your virtual server instance from one classic data center to another.
- Migrate your virtual server instance by creating an image template and deploying it in a new {{site.data.keyword.vpc_short}}.
- Migrate your VMware cluster to a new data center by using HCX.
- Migrate a local load balancer to IBM Cloud Load Balancer. For more information, see FAQs for IBM Cloud Load Balancer.
- Migrate your {{site.data.keyword.cos_full_notm}} data to a new {{site.data.keyword.cloud_notm}} data center.
Copy only applications and application data between systems. Copying older versions of operating system files to a newer version can cause problems. Shut down databases before you copy them between the systems to ensure that the data is consistent. When migrating database data, migrate the data in a way that doesn’t limit your options to import it into the new system. Rather than copying database data from system to system, consider exporting it to a format so you can import it to a newer database. Flat text files, CSV files, and other files provide more options than using proprietary or closed file formats when it comes to moving data between systems. Always test your data migration approaches on a small set of test data before officially copying.
- Cancel your servers. You continue to be invoiced for the old servers until you cancel them. For more information, see Device types.