-
Notifications
You must be signed in to change notification settings - Fork 328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Creating backups using the single helm chart #50
Comments
As I know, the |
actually |
Yeah this is why I was thinking about using a cronjob for it. But if it only works with file access to the data that is going to be a bit harder |
I think it should be possible, I am currently working on patching the helm chart to add a sidecar container to the server pod that would run Looks like https://gist.github.com/AntonFriberg/692eb1a95d61aa001dbb4ab5ce00d291 I only need to put an incremental vmbackup invocation into |
Regarding "btw, would be a bit less moving pieces if vmbackup would be able to send the "create snapshot" request itself": |
@ulikl ah, thank you, good to know! does it mean that when i pass a |
So does this mean we wouldn't have to go with the sidecar route and could go with a pod (cronjob) instead? Is |
I think you still need a sidecar to access the volume where snapshots are created. |
Ok wait, then how should I read:
(From: https://victoriametrics.github.io/vmbackup.html ) I might be missing some VM knowledge how snapshots work here tbh :D |
This is the URL on the VictoriaMetrics (vmstorage) instance itself, that would trigger a creation of a snapshot in its corresponding data directory. If vmbackup has access to that directory, it can then send the generated file wherever you point it (S3, GCP, etc). |
Ahhhh ok check 👍 . Yeah then it's going to be really hard not using a sidecar |
to run backups using helm charts there're two options:
extraObjects:
- apiVersion: v1
kind: ConfigMap
metadata:
name: vmbackup-cron
data:
root: |
* * * * * /vmbackup-prod -storageDataPath=/storage -snapshot.createURL=http://localhost:8428/snapshot/create -dst=<set-preferable-snapshot-destination>
server:
extraContainers:
- name: vmbackup
image: victoriametrics/vmbackup
command: [/usr/sbin/crond]
args:
- -f
- -l8
volumeMounts:
- name: vmbackup-cron
mountPath: /etc/crontabs
- name: server-volume
mountPath: /storage
extraVolumes:
- name: vmbackup-cron
configMap:
name: vmbackup-cron |
Been using victoriametrics for a few months now and it's absolutely a breeze to set up with these helm charts. But what I'm missing here is a way to back up to a network drive (cifs/smb in my case). Now I'd gladly add this to the helm chart with a cronjob. But up on researching this I found that the only way it seems to backup is using direct access to the data dir. Is there a way to backup metrics over TCP/UDP from another pod?
The text was updated successfully, but these errors were encountered: