Docker-based project server with automatic backups

After a long day of diving into Postgres and Project Servers, I'm writing up a guide on setting up a docker-compose stack for a Project server that runs automatic backups. I'm hoping this will be helpful to everyone using QNAP or Synology systems by making it easier to get a project server running.

The backups can be created at configurable intervals, and can be automatically pruned to keep x backups per day/week/month. The backup files are also compatible with Resolve's restore function.

A big part of this is using PostgreSQL 11.x.x, which is faster, significantly more secure, and not EOL, compared to the early 9.x.x versions that Resolve installs by default. On Windows, it's easy to uninstall PostgreSQL 9 and install 11, and when you run any database command Resolve will ask you to point it to the new PostgreSQL version. Is there a way to do that on a Mac? Without that, database tasks like backing up or optimizing fail.

Also, would anyone want to help test? I'm hoping to have a GitHub project up in the next few days

Just use https://pgbarman.org/

Apart from that I can hardly think of any worse place to run a PostgreSQL server than a qnap NAS.

Resolve workload is OLTP, lots of random IO that greatly benefits from living on a SSD and really gets trashed on parity based RAID levels like 5 and 6.

Then Qnaps are ultra low memory devices which again is the exact opposite
what an OLTP database wants.

A raspberry Pi with an SSD will likely outperform any such setup.

Postgres is extremely mature and longer around than most of you have internet access. There is really no need to come up with custom backup scripts. Just use industry standards and get on with life.

I'll have to look into pgbarman, looks pretty neat! The issue I see with this is that its archives are incompatible with Resolve's backup/restore functions, and my goal was to make things simple for smaller post houses that likely don't have IT staff.

I understand the concern about smaller/cheaper QNAP's with little RAM and no SSD's, but most people are running their OS and packages on SSD's these days, and anyone with a ZFS based box is likely going to have plenty of RAM. Really if it's a QNAP worth editing off of, it will likely have the resources to run a db. Again, my goal was simplicity, and setting up a Linux server from the ground up is not that.

Alright, here is the GitHub link if anyone is interested. If anyone has a Synology NAS and can test installation or contribute an installation guide that would be very helpful

https://github.com/ematson5897/Docker-Davinci-Resolve-Project-Server

Alright, here is the GitHub link if anyone is interested. If anyone has a Synology NAS and can test installation or contribute an installation guide that would be very helpful

https://github.com/ematson5897/Docker-Davinci-Resolve-Project-Server

Maybe a little late to the party, but I just updated to resolve 18 now that it got out of beta and gave it a try on my QNAP NAS. It works beautifully! Of course I saved my old QNAP container as a backup, but compared to the hassle of setting up the NAS the first time this makes the whole process A LOT easier. Good work (I guess you're the main author)!

Alright, here is the GitHub link if anyone is interested. If anyone has a Synology NAS and can test installation or contribute an installation guide that would be very helpful

https://github.com/ematson5897/Docker-Davinci-Resolve-Project-Server

Maybe a little late to the party, but I just updated to resolve 18 now that it got out of beta and gave it a try on my QNAP NAS. It works beautifully! Of course I saved my old QNAP container as a backup, but compared to the hassle of setting up the NAS the first time this makes the whole process A LOT easier. Good work (I guess you're the main author)!

Glad to hear it!

Good morning,

I'm very interested in this for deploying the project server to a QNAP NAS on Docker using the Container Station - thankyou for putting this together and saving us all some time!

I noticed that you mention to put the db files on an SSD and I wondered why?
We're using a RAID 5 configuration with groups of 4 (providing approx 18Gb/s througput) with 2Tb SSD Caching - would that suffice?

Regards,
Jon

Good morning,

I'm very interested in this for deploying the project server to a QNAP NAS on Docker using the Container Station - thankyou for putting this together and saving us all some time!

I noticed that you mention to put the db files on an SSD and I wondered why?
We're using a RAID 5 configuration with groups of 4 (providing approx 18Gb/s througput) with 2Tb SSD Caching - would that suffice?

Regards,
Jon

Are you on QTS, or QuTS Hero?

I use an official Docker PostgreSQL database on Raspberry Pi 4 that backs up all Resolve databases every day, deletes the 30+1 day backup so I still have 30 days of backup, archives the last day of the month backup.
It work with a combination of cron that calls some shell scripts (maybe I should have used Python instead)
It works very effectively and has saved my ass several times.

I did some testing with the PostgreSQL database on a Synology NAS, but it was too stressful whenever an update appeared for the NAS, and there were some incidents that could have been very problematic.

My advice is that NAS are meant for putting files on and that's it.

Good morning,

I'm very interested in this for deploying the project server to a QNAP NAS on Docker using the Container Station - thankyou for putting this together and saving us all some time!

I noticed that you mention to put the db files on an SSD and I wondered why?
We're using a RAID 5 configuration with groups of 4 (providing approx 18Gb/s througput) with 2Tb SSD Caching - would that suffice?

Regards,
Jon

Are you on QTS, or QuTS Hero?

We're on QTS 5.0.1.2248