s3://weekly-backup/$thisbackkup

should be:

s3://weekly-backup/$thisbackup

root@pbx:~/s3fs $ s3fs dutrataz-weekly-backup /mnt/s3fsfuse: device not found, try ‘modprobe fuse’ first

To resolve you need to include the following two lines at installation

echo modprobe fuse > /etc/sysconfig/modules/fuse.modules
chmod +x /etc/sysconfig/modules/fuse.modules

Thereafter the problem is solved and you can run

s3fs without issue.

Can you update the installer to have the fuse.modules file created and ready?

[WM: Thanks, Malcolm. We’ve added the patch.]

Has some of the fuse stuff been taken care of already on the latest builds of PIAF? I didn’t have to install twice like you mention in the article.

[WM: S3 support already is included in the Incredible PBX.]

(1) yum install fuse-devel
(2) echo modprobe fuse > /etc/sysconfig/modules/fuse.modules
(3) wget http://s3fs.googlecode.com/files/s3fs-r191-source.tar.gz
(4) tar xzvf s3fs-r191-source.tar.gz
(5) cd s3fs
(6) make
(7) cp s3fs /usr/bin
(8) entered my credentials in /etc/passwd-s3fs in the format AccessKey:SecretKey
(9) mkdir /mnt/s3fs (in case its not there already)
(10) echo /usr/bin/s3fs mybucket /mnt/s3fs >> /etc/rc.d/rc.local
(11) then to get it running without a reboot I ran "modprobe fuse" and then "/usr/bin/s3fs mybucket /mnt/s3fs"

I then changed to that directory, and did a listing. All was well. Going to be testing a migration to a completely different box later today. Thanks, this stuff ROCKS!

I can mount the s3 drive, I can see I have 256T available. I have a bucket available.

When i run the command I get the following:

[root@localhost /]# rsync -avz –delete /home/mysqldumps /mnt/s3
building file list … done
mysqldumps/
rsync: recv_generator: failed to stat “/mnt/s3/mysqldumps/backup.txt”: Not a directory (20)

sent 85 bytes received 26 bytes 74.00 bytes/sec
total size is 124 speedup is 1.12
rsync error: some files could not be transferred (code 23) at main.c(892) [sender=2.6.8]

Any help would be appreciated.

[WM: I think you need to first create the mysqldumps subdirectory on /mnt/s3 manually.]

How does one fix the fact that WordPress is cutting off your articles?

[WM: The short term answer is look at the page source for anything you need. It’s complete there. This is merely a CSS display problem. The longer term answer is I’m afraid this one is going to have to wade through the articles again and move some text to other lines. Bear with us. We’ll get it done. If there are particular ones you need, just let us know, and we’ll do those first. Thanks.]

If it’s still not working (try "modprobe fuse", if it gives an error then we have something wrong), compare the output of the following two commands:
"rpm -qa | grep kernel-devel"
"uname -r"

if they aren’t the same, then you have to update your kernel ("yum upgrade") and restart.

Small note, after doing an upgrade, freePBX will likely be broken (PEAR dependencies, so run "pear upgrade-all" to fix that little error)

As of the writing, the Kernel should show as: "2.6.18-92.1.17.el5″

[WM: We like nuggets. Thanks, Philippe. I’m no Perl whiz, but it looks like a one-line change in the backup script could have the FreePBX backups rerouted to Amazon S3 so long as your bucket already was mounted. Remember that an S3 bucket once mounted appears as just another directory on your server! Step 1 is to mount your S3 bucket whenever your server boots. Then make a new directory called backups, e.g. mkdir /mnt/s3fs/backups. Now the pertinent script to adjust is ampbackup.pl in the modules/backup/bin directory under the FreePBX modules. And the line that needs changing to point to your mounted S3 bucket is line 104 which begins with $backupdir =. Comment out the line with a leading # symbol, and then add a new line below it that looks like this:

$backupdir = "/mnt/s3fs/backups";

Once you’ve saved your change, remember to add a line at the end of /etc/rc.d/rc.local to automatically mount your S3 bucket when your system boots:

s3fs weekly-backup /mnt/s3fs