The following example outputs the LCR status of all mailbox databases in the
organization:
Get-MailboxDatabase | fl Identity, HasLocalCopy
Enabling the Storage Group
Before LCR is enabled, the storage group must also be configured with the Enable-StorageGroupCopy
cmdlet:
Enable-StorageGroupCopy -Identity < StorageGroupIdParameter > [-Confirm
[ < SwitchParameter > ]] [-CopyLogFolderPath < NonRootLocalLongFullPath > ]
[-CopySystemFolderPath < NonRootLocalLongFullPath > ] [-DomainController
< Fqdn > ] [-ReplayLagTime < Nullable > ] [-SeedingPostponed
< SwitchParameter > ] [-StandbyMachine < String > ] [-TruncationLagTime
< Nullable > ] [-WhatIf [ < SwitchParameter > ]]
The CopyLogFolderPath and CopySystemFolderPath parameters must contain a different path than
the source storage group. No other storage groups can share the same path.
The SeedingPostponed switch parameter takes no value and prevents the newly enabled storage group
copy from automatic seeding. Seeding is discussed in the next section.
This cmdlet continues the previous example, and LCR enables the first storage group on the server
MB100 without an initial seeding:
Enable-StorageGroupCopy -Identity ???mb100\first storage group???
-CopyLogFolderPath ???E:\LCRBackup\Logs\SG1Logs??? -CopySystemFolderPath
???E:\LCRBackup\Logs\SG1Logs??? -SeedingPostponed
Part III: Working with PowerShell in a Production Environment
336
Installing Clustering Continuous Replication (CCR)
Unlike LCR, CCR can be enabled only when installing the mailbox server.
Pages:
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477