| Yes, I forgot to attach the conf file the first time. The attached has examples for both mysql and sqlite, for both source & destination. For mysql, the host, user, and password of course need to be filled in; likewise for the path(s) to the sqlite database file(s). The database name for a mysql destination can be whatever you want; in particular, “weewx” would work fine if you’ve got another weewx installation reading from that db.
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
|
dbackup.conf
Description: Binary data
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
|
wee_dbackup
Description: Binary data
This is great Les thank you! That sounds very much like a tool that could work. Do you have an example dbackup.conf I could use? On Friday, January 5, 2018 at 2:11:42 PM UTC-8, ln77 wrote: I wrote a little tool for syncing weewx data from one database to another, which I think can address Chris’ cloning request. It’s weewx-specific — when run, it copies all archive records from the source database that are later than the latest record in the destination database, to the destination database. The motivation was to do incremental backups to a remote mysql database, though mysql’s built-in cloning might be better for that. But it uses weewx’s database interface so it is supports the same types of databases and access that weewx does, with the same configuration files. To do the cloning it just needs to get fired off after every archive interval, either from a cron job or by packaging as a report generator.
To use from a cron job or manually, put it in the same directory as wee_reports, wee_extension, etc. The comment describes the config file(s) that specify the source and destination. The intent is that weewx.conf will specify the source in the usual case where the source is the active weewx database. The destination specification can be added to weewx.conf, or put in a separate config file.
-Les
On Friday, January 5, 2018 at 11:06:27 AM UTC-8, Huw Pearce wrote:
yeccch - requires tomcat and it's binary only cool idea though....
--
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+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
|
