What kind of files have to be backed up on 2003 servers in order to reconstruct the server in the even of hardware failure.

I have a primary DC, secondary DCs, few Terminal servers, few  other servers running general applications. I want to start backing up important files/system state  from the servers so that in case of hardware failure, i should be able to restore the same functionality on new server. All the machines are win 2003 servers. Any information on how to back up mssql and mysql will be appreciated. I am planning on developing a back up plan for the servers. so any important information on backing up server is welcome.
kiranjanaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David ToddSenior DBACommented:
Hi,

MS SQL has its own backup.

The catch is, you can't just copy the live data-files to tape. They won't recover.

The simplest approach with smallish databases is to use the SQL backup command to back up the databases to disk, and then use whatever backup system to copy those backup files to tape.

HTH
  David
0
TAB8Commented:
You also need to backup the system state data (registry) if you want to just restore the whole server rather than restore just a databse
0
kiranjanaAuthor Commented:
Thank you for the suggestions. Can you help me finding step by step instructions on how to backup the system state data. Todd, would appreciate any information on sql backup command. thank you once again.
kj
0
kiranjanaAuthor Commented:
Also, how often will i have to make a backup of that system state data.
Thank you
kj
0
David ToddSenior DBACommented:
Hi,

My guess is that the system state should be backed up at least weekly. It wont change that much. But since it is relatviely small, then it should be backed up with most backups.

SQL Backup looks something like this:
-- ===========================
-- Backup Database Template
-- ===========================
BACKUP DATABASE <Database_Name, sysname, Database_Name>
      TO  DISK = N'<Backup_Path,,C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\><Database_Name, sysname, Database_Name>.bak'
WITH
      NOFORMAT,
      NOINIT,  
      NAME = N'<Database_Name, sysname, Database_Name>-Full Database Backup',
      SKIP,
      STATS = 10;
GO

This was taken from the SSMS 2005 templates. The <> (angle brackets) denote things that need to be changed for the SQL to execute. It would look something like this

-- ===========================
-- Backup Database Template
-- ===========================
BACKUP DATABASE YourDatabaseName
      TO  DISK = N'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\YourDatabaseName.bak'
WITH
      NOFORMAT,
      NOINIT,  
      NAME = N'YourDatabaseName-Full Database Backup',
      SKIP,
      STATS = 10;
GO

HTH
  David
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.