I'm a big believer in backup routines telling you of any failures, rather than just failing silently. I have many SyncBack Free profiles running and sending emails about completion status. The number of emails actually has gotten bothersome. So I'm looking into ways for backup results to be summarized and emailed once a day.
A complication is that I also use other backup routines (mainly a wrapper script that I wrote for Microsoft's Robocopy) and I would like the daily summary email to include completion status results from those routines as well as from SyncBack.
Since all of the backup tools in question send emails, one solution is to create a listserv, e.g. at GoogleGroups, and have the backup tools send their emails to the group. Then, subscribe to the group with preferences that call for a daily digest email. But I'd rather not get this third-party infrastructure involved.
This week I've adapted my backup scripts to write their completion status info into a text file on a file server on my LAN. Another script is scheduled to email that text file at the end of each day. Now I'd like to get SyncBack profiles to write their completion status to that same text file.
Judging by a read of the SyncBack Free help file, I'll be able to read a completion status exit code from SyncBack Free if I start the program from a wrapper script. The script can then write the status text I need based on the exit code.
Comments or suggestions welcome!
----
From the help file:
Exit codes
0 Success, no error.
100 SyncBackPro did not close because of user interaction or the donotexit
parameter was used
etc.
A complication is that I also use other backup routines (mainly a wrapper script that I wrote for Microsoft's Robocopy) and I would like the daily summary email to include completion status results from those routines as well as from SyncBack.
Since all of the backup tools in question send emails, one solution is to create a listserv, e.g. at GoogleGroups, and have the backup tools send their emails to the group. Then, subscribe to the group with preferences that call for a daily digest email. But I'd rather not get this third-party infrastructure involved.
This week I've adapted my backup scripts to write their completion status info into a text file on a file server on my LAN. Another script is scheduled to email that text file at the end of each day. Now I'd like to get SyncBack profiles to write their completion status to that same text file.
Judging by a read of the SyncBack Free help file, I'll be able to read a completion status exit code from SyncBack Free if I start the program from a wrapper script. The script can then write the status text I need based on the exit code.
Comments or suggestions welcome!
----
From the help file:
Exit codes
0 Success, no error.
100 SyncBackPro did not close because of user interaction or the donotexit
parameter was used
etc.