We have regular account backups that are generated every day. These backups contain all the account information for each account and are stored as .tar.gz files.
Recently we needed to explore the SQL data in some backups and found issues that the backup file size was so big it was causing a big slowdown in processing this request (from the client).
The account.tar.gz was 24Gb - This was stored remotely and so we needed to download 24Gb in order to open the file and then to extract the account.sql which was 100kb.
Almost all of the backups size is emails. Is there any way, or any how-to guide as to creating a backup system that stores account details seperately from mail details such as:
account.tar.gz = All account files and folders EXCEPT mail (and any related mail data)
account-mail.tar.gz = the account /mail/ folder (and any related mail data)
This would help enormously in only needing to download much smaller data amounts and opening much smaller files when we simply don't need to explore clients vast emails
Cheers
Recently we needed to explore the SQL data in some backups and found issues that the backup file size was so big it was causing a big slowdown in processing this request (from the client).
The account.tar.gz was 24Gb - This was stored remotely and so we needed to download 24Gb in order to open the file and then to extract the account.sql which was 100kb.
Almost all of the backups size is emails. Is there any way, or any how-to guide as to creating a backup system that stores account details seperately from mail details such as:
account.tar.gz = All account files and folders EXCEPT mail (and any related mail data)
account-mail.tar.gz = the account /mail/ folder (and any related mail data)
This would help enormously in only needing to download much smaller data amounts and opening much smaller files when we simply don't need to explore clients vast emails
Cheers
Last edited by a moderator: