![]() ![]() To do so, use Express Route, a Site-to-Site VPN gateway connection, or install VPN software in your Azure VMs to connect them with your on-premises network. ![]() If you're replicating between on-premises servers and Azure VMs, you must create a network link between the on-premises servers and the Azure VMs. Asynchronous replication doesn't have a latency recommendation. A network between servers with enough bandwidth to contain your IO write workload and an average of =5ms round trip latency, for synchronous replication.Appropriate firewall and router rules to allow ICMP, SMB (port 445, plus 5445 for SMB Direct) and WS-MAN (port 5985) bi-directional traffic between all nodes.At least one ethernet/TCP connection on each server for synchronous replication, but preferably RDMA.The physical storage must have the same sector sizes on all the log disks. The physical storage must have the same sector sizes on all the data disks. Each set of storage must allow creation of at least two virtual disks, one for replicated data and one for logs.You will make each storage set available only to each of the servers, with no shared access. The storage should contain a mix of HDD and SSD media. Two sets of storage, using SAS JBODs, fibre channel SAN, iSCSI target, or local SCSI/SATA storage.If you're running Windows Server 2019, you can instead use Standard Edition if you're OK replicating only a single volume up to 2 TB in size. Two servers running Windows Server 2019 or Windows Server 2016, Datacenter Edition.Active Directory Domain Services forest (doesn't need to run Windows Server 2016). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |