Question Can I force incremental backups?

[ManuelGDot]

My backup space is currently limited so I'm having backups moved from their original FTP-Repo to another location.

But everytime I move a "full" backup Plesk will notice and create a new "full" backup - Plesk doesn't know that the full backup still exists only in another location.

Can I force Plesk to follow the schedule strictly and only create incremental backups? Does Plesk need the full backup to figure out, what it's gonna put into the incremental archive?

p.s. Yes I know for the restore I need to bring them all together again..

 

[virtubox]

My backup space is currently limited so I'm having backups moved from their original FTP-Repo to another location.

But everytime I move a "full" backup Plesk will notice and create a new "full" backup - Plesk doesn't know that the full backup still exists only in another location.

Can I force Plesk to follow the schedule strictly and only create incremental backups? Does Plesk need the full backup to figure out, what it's gonna put into the incremental archive?

p.s. Yes I know for the restore I need to bring them all together again..

Hello,
It's the normal incremental backup process. 1 Full backup then daily incremental backup based on the full one.

 

[ManuelGDot]

Hello,
It's the normal incremental backup process. 1 Full backup then daily incremental backup based on the full one.

Hi virtubox,

I'm aware that it's the normal process, I just wanted to know if I'm able to change that behaviour. Does Plesk rely on the presence of the Full Backup to create the incremental one?
Two scenarios I'm imagining:
a.) I have a "force incremental" switch so Plesk only creates incremental backups and ignores the "absence" of the full backup (it's not really absent, it's just out of reach of Plesk)

b.) Could it be split maybe, like this?
Full Backup (initial) remains on the server -> I'll take a manual copy to my 3rd remote location
Incremental Backups (daily) -> Only incremental go into FTP Repo and not on the server.

Thanks.