Support

Please look at the bottom of this page (under Support Policy Summary) for our support policy summary, containing important information regarding our working hours and our support policy. Thank you!

EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.

Description of my issue:

I am trying to backup a large site. 19GB of files, mostly images. It is hosted on NameCheap with an "unlimted" space and use account. But, of course, it is limited. The backup fails after producing 3 archives of 2GB each and then a partial of about 250MB. I assume a full backup will be 8 or more of these 2GB archives. My question is can I download the archives that did get produced using ftp. Then delete the from Akeeba backup folder. Next rerun the backup and deleting the archives as they are produced a second time to make more space for the remaining backup archives? So if I delete parts .jo1, jo2, and .jo3 after downloading them, then rerun the backup, delete these same parts as they are recreated in order to make space for the new parts will I be able to use them to restore the website?

If you have any other suggestions I'd be happy to hear them as well. I have successfully run this backup in the past but the host must have made some changes.

Thank you.

Duane Mitchell

That sounds great. I do have it going to S3 as post processing but did not know about processing each part. I set that up as you described. I don't see where to set the part size? Maybe that is different in this older version of Akeeba Backup? This host is also running a obsolete version of PHP.

I found where to set the part size. Ignore that question.

I'm trying it with the 2GB part size because I find that transferring from one host to another is very fast. Maybe not so much on NameCheap but we'll see.

Thanks!

This worked out well. I made the part size 500MB. That meant Akeeba could upload the part to S3 and then delete it on the localhost while the backup process is ongoing and consuming disk space against the quota. I did not hit my disk quota limit and have the process shut down.

There were 35 parts of about 500MB each. For some reason it failed to upload two during the backup. The error referred to Amazon S3 as where the problem lied. So I downloaded them using ftp because I didn't know what would happen or if the upload process would continue or not. It did. It continued to upload the parts after those two errors. Also, after the backup was completed it went back to those two parts and successfully uploaded them. Then it cleaned up and ended the process. About 12 hours in all. Very impressive.

Thanks for your help.

Yes it did. Just had to make sure that the archive parts got uploaded to S3 and deleted faster than new archive parts used up more disk space. That's where setting the correct part size comes in. I used 500MB part sizes. That worked.

Let's close this ticket. Thanks!