SQL/ MS 2003 server backups/restores

From: Mrpush (Mrpush_at_discussions.microsoft.com)
Date: 12/16/04 

Date: Thu, 16 Dec 2004 10:21:04 -0800

Hello,

I'm a bit confused on the backup necessary for my SQL server running on MS
2003 server. My setup is like this: MS 2003 server setup as domain
controller, file server, DHCP and DNS and SLQ server installed, all on one
box. (Am I in trouble for this????)

I know I can backup the operating system with BACKUP and do an ARS
(automated system recovery) with tape drive and startup disk. I'm aware that
this will backup my full system, ACTIVE DIRECTORY (and maybe DHCP and other
important role databases???) as long as I include "system state".

However, does this one backup also backup my SQL databases normally so a
restore would be normal for the entire server including SQL data?

If not, I'll assume I have to do 2 backups for this server, one for the
system state, OS etc, and another for my SQL databases. Is this correct?

Are there any other BACKUPS I'll have to do as well? Just seems like a lot
of backing up for a single server.

The way I see it, there are 3 general cases:

1.) Corruption of OS files or SQL databases which does not reguire new
hardware OR

2.) Server hardware dies (say 2 disks in my RAID 5) which does not reguire
new hardware (server) OR

3.)Server hardware dies (say mother board) and I need to get a new server
and I'm forced to "rebuild" all the software from scratch.

In the first 2 cases, I could restore from tape and disk created via an ARS.
 But will this restore my SQL server install and databases as well?

In the last case, I'm forced to manually re-build the server due to all new
hardware.

I'm concerned in that I NEVER read of anyone using ARS, so should I assume
that its best to just "RE-BUILD" the server from scratch and then restore
the necessary databases (active directory etc) and SQL from separate backups?
 

I'd really like a "catch all" backup, maybe on one tape, to make managment
easy. Is this possible or am I dreaming?

Note that my SQL user databases will probably use a FULL weekly, with DIFF
nightly and Trans logs every 2-4 hours daily. Is it a MUST that I backup SQL
data on separate media or separetly (within SQL) from an OS or ARS backup?

Thanks much,

MP

Relevant Pages

  • Re: SBS2003, NTBackup-Fehler
    ... Windows Server 2003 to resolve some VSS snapshot issues ... Backup fails on a computer that is running Small Business Server 2003 ... Die Sicherung kann nicht fortgesetzt werden. ... Microsoft OLE DB Provider for SQL Server ...
    (microsoft.public.de.german.backoffice.smallbiz)
  • RE: Backups have Shadow Copy Problems
    ... and restarted the server. ... suggested and changed the recovery model to simple on the one database called ... I understand the issue to be: the backup task failed ... You back up data from a volume that contains a Microsoft SQL Server ...
    (microsoft.public.windows.server.sbs)
  • Re: Scheduled Backup for SQL Database
    ... Look in the SQL Server log too, ... Need smaller SQL2K backup files? ... >>Need smaller SQL2K backup files? ...
    (microsoft.public.sqlserver.server)
  • Re: VSS event 6013
    ... I am experiencing a similar issue where VSS tries to access my SQL ... Server every time I perform a system state backup. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS2003 Exchange Backup Problems (& musings)
    ... We're ordering a new server. ... "Frank McCallister SBS MVP" wrote: ... On the Bad backup VSS ... >>> most obvious is to be sure that any SQL databases you have are in Simple ...
    (microsoft.public.windows.server.sbs)