Jump to content
thirty bees forum

Recommended Posts

Posted

Hi everyone,

I have a question about backups. Our site has a lot of images and while we compress them daily using a cron task and delete any extraneous images again using a cron task, this folder ends up being the most massive folder on our website. We have an automated backup that backups the database every night and the files for the website itself once a week. However, the image folder is becoming so huge that the backup routine times out before it can be finished, resulting in an incomplete archive. And when we managed to get complete, uncorrupted archives, the process of opening it usually fails because it is too huge.

Is there a solution to have the images backup separately, or to breakdown the backup of that folder in smaller chunks so that it can be reconstructed if it ever fails? Because reinstalling tens of thousands of images is not a fun task...

Anyhow, just thought I would ask if anyone had to deal with that sort of challenges. Any suggestions are welcome!

Posted

A partial solution would be to backup only the base files like 123.jpg for the products and to skip all the derived files like 123-home_default.jpg. You can always regenerate them.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...