lbicher56
asked on
How to improve network throughput for Exchange 2007 SP1 CCR
Hello,
I have an Exchange 2007 SP1 setup with CCR. This is running on Windows 2008 servers. I have to reseed all the storage groups on the passive node. I ran one successfully using the wizard from the Exchange Management Console last night. That was a 4 GB storage group and it took 7 hours to complete. That seems to be an excessive amount of time, and with my largest storage group at 80 GB, that rate is very bad.
The hardware is Dell poweredge 2950s with dual quad core processers and 4 GB of RAM. Network is Fast Ethernet. The servers are located on the same subnet and not across a WAN link. The servers are running Windows Server 2008 64 bit.
Is there something I am missing to increase the rate that these databases can reseed? Having a week long process to do this seems to defeat the purpose of a high availablity solution.
Thanks in advance.
I have an Exchange 2007 SP1 setup with CCR. This is running on Windows 2008 servers. I have to reseed all the storage groups on the passive node. I ran one successfully using the wizard from the Exchange Management Console last night. That was a 4 GB storage group and it took 7 hours to complete. That seems to be an excessive amount of time, and with my largest storage group at 80 GB, that rate is very bad.
The hardware is Dell poweredge 2950s with dual quad core processers and 4 GB of RAM. Network is Fast Ethernet. The servers are located on the same subnet and not across a WAN link. The servers are running Windows Server 2008 64 bit.
Is there something I am missing to increase the rate that these databases can reseed? Having a week long process to do this seems to defeat the purpose of a high availablity solution.
Thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Until I fix that, since I'm running update-storagegroupcopy via the Management console, if I run the command can I specify the public interface for now? I know that may interfere with client access but I may need to take that risk.