Innhold er ikke tilgjengelig i valgt språk enda
The entire VPS is backed up by Hostinger.
This section explains in detail how Jottacloud is used on my Hostinger VPS for backups. The main purpose is database backup / SQL dump of MariaDb tables and contents. In the future images can be synced from Jottacloud to a shared volume on the VPS for Docker too. Manual backup of some important files to the Jottacloud archive is also easy to do.
Jottacloud CLI is used, in addition to standard backup mechanisms of Jottacloud. Please refer to Jottacloud CLI commands. Be aware of the 30-day storage limitation before Jottacloud removes old backups, this limitation can be a reason for looking at other cloud providers with similar services. The VPS (Ubuntu) is set up to use the standard command line backup mechanism (mysqldunp) for the MariaDB database. MariaDB is managed by Cyberpanel in my setup, and I could have used this paid service. I prefer the Jottacloud backup, because it is more flexible and I already have paid for a Jottacloud account. The Jottacloud archive can be used to avoid the 30-day limitation. Jottacloud CLI can be used for long term storage to store in the archive. This solution is not set up yet.
I have used the Jottacloud Ubuntu recipe. You need a token to log in the first time You have to name the backup device, I have called it techreier.
The system and service manager for Linux is used (systemd). Services set up to run automatically:
The files listed below is stored in the /etc/systemd/system folder.
db-backup.service:
[Unit]
Description=Daily database backup
[Service]
Type=oneshot
ExecStart=/root/dbbackup.sh
dbbackup.sh is the bash script that performs the backup running mysqldump for MariaDB, and the most complicated part of the solution.
db-backup.timer:
[Unit]
Description=Run database backup daily at 02:00
[Timer]
OnCalendar=*-*-* 02:00:00
Persistent=true
[Install]
WantedBy=timers.target
jottad-custom.service:
[Unit]
Description=Jottacloud Custom Daemon
After=network-online.target
Wants=network-online.target
[Service]
ExecStart=/usr/bin/jottad
User=root
Type=simple
Restart=always
RestartSec=5
[Install]
WantedBy=multi-user.target
The backup folders are added using jotta-cli directly. Some jotta-cli commands:
jotta-cli login // Important to get started
jotta-cli add /root/db_backups // Add folders to backup
jotta-cli status // Get current status of jotta-cli
jotta-cli scaninterval 15m // Interval of scanning files for backup.
run-jottad // start the jottad deamon manually (not recommended, use systemctl instead)
The catalog /root/.jottad stores jotta cli sonfiguration and logs. The file jottabackup.log is essential to study if a problem appears. It can be required to use sudo, even as a root user for jotta-cli.
Some important systemctl commands to instruct systemd:
// TIMER commands used for db-backup.timer
systemctl daemon-reload //always required after changes in files it uses
systemctl enable db-backup.timer //mark timer to start on boot
systmctl start db-backup.timer //start timer immediately
systemctl restart db-backup.timer //restart timer immediately
systemctl status db-backup.timer //shows current timer status
journalctl -u db-backup.timer -xe //shows detailed log message for the timer
// SERVICE commands:
systemctl status jottad-custom.service //check status of the jottad service
systemctl status mariadb //check status of the mariadb service
systemctl start jottad-custom.service //manually start the jottad service
systemctl start db-backup.service //manually start the backup service
Systemd manages services and can be started, stopped and restarted independently. Timers can be set up for scheduling the services. Jottad-customer services does not use timer, because the jottad deamon runs all the time in the background.
I plan to set this up for images, so the docker container can fetch this as a mounted volume. Not done.