search

mongodb / mongodb-kubernetes-operator

MongoDB Community Kubernetes Operator
Other
1.24k stars 506 forks source link

File System Snapshot #573

Closed rajavignesh closed 3 years ago

rajavignesh commented 3 years ago

What did you do to encounter the bug? Steps to reproduce the behavior: MongoDB Version: 4.2.11 Take a snapshot of the persistence volume using Cohesity or Velero and restore the PVC Pods will go in Error or CrashLoopBackOff state Note: even copying the files from pod to VM, facing the same issue

What did you expect? Pod should come up using the data files that have been restored

What happened instead? Facing checksum issue (attached the complete error description)

Screenshots Attached the error

Operator Information

file_snapshot_error.txt

bznein commented 3 years ago

Hi @rajavignesh

The usage of tools such as Cohesity or Velero is not something we support at the moment. The suggested approach to save and restore data is through the use of mongodump and mongorestore.

The enterprise operator supports more advanced backup configurations.