Get extra internal hdd's or external hdd's to do the back up, and since you have not done any then your best bet is to do two or three back up jobs.
Back up methods:
Introduction to Exchange 2003 Backup Methods
Microsoft Exchange server has the usual range of backup methods, FULL, incremental and differential. What's new is Windows Server 2003 supplying the Volume Shadow Copy Service, which speeds up online Exchange 2003 backups.
What you need to do is the FULL back up.
When you have done the full back up you can then do an incremental back up (meaning any data that is changed, gets changed in the back up, so you do not have to do a full back up).
A full back up takes up more storage space than Incremental back ups.
Types of Exchange Server 2003 Backup
Full Backup
Make it your reflex to make a full backup of Exchange. Here are two killer reasons why a full backup is so much better than the alternatives; you only need one tape for a restore and a full backup purges the transaction logs.
Only resort to differential or incremental if the time taken by the full backup is unacceptable. If the duration seems too long for a full backup, try work-arounds like faster tapes, backup to disk then to tape. Anything to avoid having to use incremental or differential backups.
Differential Backup
If you have tried every trick in the book, and a full backup still takes too much time, then choose a differential rather than incremental backup. Remember that when you restore differential tapes, there must be a full backup as a reference point. Traditionally, the full backup is made at weekends, complimented by a differential backup on each weekday night. Times may vary but the guideline would be the hours of lowest user activity.
Unfortunately, differential backups do not purge or truncate the transaction logs, so not only does the differential backup get slightly bigger each day, but the logs are using up more and more disk space until you perform the next full backup.
Incremental Backup
Avoid this method. To prove my point try a test restore on a Friday. Calculate how many tapes you need and how long it will take. Realize that there is a five times greater chance of a slip up before the data is recovered, than with a full backup. Another clue that this is a poor method is that SQL and other relational databases do not allow incremental backups. Two tiny pieces of good news, incremental backups are quick and they do delete old portions of the transaction logs.
Copy Backup
This is a specialist method which is useful if you need to take a snapshot of the system without altering the archive bit. Differential and Incremental backups take their cue from the archive property of the files, so my point is that a copy backup doesn't affect other backup schedules that you have in place.
Daily Backup
This method surprised me, I thought that it would backup any file within the last 24hrs. Not so. It only backed up files that had changed since midnight, time stamp 0:00. I cannot recommend this method for Exchange 2003.
http://www.computerperformance.co.uk/exchange2003/exchange2003_backup_methods.htm
Please post back if you have any more problems or questions.
If this information is useful, please mark as helpful. Thanks.