Configure File System Backup Store with Kubernetes Operator

On this page

Prerequisites

Procedure

This version of the operator is no longer officially supported. View the current documentation to learn how to upgrade your version of MongoDB Enterprise Kubernetes Operator.

Kubernetes Operator supports storage of filesystem snapshots.

Prerequisites

To configure file system snapshot storage, your Kubernetes Operator deployment must have a storage class configured with the ReadWriteMany method.

Procedure

To configure file system snapshot storage:

Create a PersistentVolumeClaim object.

Create a PersistentVolumeClaim object, and allocate storage as needed. Set accessModes to ReadWriteMany:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: snapshot-store-ops-manager
spec:
  storageClassName: managed-nfs-storage #SC that supports(RWX)
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 10G
    ...

Create and apply an Ops Manager Custom Resource Definition specifying your PersistentVolumeClaim.

Create an Ops Manager CustomResourceDefinition that specifies your PersistentVolumeClaim object and the backup.fileSystemStores field, which is the name of your file system snapshot store.

The following example creates a CustomResourceDefinition file named ops-manager-fs.yaml, for the MongoDB oplog store with a kube-user.

apiVersion: mongodb.com/v1
  kind: MongoDBOpsManager
  metadata:
    name: ops-manager
  spec:
    replicas: 1
    version: 6.0.7
    adminCredentials: ops-manager-admin-secret
    statefulSet:
      spec:
        template:
          spec:
            volumes:
              - name: snapshot-store
                persistentVolumeClaim:
                  claimName: snapshot-store-ops-manager
            containers:
              - name: mongodb-ops-manager
                volumeMounts:
                  - name: snapshot-store
                    mountPath: /snapshot_store
    backup:
      enabled: true
      fileSystemStores:
        - name: filesystem1
       assignmentLabels: ["test1", "test2"]
      opLogStores:
        assignmentLabels: ["test1", "test2"]
        - name: oplog1
          mongodbResourceRef:
            name: oplog-db
          # mongodbUserRef:
          #   name: kube-user
      statefulSet:
        spec:
          template:
            spec:
              volumes:
                - name: snapshot-store
                  persistentVolumeClaim:
                    claimName: snapshot-store-ops-manager
              containers:
                - name: mongodb-backup-daemon
                  volumeMounts:
                    - name: snapshot-store
                      mountPath: /snapshot_store
    applicationDatabase:
      members: 3
      version: 5.0.7-ubi8

Apply changes to your Ops Manager deployment.

Invoke the following kubectl command on the filename of your Ops Manager resource definition:

kubectl apply -f <opsmgr-resource>.yaml

Configure your oplog store.

Wait for your Ops Manager object to report its state as Running, then configure your oplog store as described in the Configure Backup Settings step of the Deploy an Ops Manager Resource procedure.

Create a File System Snapshot Store in Ops Manager.

Log into your Ops Manager instance and navigate to: Admin Backup Snapshot Store Create New File System Store.

Set the name to the value you set for backup.fileSystemStores in your CustomResourceDefinition. Set the other values as appropriate, then click Create.

Your Ops Manager object will report a BACKUP state of Pending after you create the new file system store.

Back

Configure KMIP Backup Encryption for Ops Manager

Set Up a cert-manager Integration