This logic is tuned with the
AutoDatabaseMountDial parameter. There are three possible settings:
??‘ Lossless
??‘ GoodAvailability
??‘ BestAvailability
The Lossless setting prevents the passive node from mounting if any logs are missing. In most
circumstances the system will need to wait until the failed node is back online and the missing logs can
be copied to the passive node. This setting allows for an administrator to explicitly decide when to bring
a failed system online.
GoodAvailability sets the copy queue to three logs and BestAvailability is six logs.
The next tuning parameter is ForceDatabaseMountAfter . The ForceDatabaseMountAfter setting
forces the database to mount after a specified period of time. For example, if
ForceDatabaseMountAfter is set to one hour, if the passive node fails to copy all required logs the
database will mount with some data loss.
Chapter 12: Working with Continuous Replication
355
Both of these parameters are configured with the Set-MailboxServer cmdlet:
Set-MailboxServer -Identity < MailboxServerIdParameter > [-AutoDatabaseMountDial
< Lossless | GoodAvailability | BestAvailability > ] [-ClusteredStorageType
< Disabled | NonShared | Shared > ] [-Confirm [ < SwitchParameter > ]]
[-DomainController < Fqdn > ] [-FolderLogForManagedFoldersEnabled < $true |
$false > ] [-ForcedDatabaseMountAfter < Unlimited > ]
[-JournalingLogForManagedFoldersEnabled < $true | $false > ] [-Locale
< MultiValuedProperty > ] [-LogDirectorySizeLimitForManagedFolders < Unlimited > ]
[-LogFileAgeLimitForManagedFolders < EnhancedTimeSpan > ]
[-LogFileSizeLimitForManagedFolders < Unlimited > ] [-LogPathForManagedFolders
< LocalLongFullPath > ] [-ManagedFolderAssistantSchedule < ScheduleInterval[] > ]
[-MAPIEncryptionRequired < $true | $false > ] [-MessageTrackingLogEnabled < $true
| $false > ] [-MessageTrackingLogMaxAge < EnhancedTimeSpan > ]
[-MessageTrackingLogMaxDirectorySize < Unlimited > ]
[-MessageTrackingLogMaxFileSize < Unlimited > ] [-MessageTrackingLogPath
< LocalLongFullPath > ] [-MessageTrackingLogSubjectLoggingEnabled < $true |
$false > ] [-RedundantMachines < MultiValuedProperty > ] [-ReplicationNetworks
< PrivateOnly | PrivateThenMixed | AllNetworks > ]
[-RetentionLogForManagedFoldersEnabled < $true | $false > ]
[-SubjectLogForManagedFoldersEnabled < $true | $false > ]
[-SubmissionServerOverrideList < MultiValuedProperty > ] [-WhatIf
[ < SwitchParameter > ]]
Set-MailboxServer [-AutoDatabaseMountDial < Lossless | GoodAvailability |
BestAvailability > ] [-ClusteredStorageType < Disabled | NonShared | Shared > ]
[-Confirm [ < SwitchParameter > ]] [-DomainController < Fqdn > ]
[-FolderLogForManagedFoldersEnabled < $true | $false > ]
[-ForcedDatabaseMountAfter < Unlimited > ] [-Instance < MailboxServer > ]
[-JournalingLogForManagedFoldersEnabled < $true | $false > ] [-Locale
< MultiValuedProperty > ] [-LogDirectorySizeLimitForManagedFolders < Unlimited > ]
[-LogFileAgeLimitForManagedFolders < EnhancedTimeSpan > ]
[-LogFileSizeLimitForManagedFolders < Unlimited > ] [-LogPathForManagedFolders
< LocalLongFullPath > ] [-ManagedFolderAssistantSchedule < ScheduleInterval[] > ]
[-MAPIEncryptionRequired < $true | $false > ] [-MessageTrackingLogEnabled < $true
| $false > ] [-MessageTrackingLogMaxAge < EnhancedTimeSpan > ]
[-MessageTrackingLogMaxDirectorySize < Unlimited > ]
[-MessageTrackingLogMaxFileSize < Unlimited > ] [-MessageTrackingLogPath
< LocalLongFullPath > ] [-MessageTrackingLogSubjectLoggingEnabled < $true |
$false > ] [-RedundantMachines < MultiValuedProperty > ] [-ReplicationNetworks
< PrivateOnly | PrivateThenMixed | AllNetworks > ]
[-RetentionLogForManagedFoldersEnabled < $true | $false > ]
[-SubjectLogForManagedFoldersEnabled < $true | $false > ]
[-SubmissionServerOverrideList < MultiValuedProperty > ] [-WhatIf
[ < SwitchParameter > ]]
Some interesting parameters related to continuous clustering include:
??‘ AutoDatabaseMountDial
??‘ ForcedDatabaseAfterMount
??‘ ReplaceLocations
??‘ ReplicationNetworks
Part III: Working with PowerShell in a Production Environment
356
There are a number of scenarios when an administrator must take manual actions to bring the passive
node online with the Restore-StorageGroupCopy cmdlet.
Pages:
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503