Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Update-MailboxDatabaseCopy

 

Applies to: Exchange Server 2013

Topic Last Modified: 2013-01-14

Use the Update-MailboxDatabaseCopy cmdlet to seed or reseed a mailbox database copy.

For information about the parameter sets in the Syntax section below, see Syntax.

Update-MailboxDatabaseCopy -Identity <DatabaseCopyIdParameter> [-BeginSeed <SwitchParameter>] [-CatalogOnly <SwitchParameter>] [-DatabaseOnly <SwitchParameter>] [-DeleteExistingFiles <SwitchParameter>] [-Force <SwitchParameter>] [-ManualResume <SwitchParameter>] [-Network <DatabaseAvailabilityGroupNetworkIdParameter>] [-NetworkCompressionOverride <UseDagDefault | Off | On>] [-NetworkEncryptionOverride <UseDagDefault | Off | On>] [-SafeDeleteExistingFiles <SwitchParameter>] [-SourceServer <ServerIdParameter>] <COMMON PARAMETERS>
Update-MailboxDatabaseCopy -CancelSeed <SwitchParameter> -Identity <DatabaseCopyIdParameter> <COMMON PARAMETERS>
Update-MailboxDatabaseCopy -Server <MailboxServerIdParameter> [-CatalogOnly <SwitchParameter>] [-DatabaseOnly <SwitchParameter>] [-DeleteExistingFiles <SwitchParameter>] [-ManualResume <SwitchParameter>] [-MaximumSeedsInParallel <Int32>] [-NetworkCompressionOverride <UseDagDefault | Off | On>] [-NetworkEncryptionOverride <UseDagDefault | Off | On>] [-SafeDeleteExistingFiles <SwitchParameter>] <COMMON PARAMETERS>
COMMON PARAMETERS: [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-WhatIf [<SwitchParameter>]]

This example seeds a copy of the database DB1 on the Mailbox server MBX1.

Update-MailboxDatabaseCopy -Identity DB1\MBX1

This example seeds a copy of the database DB1 on the Mailbox server MBX1 using MBX2 as the source Mailbox server for the seed.

Update-MailboxDatabaseCopy -Identity DB1\MBX1 -SourceServer MBX2

This example seeds a copy of the database DB1 on the Mailbox server MBX1 without seeding the content index catalog.

Update-MailboxDatabaseCopy -Identity DB1\MBX1 -DatabaseOnly 

This example seeds the content index catalog for the copy of the database DB1 on the Mailbox server MBX1 without seeding the database file.

Update-MailboxDatabaseCopy -Identity DB1\MBX1 -CatalogOnly

This example performs a full server reseed of all of the databases on the Mailbox server MBX1.

Update-MailboxDatabaseCopy -Server MBX1

Seeding is the process in which a copy of a mailbox database is added to another Mailbox server. This becomes the database copy into which copied log files and data are replayed.

The Update-MailboxDatabaseCopy cmdlet can also be used to seed a content index catalog for a mailbox database copy.

You must suspend a database copy before you can update it using the Update-MailboxDatabaseCopy cmdlet. For detailed steps about how to suspend a database copy, see Suspend or Resume a Mailbox Database Copy.

You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Database availability groups" entry in the High Availability and Site Resilience Permissions topic.

 

Parameter Required Type Description

CancelSeed

Required

System.Management.Automation.SwitchParameter

The CancelSeed switch specifies whether to cancel an in-progress seeding operation.

Identity

Required

Microsoft.Exchange.Configuration.Tasks.DatabaseCopyIdParameter

The Identity parameter specifies the name or GUID of the mailbox database whose copy is being seeded.

Server

Required

Microsoft.Exchange.Configuration.Tasks.MailboxServerIdParameter

The Server parameter is used as part of a full server reseed operation. It can be used with the MaximumSeedsInParallel parameter to start reseeds of database copies in parallel across the specified server in batches of up to the value of the MaximumSeedsInParallel parameter copies at a time.

BeginSeed

Optional

System.Management.Automation.SwitchParameter

The BeginSeed parameter is useful for scripting reseeds, because with this parameter, the task asynchronously starts the seeding operation and then exits the cmdlet.

CatalogOnly

Optional

System.Management.Automation.SwitchParameter

The CatalogOnly parameter specifies that only the content index catalog for the database copy should be seeded.

Confirm

Optional

System.Management.Automation.SwitchParameter

The Confirm switch causes the command to pause processing and requires you to acknowledge what the command will do before processing continues. You don't have to specify a value with the Confirm switch.

DatabaseOnly

Optional

System.Management.Automation.SwitchParameter

The DatabaseOnly parameter specifies that only the database copy should be seeded. The content index catalog isn't seeded.

DeleteExistingFiles

Optional

System.Management.Automation.SwitchParameter

The DeleteExistingFiles switch specifies whether to remove the existing log files at the target location. This parameter removes only the files that it checks for and fails if other files are present. No action is taken on other files at the target location. Therefore, if database-related files are present, you must manually remove them.

DomainController

Optional

Microsoft.Exchange.Data.Fqdn

The DomainController parameter specifies the fully qualified domain name (FQDN) of the domain controller that writes this configuration change to Active Directory.

Force

Optional

System.Management.Automation.SwitchParameter

The Force switch specifies whether to suppress warning or confirmation messages. This switch can be used when the task is run programmatically and prompting for administrative input is inappropriate. If the Force switch isn't provided in the command, you're prompted for administrative input. You don't have to specify a value with this parameter.

ManualResume

Optional

System.Management.Automation.SwitchParameter

The ManualResume switch specifies whether to automatically resume replication on the database copy. With this parameter, you can manually resume replication to the database copy.

MaximumSeedsInParallel

Optional

System.Int32

The MaximumSeedsInParallel parameter is used with the Server parameter to specify the maximum number of parallel seeding operations that should occur across the specified server during a full server reseed operation. The default value is 10.

Network

Optional

Microsoft.Exchange.Configuration.Tasks.DatabaseAvailabilityGroupNetworkIdParameter

The Network parameter specifies which DAG network should be used for seeding.

NetworkCompressionOverride

Optional

Microsoft.Exchange.Management.SystemConfigurationTasks.UseDagDefaultOnOff

The NetworkCompressionOverride parameter specifies whether to override the current DAG network compression settings.

NetworkEncryptionOverride

Optional

Microsoft.Exchange.Management.SystemConfigurationTasks.UseDagDefaultOnOff

The NetworkEncryptionOverride parameter specifies whether to override the current DAG encryption settings.

SafeDeleteExistingFiles

Optional

System.Management.Automation.SwitchParameter

The SafeDeleteExistingFiles parameter is used to perform a seeding operation with a single copy redundancy pre-check prior to the seed. Because this parameter includes the redundancy safety check, it requires a lower level of permissions than the DeleteExistingFiles parameter, enabling a limited permission administrator to perform the seeding operation.

SourceServer

Optional

Microsoft.Exchange.Configuration.Tasks.ServerIdParameter

The SourceServer parameter specifies the name of a Mailbox server with a passive copy of the mailbox database to be used as the source for the seed operation.

WhatIf

Optional

System.Management.Automation.SwitchParameter

The WhatIf switch instructs the command to simulate the actions that it would take on the object. By using the WhatIf switch, you can view what changes would occur without having to apply any of those changes. You don't have to specify a value with the WhatIf switch.

To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn’t accept input data.

To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types. If the Output Type field is blank, the cmdlet doesn’t return data.

 
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.