Hi Luis,
Thank you for having parametrized the events. Great!
One remark though:
The most important parameter I use, %ERRORS, works fine.
Other simple parameters like %DATETIME work as well.
But most other parameters such as %USERNAME or %DBPATH don't.
I don't need them, so I am fine, but such parameters might be of interest to others.
Just to explain why I use parameters in events (we have had this discussion some 10 years ago!) :
Most of the people for whom I implement a backup solution are aging home users.
Whenever something goes wrong during backup, most of them just won't see the blinking Reflector icon in the task bar.
It can sit there blinking for months and nobody will notice the backups don't work correctly anymore, for whatever reason.
Therefore, when %ERRORS > 0, I pop up a red colored window the user has to acknowledge.
Similarly, when the backup has to go to an external drive (most aging people don't trust clouds...), I use a pre-backup event to check whether the external drive is present:
If not, %ERRORS will be > 0 since Reflector can't reach the target directory, allowing me to pop up a warning window asking to plug in the external drive. If this does not happen within a script specified period of time, my script cancels the job.
Best regards,
Ronald
Thank you for having parametrized the events. Great!
One remark though:
The most important parameter I use, %ERRORS, works fine.
Other simple parameters like %DATETIME work as well.
But most other parameters such as %USERNAME or %DBPATH don't.
I don't need them, so I am fine, but such parameters might be of interest to others.
Just to explain why I use parameters in events (we have had this discussion some 10 years ago!) :
Most of the people for whom I implement a backup solution are aging home users.
Whenever something goes wrong during backup, most of them just won't see the blinking Reflector icon in the task bar.
It can sit there blinking for months and nobody will notice the backups don't work correctly anymore, for whatever reason.
Therefore, when %ERRORS > 0, I pop up a red colored window the user has to acknowledge.
Similarly, when the backup has to go to an external drive (most aging people don't trust clouds...), I use a pre-backup event to check whether the external drive is present:
If not, %ERRORS will be > 0 since Reflector can't reach the target directory, allowing me to pop up a warning window asking to plug in the external drive. If this does not happen within a script specified period of time, my script cancels the job.
Best regards,
Ronald
Statistics: Posted by Frutchy — 26 Dec 2021, 12:46