Create a Storage Replica (SR) destination server with Windows Server 2016 on an existing VNET
This template will create a Storage Replica destination copy on Windows Server 2016 in an existing VNET and Active Directory environment.
This template creates the following resources by default:
- A Premium Storage Account for storing VM disks for each storage node
- A Windows Server 2016 server for the Storage Replica destination copy
- A single disk Storage Pool for both the log and data volumes
- An SR Partnership with an existing Windows Server 2016 server
This template assumes the following prerequisites on the Storage Replica source:
- The source log and data volumes are formatted as GPT, not MBR
- The source log volume is a minimum 9GB
To deploy the required Azure VNET and Active Directory infrastructure, if not already in place, you may use this template to deploy the prerequisite infrastructure.
Click the button below to deploy from the portal:
The default settings for both log and data volumes are to deploy using premium storage, which is strongly recommended for performance. When using Premium Storage, be sure to select a VM size (DS-series, GS-series) that supports Premium Storage.
The default settings deploy 2 data disks, but should be increased to account for the total capacity needed for both the log and data volumes. When increasing # of data disks, be sure to select a VM size that can support the # of data disks you specify.
The default settings for compute require that you have at least 2 cores of free quota to deploy.
The images used to create this deployment are
- Windows Server 2016 Datacenter Edition - Latest Image
To successfully deploy this template, be sure that the subnet to which the Storage Replica destination is being deployed already exists on the specified Azure virtual network, AND this subnet should be routable to BOTH the Storage Replica source and an Active Directory domain controller in the trusted Active Directory Domain.
Deploying Sample Templates
You can deploy these samples directly through the Azure Portal or by using the scripts supplied in the root of the repo.
To deploy the sample using the Azure Portal, click the Deploy to Azure button found above.
To deploy the sample via the command line (using Azure PowerShell or the Azure CLI) you can use the scripts.
Simple execute the script and pass in the folder name of the sample you want to deploy. For example:
.\Deploy-AzureResourceGroup.ps1 -ResourceGroupLocation 'eastus' -ArtifactsStagingDirectory '[foldername]'
azure-group-deploy.sh -a [foldername] -l eastus -u
If the sample has artifacts that need to be "staged" for deployment (Configuration Scripts, Nested Templates, DSC Packages) then set the upload switch on the command. You can optionally specify a storage account to use, if so the storage account must already exist within the subscription. If you don't want to specify a storage account one will be created by the script or reused if it already exists (think of this as "temp" storage for AzureRM).
.\Deploy-AzureResourceGroup.ps1 -ResourceGroupLocation 'eastus' -ArtifactsStagingDirectory '301-storage-replica-md' -UploadArtifacts
azure-group-deploy.sh -a '301-storage-replica-md' -l eastus -u
ha, storage spaces, storage replica, replica, windows server 2016, ws2016