Support

Akeeba Backup for Joomla!

#41531 Relocating Output to S3

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
5.x
PHP version
n/a
Akeeba Backup version
n/a

Latest post by tampe125 on Monday, 27 January 2025 05:56 CST

adhillon

We wish to automate our Akeeba backups and store them on S3. So, we opened a S3 account to store backups on S3 cloud.

We are trying to implement this by using your plugin for Amazon S3.

We have been successful at adding the S3 bucket. It now shows in the Content->Media menu, but we don't know where to go from there. 

 

  1. Akeeba configuration for 'output' requires a path. What could we enter there?
  2. How can we relocate Media Manager location to the visible bucket?
  3. Alternatively, how can we define Akeeba to save backups to a specific S3 container?

 

nicholas
Akeeba Staff
Manager

I think it's best if you first watched the video tutorial here: https://www.akeeba.com/videos/1212-akeeba-backup/1628-abtp07-remote-backup-amazon-s3.html It takes you through the process step by step.

Please remember that Joomla's Media Manager and Akeeba Backup have nothing to do with each other. In fact, Media Manager is only designed to handle publicly accessible static content such as images, videos, sound files, PDFs, etc. You do NOT want your backups to be publicly accessible! You want them to be private. Moreover, backups are not relatively small media files; they are very big archives. That's why we need a completely different kind of integration in our software, and cannot use Joomla's media manager filesystem drivers.

Also remember that the backup archive is created on your site, then it is uploaded to the remote storage (e.g. Amazon S3). Remote storage providers like Amazon S3 offer cheap, slow, high latency storage. When creating a backup archive you need to be able to write small chunks of data, and read from the archive. The average latency for doing that with S3 is about 1 second. The average latency doing that on a local SSD, on properly configured server with enough memory to have relatively big in-memory filesystem buffering and a fairly fast SSD or SAN is about 10 microseconds or 0.00001 seconds. On a blank Joomla site we are talking about approximately 10,000 of these operations. The difference between 10,000 seconds of accumulated latency and 0.01 seconds of accumulated latency over the course of a backup is the difference between a backup that takes 3 and half hours, and a backup that takes 30 seconds. Uploading the backup of that same, nearly-blank site to S3 after it's done only requires 3 of those write operations and adds just 20 seconds to the backup time.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

tampe125
Akeeba Staff

Hello,

please take a look at this video, it will give you all the info you need to start backing up your site in the cloud: https://www.akeeba.com/videos/1212-akeeba-backup/1628-abtp07-remote-backup-amazon-s3.html 

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!