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

Add-DfsrConnection

Windows Server 2012 R2 and Windows 8.1

Updated: October 17, 2013

Applies To: Windows 8.1, Windows PowerShell 4.0, Windows Server 2012 R2

Add-DfsrConnection

Creates a connection between members of a replication group.

Syntax

Parameter Set: Default
Add-DfsrConnection [-GroupName] <String[]> [-SourceComputerName] <String> [-DestinationComputerName] <String> [[-DisableConnection]] [[-DisableRDC]] [[-DisableCrossFileRDC]] [[-Description] <String> ] [[-MinimumRDCFileSizeInKB] <Int64> ] [[-CreateOneWay]] [[-DomainName] <String> ] [-Confirm] [-WhatIf] [ <CommonParameters>]




Detailed Description

The Add-DfsrConnection cmdlet creates a connection between members of a replication group.

DFS Replication connections are the logical partnerships between members in a replication group. The DFS Replication service uses the Remote Procedure Call (RPC) protocol to communicate between servers. You must create a connection between a pair of computers before the DFS Replication service can initiate replication. You should always create connections bidirectionally between two servers, even if you are using read-only replication. The exception to this case is if you create a ring topology between three or more servers, where all members transitively replicate to all partners, and where all servers are hosting only writable replicated folders.

This cmdlet does not support modifying connection bandwidth or schedules, which typically do not require changes.

Parameters

-CreateOneWay

Specifies that the DFSR service does not create a matching connection in the opposite direction between the two computers.

You do not typically need to specify this parameter. DFS Replication requires a fully-connected replication topology, which means that all servers have both an inbound and outbound connection between each of its direct partners, or through transitive replication. This is required even when you specify read-only replication by using the Set-DfsrMembership cmdlet and setting the ReadOnly parameter to $True.


Aliases

none

Required?

false

Position?

9

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Description<String>

Specifies a description for the connection.


Aliases

none

Required?

false

Position?

7

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-DestinationComputerName<String>

Specifies the name of the receiving computer. A receiving computer is also called an inbound or downstream computer.


Aliases

ReceivingMember,RMem

Required?

true

Position?

3

Default Value

none

Accept Pipeline Input?

True (ByPropertyName)

Accept Wildcard Characters?

false

-DisableConnection

Specifies that the DFSR service disables the connection.

You do not typically need to disable a connection. Specify this parameter to temporarily pause replication. You can also use the Suspend-DfsReplicationGroup cmdlet to halt replication between computers. You must enable a connection between the computers before the DFS Replication service can initiate replication.

Important: Specify this parameter instead of disabling a computer's membership in the replication group by using the Set-DfsrMembership cmdlet. Disabling and enabling a computer's membership will cause non-authoritative inbound replication.


Aliases

none

Required?

false

Position?

4

Default Value

false

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-DisableCrossFileRDC

Indicates that the DFSR service disables the cross-file similarity Remote Differential Compression (RDC) algorithm on this connection.

Cross-file RDC uses up to five existing previously replicated files on a volume to seed a new replicating file. Applying cross-file RDC over very low-bandwidth network connections with files that are very similar results in very large bandwidth savings and potentially large time savings. When you use cross-file RDC on very high-bandwidth network connections, cross-file RDC may add too much local processing time and negatively affect performance. In extremely large datasets (millions of files on a volume with a great deal of similarity), cross-file RDC may also negatively affect CPU and disk utilization. Consider disabling cross-file RDC during initial synchronization when you replicate over LANs and very high performance WANs. This setting is only supported on Windows Server 2012 R2 and later.


Aliases

none

Required?

false

Position?

6

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-DisableRDC

Indicates that the DFS Replication service creates the connection with Remote Differential Compression (RDC) disabled.

You do not typically need to specify this parameter when you use lower bandwidth, higher latency connections. Consider specifying this parameter if the connection is over a LAN or very high performance WAN connection. By default, RDC is enabled on DFS Replication connections.


Aliases

none

Required?

false

Position?

5

Default Value

false

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-DomainName<String>

Specifies the NetBIOS name or fully qualified domain name (FQDN) for the Active Directory Domain Service (AD DS) domain that contains the replication group. If you do not specify this parameter, the cmdlet uses the domain of the current user.


Aliases

none

Required?

false

Position?

101

Default Value

[Current Domain]

Accept Pipeline Input?

True (ByPropertyName)

Accept Wildcard Characters?

false

-GroupName<String[]>

Specifies an array of names of replication groups. You can use a comma separated list and the wildcard character (*).


Aliases

RG,RgName

Required?

true

Position?

1

Default Value

none

Accept Pipeline Input?

True (ByValue, ByPropertyName)

Accept Wildcard Characters?

true

-MinimumRDCFileSizeInKB<Int64>

Specifies the file size threshold, in kilobytes, for RDC to apply.

You do not typically need to specify this parameter when you use lower bandwidth/higher latency connections. Consider specifying this parameter only if the connection is over a LAN or a very high performance WAN connection. By default, any files equal to or greater than 64KB are chunked by RDC.


Aliases

none

Required?

false

Position?

8

Default Value

64

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-SourceComputerName<String>

Specifies the name of the sending computer. A sending computer is also called an outbound or upstream computer.


Aliases

SendingMember,SMem

Required?

true

Position?

2

Default Value

none

Accept Pipeline Input?

True (ByPropertyName)

Accept Wildcard Characters?

false

-Confirm

Prompts you for confirmation before running the cmdlet.


Required?

false

Position?

named

Default Value

false

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-WhatIf

Shows what would happen if the cmdlet runs. The cmdlet is not run.


Required?

false

Position?

named

Default Value

false

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

<CommonParameters>

This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see    about_CommonParameters.

Inputs

The input type is the type of the objects that you can pipe to the cmdlet.

  • Microsoft.DistributedFileSystemReplication.DfsReplicationGroup

Outputs

The output type is the type of the objects that the cmdlet emits.

  • Microsoft.DistributedFileSystemReplication.DfsrConnection

Examples

Example 1: Create a bidirectional connection between members of a replication group

This command creates a bidirectional replication connection between the computer named SRV01 and the computer named SRV02 in the replication group named RG24.


PS C:\> Add-DfsrConnection -GroupName "RG24" -SourceComputerName "SRV01" -DestinationComputerName "SRV02"
GroupName               : RG24
SourceComputerName      : SRV01
DestinationComputerName : SRV02
DomainName              : corp.contoso.com
Identifier              : c33eaaf1-9e50-4510-8484-68271bf93b25c33eaaf1-9e50-4510-8484-68271bf93b25
Enabled                 : True 
RdcEnabled              : True 
CrossFileRdcEnabled     : True
Description             :
MinimumRDCFileSizeInKB  : 64
State                   : Normal

GroupName               : RG24
SourceComputerName      : SRV02
DestinationComputerName : SRV01
DomainName              : corp.contoso.com
Identifier              : 97c3603a-7828-4403-adac-49575c9e5921
Enabled                 : True
RdcEnabled              : True
CrossFileRdcEnabled     : True
Description             : 
MinimumRDCFileSizeInKB  : 64
State                   : 

NormalGroupName         : RG24
SourceComputerName      : SRV02
DestinationComputerName : SRV01
DomainName              : corp.contoso.com
Identifier              : 97c3603a-7828-4403-adac-49575c9e5921
Enabled                 : True
RdcEnabled              : True
CrossFileRdcEnabled     : True
Description             : 
MinimumRDCFileSizeInKB  : 64
State                   : Normal

Example 2: Create a one-way connection between members of a replication group

This command creates a one-way replication connection from computer named SRV02 to the computer named SRV01 in the replication group named RG24. To create a one-way replication connection, you must run the cmdlet once in each direction between members of the replication group. DFS Replication supports one-way connections only for a ring topology configuration on three or more servers.


PS C:\> Add-DfsrConnection -GroupName "RG24" -SourceComputerName SRV02 -DestinationComputerName "SRV01" -CreateOneWay
GroupName               : rg24
SendingComputerName     : SRV02
ReceivingComputerName   : SRV01
DomainName              : corp.contoso.com
Identifier              : c33eaaf1-9e50-4510-8484-68271bf93b25
Enabled                 : True
RdcEnabled              : true
CrossFileRdcEnabled     : True
Description             : 
MinimumRDCFileSizeInKB  : 64
State                   : Normal

Example 3: Create a data distribution replication topology

This example creates a hub and spoke data distribution replication topology.


 

The first command uses the New-DfsReplicationGroup cmdlet to create a replication group object named Branch Office 1, and passes the object to the New-DfsReplicatedFolder cmdlet by using the pipe operator. The New-DfsReplicatedFolder cmdlet creates a replication folder object named Data Distribution 1, and passes the object to the Add-DfsrMember cmdlet by using the pipe operator. The Add-DfsrMember cmdlet adds the computers named SRV01, SRV02, and SRV03 to the replication group named Branch Office 1.


PS C:\> New-DfsReplicationGroup -GroupName "Branch Office 1" | New-DfsReplicatedFolder -FolderName "Data Distribution 1" | Add-DfsrMember -ComputerName "SRV01","SRV02","SRV03" | Format-Table dnsname,groupname -auto -wrap
DnsName                 GroupName
-------               ---------
SRV01.corp.contoso.com Branch Office 1
SRV02.corp.contoso.com Branch Office 1
SRV03.corp.contoso.com Branch Office 1

 

The second command creates a bidirectional replication connection between the computer named SRV01 and the computer named SRV02 in the replication group named Branch Office 1.


PS C:\> Add-DfsrConnection -GroupName "Branch Office 1" -SourceComputerName SRV01 -DestinationComputerName SRV02 | Format-Table *name -wrap -auto
GroupName       SourceComputerName DestinationComputerName
---------       ------------------ -----------------------
Branch Office 1 SRV01               SRV02
Branch Office 1 SRV02               SRV01

 

The third command creates a bidirectional replication connection between the computer named SRV01 and the computer named SRV03 in the replication group named Branch Office 1.


PS C:\> Add-DfsrConnection -GroupName "Branch Office 1" -SourceComputerName SRV01 -DestinationComputerName SRV03 | Format-Table *name -wrap -auto
GroupName       SourceComputerName DestinationComputerName
---------       ------------------ -----------------------
Branch Office 1 SRV01               SRV03
Branch Office 1 SRV03               SRV01

 

The fourth command uses the Set-DfsrMembership cmdlet to configure membership settings for the primary member of the replication group named Branch Office 1. The command specifies that the computer named SRV01 is the primary member of the group. The command sets an appropriate quota size of the staging folder instead of the lower default.


PS C:\> Set-DfsrMembership -GroupName "Branch Office 1" -FolderName "Data Distribution 1" -ContentPath c:\rf1 -ComputerName SRV01 -PrimaryMember $True -StagingPathQuotaInMB 16384 -Force | Format-Table *name,*path,primary* -auto -wrap
DomainName       GroupName       FolderName          ComputerName ContentPath StagingPath                PrimaryMember
----------       ---------       ----------          ------------ ----------- -----------                -------------
corp.contoso.com Branch Office 1 Data Distribution 1 SRV01         c:\rf1      c:\rf1\DfsrPrivate\Staging          True

 

The last command uses the Set-DfsrMembership cmdlet to configure membership settings for the members of the replication group named Branch Office 1. The command specifies that the computers named SRV02 and SRV03 are members of the group. The command sets an appropriate quota size of the staging folder instead of the lower default.


PS C:\> Set-DfsrMembership -GroupName "Branch Office 1" -FolderName "Data Distribution 1" -ContentPath c:\rf1 -ComputerName SRV02,SRV03 -StagingPathQuotaInMB 16384 -Force | Format-Table *name,*path,primary* -auto -wrap
DomainName       GroupName       FolderName          ComputerName ContentPath StagingPath                PrimaryMember
----------       ---------       ----------          ------------ ----------- -----------                -------------
corp.contoso.com Branch Office 1 Data Distribution 1 SRV02         c:\rf1      c:\rf1\DfsrPrivate\Staging         False
corp.contoso.com Branch Office 1 Data Distribution 1 SRV03         c:\rf1      c:\rf1\DfsrPrivate\Staging         False

Related topics

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