We have a strong rule not to modify the config of a device during read-only operations (which a scheduled backup is). As such, we do not want to do 2 config modifications (enable something, disable it after).
There are quite a few reasons for this - in particular many customers use backup triggering - a change triggers a trap, which triggers Unimus backups through the API. This can cause infinite backup loops if we change config during backup.
What is more troublesome is that many customer run Unimus with read-only accounts, so in this case, this modification attempt would completely fail.
We recommend disabling debug output by default ("no logging console"), and you can always turn it ON during a debugging session if you need it ("terminal monitor" is always available). If you wish, you can additionally configure a separate VTY for the Unimus user, and disable logging only on that VTY. So by default, users would use a VTY that has logging enabled, but Unimus user uses a VTY that has no terminal logging.