Media Temple (gs) Grid Service Domain & MySQL Backups
Posted: October 25, 2009 | By: TJ | In Technology | 4 comments
Having been on many shared hosting platforms before, I am fortunate enough to have a few (gs) Grid Services with (mt) Media Temple. Although no native backup tool currently exists for the (gs), I’ve created some simple backup scripts to backup the domain directories and MySQL databases. Both are very simple bash scripts that can be set up as cron jobs from with the AccountCenter. The first backup we’ll create is for domain backups:
1. If you haven’t done so already, enable SSH from the (mt) Media Temple AccountCenter.
2. Once you’ve logged in via SSH, navigate to the /data directory. Keep in mind you’ll need to add your site number in the ##### for this to work. You can find your site number in the Server Guide > Access Domain section of the AccountCenter.
cd /home/#####/data
3. Run the following commands to create and set permissions of the backup directory:
$ mkdir backup $ chmod 777 backup
4. Create a file called backup.sh and make it executable:
$ touch backup.sh $ chmod +x backup.sh
5. Open the file in a text editor or vim and paste in the following:
#!/bin/bash
today=$(date '+%d_%m_%y')
echo "* Performing domain backup..."
tar czf /home/#####/data/backup/example.com_"$today".tar.gz -C / home/#####/domains/example.com
# Remove backups older than 7 days:
MaxFileAge=7
find /home/#####/data/backup/ -name '*.gz' -type f -mtime +$MaxFileAge -exec rm -f {} \;
echo "* Backed up..."
This really simple script creates a tar.gz backup of the example.com directory, stamps it with the current date and places it in the the backup folder we just created. It will also prune any backup older than 7 days old. Before saving the file, be sure to make the necessary adjustments for your site number after the /home directory. You’ll also need to modify example.com for the actual domain you’ll be backing up. Before adding it as a cron, run the script via SSH — the output should look like this:
example.com@n10:/home/#####/data$ ./backup.sh * Performing domain backup... * Backed up...
Depending on the size, the backup may hesitate after the initialization while the domain directory is being compressed. You can now verify that the new backup is in the /home/#####/data/backup/ directory with the today’s date: example.com_25_10_09.tar.gz. Once you’ve confirmed the backup works, add the backup.sh file as a cron within the AccountCenter following this KnowledgeBase article. You can schedule the cron as frequent as you would like however the General Settings should look like this:
Click to enlarge
Now, you’ve probably got at least 1 MySQL database that should be backed up as well. This can be accomplished just as easily.
1. SSH back into the /data directory and create a new bash script file:
$ touch db-backup.sh $ chmod +x db-backup.sh
2. Now, open the file in a text editor or vim and paste in the following:
#!/bin/sh
#############################
SQLHOST="internal-db.s#####.gridserver.com"
SQLDB="db#####_dbname"
SQLUSER="db#####"
SQLPASS="db_user_password"
SQLFILE="db#####_example.com_$(date '+%d_%m_%y').sql"
LOCALBACKUPDIR="/home/#####/data/backup"
#############################
echo "* Performing SQL dump..."
cd $LOCALBACKUPDIR
mysqldump -h $SQLHOST --add-drop-table --user="$SQLUSER" --password="$SQLPASS" $SQLDB > $SQLFILE
# Remove backups older than 7 days:
MaxFileAge=7
find /home/#####/data/backup/ -name '*.sql' -type f -mtime +$MaxFileAge -exec rm -f {} \;
echo "* Backed up..."
exit
This bash script uses mysqldump to dump a MySQL database which stamps it with the current date and places it in the the backup folder we created before. This will also prune any database backups that are older than 7 days. Before saving the file, be sure to make the necessary adjustments for your site number and database credentials — all of this can be found under the Manage Databases section of the AccountCenter. Before adding it as a cron, run the script via SSH — the output should look like this:
example.com@n10:/home/#####/data$ ./db-backup.sh * Performing SQL dump... * Backed up...
Once you’ve confirmed the script completes without errors, add it as a cron job so you’ll never have to worry about losing your MySQL data again!
