Backup strategy for Windows Server 2003 with 40 clients

90 pts.
Active Directory
Microsoft Exchange 2007
Microsoft Windows Server 2003
wI havea small company running with win2003 server and 40 clients.
I installed DNS,DHCP, AD and exchange 2007 in a single win2003 R2 and running successfully.
if any risk happen to my server. I have no proper backup stratagy to restore my server.
presently following taking backup regularly
  1. system state-daily
  2. exchange data base-daily
  3. DNS folder-daily
  4. DHCP folder-daily
  5. SysVol-daily
  6. NTDS-daily
the above are enough to restore my server or any other good sugestable.
please suggest me

Software/Hardware used:
WIN2003 server

Answer Wiki

Thanks. We'll let you know when a new response is added.

I think the process u have taken is okay ! If possible consider Network Accessible Drives (NAS). They are cheap and reliable. Then u may use ROBOCOPY (a small tool, absolutely free) from Microsoft in conjunction with Microsoft Scheduler to backup files to the NAS drives. I hope u have to use ntbackup…. Another way is Volume Shadow Copy Technology.
This is a new technology in Windows server 2003 that did not exist in Windows server 2000 It is used to create a copy of original volume at the time a backup is initiated. Data is then backed up from the shadow copy instead of the original volume.

Discuss This Question: 4  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • jinteik
    IMHO, it is quite risky to run so many stuff at one server. once down then everything goes down at the same time...if your server is powerful enuff, install vmware (the free version) then seperate the rest... if you don't want to install vmware, you will need a backup s/ware to do image so that you can recover when your server goes down. so the most important is to be able to do backup when it is needed / scheduled
    18,995 pointsBadges:
  • Stevesz
    I generally do not backup the DNS or the DHCP if they are present on a server.They are easy enough to recreate, taking only moments to get up and running, unless you have a lot of reservations for DHCP. Your documentation for your server configuration should have all the information you need. On a server such as yours, I'd back up Exchange IS and flush the logs, the system state, and the data files for your business, including user directories. The system state includes SYSVOL, AD, the registry, and other important files for the system so there is no real need to backup SYSVOL separately. Many backup solutions allow you to backup to disk, including NTBACKUP, and then, if you wish to have the backup on tape, you can backup to tape from the disk backup. The backup to disk will take less time than the tape backup. You should store at least on current backup off site in case of a serious disaster that destroys the server and/or the area where backups are stored. This could be a tape or a portable external hard drive. I really see no need for the virtual machine Jinteik suggests. That carries its own requirements and headaches to set up and maintain. While it is not ideal to be running Exchange on a domain controller, it does work. When it comes time to upgrade your current equipment and/or server OS, you may want to consider using two servers, which will allow you some redundancy with your AD and DNS, and possibly using one machine for just data, and the other machine for Exchanage.
    2,015 pointsBadges:
  • Davidmichel
    Well what about client data? If only the server has data worth keeping then fine but if some of those clients have data that actually has value to the company then that needs to be protected as well. For something like this I lke a library with two LTO4 or 5. Setup one or two jobs to back everything up, and use multiplex so that it will be possible to achive the potential throughput these drives have. If you are just concerned about the server then why not just go with disk to disk mirroring or better yet setup a cluster. In either case you are spending the time up front instead of at the backup setting up a new server when the existing on goes down.
    570 pointsBadges:
  • btempleton
    Restore is the main issue. Should you have to rebuild this server you would to do a lot of reinstalling. For example, you would have to reinstall Exchange before you could restore just the database. You did not state whether you have a budget, but you might want to consider 3rd party products like Acronis that have a specific product for backing up and restoring Exchange that is much easier and faster that going through a Microsoft restore. Using snapshot technology products, you could even restore the whole server to the same physical machine or to another one if you are facing hardware replacement. These products are not free, but I think they are worth spending money on. My company lives and dies by email. I have to keep exchange going with a minimum amount of down time.
    220 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: