Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Exchange DataBase backup performance
- Thread starter jjjon
- Start date
theravager
Technical User
Sounds pretty normal to me, thats a pretty massive exchange database unless its 2007.
Our Exchange DBs are comp in size to yours at 177GB and 2:15 - 2:30 or roughly 75-80GB/Hour for 1 and the other at 189GB takes 2:30 - 3 hours at about 65-70GB/Hour.
Our 2003 Exchange DB LUNs are on our Fiber SAN and we use CommVault 7 to first dump them to disk (HP MSA 1500 with SATA disks) and then they get auxcopied to LTO4 tape the following morning.
Not sure if that is anything close to your environment or not, but that is ours.
Our 2003 Exchange DB LUNs are on our Fiber SAN and we use CommVault 7 to first dump them to disk (HP MSA 1500 with SATA disks) and then they get auxcopied to LTO4 tape the following morning.
Not sure if that is anything close to your environment or not, but that is ours.
Hello
I would expect to see anything up to 175GB/hour (or maybe a little more) for large databases such as Exchange, SQL, Oracle.. and so on from a gigabit LAN backup datapath to a B2D target. This is assuming optimum setup following best practice.
20GB/h sounds like somewhere there is a bottleneck.
You need to verify the memory, CPU, disk & NIC performance counters on the Exchange server and the mediaAgent, using PerfMon. Then you should see where a bottleneck is.
Perhaps you could detail the datapath and the backup target as well as the hardware spec of the client and MA if you need more suggestions.
---------------------------------------
EMCTA & EMCIE - Backup & Recovery
Legato & Commvault Certified Specialist
MCSE
I would expect to see anything up to 175GB/hour (or maybe a little more) for large databases such as Exchange, SQL, Oracle.. and so on from a gigabit LAN backup datapath to a B2D target. This is assuming optimum setup following best practice.
20GB/h sounds like somewhere there is a bottleneck.
You need to verify the memory, CPU, disk & NIC performance counters on the Exchange server and the mediaAgent, using PerfMon. Then you should see where a bottleneck is.
Perhaps you could detail the datapath and the backup target as well as the hardware spec of the client and MA if you need more suggestions.
---------------------------------------
EMCTA & EMCIE - Backup & Recovery
Legato & Commvault Certified Specialist
MCSE
It takes me about 2-4 hours backing up 8 SG's in our 2 exchange 2003 clusters. I do disk staging then aux also.
I run each SG as its own job and run all 4 sg's concurrently
I get about 45-60gb/hour. Each SG is about 180-200gb
The main thing I found is that a dedicated NIC is needed if you are not using LANLESS backups.
I had a binding order issue with exchange clusters
Microsoft wants the public lan to be at the top and Commvault wants the nic it uses to be at the top also.
So DIP's are needed to resolve. Even then it is not for sure.
Hope this helps,
Frank
I run each SG as its own job and run all 4 sg's concurrently
I get about 45-60gb/hour. Each SG is about 180-200gb
The main thing I found is that a dedicated NIC is needed if you are not using LANLESS backups.
I had a binding order issue with exchange clusters
Microsoft wants the public lan to be at the top and Commvault wants the nic it uses to be at the top also.
So DIP's are needed to resolve. Even then it is not for sure.
Hope this helps,
Frank
- Status
Similar threads
- Locked
- Question