Good stuff, seems well thought out. Hope you find the issue. Gary
On Wednesday, 12 December 2018 17:34:24 UTC+10, Dave Harper wrote: > > Gary, > > The backup strategy I use is a Python script I wrote that is started by > cron every night. I had read that there could be a problem if the database > is copied while it's being updated. The database is updated once a minute > by weeWX so the script monitors the mtime of the weewx.sdb file, waits for > the timestamp to change then waits about 15 seconds more before copying it > to a subdirectory off my home directory. I also copy the /etc/weewx > directory into the same backup subdirectory and then the script calls > Duplicity to do the actual backup. Duplicity works by starting with a full > backup the first time around and then doing incrementals from then on. A > restore starts with the original full backup and then applies all > incremental changes to get to the target restore date. To keep a restore > process within reason, I only do a month of incrementals and on the first > of each month the script creates a new monthly directory on the NAS. This > strategy has seemed to work well over the past year or so and looking into > why it failed this time around will be one of the top priorities for > tomorrow. > > Dave > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
