Netherlands: Software

Introductie Windows Server 2016

Issue link:

Contents of this Issue


Page 78 of 173

70 C H A P T E R 3 | Storage Figure 3-7: Typical architecture used for implementing server-to-server replication In the server-to-server and cluster-to-cluster scenario, there is no graphical interface and no automatic failover management—all administration is manual and human-driven through the Windows PowerShell StorageReplica module. To ensure ease of provisioning, Storage Replica implements a simple system for configuring replication with a single command when possible. The Windows PowerShell StorageReplica module contains the following commands in Windows Server 2016 Technical Preview: Get-Command -Module StorageReplica | FT –Auto CommandType Name Version Source ----------- ---- ------- ------ Function Get-SRGroup 1.0 StorageReplica Function Get-SRPartnership 1.0 StorageReplica Function New-SRGroup 1.0 StorageReplica Function New-SRPartnership 1.0 StorageReplica Function Remove-SRGroup 1.0 StorageReplica Function Remove-SRPartnership 1.0 StorageReplica Function Set-SRGroup 1.0 StorageReplica Function Set-SRPartnership 1.0 StorageReplica Function Suspend-SRGroup 1.0 StorageReplica Function Sync-SRGroup 1.0 StorageReplica Function Test-SRTopology 1.0 StorageReplica Configuring replication is as simple as providing the following information: New-SRPartnership -SourceComputerName np-sr-srv05 -SourceRGName rg01 -SourceVolumeName g: -SourceLogVolumeName h: -DestinationComputerName np-sr-srv06 -DestinationRGName rg02 -DestinationVolumeName g: -DestinationLogVolumeName h: -LogSizeInBytes 16GB There are many options for the New-SRPartnership cmdlet, including creating asynchronous replication. You can also create replication in a more granular fashion by running New-SRGroup on each server and tying them together by using New-SRPartnership. You can add additional volumes to a replication group by using Set-SRGroup, and you can run more than one replication group on a server at a time. Storage Replica will include more cmdlets before the final release, including a cmdlet to determine how well replication will perform between two servers over a given network, how to optimally size the replication logs, and what the current write I/O load is on a server you propose for replication—all without the need to install or configure Storage Replica beforehand. Storage Replica in Windows Server 2016 Technical Preview The following are some of the key things to know concerning Storage Replica as of the Windows Server 2016 Technical Preview release: Network bandwidth and latency with fastest storage There are physical limitations to synchronous replication. Because Storage Replica implements an I/O filtering mechanism using logs and requiring network roundtrips, synchronous replication is likely to make application writes

Articles in this issue

Archives of this issue

view archives of Netherlands: Software - Introductie Windows Server 2016