技术领域technical field
本发明涉及一种备份和恢复方法，具体地说是一种Linux系统备份和恢复方法。The invention relates to a backup and recovery method, in particular to a Linux system backup and recovery method.
背景技术Background technique
安装Linux操作系统的服务器下,仍然主要由系统管理员负责操作系统的备份与恢复,数据库管理员负责数据库的备份与恢复,应用系统管理员负责应用系统的备份与恢复,没有一种工具或者系统为整个服务器下操作系统、数据库数据、应用系统数据、其它资料做备份与恢复，更没有系统或者工具支持完全在线（不停机）状态下的Linux服务器完全备份。依赖管理员们的脚本和各个备份工具厂商相互不兼容的工具，备份工作复杂且容易出错。Under the server with the Linux operating system installed, the system administrator is still mainly responsible for the backup and recovery of the operating system, the database administrator is responsible for the backup and recovery of the database, and the application system administrator is responsible for the backup and recovery of the application system. There is no tool or system Backup and restore the operating system, database data, application system data, and other data of the entire server, and there is no system or tool to support the full backup of the Linux server in a completely online (non-stop) state. Relying on administrators' scripts and incompatible tools from various backup vendors makes backups complex and error-prone.
特别是，在面对机房中数量众多的Linux服务器备份与恢复的管理问题，没有一个统一的平台作为支持，靠一个一个的管理员和大量不易维护的Shell脚本是难于应付的。每个管理员定义的备份资料的名称、保存位置、有效性、使用方式都不相同，甚至是备份资料与服务器的对应关系、恢复适用条件等信息都没有记录，都为这些备份数据的恢复和使用带来困难。更不用说当管理员变动时，进行备份与恢复工作交接，就更是难上加难。In particular, in the face of the backup and recovery management of a large number of Linux servers in the computer room, without a unified platform as support, it is difficult to cope with individual administrators and a large number of difficult-to-maintain Shell scripts. The names, storage locations, validity, and usage methods of the backup data defined by each administrator are different, and even information such as the correspondence between the backup data and the server and the applicable recovery conditions are not recorded. Difficulty in use. Not to mention that when the administrator changes, it is even more difficult to carry out the handover of backup and recovery work.
发明内容Contents of the invention
为了解决上述问题，本发明提供了一种Linux系统备份和恢复方法，通过预设四种类型的处理方案，实现对大批量Linux服务器的智能备份和恢复操作。 In order to solve the above problems, the present invention provides a Linux system backup and recovery method, which realizes intelligent backup and recovery operations for a large number of Linux servers by preset four types of processing schemes.
本发明采用以下技术方案：一种Linux系统备份和恢复方法，其特征在于，所述的方法包括以下步骤：The present invention adopts following technical scheme: a kind of Linux system backup and restoration method, it is characterized in that, described method comprises the following steps:
预定义全备份方案、增量备份方案、裸设备恢复方案、增量恢复方案；Predefined full backup scheme, incremental backup scheme, raw device recovery scheme, and incremental recovery scheme;
接收实时的计划指令；Receive real-time planning instructions;
检测计划的合法性；the legality of the testing programme;
确认目标节点的状态；Confirm the status of the target node;
执行符合计划的方案。Execute the program according to the plan.
进一步的，预定义全备份方案的过程为：Further, the process of predefining the full backup scheme is:
定义命名规范；define naming conventions;
选择操作系统下的目录，设定备份范围；Select the directory under the operating system and set the backup range;
设定NFS协议和SSH协议两种传输协议；Set two transmission protocols: NFS protocol and SSH protocol;
定义备份库节点结构；Define the backup database node structure;
设定命令方式、快照方式两种备份方式；Two backup methods, command mode and snapshot mode, can be set;
将审核后的全备份方案保存到数据库中。Save the approved full backup plan to the database.
进一步的，预定义增量备份方案的过程为：Further, the process of pre-defining the incremental backup scheme is:
定义命名规范；define naming conventions;
设定累积增量备份和差异增量备份两种增量备份类型；Set two incremental backup types: cumulative incremental backup and differential incremental backup;
选择操作系统下的目录，设定备份范围；Select the directory under the operating system and set the backup range;
设定NFS协议和SSH协议两种传输协议；Set two transmission protocols: NFS protocol and SSH protocol;
定义自动增量备份时间；Define automatic incremental backup time;
定义节点备份库结构；Define the node backup library structure;
将审核后的增量备份方案保存到数据库中。Save the reviewed incremental backup plan to the database.
进一步的，驻留客户端RCT可以将目标节点的负载状况上传到数据库，根据众多目标节点负载分布情况，安排各节点增量备份起始时刻。Furthermore, the resident client RCT can upload the load status of the target nodes to the database, and arrange the start time of the incremental backup of each node according to the load distribution of many target nodes.
进一步的，在增量备份方案执行过程中，驻留客户端工具RCT自动比较目标节点原组件列表与当前最新组件列表是否有差异，如果有差异，维护一个包含组件名称、所属包、新增/删除内容的组件列表变动清单，并在增量备份方案执行结束后，传回备份集库中与原组件列表合并保存。Furthermore, during the execution of the incremental backup scheme, the resident client tool RCT automatically compares whether there is any difference between the original component list of the target node and the current latest component list. The component list change list of the deleted content, and after the execution of the incremental backup plan is completed, it will be sent back to the backup set library and saved in combination with the original component list.
进一步的，驻留客户端工具RCT执行增量备份方案选定命令方式时，RCT根据备份范围中的文件属性，比较自上次备份以来是否有变更操作，有则作为新的增量备份对象进行备份打包。Furthermore, when the resident client tool RCT executes the incremental backup scheme selection command mode, RCT compares whether there is any change operation since the last backup according to the file attributes in the backup range, and if there is any, it will be used as a new incremental backup object. Backup packaged.
进一步的，预定义裸设备恢复方案的过程为：Further, the process of pre-defining the raw device recovery scheme is:
设定恢复所需操作系统、全备份集、增量备份集所在库路径；Set the library path where the operating system, full backup set, and incremental backup set are located for recovery;
设定NFS协议和SSH协议两种传输协议；Set two transmission protocols: NFS protocol and SSH protocol;
定义恢复库结构；Define the recovery library structure;
选择LiveISO；Select LiveISO;
选择RCT客户端驻留工具；Select the RCT client resident tool;
将审核后的裸设备恢复方案保存到数据库中。Save the audited raw device recovery plan to the database.
进一步的，预定义增量恢复方案的过程为：Further, the process of pre-defining the incremental recovery scheme is:
设定恢复所需增量备份集所在库路径；Set the library path where the incremental backup set required for recovery is located;
设定NFS协议和SSH协议两种传输协议；Set two transmission protocols: NFS protocol and SSH protocol;
定义恢复库结构；Define the recovery library structure;
设定备份检测模块；Set the backup detection module;
将审核后的增量恢复方案保存到数据库中。Save the reviewed incremental recovery plan to the database.
本发明的有益效果是：本发明设计了一套完整的备份和恢复方案，通过IP地址识别服务器，接收备份和恢复计划指令，合理分配备份时间，实现了对大批量Linux服务器备份和恢复的智能管理，减少了人力物力，大大提高了反应和处理的效率。The beneficial effect of the present invention is: the present invention has designed a set of complete backup and recovery scheme, identifies server by IP address, receives backup and recovery plan instruction, allocates backup time reasonably, has realized the intelligence of backup and recovery to a large number of Linux servers Management, reducing manpower and material resources, greatly improving the efficiency of response and processing.
附图说明Description of drawings
图1是本发明流程示意图； Fig. 1 is a schematic flow chart of the present invention;
图2是本发明执行全备份方案的流程示意图； Fig. 2 is the schematic flow chart that the present invention executes full backup scheme;
图3是本发明执行增量备份方案的流程示意图； Fig. 3 is a schematic flow chart of the present invention implementing the incremental backup scheme;
图4是本发明执行裸设备恢复方案的流程示意图； Fig. 4 is a schematic flow diagram of the present invention implementing a recovery solution for raw equipment;
图5是本发明执行增量恢复方案的流程示意图。 FIG. 5 is a schematic flow chart of the implementation of the incremental recovery solution in the present invention.
具体实施方式Detailed ways
如图1所示的一种Linux系统备份和恢复方法，所述的方法包括以下步骤：A kind of Linux system backup and recovery method as shown in Figure 1, described method comprises the following steps:
S101：预定义全备份方案，其过程为：定义需要的命名规范；选择操作系统下的目录,设定备份范围，其中，对于系统组件、设备、配置目录等不需要选择会自动包含在范围内；设定NFS和SSH备份传输协议，其中，NFS协议需要备份中心开放备份集库权限，SSH协议需要用户事先将备份目标服务器的用户密码保存在数据库中，如果密码更改会导致备份失败；定义备份库节点结构；设定命令方式、快照方式两种备份方式，其中，命令方式适用于各类Linux备份目标服务器，快照方式要求目标服务器磁盘空闲空间为已用空间的1.5倍以上，且空闲空间允许重新分区；最后对该计划进行审核后，将全备份方案保存到数据库中。S101: Predefine the full backup scheme, the process of which is: define the required naming convention; select the directory under the operating system, and set the backup range, wherein, system components, equipment, configuration directories, etc. that do not need to be selected will be automatically included in the range ;Set the NFS and SSH backup transfer protocols, among which, the NFS protocol requires the backup center to open the backup set library permission, and the SSH protocol requires the user to save the user password of the backup target server in the database in advance. If the password is changed, the backup will fail; define the backup Database node structure; two backup methods, command mode and snapshot mode, are set. The command mode is applicable to all kinds of Linux backup target servers. Repartition; after final review of the plan, save the full backup plan to the database.
S102：预定义增量备份方案，其过程为：定义需要的命名规范；设定累积增量备份和差异增量备份两种增量备份类型，其中，累积增量备份备份自上次全备份或者累计增量备份以来的增量，差异增量备份备份自上次备份以来的增量；选择操作系统下的目录,设定备份范围；设定NFS和SSH备份传输协议，其中，NFS协议需要备份中心开放备份集库权限，SSH协议需要用户事先将备份目标服务器的用户密码保存在数据库中，如果密码更改会导致备份失败；定义增量备份的时间，可以是每天几点、每周初/末、每月初/末、每季度初/末、每年初/末等时间；定义节点备份库结构；设定命令方式、快照方式两种备份方式，其中，命令方式适用于各类Linux备份目标服务器，快照方式要求目标服务器磁盘空闲空间为已用空间的1.5倍以上，且空闲空间允许重新分区；最后对该计划进行审核后，将增量备份方案保存到数据库中。S102: Predefine the incremental backup scheme, the process of which is: define the required naming convention; set two incremental backup types: cumulative incremental backup and differential incremental backup, wherein the cumulative incremental backup is backed up from the last full backup or Increment since cumulative incremental backup, differential incremental backup backup since last backup; select the directory under the operating system, set the backup range; set NFS and SSH backup transfer protocol, among them, the NFS protocol needs to be backed up The center opens the backup set library authority. The SSH protocol requires the user to save the user password of the backup target server in the database in advance. If the password is changed, the backup will fail; define the time of incremental backup, which can be the time of day, the beginning/end of each week , the beginning/end of each month, the beginning/end of each quarter, the beginning/end of each year, etc.; define the structure of the node backup database; set two backup methods: command mode and snapshot mode. Among them, the command mode is applicable to all kinds of Linux backup target servers. The snapshot method requires that the free space of the target server disk is more than 1.5 times the used space, and the free space allows repartitioning; finally, after reviewing the plan, save the incremental backup plan to the database.
S103：预定义裸设备恢复方案，其过程为：设定恢复所需操作系统、全备份集、增量备份集所在库路径，选择传输协议，定义恢复库结构，选择LiveISO，选择RCT客户端驻留工具，并对该方案进行审核，将信息保存在数据库中。S103: Predefine the recovery plan for raw devices, the process is: set the path of the library where the operating system, full backup set, and incremental backup tool, and the program is reviewed and the information is kept in a database.
S104：预定义增量恢复方案，其过程为：设定恢复所需增量备份集所在库路径，选择传输协议，定义恢复库结构，并对该方案进行审核，将信息保存在数据库中。S104: Predefine an incremental recovery plan, the process of which is: setting the library path where the incremental backup set required for recovery is located, selecting a transport protocol, defining the structure of the recovery library, reviewing the plan, and storing the information in the database.
S105：接收实时的计划指令，该计划指令可以是人工输入，也可以是目标节点的反馈。S105: Receive a real-time planning instruction, which can be a manual input or a feedback from a target node.
S106：检测计划是否合法，如果合法，进入下一步，如果不合法，返回上一步。S106: Detect whether the plan is legal, if legal, go to the next step, if not, return to the previous step.
S107：确认目标节点处于连接状态，并选择目标节点采用的通讯协议；S107: Confirm that the target node is in a connected state, and select a communication protocol adopted by the target node;
S108：执行符合计划的方案。S108: Execute the plan according to the plan.
为了明确该发明中四种方案的不同，下面，结合附图对四种方案的执行过程进行说明。In order to clarify the differences between the four solutions in this invention, the implementation process of the four solutions will be described below in conjunction with the accompanying drawings.
如图2所示，执行全备份方案的过程为：As shown in Figure 2, the process of executing the full backup scheme is as follows:
S201：选择一种备份方式；S201: Select a backup method;
S202：调取备份范围内的文件；S202: Retrieving files within the backup range;
S203：根据命名规范对文件进行打包压缩；S203: Pack and compress the files according to the naming convention;
S204：根据传输协议进行通讯，将备份集归档到全备份方案对应的备份集库中，该备份集库中的文件目录会作为裸设备恢复的数据来源。S204: Perform communication according to the transmission protocol, and archive the backup set into the backup set library corresponding to the full backup solution, and the file directory in the backup set library will be used as a data source for raw device recovery.
如图3所示，执行增量备份方案的过程为：As shown in Figure 3, the process of executing the incremental backup scheme is:
S301：检查各个服务器状态，设定各服务器增量备份起始时刻；S301: Check the status of each server, and set the start time of incremental backup of each server;
S302：选择一种备份方式；S302: Select a backup method;
S303：调取备份范围内的文件；S303: Retrieving files within the backup range;
S304：驻留客户端工具RCT自动比较目标节点原组件列表与当前最新组件列表是否有差异，如果有差异，维护一个包含组件名称、所属包、新增/删除内容的组件列表变动清单后进入步骤S305，若果没有，直接进入下一步；S304: The resident client tool RCT automatically compares whether there is a difference between the original component list of the target node and the current latest component list. If there is a difference, maintain a component list change list including component names, packages, and new/deleted content before entering the step S305, if not, go directly to the next step;
S305：根据命名规范对文件进行打包压缩；S305: Pack and compress the files according to the naming convention;
S306：根据传输协议进行通讯，将备份集归档到全备份方案对应的备份集库中，该备份集库中的文件目录会作为裸设备恢复的数据来源。S306: Perform communication according to the transmission protocol, and archive the backup set into the backup set library corresponding to the full backup solution, and the file directory in the backup set library will be used as a data source for raw device recovery.
进一步的，驻留客户端工具RCT执行增量备份方案选定命令方式时，RCT根据备份范围中的文件属性，比较自上次备份以来是否有变更操作，有则作为新的增量备份对象进行备份打包。Furthermore, when the resident client tool RCT executes the incremental backup scheme selection command mode, RCT compares whether there is any change operation since the last backup according to the file attributes in the backup range, and if there is any, it will be used as a new incremental backup object. Backup packaged.
如图4所示，执行增量恢复方案的过程为：As shown in Figure 4, the process of executing the incremental recovery scheme is:
S401：进行通讯，接收恢复计划要求的备份集；S401: Communicate and receive the backup set required by the recovery plan;
S402：检查是否需要恢复前备份，若是，执行备份操作后进入下一步，若否，直接进入下一步；S402: Check whether the backup before recovery is required, if yes, go to the next step after performing the backup operation, if not, go directly to the next step;
S403：调取恢复数据，执行恢复操作；S403: Retrieve the restored data, and execute the restored operation;
S404：检查恢复结果是否符合要求，若是，进入下一步，若否，返回上一步；S404: Check whether the recovery result meets the requirements, if yes, go to the next step, if not, return to the previous step;
S405：恢复过程记录并上传到数据库。S405: Record and upload the recovery process to the database.
如图5所示，执行裸设备恢复方案的过程为：As shown in Figure 5, the process of implementing the raw device recovery solution is as follows:
S501：制作LiveISO镜像光盘，在目标服务器上光驱载入该光盘，该光盘上的引导工具自动引导服务器启动并进入裸设备恢复程序；S501: Make a LiveISO image disc, load the disc on the target server, and the boot tool on the disc will automatically guide the server to start and enter the raw device recovery program;
S502：与备份库通讯，接收恢复所需要的备份介质和备份集；S502: Communicating with the backup database to receive backup media and backup sets required for recovery;
S503：恢复操作系统；S503: restore the operating system;
S504：安装RCT工具；S504: Install the RCT tool;
S505：恢复全备份数据；S505: restore full backup data;
S506：恢复增量备份数据；S506: Restore the incremental backup data;
S507：检查恢复结果是否符合要求，若是，进入下一步，若否，返回S502；S507: Check whether the recovery result meets the requirements, if yes, go to the next step, if not, return to S502;
S508：恢复过程记录并上传到数据库。S508: Record and upload the recovery process to the database.
在四种方案的执行过程中，目标节点或服务器包含的信息包括服务器的IP地址、服务器名称、支持的传输协议、操作系统类型和版本、文件系统类型、硬盘配置、内存配置、网卡配置、目录信息、组件信息等，其中，IP地址是备份与恢复中心识别众多备份目标服务器或者恢复目标服务器的依据，操作系统类型和版本、文件系统类型、硬盘配置、内存配置、网卡配置、目录信息、组件信息等，在输入目标服务器的用户名、密码后，都可以通过本平台的自动获取工具连接到目标服务器，执行相应系统命令自动获取。During the execution of the four schemes, the information contained in the target node or server includes the server’s IP address, server name, supported transport protocol, operating system type and version, file system type, hard disk configuration, memory configuration, network card configuration, directory Information, component information, etc. Among them, the IP address is the basis for the backup and recovery center to identify many backup target servers or recovery target servers, operating system type and version, file system type, hard disk configuration, memory configuration, network card configuration, directory information, components Information, etc., after entering the user name and password of the target server, can be connected to the target server through the automatic acquisition tool of this platform, and automatically obtained by executing the corresponding system command.
除本发明所述的结构外，其余均为现有技术。Except the structure described in the present invention, all the others are prior art.
以上所述只是本发明的优选实施方式，对于本技术领域的普通技术人员来说，在不脱离本发明原理的前提下，还可以做出若干改进和润饰，这些改进和润饰也被视为本发明的保护范围。The above is only a preferred embodiment of the present invention. For those of ordinary skill in the art, without departing from the principle of the present invention, some improvements and modifications can also be made, and these improvements and modifications are also considered as the present invention. protection scope of the invention.
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410319101.5ACN104063294B (en) | 2014-07-07 | 2014-07-07 | A kind of linux system backup and restoration methods |
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410319101.5ACN104063294B (en) | 2014-07-07 | 2014-07-07 | A kind of linux system backup and restoration methods |
| Publication Number | Publication Date |
|---|---|
| CN104063294Atrue CN104063294A (en) | 2014-09-24 |
| CN104063294B CN104063294B (en) | 2016-03-16 |
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410319101.5AActiveCN104063294B (en) | 2014-07-07 | 2014-07-07 | A kind of linux system backup and restoration methods |
| Country | Link |
|---|---|
| CN (1) | CN104063294B (en) |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105302671A (en)* | 2015-11-11 | 2016-02-03 | 中国建设银行股份有限公司 | Automatic backup and rollback method and device |
| CN106339278A (en)* | 2016-08-24 | 2017-01-18 | 浪潮电子信息产业股份有限公司 | Data backup and recovery method of network file system |
| CN106919477A (en)* | 2017-03-03 | 2017-07-04 | 上海爱数信息技术股份有限公司 | The analytic method and system of a kind of virtual disk |
| CN114610535A (en)* | 2022-02-21 | 2022-06-10 | 广州鼎甲计算机科技有限公司 | Linux operating system bare computer recovery method, system, device and storage medium |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100505614C (en)* | 2006-08-15 | 2009-06-24 | 华为技术有限公司 | System backup and recovery method and backup and recovery server |
| CN102693168A (en)* | 2011-03-22 | 2012-09-26 | 中兴通讯股份有限公司 | A method, a system and a service node for data backup recovery |
| US20120324280A1 (en)* | 2011-06-14 | 2012-12-20 | Computer Associates Think, Inc. | System and method for data disaster recovery |
| CN103885855A (en)* | 2012-12-20 | 2014-06-25 | 航天信息股份有限公司 | Data backup and recovery method and data backup and recovery device |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100505614C (en)* | 2006-08-15 | 2009-06-24 | 华为技术有限公司 | System backup and recovery method and backup and recovery server |
| CN102693168A (en)* | 2011-03-22 | 2012-09-26 | 中兴通讯股份有限公司 | A method, a system and a service node for data backup recovery |
| US20120324280A1 (en)* | 2011-06-14 | 2012-12-20 | Computer Associates Think, Inc. | System and method for data disaster recovery |
| CN103885855A (en)* | 2012-12-20 | 2014-06-25 | 航天信息股份有限公司 | Data backup and recovery method and data backup and recovery device |
| Title |
|---|
| 张兴发等: "分布式Linux下数据库文件自动备份和恢复", 《计算机时代》, no. 1, 31 January 2006 (2006-01-31), pages 16 - 17* |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105302671A (en)* | 2015-11-11 | 2016-02-03 | 中国建设银行股份有限公司 | Automatic backup and rollback method and device |
| CN106339278A (en)* | 2016-08-24 | 2017-01-18 | 浪潮电子信息产业股份有限公司 | Data backup and recovery method of network file system |
| CN106919477A (en)* | 2017-03-03 | 2017-07-04 | 上海爱数信息技术股份有限公司 | The analytic method and system of a kind of virtual disk |
| CN106919477B (en)* | 2017-03-03 | 2020-05-22 | 上海爱数信息技术股份有限公司 | Virtual disk analysis method and system |
| CN114610535A (en)* | 2022-02-21 | 2022-06-10 | 广州鼎甲计算机科技有限公司 | Linux operating system bare computer recovery method, system, device and storage medium |
| Publication number | Publication date |
|---|---|
| CN104063294B (en) | 2016-03-16 |
| Publication | Publication Date | Title |
|---|---|---|
| US11243849B2 (en) | Restoration of centralized data storage manager, such as data storage manager in a hierarchical data storage system | |
| US10007499B2 (en) | Decoupled installation of data management systems | |
| US11199985B2 (en) | Tracking storage capacity usage by snapshot lineages using metadata in a multi-level tree structure | |
| EP3069274B1 (en) | Managed service for acquisition, storage and consumption of large-scale data streams | |
| US11537553B2 (en) | Managing snapshots stored locally in a storage system and in cloud storage utilizing policy-based snapshot lineages | |
| US11630736B2 (en) | Recovering a storage volume associated with a snapshot lineage from cloud storage | |
| US11079960B2 (en) | Object storage system with priority meta object replication | |
| CN111614733A (en) | Deployment method, device and storage medium of distributed multi-fragmentation cluster | |
| CN111737227A (en) | Data modification method and system | |
| US11288134B2 (en) | Pausing and resuming copying of snapshots from a local snapshot lineage to at least one cloud snapshot lineage | |
| CN104063294B (en) | A kind of linux system backup and restoration methods | |
| TW201351264A (en) | System and method for storing distributed documents | |
| US11599276B1 (en) | Snapshot shipping to multiple cloud destinations | |
| US11573923B2 (en) | Generating configuration data enabling remote access to portions of a snapshot lineage copied to cloud storage | |
| US11093465B2 (en) | Object storage system with versioned meta objects | |
| US20230252229A1 (en) | Fast fill for computerized data input | |
| US9274724B1 (en) | Distributed virtual tape library | |
| US11366600B2 (en) | Moving snapshots from a local snapshot lineage on a storage system to a cloud snapshot lineage on cloud storage | |
| US11074002B2 (en) | Object storage system with meta object replication | |
| US20150370649A1 (en) | Sending a Request to a Management Service | |
| US11907163B1 (en) | Cloud snapshot lineage mobility between virtualization software running on different storage systems | |
| US12056023B2 (en) | Orchestration of storage system-based snapshot recovery | |
| DE112016004457T5 (en) | Duplicating data in data storage devices of a linked volume | |
| CN106649419A (en) | Electricity information acquisition system-based cross-platform database data migration method | |
| CN104809033A (en) | Backup method and system |
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |