Comments on: FTP or Amazon S3 Server Backup PHP Script

By: Eric Nagel

Eric Nagel — Thu, 07 Jan 2010 16:24:29 +0000

Nice job, Jordi! Thanks for not only improving on the backup script, but giving it away, too!

@Niro – take a look at what Jordi did, and you should be able to backup your server now

By: Jordi

Jordi — Thu, 07 Jan 2010 15:41:47 +0000

I wrote a new version which fixed my large file problems and the timeout issue. Hopefully this will fix your problem too Niro, or anyone else that stumbles on the same issues

http://www.jor-on.com/blog/2010/01/07/php-amazons3-ftp-server-backup-script

My server is backing up again, I feel much saver now hahaha

By: Jordi

Jordi — Tue, 05 Jan 2010 19:32:13 +0000

Thanks for the quick response. For me unfortunately it didn’t work though. I tried to turn of SSL but that didn’t do the trick. It’s probably the 2GB file limit then because the tar.gz file is just a little over 2GB.

For me it’s not the database dump that’s causing problems. That’s actually uploading correctly. The problem lies with the complete file dump, probably have to many images

I’ll have to try something else then. Maybe I’ll have to split it into different files. Too bad automated backups with an option to upload to S3 isn’t baked into Plesk.

Thanks again!

By: Eric Nagel

Eric Nagel — Tue, 05 Jan 2010 15:58:03 +0000

Hi Niro, Jordi – I’m not sure why it’s getting stuck. According to the author of the S3 component

Known Issues:
Files larger than 2GB are not supported on 32 bit systems due to PHP’s signed integer problem
SSL is enabled by default and can cause problems with large files. If you don’t need SSL, disable it with S3::$useSSL = false;

For the database, you can change the dump to dump tables, not the whole database at once, and maybe then you’d be under 2GB. Or, take the .sql file that’s the export from the database and split it up.

By: Jordi

Jordi — Tue, 05 Jan 2010 15:48:51 +0000

I have the same problem as Niro. Is there some sort of file limit? The file that it’s uploading is around 2GB.

By: Niro

Niro — Sun, 22 Nov 2009 07:25:02 +0000

Eric, thanks for the excellent script.
For some reason it gets stuck when trying to send to amazon a database file which is 400M after the compression. Top command shows cpu is at 100% on httpd process. smaller files did work.

I tried removing the https in the s3 initialization but it did not help.

Anyone know how to solve this?

By: Eric Nagel

Eric Nagel — Fri, 23 Oct 2009 19:51:22 +0000

@RPM – everything above “Done editing script” should be looked over and probably changed, including $workingDir

By: RPM

RPM — Fri, 23 Oct 2009 19:32:09 +0000

Great Script!

I have a question if you don’t mind; if i would like to run this script in the daily cron folder should i change $workingDir ?

cheers!

By: Z

Wed, 29 Jul 2009 05:45:04 +0000

Just wanted to stop by and say thank you very much for sharing this script. It’s very well commented, and worked perfectly. I set it up as a daily cron job. I now have piece of mind. Thanks a lot!

By: Eric

Eric — Sun, 28 Jun 2009 18:08:12 +0000

@Dash: the very first variable in the script is $nDays, which is "How many days of backups to keep?" It's set to 5, but you can change that to whatever you'd like. After backing up, the script takes care of clean up.