![]() ![]() ![]() There's over 80 different variables and a good way to get a feel of how this all works is to set both commands to ![]() See for additional information on email alerts. The only difference is that the latter prefixes all variable names with BVCKUP_. The variable set used for email alerts is almost exactly as the set used for external commands. īVCKUP_errors - the number of errors encountered by the backupīVCKUP_stats_files_created - self-explanatoryīVCKUP_stats_files_updated - self-explanatoryīVCKUP_stats_files_deleted - self-explanatoryīVCKUP_stats_files_moved - self-explanatoryīVCKUP_stats_bytes_read - how much data was read from the diskīVCKUP_stats_bytes_written - how much was written outīVCKUP_time_started - start time (see below)īVCKUP_time_elapsed - elapsed time in human readable format, e.g “4 hours 16 minutes” or “13 seconds” Some variables are valid only for a post-backup command as they capture the _results_ of a backup run, e.g. The "failed" backup run is the one that did not manage to get to the actual backup phase and failed during the preparation (scanning/planning/etc) phase. Variable names start with BVCKUP_ and they cover Environment, Program details, Backup configuration and Backup status.īVCKUP_run - the run number of the backupīVCKUP_status - the state of the backup and it is set to "Initializing" for pre-backup command, and to one of "Cancelled", "Completed", "Failed" for the post-backup command. Or something else that can be executed by invoking shell rather than by spawning a process (see below).īy default, the program will wait for both commands to complete before proceeding with the backup, but timing out after 1 hour.Īll aspects of this behavior are configurable - it's possible to change the timeout, make the program launch the command and continue with the backup immediately, cancel the backup if the command doesn't exit with a specific code, etc.ĭetails of the backup state and configuration are passed to the commands with a set of environment variables that are set up by the program. They can be used to cancel backups if certain condition is not met, to mount volumes before the backup, to rearrange things after a backup, to feed events and alerts into existing management systems, etc. Pre/post-backup commands allow customizing both the logic and the flow of every backup. ![]() These can be configured in the More Options section of Backup Settings window. I could use command-line parameter, but I would also have to modify that as well.īy supporting empty portable.dat file in bvckup2.exe folder, and placing both app and service config data folders in same folder, I can keep it on a separate partition, and move the bvckup folder around to my liking, without ever having to worry about specifying where the config folders are/go - it just works, as they are always in the same folder as is possible to execute arbitrary commands at the very start and at the very end of a backup run. If I want the config data elsewhere, I have to modify both of these again. I understand the redirect.ini option, service config registry option, and command line option for specifying different config folder, and that it might be considered "messy" to have config data and exe together, but the problem with the existing solution's, is that a Bvckup folder, with all corresponding config data, cannot be moved around as easily.įor example, suppose I re-install Windows, I have to re-copy over the redirect.ini file, and change the service config registry value again. If found, it will automatically place config folder in same folder as bvckup2.exe. Apr 24, 2023+1 for portable idea - I would also like to see Bvckup2.exe look for an empty file, like portable.dat, in same folder as itself. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |