Discussion Locked

APP SERVER BACKUPS

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Which is the best way to go to back up a application server running SQL?

a. Tapes drive
b. No backup - just RAID 3 or 5 with hot swappable drives.
c. Backup external hard drive
d. Over the wire backups

I need to figure this out for a remote application server on a network. It is unattended and I need to to be able have it run with as little administration as possible.

Any good ideas?

4 replies

by jdmercha

a. Tapes provide good backup. But how unattended do you need. You can backup to a single tape and overwrite that tape every night. You could get an auto loader and pverwrite the same tapes every week. But the you won't be covered in case of fire, or if you need to restore data over one week old.

b. No backup (RAID) that's not much of a backup at all.

c. An external hard dirve is probably more economical than tapes. But it still gives you the problem of overwriting the same files each noght.

d. Over the wire backup is only good if you have a liited amount of data, and don't mind others getting a copy of it.

More importantly be aware that you cannot backup and SQL database without shutting it down. Most backup software will have a seperate SQL module you'll have to buy to do the job.

by xentity

The box is a hardened cabinet remotely placed on a client network with its own UPS and backup. Data is gathered and stored in the SQL/2003 Server.

My thinking is to use an external USB drive for a local backup and some sort of over the wire backup for disaster recovery.

Overall there will be between 7 to 15 of these geographically remote servers. I'll need to be time and cost efficient as possible without risking information recovery.

I am not a fan of tape backups and have never had the kind of success I need.

by jdmercha

Sounds like you might need to do a risk analysis.

What are you trying to accomplish with this backup. You said that the systems have their "...own UPS and backup". Why do you need another backup?

Certainly an external USB drive is the cheapest way to go. But that doesn't protect you much more than a mirrored drive. That also doesn't provide protection against corrupted data. Once the corrupted data has been backed up you've overwritten your only copy of good data.

But what I would consider is taking an image of the system when it is built. Then you can always restore the system to its starting point. You will then only have to back up the database on a regualr basis. You would also have to create a new image of the machine any time the software was upgraded.

But you still have the problem of backing up an active SQL database. You'll need expensive ($1,000) software to control this, or you can do it manually if you don't need the system 24x7.

If you want to be able to back up all the systems to a central location, then you might want to consider a replication server at each site. Then you can backup the replication server over the wire, and not have to take down the active servers.

Of course if you have large databases then backing up over the wire won't be fast enough to keep up. Not to mentino that backing up over the wire is much less reliable than backing up locally to tape.

by jim.azar

A good online backup service is extremely reliable. I backup SQL servers using Rhinoback, http://www.rhinoback.com. It invokes the native SQL Server backup utility, and then compresses and encrypts the data and transmits it to a secure offsite datacenter. After the backup data is transmitted, CRC's are computed on both the client and server to ensure data integrity. I am sure there are other offsite backup services that can do the same thing. I use Rhinoback because it has specific support for MS SQL Server 2000 and MS SQL Server 2003, MySQL and Oracle. Unless your database is absolute huge and you have very limited bandwidth, there is little reason not to backup SQL Server with an online backup utility. The cost is really not a factor.

This discussion is closed to new replies.