• The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Removing remote storage backups

fmmek

New Pleskian
Hi there,

Are remote stored backups supposed to be removed by the following option:

Maximum number of full backup files to store (including both scheduled and manual backups)

This option is set to 4.

After switching to only storing backups remotely it appears that full backups are no longer deleted, It did however keep the last 4 local backups.

Is this by design or should remotely stored backups also be removed by this scheduled task.
 
It should also remove the remote backups. However, if they are not being removed, I suggest to check the logs of the backup process for the reason why the remote backups could not be removed.
 
It should also remove the remote backups. However, if they are not being removed, I suggest to check the logs of the backup process for the reason why the remote backups could not be removed.

I checked the backup.log located in the folder of last nights scheduled backup in /var/log/plesk/PMM

I couldn't see anything concerning the removal of backups. Am I looking in the right place? Any more specifics what I should look for?

Thanks for your help so far.
 
I do not have an example for an unsuccessful removal of old backup files. So I am not perfectly sure, but it probably works somewhat similar to this:

1) Find the time in the backup log files when "delete-dump" is executed:
# grep delete-dump *
in your backup log directory of the backup will yield something similar like
Code:
[2022-02-16 00:14:58.100|18059] INFO: pmm-ras started : /usr/local/psa/admin/bin/pmm-ras --delete-dump --session-path=/usr/local/psa/PMM/sessions/2022-02-15-233318.887 --dump-specification=backup_info_2202132334_2202152340.xml
To me this looks like the moment when Plesk tries to delete a previous backup file. You can also try to search for terms "delete", "remove" in the log files.

2) Look into the log files at, around and after that timestamp, e.g.#
# grep 00:14:58. backup.log
will yield something similar like this if something was deleted:

Code:
[2022-02-16 00:14:58.078|17050] INFO: Repository 'ftps://redacted': Validate incremental backup backup_2202132334_2202152340.tar
[2022-02-16 00:14:58.078|17050] INFO: Find packed incremental backups in '' for prefix 'backup' and base version 2202132334
[2022-02-16 00:14:58.082|17050] INFO: pmm-ras finished. Exit code: 0
[2022-02-16 00:14:58.100|18059] INFO: pmm-ras started : /usr/local/psa/admin/bin/pmm-ras --delete-dump --session-path=/usr/local/psa/PMM/sessions/2022-02-15-233318.887 --dump-specification=backup_info_2202132334_2202152340.xml
[2022-02-16 00:14:58.100|18059] INFO: Repository '/home/backup': Initializing...
[2022-02-16 00:14:58.100|18059] INFO: Repository '/home/backup': Initialized
[2022-02-16 00:14:58.100|18059] INFO: Repository '/home/backup': Get backup info from backup_info_2202132334_2202152340.xml
[2022-02-16 00:14:58.100|18059] INFO: Repository '/home/backup': Get initial backup info for backup_info_2202132334_2202152340.xml
[2022-02-16 00:14:58.100|18059] INFO: Repository '/home/backup': Get info from .discovered/backup_info_2202132334_2202152340/props
[2022-02-16 00:14:58.101|18059] INFO: Repository '/home/backup': Get info from .discovered/backup_info_2202132334_2202152340/storages
[2022-02-16 00:14:58.101|18059] INFO: Read properties from xml backup_info_2202132334_2202152340.xml
[2022-02-16 00:14:58.101|18059] INFO: Repository '/home/backup': Validate backup backup_info_2202132334_2202152340.xml
[2022-02-16 00:14:58.101|18059] INFO: Repository '/home/backup': Get info from .discovered/backup_info_2202132334_2202152340/props
[2022-02-16 00:14:58.101|18059] INFO: Repository '/home/backup': Get info from .discovered/backup_info_2202132334_2202152340/status_OK
[2022-02-16 00:14:58.101|18059] INFO: Repository '/home/backup': Validate incremental backup backup_info_2202132334_2202152340.xml
[2022-02-16 00:14:58.101|18059] INFO: Find incremental backups in '' for prefix 'backup' and base version 2202132334
[2022-02-16 00:14:58.105|18059] INFO: Repository '/home/backup': Get info from .discovered/backup_info_2202132334_2202152340/dumpresult_SUCCESS
[2022-02-16 00:14:58.105|18059] INFO: Find incremental backups in '' for prefix 'backup' and base version 2202132334
[2022-02-16 00:14:58.109|18059] INFO: Repository '/home/backup': Delete backup backup_info_2202132334_2202152340.xml
[2022-02-16 00:14:58.109|18059] INFO: Repository '/home/backup': Get info from .discovered/backup_info_2202132334_2202152340/storages
[2022-02-16 00:14:58.109|18059] INFO: Repository '/home/backup': Get info from .discovered/backup_info_2202132334_2202152340/props

In that output notice the line
Code:
[2022-02-16 00:14:58.109|18059] INFO: Repository '/home/backup': Delete backup backup_info_2202132334_2202152340.xml

In case a file cannot be deleted, it will probably show an error entry in the log instead of a successful completion.

Can you see similar entries in your logs? Or better: Can you identify the location where deletion fails?
 
Update, i could not find anything in the logs.. however remaking the schedule seems to have fixed the issue, it's all working great now! Thanks for your help!
 
Back
Top