儲存體複本的常見問題集Frequently Asked Questions about Storage Replica

適用於:Windows Server (半年度管道)、Windows Server 2016Applies to: Windows Server (Semi-Annual Channel), Windows Server 2016

本主題包含關於「儲存體複本」的常見問題集 (FAQ) 解答。This topic contains answers to frequently asked questions (FAQs) about Storage Replica.

Nano 伺服器上是否支援「儲存體複本」? Is Storage Replica supported on Nano Server?

是。Yes.

注意

您必須在安裝期間使用儲存體 Nano 伺服器套件。You must use the Storage Nano Server package during setup. 如需部署 Nano 伺服器的詳細資訊,請參閱開始使用 Nano 伺服器For more information about deploying Nano Server, see Getting Started with Nano Server.

使用 PowerShell 遠端執行功能,在 Nano 伺服器上安裝「儲存體複本」,如下所示:Install Storage Replica on Nano Server using PowerShell remoting as follows:

  1. 將 Nano 伺服器新增至您的用戶端信任清單。Add the Nano server to your client trust list.

    注意

    只有在電腦不是 Active Directory 網域服務樹系的成員,或位於不受信任的樹系中時,才需要此步驟。This step is only necessary if the computer is not a member of an Active Directory Domain Services forest or in an untrusted forest. 它在 PSSession 遠端執行功能中新增 NTLM 支援,但基於安全性因素預設會停用此支援。It adds NTLM support to PSSession remoting, which is disabled by default for security reasons. 如需詳細資訊,請參閱 PowerShell 遠端執行功能安全性考量For more information, see PowerShell Remoting Security Considerations.

        Set-Item WSMan:\localhost\Client\TrustedHosts "<computer name of Nano Server>"  
    
  2. 若要安裝「儲存體複本」功能,請從管理電腦執行下列 Cmdlet:To install the Storage Replica feature, run the following cmdlet from a management computer:

    Install-windowsfeature -Name storage-replica,RSAT-Storage-Replica -ComputerName <nano server> -Restart -IncludeManagementTools  
    

    在 Windows Server 2016 中使用 Test-SRTopology Cmdlet 搭配 Nano 伺服器,需要含有 CredSSP 的遠端指令碼引動過程。Using the Test-SRTopology cmdlet with Nano Server in Windows Server 2016 requires remote script invocation with CredSSP. 不像其他「儲存體複本」Cmdlet,Test-SRTopology 需要在來源伺服器上本機執行。Unlike other Storage Replica cmdlets, Test-SRTopology requires running locally on the source server.
    在 Nano 伺服器上 (透過遠端 PSSession):On the Nano server (through a remote PSSession) :

    注意

    Test-SRTopology Cmdlet 中對於 Kerberos 雙躍點支援需要有 CREDSSP,而其他「儲存體複本」Cmdlet 則不需要,這些 Cmdlet 會自動處理分散式系統認證。CREDSSP is needed for Kerberos double-hop support in the Test-SRTopology cmdlet, and not needed by other Storage Replica cmdlets, which handle distributed system credentials automatically. 不建議在一般情況中使用 CREDSSP。Using CREDSSP is not recommended under typical circumstances. 如需 CREDSSP 的的替代方案,請檢閱下列 Microsoft 部落格文章:"PowerShell Remoting Kerberos Double Hop Solved Securely" - https://blogs.technet.microsoft.com/ashleymcglone/2016/08/30/powershell-remoting-kerberos-double-hop-solved-securely/ (安全解決的 PowerShell Remoting Kerberos 雙躍點)For an alternative to CREDSSP, review the following Microsoft blog post: "PowerShell Remoting Kerberos Double Hop Solved Securely" - https://blogs.technet.microsoft.com/ashleymcglone/2016/08/30/powershell-remoting-kerberos-double-hop-solved-securely/

    Enable-WSManCredSSP -role server       
    

    在管理電腦上:On the management computer:

     Enable-WSManCredSSP Client -DelegateComputer <remote server name>  
    
     $CustomCred = Get-Credential  
    
     Invoke-Command -ComputerName sr-srv01 -ScriptBlock { Test-SRTopology <commands> } -Authentication Credssp -Credential $CustomCred  
    

    接著將結果複製到您的管理電腦或共用路徑。Then copy the results to your management computer or share the path. 因為 Nano 缺少必要的圖形庫,您可以使用 Test-SRTopology 來處理結果,並提供含有圖表的報告檔案。Because Nano lacks the necessary graphical libraries, you can use Test-SRTopology to process the results and give you a report file with charts. 例如:For example:

    Test-SRTopology -GenerateReport -DataPath \\sr-srv05\c$\temp  
    

如何在初始同步期間查看複寫的進度? How do I see the progress of replication during initial sync?

目的地伺服器上「儲存體複本系統管理」事件記錄檔中所示的事件 1237 訊息,每隔 10 秒會顯示已複製的位元組數目和剩餘的位元組數目。The Event 1237 messages shown in the Storage Replica Admin even log on the destination server show number of bytes copied and bytes remaining every 10 seconds. 您也可以使用目的地上的「儲存體複本」效能計數器,該計數器針對一或多個複寫的磁碟區顯示 \儲存體複本統計資料\已接收的位元組總數You can also use the Storage Replica performance counter on the destination showing \Storage Replica Statistics\Total Bytes Received for one or more replicated volumes. 您也可以使用 Windows PowerShell 來查詢複寫群組。You can also query the replication group using Windows PowerShell. 例如,此範例命令會取得目的地上的群組名稱,然後每隔 10 秒查詢一個名為 Replication 2 的群組來顯示進度:For instance, this sample command gets the name of the groups on the destination then queries one group named Replication 2 every 10 seconds to show progress:

Get-SRGroup

do{
    $r=(Get-SRGroup -Name "Replication 2").replicas
    [System.Console]::Write("Number of remaining bytes {0}`n", $r.NumOfBytesRemaining)
    Start-Sleep 10
}until($r.ReplicationStatus -eq 'ContinuouslyReplicating')
Write-Output "Replica Status: "$r.replicationstatus

我是否可以指定要用於複寫的特定網路介面?Can I specify specific network interfaces to be used for replication?

是,請使用 Set-SRNetworkConstraintYes, using Set-SRNetworkConstraint. 這個 Cmdlet 會在介面層上運作,並在叢集與非叢集案例上使用。This cmdlet operates at the interface layer and be used on both cluster and non-cluster scenarios.
例如,利用獨立伺服器 (在每個節點上):For example, with a standalone server (on each node):

Get-SRPartnership  

Get-NetIPConfiguration  

記下閘道和介面資訊 (在這兩部伺服器上) 及合作關係指引。Note the gateway and interface information (on both servers) and the partnership directions. 然後執行:Then run:

Set-SRNetworkConstraint -SourceComputerName sr-srv06 -SourceRGName rg02 -  
SourceNWInterface 2 -DestinationComputerName sr-srv05 -DestinationNWInterface 3 -DestinationRGName rg01  

Get-SRNetworkConstraint  

Update-SmbMultichannelConnection  

在延展式叢集上設定網路限制式:For configuring network constraints on a stretch cluster:

Set-SRNetworkConstraint -SourceComputerName sr-srv01 -SourceRGName group1 -SourceNWInterface "Cluster Network 1","Cluster Network 2" -DestinationComputerName sr-srv03 -DestinationRGName group2 -DestinationNWInterface "Cluster Network 1","Cluster Network 2"  

我是否可以設定一對多的複寫或可轉移 (A 到 B 到 C) 的複寫? Can I configure one-to-many replication or transitive (A to B to C) replication?

不在 Windows Server 2016 中。Not in Windows Server 2016. 這個版本只支援伺服器、叢集或延展式叢集節點的一對一複寫。This release only supports one to one replication of a server, cluster, or stretch cluster node. 這可能會在未來版本中變更。This may change in a later release. 當然,您可以設定特定磁碟區組的各種伺服器間任一方向的複寫。You can of course configure replication between various servers of a specific volume pair, in either direction. 例如,伺服器 1 可以將其 D 磁碟區複寫到伺服器 2,並從伺服器 3 複寫其 E 磁碟區。For instance, Server 1 can replicate its D volume to server 2, and its E volume from Server 3.

我是否可以增加或縮減「儲存體複本」所複寫的複寫磁碟區? Can I grow or shrink replicated volumes replicated by Storage Replica?

您可以增加 (延伸) 磁碟區,而不是進行壓縮。You can grow (extend) volumes, but not shrink them. 根據預設,儲存體複本防止系統管理員延伸複寫磁碟區。在調整大小之前,在來源群組上使用 Set-SRGroup -AllowVolumeResize $TRUE 選項。By default, Storage Replica prevents administrators from extending replicated volumes; use the Set-SRGroup -AllowVolumeResize $TRUE option on the source group, prior to resizing. 例如:For example:

  1. 針對來源電腦使用:Use against the source computer: Set-SRGroup -Name YourRG -AllowVolumeResize $TRUE
  2. 使用任何您想要的技術增加磁碟區Grow the volume using whatever technique you prefer
  3. 針對來源電腦使用:Use against the source computer: Set-SRGroup -Name YourRG -AllowVolumeResize $FALSE

我是否可以使目的地磁碟區上線以進行唯讀存取?Can I bring a destination volume online for read-only access?

不在 Windows Server 2016 RTM (亦即所謂的「RS1」版本) 中。Not in Windows Server 2016 RTM, aka the so-called "RS1" release. 當複寫開始,儲存體複本會卸載目的地磁碟區。Storage Replica dismounts the destination volume when replication begins.

不過,現已可以在 Windows Server 版本 1709 中掛接目的地存放裝置,這項功能稱為「測試容錯移轉」。However, in Windows Server Version, 1709 the option to mount the destination storage is now possible - this feature is called "Test Failover". 若要這樣做,您必須有目前未於目的地複寫的未使用磁碟區或者 NTFS 或 ReFS 格式化磁碟區。To do this, you must have an unused, NTFS or ReFS formatted volume that is not currently replicating on the destination. 然後便可暫時掛接已複寫存放裝置的快照集以作測試或備份之用。Then you can mount a snapshot of the replicated storage temporarily for testing or backup purposes.

例如,若要建立測試容錯移轉,藉以在目的地伺服器「SRV2」的複寫群組「RG2」中複寫磁碟區「D:」,以及在 SRV2 上安裝未經複寫的「T:」磁碟機:For example, to create a test failover where you are replicating a volume "D:" in the Replication Group "RG2" on the destination server "SRV2" and have a "T:" drive on SRV2 that is not being replicated:

Mount-SRDestination -Name RG2 -Computername SRV2 -TemporaryPath T:\

現已可在 SRV2 上存取複寫的磁碟區 D:。The replicated volume D: is now accessible on SRV2. 您可以正常對其讀取和寫入、將檔案複製出來,或執行要儲存在其他位置妥善保管的線上備份。You can read and write to it normally, copy files off it, or run an online backup that you save elsewhere for safekeeping.

若要移除測試容錯移轉快照並捨棄其變更:To remove the test failover snapshot and discard its changes:

Dismount-SRDestination -Name RG2 -Computername SRV2

您只能將測試容錯移轉功能用於短期暫時作業。You should only use the test failover feature for short-term temporary operations. 此功能並不適合長期使用。It is not intended for long term usage. 使用時,複寫會持續對實際目的地磁碟區進行。When in use, replication continues to the real destination volume.

是否可以在延展式叢集中設定向外延展檔案伺服器 (SOFS)? Can I configure Scale-out File Server (SOFS) in a stretch cluster?

儘管技術上可行,但這不是 Windows Server 2016 中的建議設定,因為連絡 SOFS 的計算節點中缺少站台感知。While technically possible, this is not a recommended configuration in Windows Server 2016 due to the lack of site awareness in the compute nodes contacting the SOFS. 如果使用校園距離的網路 (其中的延遲通常是以子毫秒為單位),此設定一般會正確運作而不會產生問題。If using campus-distance networking, where latencies are typically sub-millisecond, this configuration typically works works without issues.

如果設定叢集對叢集複寫,在兩個叢集之間進行複寫時,「儲存體複本」可完全支援「向外延展檔案伺服器」,包括使用「儲存空間直接存取」。If configuring cluster-to-cluster replication, Storage Replica fully supports Scale-out File Servers, including the use of Storage Spaces Direct, when replicating between two clusters.

我是否可以在延展式叢集上使用「儲存體複本」來設定「儲存空間直接存取」?Can I configure Storage Spaces Direct in a stretch cluster with Storage Replica?

Windows Server 2016 中不支援此設定。This is not a supported configuration in Windows Server 2016. 這可能會在未來版本中變更。This may change in a later release. 如果設定叢集對叢集複寫,「儲存體複本」可完全支援「向外延展檔案伺服器」和 Hyper-V 伺服器,包括使用「儲存空間直接存取」。If configuring cluster-to-cluster replication, Storage Replica fully supports Scale Out File Servers and Hyper-V Servers, including the use of Storage Spaces Direct.

如何設定非同步複寫?How do I configure asynchronous replication?

指定 New-SRPartnership -ReplicationMode 並提供引數 AsynchronousSpecify New-SRPartnership -ReplicationMode and provide argument Asynchronous. 根據預設值,「儲存體複本」中的所有複寫都是同步的。By default, all replication in Storage Replica is synchronous. 您也可以使用 Set-SRPartnership -ReplicationMode 來變更模式。You can also change the mode with Set-SRPartnership -ReplicationMode.

如何防止延展式叢集進行自動容錯移轉?How do I prevent automatic failover of a stretch cluster?

若要防止自動容錯移轉,您可以使用 PowerShell 來設定 Get-ClusterNode -Name "NodeName").NodeWeight=0To prevent automatic failover, you can use PowerShell to configure Get-ClusterNode -Name "NodeName").NodeWeight=0. 這將會在災害復原網站中移除每個節點上的投票。This removes the vote on each node in the disaster recovery site. 接著,您可以在主要網站的節點上使用 Start-ClusterNode -PreventQuorum,以及在災害網站的節點上使用 Start-ClusterNode -ForceQuorum,以強制執行容錯移轉。Then you can use Start-ClusterNode -PreventQuorum on nodes in the primary site and Start-ClusterNode -ForceQuorum on nodes in the disaster site to force failover. 沒有任何圖形化選項可防止自動容錯移轉,且不建議防止自動容錯移轉。There is no graphical option for preventing automatic failover, and preventing automatic failover is not recommended.

如何停用虛擬機器復原功能?How do I disable virtual machine resiliency?

若要防止新的 Hyper-V 虛擬機器復原功能執行,因而暫停虛擬機器,而不是讓它們容錯移轉到災害復原站台,請執行To prevent the new Hyper-V virtual machine resiliency feature from running and therefore pausing virtual machines instead of failing them over to the disaster recovery site, run (Get-Cluster).ResiliencyDefaultPeriod=0

如何減少初始同步的時間? How can I reduce time for initial synchronization?

您可以使用精簡佈建的儲存體做為一種方式來加速初始同步時間。You can use thin-provisioned storage as one way to speed up initial sync times. 「儲存體複本」會查詢並自動使用精簡佈建的儲存體,包括非叢集儲存空間、Hyper-V 動態磁碟與 SAN LUN。Storage Replica queries for and automatically uses thin-provisioned storage, including non-clustered Storage Spaces, Hyper-V dynamic disks, and SAN LUNs.

您也可以使用植入的資料磁碟區來減少頻寬使用量,有時還可以減少時間,方法是確定目的地磁碟區含有來自主要站台的一些資料子站台 (透過還原的備份、舊的快照、先前的複寫、複製的檔案等),然後使用「容錯移轉叢集管理員」或 New-SRPartnership 中的 [已植入] 選項。You can also use seeded data volumes to reduce bandwidth usage and sometimes time, by ensuring that the destination volume has some subset of data from the primary - via a restored backup, old snapshot, previous replication, copied files, etc. - then using the Seeded option in Failover Cluster Manager or New-SRPartnership. 如果磁碟區大部分都是空的,則使用植入的同步可能會降減少時間和頻寬使用量。If the volume is mostly empty, using seeded sync may reduce time and bandwidth usage.

我是否可以委派使用者管理複寫? Can I delegate users to administer replication?

您可以使用 Windows Server 2016 中的 Grant-SRDelegation Cmdlet。You can use the Grant-SRDelegation cmdlet in Windows Server 2016. 這可讓您在伺服器對伺服器、叢集對叢集及延展式複寫案例中設定特定使用者,就像擁有建立、修改或移除複寫的權限,而不需是本機系統管理員群組的成員。This allows you to set specific users in server to server, cluster to cluster, and stretch cluster replication scenarios as having the permissions to create, modify, or remove replication, without being a member of the local administrators group. 例如:For example:

Grant-SRDelegation -UserName contso\tonywang  

這個 Cmdlet 將提醒您,使用者必須登出,然後登入其正準備進行管理的伺服器,以便讓變更生效。The cmdlet will remind you that the user needs to log off and on of the server they are planning to administer in order for the change to take effect. 您可以使用 Get-SRDelegationRevoke-SRDelegation 進一步控制此動作。You can use Get-SRDelegation and Revoke-SRDelegation to further control this.

我有哪些適用於複寫磁碟區的備份與還原選項? What are my backup and restore options for replicated volumes?

「儲存體複本」支援備份及還原來源磁碟區。Storage Replica supports backing up and restoring the source volume. 它也支援建立及還原來源磁碟區的快照。It also supports creating and restoring snapshots of the source volume. 您無法在目的地磁碟區受到「儲存體複本」保護時備份或還原該磁碟區,因為它並未掛接,也無法存取。You cannot backup or restore the destination volume while protected by Storage Replica, as it is not mounted nor accessible. 如果您遇到來源磁碟區遺失的災害時,使用 Set-SRPartnership 將前一個目的地磁碟區立即升級為讀取/可寫入來源,將可讓您備份或還原該磁碟區。If you experience a disaster where the source volume is lost, using Set-SRPartnership to promote the previous destination volume to now be a read/writable source will allow you to backup or restore that volume. 您也可以使用 Remove-SRPartnershipRemove-SRGroup 來移除複寫,以重新掛接該磁碟區做為讀取/可寫入來源。You can also remove replication with Remove-SRPartnership and Remove-SRGroup to remount that volume as read/writable. 若要定期建立應用程式一致快照,您可以在來源伺服器上使用 VSSADMIN.EXE 以建立複寫資料磁碟區的快照。To create periodic application consistent snapshots, you can use VSSADMIN.EXE on the source server to snapshot replicated data volumes. 例如,您正在其中使用「儲存體複本」來複寫 F: 磁碟區:For example, where you are replicating the F: volume with Storage Replica:

vssadmin create shadow /for=F:

接著,在您切換複寫方向、移除複寫,或者就只是仍位於相同來源磁碟機之後,您可以將任何快照還原到它的時間點。Then, after you switch replication direction, remove replication, or are simply still on the same source volume, you can restore any snapshot to its point in time. 例如,仍然使用 F:For example, still using F:

vssadmin list shadows
 vssadmin revert shadow /shadow={shadown copy ID GUID listed previously}

您也可以使用排程的工作,定期排程此工具來執行。You can also schedule this tool to run periodically using a scheduled task. 如需使用 VSS 的詳細資訊,請檢閱 VssadminFor more information on using VSS, review Vssadmin. 備份記錄檔磁碟區時沒有任何需要或值。There is no need or value in backing up the log volumes. 嘗試這麼做時,VSS 將會加以忽略。Attempting to do so will be ignored by VSS. 使用 Windows Server Backup、Microsoft Azure 備份、Microsoft DPM 或其他快照,只要 VSS、虛擬機器或以檔案為基礎的技術是在磁碟區層內運作,就受到「儲存體複本」所支援。Use of Windows Server Backup, Microsoft Azure Backup, Microsoft DPM, or other snapshot, VSS, virtual machine, or file-based technologies are supported by Storage Replica as long as they operate within the volume layer. 「儲存體複本」不支援以區塊為基礎的備份及還原。Storage Replica does not support block-based backup and restore.

我是否可以設定複寫來限制頻寬使用量? Can I configure replication to restrict bandwidth usage?

是,可透過 SMB 頻寬限制器來設定。Yes, via the SMB bandwidth limiter. 這是適用於所有「儲存體複本」流量的全域設定,因此會影響所有來自此伺服器的複寫。This is a global setting for all Storage Replica traffic and therefore affects all replication from this server. 一般而言,只有使用「儲存體複本」初始同步設定時才需要此項,而其中的所有磁碟區資料都必須傳輸。Typically, this is needed only with Storage Replica initial sync setup, where all the volume data must transfer. 如果在初始同步之後需要執行此動作,您的網路頻寬對 IO 工作負載而言就會過低;請減少 IO 或增加頻寬。If needed after initial sync, your network bandwidth is too low for your IO workload; reduce the IO or increase the bandwidth.

這應該只能用於非同步複寫 (注意︰初始同步一律是非同步,即使您已指定同步也一樣)。This should only be used with asynchronous replication (note: initial sync is always asynchronous even if you have specified synchronous). 您也可以使用網路 QoS 原則,來為「儲存體複本」流量塑型。You can also use network QoS policies to shape Storage Replica traffic. 使用高度相符的植入「儲存體複本」複寫,也會大幅降低整體初始同步的頻寬使用量。Use of highly matched seeded Storage Replica replication will also lower overall initial sync bandwidth usage considerably.

若要設定頻寬限制,請使用:To set the bandwidth limit, use:

Set-SmbBandwidthLimit  -Category StorageReplication -BytesPerSecond x

若要查看頻寬限制,請使用:To see the bandwidth limit, use:

Get-SmbBandwidthLimit -Category StorageReplication

若要移除頻寬限制,請使用:To remove the bandwidth limit, use:

Remove-SmbBandwidthLimit -Category StorageReplication

儲存體複本需要哪些網路連接埠?What network ports does Storage Replica require?

儲存體複本依賴 SMB 和 WSMAN 的複寫和管理。Storage Replica relies on SMB and WSMAN for its replication and management. 這表示需要下列連接埠:This means the following ports are required:

445 (SMB - 複寫傳輸通訊協定) 5445 (iWARP SMB - 只在 iWARP RDMA 網路時需要) 5895 (WSManHTTP - WMI/CIM/PowerShell 管理通訊協定)445 (SMB - replication transport protocol) 5445 (iWARP SMB - only needed when using iWARP RDMA networking) 5895 (WSManHTTP - Management protocol for WMI/CIM/PowerShell)

注意:Test-SRTopology cmdlet 需要 ICMPv4/ICMPv6,但不適用於複寫或管理。Note: The Test-SRTopology cmdlet requires ICMPv4/ICMPv6, but not for replication or management.

有哪些記錄檔磁碟區最佳做法?What are the log volume best practices?

記錄檔的最佳大小會依照環境和工作負載而有很大差別,取決於您的工作負載執行多少寫入 IO。The optimal size size of the log varies widely per environment and workload, and is determined by how much write IO your workload performs.

  1. 記錄檔放大或縮小並不會讓您變得再快或再慢一點A larger or smaller log doesn’t make you any faster or slower
  2. 例如,更大或更小的記錄檔對小至 10GB 的資料磁碟區和大至 10TB 的資料磁碟區都不會有任何影響。A larger or smaller log doesn’t have any bearing on a 10GB data volume versus a 10TB data volume, for instance

較大的記錄檔只是在換出寫滿的資料之前收集和保留較多寫入 IO 而已。這可能會讓來源與目的地電腦之間發生的服務中斷 (例如網路斷線或目的地離線) 持續得更久。A larger log simply collects and retains more write IOs before they are wrapped out. This allows an interruption in service between the source and destination computer – such as a network outage or the destination being offline - to go longer. 如果記錄檔可以保留 10 小時的寫入,而網路中斷了 2 小時,當網路回復時,來源可以簡單地重新執行未同步的變更,非常迅速地將目的地的落差補足,您也很快地重新受到保護。If the log can hold 10 hours of writes, and the network goes down for 2 hours, when the network returns the source can simply play the delta of unsynced changes back to the destination very fast and you are protected again very quickly. 如果記錄檔保留 10 小時寫入而斷線了 2 天,來源現在則必須從不同的記錄檔 (稱為點陣圖) 開始重新執行,很可能較慢恢復到同步狀態。一旦進入同步狀態,就會回復使用原本的記錄檔。If the log holds 10 hours and the outage is 2 days, the source now has to play back from a different log called the bitmap – and will likely be slower to get back into sync. Once in sync it returns to using the log.

會有 SR 效能計數器告訴您記錄檔的變換速率,讓您可以做一些判斷。There are SR performance counters that will tell you the rate the log is churning, allowing you to make some judgements. 此外,Test-SRTopology Cmdlet 也有同樣的作用。Also the Test-SRTopology cmdlet does this. 您基本上只是查看現有工作負載的寫入 IO,來決定每分鐘、每小時或每天有多少 IO 可能在記錄檔流動。Basically you are just looking at write IO on an existing workload to decide how much IO will likely flow the log per minute, hour, or day.

儲存體複本完全仰賴記錄檔發揮寫入效能。Storage Replica relies on the log for all write performance. 記錄檔效能對複寫效能非常重要。Log performance critical to replication performance. 因為記錄檔會序列化並循序化所有的寫入 IO,您必須確保記錄磁碟區的效能比資料磁碟區的效能還要好。You must ensure that the log volume performs better than the data volume, as the log will serialize and sequentialize all write IO. 記錄磁碟區一定要使用像 SSD 這樣的快閃媒體。You should always use flash media like SSD on log volumes. 絕不允許任何其他工作負載在記錄檔磁碟區上執行,同樣也不允許其他工作負載在 SQL 資料庫記錄檔磁碟區上執行。You must never allow any other workloads to run on the log volume, the same way you would never allow other workloads to run on SQL database log volumes.

再說一次:Microsoft 強烈建議記錄檔儲存體必須比資料儲存體更快速,而且記錄磁碟區絕不能用於其他工作負載。Again: Microsoft strongly recommends that the log storage be faster than the data storage and that log volumes must never be used for other workloads.

您選擇延展式叢集、叢集對叢集或伺服器對伺服器拓撲會有不同原因,差異何在? Why would you choose a stretch cluster versus cluster-to-cluster versus server-to-server topology?

儲存體複本有三個主要設定:延展式叢集、叢集對叢集和伺服器對伺服器。Storage Replica comes in three main configurations: strech cluster, cluster-to-cluster, and server-to-server. 各有不同的優點。There are different advantages to each.

延展式叢集拓撲非常適合需要可透過協調流程自動容錯移轉的工作負載,例如 Hyper-V 私人雲端叢集和 SQL Server FCI。The stretch cluster topology is ideal for workloads requiring automatic failover with orchestration, such as Hyper-V private cloud clusters and SQL Server FCI. 其中也有使用 [容錯移轉叢集管理員] 的內建圖形介面。It also has a built-in graphical interface using Failover Cluster Manager. 透過持續保留使用 [儲存空間]、SAN、iSCSI 及 RAID 的傳統非對稱式叢集共用存放架構。It utilizes the classic asymmetric cluster shared storage architecture of Storage Spaces, SAN, iSCSI, and RAID via persistent reservation. 您只使用 2 個節點就可以執行這種拓撲。You can run this with as few as 2 nodes.

叢集對叢集拓撲使用兩個不同的叢集,非常適合需要手動容錯移轉的系統管理員,尤其是在佈建第二網站作災害復原之用,而非日常使用時。The cluster-to-cluster topology uses two separate clusters and is ideal for administrators who want manual failover, especially when the second site is provisioned for disaster recovery and not everyday usage. 協調流程為手動。Orchestration is manual. 和延展式叢集不同的是,此設定可以使用儲存空間直接存取。Unlike stretch cluster, Storage Spaces Direct can be used in this configuration. 您只使用 4 個節點就可以執行這種拓撲。You can run this with as few as four nodes.

伺服器對伺服器拓撲非常適合執行無法納入叢集之硬體的客戶。The server-to-server topology is ideal for customers running hardware that cannot be clustered. 這需要手動容錯移轉及協調流程。It requires manual failover and orchestration. 適用於分公司與中央資料中心之間的低成本部署,尤其是在使用非同步複寫時。It is ideal for inexpensive deployments between branch offices and central datacenters, especially when using asynchronous replication. 此設定通常可以取代用於單一主機災害復原案例之受 DFSR 保護的檔案伺服器執行個體。This configuration can often replace instances of DFSR-protected File Servers used for single-master disaster recovery scenarios.

在所有情況下,這些拓撲都支援在實體硬體及虛擬機器上執行。In all cases, the topologies support both running on physical hardware as well as virtual machines. 在虛擬機器時,基礎 Hypervisor 不需要 Hyper-V;可以是 VMWare、KVM、Xen 等。When in virtual machines, the underlying hypervisor doesn't require Hyper-V; it can be VMware, KVM, Xen, etc.

儲存複本也有伺服器對自我模式,您在此模式下將複寫指向同一台電腦上的兩個不同磁碟區。Storage Replica also has a server-to-self mode, where you point replication to two different volumes on the same computer.

我該如何回報有關「儲存體複本」或本指南的問題? How do I report an issue with Storage Replica or this guide?

如需「儲存體複本」的技術協助,您可以張貼於 Microsoft TechNet 論壇For technical assistance with Storage Replica, you can post at the Microsoft TechNet forums. 您也可以透過電子郵件,將「儲存體複本」相關問題或與此文件的相關問題寄送到 srfeed@microsoft.com。You can also email srfeed@microsoft.com for questions on Storage Replica or issues with this documentation. 偏好使用 https://windowsserver.uservoice.com 網站來了解設計變更要求,因為它可讓您的客戶對您的想法提供支援和意見。The https://windowsserver.uservoice.com site is preferred for design change requests, as it allows your fellow customers to provide support and feedback for your ideas.

另請參閱See Also