H i g h Av a i l a b i l i t y in Software

Encoding QR Code in Software H i g h Av a i l a b i l i t y

6 On the Set Paths page, select the paths for system files and transaction logs Click Next 7 On the Mailbox Database page, select the path where the database should be replicated to and click Next 8 On the Enable page, review the paths selected in the previous steps Click Enable to enable LCR replication 9 On the Completion page, review the output to ensure LCR was enabled successfully Then click Finish to close the wizard To enable LCR using the Exchange shell, use the following commands:

Enable-DatabaseCopy "E12Postcard\SG3\SG3-MBX2" CopyEDBFilePath "E:\SG3-MBX2\SG3-MBX2EDB"

In these commands, E12Postcard is the server name, SG3 the storage group, and SG3-MBX2 the mailbox database Note that the path includes the EDB filename Next, enable LCR on the storage group:

Enable-StorageGroupCopy "E12Postcard\SG3" CopyLogFolderPath "C:\SG3-Logs" CopySystemFolderPath "C:\SG3-Logs"

Once an LCR replica is created on a server, the server cannot be a target of a Standby Continuous Replication (SCR is discussed later in this chapter) replica from another Exchange server However, you can replicate a storage group from this server to any other server using SCR, including any storage groups that are already being replicated locally using LCR

When you re creating new storage groups using the EMC, the New Storage Group Wizard provides the ability to enable LCR for the storage groups and to select replica log and system file paths during creation To create a new storage group and enable LCR for it, use the following command:

New-StorageGroup Server "E12Postcard" Name "E12Postcard-SG4" SystemFolderPath C:\SG4-Logs" LogFolderPath "C:\SG4-Logs" HasLocalCopy $true CopyLogFolderpath "E:\SG4-Logs" CopySystemFolderPath "E:\SG4-Logs"

A storage group without a database is of no particular use In fact, if you leave a storage group in this state with LCR enabled, the Microsoft Exchange Replication Service will take the opportunity to chastise you for it, by logging Event ID 2062 in the Application event log The event reminds you that there are no databases to replicate you should either create one or delete the storage group Being the good Exchange geeks that we are, we will not provide any Exchange service to complain or be dissatisfied with our attitude to it In the next step, we create a new mailbox database and enable replication for it The New Mailbox Database Wizard behaves like the New Storage Group Wizard it allows you to specify the path for the LCR replica database Here s how to create a new mailbox database and enable it for LCR using the Exchange shell:

New-MailboxDatabase StorageGroup "E12Postcard-SG4" Name "E12Postcard-SG4-MBX1" EDBFolderPath "C:\SG4-MBX1" CopyEDBFolderPath "E:\SG4-MBX1"

Part VI:

With LCR enabled, one should keep a close eye on replication health We want to ensure the replica is marching in lockstep with the active copy of the storage group, that copy and replay queues are not building up, and that there is not a huge gap between the time when logs are closed by the active storage group and when they are copied, inspected, and replayed to the replica This can be done using the EMC by viewing the properties of a storage group, as shown in Figure 19-2, or you can do it from the shell As you may already have noticed when working with the EMC and the shell, the latter generally provides more information Here s the command to use:

Get-StorageGroupCopyStatus "E12Postcard\E12Postcard-SG4"

the identity of an object that is the target of a particular shell command is the first parameter you use after the command, you can also get by without having to type identity every time

The preceding command outputs replication status in brief, by displaying four important parameters SummaryCopyStatus, CopyQueueLength, ReplayQueueLength, and LastInspectedLogTime The SummaryCopyStatus parameter can be Healthy, Seeding, Copying, Stopped, Disabled, or Failed The CopyQueueLength parameter, as the name