CN111400100B - Management method and system for distributed software backup - Google Patents
Management method and system for distributed software backup Download PDFInfo
- Publication number
- CN111400100B CN111400100B CN202010182473.3A CN202010182473A CN111400100B CN 111400100 B CN111400100 B CN 111400100B CN 202010182473 A CN202010182473 A CN 202010182473A CN 111400100 B CN111400100 B CN 111400100B
- Authority
- CN
- China
- Prior art keywords
- backup
- read
- storage unit
- distributed software
- log
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1469—Backup restoration techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1471—Saving, restoring, recovering or retrying involving logging of persistent data for recovery
Abstract
The application discloses a management method and a system for distributed software backup, wherein the management method for the distributed software backup specifically comprises the following steps: in response to the start of the distributed software, the physical machine creates a virtual management node and at least one backup node; according to the read-write command of the distributed software, the virtual management node establishes a read-write log; sending the read-write log to a physical machine within a preset time window; searching a corresponding storage unit according to the read-write log, and sending a log entry corresponding to the storage unit to a backup node; and modifying the backup storage unit according to the log entry. The management method and the system for the distributed software backup can select the corresponding virtual management node for the distributed software, and uniformly manage the backup through the virtual management node, so that the data recovery can be normally carried out when the storage unit cannot be recovered due to abnormality, and the normal operation of the distributed software is ensured.
Description
Technical Field
The present application relates to the field of software, and in particular, to a management method and system for distributed software backup.
Background
In the prior art, distributed computers have been developed along with the ubiquitous idea of interconnection, the scale of software is continuously increased, more and more data information needs to be stored and processed, and the mode of a single server in the past cannot meet the use requirement, so that multitask parallel processing by using a distributed software system is generated. However, although the efficiency of such distributed software processing tasks is improved, the backup functionality remains less powerful. In the existing distributed processing system, the storage unit is usually relied on to perform self exception recovery or restart recovery, but if the storage unit has an exception which cannot be recovered, the distributed software cannot perform normal operation. Therefore, a stronger backup management mode is needed, which can perform data recovery when the storage unit corresponding to the distributed software is abnormal, and ensure the normal operation of the distributed software.
Disclosure of Invention
The application aims to provide a management method and a system for distributed software backup, which can uniformly manage backup data when a storage unit corresponding to distributed software is abnormal or the storage unit is artificially replaced, and make log entries in the backup storage unit consistent with the storage unit by modifying the backup storage unit in real time, so that the backup storage unit can replace the storage unit at any time when the storage unit is abnormal, and the normal operation of the distributed software is ensured.
In order to achieve the above object, the present application provides a management method for distributed software backup, which specifically includes the following steps: in response to the start of the distributed software, the physical machine creates a virtual management node and at least one backup node; according to the read-write command of the distributed software, the virtual management node establishes a read-write log; sending the read-write log to a physical machine within a preset time window; searching a corresponding storage unit according to the read-write log, and sending a log entry corresponding to the storage unit to a backup node; and modifying the backup storage unit according to the log entry.
The above, wherein, after the virtual management node is created, further comprising creating a backup storage unit.
As above, wherein, when creating the backup storage unit, a plurality of backup storage units are created according to the type of storage unit allocated to the distributed software by the virtual management node.
As above, the number of the virtual management nodes is one or more, and if there are a plurality of starting numbers of the distributed software, a plurality of virtual management nodes are set.
As described above, when the physical machine performs a read-write operation on one storage unit of the storage device of the distributed software in response to the read-write command of the distributed software, the virtual management node serves as an independent device to generate a corresponding read-write log according to the operation of the physical machine.
As above, the read-write log includes a logical address of the read-write operation, and the storage unit corresponding to the logical address is searched according to the logical address.
As above, before sending the read-write log to the physical machine, the method further includes determining a predetermined time window, and specifically includes the following steps: selecting a peak time period for sending the read-write log; in a peak time period, acquiring the total number of actually sent read-write logs and the number of actually successfully sent logs; calculating the successful sending probability of the read-write log; the probability P that the read-write log is successfully sent is expressed as P ═ S1/S2，S1Number of actual successful transmissions of the read-write log, S2Representing the total number of actually sent read-write logs; if P is greater than the designated probability, the peak time period is used as a preset time window to transmit the read-write log; if P is smallAnd selecting the time except the peak time period as a preset time window at the appointed probability, and transmitting the read-write log.
As above, searching the corresponding storage unit according to the read-write log, and sending the log entry corresponding to the storage unit to the backup node specifically includes the following steps: determining a storage unit set corresponding to the read-write log according to the read-write log; determining a log entry in a storage unit set; the log entry is sent to the backup node.
As above, the log entry is searched and determined according to the correspondence table, where the correspondence table includes at least one entry, and each entry includes the storage unit with the identifier and the log entry corresponding to the storage unit with the identifier.
A management system of distributed software backup comprises a physical machine, a virtual management node and a backup node; wherein the physical machine has distributed software running thereon; in response to the start of the distributed software, the physical machine creates a virtual management node and at least one backup node; according to the read-write command of the distributed software, the virtual management node establishes a read-write log; sending the read-write log to a physical machine within a preset time window; searching a corresponding storage unit according to the read-write log, and sending a log entry corresponding to the storage unit to a backup node; and modifying the backup storage unit according to the log entry.
The application has the following beneficial effects:
(1) the management method and the system for the distributed software backup can select the corresponding virtual management node for the distributed software, and uniformly manage the backup through the virtual management node, so that the data recovery can be normally carried out when the storage unit cannot be recovered due to abnormality, and the normal operation of the distributed software is ensured.
(2) The backup management method and the backup management system for the distributed software can establish the corresponding backup storage unit for the storage unit corresponding to the distributed software, and ensure the consistency of the data in the backup storage unit and the storage unit, so that the backup storage unit can replace the storage unit at any time.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art according to the drawings.
FIG. 1 is a flowchart of a method for managing distributed software backups provided according to an embodiment of the present application;
fig. 2 is a structural diagram of a management system for distributed software backup provided according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application are clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The application relates to a method and a system for managing backup of distributed software. According to the method and the device, when the storage unit corresponding to the distributed software is abnormal or the storage unit is artificially replaced, the backup data can be uniformly managed, the backup storage unit is modified in real time, the log entries in the backup storage unit can be consistent with the storage unit, and then the backup storage unit can replace the storage unit at any time when the storage unit is abnormal, so that the normal operation of the distributed software is guaranteed. The distributed software is suitable for a distributed system, is used for managing the distributed system or operating functions used in a certain distributed system, consists of a plurality of physical machines, and can exist on any one physical machine.
Fig. 1 is a flowchart illustrating a method for managing backup by distributed software according to the present application.
Step S110: in response to the initiation of the distributed software, the physical machine creates a virtual management node and at least one backup node.
The distributed software exists on the physical machine and is used for running in a distributed system comprising a plurality of physical machines, when the distributed software is started, the physical machine which starts the distributed software establishes a virtual management node and at least one backup node in the distributed system, wherein the virtual management node is used for monitoring the state of the distributed software and providing software and hardware resources. The backup node is used for managing backup contents of the distributed software, wherein the backup node is controlled by the virtual management node.
Preferably, after the virtual management node and the backup node are created, creating a backup storage unit is further included.
Further, when creating the backup storage unit, a plurality of backup storage units may be created according to the types of storage units allocated to the distributed software by the virtual management node. Further, the backup storage unit remains the same as the storage data in the storage unit to which the distributed software is allocated. When the storage unit is abnormal, the backup storage unit can replace the storage unit at any time, and normal operation of the physical machine is guaranteed.
Preferably, the number of virtual management nodes may be one or more, for example, when the number of the distributed software starts is plural, a plurality of virtual management nodes may be provided in the system.
Step S120: and according to the read-write command of the distributed software, the virtual management node establishes a read-write log.
In particular, the virtual management node may act as a stand-alone (e.g., server, physical machine) or virtual device (e.g., virtual machine).
If the virtual management node is an independent device, according to the read-write command of the distributed software, when the physical machine performs read-write operation on one storage unit of the storage device of the distributed software, the physical machine does not establish a read-write log, and the virtual management node generates a corresponding read-write log according to the operation of the physical machine.
If the virtual management node is a virtual device, the read-write log does not need to be established. When the distributed software sends a read-write command and the physical machine carries out read-write operation, the read-write log generated by the physical machine is directly obtained.
Specifically, the read-write log includes a logical address for performing the read-write operation, the logical address indicates a storage unit to be read and written, and the storage unit can be found according to the read-write log. And generating a corresponding read-write log according to the logical address.
Preferably, if the logical addresses accessed by the read-write command are different, a plurality of read-write logs can be generated.
Step S130: and sending the read-write log to the physical machine within a preset time window.
The time window refers to a time period when the physical machine notifies the virtual management node to update corresponding content, and the notification needs to be sent within a specified time period, and the sending of the notification is not allowed beyond the specified time period. Therefore, the virtual management node needs to send the read-write log to the physical machine within a specified time window.
Further, the determining the predetermined time window specifically includes the following steps:
step Q1: and selecting a peak time period for sending the read-write log.
Illustratively, if the number of times of concentrated or scattered transmission of the read-write log in a certain time period is the largest, the time period is taken as a peak time period.
Step Q2: and acquiring the total number of actually transmitted read-write logs and the number of actually successfully transmitted read-write logs in a peak time period.
Step Q3: and calculating the successful sending probability of the read-write log.
The probability P that the read-write log is successfully sent can be expressed as P ═ S1/S2In which S is1Number of actual successful transmissions of the read-write log, S2Representing the total number of actual transmissions of the read-write log. If P is larger than the designated probability, the peak time period can be used as a preset time window for transmitting the read-write log. And if the P is less than the designated probability, selecting the previous period or the later period of the peak time period as a preset time window, and transmitting the read-write log.
Preferably, before a period before or after the peak period is selected as the predetermined time window, the probability of successful sending of the read-write log in the period may also be calculated, and specifically, the formula in step Q2 may be referred to.
It is to be noted that the specific probability is set by human and can be changed, and the specific numerical value is not limited herein.
Step S140: and the physical machine searches the corresponding storage unit according to the read-write log and sends the log entry corresponding to the storage unit to the backup node.
The physical machine specifically comprises the following steps of searching the log entries according to the read-write log:
step D1: and determining a storage unit set corresponding to the read-write log.
Specifically, a storage unit set corresponding to the read-write log is determined, that is, storage units read and written by the distributed software are determined, and the distributed software performs read-write operation on the storage units.
Furthermore, because the read-write log has a logical address for performing the read-write operation, the corresponding storage unit and the storage unit set can be determined according to the logical address. If the logical address is one, the corresponding storage unit corresponds to one storage unit, and if the logical address is multiple, the corresponding storage units form a storage unit set.
Step D2: a log entry in a set of storage units is determined.
The log entries can be searched and determined through a corresponding relation table, wherein the corresponding relation table comprises at least one table entry, and each table entry comprises a storage unit with an identifier and a log entry corresponding to the storage unit with the identifier. The log entries represent the types and/or contents of data read and written by the physical machine during read and write operations.
Preferably, the identification forms in the storage unit and the log entry may be set to be the same or different, but it must be ensured that the corresponding relationship between the storage unit and the log entry can be found.
Step D3: the log entry is sent to the backup node.
Step S150: and the backup node modifies the backup storage unit according to the log entry.
Before modifying the backup storage unit, the method further comprises the following steps:
step X1: a set of backup storage units is determined.
Specifically, determining the backup storage unit set is determining a plurality of backup storage units corresponding to the storage unit set. And allocating a backup index to each storage unit in the storage unit set, wherein the backup index enables the storage unit and the backup storage unit to form a mapping relation, so that the backup storage unit set can be determined through the backup index, and the backup node modifies the corresponding backup storage unit.
Step X2: and judging whether the number of the backup storage units is the same as that of the storage units.
In the case of creating a backup storage unit, there may be a case where the storage unit and the backup storage unit exist in one-to-one or one-to-many. If there is a one-to-many storage cell and backup storage cell, step X3 is executed.
Step X3: the number of backup storage units is modified.
Preferably, the backup storage unit is deleted according to the type of the storage unit and the base type of the storage unit. For example, if the base type of the storage unit is int type, the non-int type unit in the backup storage unit is deleted accordingly.
Preferably, the storage units are maintained in one-to-one correspondence with the backup storage units.
Specifically, some log entries of the storage device are read into the storage unit through the physical machine, and other log entries of the storage device can also be read into the backup storage unit, so that the log entries in the storage unit and the backup storage unit are inconsistent, and if the storage unit is abnormal, the backup storage unit cannot replace the storage unit to perform data recovery. In order to prevent such inconsistency, the log entries in the backup storage unit need to be modified so that the contents in the backup storage unit can be kept up to date. The specific modification comprises the following steps:
step P1: a log entry in a storage unit is received.
Step P2: the log entries in the backup storage unit are queried.
Step P3: the log entries in the storage unit are compared with the log entries in the backup storage unit.
And if the two are consistent, the log entries in the backup storage unit are not modified. If the two are not consistent, step P4 is executed.
Step P4: the log entries in the backup storage unit are modified.
Specifically, the modification of the backup unit log entry is performed with the log entry in the storage unit as a reference. Specifically, if the storage unit stores log entry 1, log entry 3, and log entry 5. The backup storage unit stores log entry 3, log entry 5, and log entry 6. The log entry 6 is deleted and the backup node copies the received log entry 1 to the backup storage unit.
The present application further includes a management system for providing a distributed software backup, where the management system has a structure of a general server, as shown in fig. 2, the management system for providing a distributed software backup includes a physical machine 201, a virtual management node 202, and a backup node 203, where the physical machine 201 runs a distributed software 204, and the virtual management node 202 is configured to monitor a state of the distributed software 204 and provide software and hardware resources. The backup node 203 is used for managing backup contents of the distributed software 204, wherein the backup node 203 is controlled by the virtual management node 202. The processor thereon executes the management method of distributed software backup as described above, which is stored on the storage medium of the system in the form of computer instructions, by managing the virtual management node.
The application has the following beneficial effects:
(1) the management method and the system for the distributed software backup can select the corresponding virtual management node for the distributed software, and uniformly manage the backup through the virtual management node, so that the data recovery can be normally carried out when the storage unit cannot be recovered due to abnormality, and the normal operation of the distributed software is ensured.
(2) The backup management method and the backup management system for the distributed software can establish the corresponding backup storage unit for the storage unit corresponding to the distributed software, and ensure the consistency of the data in the backup storage unit and the storage unit, so that the backup storage unit can replace the storage unit at any time.
Although the present application has been described with reference to examples, which are intended to be illustrative only and not to be limiting of the application, changes, additions and/or deletions may be made to the embodiments without departing from the scope of the application.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A management method for distributed software backup is characterized by comprising the following steps:
in response to the start of the distributed software, the physical machine creates a virtual management node and at least one backup node;
according to the read-write command of the distributed software, the virtual management node establishes a read-write log;
sending the read-write log to a physical machine within a preset time window;
searching a corresponding storage unit according to the read-write log, and sending a log entry corresponding to the storage unit to a backup node;
modifying the backup storage unit according to the log entries;
before modifying the backup storage unit, the method further comprises the following steps:
determining a backup storage unit set;
judging whether the number of the backup storage units is the same as that of the storage units;
the number of backup storage units is modified.
2. The method for managing distributed software backups of claim 1, further comprising, after creating the virtual management node, creating a backup storage unit.
3. The method for managing distributed software backup according to claim 2, wherein when creating the backup storage unit, a plurality of backup storage units are created according to types of storage units allocated to the distributed software by the virtual management node.
4. The method for managing distributed software backup according to claim 3, wherein the number of the virtual management nodes is one or more, and when there is a plurality of the number of the distributed software backups, a plurality of virtual management nodes are provided.
5. The management method for distributed software backup as claimed in claim 1, wherein in response to the read-write command of the distributed software, when the physical machine performs read-write operation on one storage unit of the storage device of the distributed software, the virtual management node is used as an independent device to generate a corresponding read-write log according to the operation of the physical machine.
6. The distributed software backup management method according to claim 1, wherein the read-write log includes a logical address of the read-write operation, and the storage unit corresponding to the logical address is searched according to the logical address.
7. The method for managing distributed software backup according to claim 1, further comprising, before sending the read-write log to the physical machine, determining a predetermined time window, specifically comprising the steps of:
selecting a peak time period for sending the read-write log;
in a peak time period, acquiring the total number of actually sent read-write logs and the number of actually successfully sent logs;
calculating the successful sending probability of the read-write log;
the probability P that the read-write log is successfully sent is expressed as P ═ S1/S2，S1Number of actual successful transmissions of the read-write log, S2Representing the total number of actually sent read-write logs;
if P is greater than the designated probability, the peak time period is used as a preset time window to transmit the read-write log; and if the P is less than the designated probability, selecting the time except the peak time period as a preset time window, and transmitting the read-write log.
8. The distributed software backup management method according to claim 1, wherein searching for a corresponding storage unit according to the read-write log, and sending a log entry corresponding to the storage unit to the backup node specifically comprises the following steps:
determining a storage unit set corresponding to the read-write log according to the read-write log;
determining a log entry in a storage unit set;
the log entry is sent to the backup node.
9. The method for managing distributed software backup according to claim 8, wherein the log entries are searched and determined according to a correspondence table, the correspondence table includes at least one entry, and each entry includes an identified storage unit and a log entry corresponding to the identified storage unit.
10. A management system of distributed software backup is characterized by comprising a physical machine, a virtual management node and a backup node;
wherein the physical machine has distributed software running thereon;
in response to the start of the distributed software, the physical machine creates a virtual management node and at least one backup node;
according to the read-write command of the distributed software, the virtual management node establishes a read-write log;
sending the read-write log to a physical machine within a preset time window;
searching a corresponding storage unit according to the read-write log, and sending a log entry corresponding to the storage unit to a backup node;
modifying the backup storage unit according to the log entries;
before modifying the backup storage unit, the method further comprises the following steps:
determining a backup storage unit set;
judging whether the number of the backup storage units is the same as that of the storage units;
the number of backup storage units is modified.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010182473.3A CN111400100B (en) | 2020-03-16 | 2020-03-16 | Management method and system for distributed software backup |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010182473.3A CN111400100B (en) | 2020-03-16 | 2020-03-16 | Management method and system for distributed software backup |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111400100A CN111400100A (en) | 2020-07-10 |
| CN111400100B true CN111400100B (en) | 2021-05-28 |
Family
ID=71434791
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010182473.3A Active CN111400100B (en) | 2020-03-16 | 2020-03-16 | Management method and system for distributed software backup |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111400100B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113286177B (en) * | 2021-07-26 | 2021-09-28 | 北京小鸟科技股份有限公司 | Block chain based distributed video processing system |
Family Cites Families (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103544076B (en) * | 2012-07-13 | 2016-04-06 | 阿里巴巴集团控股有限公司 | A kind of data back up method and device |
| CN103810060A (en) * | 2013-11-21 | 2014-05-21 | 北京奇虎科技有限公司 | Data backup method and system thereof based on distributed database |
| CN103929276B (en) * | 2014-04-30 | 2017-02-15 | 中国科学院微电子研究所 | Rate self-adaption method and system of wireless body area network |
| CN104320401B (en) * | 2014-10-31 | 2018-06-22 | 北京思特奇信息技术股份有限公司 | A kind of big data storage based on distributed file system accesses system and method |
| CN104866394B (en) * | 2015-06-08 | 2018-03-09 | 肖选文 | A kind of distributed document backup method and system |
| CN105511987A (en) * | 2015-12-08 | 2016-04-20 | 上海爱数信息技术股份有限公司 | Distributed task management system with high consistency and availability |
| US10567500B1 (en) * | 2015-12-21 | 2020-02-18 | Amazon Technologies, Inc. | Continuous backup of data in a distributed data store |
| US10216588B2 (en) * | 2016-11-22 | 2019-02-26 | Sap Se | Database system recovery using preliminary and final slave node replay positions |
| CN106682227A (en) * | 2017-01-06 | 2017-05-17 | 郑州云海信息技术有限公司 | Log data storage system based on distributed file system and reading-writing method |
| CN108363641B (en) * | 2017-01-26 | 2022-01-14 | 华为技术有限公司 | Main and standby machine data transmission method, control node and database system |
| CN109656911B (en) * | 2018-12-11 | 2023-08-01 | 江苏瑞中数据股份有限公司 | Distributed parallel processing database system and data processing method thereof |
| CN110162534B (en) * | 2019-05-30 | 2021-10-26 | 阿波罗智能技术(北京)有限公司 | Data management method and data storage system |
-
2020
- 2020-03-16 CN CN202010182473.3A patent/CN111400100B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN111400100A (en) | 2020-07-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5075736B2 (en) | System failure recovery method and system for virtual server | |
| US9917741B2 (en) | Method and system for processing network activity data | |
| US7552447B2 (en) | System and method for using root cause analysis to generate a representation of resource dependencies | |
| CN105357038B (en) | Monitor the method and system of cluster virtual machine | |
| CN110807064B (en) | Data recovery device in RAC distributed database cluster system | |
| CN109558260B (en) | Kubernetes fault elimination system, method, equipment and medium | |
| CN106452836B (en) | main node setting method and device | |
| CN111240806B (en) | Distributed container mirror image construction scheduling method | |
| US20030014522A1 (en) | Activating a volume group without a quorum of disks in the volume group being active | |
| CN109308242A (en) | A kind of dynamic monitoring and controlling method, device, equipment and storage medium | |
| CN111400100B (en) | Management method and system for distributed software backup | |
| CN109558209B (en) | Monitoring method for virtual machine | |
| CN112261114A (en) | Data backup system and method | |
| CN111404737B (en) | Disaster recovery processing method and related device | |
| CN116540938A (en) | Data reading method, device, distributed storage system, equipment and storage medium | |
| US11762741B2 (en) | Storage system, storage node virtual machine restore method, and recording medium | |
| CN115309336A (en) | Data writing method, cache information updating method and related device | |
| CN114791900A (en) | Operator-based Redis operation and maintenance method, device, system and storage medium | |
| CN111381969B (en) | Management method and system of distributed software | |
| US11636013B2 (en) | Event-driven system failover and failback | |
| CN113032141B (en) | AI platform resource switching method, system and medium | |
| US20230118525A1 (en) | Recovery of a software-defined data center | |
| CN113609199A (en) | Database system, server, and storage medium | |
| CN116467282A (en) | Database creation method and device and storage medium | |
| JP2023061137A (en) | Management method of virtual server and virtual server management system used for the same |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20210507 Address after: 310016 room 304, building A07, 9 Jiusheng Road, Jianggan District, Hangzhou City, Zhejiang Province Applicant after: Hangzhou Kunze Industrial Co.,Ltd. Address before: 101300 room 3001, 3rd floor, 102 door, building 8, yard 12, Xinzhong street, Nanfaxin Town, Shunyi District, Beijing Applicant before: Beijing Weijie Dongbo Information Technology Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |