Skip to main content
Question

Exporting Metadata to S3 Compatible MinIO

  • June 16, 2025
  • 2 comments
  • 20 views

I am using a simple policy to export one application namespace to MinIO from our Openshift Cluster. Everything works in Kasten upon the point of exporting the metadata, where it hangs.

2 comments

  • Author
  • New Here
  • June 16, 2025
kind: Profile
apiVersion: config.kio.kasten.io/v1alpha1
metadata:
name: minio-s3
namespace: kasten-io
uid: c859d03e-6ced-4a00-8d40-b6e3d4abf33a
resourceVersion: "3677795"
generation: 8
creationTimestamp: 2025-06-10T12:58:21Z
spec:
locationSpec:
type: ObjectStore
objectStore:
endpoint: http://10.3.17.19:9000
name: oebb-backup
objectStoreType: S3
path: k10/61882629-8d51-4535-8fa2-c350b185099e/migration
pathType: Directory
protectionPeriod: 2160h0m0s
region: eu-vienna-1
skipSSLVerify: true
credential:
secretType: AwsAccessKey
secret:
apiVersion: v1
kind: secret
name: k10secret-5rhlw
namespace: kasten-io
type: Location
status:
validation: Success
hash: 114589335

 


Forum|alt.badge.img
  • Comes here often
  • July 30, 2025

There are several factors that could cause metadata export to hang:

Common causes to check:

Storage Constraints

  Is your MinIO storage capacity approaching its limit?

  Check if there's sufficient space for the metadata export

Permission Issues

  Review the logs for any "Permission to write to volume not granted" errors

  Verify that Kasten has proper write permissions to the MinIO bucket. 

 

To thoroughly investigate this issue and ensure we identify the root cause, I recommend creating a support ticket.