add shard pitr

Signed-off-by: sayedppqq <[email protected]>
kubedb · Sep 19, 2024 · 78054d7 · 78054d7
1 parent 5957220
commit 78054d7
Show file tree

Hide file tree

Showing 5 changed files with 8 additions and 8 deletions.
diff --git a/docs/guides/mongodb/backup/kubestash/application-level/examples/restoresession.yaml b/docs/guides/mongodb/backup/kubestash/application-level/examples/restoresession.yaml
@@ -6,7 +6,7 @@ metadata:
 spec:
   manifestOptions:
     restoreNamespace: dev
-    mongodb:
+    mongoDB:
       db: true
   dataSource:
     repository: s3-mongodb-repo

diff --git a/docs/guides/mongodb/backup/kubestash/application-level/examples/sample-mongodb.yaml b/docs/guides/mongodb/backup/kubestash/application-level/examples/sample-mongodb.yaml
@@ -9,7 +9,6 @@ spec:
     name: "replicaset"
   replicas: 3
   storageType: Durable
-  terminationPolicy: WipeOut
   storage:
     accessModes:
       - ReadWriteOnce

diff --git a/docs/guides/mongodb/backup/kubestash/application-level/index.md b/docs/guides/mongodb/backup/kubestash/application-level/index.md
@@ -70,7 +70,6 @@ spec:
     name: "replicaset"
   replicas: 3
   storageType: Durable
-  terminationPolicy: WipeOut
   storage:
     accessModes:
       - ReadWriteOnce
@@ -573,7 +572,7 @@ metadata:
 spec:
   manifestOptions:
     restoreNamespace: dev
-    mongodb:
+    mongoDB:
       db: true
   dataSource:
     repository: s3-mongodb-repo

diff --git a/docs/guides/mongodb/backup/kubestash/auto-backup/index.md b/docs/guides/mongodb/backup/kubestash/auto-backup/index.md
@@ -109,7 +109,7 @@ secret/encry-secret created
 
 `RetentionPolicy` specifies how the old Snapshots should be cleaned up. This is a namespaced CRD. However, we can refer it from other namespaces as long as it is permitted via `.spec.usagePolicy`. Below is the YAML of the `RetentionPolicy` called `backup-rp`
 
-```console
+```yaml
 apiVersion: storage.kubestash.com/v1alpha1
 kind: RetentionPolicy
 metadata:

diff --git a/docs/guides/mongodb/pitr/pitr.md b/docs/guides/mongodb/pitr/pitr.md
@@ -231,7 +231,9 @@ stringData:
 
 
 # Deploy MongoDB
-So far we are ready with setup for continuously archive MongoDB, We deploy a MongoDB referring the MongoDB archiver object
+So far we are ready with setup for continuously archive MongoDB, We deploy a MongoDB referring the MongoDB archiver object.
+> KubeDB has supports for KubeDB managed Replicaset and Sharded MongoDB PITR support. It doesn't have support for standalone MongoDB. 
+> Bellow is the example for a Replicaset MongoDB. Process for Sharded MongoDB is exactly same.
 
 ```yaml
 apiVersion: kubedb.com/v1
@@ -368,8 +370,8 @@ rs:PRIMARY> db.dropDatabase()
 
 ```
 
-Time time `1702457742` is unix timestamp. This is `Wed Dec 13 2023 08:55:42 GMT+0000` in human readable format.
-We can't restore from a full backup since at this point no full backup was perform. so we can choose a specific time in (just before this timestamp, for example `08:55:30`) which time we want to restore.
+Time `1702457742` is unix timestamp. This is `Wed Dec 13 2023 08:55:42 GMT+0000` in human-readable format.
+We can't restore from a full backup since at this point no full backup was performed. so we can choose a specific time in (just before this timestamp, for example `08:55:30`) which time we want to restore.
 
 ### Restore MongoDB
 ```yaml