Quantcast
Channel: Veeam Support Knowledge Base
Viewing all articles
Browse latest Browse all 4469

How to Update Location Profile Endpoint Details and Preserve Access to an Existing Kopia Storage Repository

$
0
0

How to Update Location Profile Endpoint Details and Preserve Access to an Existing Kopia Storage Repository

KB ID: 4691
Product: Veeam Kasten for Kubernetes
Version: 7.5+
Published: 2024-12-03
Last Modified: 2024-12-03

Purpose

This article documents the correct procedure to update the Endpoint details in the Location Profile for an existing Kopia storage repository in S3-compatible stores and ensure the existing associated repositories remain accessible.

Customers may wish to update the Endpoint details (e.g., updating the hostname or endpoint protocol) for the S3-compatible stores for existing Kopia repositories. However, if the customer only updates the Endpoint details in the Location Profile, the existing Kopia repositories using the Location Profile may become inaccessible.

 

Solution

Use the following procedure to update the Endpoint details within the Location Profile and ensure that the Kopia storage repositories remain accessible.

Example note: In the examples shown, the use case is switching from an existing endpoint to a new endpoint(IP address specifically).

  1. Update the Endpoint details in the Location Profile for the S3-compatible store.
  1. Use the following command to identify the storage repositories that point to the old location endpoint:
    Note: Update the OLDENDPOINT variable with the old endpoint details. The example variable value shown is relevant only to the use case example being presented.
OLDENDPOINT="http://34.145.91.92:9000"

kubectl get storagerepositories.repositories.kio.kasten.io -n kasten-io \
-o=jsonpath="{range .items[?(@.status.location.objectStore.endpoint==\"${OLDENDPOINT}\")]}{.metadata.name}{\"\n\"}{end}"
Command Example
Old endpoint details are highlighted in pink.
Output is highlighted in Green.
  1. Using the output from the previous command, modify the following commands to update the storagerepositories API resource that uses the older location endpoint. Add a new field, overrideLocation, to replace the endpoint details from the Location Profile. Update both the metadata and volume storage repositories accordingly.
# Define variables for the repository names and location profile
KOPIA_METADATA_REPOSITORY_NAME="<kopia-metadata-repository-name>"
KOPIA_VOLUMEDATA_REPOSITORY_NAME="<kopia-volumedata-repository-name>"
LOCATION_PROFILE_NAME="<location-profile-name>"
LOCATION_PROFILE_NAMESPACE="<location-profile-namespace>"

# Update the metadata storage repository
kubectl -n kasten-io patch storagerepository $KOPIA_METADATA_REPOSITORY_NAME \
--type merge \
--patch '{"spec": {"overrideLocation": {"name": "'"${LOCATION_PROFILE_NAME}"'", "namespace": "'"${LOCATION_PROFILE_NAMESPACE}"'"}}}'

# Update the volume data storage repository
kubectl -n kasten-io patch storagerepository $KOPIA_VOLUMEDATA_REPOSITORY_NAME \
--type merge \
--patch '
{"spec": {"overrideLocation": {"name": "'"${LOCATION_PROFILE_NAME}"'", "namespace": "'"${LOCATION_PROFILE_NAMESPACE}"'"}}}'
  1. Once the location profile and storage repositories are updated with the new field "overrideLocation", backups and exports can be expected to work seamlessly without any interruptions.
  2. If the same storage repository also exists on a target cluster where the application’s data needs to be imported, and the storagerepositories API resource with the old location endpoint is present on the target cluster, update the storagerepositories API on the target cluster using the method mentioned above.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Viewing all articles
Browse latest Browse all 4469

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>