COMMAND EVERYTHING.
Creates a replication partnership between two replication groups.
Microsoft StorageReplica reference: Creates a replication partnership between two replication groups. The syntax and selected example below are adapted from the pinned Windows Server 2025 reference. Module availability, target configuration and delegated permissions determine whether it can run in your environment. Documentation and parameter text: Microsoft, CC BY 4.0; formatting adapted by Cmdlet World. No execution testing is claimed.
Use an account with the target resource permissions documented for New-SRPartnership. Modifying administrative cmdlets may require elevation or delegated administration. This catalog does not assert that ordinary users can execute the command.
Windows / StorageReplica · Windows Server 2025 documentation; feature/module prerequisites apply
-AsJob- Runs the cmdlet as a background job. Use this parameter to run commands that take a long time to complete.
-AsyncRPO- Specifies the maximum difference in time, in seconds, that data for an asynchronous partnership can be different between source and destination. This is a Recovery Point Objective. The minimum value is 30 seconds. The default value is 5 minutes. After exceeding this time, the source server alerts the Health Service on clusters. It logs event 1239 in the Storage Replica Admin event log channel. If the RPO time is lower than the configured time, event 1240 is logged.
-CimSession- Runs the cmdlet in a remote session or on a remote computer. Enter a computer name or a session object, such as the output of a New-CimSession or Get-CimSession cmdlet. The default is the current session on the local computer.
-DestinationComputerName (required)- Specifies a single replica host computer NetBIOS name or fully qualified domain name (FQDN) of the destination computer.
-DestinationLogVolumeName (required)- Specifies a drive letter, mount point path, or volume GUID where Storage Replication creates destination replication logs. The volume must contain an NTFS-formatted volume or ReFS-formatted volume. The path must exist. The path cannot be a mapped drive or UNC path. Storage Replication creates logs in the System Volume Information folder.
-DestinationRGDescription- Specifies a description for the destination replication group.
-DestinationRGName (required)- Specifies a name for the destination replication group.
-DestinationVolumeName (required)- Specifies an array of drive letters or mount point paths of partitions for the replica. The volumes must exist. The volumes cannot be mapped drives or UNC paths. You can omit the colon symbol when you specify drive letters. This is an ordered list. The order of volumes determines the order of replication. For instance, to replicate the F: and H: drives on one server to the F: and H: drives of another server, specify the following values: -SourceVolumeName "F:","H:" -DestinationVolumeName "F:","H:" To replicate F: to H: instead, specify the following values: -SourceVolumeName "F:","H:" -DestinationVolumeName "H:","F:" We do not recommend replicating different drive letters or mount point paths. This practice can cause application failures because of stored settings after a failover occurs.
-EnableCompression- Indicates that the connections in this partnership should use SMB compression for data transfer.
-EnableConsistencyGroups- Indicates that consistency groups are enabled for the replication group that contains multiple volumes. Consistency groups provide write ordering. This can be important, for example, for replication of application data on multiple volumes. If you enable consistency groups, it may decrease replication and write Input/Output performance.
-EnableEncryption- Indicates that this partnership should encrypt connections by using SMB AES-128-GCM. Enabling encryption can protect Storage Replica block transfers from man-in-the-middle interception or reading. Enabling encryption decreases replication and write Input/Output performance.
-Force- Forces the command to run without asking for user confirmation.
-LogSizeInBytes- Specifies the aggregate size of log files on each server in the replication group for the volumes that are associated with this replication group. The minimum size 512MB. You can specify a value by using the Windows PowerShell byte conversion capability, such as 4GB or 3200MB. A value that is too small may cause decreased replication performance or increased recovery time after an interruption between computers.
-PreventReplication- Indicates that this cmdlet prevent replication from starting immediately. By default, replication starts automatically at the time that you create the partnership. To start replication later, use the Sync-SRGroup cmdlet.
-ReplicationMode- Specifies the desired mode of replication for this source and destination pair. The acceptable values for this parameter are: - Synchronous or 1. The synchronous mode requires all writes to commit on the destination server and on the source server, which guarantees data integrity between computers. - Asynchronous or 2. The asynchronous mode writes to the source server without waiting for the destination server, which allows for replication over high latency, geographic networks. The default value is synchronous. The default asynchronous recovery point alert time is 5 minutes. You can modify it by using the Set-SRPartnership cmdlet. The alert time has no effect on replication behavior, only on reporting.
-Seeded- Indicates that the destination server contains a seeded copy of the data from the source server. Seeded data is defined as a copy of data from the source server that has a high similarity, such as mostly empty blocks, restoring a recent backup, or shipping cloned copies of disks to the destination server. Seeding is most effective when using a previous copy of the storage, such as a split mirror or previously replicated drives, or when the storage is mostly empty and was always empty, such as a recently initialized drive with a newly formatted volume. Seeding is somewhat effective with data that came from a backup restore or a complete tree copy of data or from copies of very large files. Seeding is least effective when copying large numbers of small files from some random locations to some other random locations. Storage Replica automatically uses seeding when it restarts replication after a long outage that wrapped the logs.
-SourceComputerName- Specifies a single replica host computer NetBIOS name or FQDN of the source computer. The default value is the local computer.
-SourceLogVolumeName (required)- Specifies a drive letter, mount point path, or volume GUID where Storage Replication creates source replication logs. The volume must contain an NTFS-formatted volume or ReFS-formatted volume. The path must exist. The path cannot be a mapped drive or UNC path. Storage Replication creates logs in the System Volume Information folder.
-SourceRGDescription- Specifies a description for the source replication group.
-SourceRGName (required)- Specifies the name of the source replication group.
-SourceVolumeName (required)- Specifies an array of drive letters or mount point paths of partitions for the replica. The volumes must exist. The volumes cannot be mapped drives or UNC paths. This is an ordered list. The order of volumes determines the order of replication. For more information, see the DestinationVolumeName parameter.
-ThrottleLimit- Specifies the maximum number of concurrent operations that can be established to run the cmdlet. If this parameter is omitted or a value of 0 is entered, then Windows PowerShell® calculates an optimum throttle limit for the cmdlet based on the number of CIM cmdlets that are running on the computer. The throttle limit applies only to the current cmdlet, not to the session or to the computer.
Windows with the StorageReplica module and the Windows feature or management tools that provide it. Confirm target connectivity and version compatibility using the linked Microsoft reference.
This cmdlet changes system state. Review every target and parameter in the official reference, test outside production, and prepare an appropriate backup or rollback. Do not execute the example automatically.