Edit testing and debugging

Dan MacDonald
2023-10-15 20:21:59 +01:00
parent f6dc6f17a4
commit c0a5defe6f

@ -29,13 +29,13 @@ Keeping this in mind can help make more sense of the options described here: mos
## Testing and debugging
Its recommended to always use `--verbose` to see whats going on. It makes debugging easier.
It's recommended to always use `--verbose` or `-v` to see whats going on. It makes debugging easier.
During initial setup and testing of a backup you should use `--test`. This will do all the read-only operations, but will not change anything. It will show you exactly what its going to do.
During initial setup and testing of a backup you should use `--test`. This will perform all the read-only operations, but will not change anything. It will show you exactly what it's going to do.
If you encounter a problem and want to see the exact ZFS commands, use `--debug`. This outputs all the underlying zfs-commands in a different color. To even see the output of each command, use `--debug-output`.
If you encounter a problem and want to see the exact ZFS commands, use `--debug`. This outputs all the underlying zfs-commands in a different color. To see the output of each command, use `--debug-output`.
Note that debug mode will abort on the first failed dataset, and show a stacktrace. So its not recommended in production.
Note that debug mode will abort on the first failed dataset, and show a stacktrace so it's not recommended for use in production.
## Source and target SSH