NAME

Add-DcsReplicationPartnerGroup

SYNOPSIS

Partners one server group to another server group for the purpose of performing replications.

SYNTAX

Add-DcsReplicationPartnerGroup -Server <String> -LocalUserName <String> -LocalPassword <String> -RemoteUserName <String> -RemotePassword <String> [ -Connection <String> ] [ -PipelineVariable <String> ]

Add-DcsReplicationPartnerGroup -Server <String> -LocalCredential <PSCredential> -RemoteCredential <PSCredential> [ -Connection <String> ] [ -PipelineVariable <String> ]

DESCRIPTION

Partners one server group to another server group in order to perform replications, see Add-DcsReplication. A replication buffer must be created, see Set-DcsReplicationBufferFolder.

PARAMETERS

-Server<String>: Computer name or ID of one of the servers in the remote destination group. The computer name must be unique or the name must be fully qualified. The specified server will be used for communications between local (source) and remote (destination) server groups.; Required: true; Position: 1; Default value:; Accept pipeline input: false; Accept wildcard characters: false
-LocalUserName<String>: User name of the account used to connect to the local (source) server group. User names must match Windows user accounts and must reside on all servers in the local server group. Credentials can be domain-wide or local (workgroup). If credentials are domain-wide, include the domain with the name for example: DOMAIN\user name.) Name resolution is required between local and remote groups.; Required: true; Position: 2; Default value:; Accept pipeline input: false; Accept wildcard characters: false
-LocalPassword<String>: Login password that corresponds to the local user name.; Required: true; Position: 3; Default value:; Accept pipeline input: false; Accept wildcard characters: false
-RemoteUserName<String>: User name of the account used to connect to the remote (destination) server group. User names must match Windows user accounts and must reside on all servers in the remote server group. Credentials can be domain-wide or local (workgroup). If credentials are domain-wide, include the domain with the name for example: DOMAIN\user name.) Name resolution is required between local and remote groups.; Required: true; Position: 4; Default value:; Accept pipeline input: false; Accept wildcard characters: false
-RemotePassword<String>: Login password that corresponds to the remote user name.; Required: true; Position: 5; Default value:; Accept pipeline input: false; Accept wildcard characters: false
-Connection<String>: Alias of the connection to the server group. If not specified, the default connection will be used.; Required: false; Position: named; Default value:; Accept pipeline input: false; Accept wildcard characters: false
-PipelineVariable<String>: Required: false; Position: named; Default value:; Accept pipeline input: false; Accept wildcard characters: false
-LocalCredential<PSCredential>: The PSCredential object containing user name and password for the local server group. This object can be obtained by invoking the Windows PowerShell cmdlet Get-Credential, see Example 2. In this manner, credentials can be passed through the object instead of typing the credentials.; Required: true; Position: 2; Default value:; Accept pipeline input: false; Accept wildcard characters: false
-RemoteCredential<PSCredential>: The PSCredential object containing user name and password for the remote server group. This object can be obtained by invoking the Windows PowerShell cmdlet Get-Credential, see Example 2. In this manner, credentials can be passed through the object instead of typing the credentials.; Required: true; Position: 3; Default value:; Accept pipeline input: false; Accept wildcard characters: false

INPUTS

OUTPUTS

PartnershipData : Object that identifies and describes the replication partner group.

NOTES

Also see Add-DcsReplication, Set-DcsReplicationBufferFolder, Remove-DcsReplicationPartnerGroup, Get-DcsReplicationPartnerGroup.

EXAMPLES

-------------- Example 1 Adds a replication partner group for replication --------------

Add-DcsReplicationPartnerGroup -Server SSV3 -LocalUserName administrator -LocalPassword Adminpw! -RemoteUserName administrator -RemotePassword Adminpw!

Adds a replication partner group to the current server group for replication purposes. In this example, the partner group contains a server named "SSV3". The User Names and Passwords are "administrator" and "Adminpw!" on both local and remote servers.

GroupId	:	091705db-3bfd-4c3a-9d58-8455fe6628ef
HostAddresses	:	{SSV3.datacoresoftware.com}
IncomingCredentials	:	DataCore.Executive.ConnectionCredentials
OutgoingCredentials	:	DataCore.Executive.ConnectionCredentials
Connected	:	True
EnableCompression	:	True
Id	:	285ea682-2b07-4020-8f52-b87441579783
Caption	:	ControllerProxy
ExtendedCaption	:	ControllerProxy

-------------- Example 2 Adds a replication partner group by passing the PSCredential objects --------------

$localCred = Get-Credential
$remoteCred = Get-Credential
Add-DcsReplicationPartnerGroup -Server SSV3.datacoresoftware.com -LocalCredential $localCred -RemoteCredential $remoteCred

The Windows PowerShell cmdlet Get-Credential is invoked to collect the credentials for the local and remote server groups. When Get-Credential is invoked a dialog box opens and the user name and password can be entered in a secure manner. The local credentials are saved to the variable $localCred and the remote credentials are saved to the variable $remoteCred.
The cmdlet Add-DcsReplicationPartnerGroup is invoked to create a replication partnership between the local and remote server groups. The remote server is named "SSV3.datacoresoftware.com" and is identified by the parameter Server. Local credentials are passed using $localCred as the value for the parameter LocalCredential. Remote credentials are passed using $remoteCred as the value for the parameter RemoteCredential.

$remoteCred = Get-Credential