From f3ae38d9c2efee77959bdc83395cc5ff8b10ca41 Mon Sep 17 00:00:00 2001 From: MAOhongming Date: Tue, 30 Jun 2026 11:00:47 +0800 Subject: [PATCH 1/2] Update AI support links and hide Dify bubble --- src/.vuepress/client.ts | 4 ++-- src/.vuepress/client/components/HomePage.vue | 2 +- src/.vuepress/client/homepage.config.ts | 4 ++-- src/.vuepress/client/homepage.config.zh.ts | 4 ++-- src/.vuepress/navbar/en.main.ts | 2 +- src/.vuepress/navbar/zh.main.ts | 2 +- 6 files changed, 9 insertions(+), 9 deletions(-) diff --git a/src/.vuepress/client.ts b/src/.vuepress/client.ts index 53e19076..8b8c901e 100644 --- a/src/.vuepress/client.ts +++ b/src/.vuepress/client.ts @@ -35,7 +35,7 @@ export default defineClientConfig({ // 样式 const style = document.createElement('style') style.textContent = ` - #dify-chatbot-bubble-button { background-color: #1C64F2 !important; } + #dify-chatbot-bubble-button { display: none !important; } #dify-chatbot-bubble-window { width: 35rem !important; height: 80rem !important; position: fixed !important; } .VIpgJd-ZVi9od-ORHb-OEVmcd { display: none !important; height: 0 !important; } .goog-te-banner-frame { display: none !important; height: 0 !important; } @@ -105,4 +105,4 @@ export default defineClientConfig({ } } } -}) \ No newline at end of file +}) diff --git a/src/.vuepress/client/components/HomePage.vue b/src/.vuepress/client/components/HomePage.vue index 05598fb1..76718ed8 100644 --- a/src/.vuepress/client/components/HomePage.vue +++ b/src/.vuepress/client/components/HomePage.vue @@ -202,7 +202,7 @@ const searchSuggestions = useSearchSuggestions({ }) // AI 搜索 URL -const AI_SEARCH_URL = 'https://ai.oneprocloud.com/chat/qWGp3yX8ain2550b' +const AI_SEARCH_URL = 'https://sourcelens.oneprocloud.com/lens/assistants/AI_HyperBDR/chat' // 判断是否为中文环境 const isZh = computed(() => { diff --git a/src/.vuepress/client/homepage.config.ts b/src/.vuepress/client/homepage.config.ts index b8873924..db26269b 100644 --- a/src/.vuepress/client/homepage.config.ts +++ b/src/.vuepress/client/homepage.config.ts @@ -276,7 +276,7 @@ export const homepageSections: HomepageSection[] = [ { title: "AI Support", desc: "AI Support from OneProCloud.", - link: "https://ai.oneprocloud.com/chat/qWGp3yX8ain2550b", + link: "https://sourcelens.oneprocloud.com/lens/assistants/AI_HyperBDR/chat", icon: "fa-solid fa-robot" }, { @@ -309,7 +309,7 @@ export const coreActions: CoreAction[] = [ { title: "AI Support", desc: "AI Support from OneProCloud.", - link: "https://ai.oneprocloud.com/chat/qWGp3yX8ain2550b", + link: "https://sourcelens.oneprocloud.com/lens/assistants/AI_HyperBDR/chat", icon: "fa-solid fa-robot" } ] diff --git a/src/.vuepress/client/homepage.config.zh.ts b/src/.vuepress/client/homepage.config.zh.ts index e976597d..cc7e5cd4 100644 --- a/src/.vuepress/client/homepage.config.zh.ts +++ b/src/.vuepress/client/homepage.config.zh.ts @@ -237,7 +237,7 @@ export const homepageSectionsZh: HomepageSection[] = [ { title: "AI 智能搜索", desc: "AI 智能搜索 from OneProCloud.", - link: "https://ai.oneprocloud.com/chat/qWGp3yX8ain2550b", + link: "https://sourcelens.oneprocloud.com/lens/assistants/AI_HyperBDR/chat", icon: "fa-solid fa-robot" }, { @@ -270,7 +270,7 @@ export const coreActionsZh: CoreAction[] = [ { title: "AI Support", desc: "AI Support from OneProCloud.", - link: "https://ai.oneprocloud.com/chat/qWGp3yX8ain2550b", + link: "https://sourcelens.oneprocloud.com/lens/assistants/AI_HyperBDR/chat", icon: "fa-solid fa-robot" }, ] diff --git a/src/.vuepress/navbar/en.main.ts b/src/.vuepress/navbar/en.main.ts index 609d9d01..876f8aff 100644 --- a/src/.vuepress/navbar/en.main.ts +++ b/src/.vuepress/navbar/en.main.ts @@ -162,7 +162,7 @@ export const enNavbar = navbar([ { text: "AI Support", icon: "robot", - link: "https://ai.oneprocloud.com/chat/qWGp3yX8ain2550b", + link: "https://sourcelens.oneprocloud.com/lens/assistants/AI_HyperBDR/chat", }, { text: "Get Support", diff --git a/src/.vuepress/navbar/zh.main.ts b/src/.vuepress/navbar/zh.main.ts index ded08817..151bc37c 100644 --- a/src/.vuepress/navbar/zh.main.ts +++ b/src/.vuepress/navbar/zh.main.ts @@ -162,7 +162,7 @@ export const zhNavbar = navbar([ { text: "AI支持", icon: "robot", - link: "https://ai.oneprocloud.com/chat/qWGp3yX8ain2550b", + link: "https://sourcelens.oneprocloud.com/lens/assistants/AI_HyperBDR/chat", }, { text: "获取支持", From 497becb68422b2a890c4340cd73d17df1374a23d Mon Sep 17 00:00:00 2001 From: dianzheng <910852115@qq.com> Date: Thu, 2 Jul 2026 11:28:39 +0800 Subject: [PATCH 2/2] update General Failback Drill --- .../general-failback-drill.md | 206 ++---------------- ...penstack-failback-drill-reference-guide.md | 4 - .../vmware-failback-drill-reference-guide.md | 6 +- .../general-failback-drill.md | 206 ++---------------- ...penstack-failback-drill-reference-guide.md | 4 - .../vmware-failback-drill-reference-guide.md | 6 +- 6 files changed, 36 insertions(+), 396 deletions(-) diff --git a/src/userguide/technical-practices/general-failback-drill.md b/src/userguide/technical-practices/general-failback-drill.md index 66089fc3..4c05937d 100644 --- a/src/userguide/technical-practices/general-failback-drill.md +++ b/src/userguide/technical-practices/general-failback-drill.md @@ -1,202 +1,28 @@ # General Failback Drill -## The loopback platform supports ISO boot +The general failback drill is designed for scenarios where the failback target platform lacks standard automated failback capabilities. By copying disk data from the failback transition host and performing driver repair using the HyperDoor boot image, you can create an independent drill host for startup and service verification without impacting ongoing failback data synchronization or business continuity. -### Supports cloning hosts +## Applicable Scenarios -- On the disaster recovery platform, after waiting for the failback data synchronization to complete, log in to the target platform for failback\. +- The failback target platform does not support platform-level automatic failback, or has not yet been adapted for the target cloud or virtualization platform. +- Before the formal failback, you need to verify whether the operating system can boot normally, disks are recognized, and the network and services are available after failback. +- The target platform supports capabilities such as VM cloning, disk snapshots, volume replication, or disk attachment, allowing an independent drill environment to be created from the failback transition host's data. +- There are differences in virtualization drivers, disk controllers, or boot modes between the source and failback target, requiring driver repair via the Livecd-HyperDoor image. +- You need to avoid directly operating the failback transition host that is synchronizing data or running formal failback tasks, minimizing the drill's impact on the formal failback process. -- Find the "rollback transition host" that receives data, and use the platform's host cloning capability to clone a new host\. +## Core Principles -- Use the Livecd\-HyperDoor\.iso mirroring image to boot up this cloned host using the platform's Livecd\. - -- Log in to this cloned host, execute the minitgt\-fix command, and perform driver repair\. - -- Wait for the driver repair to complete, shut down the host, remove the optical drive, and then boot from the hard disk\. - -- Configure the IP Address for this test host\. - -- Just adjust the business configuration and perform verification\. - - - -### Cloning hosts is not supported - -- On the disaster recovery platform, after waiting for the failback data synchronization to complete, log in to the target platform for failback\. - -- Locate the "rollback transition host" that receives data, and make a copy of all disks corresponding to this host for backup - -- Use the copied system disk, leverage the volume boot capability, start up a host, and mount the remaining data disks to this host - -- Use the Livecd\-HyperDoor\.iso mirroring image to boot up this cloned host using the platform's Livecd\. - -- Log in to this cloned host, execute the minitgt\-fix command, and perform driver repair\. - -- Wait for the driver repair to complete, shut down the host, remove the optical drive, and then boot from the hard disk\. - -- Configure the IP Address for this test host\. - -- Just adjust the business configuration and perform verification\. - - - -## The backcut platform does not support ISO boot - -- On the disaster recovery platform, after waiting for the failback data synchronization to complete, log in to the target platform for failback\. - -- Locate the "rollback transition host" that receives data, and make a copy of all disks corresponding to this host for backup - -- Use the Livecd\-HyperDoor\.iso or Livecd\-HyperDoor\.qcow2 mirroring to create a brand new transitional host, and the system disk of this host must be equal in size to or larger than that of the host to be reverted - -- Then mount all the system disks and data disks that were previously copied out for backup onto this new transitional host\. - -- Use the dd command to copy the newly mounted system disk in its entirety to the system disk of the transition host itself\. After the copy is completed, unmount the mounted system disk\. - -- In this transition host, use lsblk to check the system disk of this host \(assuming it is vda\), and execute the minitgt\-fix /dev/vda command to perform driver repair\. - -- Wait for the driver repair to complete, then restart the transition host\. - -- After the host has finished starting up, configure the IP Address for this host\. - -- Just adjust the business configuration and perform verification\. - - - ---- - -## Organize and optimize - -Based on the above document, I think it can be used as a multi\-step guiding process to allow users to perform operations: - -#### Step 1: Upload mirroring - -```Plain Text -The disaster recovery drill requires a boot image. Upload the image to the target platform first. - -> Platforms that support ISO boot, such as VMware - -Recommended for VMware vSphere environments. It provides complete virtual machine image support. -Download link: https://192.168.8.22:30080/softwares/hyperdoor/Livecd-HyperDoor.iso - -> Cloud platforms that support QCOW2, such as OpenStack - -Recommended for mainstream cloud platforms. It provides strong compatibility with cloud environments. -Download link: https://192.168.8.22:30080/softwares/hyperdoor/Livecd-HyperDoor.qcow2 - -> Upload the image to the target platform - -Upload the downloaded image to your target cloud platform or VMware environment. The upload process may vary by platform. Refer to the documentation of your platform for details. - -Upload notes: -- For cloud platforms: upload the QCOW2 image through the console. -- For VMware: upload the ISO image through vCenter. -- Make sure the image is uploaded to the correct region or data center. -- After the upload is complete, verify the image integrity. - -``` - -#### Step 2: Copy Disk - -First, this page should prompt the following content: - -```Plain Text -Do not copy disks while data synchronization is in progress. This may cause data inconsistency. Before copying disks, confirm that: -1. Data synchronization has completed. -2. The protection policy for the host can be disabled. -After both items are confirmed, copy the disks. -``` - -Then it is to guide users to copy the disk, mainly including: - -```Plain Text -> Platforms that support host cloning, such as VMware - -Find the transition host that receives the synchronized data. Use the platform's host cloning feature to create a new host for the drill. - -> Platforms that support snapshots, such as OpenStack - -Find the transition host that receives the synchronized data. Use host snapshots or volume snapshots to create snapshots for all disks of the transition host. -Then create volumes from the snapshots for later use. - -> Platforms that do not support the quick disk copy methods above, such as physical servers - -Create the same number of disks with the same sizes as the disks on the transition host, and attach them to the transition host. -Log in to the transition host through SSH. Use the dd command to copy each disk to the newly attached drill disk. -After the copy is complete, detach the disks for later use. - -``` - -#### Step 3: Boot the host - -```Plain Text -> Platforms that support host cloning and ISO boot, such as VMware - -Attach the ISO image uploaded in Step 1 to the host cloned in Step 2. -Start the host and make sure it boots successfully from the ISO. -For easier management, configure the IP address through DHCP or manually. - -> Cloud platforms that support QCOW2 images, such as OpenStack - -Use the QCOW2 image uploaded in Step 1 to create a new drill host on the platform. The system disk must be the same size as or larger than the system disk of the transition host. -Attach the disks prepared in Step 2 to the new drill host, using the same disk order as the transition host that receives synchronized data. -Start the host and make sure it boots successfully. -For easier management, configure the IP address through DHCP or manually. - -``` - -#### Step 4: Driver Repair - -```Plain Text -Log in to the drill host started in Step 3 through the console or SSH. -Run minitgt-fix to repair the drivers. -If you need to convert UEFI to BIOS, refer to the document: xxx. -If you need WinPE repair, refer to the document: xxx. - -``` - -#### Step 5: Verify the host - -```Plain Text -> Drill hosts cloned and started through ISO boot, such as VMware - -Unmount the ISO image from the CD/DVD drive. -Run reboot to restart the system. -Verify the system after startup. - -> Drill hosts created from a QCOW2 image, such as OpenStack - -Use dd to overwrite the system disk created from the QCOW2 image with the repaired system disk. -Run reboot to restart the system. -Verify the system after startup. - -``` - -## Final Solution - -Use only one page to guide users to download the mirroring, and then direct them to the document platform for processing\. - -```Plain Text -The disaster recovery drill requires a boot image. Upload the image to the target platform first. - -> Platforms that support ISO boot, such as VMware - -Recommended for VMware vSphere environments. It provides complete virtual machine image support. -Download link: https://192.168.8.22:30080/softwares/hyperdoor/Livecd-HyperDoor.iso - -> Cloud platforms that support QCOW2, such as OpenStack and Alibaba Cloud - -Recommended for mainstream cloud platforms. It provides strong compatibility with cloud environments. -Download link: https://192.168.8.22:30080/softwares/hyperdoor/Livecd-HyperDoor.qcow2 - -> Upload the image to the target platform - -Upload the downloaded image to your target cloud platform or VMware environment. The upload process may vary by platform. Refer to the documentation of your platform for details. - - -``` +- The drill must be based on a disk copy of the failback transition host. Do not directly modify the failback transition host that is synchronizing data. +- Before copying the disk, confirm that failback data synchronization is complete and that the host is allowed to be shut down or enter drill mode. +- The number of disks on the drill host must match the failback host. Disk capacity can be larger than the original, but not smaller. +- The boot mode of the source and drill target must match. For example, if the source uses BIOS boot, the target must also use BIOS; if the source uses UEFI, the target must also use UEFI. +- After driver repair is complete, remove the Livecd-HyperDoor boot image and boot the host from the repaired system disk. +- It is recommended to use independent IP addresses, network policies, and service configurations for the drill environment to avoid conflicts with the production environment. ## Reference Guide +If your failback target platform belongs to one of the following types, refer to the corresponding guide to complete the general failback drill. Different platforms may differ in image upload, disk copy, host creation, disk attachment, and boot mode configuration. Please follow the platform-specific guide. + | Cloud Provider | Configuration Guide | | ------------------------------- | ---- | | VMware | [View guide](./vmware-failback-drill-reference-guide.md) | diff --git a/src/userguide/technical-practices/openstack-failback-drill-reference-guide.md b/src/userguide/technical-practices/openstack-failback-drill-reference-guide.md index 28f62fdf..85032591 100644 --- a/src/userguide/technical-practices/openstack-failback-drill-reference-guide.md +++ b/src/userguide/technical-practices/openstack-failback-drill-reference-guide.md @@ -74,10 +74,6 @@ Enter Project, Volumes, Volumes, find the volume created by the snapshot, and mo Log in to the HyperUbuntuDrill host that has just completed booting via the Console or SSH, and execute minitgt\-fix to complete driver repair; -If UEFI to BIOS conversion is required, please refer to the document: xxx\. - -If WinPE repair is needed, please refer to the document: xxx\. - ![Image](./images/openstack-failback-drill-reference-guide-13.png) ![Image](./images/openstack-failback-drill-reference-guide-14.png) diff --git a/src/userguide/technical-practices/vmware-failback-drill-reference-guide.md b/src/userguide/technical-practices/vmware-failback-drill-reference-guide.md index f32979e8..fbd4e8a9 100644 --- a/src/userguide/technical-practices/vmware-failback-drill-reference-guide.md +++ b/src/userguide/technical-practices/vmware-failback-drill-reference-guide.md @@ -30,6 +30,8 @@ At this time, Livecd\-HyperDoor\.iso has been successfully uploaded to the Cloud Find the transition host that has completed synchronization, and use the host cloning capability of the platform to clone a new host for standby\. +> After the cloning process is complete, please verify that the boot mode of the target host is consistent with that of the source host. Under normal circumstances, the cloned host should use the same boot mode as the source host. + Find HyperUbuntu, click ACTIONS, move to Clone, and click Clone to Virtual Machine\.\.\. ![Image](./images/vmware-failback-drill-reference-guide-5.png) @@ -65,10 +67,6 @@ setting-ip 192.168.8.35 255.255.240.0 192.168.0.1 114.114.114.114 Log in to the HyperUbuntuDrill host that has just completed booting via the Console or SSH, and execute minitgt\-fix to complete driver repair; -If UEFI to BIOS conversion is required, please refer to the document: xxx\. - -If WinPE repair is required, please refer to the document: xxx\. - ![Image](./images/vmware-failback-drill-reference-guide-9.png) ![Image](./images/vmware-failback-drill-reference-guide-10.png) diff --git a/src/zh/userguide/technical-practices/general-failback-drill.md b/src/zh/userguide/technical-practices/general-failback-drill.md index 3ee17cb7..5423202d 100644 --- a/src/zh/userguide/technical-practices/general-failback-drill.md +++ b/src/zh/userguide/technical-practices/general-failback-drill.md @@ -1,202 +1,28 @@ # 通用方式回切演练 -## 回切平台支持ISO引导 +通用方式回切演练适用于回切目标平台不具备标准自动化回切能力的场景。通过复制回切过渡主机的磁盘数据，并使用 HyperDoor 引导镜像完成驱动修复，可在不影响正式回切数据和业务连续性的前提下，创建一台独立的演练主机进行启动和业务验证。 -### 支持克隆主机 +## 主要适用于以下场景 -- 容灾平台上，等待failback数据同步完成后，登录回切目标平台。 +- 回切目标平台不支持平台级自动回切，或暂未适配对应的云平台、虚拟化平台。 +- 需要在正式回切前，提前验证回切后的操作系统是否能够正常启动、磁盘是否可识别、网络和业务是否可用。 +- 目标平台支持虚拟机克隆、磁盘快照、卷复制或磁盘挂载等能力，可基于回切过渡主机的数据创建独立的演练环境。 +- 源端与回切目标端的虚拟化驱动、磁盘控制器或启动方式存在差异，需要通过 Livecd-HyperDoor 镜像执行驱动修复。 +- 需要避免直接操作正在进行数据同步或承载正式回切任务的过渡主机，降低演练对正式回切流程的影响。 -- 找到接收数据的“回切过渡主机”，使用平台的主机克隆能力，克隆出一台新的主机。 +## 通用方式回切演练的核心原则 -- 用Livecd\-HyperDoor\.iso镜像，使用平台的Livecd把克隆好的这台主机引导起来。 - -- 登录这台克隆好的主机，执行 minitgt\-fix 命令，进行驱动修复。 - -- 等待驱动修复完成，关闭主机，移除光驱后，从硬盘引导起来即可。 - -- 为该测试主机配置IP地址。 - -- 调整好业务配置，进行验证即可。 - - - -### 不支持克隆主机 - -- 容灾平台上，等待failback数据同步完成后，登录回切目标平台。 - -- 找到接收数据的“回切过渡主机”，把该主机对应的所有磁盘，复制一份出来备用 - -- 使用复制出来的系统盘，利用卷启动的能力，拉起一台主机，并把剩余的数据盘挂载给该主机 - -- 用Livecd\-HyperDoor\.iso镜像，使用平台的Livecd把克隆好的这台主机引导起来。 - -- 登录这台克隆好的主机，执行 minitgt\-fix 命令，进行驱动修复。 - -- 等待驱动修复完成，关闭主机，移除光驱后，从硬盘引导起来即可。 - -- 为该测试主机配置IP地址。 - -- 调整好业务配置，进行验证即可。 - - - -## 回切平台不支持ISO引导 - -- 容灾平台上，等待failback数据同步完成后，登录回切目标平台。 - -- 找到接收数据的“回切过渡主机”，把该主机对应的所有磁盘，复制一份出来备用 - -- 用Livecd\-HyperDoor\.iso 或 Livecd\-HyperDoor\.qcow2镜像，创建一台全新过渡主机，且该主机的系统盘要跟待回切主机的系统盘大小相等或比之更大 - -- 然后把前面复制出来备用的系统盘和数据盘，全部挂载到这台新过渡主机上。 - -- 把新挂载上去的这块系统盘，用dd命令，全部复制到过渡主机本身的系统盘里，复制完成之后，把挂载的这块系统盘卸载掉。 - -- 在这台过渡主机里，通过lsblk查看这台主机的系统盘\(假设是vda\),执行 minitgt\-fix /dev/vda 命令，进行驱动修复。 - -- 等待驱动修复完成，重启该过渡主机即可。 - -- 等主机启动完成，为该主机配置IP地址。 - -- 调整好业务配置，进行验证即可。 - - - ---- - -## 整理优化 - -根据上面的文档，我看可以做为几步引导步骤来让用户进行操作： - -#### 第一步：上传镜像 - -```Plain Text -容灾演练需要使用引导镜像，请先将镜像上传至目标平台。 - -> 支持 ISO 引导的平台，如 VMware 等 - -适用于VMware vSphere虚拟化环境，提供完整的虚拟机镜像支持。 -下载链接：https://192.168.8.22:30080/softwares/hyperdoor/Livecd-HyperDoor.iso - -> 支持 QCOW2 格式的云平台，如 OpenStack 等 - -适用于市场主流云平台，提供最佳的云环境兼容性。 -下载链接：https://192.168.8.22:30080/softwares/hyperdoor/Livecd-HyperDoor.qcow2 - -> 上传镜像至目标平台 - -请将下载的镜像上传到您的目标云平台或VMware环境。上传过程可能因平台不同而有所差异，请参考相应平台的文档。 - -上传说明： -- 对于云平台：通过控制台上传QCOW2镜像 -- 对于VMware：通过vCenter上传ISO镜像 -- 确保镜像上传到正确的区域/数据中心 -- 上传完成后验证镜像完整性 - -``` - -#### 第二步：拷贝磁盘 - -首先，这个页面先要提示下面的内容： - -```Plain Text -请不要在数据同步的时候拷贝磁盘，否则可能会导致数据异常；建议先确认： -1. 是否已经数据同步完毕 -2. 主机是否可以关闭策略 -请完成上面两项确认后，再执行拷贝磁盘操作 -``` - -然后就是引导用户拷贝磁盘，主要有： - -```Plain Text -> 支持克隆主机的平台，如 VMware 等 - -找到接收数据的过渡主机，使用平台的主机克隆能力，克隆出一台新的主机备用。 - -> 支持创建快照的平台，如 OpenStack 等 - -找到接收数据的过渡主机，使用平台的主机快照能力或者卷快照能力，将过渡主机的所有磁盘创建快照； -然后将快照创建为卷备用。 - -> 不支持上述快速拷贝磁盘的平台，如物理机等 - -请创建与接收数据的过渡主机相同数量和相同大小的磁盘，挂载到过渡主机； -通过 ssh 登录到过渡主机，然后通过 dd 命令，分别将每个磁盘数据拷贝至新挂载的演练磁盘中； -拷贝完成后，卸载磁盘备用。 - -``` - -#### 第三步：引导主机 - -```Plain Text -> 支持克隆主机并支持 ISO 引导的平台，如 VMware 等 - -将第一步上传的 ISO 镜像，设置到第二步克隆的主机中； -然后启动主机，确保 ISO 正常完成主机引导； -考虑到管理方便，可以考虑通过 DHCP 或手动的方式设置 IP。 - -> 支持 QCOW2 镜像的云平台，如 OpenStack 等 - -使用第一步上传的 QCOW2 镜像在平台上创建一台新演练主机，系统盘大小要等于或者大于接收数据的过渡主机系统盘大小； -参考接收同步数据过渡主机的磁盘顺序，将第二步备用的磁盘挂载到新的演练主机中； -启动主机，确保正常完成主机引导； -考虑到管理方便，可以考虑通过 DHCP 或手动的方式设置 IP。 - -``` - -#### 第四步：驱动修复 - -```Plain Text -通过控制台或者 SSH 登录到第三步引导的演练主机； -执行 minitgt-fix 完成驱动修复； -如果需要 UEFI 转 BIOS 请参考文档：xxx。 -如果需要 WinPE 修复请参考文档：xxx。 - -``` - -#### 第五步：验证主机 - -```Plain Text -> 支持克隆主机并通过 ISO 引导的演练主机，如 VMware 等 - -将光驱中的 ISO 镜像卸载； -执行 reboot 重启系统。 -验证启动后的系统。 - -> 通过 QCOW2 镜像新创建的演练主机，如 OpenStack 等 - -将驱动修复后的系统盘通过 dd 的方式覆盖 QCOW2 镜像创建的系统盘； -执行 reboot 重启系统。 -验证启动后的系统。 - -``` - -## 最终方案 - -仅使用一个页面，引导用户下载镜像后，引导到文档平台处理。 - -```Plain Text -容灾演练需要使用引导镜像，请先将镜像上传至目标平台。 - -> 支持 ISO 引导的平台，如 VMware 等 - -适用于VMware vSphere虚拟化环境，提供完整的虚拟机镜像支持。 -下载链接：https://192.168.8.22:30080/softwares/hyperdoor/Livecd-HyperDoor.iso - -> 支持 QCOW2 格式的云平台，如 OpenStack/阿里云 等 - -适用于市场主流云平台，提供最佳的云环境兼容性。 -下载链接：https://192.168.8.22:30080/softwares/hyperdoor/Livecd-HyperDoor.qcow2 - -> 上传镜像至目标平台 - -请将下载的镜像上传到您的目标云平台或VMware环境。上传过程可能因平台不同而有所差异，请参考相应平台的文档。 - - -``` +- 演练应基于回切过渡主机的磁盘副本进行，避免直接修改正在同步数据的过渡主机。 +- 在复制磁盘前，应确认回切数据同步已完成，并确认主机允许执行关闭或演练操作。 +- 演练主机的磁盘数量应与回切主机保持一致；磁盘容量可以大于原磁盘，但不能小于原磁盘。 +- 源端与演练目标端的启动方式应保持一致，例如源端为 BIOS 启动时，目标主机也应使用 BIOS；源端为 UEFI 启动时，目标主机也应使用 UEFI。 +- 驱动修复完成后，应移除 Livecd-HyperDoor 引导镜像，并从修复后的系统盘启动主机。 +- 演练环境建议使用独立 IP 地址、网络策略和业务配置，避免与生产环境发生冲突。 ## 参考文档 +如果您的回切目标平台属于下列平台类型，可参考对应的操作文档完成通用方式回切演练。不同平台在镜像上传、磁盘复制、主机创建、磁盘挂载及启动方式配置等操作上可能存在差异，请以对应平台的参考文档为准。 + | 云厂商名称 | 配置说明 | | ------------------------------- | ---- | | VMware | [点击查看](./vmware-failback-drill-reference-guide.md) | diff --git a/src/zh/userguide/technical-practices/openstack-failback-drill-reference-guide.md b/src/zh/userguide/technical-practices/openstack-failback-drill-reference-guide.md index a641ef03..883d9ad9 100644 --- a/src/zh/userguide/technical-practices/openstack-failback-drill-reference-guide.md +++ b/src/zh/userguide/technical-practices/openstack-failback-drill-reference-guide.md @@ -72,10 +72,6 @@ Format：选择 QCOW2 通过控制台或者 SSH 登录刚刚完成引导的 HyperUbuntuDrill 主机，执行 minitgt\-fix 完成驱动修复； -如果需要 UEFI 转 BIOS 请参考文档：xxx。 - -如果需要 WinPE 修复请参考文档：xxx。 - ![Image](./images/openstack-failback-drill-reference-guide-13.png) ![Image](./images/openstack-failback-drill-reference-guide-14.png) diff --git a/src/zh/userguide/technical-practices/vmware-failback-drill-reference-guide.md b/src/zh/userguide/technical-practices/vmware-failback-drill-reference-guide.md index 9334e927..4658f73a 100644 --- a/src/zh/userguide/technical-practices/vmware-failback-drill-reference-guide.md +++ b/src/zh/userguide/technical-practices/vmware-failback-drill-reference-guide.md @@ -30,6 +30,8 @@ 找到同步完成的过渡主机，使用平台的主机克隆能力，克隆出一台新的主机备用。 +> 克隆完成后，请检查目标主机的启动方式是否与源主机保持一致。正常情况下，克隆后的主机启动方式应与源主机一致。 + 找到 HyperUbuntu，点击 ACTIONS，移动到 Clone，点击 Clone to Virtual Machine\.\.\. ![Image](./images/vmware-failback-drill-reference-guide-5.png) @@ -65,10 +67,6 @@ setting-ip 192.168.8.35 255.255.240.0 192.168.0.1 114.114.114.114 通过控制台或者 SSH 登录刚刚完成引导的 HyperUbuntuDrill 主机，执行 minitgt\-fix 完成驱动修复； -如果需要 UEFI 转 BIOS 请参考文档：xxx。 - -如果需要 WinPE 修复请参考文档：xxx。 - ![Image](./images/vmware-failback-drill-reference-guide-9.png) ![Image](./images/vmware-failback-drill-reference-guide-10.png)