0

How is everybody backing up after SUPEE-10975? (backup module has been disabled).

Here is what I temporarily figured out:

1) Dump the database into ZIP (not the best since cron commands can be looked up by other users on the system by ps command from what I hear)

/usr/bin/mysqldump -u user -pPASSWORD DATABASE | /usr/bin/zip > /home/user/public_html/var/backups/db_$(date +\%d-\%m-\%Y).zip

2) GPG encrypt with AES256. Password located in pass file with 400 permissions.

cat /home/user/.gnupg/pass | /usr/bin/gpg -c --batch --passphrase-fd 0 --cipher-algo AES256  /home/user/public_html/var/backups/db_$(date +\%d-\%m-\%Y).sql.zip

3) Remove zip file

rm -f /home/user/public_html/var/backups/db_$(date +\%d-\%m-\%Y).sql.zip

Then I download RSYNC and remove backups off the server.

UPDATE: this is probably not the best strategy for large databases.

PS: for me its confusing to force users to use a different strategy to back up without replacing it. If your server is owned, don't you think the same people who have access to your file system can just look into your local.xml and find your DB password?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.