Support

Akeeba Backup for Joomla!

#9044 Backup to filesystem outside of the Joomla installation

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
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by nicholas on Thursday, 15 September 2011 16:01 CDT

user46264
I am using Joomla 1.7 and the latest version of Akeebabackup. All is running on a CentOS 5.6 Server maintained by myself.

I try to define a backup location outside of the Joomla instance. It is a mounted NFS directory that points to another storage on the same network.

This seems not to work. The output path is always set back to .../administrator/components/com_akeeba/backup. I have changed the owner to root:apache on the specified directory and gave write permission to group (chmod -R g+w ). When I define that directory there is a note saying that this directory is outside of the Joomla directory and its content my not be read...

Any idea what I am missing or is it not possible to place backups on a different filesystem?

Thanks for your help.

nicholas
Akeeba Staff
Manager
You have to make sure of two things:

1. If you have open_basedir restrictions in your php.ini file you must put the NFS root path in there, otherwise PHP will be unable to access this directory.

2. Mind your ownership. NFS shares use the ownership (user, group) numerical IDs of the remote system. In order to make the directory writable, you may have to give the target directory in your NFS share 0777 permissions.

3. If you are using PHP in CGI/FastCGI mode running in a chroot jail, please note that the effective filesystem root is your site's root directory. This means that any directory outside your site's root is inaccessible, as it is outside the chroot jail PHP is confined in. Using a symlink to the NFS share also won't work, as the symlink points to a non-existent path when you are inside the chroot jail. Under these circumstances, the only way to deal with the issue is to remove the chroot jail and use a different security method, e.g. suPHP and/or open_basedir restrictions.

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!

user46264
Hi Nicholas,
Thanks for your help and sorry for the late answer, I could not look at this earlier.

The second hint solved the problem. I re-created the directories on the remote system and they got other numerical IDs and 777 but are limited to certain IP-Adresses. It is working now.

Thanks again!

Thoma

nicholas
Akeeba Staff
Manager
You're welcome! I am glad it's working now :)

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!

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!