Database Reference
In-Depth Information
Saving the export file on the server
Instead of transmitting the export file over the network with HTTP, it is possible to
save it directly on the file system of the web server. This could be quicker and less
sensitive to execution time limits because the entire transfer from the server to the
client browser is bypassed. Eventually, a file transfer protocol such as FTP or SFTP
can be used to retrieve the file, as leaving it on the same machine would not provide
good backup protection.
A special directory has to be created on the web server before saving an export file
on it. Usually, this is a subdirectory of the main
phpMyAdmin
directory. We will use
save_dir
as an example. This directory must have special permissions. First, the
web server must have write permissions for this directory. Also, if the web server's
PHP component is running in safe mode, the owner of the phpMyAdmin scripts
must be the same as that of
save_dir
.
On a Linux system, assuming that the web server is running as group apache, and
the scripts are owned by a user "marc", the following commands would do the trick:
# mkdir save_dir
# chown marc.apache save_dir
# chmod g=rwx save_dir
The proper ownership and permissions mask depend highly on the
chosen web server and the
SAPI
(
Server Application Programming
Interface
)
(see
http://en.wikipedia.org/wiki/Server_
Application_Programming_Interface
) used, which influences how
directories and files are created and accessed. PHP could be using the
scripts' owner as the accessing user, or the web server's user/group itself.
We also have to define the
'./save_dir'
directory name in
$cfg['SaveDir']
.
We are using a path relative to the
phpMyAdmin
directory here, but an absolute
path would work just as well.
The
Save as file
section will appear with a new
Save on server...
section:
Search WWH ::
Custom Search