Get-Exchange: High Availability

Showing posts with label High Availability. Show all posts

Wednesday, March 1, 2017

[LAB] Exchange 2007 CCR

Pre-requisites in both Mailbox servers

Import-Module Server Manager

Add-WindowsFeature RSAT-ADDS,Web-Server,Web-ISAPI-Ext,Web-Metabase,Web-Lgcy-Mgmt-Console,Web-Basic-Auth,Web-Windows-Auth

To each MBX server, on Hyper-V:

Click on SCSI Controler -> Hard Drive -> Add -> New -> Create a new VHD (one per server)
Click on Add Hardware -> Network Adapter -> Add -> Select a private heartbeat network

Turn on the servers and:

Rename NICs, add IPs and Set the correct binding order
Bring the disks Online and Initialize them (assign the same letter)
In the Server Manager -> Features ->Add Features -> Failover Clustering

In the first server

Create a Cluster
Add all mailbox servers (in validation warning select: I don't require support...)
Set name and cluster IP

Go to a CAS/HUB server

Create a folder called FSW_CCR1
Share the folder with Everyone and with Cluster Service Account
Finally give them Full Control Permissions

Back into the mailbox server

Open the Failover Cluster Management -> More Actions -> Configure Cluster Quorum Settings
Select Node And File Share Majority
Browse the Cas/Hub Server and select the Network sharing
Start installation of the Clustered Mailbox servers
Select Custom Exchange Server Installation -> Active Clustered Mailbox Role -> Cluster Continuous Replication
Add a name for the Clustered mailbox, specify the path for database files in the SCSI disk previously created and specify the IP Address of the Clustered mailbox
After completed, proceed with the installation of the other servers selecting Passive Clustered Mailbox Role

Tuesday, September 1, 2015

[EX2013] Content Index

Reseed the content index catalog if the mailbox database is part of a DAG

Reseed the content index catalog from any source

Update-MailboxDatabaseCopy -Identity DB1\MBX1 -CatalogOnly

Reseed the content index catalog from a specific source

Update-MailboxDatabaseCopy -Identity DB1\MBX1 -SourceServer MBX2 -CatalogOnly

Reseed the content index catalog if there is only one copy of the mailbox database

Stop-Service MSExchangeFastSearch
Stop-Service HostControllerService
Delete, move, or rename the folder that contains the Exchange content index catalog.
Start-Service MSExchangeFastSearch
Start-Service HostControllerService

Get-MailboxDatabaseCopyStatus | FL Name,*Index*

** ResetSearchIndex.ps1 **

Content Index status of all or most of the mailbox databases in the environment shows "Failed"

Create a new Active Directory group that is named "ContentSubmitters" and then grant Admistrators and NetworkService full access to the group. This is a dummy group and should be used as a placeholder only. You might want to add a description so that the group is not removed.
Force or wait for Active Directory replication.
Restart the following services:

Microsoft Exchange Search
Microsoft Exchange Search Host Controller

De <http://support.microsoft.com/kb/2807668/en-us>

Sunday, August 30, 2015

[EX2010] DAG Maintenance Cmdlets

Cmdlets

Get-MailboxDatabaseCopyStatus -id <dbname> -server <servername>

Test-ReplicationHealth -server <servername>

Suspend-MailboxDatabaseCopy -Identity <DB\MBX>

Resume-MailboxDatabaseCopy -Identity <DB\MBX> -ReplicationOnly (After the copy is resumed, it remains administratively blocked for activation.)

Update-MailboxDatabaseCopy -Identity <DB\MBX> -SourceServer <MBX2> -DeleteExistFile: $True -CatalogOnly -DatabaseOnly

.\CheckDatabaseRedundancy.ps1 -MailboxDatabaseName <DB>

.\StartDagServerMaintenance.ps1 -serverName <MBX>

.\StopDagServerMaintenance.ps1 -serverName <MBX>

Events

Event Viewer -> Applications and Services Logs

-> Microsoft -> Exchange -> HighAvailability

HighAvailability that contains events related to the startup and shutdown of the Microsoft Exchange Replication service and all the components that run within it, and events such as a database mount, log truncation or events related to the DAG's underlying cluster;

-> Microsoft -> Exchange -> MailboxDatabaseFailureItems

MailboxDatabaseFailureItems is used to log events associated with any failures that affect a replicated mailbox database;

-> Microsoft -> Exchange -> Troubleshooters

Troubleshooters is used by some Exchange troubleshooting scripts such as the Content Index Troubleshooter (Troubleshoot-CI.ps1) to log warnings and failures.

-> Microsoft-Exchange-Troubleshooters/Operational

-> MSExchange Management

If a database is in a “bad” state for over 20 minutes (in duration, not consecutive) in the hour-long run of the script, an EventID 4113 is generated and logged into the local server’s Application log. If the database is “ok” for 10 consecutive minutes, an EventID 4114 is logged.