Creating Magento code archive

Last modified by sashka_ua on Sun, June 17, 2012 09:04
Source|Old Revisions  

This guide describes how to create full Magento backup as well as partial archive for providing to Magento support. The goals of the guide is help Magento customers to:

1. prepare appropriate code archive for debugging or backup

2. avoid archiving unnecessary data

3. avoid system performance impact

1. Checking and preparing system for archiving

a) You need to check if the system has enough free space to store newly created archive.

tar -cjf ./8220a33ae747b30e4bd135335edea410.201204241703.tbz2 ./app ./downloader ./errors ./includes ./js ./lib ./pkginfo ./shell ./skin ./.htaccess ./cron.php ./ ./get.php ./index.php ./install.php ./mage ./*.patch

Sample: how output of “df -h” may looks like

sash@host01:~$ df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             400M  209M  192M  53% /
tmpfs                1013M     0 1013M   0% /lib/init/rw
udev                 1008M  156K 1008M   1% /dev
tmpfs                1013M     0 1013M   0% /dev/shm
/dev/sda5             228M   27M  190M  13% /boot
/dev/sda6             9.8G   33M  9.8G   1% /home
/dev/sda7             2.0G   53M  2.0G   3% /tmp
/dev/sda8              20G  867M   19G   5% /usr
/dev/sda9              20G  8.5G   12G  44% /var

2. Creating archive

Creating Magento partial code archive for debugging

Creating Magento full code archive for backup

Creating Magento full DB dump for backup

Creating Magento partial DB dump for debugging