Slow and large backups i need find solution

[leonep]

HI,
My backup size is 216GB . I store 2 weekly and 3 daily
Today i got a disk warn about low space.
The backup duration is also long , it is 8 hours !
i removed compression to save time , but it not helps about space
i have excluded something from backup with global exclude file.
i am thinking to remove mails from backups , but i am not very happy with this .
or may be i can remove a weekly from retention
Do you have any ideas to help me?

 

[ZenHostingTravis]

Hi @leonep,

Could you confirm whether you are using the built-in cPanel backup functionality?

Also, have you considered incremental backups?

 

[leonep]

yes i use cpanel backup.
i never use incremental beacause it requires rsync and my provider offer me only ftp.
may be it's time to migrate backup destination, i need to find low budget destination.
thanks for this !

 

[cPAdminsMichael]

I would strongly recommend using incremental backup. It will both speed up your backups, but also decrease backup space needed and the load on your server while running the backups.
There are a few rsync remote backup services out there... maybe combine it with JetBackup to get an extra smooth backup experience ;-)

 

[sparek-3]

Nobody ever really wants to talk about the downsides of backups.

It takes space to create backups.

It takes time to create backups.

It takes processing power to create backups.


Now, when you need a backup to recover from, they are a life saver. And I'm not in any way, shape, or form saying backups should never be done. BUT... how often are you recovering from these backups? Where is the tipping point between consuming too many resources creating the backups vs. actually using the backups you have created?

If you have really large backups, then you should probably take a look at where the majority of that disk space is being used.

I'm assuming 216GB is a total for the 5 backups you keep, so on average each backup is 43.2GB. What on your account is taking up the majority of the disk space? And is that changing very often?

For example, if you have 38GB stored in an image folder that stores images from way back when and often never gets files added or removed, then maybe it makes sense to archive one copy of that 38GB and exclude it from future backups.

 

[cPanelLauren]

To add to @sparek-3's suggestion, mail is another common one that causes a lot of backup delay and is usually best handled when stored off the server (i.e., on the user's mail client) backup exclusions may be something you want to look at for these items.

Bottom line is that you have a lot of data you're attempting to backup and without using an incremental solution you're backing up all that data every single time. It's going to take time and it's going to cause load on the server.

 

[leonep]

I have fixed backup with incremental and rsync destination ! it works
i only have annoying alert on pruning over backup destination. the curious is that if i look at destination the backup is correct and the directory is deleted .... why this happen?

Unable to prune transport “raspberry casa rsync”
Error pruning “rsync_gemini/2020-10-09” from “raspberry casa rsync”: ssh slave failed: timed out
The system could not prune the “rsync_gemini/2020-10-09” directory due to an error.

[2020-10-13 01:13:23 +0200] info [backup] Pruning backup directory: /backup/2020-10-08
[2020-10-13 01:18:55 +0200] info [backup] Queuing prune operation for remote destination daily backups
[2020-10-13 01:18:55 +0200] info [backup] no_transport = 0 .. and queueid = TQ:TaskQueue:15247
[2020-10-13 01:18:55 +0200] info [backup] leaving queue_backup_transport_item

any help please?thanks

 

[cPanelLauren]

Hi @leonep

This commonly happens when you're using a non-root user, the thread here goes over this pretty well: Error Pruning - ssh slave failed: timed out

 

[leonep]

once upon a time there was a bad backup that after your great help has now become a beautiful backup that works great !!
thank you very much

 

[cPanelLauren]

I'm so happy to hear it's working!! Thanks!