Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CopyVolumeData followed by RestoreData does not restore to the original location #2444

Open
laurentiusoica opened this issue Oct 27, 2023 · 2 comments
Assignees
Labels

Comments

@laurentiusoica
Copy link

For a single node PostgreSQL deployment with the Bitnami charts:

helm install postgresql --namespace postgresql bitnami/postgresql -f values.yaml --create-namespace

with this backup phase:

    - func: CopyVolumeData
      name: CopyPostgreSQLVolumeDataToObjectStore
      args:
        namespace: "{{ .StatefulSet.Namespace }}"
        volume: "data-postgresql-0"
        dataArtifactPrefix: indigo/postgresql/{{ toDate "2006-01-02T15:04:05.999999999Z07:00" .Time | date "20060102150405" }}

and this restore phase:

    - func: RestoreData
      name: Restore Data From Object Store
      args:
        namespace: "{{ .StatefulSet.Namespace }}"
        image: ghcr.io/kanisterio/kanister-tools:0.98.0
        backupArtifactPrefix: "{{ .ArtifactsIn.backup.KeyValue.backupArtifactLocation }}"
        backupTag: "{{ .ArtifactsIn.backup.KeyValue.backupTag }}"
        volumes:
          data-postgresql-0: /bitnami/postgresql
        restorePath: /bitnami/postgresql

The data is restored under /mnt/vol_data/data-postgresql-0/ instead of the root of the volume.

@github-actions
Copy link
Contributor

Thanks for opening this issue 👍. The team will review it shortly.

If this is a bug report, make sure to include clear instructions how on to reproduce the problem with minimal reproducible examples, where possible. If this is a security report, please review our security policy as outlined in SECURITY.md.

If you haven't already, please take a moment to review our project's Code of Conduct document.

Copy link
Contributor

github-actions bot commented Mar 7, 2024

This issue is marked as stale due to inactivity. Add a new comment to reactivate it.

@github-actions github-actions bot added the stale label Mar 7, 2024
@pavannd1 pavannd1 removed the stale label Mar 7, 2024
@github-project-automation github-project-automation bot moved this to To Be Triaged in Kanister Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: To Be Triaged
Development

No branches or pull requests

4 participants