So as a test, I've setup PBS as a VM on my Synology NAS (it makes sense, it only runs backup at night and it uses almost no resources during the day). However, my question is regarding the location for the storage of the backups. Right now, I have the datastore as the local disk of the PBS VM. I've seen other people have the PBS VM write to a NFS share. Isn't it "extra work" to have it write to NFS share when it can just backup to local disk that is part of the PBS VM, or am I missing something?
Running PBS as a VM on my Synology - Backup to NFS share or the PBS VM's own disk?
- Thread starter inlinexmr
- Start date
Although it is possible to re-create the PBS VM on the Synology from scratch you may wish to back it up. In this case you usually do NOT want to backup also the whole backup data but only the functionality of the VM. This is possible only if the actual backup data store is "somewhere else", not in the (single?) virtual disk of the VM. (Can you backup a VM in Synology whith selecting which virtual drives to get included in the backup? What happens on restore of the VM?)
The long way through the network stack (twice!) reduces the IOPS drastically. And we all know PBS wants the performance of SSDs for the datastore!
That said I am doing exactly this. The only necessary tweak was to add some (mirrored, expensive) SSDs for Btrfs metadata on the Synology.
To repeat again: this construction is NOT recommended. But it may work...
The long way through the network stack (twice!) reduces the IOPS drastically. And we all know PBS wants the performance of SSDs for the datastore!
That said I am doing exactly this. The only necessary tweak was to add some (mirrored, expensive) SSDs for Btrfs metadata on the Synology.
To repeat again: this construction is NOT recommended. But it may work...
You can run PBS in docker on synology nas. https://github.com/ayufan/pve-backup-server-dockerfiles
(i made an own docker image, and it works good!)
(i made an own docker image, and it works good!)
PBS needs IOPS performance. So yes, virtual disk instead of NFS should perform better.
As i guess, you should be able to use volume mapping directly from docker to the synostore itself - this should be the best way to get most IOPS as possible.
The only thing i was thinking about to use PBS in docker on the syno - The recommendations for CPU/RAM for garbage collection and deduplication are relatively high. Someone has experience how this is performing on different models?