SQL Server Backups on Go Daddy Shared Hosting
Summary
The backup tool is a relatively recent addition to the Go Daddy control panel (July 2007) so you may not be familiar with it. This article provides a step-by-step walkthrough with screenshots to show you how to back up your SQL Server database.
The Backup Process
The backup process involves SQL Server saving a copy of the database to file. This file is in a proprietary format that only SQL Server can read and restore either to a copy of the original or back into the original database.
Go Daddy stores the file in a directory called _db_backups. This directory is on your web server, and is accessible via their FTP client (or your own FTP tool).
Preparing for Backup
The backup process itself does not take your database offline - your users will still be able to log in and access data. However, it does add a load to the SQL Server engine itself and will impact on the database performance.
It's a good idea to try to ensure that there are no heavy data operations going on while you're performing the backup. If you have processes which upload or update large volumes of data, then these would slow the backup process itself, while the backup would slow the data operations.
Using the Go Daddy Backup Tool
The backup tool is a relatively recent addition to the Go Daddy control panel (July 2007) so you may not be familiar with it.
Log into your Go Daddy account and open the SQL Server section.
Figure 1. Open SQL Server

The Backup tool is available from the Database Information screen. Use the pencil icon within the SQL Server section to open the Database Information screen.
Figure 2. Open the Database Information Screen

At the top of the information screen is a row of icons. The first icon is the Backup tool. Click the Backup icon.
Figure 3. The Backup Tool
An information window informs you that the backup process may take up to 2 hours. In our experience, databases are backed up within ten minutes of making the request.
All backups you take are saved to the same named file: <database name>.bak. The files are kept in a directory called _db_backups on your web server.
If you or someone else have previously backed up your database but have not changed the name of the existing file in the directory, you will be prompted as to whether you want to proceed. If you proceed now, the backup process will overwrite the existing file.
If you prefer to keep a history of backup files then cancel this backup operation, rename the existing file in directory _db_backups using the FTP Client tool, and start the backup again.
The Database Information page will change the database status to "Pending Backup".
Figure 3. Pending Backup

It would be nice if the web page would sound a trumpet call when the backup is complete. Unfortunately, you will have to keep refreshing the page until you see the status change to "Setup".
Figure 4. Backup Completed

Finding the Backup
Once the backup is complete, the backup file will remain in the directory on the web server. If you want to get a copy of it onto your local machine, then you'll find it in a directory called _db_backup within the main directory of your web project.
You can use the Go Daddy FTP client or your preferred FTP tool to copy the file down to your local machine.
Summary
This article provided a step-by-step walkthrough with screenshots to show you how to back up your SQL Server database.
Submitted: 10 August 2007
Author: Margaret Cruise O'Brien
(c) M.C.O.B. Technology 2007