VMware Data Recovery 管理员指南 ZH_CN-000193-00 VMware Data Recovery 2 VMware, Inc. 您可以在 VMware 的网站上找到最新的技术文档，网址为 http://www.vmware.com/cn/support/ VMware 网站还提供了最新的产品更新。 如果您对本文档有任何意见和建议，请将您的反馈提交到： 1 了解 VMware Data Recovery 7 备份虚拟机 7 卷影复制服务 8 删除重复存储的优点 8 2 安装 VMware Data Recovery 9 VMware Data Recovery 系统要求 9 安装客户端插件 9 安装备份设备 10 向备份设备中添加硬盘 10 3 配置 VMware Data Recovery 13 启动备份设备 13 配置备份设备 VMware Data Recovery 故障排除 18 索引 21 VMware, Inc. 3 VMware Data Recovery 4 VMware, Inc. 关于本文档 《VMware Data Recovery 管理员指南》包含为中小型企业建立备份解决方案的信息。 目标读者 本文档适用于需要使用 VMware Data Recovery 提供备份解决方案的用户。本书的目标读者为熟悉虚拟机技术

availability, recovery semantics, and guarantees Vasiliki Kalavri | Boston University 2020 Today’s topics • High-availability and fault-tolerance in distributed stream processing • Recovery semantics against failures and guarantee correct results after recovery? • how can we ensure minimal downtime and fast recovery? • how can we hide recovery side-effects from downstream applications? Vasiliki failures. 7 Vasiliki Kalavri | Boston University 2020 Recovery types 8 Vasiliki Kalavri | Boston University 2020 Recovery types • Precise recovery (exactly-once) • It hides the effects of a failure

using PVCs. PVCs are included along with other namespaces in PowerProtect Data Manager backup and recovery operations. Rancher Kubernetes Cluster Data Protection using PowerProtect Data Manager creating a Kubernetes cluster protection policy: • Crash Consistent: Select this type for point-in-time backup of namespaces. • Exclusion: Select this type if there are assets within the protection type is supported for Kubernetes protection. For more information about performing backup and recovery of Kubernetes workloads using PowerProtect Data Manager, see Dell EMC PowerProtect Data Manager

Schemes ❏ Should be able to recover the files automatically on failures ❏ Online recovery ❏ Phase - II ❏ Offline recovery ❏ Phase - III ❏ Should provide options to enable EC via Recon / CM ❏ Should decode operation. ➢ To avoid the degraded reads, we need to recover the lost replicas offline. EC Recovery Reads ReplicaIndex-1 ReplicaIndex-2 ReplicaIndex-3 ReplicaIndex-4 ReplicaIndex-5 EC Container Reconstruct and Read stripe-1 Reconstruct and Read stripe-2 N1 N2 N3 N4 N5 What is the Offline Recovery? ➢ When a node/Disk lost, we will lose the containers which are residing in that node/disk. We

how and when to start the initial recovery process on # a full cluster restart (to reuse as much local data as possible when using shared # gateway). # Allow recovery process after N nodes in a cluster cluster are up: # #gateway.recover_after_nodes: 1 # Set the timeout to initiate the recovery process, once the N nodes # from previous setting are up (accepts time value): # #gateway.recover_after_time: 5m recover_after_nodes is met), begin recovery process immediately # (without waiting for recover_after_time to expire): # #gateway.expected_nodes: 2 ############################# Recovery Throttling #############################

vMotion）。 • 计划外基础架构停机的常规应用程序保护（网卡绑定、多路径、VMware HA、VMware Consolidated Backup、VMware vCenter Site Recovery Manager）。 • 计划外应用程序停机（通过 VMware HA 中的虚拟机故障监控）。 图 5. 用于实现业务连续性的 VMware 技术 在这方面，VMware 通过使用 VMware vCenter Site Recovery Manager 管理从生产数据中心到备份站点的故障切换，帮 助达到您的恢复时间目标 (RTO) 和遵从性要求。通过将两个站点设置为彼此的恢复站点来管理两个活 动站点之间的故障切换。甚至数据中心迁移等情景下的计划内数据中心故障切换也可以通过 VMware vCenter Site Recovery Manager 得到简化。 通过 VMware VMware vCenter Site Recovery Manager 简化和自动建立、测试和执行恢复计划的关键要素。 • 建立恢复基础架构 – VMware vCenter Site Recovery Manager 将指导用户完成连接到远程站 点和正在使用的存储复制软件的过程。另外，还可以通过其轻松地将生产资源（包括计算和网络 资源）映射到恢复站点上的相应资源。 • 创建恢复计划 –

Health Checks/HA ✔ Load Balancing ✔ Overlay Networking ✔ Network Security Policies ✔ Backup and Recovery ✔ Autoscaling ✔ Service Discovery ✔ Networking ✔ RBAC & Access Control DEV DATA CENTER CLOUD Health Checks/HA ✔ Load Balancing ✔ Overlay Networking ✔ Network Security Policies ✔ Backup and Recovery ✔ Autoscaling ✔ Service Discovery ✔ Networking ✔ RBAC & Access Control ✔ Common API & Packaging Health Checks/HA ✔ Load Balancing ✔ Overlay Networking ✔ Network Security Policies ✔ Backup and Recovery ✔ Autoscaling ✔ Service Discovery ✔ Networking ✔ RBAC & Access Control Common compute platform

7.3. 资源要求 7.4. POD 放置规则 7.5. 存储设备要求 7.6. 网络要求 7.7. 多网络插件 (MULTUS) 支持 [技术预览] 第 第 8 章 章 DISASTER RECOVERY 8.1. METRO-DR 8.2. REGION-DR [技术预览] 第 第 9 章 章 断开 断开连 连接的 接的环 环境 境 第 第 10 章 章 IBM POWER 和 和 IBM 如需了解在 VMware 上配置 Multus 配置所需的步骤，请参阅创建 Multus 网络。 第 第 7 章 章 基 基础 础架 架构 构要求 要求 27 第 8 章 DISASTER RECOVERY 灾难恢复 (DR) 有助于机构在出现中断或紧急情况时恢复业务关键功能或正常操作。OpenShift Data Foundation 为有状态应用程序提供高可用性(HA)和 DR 解决方案，它们被广泛分为两个宽泛： 支持，且功能可能并不完整。红帽不推荐在生产环境中使用它们。这些技术预览功能可以 使用户提早试用新的功能，并有机会在开发阶段提供反馈意见。 如需更多信息，请参阅技术预览功能支持范围。 第 第 8 章 章 DISASTER RECOVERY 29 第 9 章 断开连接的环境 断开连接的环境是一个网络受限网络，Operator Lifecycle Manager (OLM) 无法访问需要互联网连接的默 认 Operator Hub

Healthy Terminating Pod Number Daily Report Validation Housekeepi ng High Available Fast Recovery Display Board Alert Analysis Platform Weekly Report SLO： Indicate the cluster is healthy or there • orphaned pod directories/volumes • orphaned cgroups • orphaned net device and so on, node recovery system can cleanup those dirty data or alert cluster admins to process dirty data manually. Unhealthy ntoller failedPodContr oller Detector Strategy Unhealthy node list Fast Taint Weight Adjust Recovery Manual Handling Improve Auto Human experience Improve of strategy …… 1. Collect data from

member Kubelet Pods API Server Scheduler Controller Manager etcd operator etcd Disaster Recovery Node failure in HA deployments (Kubernetes) Partial loss of control plane components (Kubernetes) the entire control plane (Kubernetes) Permanent loss of control plane (External tool) Disaster Recovery Permanent loss of control plane ● Similar situation to initial node bootstrap, but utilizing start a temporary replacement api-server ○ Could be binary, static pod, new tool, bootkube, etc. ● Recovery once etcd+api is available can be done via kubectl (as seen previously) Self-Driving Kubernetes