Backing up Exchange 2007 databases.. takes too long ?

Hello,

We have an Exchange server roughly 1TB in size, we are using CA ArcServe to backup our Exchange mailboxes. The data is split between 5 mail groups.

Our CA ArcServe is configured to do a full backup, Database Level Backup and using the active database. When the backup starts, it pulls down all 5 storage groups at once, each goes at rouhgly 150mb/min.

This to me sounds slow, does anyone know of any issues or ways to speed up exchange backups? They currently take 40+ hours to backup, delaying the tape write and the nightly job.

The exchange server is on VMWare infrastructure (vSphere 4.1.0, vCenter 4.1.0), the storage is Fibre.

 exch_logstatistics.png
mirdeAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
itprotocallConnect With a Mentor Commented:
a few things i could suggest you look at:

- you mentioned that the databases are stored on FC, so are you're backups going through FC or LAN?
  one way to ensure this is that the backup server 'sees' the same LUNs hosting your databases. By 'sees' i mean windows device manager should be able to see them and not necessary have them mounted or assigned to a drive letter.

- check for fragmentation on the volumes which host your exchange databases, this can have a significant impact.

- if you have a LCR or CCR copy of the database, then using the Replica instead of Active DB will definitely increase your throughput (this can easily be altered in the Exchange agent options while configuring the ARCserve backup job)

- are the 5 mailbox stores on different disk spindles (if there is a way for you to ensure this via your array configuration, this may help... but changing this may require downtime)

- some tweaks could be done to the 'buffers' and other registry values used by the ARCserve agent on your exchange box (for this i would suggest you reach out to CA support)
0
 
mirdeAuthor Commented:
I looked at your points, and they are good however they did not fix my issue, a reboot did.

Though your steps are useful for down the road troubleshooting.
0
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.

All Courses

From novice to tech pro — start learning today.