Thanks Joe,

Looking forward to using S3.

I do nightly scheduled ssh backups to another virtualmin server I use for experiments which resides on a 156/34 DSL connection.

Recently I started backing up using my home cable 800/80 connection using cygwin to receive the backups. Anyway... both backups are on residential grade internet connections.

Since my house cable connection is 800/80 I can backup from the VPS virtualmin server to cygwin quickly so that's nice.

A backup or restore from the amazon S3 backup would happen at around 800 per second either direction.

A restore from my house would be pushed out at 80 so to restore 3, 4, or 5 gigs of server would take a while.

To restore from the DSL connection at a 156 down / 34 up from my experimental virtualmin server would be nerve wracking. ;-(

Although I haven't had to restore 8-) yet... I know the day will come so I am hoping I can do it from amazon S3


HUMBLE REQUEST

Out of curiosity... After the :-D "all kinds of stupid" S3 issues are worked out in the virtual server backups would it be hard to offer S3 backups under webmin/system/filesystem backup area?

Also, would it possible to build in a field to list directories and files you would like to exclude from a backup or scheduled backup?

A pleasant surprise. Performance is unbelievable.

Thanks so much for the S3 feature that is now complete and working perfectly.

I yum updated the day before your major update notification on the home page and I noticed the S3 had been completed.

I've run several tests and all have worked.


Here is a rundown for anyone interested.


I have 2 servers. A VPS-link-5 server at www.vpslink.com

and a test server to play with and to use for backups. Both are running Centos and Virtualmin-Pro

I did a backup of all 14 of my v-servers on my VPS to S3 and then a restore from S3 to my physical test server.

Once Virtualmin Pro packaged them up it transfered them to S3 at the rate of:
5,250.0 KB/s... OMG

I wanted to use the nightly scheduled backup method using a date and number so I used the following bucket filename:

test_%m_%d_%Y_%u

I entered my S3 key and access key

checked:
Do strftime-style time substitutions on file or directory name

Checked:
One file per server, in new format

checked:
Create destination directory?

checked:
Halt the backup immediately Action on error


It placed all virtual servers in a bucket named:
test_04_19_2007_4

Thanks once again to Jamie and Joe for this fabulous feature.

Hey John,

Thanks for the informative update! I knew I'd get that bastard figured out eventually...it was a missing dependency, but one that only showed up inside of the error message returned from Amazon...so nobody ever saw the details. Again, just a stupid bit of me not realizing which packages were actually needed.

I've been wanting to use S3 ever since I started using Virtualmin. I just tried the above on my Ubuntu system and all I keep getting is Backup failed : Missing or invalid S3 secret key. I even regenerated my key (which was an ok thing to do for me cause I have NEVER been able to use it for anything yet.) :(

It really taxes my little DSL circuit every Sunday morning when I get a gigabyte download to my home just to keep backups current on my Virtualmin box. ANy help with this would be very much appreciated.

Tom Beattie & Bryan Smith

UPDATE: I feel pretty stupid now but for some of those that are having problems with this, you should copy and paste your ID and secret to notepad or something and make sure that you don't have a space on the tail of either one. That has been the case with me ever since the perl module got fixed on this. (Thanks guys!) As of this writing at least, it's happy enough with it that it's now making the archives to upload to S3.

Hi,

I did a test restore months ago to make sure restoreing from amazon worked and it worked and it did work great.

For some reason I just got this error when trying to restore a server.

Error - Perl execution failed
File does not exist: at S3/ListBucketResponse.pm line 26


Can anyone point me in the right direction?

Thanks ahead,
Wolga