search

fititnt / ap-application-load-balancer

AP Application Load Balancer (AP-ALB). Sophisticated monolithic Ansible role to manage standalone and clusters of cross-platform and multicloud load balancers. Abstract HAProxy + OpenResty + On-the-fly auto HTTPS. Dedicated to Public Domain.
https://ap-application-load-balancer.etica.ai/
The Unlicense
1 stars 0 forks source link

MVP of optional backup strategies for apps/sysapps that cannot be recreated by scratch with Ansible #31

Open fititnt opened 4 years ago

fititnt commented 4 years ago

About the draft of backup-alb-full.yml / uninstall-alb-purge.yml

At /ad-hoc-alb/backup-alb-full.yml we already have one way to do a simply backup of main configuration files created by AP-ALB.

At this moment does not have option to not discard logs of applications, but as MVP it somewhat works. It also does not implement a script that could do the reverse.

That script was made mainly because of the ad-hoc-alb/uninstall-alb-purge.yml, that try to near unninstall all AP-ALB from a host and delete everyiting, but by default that purge will first call ad-hoc-alb/backup-alb-full.yml if the user did not explicitly disable backup before uninstall.

About this issue

On this issue, maybe is just some MVP about to document on YAML if one app, on a specific host, contains some directory that could handle data that worth to be saved from time to time or in a worst case scenario would be the one used to "move" apps from one node to another after total reconstruction of a node.

Note that this issue may not implement the full logistics (for example, may exist some external roles that could already sincronize encrypted backups from one directory to some remote source. But this MVP maybe could at least app new options to the Apps and Sysapps and then or create a Symlink, or copy the files to another directory, that this one is the one who should be handled by the backup strategy.

Default backup strategy

Since it could be simpler, maybe the default backup could be simple a copy of full directory without external dependencies.

Non-goals

For sake of simplicity, we will assume backup of files only. So if eventually have databases or some other storage, we could at best allow some hooks to be called before and after the actions, but the underline result should a file or a directory of files, preferable files that could be optimized by common backup strategies to use less bandwidth and remote space.

fititnt commented 4 years ago

Note to self: actually, /var/backup is not one ideal place to store non-system backups.