Originally posted by: <email address deleted>
I just added the following line to my fhem.cfg
define Backup notify Backup "/bin/tar -c -f
/var/InternerSpeicher/fhem.tar.gz /var/InternerSpeicher/fhem"
and saved it.
Now I can backup by creating a rule or simply typing "trigger Backup" in the
Webinterface.
Ignisquivir
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
Originally posted by: <email address deleted>
I played around a little with the Backup, and have now arrived at (enter
into fhem.cfg)
define Backup notify Backup "/bin/tar -c -f ../fhem$(date
\+%%Y%%m%%d%%H%%M).tar.gz -C ../ fhem"
attr Backup comment restore with tar archive in /var/InternerSpeicher, then
issue "tar -xv -f fhem.tar.gz
attr Backup room hidden
This will create a tar archive with timestamp (fhemyyyymmddhhmm.tar.gz) in
/var/InternerSpeicher
As some people seem to think it's enough to save fhem.cfg frequently, I
want to stress that all sorts of trouble can happen to the rest of the
files.
What about an "updatefhem" that creates a state not compatible with your
present setup ?
What about private modules that are not part of the distribution ?
What about collected data (weather, logs, etc., etc.) ?
What about fingertrouble ?
Or, as the great philosopher Murphy put it: "If it can go wrong, it will go
wrong!"
Additions / Modifications welcome.
ignisquivir
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com