Question Plesk Backup Manager : How to store account specific backups rather than in one massive file?

[MHC_1]

Server operating system version

Alma Linux 9.7

Plesk version and microupdate number

18.0.75

Using Dropbox Backup
Version
4.4.2-8333


lesk makes huge unwieldy server wide backups encompassing all accounts. However, these files are sent across for third party storage (in our case, Dropbox) but this makes the files are hugely unwieldy to deal with as Dropbox does not handle these files well (.tar) . WE have 200Gb files we need to download and open and explore to extract just a 100Mb part thereof (a single email mailbox from a single account).

How can we get Plesk to store the backups as individual account specific .tar files rather than a huge collective.

 

[MHC_1]

Ok I have found we can enable clients and resellers to set their own backup details. This helps.

BUT: If clients and resellers set their own backup details / schedules / files ARE THESE STILL INCLUDED IN THE SERVER WIDE BACKUP?

Thanks

 

[Kaspar]

Not sure what you've tried already and limits you ran into, so this is more of a generic answer than perhaps an solution to your specific problem. The backup manager has the option to restore individual domains, mailboxes or even single files within a webspace. There really should be no need to extract files manually from a backup (although in some cases, there might be).

If you want to restore deleted mail messages from a mailbox, simply restore just that particular mailbox from a Plesk backup. Is will restore any deleted messages and leave a current messages as they are.

BUT: If clients and resellers set their own backup details / schedules / files ARE THESE STILL INCLUDED IN THE SERVER WIDE BACKUP?

Yes. These backups are create independently of each other. However, if you create full servers backups and store those locally, customers (and I think resellers too) have access to these backups too and can restore their own accounts/domains/mailboxes from these server wide backups. Negating the need for customers to run there own backups (which can fill up your disk rather fast if you allow them to store backups locally too).

 

[MHC_1]

Not sure what you've tried already and limits you ran into, so this is more of a generic answer than perhaps an solution to your specific problem. The backup manager has the option to restore individual domains, mailboxes or even single files within a webspace. There really should be no need to extract files manually from a backup (although in some cases, there might be).

The thing is the backup manager only works on server-local files or the single most recent Dropbox file. But when the single most recent Dropbox file is replaced by an older Dropbox file (same name, same contents but from an earlier backup) the Backup manager can't "see" it.