1+ title : " Create a PersistentVolumeClaim object."
2+ stepnum : 1
3+ level : 4
4+ ref : filestore-create-pvc-object
5+ content : |
6+
7+ Create a :k8sdocs:`PersistentVolumeClaim </concepts/storage/persistent-volumes/>`
8+ object, and allocate storage as needed. Set
9+ :k8sdocs:`accessModes </concepts/storage/persistent-volumes/#access-modes>`
10+ to ``ReadWriteMany``:
11+
12+ .. code-block:: yaml
13+
14+ apiVersion: v1
15+ kind: PersistentVolumeClaim
16+ metadata:
17+ name: snapshot-store-ops-manager
18+ spec:
19+ storageClassName: managed-nfs-storage #SC that supports(RWX)
20+ accessModes:
21+ - ReadWriteMany
22+ resources:
23+ requests:
24+ storage: 10G
25+ ...
26+
27+
28+ title : " Create and apply an Ops Manager Custom Resource Definition specifying your PersistentVolumeClaim."
29+ stepnum : 2
30+ level : 4
31+ ref : filestore-create-apply-crd
32+ content : |
33+
34+ Create an |onprem| |k8s-crd| that specifies your
35+ ``PersistentVolumeClaim`` object and the ``backup.fileSystemStores``
36+ field, which is the name of your file system snapshot store.
37+
38+ The following example creates a |k8s-crd| file named
39+ ``ops-manager-fs.yaml``, for the MongoDB
40+ :term:`oplog store <oplog store database>` with a ``kube-user``.
41+
42+ .. code-block:: yaml
43+
44+ apiVersion: mongodb.com/v1
45+ kind: MongoDBOpsManager
46+ metadata:
47+ name: ops-manager
48+ spec:
49+ replicas: 1
50+ version: 6.0.7
51+ adminCredentials: ops-manager-admin-secret
52+ statefulSet:
53+ spec:
54+ template:
55+ spec:
56+ volumes:
57+ - name: snapshot-store
58+ persistentVolumeClaim:
59+ claimName: snapshot-store-ops-manager
60+ containers:
61+ - name: mongodb-ops-manager
62+ volumeMounts:
63+ - name: snapshot-store
64+ mountPath: /snapshot_store
65+ backup:
66+ enabled: true
67+ fileSystemStores: filesystem1
68+ opLogStores:
69+ - name: oplog1
70+ mongodbResourceRef:
71+ name: oplog-db
72+ # mongodbUserRef:
73+ # name: kube-user
74+ statefulSet:
75+ spec:
76+ template:
77+ spec:
78+ volumes:
79+ - name: snapshot-store
80+ persistentVolumeClaim:
81+ claimName: snapshot-store-ops-manager
82+ containers:
83+ - name: mongodb-backup-daemon
84+ volumeMounts:
85+ - name: snapshot-store
86+ mountPath: /snapshot_store
87+ applicationDatabase:
88+ members: 3
89+ version: 5.0.7-ent
90+
91+
92+ title : " Apply changes to your |onprem| deployment."
93+ stepnum : 3
94+ level : 4
95+ ref : apply-changes-om-k8s
96+ content : |
97+
98+ Invoke the following ``kubectl`` command on the filename of your
99+ |onprem| resource definition:
100+
101+ .. code-block:: sh
102+
103+ kubectl apply -f <opsmgr-resource>.yaml
104+
105+
106+ title : " Configure your oplog store."
107+ stepnum : 4
108+ level : 4
109+ ref : filestore-config-oplog-store
110+ content : |
111+
112+ Wait for your |onprem| object to report its state as ``Running``, then
113+ configure your oplog store as described in the
114+ **Configure Backup Settings** step of the
115+ :ref:`Deploy an Ops Manager Resource <deploy-om-tls>` procedure.
116+
117+
118+ title : " Create a File System Snapshot Store in |onprem|."
119+ stepnum : 5
120+ level : 4
121+ ref : filestore-create-snapshot-store
122+ content : |
123+
124+ Log into your |onprem| instance and navigate to: :guilabel:`Admin`
125+ :icon-fa5:`arrow-right` :guilabel:`Backup` :icon-fa5:`arrow-right`
126+ :guilabel:`Snapshot Store` :icon-fa5:`arrow-right`
127+ :guilabel:`Create New File System Store`.
128+
129+ Set the name to the value you set for ``backup.fileSystemStores``
130+ in your |k8s-crd|. Set the other values as appropriate, then click
131+ :guilabel:`Create`.
132+
133+ Your |onprem| object will report a ``BACKUP`` state of ``Pending``
134+ after you create the new file system store.
135+
136+
0 commit comments