-
Notifications
You must be signed in to change notification settings - Fork 1
Testing the WABAC Machine (dry run)
François edited this page Jun 18, 2015
·
1 revision
If, for some reason, you want to conduct a dry-run, you can add the --dry-run
flag in the opts
preference in your configuration file:
[snip]
opts=(
--dry-run
--stats
--archive
[snip]
)
[snip]
In DRY RUN MODE, the WABAC Machine:
- doesn't actually copy the files (doesn't create a new backup),
- doesn't remove expired backups,
- doesn't create a new
latest
link.
It can be useful if you want to test changes in your configuration file, if you are not confident, if you want to see what would have happend, etc.
Please also note that:
- This flag doesn't have any effect when invoking the WABAC Machine with the
init
andinfo
verb. - Preflight and postflight scripts will actually run.
WABAC Machine | Copyright © 2009-2016 François Kubler (@fkubler)