add nfs backend for pitr

Signed-off-by: SK Ali Arman <[email protected]>

docs/guides/mariadb/pitr/nfs/yamls/backupstorage.yaml

@@ -0,0 +1,22 @@
+apiVersion: storage.kubestash.com/v1alpha1
+kind: BackupStorage
+metadata:
+  name: local-storage
+  namespace: demo
+spec:
+  storage:
+    provider: local
+    local:
+      mountPath: /md/walg
+      persistentVolumeClaim:
+        claimName: nfs-pvc
+  usagePolicy:
+    allowedNamespaces:
+      from: All
+  default: false
+  deletionPolicy: WipeOut
+  runtimeSettings:
+    pod:
+      securityContext:
+        fsGroup: 999
+        runAsUser: 999

docs/guides/mariadb/pitr/nfs/yamls/mariadbarchiver.yaml

@@ -0,0 +1,52 @@
+apiVersion: archiver.kubedb.com/v1alpha1
+kind: MariaDBArchiver
+metadata:
+  name: mariadbarchiver-sample
+  namespace: demo
+spec:
+  pause: false
+  databases:
+    namespaces:
+      from: Selector
+      selector:
+        matchLabels:
+          kubernetes.io/metadata.name: demo
+    selector:
+      matchLabels:
+        archiver: "true"
+  retentionPolicy:
+    name: mariadb-retention-policy
+    namespace: demo
+  encryptionSecret:
+    name: "encrypt-secret"
+    namespace: "demo"
+  fullBackup:
+    jobTemplate:
+      spec:
+        securityContext:
+          fsGroup: 999
+          runAsUser: 999
+    driver: "VolumeSnapshotter"
+    task:
+      params:
+        volumeSnapshotClassName: "longhorn-snapshot-vsc"
+    scheduler:
+      successfulJobsHistoryLimit: 1
+      failedJobsHistoryLimit: 1
+      schedule: "*/1 * * * *"
+    sessionHistoryLimit: 2
+  manifestBackup:
+    jobTemplate:
+      spec:
+        securityContext:
+          fsGroup: 999
+          runAsUser: 999
+    scheduler:
+      successfulJobsHistoryLimit: 1
+      failedJobsHistoryLimit: 1
+      schedule: "*/1 * * * *"
+    sessionHistoryLimit: 2
+  backupStorage:
+    ref:
+      name: "local-storage"
+      namespace: "demo"

docs/guides/mariadb/pitr/nfs/yamls/nfs-pvc.yaml

@@ -0,0 +1,12 @@
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: nfs-pvc
+  namespace: demo
+spec:
+  storageClassName: "nfs"
+  resources:
+    requests:
+      storage: 1Gi
+  accessModes:
+    - ReadWriteOnce

docs/guides/mariadb/pitr/nfs/yamls/nfs-server.yaml

@@ -0,0 +1,51 @@
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: nfs-server
+  namespace: demo
+spec:
+  selector:
+    matchLabels:
+      app: nfs-server
+  template:
+    metadata:
+      labels:
+        app: nfs-server
+    spec:
+      containers:
+        - name: nfs-server
+          image: k8s.gcr.io/volume-nfs:0.8
+          ports:
+            - name: nfs
+              containerPort: 2049
+            - name: mountd
+              containerPort: 20048
+            - name: rpcbind
+              containerPort: 111
+          securityContext:
+            privileged: true
+          volumeMounts:
+            - name: storage
+              mountPath: /exports
+      volumes:
+        - name: storage
+          hostPath:
+            path: /data/nfs # store all data in "/data/nfs" directory of the node where it is running
+            type: DirectoryOrCreate
+---
+
+apiVersion: v1
+kind: Service
+metadata:
+  name: nfs-server
+  namespace: demo
+spec:
+  ports:
+    - name: nfs
+      port: 2049
+    - name: mountd
+      port: 20048
+    - name: rpcbind
+      port: 111
+  selector:
+    app: nfs-server # must match with the label of NFS pod

docs/guides/mariadb/pitr/nfs/yamls/nfs-storage-class.yaml

@@ -0,0 +1,11 @@
+allowVolumeExpansion: true
+apiVersion: storage.k8s.io/v1
+kind: StorageClass
+metadata:
+  name: nfs
+parameters:
+  server: nfs-server.demo.svc.cluster.local
+  share: /
+provisioner: nfs.csi.k8s.io
+reclaimPolicy: Delete
+volumeBindingMode: Immediate

docs/guides/mariadb/pitr/yamls/retentionPolicy.yaml → docs/guides/mariadb/pitr/nfs/yamls/retentionPolicy.yaml

@@ -6,6 +6,6 @@ metadata:
 spec:
   maxRetentionPeriod: "30d"
   successfulSnapshots:
-    last: 100
+    last: 2
   failedSnapshots:
     last: 2

docs/guides/mariadb/pitr/archiver.md → docs/guides/mariadb/pitr/overview/index.md

@@ -32,13 +32,14 @@ To keep things isolated, this tutorial uses a separate namespace called `demo` t
 $ kubectl create ns demo
 namespace/demo created
 ```
-> Note: The yaml files used in this tutorial are stored in [docs/guides/mariadb/remote-replica/yamls](https://github.com/kubedb/docs/tree/{{< param "info.version" >}}/docs/guides/mariadb/remote-replica/yamls) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs).
+> Note: The yaml files used in this tutorial are stored in [docs/guides/mariadb/pitr/overview/yamls](https://github.com/kubedb/docs/tree/{{< param "info.version" >}}/docs/guides/mariadb/remote-replica/yamls) folder in GitHub repository [kubedb/docs](https://github.com/kubedb/docs).
 
 ## continuous archiving
 Continuous archiving involves making regular copies (or "archives") of the MariaDB transaction log files.To ensure continuous archiving to a remote location we need prepare `BackupStorage`,`RetentionPolicy`,`MariaDBArchiver` for the KubeDB Managed MariaDB Databases.
 
 ### BackupStorage
 BackupStorage is a CR provided by KubeStash that can manage storage from various providers like GCS, S3, and more.
+We are going to store our backup data into a `S3` bucket. We have to create a `Secret` with necessary credentials and a `BackupStorage` CR to use this backend. If you want to use a different backend, please read the respective backend configuration doc from [here](https://kubestash.com/docs/latest/guides/backends/overview/).
 
 ```yaml
 apiVersion: storage.kubestash.com/v1alpha1

docs/guides/mariadb/pitr/overview/yamls/encryptionSecret.yaml

@@ -0,0 +1,8 @@
+apiVersion: v1
+kind: Secret
+type: Opaque
+metadata:
+  name: encrypt-secret
+  namespace: demo
+stringData:
+  RESTIC_PASSWORD: "changeit"

docs/guides/mariadb/pitr/overview/yamls/mariadb.yaml

@@ -0,0 +1,31 @@
+apiVersion: kubedb.com/v1
+kind: MariaDB
+metadata:
+  name: mariadb
+  namespace: demo
+  labels:
+    archiver: "true"
+spec:
+  version: "11.1.3"
+  replicas: 3
+  storageType: Durable
+  storage:
+    storageClassName: "longhorn"
+    accessModes:
+      - ReadWriteOnce
+    resources:
+      requests:
+        storage: 10Gi
+  archiver:
+    ref:
+      name: mariadbarchiver-sample
+      namespace: demo
+  deletionPolicy: WipeOut
+  podTemplate:
+    spec:
+      containers:
+        - name: mariadb
+          args:
+            - "--log-bin"
+            - "--log-slave-updates"
+            - "--wsrep-gtid-mode=ON"

docs/guides/mariadb/pitr/overview/yamls/mariadbrestore.yaml

@@ -0,0 +1,34 @@
+apiVersion: kubedb.com/v1
+kind: MariaDB
+metadata:
+  name: restore-mariadb
+  namespace: demo
+spec:
+  init:
+    archiver:
+      encryptionSecret:
+        name: encrypt-secret
+        namespace: demo
+      fullDBRepository:
+        name: mariadb-full
+        namespace: demo
+      recoveryTimestamp: "2025-09-17T05:28:26Z"
+  version: "11.1.3"
+  replicas: 3
+  storageType: Durable
+  storage:
+    storageClassName: "longhorn"
+    accessModes:
+      - ReadWriteOnce
+    resources:
+      requests:
+        storage: 10Gi
+  deletionPolicy: WipeOut
+  podTemplate:
+    spec:
+      containers:
+        - name: mariadb
+          args:
+            - "--log-bin"
+            - "--log-slave-updates"
+            - "--wsrep-gtid-mode=ON"

docs/guides/mariadb/pitr/overview/yamls/retentionPolicy.yaml

@@ -0,0 +1,11 @@
+apiVersion: storage.kubestash.com/v1alpha1
+kind: RetentionPolicy
+metadata:
+  name: mariadb-retention-policy
+  namespace: demo
+spec:
+  maxRetentionPeriod: "30d"
+  successfulSnapshots:
+    last: 2
+  failedSnapshots:
+    last: 2

docs/guides/mariadb/pitr/overview/yamls/voluemsnapshotclass.yaml

@@ -0,0 +1,8 @@
+kind: VolumeSnapshotClass
+apiVersion: snapshot.storage.k8s.io/v1
+metadata:
+  name: longhorn-snapshot-vsc
+driver: driver.longhorn.io
+deletionPolicy: Delete
+parameters:
+  type: snap