diff --git a/docs/guides/postgres/backup/kubestash/application-level/examples/restoresession.yaml b/docs/guides/postgres/backup/kubestash/application-level/examples/restoresession.yaml index 7ff80b1266..92780fdd07 100644 --- a/docs/guides/postgres/backup/kubestash/application-level/examples/restoresession.yaml +++ b/docs/guides/postgres/backup/kubestash/application-level/examples/restoresession.yaml @@ -5,9 +5,9 @@ metadata: namespace: demo spec: manifestOptions: - restoreNamespace: dev postgres: db: true + restoreNamespace: dev dataSource: repository: gcs-postgres-repo snapshot: latest diff --git a/docs/guides/postgres/backup/kubestash/application-level/index.md b/docs/guides/postgres/backup/kubestash/application-level/index.md index 9d3a46bf96..7e7c0a63a4 100644 --- a/docs/guides/postgres/backup/kubestash/application-level/index.md +++ b/docs/guides/postgres/backup/kubestash/application-level/index.md @@ -375,7 +375,7 @@ Let's create a secret called `encrypt-secret` with the Restic password, ```bash $ echo -n 'changeit' > RESTIC_PASSWORD $ kubectl create secret generic -n demo encrypt-secret \ - --from-file=./RESTIC_PASSWORD \ + --from-file=./RESTIC_PASSWORD secret "encrypt-secret" created ``` @@ -628,8 +628,8 @@ metadata: namespace: demo spec: manifestOptions: - restoreNamespace: dev postgres: + restoreNamespace: dev db: true dataSource: repository: gcs-postgres-repo @@ -682,7 +682,6 @@ sample-postgres 16.1 Ready 9m46s The output confirms that the `PostgreSQL` database has been successfully created with the same configuration as it had at the time of backup. - #### Verify Restored Data: In this section, we are going to verify whether the desired data has been restored successfully. We are going to connect to the database server and check whether the database and the table we created earlier in the original database are restored. diff --git a/docs/guides/postgres/backup/kubestash/auto-backup/index.md b/docs/guides/postgres/backup/kubestash/auto-backup/index.md index 56861e80b2..a18b1be1b2 100644 --- a/docs/guides/postgres/backup/kubestash/auto-backup/index.md +++ b/docs/guides/postgres/backup/kubestash/auto-backup/index.md @@ -134,7 +134,7 @@ Let's create a secret called `encrypt-secret` with the Restic password, ```bash $ echo -n 'changeit' > RESTIC_PASSWORD $ kubectl create secret generic -n demo encrypt-secret \ - --from-file=./RESTIC_PASSWORD \ + --from-file=./RESTIC_PASSWORD secret "encrypt-secret" created ``` @@ -373,12 +373,12 @@ We can see from the above output that the backup session has succeeded. Now, we **Verify Backup:** -Once a backup is complete, KubeStash will update the respective `Repository` CR to reflect the backup. Check that the repository `sample-postgres-backup` has been updated by the following command, +Once a backup is complete, KubeStash will update the respective `Repository` CR to reflect the backup. Check that the repository `default-blueprint` has been updated by the following command, ```bash $ kubectl get repository -n demo default-blueprint NAME INTEGRITY SNAPSHOT-COUNT SIZE PHASE LAST-SUCCESSFUL-BACKUP AGE -default-blueprint true 3 1.559 KiB Ready 80s 7m32s +default-blueprint true 1 1.559 KiB Ready 80s 7m32s ``` At this moment we have one `Snapshot`. Run the following command to check the respective `Snapshot` which represents the state of a backup run for an application. diff --git a/docs/guides/postgres/backup/kubestash/logical/index.md b/docs/guides/postgres/backup/kubestash/logical/index.md index d87f0e7adc..b2ef2a55c7 100644 --- a/docs/guides/postgres/backup/kubestash/logical/index.md +++ b/docs/guides/postgres/backup/kubestash/logical/index.md @@ -379,7 +379,7 @@ Let's create a secret called `encrypt-secret` with the Restic password, ```bash $ echo -n 'changeit' > RESTIC_PASSWORD $ kubectl create secret generic -n demo encrypt-secret \ - --from-file=./RESTIC_PASSWORD \ + --from-file=./RESTIC_PASSWORD secret "encrypt-secret" created ```