简体中文版经机器翻译而成，仅供参考。如与英语版出现任何冲突，应以英语版为准。
配置 MetroCluster 以进行过渡
贡献者
建议更改
PDF
要为过渡准备配置，请将新节点添加到现有 MetroCluster 配置中，然后将数据移动到新节点。
在维护之前发送自定义 AutoSupport 消息
在执行维护问题描述之前，您应发送 AutoSupport 消息以通知 NetApp 技术支持正在进行维护。告知技术支持正在进行维护，可防止他们在假定已发生中断的情况下创建案例。
关于此任务
必须在每个 MetroCluster 站点上执行此任务。
步骤
-
要防止自动生成支持案例，请发送一条 AutoSupport 消息以指示正在进行维护：
ssystem node AutoSupport invoke -node * -type all -message MAINT=maintenance-window-in-hours"
maintenance-window-in-hours" 指定维护时段的长度，最长为 72 小时。如果在该时间过后完成维护，您可以调用一条 AutoSupport 消息，指示维护期结束：ssystem node AutoSupport invoke -node * -type all -message MAINT=end -
在配对集群上重复此命令。
启用过渡模式并禁用集群 HA
您必须启用 MetroCluster 过渡模式，以允许旧节点和新节点在 MetroCluster 配置中同时运行，并禁用集群 HA 。
-
启用过渡：
-
更改为高级权限级别：
set -privilege advanced -
启用过渡模式：
MetroCluster transition enable -transition-mode non-disruptive
仅在一个集群上运行此命令。
cluster_A::*> metrocluster transition enable -transition-mode non-disruptive Warning: This command enables the start of a "non-disruptive" MetroCluster FC-to-IP transition. It allows the addition of hardware for another DR group that uses IP fabrics, and the removal of a DR group that uses FC fabrics. Clients will continue to access their data during a non-disruptive transition. Automatic unplanned switchover will also be disabled by this command. Do you want to continue? {y|n}: y cluster_A::*>-
返回到管理权限级别：
set -privilege admin
-
-
验证是否已在两个集群上启用过渡。
cluster_A::> metrocluster transition show-mode Transition Mode non-disruptive cluster_A::*> cluster_B::*> metrocluster transition show-mode Transition Mode non-disruptive Cluster_B::>
-
禁用集群 HA 。
您必须在两个集群上运行此命令。 cluster_A::*> cluster ha modify -configured false Warning: This operation will unconfigure cluster HA. Cluster HA must be configured on a two-node cluster to ensure data access availability in the event of storage failover. Do you want to continue? {y|n}: y Notice: HA is disabled. cluster_A::*> cluster_B::*> cluster ha modify -configured false Warning: This operation will unconfigure cluster HA. Cluster HA must be configured on a two-node cluster to ensure data access availability in the event of storage failover. Do you want to continue? {y|n}: y Notice: HA is disabled. cluster_B::*> -
验证是否已禁用集群 HA 。
您必须在两个集群上运行此命令。 cluster_A::> cluster ha show High Availability Configured: false Warning: Cluster HA has not been configured. Cluster HA must be configured on a two-node cluster to ensure data access availability in the event of storage failover. Use the "cluster ha modify -configured true" command to configure cluster HA. cluster_A::> cluster_B::> cluster ha show High Availability Configured: false Warning: Cluster HA has not been configured. Cluster HA must be configured on a two-node cluster to ensure data access availability in the event of storage failover. Use the "cluster ha modify -configured true" command to configure cluster HA. cluster_B::>
将 MetroCluster IP 节点加入集群
您必须将四个新的 MetroCluster IP 节点添加到现有 MetroCluster 配置中。
关于此任务
您必须在两个集群上执行此任务。
步骤
-
将 MetroCluster IP 节点添加到现有 MetroCluster 配置中。
-
将第一个MetroCluster IP节点(node_A_3-IP)加入现有MetroCluster FC配置。
Welcome to the cluster setup wizard. You can enter the following commands at any time: "help" or "?" - if you want to have a question clarified, "back" - if you want to change previously answered questions, and "exit" or "quit" - if you want to quit the cluster setup wizard. Any changes you made before quitting will be saved. You can return to cluster setup at any time by typing "cluster setup". To accept a default or omit a question, do not enter a value. This system will send event messages and periodic reports to NetApp Technical Support. To disable this feature, enter autosupport modify -support disable within 24 hours. Enabling AutoSupport can significantly speed problem determination and resolution, should a problem occur on your system. For further information on AutoSupport, see: http://support.netapp.com/autosupport/ Type yes to confirm and continue {yes}: yes Enter the node management interface port [e0M]: Enter the node management interface IP address: 172.17.8.93 Enter the node management interface netmask: 255.255.254.0 Enter the node management interface default gateway: 172.17.8.1 A node management interface on port e0M with IP address 172.17.8.93 has been created. Use your web browser to complete cluster setup by accessing https://172.17.8.93 Otherwise, press Enter to complete cluster setup using the command line interface: Do you want to create a new cluster or join an existing cluster? {create, join}: join Existing cluster interface configuration found: Port MTU IP Netmask e0c 9000 169.254.148.217 255.255.0.0 e0d 9000 169.254.144.238 255.255.0.0 Do you want to use this configuration? {yes, no} [yes]: yes . . . -
将第二个MetroCluster IP节点(node_A_4-IP)加入现有MetroCluster FC配置。
-
-
重复上述步骤、将node_B_3-IP和node_B_4-IP加入cluster_B
配置集群间 LIF ，创建 MetroCluster 接口以及镜像根聚合
您必须创建集群对等 LIF ，并在新的 MetroCluster IP 节点上创建 MetroCluster 接口。
关于此任务
示例中使用的主端口是特定于平台的。您应使用特定于 MetroCluster IP 节点平台的相应主端口。
步骤
-
在新的 MetroCluster IP 节点上， "配置集群间 LIF"。
-
在每个站点上，验证是否已配置集群对等：
cluster peer show以下示例显示了 cluster_A 上的集群对等配置：
cluster_A:> cluster peer show Peer Cluster Name Cluster Serial Number Availability Authentication ------------------------- --------------------- -------------- -------------- cluster_B 1-80-000011 Available ok
以下示例显示了 cluster_B 上的集群对等配置：
cluster_B:> cluster peer show Peer Cluster Name Cluster Serial Number Availability Authentication ------------------------- --------------------- -------------- -------------- cluster_A 1-80-000011 Available ok
-
为 MetroCluster IP 节点配置 DR 组：
MetroCluster configuration-settings dr-group create -partner-cluster`
cluster_A::> metrocluster configuration-settings dr-group create -partner-cluster cluster_B -local-node node_A_3-IP -remote-node node_B_3-IP [Job 259] Job succeeded: DR Group Create is successful. cluster_A::>
-
验证是否已创建灾难恢复组。
MetroCluster configuration-settings dr-group showcluster_A::> metrocluster configuration-settings dr-group show DR Group ID Cluster Node DR Partner Node ----------- -------------------------- ------------------ ------------------ 2 cluster_A node_A_3-IP node_B_3-IP node_A_4-IP node_B_4-IP cluster_B node_B_3-IP node_A_3-IP node_B_4-IP node_A_4-IP 4 entries were displayed. cluster_A::>您会注意到，在运行
MetroCluster configuration-settings dr-group show命令时，旧 MetroCluster FC 节点（ DR 组 1 ）的 DR 组未列出。您可以在两个站点上使用
MetroCluster node show命令列出所有节点。cluster_A::> metrocluster node show DR Configuration DR Group Cluster Node State Mirroring Mode ----- ------- ------------------ -------------- --------- -------------------- 1 cluster_A node_A_1-FC configured enabled normal node_A_2-FC configured enabled normal cluster_B node_B_1-FC configured enabled normal node_B_2-FC configured enabled normal 2 cluster_A node_A_3-IP ready to configure - - node_A_4-IP ready to configure - - cluster_B::> metrocluster node show DR Configuration DR Group Cluster Node State Mirroring Mode ----- ------- ------------------ -------------- --------- -------------------- 1 cluster_B node_B_1-FC configured enabled normal node_B_2-FC configured enabled normal cluster_A node_A_1-FC configured enabled normal node_A_2-FC configured enabled normal 2 cluster_B node_B_3-IP ready to configure - - node_B_4-IP ready to configure - - -
为新加入的 MetroCluster IP 节点配置 MetroCluster IP 接口：
MetroCluster configuration-settings interface create -cluster-name`
请参见 "配置和连接 MetroCluster IP 接口" 配置 IP 接口时的注意事项。
您可以从任一集群配置 MetroCluster IP 接口。 cluster_A::> metrocluster configuration-settings interface create -cluster-name cluster_A -home-node node_A_3-IP -home-port e1a -address 172.17.26.10 -netmask 255.255.255.0 [Job 260] Job succeeded: Interface Create is successful. cluster_A::> metrocluster configuration-settings interface create -cluster-name cluster_A -home-node node_A_3-IP -home-port e1b -address 172.17.27.10 -netmask 255.255.255.0 [Job 261] Job succeeded: Interface Create is successful. cluster_A::> metrocluster configuration-settings interface create -cluster-name cluster_A -home-node node_A_4-IP -home-port e1a -address 172.17.26.11 -netmask 255.255.255.0 [Job 262] Job succeeded: Interface Create is successful. cluster_A::> :metrocluster configuration-settings interface create -cluster-name cluster_A -home-node node_A_4-IP -home-port e1b -address 172.17.27.11 -netmask 255.255.255.0 [Job 263] Job succeeded: Interface Create is successful. cluster_A::> metrocluster configuration-settings interface create -cluster-name cluster_B -home-node node_B_3-IP -home-port e1a -address 172.17.26.12 -netmask 255.255.255.0 [Job 264] Job succeeded: Interface Create is successful. cluster_A::> metrocluster configuration-settings interface create -cluster-name cluster_B -home-node node_B_3-IP -home-port e1b -address 172.17.27.12 -netmask 255.255.255.0 [Job 265] Job succeeded: Interface Create is successful. cluster_A::> metrocluster configuration-settings interface create -cluster-name cluster_B -home-node node_B_4-IP -home-port e1a -address 172.17.26.13 -netmask 255.255.255.0 [Job 266] Job succeeded: Interface Create is successful. cluster_A::> metrocluster configuration-settings interface create -cluster-name cluster_B -home-node node_B_4-IP -home-port e1b -address 172.17.27.13 -netmask 255.255.255.0 [Job 267] Job succeeded: Interface Create is successful.
-
验证是否已创建 MetroCluster IP 接口：
MetroCluster configuration-settings interface showcluster_A::>metrocluster configuration-settings interface show DR Config Group Cluster Node Network Address Netmask Gateway State ----- ------- ------- --------------- --------------- --------------- --------- 2 cluster_A node_A_3-IP Home Port: e1a 172.17.26.10 255.255.255.0 - completed Home Port: e1b 172.17.27.10 255.255.255.0 - completed node_A_4-IP Home Port: e1a 172.17.26.11 255.255.255.0 - completed Home Port: e1b 172.17.27.11 255.255.255.0 - completed cluster_B node_B_3-IP Home Port: e1a 172.17.26.13 255.255.255.0 - completed Home Port: e1b 172.17.27.13 255.255.255.0 - completed node_B_3-IP Home Port: e1a 172.17.26.12 255.255.255.0 - completed Home Port: e1b 172.17.27.12 255.255.255.0 - completed 8 entries were displayed. cluster_A> -
连接 MetroCluster IP 接口：
MetroCluster configuration-settings connection connect
此命令可能需要几分钟才能完成。 cluster_A::> metrocluster configuration-settings connection connect cluster_A::>
-
验证是否已正确建立连接：
MetroCluster configuration-settings connection showcluster_A::> metrocluster configuration-settings connection show DR Source Destination Group Cluster Node Network Address Network Address Partner Type Config State ----- ------- ------- --------------- --------------- ------------ ------------ 2 cluster_A node_A_3-IP** Home Port: e1a 172.17.26.10 172.17.26.11 HA Partner completed Home Port: e1a 172.17.26.10 172.17.26.12 DR Partner completed Home Port: e1a 172.17.26.10 172.17.26.13 DR Auxiliary completed Home Port: e1b 172.17.27.10 172.17.27.11 HA Partner completed Home Port: e1b 172.17.27.10 172.17.27.12 DR Partner completed Home Port: e1b 172.17.27.10 172.17.27.13 DR Auxiliary completed node_A_4-IP Home Port: e1a 172.17.26.11 172.17.26.10 HA Partner completed Home Port: e1a 172.17.26.11 172.17.26.13 DR Partner completed Home Port: e1a 172.17.26.11 172.17.26.12 DR Auxiliary completed Home Port: e1b 172.17.27.11 172.17.27.10 HA Partner completed Home Port: e1b 172.17.27.11 172.17.27.13 DR Partner completed Home Port: e1b 172.17.27.11 172.17.27.12 DR Auxiliary completed DR Source Destination Group Cluster Node Network Address Network Address Partner Type Config State ----- ------- ------- --------------- --------------- ------------ ------------ 2 cluster_B node_B_4-IP Home Port: e1a 172.17.26.13 172.17.26.12 HA Partner completed Home Port: e1a 172.17.26.13 172.17.26.11 DR Partner completed Home Port: e1a 172.17.26.13 172.17.26.10 DR Auxiliary completed Home Port: e1b 172.17.27.13 172.17.27.12 HA Partner completed Home Port: e1b 172.17.27.13 172.17.27.11 DR Partner completed Home Port: e1b 172.17.27.13 172.17.27.10 DR Auxiliary completed node_B_3-IP Home Port: e1a 172.17.26.12 172.17.26.13 HA Partner completed Home Port: e1a 172.17.26.12 172.17.26.10 DR Partner completed Home Port: e1a 172.17.26.12 172.17.26.11 DR Auxiliary completed Home Port: e1b 172.17.27.12 172.17.27.13 HA Partner completed Home Port: e1b 172.17.27.12 172.17.27.10 DR Partner completed Home Port: e1b 172.17.27.12 172.17.27.11 DR Auxiliary completed 24 entries were displayed. cluster_A::> -
验证磁盘自动分配和分区：
disk show -pool Pool1cluster_A::> disk show -pool Pool1 Usable Disk Container Container Disk Size Shelf Bay Type Type Name Owner ---------------- ---------- ----- --- ------- ----------- --------- -------- 1.10.4 - 10 4 SAS remote - node_B_2 1.10.13 - 10 13 SAS remote - node_B_2 1.10.14 - 10 14 SAS remote - node_B_1 1.10.15 - 10 15 SAS remote - node_B_1 1.10.16 - 10 16 SAS remote - node_B_1 1.10.18 - 10 18 SAS remote - node_B_2 ... 2.20.0 546.9GB 20 0 SAS aggregate aggr0_rha1_a1 node_a_1 2.20.3 546.9GB 20 3 SAS aggregate aggr0_rha1_a2 node_a_2 2.20.5 546.9GB 20 5 SAS aggregate rha1_a1_aggr1 node_a_1 2.20.6 546.9GB 20 6 SAS aggregate rha1_a1_aggr1 node_a_1 2.20.7 546.9GB 20 7 SAS aggregate rha1_a2_aggr1 node_a_2 2.20.10 546.9GB 20 10 SAS aggregate rha1_a1_aggr1 node_a_1 ... 43 entries were displayed. cluster_A::>
在配置了高级驱动器分区(ADP)的系统上、容器类型为"共享"、而不是"远程"、如示例输出所示。 -
镜像根聚合：
storage aggregate mirror -aggregate aggr0_node_A_3_IP
您必须在每个 MetroCluster IP 节点上完成此步骤。 cluster_A::> aggr mirror -aggregate aggr0_node_A_3_IP Info: Disks would be added to aggregate "aggr0_node_A_3_IP"on node "node_A_3-IP" in the following manner: Second Plex RAID Group rg0, 3 disks (block checksum, raid_dp) Usable Physical Position Disk Type Size Size ---------- ------------------------- ---------- -------- -------- dparity 4.20.0 SAS - - parity 4.20.3 SAS - - data 4.20.1 SAS 546.9GB 558.9GB Aggregate capacity available for volume use would be 467.6GB. Do you want to continue? {y|n}: y cluster_A::> -
验证根聚合是否已镜像：
s存储聚合显示cluster_A::> aggr show Aggregate Size Available Used% State #Vols Nodes RAID Status --------- -------- --------- ----- ------- ------ ---------------- ------------ aggr0_node_A_1_FC 349.0GB 16.84GB 95% online 1 node_A_1-FC raid_dp, mirrored, normal aggr0_node_A_2_FC 349.0GB 16.84GB 95% online 1 node_A_2-FC raid_dp, mirrored, normal aggr0_node_A_3_IP 467.6GB 22.63GB 95% online 1 node_A_3-IP raid_dp, mirrored, normal aggr0_node_A_4_IP 467.6GB 22.62GB 95% online 1 node_A_4-IP raid_dp, mirrored, normal aggr_data_a1 1.02TB 1.01TB 1% online 1 node_A_1-FC raid_dp, mirrored, normal aggr_data_a2 1.02TB 1.01TB 1% online 1 node_A_2-FC raid_dp, mirrored,
完成 MetroCluster IP 节点的添加
您必须将新的 DR 组加入 MetroCluster 配置，并在新节点上创建镜像数据聚合。
步骤
-
根据MetroCluster 具有单个或多个数据聚合来配置它：
如果您的 MetroCluster 配置 …
然后执行此操作 …
多个数据聚合
从任何节点的提示符处，配置 MetroCluster ：
metrocluster configure <node-name>
您必须运行 MetroCluster configure和 * 不 *MetroCluster configure -refresh true一个镜像数据聚合
-
在任何节点的提示符处，更改为高级权限级别：
set -privilege advanced您必须回答
y当系统提示您继续进入高级模式时、您会看到高级模式提示符(*)。 -
使用 ` -allow-with-one-aggregate true` 参数配置 MetroCluster ：
metrocluster configure -allow-with-one-aggregate true -node-name <node-name> -
返回到管理权限级别：
set -privilege admin
最佳做法是、具有多个镜像数据聚合。如果只有一个镜像聚合、则保护程度较低、因为元数据卷位于同一个聚合上、而不是位于不同的聚合上。 -
-
重新启动每个新节点：
node reboot -node <node_name> -inhibit-takeover true
您无需按特定顺序重新启动节点、但应等待一个节点完全启动并建立所有连接后、再重新启动下一个节点。 -
验证节点是否已添加到其 DR 组：
MetroCluster node showcluster_A::> metrocluster node show DR Configuration DR Group Cluster Node State Mirroring Mode ----- ------- ------------------ -------------- --------- -------------------- 1 cluster_A node-A-1-FC configured enabled normal node-A-2-FC configured enabled normal Cluster-B node-B-1-FC configured enabled normal node-B-2-FC configured enabled normal 2 cluster_A node-A-3-IP configured enabled normal node-A-4-IP configured enabled normal Cluster-B node-B-3-IP configured enabled normal node-B-4-IP configured enabled normal 8 entries were displayed. cluster_A::> -
在每个新 MetroCluster 节点上创建镜像数据聚合：
storage aggregate create -aggregate aggregate-name -node node-name -diskcount no-of-disks -mirror true
每个站点必须至少创建一个镜像数据聚合。建议在 MetroCluster IP 节点上为每个站点配置两个镜像数据聚合以托管 MDV 卷，但支持每个站点一个聚合（但不建议这样做）。MetroCluster的一个站点具有一个镜像数据聚合、而另一个站点具有多个镜像数据聚合、这是可以接受的。 以下示例显示了如何在node_A_3-IP上创建聚合。
cluster_A::> storage aggregate create -aggregate data_a3 -node node_A_3-IP -diskcount 10 -mirror t Info: The layout for aggregate "data_a3" on node "node_A_3-IP" would be: First Plex RAID Group rg0, 5 disks (block checksum, raid_dp) Usable Physical Position Disk Type Size Size ---------- ------------------------- ---------- -------- -------- dparity 5.10.15 SAS - - parity 5.10.16 SAS - - data 5.10.17 SAS 546.9GB 547.1GB data 5.10.18 SAS 546.9GB 558.9GB data 5.10.19 SAS 546.9GB 558.9GB Second Plex RAID Group rg0, 5 disks (block checksum, raid_dp) Usable Physical Position Disk Type Size Size ---------- ------------------------- ---------- -------- -------- dparity 4.20.17 SAS - - parity 4.20.14 SAS - - data 4.20.18 SAS 546.9GB 547.1GB data 4.20.19 SAS 546.9GB 547.1GB data 4.20.16 SAS 546.9GB 547.1GB Aggregate capacity available for volume use would be 1.37TB. Do you want to continue? {y|n}: y [Job 440] Job succeeded: DONE cluster_A::> -
验证集群中的所有节点是否运行正常：
cluster show输出应显示
true。health字段。 -
在两个集群上运行以下命令、以确认可以接管并且节点已连接：
s存储故障转移显示cluster_A::> storage failover show Takeover Node Partner Possible State Description -------------- -------------------- --------- ------------------ Node_FC_1 Node_FC_2 true Connected to Node_FC_2 Node_FC_2 Node_FC_1 true Connected to Node_FC_1 Node_IP_1 Node_IP_2 true Connected to Node_IP_2 Node_IP_2 Node_IP_1 true Connected to Node_IP_1 -
确认连接到新加入的MetroCluster IP节点的所有磁盘均存在：
d展示 -
运行以下命令、验证MetroCluster配置的运行状况：
-
MetroCluster check run -
MetroCluster check show`
-
MetroCluster 互连镜像显示 -
MetroCluster 互连适配器 show
-
-
以高级权限将 MDV_CRS 卷从旧节点移动到新节点。
-
显示卷以标识 MDV 卷：
如果每个站点有一个镜像数据聚合，则将两个 MDV 卷移动到此一个聚合。如果您有两个或更多镜像数据聚合，请将每个 MDV 卷移动到其他聚合。 以下示例显示了 volume show 输出中的 MDV 卷：
cluster_A::> volume show Vserver Volume Aggregate State Type Size Available Used% --------- ------------ ------------ ---------- ---- ---------- ---------- ----- ... cluster_A MDV_CRS_2c78e009ff5611e9b0f300a0985ef8c4_A aggr_b1 - RW - - - cluster_A MDV_CRS_2c78e009ff5611e9b0f300a0985ef8c4_B aggr_b2 - RW - - - cluster_A MDV_CRS_d6b0b313ff5611e9837100a098544e51_A aggr_a1 online RW 10GB 9.50GB 0% cluster_A MDV_CRS_d6b0b313ff5611e9837100a098544e51_B aggr_a2 online RW 10GB 9.50GB 0% ... 11 entries were displayed.mple -
设置高级权限级别：
set -privilege advanced -
一次移动一个 MDV 卷：
volume move start -volume mDV-volume -destination-aggregate aggr-on-new-node -vserver vserver-name以下示例显示了将 MDV_CRS_d6b0b313ff5611e9837100a098544e51_A 移动到 node_A_3 上聚合 data_A3 的命令和输出。
cluster_A::*> vol move start -volume MDV_CRS_d6b0b313ff5611e9837100a098544e51_A -destination-aggregate data_a3 -vserver cluster_A Warning: You are about to modify the system volume "MDV_CRS_d6b0b313ff5611e9837100a098544e51_A". This might cause severe performance or stability problems. Do not proceed unless directed to do so by support. Do you want to proceed? {y|n}: y [Job 494] Job is queued: Move "MDV_CRS_d6b0b313ff5611e9837100a098544e51_A" in Vserver "cluster_A" to aggregate "data_a3". Use the "volume move show -vserver cluster_A -volume MDV_CRS_d6b0b313ff5611e9837100a098544e51_A" command to view the status of this operation. -
使用 volume show 命令检查是否已成功移动 MDV 卷：
volume show mDV-name以下输出显示 MDV 卷已成功移动。
cluster_A::*> vol show MDV_CRS_d6b0b313ff5611e9837100a098544e51_B Vserver Volume Aggregate State Type Size Available Used% --------- ------------ ------------ ---------- ---- ---------- ---------- ----- cluster_A MDV_CRS_d6b0b313ff5611e9837100a098544e51_B aggr_a2 online RW 10GB 9.50GB 0%-
返回到管理模式：
set -privilege admin
-