In a previous blog post I outlined a failure behavior of the file share witness resource on Windows 2008 clusters. http://blogs.technet.com/timmcmic/archive/2009/01/22/exchange-2007-sp1-ccr-windows-2008-clusters-file-share-witness-fsw-failures.aspx Ultimately there could exist a condition where the cluster enters a lost quorum state due to the File Share Witness resource being in a FAILED status even though the witness directory was fully available….
Installing Exchange 2010 rollups on DAG servers…
Great blog post on installing rollup updates on DAG members. http://www.ucblogs.net/blogs/exchange/archive/2009/12/15/Installing-Exchange-2010-rollups-on-DAG-servers.aspx
Do I need to move my cluster core resources?
Recently one of our Exchange MVPs posted a question to our support engineers…Is it necessary to move the cluster group / cluster core resources in Exchange 2007 / Exchange 2010? As a reminder…the cluster core resources are generally the cluster name and cluster IP address. This is the management name specified when the cluster is…
Exchange 2010 – Pre-staging the Cluster Name Object (CNO) to support a Database Availability Group (DAG)
In Exchange 2010 when using the Database Availability Group (DAG) we leverage the cluster services in Windows 2008 and Windows 2008 R2. When utilizing the cluster services in Windows 2008 and Windows 2008 R2 the cluster core resources – cluster name is a Kerberos enabled name. This requires that a machine account be created within…
Windows 2003 / Exchange 2007 SP1 – Alternate Cluster Setup
The official TechNet documentation for establishing a Windows 2003 / Exchange 2007 SP1 cluster can be found at: Exchange 2007 SP1 Single Copy Clusters (SCC) – http://technet.microsoft.com/en-us/library/bb125217.aspx Exchange 2007 SP1 Cluster Continuous Replication (CCR) – http://technet.microsoft.com/en-us/library/bb124521.aspx Installing Exchange 2007 SP1 Cluster Continuous Replication (CCR) on Windows 2003 – http://technet.microsoft.com/en-us/library/aa997144.aspx Installing Exchange 2007 SP1 Single Copy…
Windows 2008 – Exchange 2007 SP1 – Alternate Cluster Setup
The official TechNet documentation for establishing a Windows 2008 / Exchange 2007 SP1 cluster can be found at: Exchange 2007 SP1 Single Copy Clusters (SCC) – http://technet.microsoft.com/en-us/library/bb125217.aspx Exchange 2007 SP1 Cluster Continuous Replication (CCR) – http://technet.microsoft.com/en-us/library/bb124521.aspx Installing Exchange 2007 SP1 Single Copy Clusters (SCC) on Windows 2008 – http://technet.microsoft.com/en-us/library/bb629581.aspx Installing Exchange 2007 SP1 Cluster Continuous…
An interesting issue with file level antivirus…
In order for Exchange to function correctly administrators are generally advised to make two important configuration changes to their file level antivirus scanners: Exclude directories that contain Exchange binaries and Exchange data. Add process exclusions for the Exchange processes (for example – store.exe etc). When antivirus exclusions are not properly set servers may experience performance…
Considerations when using mountpoints with Exchange 2007 clusters.
It is not uncommon in many installations today, especially clustered installations, to see the use of mountpoints. When using mountpoints with clustering it is a requirement that the physical disk resources created for the mountpoints be dependant on the lettered physical volume that hosts them. The use of mountpoints also requires that the lettered physical…
‘ClusteredMailboxServer’ is partially configured – ExBPA.
When running ExBPA against an Exchange 2007 cluster, the following error text may be noted: =========================================================== Error: ‘ClusteredMailboxServer’ is partially configured Server: <SERVER> ‘ClusteredMailboxServer’ is partially configured on server <SERVER>.contoso.com. Either setup is configuring it right now or setup failed while configuring it. Please rerun setup if it isn’t currently running. =========================================================== The link text…
Log files required to be copied after an update-storagegroupcopy / re-seed has been successfully completed.
There may arise times where it is necessary to completely reseed an LCR, CCR, or SCR database copy from the source database. In order to reseed the copy we use the update-storagegroupcopy commandlet. When the update-storagegroupcopy is run, the database is pulled using the ESE backup online streaming API from the source machine to the…