Andre
My feedback
-
10 votes
-
65 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 667 ideas
- Atlas Data Lake 23 ideas
- Atlas Search 73 ideas
- Charts 140 ideas
- Compass 182 ideas
- Connectors (BI, Kafka, Spark) 20 ideas
- Database 90 ideas
- Drivers 39 ideas
- MongoDB CLI 15 ideas
- MongoDB for VS Code 31 ideas
- MongoDB Shell 12 ideas
- Ops Tools 286 ideas
- Realm 208 ideas
- UI 64 ideas
- University 0 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.