• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx

  • We are developing a new feature in Plesk that will help you promote your websites or business on social media. We want to conduct a one-hour online UX test to present the prototype and collect feedback. If you are interested in the feature, please book a meeting via this link.
    Thank you in advance!
  • 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.

Issue Incremental Backups - always full backup

froggift

New Pleskian
Hi,

our Server has the newest CentOS 7.X and the newest Plesk Onyx Version Running.

Since around two weeks the server is making a full backup every day. Configuration is set to 1 full per week! (See attached Screenshots)

Is anyone else having this issue? Additional information: we store our Backups on an FTP Server.
 

Attachments

  • 5316F4B9-7147-408F-9621-98EF5DC3A0FB.jpeg
    5316F4B9-7147-408F-9621-98EF5DC3A0FB.jpeg
    956.8 KB · Views: 21
  • FB515275-C6BF-45F7-A4AB-A45D2A8B865F.jpeg
    FB515275-C6BF-45F7-A4AB-A45D2A8B865F.jpeg
    638 KB · Views: 19
I know this behavior from when I was hosting at Host Europe on a Virtual Server. Plesk then always backs up the whole server content no matter if something changed or not. I never found a solution to this and accepted to have to buy a large FTP to compensate the extra size. Only when switching to a dedicated it suddenly started working as intended.
 
I know this behavior from when I was hosting at Host Europe on a Virtual Server. Plesk then always backs up the whole server content no matter if something changed or not. I never found a solution to this and accepted to have to buy a large FTP to compensate the extra size. Only when switching to a dedicated it suddenly started working as intended.

Interesting, but I didn‘t change the Server or anything else. It suddently stopped working.
 
Have you tried setting up the backup job from scratch? Or do you run any kind of software on the server that actually "touches" all files so for plesk they are marked as "modified"? Any odd log entries like no incremental backup possible, doing full backup instead? Like I said, I never really came behind the works on my problem so I hope you can fix yours, maybe an official could chime in here.
 
Already searched the logs. Nothing suspicious there... File dates are all normal there is no tool running which is changing anything regarding the file date or anything else.



Gesendet von iPhone mit Tapatalk
 
Do your backups opened without any errors? Or can you unpack them manually? Also you may check manually size and modification time of some file backed up by using stat command.
 
It should be verified that the backup is actually present on the FTP storage space and that no other device is using the same FTP storage space. For example if two systems use the same FTP account, the backup will likely not work correctly, because the correct backup archive files cannot be identified to determine whether an increment or a new full backup needs to be created. In that case a full backup will be created.

Please see this article, too, and check whether it applies to your case Unable to create an incremental backup: Unable to load previous backup index required for making incremental backup, full dump will be created instead .
 
Do your backups opened without any errors? Or can you unpack them manually? Also you may check manually size and modification time of some file backed up by using stat command.

It should be verified that the backup is actually present on the FTP storage space and that no other device is using the same FTP storage space. For example if two systems use the same FTP account, the backup will likely not work correctly, because the correct backup archive files cannot be identified to determine whether an increment or a new full backup needs to be created. In that case a full backup will be created.

Please see this article, too, and check whether it applies to your case Unable to create an incremental backup: Unable to load previous backup index required for making incremental backup, full dump will be created instead .

Both verified. Backups work and als restore works. As soon as I use the local server space to store Backups (instead of FTP) the incremental backups works as intended.
As soon as I start to use FTP Server again. Every backup is a full backup again.

Found something interesting in the logs!

pmmcli.log ( 08.10.2017 - planned backup to local server storage): --incremental is used and working

PHP:
[2017-10-08 03:01:03.131|26100] DEBUG: LOG: custom log /var/log/plesk/PMM/backup-2017-10-08-03-01-03-131/backup.log
[2017-10-08 03:01:03.137|26100] INFO: Executing asynchronously <subprocess[26101] '/usr/bin/perl /usr/local/psa/admin/bin/plesk_agent_manager server --owner-uid=434b4545-f2d8-4779-a32e-6e87964cb026 --owner-type=server --dump-rotation=-1 --incremental --split=1073741824 --description=Scheduled Backup. All configuration and content. --keep-local-backup --exclude-pattern-file=/usr/local/psa/PMM/sessions/2017-10-08-030103.132/exclude --session-path=/usr/local/psa/PMM/sessions/2017-10-08-030103.132'>
[2017-10-08 03:01:03.138|26100] DEBUG: Acquired session mutex: MainThread
[2017-10-08 03:01:03.138|26100] DEBUG: detecting running pmmcli daemon...
[2017-10-08 03:01:03.139|26100] DEBUG: starting pmmcli daemon...
[2017-10-08 03:01:03.149|26100] DEBUG: Executing asynchronously [26102] process. CmdLine is '/usr/local/psa/admin/sbin/pmmcli_daemon'
[2017-10-08 03:01:03.149|26100] DEBUG: Create type=Backup
[2017-10-08 03:01:03.265|26100] DEBUG: Released session mutex: MainThread
[2017-10-08 03:01:03.266|26100] DEBUG: Acquired session mutex: MainThread
[2017-10-08 03:01:03.266|26100] DEBUG: Update task id=628, type=Backup
[2017-10-08 03:01:03.378|26100] DEBUG: Released session mutex: MainThread
[2017-10-08 03:01:03.378|26100] DEBUG: <pmmcli.MakeDumpAction object at 0x266a350>: response
[2017-10-08 03:01:03.381|26100] INFO: Outgoing packet:
<?xml version="1.0" ?><response>
    <errcode>0</errcode>
    <data>
        <task-id>628</task-id>
    </data>
</response>


pmmcli.log ( 10.10.2017 - planned backup to FTP server storage): --incremental is ignored and not even used in the command even if it's configured in the Plesk GUI!

PHP:
[2017-10-10 03:01:03.780|17126] DEBUG: LOG: custom log /var/log/plesk/PMM/backup-2017-10-10-03-01-03-779/backup.log
[2017-10-10 03:01:03.790|17126] INFO: Executing asynchronously <subprocess[17127] '/usr/bin/perl /usr/local/psa/admin/bin/plesk_agent_manager server --owner-uid=434b4545-f2d8-4779-a32e-6e87964cb026 --owner-type=server --split=1073741824 --description=Scheduled Backup. All configuration and content. --keep-local-backup --session-path=/usr/local/psa/PMM/sessions/2017-10-10-030103.780 --output-file=ftps://[email protected]//plesk/ --ftp-passive-mode'>
[2017-10-10 03:01:03.791|17126] DEBUG: Acquired session mutex: MainThread
[2017-10-10 03:01:03.791|17126] DEBUG: detecting running pmmcli daemon...
[2017-10-10 03:01:03.791|17126] DEBUG: starting pmmcli daemon...
[2017-10-10 03:01:03.809|17126] DEBUG: Executing asynchronously [17128] process. CmdLine is '/usr/local/psa/admin/sbin/pmmcli_daemon'
[2017-10-10 03:01:03.810|17126] DEBUG: Create type=Backup
[2017-10-10 03:01:03.884|17126] DEBUG: Released session mutex: MainThread
[2017-10-10 03:01:03.884|17126] DEBUG: Acquired session mutex: MainThread
[2017-10-10 03:01:03.885|17126] DEBUG: Update task id=630, type=Backup
[2017-10-10 03:01:03.939|17126] DEBUG: Released session mutex: MainThread
[2017-10-10 03:01:03.939|17126] DEBUG: <pmmcli.MakeDumpAction object at 0x27d8350>: response
[2017-10-10 03:01:03.942|17126] INFO: Outgoing packet:
<?xml version="1.0" ?><response>
    <errcode>0</errcode>
    <data>
        <task-id>630</task-id>
    </data>
</response>

backup.log ( 10.10.2017 - planned backup to FTP server storage): Somehow Plesk can't find the last incremental backup:

"Unable to find last incremental backup, because of current backup has no version mark in the file name backup_domainmail_1710100301.tgz"

PHP:
[2017-10-10 03:01:13.451|18246] INFO: pmm-ras started : /usr/local/psa/admin/sbin/pmm-ras --get-diff --listing-file /usr/local/psa/PMM/tmp/incUserData2FOLbO --backup-file /var/lib/psa/dumps/clients/mydomain/domains/mydomain.de/backup_domainmail_1710100301.tgz --changes-file /usr/local/psa/PMM/tmp/chn0HvVzJTc --index-file /usr/local/psa/PMM/tmp/idxQUhM6psM --dependencies-file /usr/local/psa/PMM/tmp/depJYXhcTjs --id 2
[2017-10-10 03:01:13.452|18246] INFO: Repository '/var/lib/psa/dumps/': Initializing...
[2017-10-10 03:01:13.452|18246] INFO: Repository '/var/lib/psa/dumps/': Initialized
[2017-10-10 03:01:13.453|18246] INFO: Unable to find last incremental backup, because of current backup has no version mark in the file name backup_domainmail_1710100301.tgz
[2017-10-10 03:01:13.453|18246] INFO: Calculate list of files to pack
[2017-10-10 03:01:13.590|18246] INFO: pmm-ras finished. Exit code: 0
[2017-10-10 03:02:09.299|18314] INFO: pmm-ras started : /usr/local/psa/admin/sbin/pmm-ras --export-dump-as-file --dump-file-specification ftps://[email protected]//plesk/backup_1710100301.tar --use-ftp-passive-mode --dump-storage /var/lib/psa/dumps/ --split-size 1073741824 --session-path /usr/local/psa/PMM/sessions/2017-10-10-030103.780
[2017-10-10 03:02:09.300|18314] INFO: Repository '/var/lib/psa/dumps/': Initializing...
[2017-10-10 03:02:09.300|18314] INFO: Repository '/var/lib/psa/dumps/': Initialized
[2017-10-10 03:02:09.301|18314] INFO: Repository 'ftps://myftpstorage.de//plesk/': Initializing...
[2017-10-10 03:02:09.301|18314] INFO: Curl version: 0x72300
[2017-10-10 03:02:09.304|18314] INFO: Repository 'ftps://myftpstorage.de//plesk/': Initialized
[2017-10-10 03:02:09.304|18314] INFO: Repository '/var/lib/psa/dumps/': Export from /var/lib/psa/dumps to ftps://myftpstorage.de//plesk/backup_1710100301.tar
[2017-10-10 03:02:09.304|18314] INFO: Ftp init url ftps://myftpstorage.de//plesk/
[2017-10-10 03:02:09.589|18314] INFO: Repository '/usr/local/psa/PMM/tmp/repo_transport_tmp_nnYwQx': Initializing...
[2017-10-10 03:02:09.589|18314] INFO: Repository '/usr/local/psa/PMM/tmp/repo_transport_tmp_nnYwQx': Initialized
[2017-10-10 03:02:09.589|18314] INFO: Create directory /usr/local/psa/PMM/tmp/repo_transport_tmp_nnYwQx/clients/mydomain/domains/mydomain.de
[2017-10-10 03:02:09.590|18314] INFO: Link /var/lib/psa/dumps/clients/mydomain/domains/mydomain.de/backup_domainmail_1710100301.tgz to /usr/local/psa/PMM/tmp/repo_transport_tmp_nnYwQx/clients/mydomain/domains/mydomain.de/backup_domainmail_1710100301.tgz
[2017-10-10 03:02:09.590|18314] INFO: Add file '/usr/local/psa/PMM/tmp/repo_transport_tmp_nnYwQx/clients/mydomain/domains/mydomain.de/backup_domainmail_1710100301.tgz' to archive as 'clients/mydomain/domains/mydomain.de/backup_domainmail_1710100301.tgz'
[2017-10-10 03:02:09.591|18314] INFO: ENV[LANG]=en_US.UTF-8
[2017-10-10 03:02:09.591|18314] INFO: Executing utility: /bin/tar --create --file - --directory /usr/local/psa/PMM/tmp/repo_transport_tmp_nnYwQx --dereference --blocking-factor 1 --no-recursion --files-from /usr/local/psa/PMM/tmp/repo_transport_tmp_fhtg0g
[2017-10-10 03:02:09.620|18314] INFO: Ftp init url ftps://myftpstorage.de//plesk/backup_1710100301.tar
[2017-10-10 03:02:48.415|18314] INFO: The utility succesfully executed.
[2017-10-10 03:03:13.145|18314] INFO: Link /var/lib/psa/dumps/clients/mydomain/domains/mydomain.de/backup_domainmail_1710100301.tgz1 to /usr/local/psa/PMM/tmp/repo_transport_tmp_nnYwQx/clients/mydomain/domains/mydomain.de/backup_domainmail_1710100301.tgz1
[2017-10-10 03:03:13.145|18314] INFO: Add file '/usr/local/psa/PMM/tmp/repo_transport_tmp_nnYwQx/clients/mydomain/domains/mydomain.de/backup_domainmail_1710100301.tgz1' to archive as 'clients/mydomain/domains/mydomain.de/backup_domainmail_1710100301.tgz1'
[2017-10-10 03:03:13.146|18314] INFO: ENV[LANG]=en_US.UTF-8
[2017-10-10 03:03:13.146|18314] INFO: Executing utility: /bin/tar --create --file - --directory /usr/local/psa/PMM/tmp/repo_transport_tmp_nnYwQx --dereference --blocking-factor 1 --no-recursion --files-from /usr/local/psa/PMM/tmp/repo_transport_tmp_bcPfQl
[2017-10-10 03:03:13.266|18314] INFO: Ftp init url ftps://myftpstorage.de//plesk/backup_1710100301.tar1[/B]

So could anyone please help me out here? I need to get the incremental backups to FTP working again...
 
I'm having the same issue on my Plesk 12. All was good while the backups were set to be stored on the local server. This week I set them to the external FTP, so every time now a full backup is created instead of incremental. Any update on support your ticket?
 
Back
Top