存储副本概述Storage Replica overview

适用于:Windows Server(半年频道)、Windows Server 2016Applies to: Windows Server (Semi-Annual Channel), Windows Server 2016

存储副本 (Storage Replica) 是一种 Windows Server 技术,它允许针对灾难恢复在服务器或群集之间进行卷的复制。Storage Replica is Windows Server technology that enables replication of volumes between servers or clusters for disaster recovery. 它还允许你创建跨越两个站点的拉伸故障转移群集,同时保持所有节点同步。It also enables you to create stretch failover clusters that span two sites, with all nodes staying in sync.

存储副本支持同步和异步复制:Storage Replica supports synchronous and asynchronous replication:

  • 同步复制映射低延迟网络站点中的数据和在崩溃时保持一致的卷,以确保在故障发生过程中文件系统级别的数据损失为零。Synchronous replication mirrors data within a low-latency network site with crash-consistent volumes to ensure zero data loss at the file-system level during a failure.
  • 异步复制通过较高延迟网络链接映射都市范围外的站点之间的数据,但不保证在出现故障时两个站点具有完全相同的数据副本。Asynchronous replication mirrors data across sites beyond metropolitan ranges over network links with higher latencies, but without a guarantee that both sites have identical copies of the data at the time of a failure.

本指南概述了业务将如何从这一新功能和存储副本支持的不同复制方案中获益。This guide outlines how your business can benefit from this new functionality and the different replication scenarios that are supported by Storage Replica. 它假定你熟悉 Windows Server、故障转移群集、文件服务器和 Hyper-V,可进行基本管理。It assumes that you have a previous working knowledge of Windows Server, Failover Clustering, File Servers, and Hyper-V, to include basic administration.

为什么要使用存储副本?Why use Storage Replica?

存储副本在 Windows Server 2016 Datacenter Edition 中提供新的灾难恢复和预防准备功能。Storage Replica offers new disaster recovery and preparedness capabilities in Windows Server 2016 Datacenter Edition. Windows Server 首次做到了零数据丢失,免除你的后顾之忧,能够同步保护不同机架、楼层、建筑物、园区、县和城市的数据。For the first time, Windows Server offers the peace of mind of zero data loss, with the ability to synchronously protect data on different racks, floors, buildings, campuses, counties, and cities. 灾难发生后,所有数据将存在于其他地方,不会有任何丢失的情况的出现。After a disaster strikes, all data will exist elsewhere without any possibility of loss. 这同样适用灾难发生;在授予片刻警告时,存储副本会在在灾难发生前切换到安全位置 - 再次声明,不会有数据丢失。The same applies before a disaster strikes; Storage Replica offers you the ability to switch workloads to safe locations prior to catastrophes when granted a few moments warning - again, with no data loss.

存储副本允许更有效地利用多个数据中心。Storage Replica allows more efficient use of multiple datacenters. 通过拉伸或复制群集,工作负荷可在多个数据中心中运行,以使本地邻近用户和应用程序能够更加快速地对其进行访问,以及更好地分布负载和使用计算资源。By stretching clusters or replicating clusters, workloads can be run in multiple datacenters for quicker data access by local proximity users and applications, as well as better load distribution and use of compute resources. 如果灾难导致一个数据中心脱机,可以将其典型的工作负载暂时移动到另一个站点。If a disaster takes one datacenter offline, you can move its typical workloads to the other site temporarily.

存储副本可能会允许取消配置作为低端灾难恢复解决方案的现有文件复制系统,如 DFSR。Storage Replica may allow you to decommission existing file replication systems such as DFS Replication that were pressed into duty as low-end disaster recovery solutions. DFS 复制在极低带宽网络上运行非常出色,同时其延迟时间很高 - 通常以小时或天为单位。While DFS Replication works well over extremely low bandwidth networks, its latency is very high - often measured in hours or days. 这是由文件关闭需求和防止网络拥塞的人为限制所引起。This is caused by its requirement for files to close and its artificial throttles meant to prevent network congestion. 正因具有这些设计特性,因此最不可能复制 DFS 复制副本中最新和最热门的文件。With those design characteristics, the newest and hottest files in a DFS Replication replica are the least likely to replicate. 存储副本在文件级别以下运行,并且没有这些限制。Storage Replica operates below the file level and has none of these restrictions.

存储副本还支持适用于更长范围和更高延迟网络的异步复制。Storage Replica also supports asynchronous replication for longer ranges and higher latency networks. 因为它不是基于检查点,而是持续复制,更改的增量将倾向于比基于快照的产品要低得多。Because it is not checkpoint-based, and instead continuously replicates, the delta of changes will tend to be far lower than snapshot-based products. 此外,存储副本在分区层进行操作,因此它将复制由 Windows Server 或备份软件创建的所有 VSS 快照;这允许将应用程序一致的数据快照用于时间点恢复,尤其是异步复制的非结构化用户数据。Furthermore, Storage Replica operates at the partition layer and therefore replicates all VSS snapshots created by Windows Server or backup software; this allows use of application-consistent data snapshots for point in time recovery, especially unstructured user data replicated asynchronously.

支持的配置Supported configurations

使用本指南和 Windows Server 2016 Datacenter Edition,可以在拉伸群集中、在群集到群集配置之间和服务器到服务器配置之间部署存储复制(请参见图 1-3)。Using this guide and Windows Server 2016 Datacenter Edition, you can deploy storage replication in a stretch cluster, between cluster-to-cluster, and in server-to-server configurations (see Figures 1-3).

拉伸群集允许在单个群集中配置计算机和存储,其中某些节点共享一组非对称存储,而另一些节点共享另一组,然后通过站点感知进行同步或异步复制。Stretch Cluster allows configuration of computers and storage in a single cluster, where some nodes share one set of asymmetric storage and some nodes share another, then synchronously or asynchronously replicate with site awareness. 此方案可以利用具有共享的 SAS 存储的存储空间、连接了 SAN 和 iSCSI 的 LUN。This scenario can utilize Storage Spaces with shared SAS storage, SAN and iSCSI-attached LUNs. 它通过 PowerShell 和故障转移群集管理器图形工具进行管理,并允许自动化工作负载故障转移。It is managed with PowerShell and the Failover Cluster Manager graphical tool, and allows for automated workload failover.

显示使用存储副本将 New York 中的两个群集节点的存储复制为 New Jersey 中的两个节点的关系图

图 1:在拉伸群集中使用存储副本的存储复制FIGURE 1: Storage replication in a stretch cluster using Storage Replica

群集到群集允许两个独立群集之间的复制,其中一个群集与另一个群集进行同步复制或异步复制。Cluster to Cluster allows replication between two separate clusters, where one cluster synchronously or asynchronously replicates with another cluster. 此方案可以利用存储空间直通、具有共享的 SAS 存储的存储空间以及连接了 SAN 和 iSCSI 的 LUN。This scenario can utilize Storage Spaces Direct, Storage Spaces with shared SAS storage, SAN and iSCSI-attached LUNs. 它通过 PowerShell 进行管理,并且需要手动干预故障转移。It is managed with PowerShell and requires manual intervention for failover. 已计划支持此方案的 Azure Site Recovery。Support for Azure Site Recovery of this scenario is scheduled.

显示使用存储副本将 Los Angeles 中的群集的存储复制为 Las Vegas 中的不同的群集的关系图

图 2:使用存储副本的群集到群集存储复制FIGURE 2: Cluster-to-cluster storage replication using Storage Replica

服务器到服务器允许使用具有共享的 SAS 存储的存储空间、连接了 SAN 和 iSCSI 的 LUN 以及本地驱动器,在两个独立服务器之间进行同步和异步复制。Server to server allows synchronous and asynchronous replication between two standalone servers, using Storage Spaces with shared SAS storage, SAN and iSCSI-attached LUNs, and local drives. 它通过 PowerShell 和服务器管理器工具进行管理,并且需要手动干预故障转移。It is managed with PowerShell and the Server Manager Tool, and requires manual intervention for failover.

显示使用构建 5 中的服务器复制构建 9 中的服务器的关系图

图 3:使用存储副本的服务器到服务器存储复制FIGURE 3: Server-to-server storage replication using Storage Replica

备注

还可以在一台计算机上使用四个单独的卷配置服务器到自我复制。You can also configure server-to-self replication, using four separate volumes on one computer. 但是,本指南不涉及这种情况。However, this guide does not cover this scenario.

存储副本功能 Storage Replica Features

  • 零数据丢失、块级复制Zero data loss, block-level replication. 使用同步复制,不可能丢失数据。With synchronous replication, there is no possibility of data loss. 使用块级复制,不可能锁定文件。With block-level replication, there is no possibility of file locking.

  • 简单部署和管理Simple deployment and management. 存储副本具有易于使用的设计要求。Storage Replica has a design mandate for ease of use. 只需要单个 PowerShell 命令即可创建两个服务器之间的复制合作关系。Creation of a replication partnership between two servers requires only a single PowerShell command. 拉伸群集的部署在熟悉的故障转移群集管理器工具中使用直观向导。Deployment of stretch clusters uses intuitive wizard in the familiar Failover Cluster Manager tool.

  • 来宾和主机Guest and host. 存储副本的所有功能均将在基于虚拟化来宾和主机的部署中公开。All capabilities of Storage Replica are exposed in both virtualized guest and host-based deployments. 这意味着只要在来宾中使用 Windows Server 2016 Datacenter Edition,即使数据卷在非 Windows 虚拟化平台或在公有云中运行,来宾也可以复制其数据卷。This means guests can replicate their data volumes even if running on non-Windows virtualization platforms or in public clouds, as long as using Windows Server 2016 Datacenter Edition in the guest.

  • 基于 SMB3SMB3-based. 存储副本使用 SMB 3 这一公认的成熟技术,该技术在 Windows Server 2012 中首次推出。Storage Replica uses the proven and mature technology of SMB 3, first released in Windows Server 2012. 这意味着 SMB 的所有高级特性(如RoCE、iWARP 和 InfiniBand RDMA 网卡上的多通道和 SMB 直通支持)均可用于存储副本。This means all of SMB's advanced characteristics - such as multichannel and SMB direct support on RoCE, iWARP, and InfiniBand RDMA network cards - are available to Storage Replica.

  • 安全Security. 与许多供应商的产品不同,存储副本由行业领先的安全技术提供支持。Unlike many vendor's products, Storage Replica has industry-leading security technology baked in. 这包括数据包签名、AES-128-GCM 完整数据加密、对 Intel AES-NI 加密加速的支持和完整预身份验证中间人攻击防护。This includes packet signing, AES-128-GCM full data encryption, support for Intel AES-NI encryption acceleration, and pre-authentication integrity man-in-the-middle attack prevention. 存储副本利用 Kerberos AES256 进行节点之间所有的身份验证。Storage Replica utilizes Kerberos AES256 for all authentication between nodes.

  • 高性能初始同步。存储副本支持种子初始同步,其中,数据的一个子集已存在于较旧的副本、备份或随附驱动器上的目标中。High performance initial sync. Storage Replica supports seeded initial sync, where a subset of data already exists on a target from older copies, backups, or shipped drives. 初始复制将仅复制不同的块,这可能会缩短初始同步时间并防止数据耗尽有限的带宽。Initial replication will only copy the differing blocks, potentially shortening initial sync time and preventing data from using up limited bandwidth. 存储副本阻止校验和计算,聚合意味着初始同步性能只受存储和网络速度限制。Storage replicas block checksum calculation and aggregation means that initial sync performance is limited only by the speed of the storage and network.

  • 一致性组Consistency groups. 写入排序可保证 Microsoft SQL Server 等应用程序可以写入多个复制的卷,并了解数据将按顺序写入到目标服务器上。Write ordering guarantees that applications such as Microsoft SQL Server can write to multiple replicated volumes and know the data will write on the destination server sequentially.

  • 用户委托User delegation. 可对不是复制的节点上内置管理员组成员的用户委派管理复制的权限,从而限制他们对不相关区域的访问。Users can be delegated permissions to manage replication without being a member of the built-in Administrators group on the replicated nodes, therefore limiting their access to unrelated areas.

  • 网络约束Network Constraint. 为了提供应用程序、备份和管理软件带宽,可由服务器和已复制的卷将存储副本限制到独立网络。Storage Replica can be limited to individual networks by server and by replicated volumes, in order to provide application, backup, and management software bandwidth.

  • 精简预配Thin provisioning. 在很多情况下,为了提供近乎瞬间的初始复制时间,支持在存储空间和 SAN 设备中进行精简配置。Support for thin provisioning in Storage Spaces and SAN devices is supported, in order to provide near-instantaneous initial replication times under many circumstances.

Windows Server 2016 在存储副本中实现了以下功能:Windows Server 2016 implements the following features in Storage Replica:

功能Feature 详细信息Details
类型Type 基于主机Host-based
同步Synchronous Yes
异步Asynchronous Yes
存储硬件不可知Storage hardware agnostic Yes
复制单元Replication unit 卷(分区)Volume (Partition)
Windows Server 拉伸群集创建Windows Server Stretch Cluster creation Yes
服务器到服务器复制Server to server replication Yes
群集到群集复制Cluster to cluster replication Yes
“传输”Transport SMB3SMB3
Network (网络)Network TCP/IP 或 RDMATCP/IP or RDMA
网络约束支持Network constraint support Yes
RDMARDMA iWARP、InfiniBand、RoCE v2iWARP, InfiniBand, RoCE v2
复制网络端口防火墙要求Replication network port firewall requirements 单个 IANA 端口(TCP 445 或 5445)Single IANA port (TCP 445 or 5445)
多路径/多通道Multipath/Multichannel 是 (SMB3)Yes (SMB3)
Kerberos 支持Kerberos support 是 (SMB3)Yes (SMB3)
通过有线加密和签名Over the wire encryption and signing 是 (SMB3)Yes (SMB3)
允许按每个卷进行故障转移Per-volume failovers allowed Yes
精简配置的存储支持Thin-provisioned storage support Yes
管理 UI 内部Management UI in-box PowerShell、故障转移群集管理器PowerShell, Failover Cluster Manager

可能需要其他远程设备和电缆线路。May require additional long haul equipment and cabling.

存储副本先决条件 Storage Replica Prerequisites

  • Active Directory 域服务林。Active Directory Domain Services forest.
  • 具有 SAS JBOD 的存储空间、存储空间直通、光纤通道 SAN、共享 VHDX、iSCSI 目标或本地 SAS/SCSI/SATA 存储。Storage Spaces with SAS JBODs, Storage Spaces Direct, fibre channel SAN, shared VHDX, iSCSI Target, or local SAS/SCSI/SATA storage. 对于复制日志驱动器,建议使用 SSD 或更快速度。SSD or faster recommended for replication log drives. Microsoft 建议,日志存储应比数据存储速度快。Microsoft recommends that the log storage be faster than the data storage. 日志卷不得用于其他工作负荷。Log volumes must never be used for other workloads.
  • 每个服务器上必须具有至少一个用于同步复制的以太网/TCP 连接,但最好是 RDMA。At least one ethernet/TCP connection on each server for synchronous replication, but preferably RDMA.
  • 至少 2 GB 的 RAM 且每台服务器具有两个内核。At least 2GB of RAM and two cores per server.
  • 服务器间的网络具有足够的带宽,以包含 IO 写入工作负载和平均值为 5 毫秒或更低的往返行程延迟(对于同步复制)。A network between servers with enough bandwidth to contain your IO write workload and an average of 5ms round trip latency or lower, for synchronous replication. 异步复制没有延迟建议。Asynchronous replication does not have a latency recommendation.

背景 Background

本节包括有关高级行业术语、同步和异步复制以及关键行为的信息。This section includes information about high-level industry terms, synchronous and asynchronous replication, and key behaviors.

高级行业术语High level industry terms

灾难恢复 (DR) 是指从站点灾难恢复,以便业务继续运行的应急计划。Disaster Recovery (DR) refers to a contingency plan for recovering from site catastrophes so that the business continues to operate. 数据 DR 表示单独物理位置中的多个生产数据副本。Data DR means multiple copies of production data in a separate physical location. 例如延伸群集,其中一半的节点在一个站点中,另一半则在另一个站点中。For example, a stretch cluster, where half the nodes are in one site and half are in another. 灾难预防 (DP) 是指在灾难到来前(如飓风),提前将工作负载移动到另一个位置的应急计划。Disaster Preparedness (DP) refers to a contingency plan for preemptively moving workloads to a different location prior to an oncoming disaster, such as a hurricane.

服务级别协议 (SLA) 表示在已计划和非计划停机期间,企业的应用程序的可用性及其停机时间和数据丢失容差。Service level agreements (SLAs) define the availability of a business' applications and their tolerance of down time and data loss during planned and unplanned outages. 恢复时间目标 (RTO) 表示业务对数据不可访问的总承受时间。Recovery Time Objective (RTO) defines how long the business can tolerate total inaccessibility of data. 恢复点目标 (RPO) 表示业务对丢失数据的承受量。Recovery Point Objective (RPO) defines how much data the business can afford to lose.

同步复制Synchronous Replication

同步复制可确保应用程序在 IO 完成之前将数据一次写入两个位置。Synchronous replication guarantees that the application writes data to two locations at once before completion of the IO. 由于这种复制要求网络和存储投资且有降低应用程序性能的风险,所以它更适合于任务关键数据。This replication is more suitable for mission critical data, as it requires network and storage investments, as well as a risk of degraded application performance.

当源数据副本上发生应用程序写入操作时,源存储不会立即确认 IO。When application writes occur on the source data copy, the originating storage does not acknowledge the IO immediately. 相反,那些数据更改对远程目标副本的复制,并返回一条确认。Instead, those data changes replicate to the remote destination copy and return an acknowledgement. 此时,应用程序才会收到 IO 确认。Only then does the application receive the IO acknowledgment. 这可确保远程站点与源站点的固定同步,有效地跨网络扩展存储 IO。This ensures constant synchronization of the remote site with the source site, in effect extending storage IOs across the network. 在源站点故障时,应用程序可以故障转移到远程站点并恢复其运行,同时保证零数据丢失。In the event of a source site failure, applications can failover to the remote site and resume their operations with assurance of zero data loss.

模式Mode 图示Diagram 步骤Steps
同步Synchronous

零数据丢失Zero Data Loss

RPORPO
显示存储副本如何在同步复制中写入数据的关系图 1.应用程序写入数据1. Application writes data
2.写入日志数据,并将数据复制到远程站点2. Log data is written and the data is replicated to the remote site
3.在远程站点写入日志数据3. Log data is written at the remote site
4.从远程站点确认4. Acknowledgement from the remote site
5.确认应用程序写入5. Application write acknowledged

t & t1:数据刷新到该卷,始终写入日志t & t1 : Data flushed to the volume, logs always write through

异步复制Asynchronous Replication

相反,异步复制意味着当应用程序写入数据时,将在没有立即确认保证的情况下将该数据复制到远程站点。Contrarily, asynchronous replication means that when the application writes data, that data replicates to the remote site without immediate acknowledgment guarantees. 此模式允许更迅速地响应应用程序以及按地理位置工作的 DR 解决方案。This mode allows faster response time to the application as well as a DR solution that works geographically.

当应用程序写入数据时,复制引擎将捕获该写入并立即向应用程序确认。When the application writes data, the replication engine captures the write and immediately acknowledges to the application. 然后,捕获的数据将复制到远程位置。The captured data then replicates to the remote location. 远程节点处理数据的副本,并延迟返回向源副本确认。The remote node processes the copy of the data and lazily acknowledges back to the source copy. 由于复制性能不再处于应用程序 IO 路径中,因此远程站点的响应速度和距离都是不太重要的因素。Since replication performance is no longer in the application IO path, the remote site's responsiveness and distance are less important factors. 如果源数据丢失,并且数据的目标副本仍在缓冲区而没有离开源,则存在数据丢失的风险。There is risk of data loss if the source data is lost and the destination copy of the data was still in buffer without leaving the source.

使用其比 zero RPO 更高的版本,异步复制不太适用于 HA 解决方案,如故障转移群集,因为它们是为具有冗余和无数据丢失的连续操作而设计。With its higher than zero RPO, asynchronous replication is less suitable for HA solutions like Failover Clusters, as they are designed for continuous operation with redundancy and no loss of data.

模式Mode 图示Diagram 步骤Steps
异步Asynchronous

几乎零数据丢失Near zero data loss

(取决于多种因素)(depends on multiple factors)

RPORPO
显示存储副本如何在异步复制中写入数据的关系图 1.应用程序写入数据1. Application writes data
2.写入日志数据2. Log data written
3.确认应用程序写入3. Application write acknowledged
4.数据复制到远程站点4. Data replicated to the remote site
5.日志数据在远程站点写入5. Log data written at the remote site
6.从远程站点确认6. Acknowledgement from the remote site

t & t1:数据刷新到该卷,始终写入日志t & t1 : Data flushed to the volume, logs always write through

关键评估值和行为Key Evaluation Points and Behaviors

  • 具备最快存储速度的网络带宽和延迟。Network bandwidth and latency with fastest storage. 同步复制方面存在一些物理限制。There are physical limitations around synchronous replication. 因为存储副本实现使用日志和要求网络往返行程的 IO 筛选机制,同步复制可能会使应用程序写入速度较慢。Because Storage Replica implements an IO filtering mechanism using logs and requiring network round trips, synchronous replication is likely make application writes slower. 通过为日志使用低延迟、高带宽网络以及高吞吐量磁盘子系统,将尽量减少性能开销。By using low latency, high-bandwidth networks as well as high-throughput disk subsystems for the logs, you will minimize performance overhead.

  • 在 Windows Server 2016 中复制时目标卷不可访问。The destination volume is not accessible while replicating in Windows Server 2016. 在配置复制时,目标卷将卸除,这使得用户无法进行任何读取或写入。When you configure replication, the destination volume dismounts, making it inaccessible to any reads or writes by users. 其驱动器号可以显示在文件资源管理器等常见界面中,但是,应用程序无法访问卷本身。Its driver letter may be visible in typical interfaces like File Explorer, but an application cannot access the volume itself. 块级别复制技术与卷中允许访问的目标已装载文件系统不兼容;当块在其下更改时,NTFS 和 ReFS 不支持用户将数据写入该卷中。Block-level replication technologies are incompatible with allowing access to the destination target's mounted file system in a volume; NTFS and ReFS do not support users writing data to the volume while blocks change underneath them.

在 Windows Server 版本 1709 中,添加了新的“测试故障转移”选项。In Windows Server, Version 1709 the new Test-Failover option was added. 此版本现在支持临时安装目标卷的读写快照以用于备份、测试等用途。有关详细信息,请访问 https://aka.ms/srfaq。This now supports temporarily mounting a read-write snapshot of the destination volume for backups, testing, etc. See https://aka.ms/srfaq for more info.

  • 异步复制的 Microsoft 实现与大多数不同。The Microsoft implementation of asynchronous replication is different than most. 异步复制的大多数行业实现依赖于基于快照的复制,其中周期性差异传输移动到另一个节点并进行合并。Most industry implementations of asynchronous replication rely on snapshot-based replication, where periodic differential transfers move to the other node and merge. 存储副本异步复制的操作与同步复制相同,只是它不需要从目标进行序列化同步确认。Storage Replica asynchronous replication operates just like synchronous replication, except that it removes the requirement for a serialized synchronous acknowledgment from the destination. 这意味着存储副本理论上具有较低的 RPO,因为它会持续进行复制。This means that Storage Replica theoretically has a lower RPO as it continuously replicates. 但是,这也意味着它依赖于内部应用程序一致性保证,而不是使用快照来强制实现应用程序文件一致性。However, this also means it relies on internal application consistency guarantees rather than using snapshots to force consistency in application files. 存储副本保证所有复制模式中的故障一致性Storage Replica guarantees crash consistency in all replication modes

  • 许多客户使用 DFS 复制作为灾难恢复解决方案,即使往往在这种情况下不切实际 - DFS 复制不能复制打开的文件,它旨在最小化带宽使用量,这会降低性能,从而导致较大的恢复点增量。Many customers use DFS Replication as a disaster recovery solution even though often impractical for that scenario - DFS Replication cannot replicate open files and is designed to minimize bandwidth usage at the expense of performance, leading to large recovery point deltas. 存储副本可能允许从这些类型的灾难恢复职责停用 DFS 复制。Storage Replica may allow you to retire DFS Replication from some of these types of disaster recovery duties.

  • 存储副本未备份。Storage Replica is not backup. 某些 IT 环境部署复制系统作为备份解决方案,因为相比每日备份,它们具有零数据丢失选项。Some IT environments deploy replication systems as backup solutions, due to their zero data loss options when compared to daily backups. 存储副本将所有更改都复制到卷上的数据块,而不考虑更改类型。Storage Replica replicates all changes to all blocks of data on the volume, regardless of the change type. 如果用户从卷中删除所有数据,存储副本会立即将删除数据复制到另一个卷,且无法撤消地从这两个服务器中删除该数据。If a user deletes all data from a volume, Storage Replica will replicate the deletion instantly to the other volume, irrevocably removing the data from both servers. 不要使用存储副本来替换时间点备份解决方案。Do not use Storage Replica as a replacement for a point-in-time backup solution.

  • 存储副本不是 Hyper-V 副本或 Microsoft SQL AlwaysOn 可用性组。Storage Replica is not Hyper-V Replica or Microsoft SQL AlwaysOn Availability Groups. 存储副本是存储不可知的常规用途引擎。Storage Replica is a general purpose, storage-agnostic engine. 根据定义,它不能像应用程序级别的复制一样理想地定制其行为。By definition, it cannot tailor its behavior as ideally as application-level replication. 这可能导致特定功能差距,它鼓励你部署或保持特定的应用程序复制技术。This may lead to specific feature gaps that encourage you to deploy or remain on specific application replication technologies.

备注

本文档包含已知问题和预期行为列表,以及常见问题部分。This document contains a list of known issues and expected behaviors as well as Frequently Asked Questions section.

存储副本术语Storage Replica terminology

本指南经常使用以下术语:This guide frequently uses the following terms:

  • 源是计算机的卷,它允许本地写入和出站复制,The source is a computer's volume that allows local writes and replicates outbound. 也称为“主要”。Also known as "primary".

  • 目标是计算机的卷,它不允许本地写入和入站复制,The destination is a computer's volume that does not allow local writes and replicates inbound. 也称为“次要”。Also known as "secondary".

  • 复制合作关系是对一个或多个卷的源和目标计算机之间的同步关系,并利用单个日志。A replication partnership is the synchronization relationship between a source and destination computer for one or more volumes and utilizes a single log.

  • 复制组是合作关系内的卷及其复制配置的组织,在每个服务器上有所不同。A replication group is the organization of volumes and their replication configuration within a partnership, on a per server basis. 组可以包含一个或多个卷。A group may contain one or more volumes.

另请参阅See also