fbrettnich / hcloud-snapshot-as-backup Goto Github PK

Hi,

I just deployed a docker container (and i'm pretty new to docker). I added;
--restart unless-stopped \ to start the container when the host is rebooted for some reason, so I don't forget to start the container.

I wanted to test the snapshot execution so I don't have to wait until 1 am following the crontab so I ran;
docker exec -it 7f6772ed0a6d python3 snapshot-as-backup.py

this gave me as output;
Starting CronScheduler [0 1 * * *]...

I've waited about 15min but I don't see any snapshots being made. Is it possible somehow? Thanks!

The possibility to specify multiple API tokens to run the script across multiple Hetzner Cloud projects at the same time.

Currently, only the first page of snapshots is queried.
This means that only a maximum of 25 snapshots are queried and processed.
All pages of the snapshot images must be retrieved, as is already the case with the servers.

For more information on retrieving the images, see the Hetzner documentation: https://docs.hetzner.cloud/#images-get-all-images

Request

Currently it's only possible to use a cron schedule for defining when snapshots are created. This is nice until you realise that you may require a more complex schedule.

As an example, I would also like to keep X weekly snapshots, keep Y monthly snapshots and Z yearly snapshots (ofcourse without manual intervention).

Possible implementation

Something that can be used to create a more flexible schedule is rotate-backups. This works quite well for things like database backups, so I assume it can be used for this as well.

Can you please add an option to shutdown the VPS before attempting snapshot?

can we have something like a daily, weekly, monthly snapshot?

After upgrading to the latest Debian Bookworm I started getting this error message:

/usr/bin/python3 /opt/hcloud-snapshot-as-backup/snapshot-as-backup.py > /dev/null Traceback (most recent call last):

  File "/opt/hcloud-snapshot-as-backup/snapshot-as-backup.py", line 9, in <module>
    from cron_validator import CronScheduler
ModuleNotFoundError: No module named 'cron_validator'

Then if I try to install the module cron-validator with:

pip install cron-validator

I'm getting this:

error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
    python3-xyz, where xyz is the package you are trying to
    install.

    If you wish to install a non-Debian-packaged Python package,
    create a virtual environment using python3 -m venv path/to/venv.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
    sure you have python3-full installed.

    If you wish to install a non-Debian packaged Python application,
    it may be easiest to use pipx install xyz, which will manage a
    virtual environment for you. Make sure you have pipx installed.

    See /usr/share/doc/python3.11/README.venv for more information.

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.

Any idea what to do?

Thanks.

Make script available as Docker container for easier use

Problem

Currently you can name the snapshot with for example %name%-%timestamp% format. This will result in something like new-server-1667887200. The problem is, timestamps are not really that human friendly, as you just can't directly see what the date and time is when the snapshot was created.

Proposed

Allow user specified custom datetime format (using for example strftime), and fallback to timestamp as default to avoid breaking change.