Windows 2000 BackUp Fundamentals 1

[SteadySystems]

I'd like to get a better understanding for using Windows 2000 Server Backup utility.

Currently I have two Windows 2000 Servers in a workgroup environment. Server #1 is a RAID 5 configuration and used to run the primary database application and ftp service.

Server #2 is newly implemented and I would like to backup all data on Server #1 using Server #2's Backup utility.

The data on Server #1 that I plan to backup will be the database (about 2gb and growing), the system state, system files and user data on C and D Drives. Server #2 has a SONy 4GB Dat tape configuration.

I tested the backup utility on Server #2, was able to browse to Server #1 and select which files, folders I want to backup. Successfuly backed up the database.

Yet I still want to understand: Fundamentaly what is the best practice and safety procedures to understand and implement backup plans?

 

[mattjurado]

If your users are inputing a lot of data, and you have plenty of tapes, I'd do a full backup every day, and swap the tape daily. Make sure the job overwrites and retensions the tape every day, it will extend the life of the tapes. I'd only backup your system state but maybe once a week, and I would have that run as a separate job, AFTER the data backup is completed. This way, if the system state backup fails (which is common with NT/2000), at least your data backup will be complete. Cycle one tape a week out to an offsite safe storage location.

Make sure your users log off all applications properly, or you could have issues copying open files (unless you want to purchase an open file manager).

Also, I wouldn't rely to heavily on ntbackup, its really limited in what it can do. I'd suggest the Veritas Backup or Arcserver Brightstor server packages. The ntbackup isn't a real professional solution.

One last thing, you don't have a backup, unless you can restore from it. After you have your jobs scheduled and running the way you want (like the morning after your first backup), do a full restore to a different location (so you don't overwrite anything), and make sure the data is usable. I'd do this at least once a month, to make sure your backups are not only readable, but usable.

Matt