location-copy.md

copyright	years 2020, 2026
lastupdated	2026-08-27
keywords	satellite, hybrid, multicloud, copy location, IBM Cloud location, Satellite location, create location
subcollection	satellite

{{site.data.keyword.attribute-definition-list}}

Copying an {{site.data.keyword.satelliteshort}} location

{: #location-copy}

Copy your {{site.data.keyword.satelliteshort}} location to a new location by reviewing and re-creating resource details, or keep a copy for archival purposes. {: shortdesc}

1. Get your location details and optionally save the details to a local file.

   ibmcloud sat location get --location LOCATION_ID [> mylocation.txt]

   {: pre}

2. List the hosts in your location.

   ibmcloud sat host ls --location LOCATION_ID

   {: pre}

3. Get the details of a host and optionally save the details to a local file. In particular, note the labels for CPU and memory so that you know your host configuration. Repeat this step for each host in your location.

   ibmcloud sat host get --location LOCATION_ID --host HOST_ID [> host1.txt]

   {: pre}

4. List your {{site.data.keyword.satelliteshort}} Link endpoints. A certain set of endpoints are created by default, but note your other endpoints.

   ibmcloud sat endpoint ls --location LOCATION_ID

   {: pre}

5. Get the details of an endpoint and optionally save the details to a local file. Repeat this step for each endpoint in your location.

   ibmcloud sat endpoint get --location LOCATION_ID --endpoint ENDPOINT_ID [> endpoint1.txt]

   {: pre}

6. List the clusters that are created in your {{site.data.keyword.satelliteshort}} location.

   ibmcloud oc cluster ls --provider satellite

   {: pre}

7. Re-create your location.

   • For options to create the location and hosts, see Deciding how to create your {{site.data.keyword.satelliteshort}} location.
   • To create {{site.data.keyword.satelliteshort}} Link endpoints, see cloud or location endpoint instructions.
   • For clusters, see Creating {{site.data.keyword.redhat_openshift_notm}} in {{site.data.keyword.satelliteshort}}. If you manually deployed Kubernetes configurations instead of using {{site.data.keyword.satelliteshort}} Config, also see Copying deployments to another cluster.

8. Redeploy your apps to your cluster. Because {{site.data.keyword.satelliteshort}} Config works across {{site.data.keyword.satelliteshort}} locations, you can add your new clusters to existing cluster groups that are already subscribed to the configurations that you want to deploy.

9. Similar to {{site.data.keyword.satelliteshort}} Config, if you used {{site.data.keyword.satelliteshort}} storage configurations, you can assign these configurations to your new clusters to install the storage drivers.

When you are done and your new location is healthy, you can remove the previous location.