Andre
My feedback
-
52 votes
An error occurred while saving the comment Andre
supported this idea
·
We're glad you're here
Please sign in to leave feedback
Signed in as
(Sign out)
We're glad you're here
Please sign in to leave feedback
Signed in as
(Sign out)
Feedback and Knowledge Base
-
Searching…
No results.
Clear search results
-
Give feedback
- Atlas 497 ideas
- Atlas Data Lake 20 ideas
- Atlas Search 57 ideas
- Charts 112 ideas
- Compass 169 ideas
- Connectors (BI, Kafka, Spark) 11 ideas
- Database 68 ideas
- Drivers 32 ideas
- MongoDB CLI 9 ideas
- MongoDB for VS Code 18 ideas
- MongoDB Shell 8 ideas
- Ops Tools 208 ideas
- Realm 162 ideas
- UI 43 ideas
Your password has been reset
We have made changes to increase our security and have reset your password.
We've just sent you an email to . Click the link to create a password, then come back here and sign in.
This would be nice, its an extra step to restore for us since you have to launch a matching MongoDB Server and then dump the data just to make it usable
We created a k8s pod that we run that loads it after we have extracted it to a PVC:
```
---
apiVersion: v1
kind: Pod
metadata:
name: mongo-s3-restore-pod
namespace: mongo-s3-backup
spec:
containers:
- name: mongo-s3-restore-pod
image: "mongo:3.6-xenial"
imagePullPolicy: Always
envFrom:
- configMapRef:
name: mongo-s3-backup-config
volumeMounts:
- name: snapshot-volume
mountPath: /snapshots
- name: snapshot-volume
mountPath: /data/db
subPath: "path/to/dump"
restartPolicy: OnFailure
volumes:
- name: snapshot-volume
persistentVolumeClaim:
claimName: mongo-s3-restore-pod
---
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: mongo-s3-restore-pod
namespace: mongo-s3-backup
labels:
app: mongo-s3-restore-pod
spec:
accessModes:
- "ReadWriteOnce"
resources:
requests:
storage: 750Gi
```
Also we have an entire script that runs daily and archives the backups to our own S3, really would not like to have to do this as its prone to errors and we manage it.