Feature/new backup

The current backup implementation has issues with larger database footprints (>20G).

First, a scratch space is needed for the basebackup process, which (temporarily) consumes a lot of unnecessary storage space.

This MR minimizes resource usages by taking a so-called low-level backup (see here) directly via a postgres client connection.