#hc14s — Public Fediverse posts

#HamChallenge Week 14: Implement and describe a backup solution for your ham radio log.

I use RumLogNG on macOS, and after filling in the log database I run a shell alias that copies the main database to a file containing today’s date, in my cloud storage folder. It also gets backed up by Time Machine every so often. I also take full ADIF exports regularly, for reading into WSJT-X and various online logbooks.

@hamchallenge #HC14S #hamradio

#HamChallenge Week 14: Implement and describe a backup solution for your ham radio log.

I use QLog as main logging app. It automatically creates backups of the log. I also regularly backup to an external hard drive.
Also my uploads to Cloudlog can be seen as backup as it is possible to download at least a mininum set of QSO info from Clublog.

@hamchallenge #HC14S #hamradio #amateurradio #Amateurfunk

#hamchallenge Week 14: My #hamradio logbook #backup system is simple: My central log (to which I live-log contacts and import all my contest logs) is the console logger "YFKlog", which uses a MySQL database backend. It's running on a Hetzner VPS which creates nightly snapshots of the system disk that reach back seven days. In addition, a nightly cron-job creates a database dump which gets rsynced to another VPS in another datacenter. I also regularly upload my log to LoTW. #HC14S @hamchallenge

For this week's #hamchallenge : My primary logging software is #Wavelog. The webserver and backend database both run on virtualized machines in a #HighAvailability #Proxmox #cluster (same one that hosts this instance!). Those are backed up daily to another machine on site via PBS, then those backups are synced to a remote server running in a house in another city.

In addition, my log is also synced to both #QRZ and #LOTW every 6 hours or so, but I didn't think it qualifies as a true backup, since there is some data which those logs don't record.

#HC14S @hamchallenge #hamradio #amatuerradio