#1 Global Leader in Data Resilience
#1 Global Leader in Data Resilience
BACK TO KB LIST

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
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

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.
Endpoint
  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.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Start using Veeam:
Download the product
&
Activate the license key
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.