将磁盘排除在灾难恢复之外Exclude disks from disaster recovery

本文介绍了如何使用 Azure Site Recovery 在灾难恢复期间免于将磁盘从本地复制到 Azure。This article describes how to exclude disks from replication during disaster recovery from on-premises to Azure with Azure Site Recovery. 出于多种原因,你可能要将磁盘排除在复制之外:You might exclude disks from replication for a number of reasons:

  • 为了不复制已排除的磁盘上所改动的非重要数据。So that unimportant data churned on the excluded disk isn't replicated.
  • 为了优化已使用的复制带宽或目标端资源。To optimize consumed replication bandwidth, or target-side resources.
  • 为了通过不复制非必需的数据来节省存储和网络资源。To save storage and network resources by not replicating data that you don't need.
  • Azure VM 已达到 Site Recovery 复制限制。Azure VMs have reached Site Recovery replication limits.

支持的方案Supported scenarios

可将磁盘排除在复制之外,如下图汇总所示。You can exclude disks from replication as summarized in the table.

Azure 到 AzureAzure to Azure VMware 到 AzureVMware to Azure Hyper-V 到 AzureHyper-V to Azure 物理服务器到 AzurePhysical Server to Azure
Yes Yes Yes Yes

排除限制Exclude limitations

限制Limitation Azure VMAzure VMs VMware VMVMware VMs Hyper-V VMHyper-V VMs
磁盘类型Disk types 可将基本磁盘排除在复制之外。You can exclude basic disks from replication.

不能排除操作系统磁盘或动态磁盘。You can't exclude operating system disks or dynamic disks. 默认排除临时磁盘。Temp disks are excluded by default.
可将基本磁盘排除在复制之外。You can exclude basic disks from replication.

不能排除操作系统磁盘或动态磁盘。You can't exclude operating system disks or dynamic disks.
可将基本磁盘排除在复制之外。You can exclude basic disks from replication.

不能排除操作系统磁盘。You can't exclude operating system disks. 建议不要排除动态磁盘。We recommend that you don't exclude dynamic disks. Site Recovery 无法识别 VHS 在来宾 VM 中是基本磁盘还是动态磁盘。Site Recovery can't identify which VHS is basic or dynamic in the guest VM. 如果未排除所有依赖的动态卷磁盘,则受保护的动态磁盘就会成为故障转移 VM 上的故障磁盘,且该磁盘上的数据不可访问。If all dependent dynamic volume disks aren't excluded, the protected dynamic disk becomes a failed disk on a failover VM, and the data on that disk isn't accessible.
正在复制的磁盘Replicating disk 不能排除正在复制的磁盘。You can't exclude a disk that's replicating.

禁用再重新启用 VM 的复制。Disable and reenable replication for the VM.
不能排除正在复制的磁盘。You can't exclude a disk that's replicating. 不能排除正在复制的磁盘。You can't exclude a disk that's replicating.
移动服务 (VMware)Mobility service (VMware) 不相关Not relevant 只能排除 VM 上已安装移动服务的磁盘。You can exclude disks only on VMs that have the Mobility service installed.

这意味着你必须在要排除磁盘的 VM 上手动安装移动服务。无法使用推送安装机制,因为它仅在启用复制后才安装移动服务。This means that you have to manually install the Mobility service on the VMs for which you want to exclude disks.You can't use the push installation mechanism because it installs the Mobility service only after replication is enabled.
不相关。Not relevant.
添加/删除Add/Remove 可在已启用复制且具有托管磁盘的 Azure VM 上添加托管磁盘。You can add managed disks on replication-enabled Azure VMs with managed disks. 不能在已启用复制的 Azure VM 上删除磁盘。You cannot remove disks on replication-enabled Azure VMs. 启用复制后,无法添加或删除磁盘。You can't add or remove disks after replication is enabled. 要添加磁盘,请禁用再重新启用复制。Disable and then reenable replication to add a disk. 启用复制后,无法添加或删除磁盘。You can't add or remove disks after replication is enabled. 先禁用,然后再重新启用复制。Disable and then reenable replication.
故障转移Failover 如果某项应用需要你已排除的某个磁盘,则需要在故障转移后手动创建该磁盘,以便复制应用能够运行。If an app needs a disk that you excluded, after failover you need to create the disk manually so that the replicated app can run.

或者,可在 VM 故障转移期间,通过将 Azure 自动化集成到恢复计划来创建磁盘。Alternatively, you can create the disk during VM failover, by integrating Azure automation into a recovery plan.
如果排除某应用需要的磁盘,则要在故障转移后在 Azure 中手动创建该磁盘。If you exclude a disk that an app needs, create it manually in Azure after failover. 如果排除某应用需要的磁盘,则要在故障转移后在 Azure 中手动创建该磁盘。If you exclude a disk that an app needs, create it manually in Azure after failover.
本地故障回复 - 手动创建的磁盘On-premises failback-disks created manually 不相关Not relevant Windows VM:Azure 中手动创建的磁盘不会故障回复。Windows VMs: Disks created manually in Azure aren't failed back. 例如,如果故障转移 3 个磁盘并在 Azure VM 中直接创建 2 个磁盘,则之后仅对故障转移的 3 个磁盘进行故障回复。For example, if you fail over three disks and create two disks directly on an Azure VM, only the three disks that were failed over are then failed back.

Linux VM:Azure 中手动创建的磁盘会故障回复。Linux VMs: Disks created manually in Azure are failed back. 例如,如果故障转移 3 个磁盘,并在 Azure VM 中创建 2 个磁盘,则全部 5 个磁盘都将故障回复。For example, if you fail over three disks and create two disks on an Azure VM, all five will be failed back. 无法从故障回复中排除手动创建的磁盘。You can't exclude disks that were created manually from failback.
Azure 中手动创建的磁盘不会故障回复。Disks created manually in Azure aren't failed back. 例如,如果故障转移 3 个磁盘并直接在 Azure VM 中创建 2 个磁盘,则将仅对故障转移的 3 个磁盘进行故障回复。For example, if you fail over three disks and create two disks directly on an Azure VM, only three disks that were failed over will be failed back.
本地故障回复 - 排除的磁盘On-premises failback-Excluded disks 不相关Not relevant 如果故障回复到原始计算机,则故障回复 VM 磁盘配置不包含排除的磁盘。If you fail back to the original machine, the failback VM disk configuration doesn't include the excluded disks. 无法在故障回复 VM 上使用免于从 VMware 复制到 Azure 的磁盘。Disks that were excluded from VMware to Azure replication aren't available on the failback VM. 故障回复到原始 Hyper-V 位置时,故障回复 VM 磁盘配置与原始源 VM 磁盘的配置保持一致。When failback is to the original Hyper-V location, the failback VM disk configuration remains the same as that of original source VM disk. 可在故障回复 VM 上使用免于从 Hyper-V 站点复制到 Azure 的磁盘。Disks that were excluded from Hyper-V site to Azure replication are available on the failback VM.

典型方案Typical scenarios

数据改动导致出现大量排除首选项的示例包括导页面文件 (pagefile.sys) 的写入,以及到 Microsoft SQL Server 的 tempdb 文件的写入。Examples of data churn that are great candidates for exclusion include writes to a paging file (pagefile.sys), and writes to the tempdb file of Microsoft SQL Server. 页面文件和 tempdb 文件可登记大量改动,具体取决于工作负载和存储子系统。Depending on the workload and the storage subsystem, the paging and tempdb files can register a significant amount of churn. 将此类型的数据复制到 Azure 需耗用大量资源。Replicating this type of data to Azure is resource-intensive.

  • 如果 VM 具有同时包含操作系统和页面文件的单个虚拟磁盘,则可通过以下方法优化复制:To optimize replication for a VM with a single virtual disk that includes both the operating system and the paging file, you could:

    1. 将单个虚拟磁盘拆分成两个虚拟磁盘。Split the single virtual disk into two virtual disks. 一个虚拟磁盘包含操作系统,另一个包含页面文件。One virtual disk has the operating system, and the other has the paging file.
    2. 从复制中排除页面文件磁盘。Exclude the paging file disk from replication.
  • 如果磁盘同时包含 Microsoft SQL Server tempdb 文件和系统数据库文件,则可通过以下方法优化复制:To optimize replication for a disk that includes both the Microsoft SQL Server tempdb file and the system database file, you could:

    1. 在两个不同的磁盘上保存系统数据库和 tempdb。Keep the system database and tempdb on two different disks.
    2. 从复制中排除 tempdb 磁盘。Exclude the tempdb disk from replication.

示例 1:排除 SQL Server tempdb 磁盘Example 1: Exclude the SQL Server tempdb disk

我们来看看如何处理源 SQL Server Windows VM (**SalesDB***) 的磁盘排除和故障转移操作,其中我们要排除 tempdb。Let's look at how to handle disk exclusion, failover, and failover for a source SQL Server Windows VM - **SalesDB***, for which we want to exclude tempdb.

将磁盘排除在复制之外Exclude disks from replication

源 Windows VM SalesDB 上有以下磁盘。We have these disks on the source Windows VM SalesDB.

磁盘名称Disk name 来宾 OS 磁盘Guest OS disk 驱动器号Drive letter 磁盘数据类型Disk data type
DB-Disk0-OSDB-Disk0-OS Disk0Disk0 C:C:\ 操作系统磁盘。Operating system disk.
DB-Disk1DB-Disk1 Disk1Disk1 D:D:\ SQL 系统数据库和用户数据库 1。SQL system database and User Database1.
DB-Disk2(已从保护中排除该磁盘)DB-Disk2 (Excluded the disk from protection) Disk2Disk2 E:E:\ 临时文件。Temp files.
DB-Disk3(已从保护中排除该磁盘)DB-Disk3 (Excluded the disk from protection) Disk3Disk3 F:F:\ SQL tempdb 数据库。SQL tempdb database.

文件夹路径 - F:\MSSQL\Data\。Folder path - F:\MSSQL\Data. 请在故障转移之前记下文件夹路径。Make a note of the folder path before failover.
DB-Disk4DB-Disk4 Disk4Disk4 G:G:\ 用户数据库 2User Database2
  1. 为 SalesDB VM 启用复制。We enable replication for the SalesDB VM.
  2. 将 Disk2 和 Disk3 排除在复制之外,因为这些磁盘上的数据改动是临时的。We exclude Disk2 and Disk3 from replication because data churn on those disks is temporary.

在故障转移期间处理磁盘Handle disks during failover

由于未复制磁盘,因此在你故障转移到 Azure 时,故障转移后创建的 Azure VM 上没有这些磁盘。Since disks aren't replicated, when you fail over to Azure these disks aren't present on the Azure VM created after failover. Azure VM 具有下表汇总的磁盘。The Azure VM has the disks summarized in this table.

来宾 OS 磁盘Guest OS disk 驱动器号Drive letter 磁盘数据类型Disk data type
Disk0Disk0 C:C:\ 操作系统磁盘。Operating system disk.
Disk1Disk1 E:E:\ 临时存储Temporary storage

Azure 添加了该磁盘。Azure adds this disk. 由于 Disk2 和 Disk3 已被排除在复制之外,因此 E: 是可用列表中的第一个驱动器号。Because Disk2 and Disk3 were excluded from replication, E: is the first drive letter from the available list. Azure 将 E: 分配给临时存储卷。Azure assigns E: to the temporary storage volume. 已复制磁盘的其他驱动器号保持不变。Other drive letters for replicated disks remain the same.
Disk2Disk2 D:D:\ SQL 系统数据库和用户数据库 1SQL system database and User Database1
Disk3Disk3 G:G:\ 用户数据库 2User Database2

在我们的示例中,由于 Disk3(SQL 临时磁盘)已被排除在复制之外且在 Azure VM 上不可用,因此 SQL 服务的状态为“已停止”,它需要 F:\MSSQL\Data 路径。In our example, since Disk3, the SQL tempdb disk, was excluded from replication and isn't available on the Azure VM, the SQL service is in a stopped state, and it needs the F:\MSSQL\Data path. 可通过多种方式创建此路径:You can create this path in a couple of ways:

  • 在故障转移后添加新磁盘,并分配 tempdb 文件夹路径。Add a new disk after failover, and assign tempdb folder path.
  • 使用现有临时存储磁盘作为 tempdb 文件夹路径。Use an existing temporary storage disk for the tempdb folder path.

在故障转移后添加新磁盘Add a new disk after failover

  1. 在故障转移前,记下 SQL tempdb.mdf 和 tempdb.ldf 的路径。Write down the paths of SQL tempdb.mdf and tempdb.ldf before failover.
  2. 在 Azure 门户中,将新磁盘添加到故障转移 Azure VM。From the Azure portal, add a new disk to the failover Azure VM. 磁盘大小应等于大于源 SQL tempdb 磁盘 (Disk3) 的大小。The disk should be the same size (or larger) as the source SQL tempdb disk (Disk3).
  3. 登录 Azure VM。Sign in to the Azure VM.
  4. 在磁盘管理 (diskmgmt.msc) 控制台中,初始化并格式化新添加的磁盘。From the disk management (diskmgmt.msc) console, initialize and format the newly added disk.
  5. 分配与 SQL tempdb 磁盘 (F:) 所用驱动器号相同的驱动器号Assign the same drive letter that was used by the SQL tempdb disk (F:)
  6. 在 F: 卷上创建 tempdb 文件夹 (F:\MSSQL\Data)。Create a tempdb folder on the F: volume (F:\MSSQL\Data).
  7. 从服务控制台启动 SQL 服务。Start the SQL service from the service console.

使用现有的临时存储磁盘Use an existing temporary storage disk

  1. 打开命令提示符。Open a command prompt.

  2. 通过命令提示符在恢复模式下运行 SQL Server。Run SQL Server in recovery mode from the command prompt.

    Net start MSSQLSERVER /f / T3608
    
  3. 运行以下 sqlcmd,将 tempdb 路径更改为新路径。Run the following sqlcmd to change the tempdb path to the new path.

    sqlcmd -A -S SalesDB        **Use your SQL DBname**
    USE master;     
    GO      
    ALTER DATABASE tempdb       
    MODIFY FILE (NAME = tempdev, FILENAME = 'E:\MSSQL\tempdata\tempdb.mdf');
    GO      
    ALTER DATABASE tempdb       
    MODIFY FILE (NAME = templog, FILENAME = 'E:\MSSQL\tempdata\templog.ldf');       
    GO
    
  4. 停止 Microsoft SQL Server 服务。Stop the Microsoft SQL Server service.

    Net stop MSSQLSERVER
    
  5. 启动 Microsoft SQL Server 服务。Start the Microsoft SQL Server service.

    Net start MSSQLSERVER
    

VMware VM:在故障回复期间将磁盘恢复到原始位置VMware VMs: Disks during failback to original location

现在,让我们来看看在你故障回复到原始本地位置时如何处理 VMware VM 上的磁盘。Now let's see how to handle disks on VMware VMs when you fail back to your original on-premises location.

  • 在 Azure 中创建的磁盘:由于我们的示例使用的是 Windows VM,因此在故障回复或重新保护 VM 时,你在 Azure 中手动复制的磁盘不会复制回到你的站点。Disks created in Azure: Since our example uses a Windows VM, disks that you create manually in Azure aren't replicated back to your site when you fail back or reprotect a VM.
  • Azure 中的临时存储磁盘:临时存储磁盘不会复制回到本地主机。Temporary storage disk in Azure: The temporary storage disk isn't replicated back to on-premises hosts.
  • 排除的磁盘:故障回复后,无法在本地 VM 上使用免于从 VMware 复制到 Azure 的磁盘。Excluded disks: Disks that were excluded from VMware to Azure replication aren't available on the on-premises VM after failback.

在将 VMware VM 故障回复到原始位置时,Azure VM 磁盘设置如下所示。Before you fail back the VMware VMs to the original location, the Azure VM disk settings are as follows.

来宾 OS 磁盘Guest OS disk 驱动器号Drive letter 磁盘数据类型Disk data type
Disk0Disk0 C:C:\ 操作系统磁盘。Operating system disk.
Disk1Disk1 E:E:\ 临时存储。Temporary storage.
Disk2Disk2 D:D:\ SQL 系统数据库和用户数据库 1。SQL system database and User Database1.
Disk3Disk3 G:G:\ 用户数据库 2。User Database2.

故障回复后,原始位置中的 VMware VM 具有下表汇总的磁盘。After failback, the VMware VM in the original location has the disks summarized in the table.

来宾 OS 磁盘Guest OS disk 驱动器号Drive letter 磁盘数据类型Disk data type
Disk0Disk0 C:C:\ 操作系统磁盘。Operating system disk.
Disk1Disk1 D:D:\ SQL 系统数据库和用户数据库 1。SQL system database and User Database1.
Disk2Disk2 G:G:\ 用户数据库 2。User Database2.

Hyper-V VM:在故障回复期间将磁盘恢复到原始位置Hyper-V VMs: Disks during failback to original location

现在,让我们来看看在你故障回复到原始本地位置时如何处理 Hyper-V VM 上的磁盘。Now let's see how to handle disks on Hyper-V VMs when you fail back to your original on-premises location.

  • 在 Azure 中创建的磁盘:在故障回复或重新保护 VM 时,你在 Azure 中手动复制的磁盘不会复制回到你的站点。Disks created in Azure: Disks that you create manually in Azure aren't replicated back to your site when you fail back or reprotect a VM.
  • Azure 中的临时存储磁盘:临时存储磁盘不会复制回到本地主机。Temporary storage disk in Azure: The temporary storage disk isn't replicated back to on-premises hosts.
  • 排除的磁盘:故障回复后,VM 磁盘配置与原始 VM 磁盘配置相同。Excluded disks: After failback the VM disk configuration is the same as the original VM disk configuration. 可在故障回复 VM 上使用免于从 Hyper-V 复制到 Azure 的磁盘。Disks that were excluded from replication from Hyper-V to Azure are available on the failback VM.

在将 Hyper-V VM 故障回复到原始位置时,Azure VM 磁盘设置如下所示。Before you fail back the Hyper-V VMs to the original location, the Azure VM disk settings are as follows.

来宾 OS 磁盘Guest OS disk 驱动器号Drive letter 磁盘数据类型Disk data type
Disk0Disk0 C:C:\ 操作系统磁盘。Operating system disk.
Disk1Disk1 E:E:\ 临时存储。Temporary storage.
Disk2Disk2 D:D:\ SQL 系统数据库和用户数据库 1。SQL system database and User Database1.
Disk3Disk3 G:G:\ 用户数据库 2。User Database2.

在按计划从 Azure 故障转移(故障回复)到本地 Hyper-V 之后,原始位置中的 Hyper-V VM 具有下表汇总的磁盘。After planned failover (failback) from Azure to on-premises Hyper-V, the Hyper-V VM in the original location has the disks summarized in the table.

磁盘名称Disk Name 来宾 OS 磁盘编号Guest OS disk# 驱动器号Drive letter 磁盘数据类型Disk data type
DB-Disk0-OSDB-Disk0-OS Disk0Disk0 C:C:\ 操作系统磁盘。Operating system disk.
DB-Disk1DB-Disk1 Disk1Disk1 D:D:\ SQL 系统数据库和用户数据库 1。SQL system database and User Database1.
DB Disk2(排除的磁盘)DB-Disk2 (Excluded disk) Disk2Disk2 E:E:\ 临时文件。Temp files.
DB-Disk3(排除的磁盘)DB-Disk3 (Excluded disk) Disk3Disk3 F:F:\ SQL tempdb 数据库SQL tempdb database

文件夹路径 (F:\MSSQL\Data)。Folder path (F:\MSSQL\Data).
DB-Disk4DB-Disk4 Disk4Disk4 G:G:\ 用户数据库 2User Database2

示例 2:排除页面文件磁盘Example 2: Exclude the paging file disk

让我们看看如何处理源 Windows VM 的磁盘排除和故障转移,其中我们要排除 D 驱动器和备用驱动器上 pagefile.sys 文件磁盘。Let's look at how to handle disk exclusion, failover, and failover for a source Windows VM, for which we want to exclude the pagefile.sys file disk on both the D drive, and an alternate drive.

D 驱动器上的页面文件Paging file on the D drive

源 VM 上有以下磁盘。We have these disks on the source VM.

磁盘名称Disk name 来宾 OS 磁盘Guest OS disk 驱动器号Drive letter 磁盘数据类型Disk data type
DB-Disk0-OSDB-Disk0-OS Disk0Disk0 C:C:\ 操作系统磁盘Operating system disk
DB-Disk1(排除在复制之外)DB-Disk1 (Exclude from replication) Disk1Disk1 D:D:\ pagefile.syspagefile.sys
DB-Disk2DB-Disk2 Disk2Disk2 E:E:\ 用户数据 1User data 1
DB-Disk3DB-Disk3 Disk3Disk3 F:F:\ 用户数据 2User data 2

源 VM 上的页面文件设置如下所示:Our paging file settings on the source VM are as follows:

源虚拟机上的页面文件设置

  1. 为 VM 启用复制。We enable replication for the VM.
  2. 将 DB-Disk1 排除在复制之外。We exclude DB-Disk1 from replication.

故障转移后的磁盘Disks after failover

故障转移后,Azure VM 具有下表汇总的磁盘。After failover the Azure VM has the disks summarized in the table.

磁盘名称Disk name 来宾操作系统磁盘编号Guest operating system disk# 驱动器号Drive letter 磁盘上的数据类型Data type on the disk
DB-Disk0-OSDB-Disk0-OS Disk0Disk0 C:C:\ 操作系统磁盘Operating system disk
DB-Disk1DB-Disk1 Disk1Disk1 D:D:\ 临时存储/pagefile.sysTemporary storage/pagefile.sys

由于 DB-Disk1 (D:) 已被排除,因此 D: 是可用列表中的第一个驱动器号。Because DB-Disk1 (D:) was excluded, D: is the first drive letter from the available list.

Azure 将 D: 分配给临时存储卷。Azure assigns D: to the temporary storage volume.

由于 D: 可用,VM 页面文件设置保持不变。Because D: is available, the VM paging file setting remains the same).
DB-Disk2DB-Disk2 Disk2Disk2 E:E:\ 用户数据 1User data 1
DB-Disk3DB-Disk3 Disk3Disk3 F:F:\ 用户数据 2User data 2

Azure VM 上的页面文件设置如下所示:Our paging file settings on the Azure VM are as follows:

源虚拟机上的页面文件设置

其他驱动器(非 D:)上的页面文件Paging file on another drive (not D:)

让我们来看一个示例,其中页面文件不位于 D 驱动器上。Let's look at example in which the paging file isn't on the D drive.

源 VM 上有以下磁盘。We have these disks on the source VM.

磁盘名称Disk name 来宾 OS 磁盘Guest OS disk 驱动器号Drive letter 磁盘数据类型Disk data type
DB-Disk0-OSDB-Disk0-OS Disk0Disk0 C:C:\ 操作系统磁盘Operating system disk
DB-Disk1(排除在复制之外)DB-Disk1 (Exclude from replication) Disk1Disk1 G:G:\ pagefile.syspagefile.sys
DB-Disk2DB-Disk2 Disk2Disk2 E:E:\ 用户数据 1User data 1
DB-Disk3DB-Disk3 Disk3Disk3 F:F:\ 用户数据 2User data 2

本地 VM 上的页面文件设置如下所示:Our paging file settings on the on-premises VM are as follows:

源虚拟机上的页面文件设置

  1. 为 VM 启用复制。We enable replication for the VM.
  2. 将 DB-Disk1 排除在复制之外。We exclude DB-Disk1 from replication.

故障转移后的磁盘Disks after failover

故障转移后,Azure VM 具有下表汇总的磁盘。After failover the Azure VM has the disks summarized in the table.

磁盘名称Disk name 来宾 OS 磁盘编号Guest OS disk# 驱动器号Drive letter 磁盘数据类型Disk data type
DB-Disk0-OSDB-Disk0-OS Disk0Disk0 C:C:\ 操作系统磁盘Operating system disk
DB-Disk1DB-Disk1 Disk1Disk1 D:D:\ 临时存储Temporary storage

由于 D: 是可用列表中的首个驱动器号,Azure 将 D: 分配给临时存储卷。Because D: is the first drive letter from available the list, Azure assigns D: to the temporary storage volume.

对于所有复制的磁盘,驱动器号保持不变。For all the replicated disks, the drive letter remains the same.

由于 G: 磁盘不可用,因此系统将使用 C: 驱动器存储页面文件。Because the G: disk isn't available, the system will use the C: drive for the paging file.
DB-Disk2DB-Disk2 Disk2Disk2 E:E:\ 用户数据 1User data 1
DB-Disk3DB-Disk3 Disk3Disk3 F:F:\ 用户数据 2User data 2

Azure VM 上的页面文件设置如下所示:Our paging file settings on the Azure VM are as follows:

源虚拟机上的页面文件设置

后续步骤Next steps

  • 详细了解临时存储磁盘的指导原则:Learn more about guidelines for the temporary storage disk:
    • 了解如何在 Azure VM 中使用 SSD 来存储 SQL Server TempDB 和缓冲池扩展Learn about using SSDs in Azure VMs to store SQL Server TempDB and Buffer Pool Extensions
    • 查看 Azure VM 中 SQL Server 的性能最佳做法。Review performance best practices for SQL Server in Azure VMs.
  • 设置并运行部署后,请 详细了解 不同类型的故障转移。After your deployment is set up and running, learn more about different types of failover.