What exactly does/doesn't need to be backed up with SQL 2000?

[PHead2]

I'm a little confused on what exaclty needs to be backed up to fully backup a server running SQL 2000.

I'm using BackupExec 8.6 build 3878 with all applicable hotfixes installed.

My understanding is that:

I need to back up all of the drives, system state, and check the MS SQL Server box. (This part is pretty clear)

Here's the two things I'm not so clear on:

1) I don't need to select individual file groups unless I want to be able to resotre those seperately (and I can't backup the master, pubs, primary and northwind filegroups). Basically, is it OK to not have a full check in the SQL Server box?

2) I should also deselect all the files in the ...\Microsoft SQL Server\Data folder as these can't be backed up this way and are backed up anyway when I select the SQL Server check box.

I just want to make sure I'm not missing something important be deselecting/not selecting these things.

Thanks.

 

[dogmata]

PHEAD:
------

- you do not need to select the SGL DB's for backing up at the file level unless you want to run a flatfile backup. In order to do this (and its worthwhile running a flatfile backup every once in a while), you will need to stop the sql services otherwise backup exec will skip your DB's and transaction logs.
For an online backup, you can backup at filegroup level but you have to change some options in SQL enterprise manager. As long as you are selecting the SQL DB's under the SQL agent when defining the job you will be able to fully rstore them in the event of a crash.

Cheers

 

[Qdog]

Ok, sounds like you're using the Agent for MS-SQL 2K to backup SQL. Unless you have secondary filegroups created by users or if yours is a very large database which has been split using 2ndary filegroup, you DO NOT need to backup filegroups. The primary filegroups are included in database backups.

The previous poster is correct. If you want to be able to restore filegroups seperately, then back them up. Previous poster is right about the flat-file backup as well.

Just backup all your databases. You should be good to go. If I were you, I would in addition, perform backups from within SQL Enterprise Manager and then backup the SQL dumps with Backup Exec for redundancy/safety.