---
name: satellite-location-copy
title: Copying an Satellite location
description: Learn how to copy your Satellite location to a new location by reviewing resource details and re-creating them in a new Satellite location, or to keep copies for archival purposes.
last-updated: 2026-08-14
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/satellite?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Copying an Satellite location
{: #location-copy}

Learn how to copy your Satellite location to a new location by reviewing resource details and re-creating them in a new Satellite location, or to keep copies for archival purposes.
{: shortdesc}

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

    ```sh
    ibmcloud sat location get --location LOCATION_ID [> mylocation.txt]
    ```
    {: pre}

2. List the hosts in your location.

    ```sh
    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.

    ```sh
    ibmcloud sat host get --location LOCATION_ID --host HOST_ID [> host1.txt]
    ```
    {: pre}

4. List your Satellite Link endpoints. A certain set of endpoints are created [by default](https://cloud.ibm.com/docs/satellite?topic=satellite-default-link-endpoints&format=markdown), but note your other endpoints.

    ```sh
    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.

    ```sh
    ibmcloud sat endpoint get --location LOCATION_ID --endpoint ENDPOINT_ID [> endpoint1.txt]
    ```
    {: pre}

6. List the clusters that are created in your Satellite location.

    ```sh
    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 Satellite location](https://cloud.ibm.com/docs/satellite?topic=satellite-locations&format=markdown).
    - To create Satellite Link endpoints, see [cloud](https://cloud.ibm.com/docs/satellite?topic=satellite-link-cloud-create&format=markdown#link-cloud) or [location](https://cloud.ibm.com/docs/satellite?topic=satellite-link-cloud-create&format=markdown#link-location) endpoint instructions.
    - For clusters, see [Creating Red Hat OpenShift in Satellite](https://cloud.ibm.com/docs/openshift?topic=openshift-satellite-clusters&format=markdown). If you manually deployed Kubernetes configurations instead of using Satellite Config, also see [Copying deployments to another cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-update_app&format=markdown#copy_apps_cluster).

8. Redeploy your apps to your cluster. Because Satellite Config works across Satellite locations, you can [add your new clusters to existing cluster groups](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig-groups&format=markdown) that are already [subscribed to the configurations](https://cloud.ibm.com/docs/satellite?topic=satellite-satcon-manage-direct-upload&format=markdown) that you want to deploy.
9. Similar to Satellite Config, if you used Satellite 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](https://cloud.ibm.com/docs/satellite?topic=satellite-host-remove&format=markdown#location-remove-console).