At this time proxmox backup only backs up VM and Containers - ths guide covers that.
What i didn't realize is the backup job is still defined on the cluster and PBS provides a new storage type that dedupes and managed all the vzdump files created - which is cool.
I decided to run proxmox backup on my Synology NAS where it has more reliable connection to the NAS (i.e. via memory) for doing deduple, garbage collection, prune, verification etc. However the steps here generally remain true.
Once again i used one of Derek Seaman's Awesome Blogs for the basis of this - but with my own tweaks (like using SMB instead of CIFS. As of 9/21 my tweaks are signifcnant, in the original blog it is missing steps to enable encoding acceleration in CTs and VMs.
this gist is part of this series
- create a PBS VM on your synology (see Derek's blog if you don't know how to do that)
- set password, IP, etc, call it something like pbs.mydomain.com etc
- login and check it looks ok - it should be!
- create a synology shared folder called proxmox
- hide it from explorer
- don't enable compression
- don't enable encryption unless you are truly paranoid
- assign only admins to it
- create a new user called proxmox on the synology for promox backup to access the shared folder
- set password to expire
- assign them to only the users group
- give them permissions to no apps and only the proxmox share created earlier
- login to PBS and access the shell
- create a username and password file using
nano /etc/samba/.syn01
in this example syn01 is the name of my synology - add the following based on the user you made ealier
username=proxmox
password=<yourpassword>
domain=WORKGROUP
- save the file
- create a mount point
mkdir /mnt/syn01
- now add a mount to fstab with the following command
echo "//192.168.1.30/proxmox /mnt/syn01 cifs rw,auto,uid=34,noforceuid,gid=34,noforcegid,credentials=/etc/samba/.syn01 0 0" >> /etc/fstab
note: in this example use your synology IP not the example above, if you did my other instructions correctly that is all you should need to change.
The uid and gid ensure you have no strnage issues with permission - these map to the backup user and group in proxmox
- perform a
systemctl daemon-reload
without this the fstab changed won't be picked up - now mount the share with
umount -a
- create a test fie with
nano /mnt/syn01/test.txt
populate it with some text and save - you should see it appear on the synology in file explorer with no errors
- navigae to
Datastores
and clickadd datastore
- name - call it whatevr you want, say
syn01
- backing path is
/mnt/syn01
leave GC and prune settings as is - click add
At this point it will add the storage and create all the chunks, this may take a few minutes. Aftewhich you should have a working datastore
If you plan to use SSL certificates you should configure them at this point as configuring later will invalidate the fingerprint. so if you do it after the nex step remember you will get a 500 error and need to copy the new fingerprint.
- on pve cluster navigate to
Datacenter storage
- click
add
and selectprxmox backup server
- ID is whatever name you want to call it, say,
pbs
- server = ip address or fqdn of your pbs server
- username and password is the pbs username and password you set earlier
- datastore is what you ever you named it ealier - in this example
syn01
- fingerpint - to get the fingeprint on the pbs server click
dasboard
clickshow figerprint
clickcopy
- now on the pve cluster console paste in the fingerprint and click
add
- (the namespace of Root can be left as-is)
You can now set your backup, gc, prune and verify jobs etc - this is beyond the cope of this gist