During my last failover (due to a switch needing to be replaced) I noticed that my time duration for failover was really long... like 8-10 minutes! Most of the resources were okay in moving but the MS Exchange IS just sat in online pending mode for quite some time (the afore mentioned 8 minutes). Are there any general tips for figuring what would cause such behavior? One thing I did want to address specifically was that for several days prior to the failover my backups were not purging the log files (which thankfully has been rectified!) and there were about 25GB of logs at the time of failover. Would that cause a longer failover? Do the logs get replayed in some manner during a failover. As FYI, the logs sit on the cluster shared storage on a RAID-1 set of 36GB drives. Thanks for any insights. Dan
Hi, You got the answer yourself. The larger the number of transaction logfiles the longer it will take for the Information store service to start. Leif "Dan" wrote in message news:7C02788D-6219-452C-A9B9-1BDD7B41D155@microsoft.com... > During my last failover (due to a switch needing to be replaced) I noticed > that my time duration for failover was really long... like 8-10 minutes! > Most of the resources were okay in moving but the MS Exchange IS just sat > in > online pending mode for quite some time (the afore mentioned 8 minutes). > Are > there any general tips for figuring what would cause such behavior? One > thing I did want to address specifically was that for several days prior > to > the failover my backups were not purging the log files (which thankfully > has > been rectified!) and there were about 25GB of logs at the time of > failover. > Would that cause a longer failover? Do the logs get replayed in some > manner > during a failover. As FYI, the logs sit on the cluster shared storage on a > RAID-1 set of 36GB drives. > Thanks for any insights. > Dan
Your App log would be a good place to start looking. The fact that you have large amounts of t-logs should not really matter as the large share of the t-logs will already have been committed to the DB. After a failover, if Exchange needs to replays log files it will look at the check point file see where it needs to start. An event is generated for every log that is replayed. Trawl through your app log from the point where you did the failover and you might dig something up /Simon "Dan" wrote in message news:7C02788D-6219-452C-A9B9-1BDD7B41D155@microsoft.com... > During my last failover (due to a switch needing to be replaced) I noticed > that my time duration for failover was really long... like 8-10 minutes! > Most of the resources were okay in moving but the MS Exchange IS just sat > in > online pending mode for quite some time (the afore mentioned 8 minutes). > Are > there any general tips for figuring what would cause such behavior? One > thing I did want to address specifically was that for several days prior > to > the failover my backups were not purging the log files (which thankfully > has > been rectified!) and there were about 25GB of logs at the time of > failover. > Would that cause a longer failover? Do the logs get replayed in some > manner > during a failover. As FYI, the logs sit on the cluster shared storage on a > RAID-1 set of 36GB drives. > Thanks for any insights. > Dan
