Beruflich Dokumente
Kultur Dokumente
RAJI SUBRAMANIAN
Email: mail2raji@hotmail.com
Blog:http://rajisubramanian.wordpress.com
http://rajisubramanian.blogspot.in
3/9/2014
Author
Version
Change reference
07-Mar-14
Raji Subramanian
0.0
14-Mar-14
Raji Subramanian
0.1
20-Mar-14
Raji Subramanian
0.2
26-Mar-14
Raji Subramanian
0.3
TABLE OF CONTENTS
Introduction ............................................................................................................................................................................ 5
3.1
3.2
4.2
4.3
4.4
4.5
5.1.1
5.1.2
5.1.3
5.1.4
5.1.5
5.1.6
5.1.7
5.1.8
5.1.9
5.1.10
5.1.11
5.1.12
5.1.13
5.1.14
5.1.15
5.1.16
5.1.17
5.1.18
5.1.19
5.2
5.2.1
5.2.2
5.3
5.3.1
5.3.2
5.3.3
5.3.4
5.3.5
5.3.6
5.3.7
5.3.8
5.3.9
5.3.10
5.3.11
5.3.12
5.3.13
5.3.14
5.3.15
5.3.16
5.3.17
5.4
5.4.1
5.4.2
5.4.3
5.4.4
5.4.5
5.4.6
5.4.7
5.4.8
5.4.9
5.4.10
Find NDR 5.4.6 routing loops in the last day from all transport servers ............................................................ 18
6.2
6.3
6.4
6.5
6.6
6.7
9.1
9.2
9.3
9.3.1
9.3.2
9.3.3
9.3.4
9.4
9.5
Removing additional network interface (Backup, ISCSI and Storage) from Exchange Server 2013 DAG .................... 26
9.5.1
9.5.2
9.5.3
9.5.4
9.5.5
9.5.6
9.5.7
9.5.8
9.5.9
9.5.10
Check the all the network informated connected to the server ........................................................................ 27
9.6
9.6.1
9.6.2
9.6.3
INTRODUCTION
This is the draft initial copy prepared for Exchange Server 2013 Operation Guide
The following figure shows the main components of the Exchange 2013 Admin Center:
3.1
Follow the instructions in this section to install the prerequisites on domain-joined Windows 7 64-bit computers where you want
to install the Exchange management tools.
Exchange Server 2013 Operation Guide
1.
2.
3.
4.
After you've installed the operating system features, install the following software in the order shown:
1.
2.
3.
3.2
The Exchange management tools can be installed on a domain-joined computer with a default install of Windows 8 or Windows
8.1 64-bit. Installing the Exchange 2013 management tools
1.
2.
3.
Log on to the computer on which you want to install the Exchange 2013 management tools.
Navigate to the network location of the Exchange 2013 installation files.
At the command prompt, run the following command.
Note: If you have User Access Control (UAC) enabled, you must run Setup.exe from an elevated command prompt.
Setup.exe /Role:ManagementTools /IAcceptExchangeServerLicenseTerms
4.1
Role group
Organization
Management
View-Only
Organization
Management
Recipient
Management
Description
Administrators who are members of the Organization Management role group have administrative access
to the entire Exchange 2013 organization and can perform almost any task against any Exchange 2013
object, with some exceptions. By default, members of this role group can't perform mailbox searches and
management of unscoped top-level management roles.
Administrators who are members of the View Only Organization Management role group can view the
properties of any object in the Exchange organization.
Administrators who are members of the Recipient Management role group have administrative access to
create or modify Exchange 2013 recipients within the Exchange 2013 organization.
Compliance
Management
Public Folder
Management
Administrators who are members of the UM Management role group can manage features in the Exchange
organization such as Unified Messaging (UM) service configuration, UM properties on mailboxes, UM
prompts, and UM auto attendant configuration.
Administrators or users who are members of the Discovery Management role group can perform searches
of mailboxes in the Exchange organization for data that meets specific criteria and can also configure
litigation holds on mailboxes.
Users who are members of the Records Management role group can configure compliance features, such
as retention policy tags, message classifications, transport rules, and more.
Administrators who are members of this role group can configure server-specific configuration of
transport , client access, and mailbox features such as database copies, certificates, transport queues and
Send connectors, virtual directories, and client access protocols.
Users who are members of the Help Desk role group can perform limited recipient management of
Exchange 2013 recipients.
Users who are members of the Hygiene Management role group can configure the anti-spam and antimalware features of Exchange 2013. Third-party programs that integrate with Exchange 2013 can add
service accounts to this role group to grant those programs access to the cmdlets required to retrieve and
configure the Exchange configuration.
Users who are members of the Compliance Management role group can configure and manage Exchange
compliance configuration in accordance with their policies.
Administrators who are members of the Public Folder Management role group can manage public folders
on servers running Exchange 2013.
Delegated
Setup
Administrators who are members of the Delegated Setup role group can deploy servers running Exchange
2013 that have been previously provisioned by a member of the Organization Management role group.
UM
Management
Discovery
Management
Records
Management
Server
Management
Help Desk
Hygiene
Management
4.2
ApplicationImpersonation Role
ArchiveApplication Role
MailboxSearchApplication Role
Migration Role
Monitoring Role
MyAddressInformation Role
Databases Role
MyBaseOptions Role
MyContactInformation Role
MyDiagnostics Role
MyDisplayName Role
MyDistributionGroupMembership Role
MyDistributionGroups Role
MyMobileInformation Role
MyName Role
MyPersonalInformation Role
and
MyProfileInformation Role
UM Mailboxes Role
MyRetentionPolicies Role
UM Prompts Role
Journaling Role
MyTeamMailboxes Role
MyTextMessaging Role
LegalHoldApplication Role
MyVoiceMail Role
OfficeExtensionApplication Role
UserApplication Role
4.3
2.
3.
4.
4.4
New-RoleGroup
-Name
<Name>
-Roles
<Role
RecipientOrganizationalUnitScope server.mail.com/OU
Name>
-CustomConfigWriteScope
<SCOPE>
Example: New-RoleGroup -Name HelpdeskGroup -Roles ExchangeAdmin, Mail Recipients, Mail Recipient
Creation, Delegated Setup -RecipientOrganizationalUnitScope server.mail.com/Org CustomConfigWriteScope
SCOPE-ORG-EXCHSRV
4.5
Connect to an Exchange 2010 server with an account that is member of Organization Management role group.
Launch an Exchange Management Shell console with Run as administrator privileges.
Execute these commands:
OPERATIONS MANAGEMENT
Operations management involves the administration of an organization's infrastructure components and includes the day-to-day
administrative tasks, both planned and on-demand, that are required to keep an IT system operating smoothly. Typically,
operations management tasks are covered by written procedures. These procedures provide all support staff with the same
standard tools and methods.
5.1
MAILBOX MANAGEMENT
5.1.1
1.
2.
3.
4.
5.
6.
7.
5.1.2
5.1.3
5.1.4
This command will remove mailbox from Exchange server but not the AD account
Get-Mailbox <ACCOUNT> | Disable-Mailbox
Get-Mailbox <ACCOUNT> | Enable-Mailbox
5.1.5
5.1.6
This command will remove the user account from AD and mailbox from Exchange server
Get-Mailbox <ACCOUNT> | Remove-Mailbox
5.1.7
-UserPrincipalName
5.1.8
You can purge only against disconnected or soft-deleted mailboxes not on active mailbox
Remove-StoreMailbox -Database DB01 -Identity Raji -MailboxState SoftDeleted
Remove-StoreMailbox -Database DB01 -Identity "Raji" -MailboxState Disabled
5.1.9
Add-MailboxPermission -Identity "SharedMailbox" -User Rajis -AccessRights FullAccess -InheritanceType all -AutoMapping
$false
Note: Access Rights can be FullAccess, ExternalAccount, DeleteItem, ReadPermission, ChangePermission, ChangeOwner
Add-ADPermission -Identity SharedMailbox -User Rajis -ExtendedRights "Send As"
5.1.10
5.1.11
10
5.1.12
To Clean up Mailbox database after changes perfromed in the Active Directory or to sync with AD (i.e When account is disabled)
Get-MailboxStatistics -Database DB01 | ForEach { Update-StoreMailboxState -Database $_.Database -Identity $_.MailboxGuid
-Confirm:$false }
5.1.13
When mailbox is moved to a different database - the source mailbox will not be deleted from the source database. This source
mailbox is turned to soft-deleted state.
Get-MailboxDatabase -id <source database> | Get-MailboxStatistics | Where { $_.DisconnectReason -eq "SoftDeleted" } | ft
DisplayName,Database,DisconnectDate
5.1.14
5.1.15
5.1.16
5.1.17
Get-MigrationUser | Get-MigrationUserStatistics
Get-MoveRequestStatistics Identity 'RajiS' | Select DisplayName, Status, TotalMailboxSize, TotalMailboxItemCount,
PercentComplete, BytesTransferred, ItemsTransferred, BytesTransferredPerMinute
To clear move request
Get-MoveRequest MoveStatus "Completed" | Remove-MoveRequest
5.1.18
11
5.1.19
5.2
CONTACT MANAGEMENT
5.2.1
1.
2.
3.
4.
5.2.2
5.3
5.3.1
1.
2.
3.
4.
5.3.2
5.3.3
The below list of options need to be consider when adding members or removing members from the group
Exchange Server 2013 Operation Guide
12
5.3.4
The below list of options need to be consider when for sending and receiving email from Group
Only senders inside my organization: Select this option to allow only senders in your organization to send messages to
the group. This means that if someone outside of your organization sends an email message to this group, it will be
rejected. This is the default setting.
Senders inside and outside of my organization: Select this option to allow anyone to send messages to the group.
Note: If youve configured the group to allow only senders inside your organization to send messages to the group, email
sent from a mail contact will be rejected, even if they are added to this list.
5.3.5
The below list of options need to be consider for Email approval for Sending message to the Group
Select moderation notifications Use this section to set how users are notified about message approval.
o Notify all senders when their messages aren't approved This is the default setting. Notify all senders, inside
and outside your organization, when their message isn't approved.
o Notify senders in your organization when their messages aren't approved When you select this option,
only people or groups in your organization are notified when a message that they sent to the group isn't
approved by a moderator.
o Don't notify anyone when a message isn't approved When you select this option, notifications aren't sent
to message senders whose messages aren't approved by the group moderators.
5.3.6
5.3.7
13
5.3.8
5.3.9
5.3.10
5.3.11
5.3.12
5.3.13
5.3.14
Set-MailboxRegionalConfiguration Identity 'RajiS' Language 'Es-es' TimeZone 'Eastern Standard Time' DateFormat 'ddmm-yyyy'
5.3.15
14
5.3.16
Set-MailboxMessageConfiguration -Identity 'RajiS' -AutoAddSignature $True SignatureText 'Thanks & Regards - Raji
Subramanian'
5.3.17
5.3.18
5.3.19
Set-Mailbox -Identity "RajiS" -IssueWarningQuota 2GB -ProhibitSendQuota 2.5GB -ProhibitSendReceiveQuota 3GB UseDatabaseQuotaDefaults $false
5.3.20
5.3.21
5.3.22
5.3.23
5.3.24
5.3.25
5.3.26
15
5.4
GROUPS ADMINISTRATION
5.4.1
Distribution Group Creation
New-DistributionGroup -Name "IT Exchange Administrators" -Alias ExAdmin -MemberJoinRestriction
open
5.4.2
Distribution Group Modification
Set-DistributionGroup -Identity Executives -ModerationEnabled $true -ModeratedBy administrator SendModerationNotifications Internal
Set-DistributionGroup -Identity Sales -AcceptMessagesOnlyFrom 'Bob','John'
Set-DistributionGroup -Identity Sales -AcceptMessagesOnlyFromSendersOrMembers bob@mail.com
Set-DistributionGroup -Identity Executives -RejectMessagesFromSendersOrMembers HourlyEmployees
Set-DistributionGroup -Identity HelpDesk -RequireSenderAuthenticationEnabled $false
5.4.3
Security Group Creation
New-DistributionGroup -Name "FolderAdmin" -Alias fsadmin -Type security
5.4.4
Security Group Modification
Set-DistributionGroup "FolderAdmin" -EmailAddresses
SMTP:folder.admins@mail.com,smtp:folder@mail.com
5.4.5
Dynamic Distribution Group Creation
New-DynamicDistributionGroup -Name Accounting -Alias Accounting -IncludedRecipients
MailboxUsers,MailContacts -OrganizationalUnit Accounting -ConditionalDepartment accounting,finance RecipientContainer mail.com
5.4.6
Dynamic Distribution Group Modification
Set-DynamicDistributionGroup -Name Accounting -HiddenFromAddressListsEnabled $true MaxReceiveSize 5MB -ModerationEnabled $true -ModeratedBy administrator
5.4.7
To create mail contact
New-MailContact -Name "Raji Subramanian" -ExternalEmailAddress mail2raji@mail.com OrganizationalUnit Users
5.4.8
To configure mail-enable on existing contact
Enable-MailContact -Identity "Raji Subramanian" -ExternalEmailAddress mail2raji@mail.com
5.4.9
To create mail user
New-MailUser -Name RajiS -Alias Rajis -UserPrincipalName mail2raji@hotmail.com
5.4.10 Creating Resource mailbox
New-Mailbox -Name 'RoomA' -Alias 'RoomA' -OrganizationalUnit 'mail.com/Resources' UserPrincipalName 'RoomA@mail.com' -SamAccountName 'RoomA' -FirstName 'Room' -LastName 'A'
Room
16
5.5.1
Creating Transport Rule
New-TransportRule -Name "Mark messages from the Internet to Sales DG" -FromScope
NotInOrganization -SentTo "SalesGroup" -PrependSubject "External message to Sales DG:"
5.5.2
Displaying Transport Rule
Get-TransportRule "Sender is a member of marketing" | Format-List
5.5.3
Disabling Transport Rule
Disable-TransportRule "Sender is a member of marketing"
5.5.4
Enabling Transport Rule
Enable-TransportRule "Sender is a member of marketing"
5.5.5
Removing Transport Rule
Remove-TransportRule "Sender is a member of marketing"
5.6
5.6.1
Creating Mailbox Move Request
New-MoveRequest -Identity 'tony@alpineskihouse.com' -TargetDatabase "DB01"
5.6.2
Modifying Mailbox Move Request
Set-MoveRequest -Identity Ayla@humongousinsurance.com -BadItemLimit 5
5.6.3
Removing Mailbox Move Request
Remove-MoveRequest -Identity 'Ayla@humongousinsurance.com'
5.6.4
5.7
5.7.1
17
5.7.2
Get-MessageTrackingLog -MessageSubject "This is Test Email" -Start "04/03/2014 00:00:00" -End "05/03/2014 00:00:00" server Server01
5.7.3
Get-MessageTrackingLog -MessageSubject "This is Test Email" -Start "04/03/2014 00:00:00" -End "05/03/2014 00:00:00" server Server01
5.7.4
Get-TransportService | Get-MessageTrackingLog -MessageSubject "This is Test Email" -Start "04/03/2014 00:00:00" -End
"05/03/2014 00:00:00"
5.7.5
5.7.6
5.7.7
Get-MessageTrackingLog
-EventId
FAIL
-Start
"04/03/2014
00:00:00"
TimeStamp,Source,EventID,Recipients,Sender,RecipientStatus -wrap -autosize
5.7.8
-server
server01
ft
ForEach ($server in Get-TransportServer) {Get-MessageTrackingLog -EventId EXPAND -Start "04/03/2014 00:00:00" -server
$server.name | ft Timestamp,Sender,RelatedRecipientAddress,Recipients,RecipientStatus -wrap -autosize}
5.7.9
5.7.10
Find NDR 5.4.6 routing loops in the last day from all transport servers
18
foreach ($server in Get-TransportServer) {Get-MessageTrackingLog -resultsize unlimited -EventId FAIL -Start (GetDate).AddDays(-1)
-server
$server.name
|
where
{$_.RecipientStatus
-like
'*5.4.6*'}
|
ft
Timestamp,Recipients,RecipientStatus,Sender -wrap -autosize}
DAILY TASKS
To help ensure the availability and reliability of your Exchange 2013 organization, you must actively monitor the physical
platform, the operating system, and all important Exchange 2013 services. Preventive maintenance helps you identify
potential errors before any one of these errors cause problems with the operation of your Exchange organization.
Preventive maintenance combined with disaster recovery planning and regular backups help minimize problems if they
occur.
Monitoring your Exchange organization involves checking for problems with connections, services, server resources, and
system resources. You can also set alerts to notify administrators when problems occur. Microsoft Windows Server 2008
R2 and Exchange 2013 provide you with many monitoring tools and services to help make sure that your Exchange
organization is running smoothly. The key advantages to daily monitoring are as follows:
Meeting the performance requirements of your service level agreements (SLAs).
Completing successfully specific administrative tasks, such as daily backup operations, and checking server
health.
Detecting and addressing issues, such as bottlenecks in the server performance or need for additional
resources before they affect productivity.
Daily maintenance tasks help you establish criteria for what is normal for your organization and to detect any abnormal
activity. It is important to implement these daily maintenance tasks so that you can capture and maintain data about your
Exchange organization, such as usage levels, possible performance bottlenecks, and administrative changes. See the
following topics for information about tasks that you should perform daily as a best practice:
Performing Physical Environmental Checks
Performing and Monitoring Backups
Checking Disk Usage
Checking the Event Viewer
Monitoring Server Performance
Monitoring Network Performance
6.1
6.2
19
Proactively monitoring the successful completion of your Exchange backups is critical to success of your disaster recovery
plan. Regular testing of the disaster recovery plan for your organization's Exchange infrastructure should be performed in
a
lab environment that mimics your production environment as closely as practicable.
Note: Ensure that Exchange aware backup product is used to backup Exchange infrastructure.
6.3
6.4
6.5
6.6
6.7
WEEKLY TASKS
As a recommended practice, perform the following tasks and procedures weekly:
20
Check for Security Updates - Identify any new service packs, hotfixes, or updates. If appropriate, test these in a test
lab and use the change control procedures to arrange for deployment to the production servers.
Review Performance Figures - Check the key performance data for the previous week. Review performance against
this week. Identify trends and items that have not met their targets.
Environmental Tests - Check periodically and maintain air conditioning, temperature and humidity monitors, and
physical security measures.
Site Link Utilization Weekly utilization reports of the network link should be provided by the Network Team
MONTHLY TASKS
As a recommended practice, perform the following tasks and procedures monthly:
Security Checks - Depending on the level of security that your organization requires, it may be appropriate to
perform regular audits of security, including firewall rules, user rights, group membership, delegate rights, and so
on.
Capacity Planning - Review capacity figures for the previous month, and produce a plan for any upgrades that may
be required in the coming months to keep the system operating within limits specified by the organization's service
level agreements (SLAs).
Disaster Recovery Test - Perform a system recovery for a single server to test your organization's documented
recovery process. This test will simulate a complete hardware failure for one server, and make sure that the
resources, plans, and data are available for recovery. Try to rotate the focus of the test each month, so that you test
the failure of a different server or other piece of equipment every time.
9
9.1
Get-MailboxDatabasecopyStatus * | Format-List
Update-MailboxDatabaseCopy -Identity <DATABASE>\<SRV_NAME> -SourceServer <MBX_SERVER>
Update-MailboxDatabaseCopy -Identity DB1\MBX1 CatalogOnly
Update-MailboxDatabaseCopy -Identity DB1\MBX1 DatabaseOnly
9.2
Step 1: Provide the folder path location to the backup team where the database and log file needs to restore.
Note: Make sure you have enough free disk space on the restored location
Step 2: Verify the database health status after the restoration of database file. Run the following command to verify the status
eseutil.exe /mh E:\Recovery\RDB.edb | select-string State:, Log Required
Step 3: If the database is Clean Shutdown move to next step. In case if it is dirty shutdown perform the soft recovery and if it fails
move to hard recovery
Step 4: Create Recovery database using the following commands
New-MailboxDatabase -Recovery RDB01 -Server MBX01 -EdbFilePath E:\Recovery\RDB.edb
Exchange Server 2013 Operation Guide
21
New-MailboxRestoreRequest -SourceDatabase RDB01 -SourceStoreMailbox Raji -TargetMailbox Subramanian TargetRootFolder Restore -AllowLegacyDNMismatch
Restoring the mailbox email in a seperate folder (Restore) on the user mailbox
22
9.3
9.3.1
1.
Suspending activation for the database copies on the server being updated
-ActivationOnly
To force all database to be activated on a particular Mailbox server, use this command:
Suspending the Exchange 2013 mailbox server MBX01 from the cluster
Verify there is no database mounted or active database on the server that will be under maintenance
9.3.2
23
Test-ReplicationHealth
9.3.3
9.3.4
9.4
Migration from Exchange Server 2007 Managed Mailbox Folder Policy to Exchange Server 2013 Retention Policy
24
MRM which denotes as Messaging Record Management uses Retention Tag and Retention Policy to perform their operation using
the Mailbox Assistant service in Exchange server 2013. The below steps indicates the migration from Exchange Server 2007
Managed Mailbox Folder Policy to Exchange Server 2013 Retention Policy. The same procedure can also be used if you have only
Exchange 2013 server skipping the Exchange 2007 MRM configuration
Few important points:
It uses MRM version 2.0 whereas Exchange 2007 hold MRM Version 1.0
In Exchange 2007 we have terms known as Managed Folder, Managed Folder Content, Managed Folder Policy these
are no more supported in Exchange 2013.
As similar ManagedFolderAssistantSchedule in Exchange 2007 Mailbox server we have workcycle for Exchange 2013
Mailbox Server
In Exchange 2007 SP1 when we use managed default folders we need Exchange Standard client access license
whereas on using managed custom folders then we need an Exchange Server Enterprise CAL.
2.
To schedule the mailbox folder assistance for Exchange 2007 Mailbox Server
Set-MailboxServer -Identity MailboxServer -ManagedFolderAssistantSchedule "Sun.14:00-Sun.13:00"
3.
To check the mailbox folder assistance schedule for Exchange 2007 Mailbox Server
Get-MailboxServer -Identity MailboxServer | fl Name, ManagedFolderAssistantSchedule
4.
5.
6.
Migration of Exchange 2007 Managed Folder to Exchange Server 2013 Retention Policy Tag
New-RetentionPolicyTag -Name 'Exchange 2013 Retention Tag' -ManagedFolderToUpgrade 'Exchange 2007 Managed
Folder
2.
3.
Set-RetentionPolicyTag "'Exchange 2013 Retention Policy " -Comment "This folder is under retention policy and Items
in the Deleted Items folder will be automatically deleted in 14 days"
Exchange Server 2013 Operation Guide
25
4.
5.
6.
7.
9.5
REMOVING ADDITIONAL NETWORK INTERFACE (BACKUP, ISCSI AND STORAGE) FROM EXCHANGE SERVER 2013 DAG
Whenever you add additional network to the DAG network for example additional interface for ISCSI, additional LAN Interface
for Storage or additional LAN interface to take backup this may leads to collide with Exchange 2013 DAG network automatically
and may result issue as follows,
9.5.1
9.5.2
9.5.3
9.5.4
Check the Network role status in the cluster service (New Network 01)
if Role 0 (00) tells the cluster not to use the network;
if Role 1 (01) tells the cluster that this is a private network;
if Role 3 (03) tells the cluster that this is a public network.
C:\Windows\system32>cluster network 'New Network 01' /prop
Listing properties for 'New Network 01':
26
T Network
Name
Value
-- -------------------- ------------------------------ ----------------------SR Cluster Network 1 Name
Cluster Network 1
MR Cluster Network 1 IPv6Addresses
MR Cluster Network 1 IPv6PrefixLengths
MR Cluster Network 1 IPv4Addresses
100.200.26.0
MR Cluster Network 1 IPv4PrefixLengths
24
SR Cluster Network 1 Address
100.200.26.0
SR Cluster Network 1 AddressMask
255.255.255.0
S Cluster Network 1 Description
D Cluster Network 1 Role
3 (0x3)
D Cluster Network 1 Metric
10000 (0x2710)
D Cluster Network 1 AutoMetric
1 (0x1)
9.5.5
9.5.6
9.5.7
9.5.8
9.5.9
9.5.10
9.6
9.6.1
27
Dismount state). It communicates with other members in the DAG when it responds the bit set to 1 and allowed to mount
database
Quorum Details
Odd number of nodes
Even number of nodes (but not a multi-site cluster)
Even number of nodes, multi-site cluster
Even number of nodes, no shared storage
Continous replication uses initial File Mode to replicate 1 MB of file to the passive database. When File Mode completes it moves
to Block Mode for immediate updates
Port 3343 is used Nodes for listening incoming connections from other nodes of the DAG Members
I believe it more enough to know the definition let us move pratically what we do in our Exchange infra. Its always good to have
documentaion of the below component information which will helps in case if our servers are in disaster.
9.6.2
AutoDatabaseMountDial:
Get-Mailboxserver <MailboxServerName> | FL Name, AutoDatabaseMountDial
To verify Quorum
Cluster /quorum
28
To Check DagNetworkConfiguration
Get-DatabaseAvailabilityGroup | FL Name, ManualDagNetworkConfiguration
9.6.3
When the primary site fails due to disaster on the odd nodes due to power Outage or server failure follow the below steps
Use the Stop-DatabaseAvailabilityGroup to mark the primary site DAG members are in failed state.
Stop-DatabaseAvailabilityGroup Identity <DAGName> -ActiveDirectorySite PrimarySite
Stop the cluster service in all the passive node of the secondary site
Stop-service clussvc
Use the Restore-DatabaseAvailablityGroup to remove the stoppedmailbox server from the DAG and re-establish the quorum
using the alternate Witness server
Restore-DatabaseAvailabilityGroup <DAGName> -Activedirectorysite DR
When the service or power is restored in the Primary site is up run Start-DatabaseAvailabilityGroup to revert the datacenter
Start-DatabaseAvailabilityGroup <DAGName> -ActiveDirectorySite ProductionSite
Still if its show the older quorum model execute the below powershell cmdlet
Set-DatabaseAvailabilityGroup -Identity DAG01
29