- Plesk for Linux
- Plesk for Windows
Logging of Plesk backup procedure is not detailed enough. How to increase its verbosity?
In order to enable backup debug logging for Plesk Backup Manager, enable Plesk debug mode.
Use the information below for enabling extended debug mode for backup operations:
For backup tasks that are performed in Plesk Backup Manager
Nothing needs to be done. Logs are collected with the
debug switch by default.
For scheduled backup tasks
To increase verbosity for scheduled backups, enable the
verbose_scheduled_backup_logs parameter in Plesk database using the command below:
To enable debug run:
# plesk db "REPLACE INTO misc (param,val) VALUES ('verbose_scheduled_backup_logs', 'true')"
Warning: It is strongly recommended to disable verbosity once the troubleshooting is finished. Otherwise, the server might quickly run out of free disk space, which will in turn lead to data loss and service downtime. Server performance will be affected as well.
To turn debug off, run:
# plesk db "DELETE FROM misc WHERE param='verbose_scheduled_backup_logs'"
For the 'pleskbackup' command-line utility
Add one or more verbose
-v options to the backup command.
For example, the below commands will back up the whole server with maximum verbosity in logs and output in a command-line interface:
# /usr/local/psa/bin/pleskbackup server -vvvvv
on Windows Server, multiple verbose options cannot be joined and has to be specified separately:
C:\> "%plesk_cli%\pleskbackup" --server -v -v -v -v -v
Additional debug logging for pmmcli-rc utility
In addition to debug mode mentioned above, enable debug mode:
pmmcli-rcfile in a text editor:
on Windows Server:
C:\> C:\Program Files (x86)\Plesk\admin\share\pmmcli\pmmcli-rc
Change the value of the
FORCE_DEBUG_LOGparameter from 0 to 1:
CONFIG_TEXT: FORCE_DEBUG_LOG 1
Save the changes and close the file.
Note: Do not forget to revert the changes back after troubleshooting.