CN112596951A - NAS data disaster tolerance method, device, equipment and storage medium - Google Patents
NAS data disaster tolerance method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN112596951A CN112596951A CN202011555678.8A CN202011555678A CN112596951A CN 112596951 A CN112596951 A CN 112596951A CN 202011555678 A CN202011555678 A CN 202011555678A CN 112596951 A CN112596951 A CN 112596951A
- Authority
- CN
- China
- Prior art keywords
- nas
- service
- data
- virtual machine
- backup
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 56
- 230000002159 abnormal effect Effects 0.000 claims abstract description 12
- 238000012986 modification Methods 0.000 claims description 64
- 230000004048 modification Effects 0.000 claims description 64
- 238000011084 recovery Methods 0.000 claims description 45
- 230000006870 function Effects 0.000 description 10
- 230000008569 process Effects 0.000 description 8
- 238000004891 communication Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 230000001360 synchronised effect Effects 0.000 description 5
- 238000013500 data storage Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
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/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0727—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a storage system, e.g. in a DASD or network based storage system
-
- 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/1464—Management of the backup or restore process for networked environments
-
- 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/1479—Generic software techniques for error detection or fault masking
- G06F11/1482—Generic software techniques for error detection or fault masking by means of middleware or OS functionality
- G06F11/1484—Generic software techniques for error detection or fault masking by means of middleware or OS functionality involving virtual machines
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
- G06F9/4451—User profiles; Roaming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45579—I/O management, e.g. providing access to device drivers or storage
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Quality & Reliability (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention belongs to the technical field of computers, and discloses a method, a device, equipment and a storage medium for NAS data disaster tolerance. When detecting that the source network storage NAS is abnormal, searching backup point data corresponding to the source NAS in a preset storage space; establishing a service takeover virtual machine according to the backup point data, and communicating the service takeover virtual machine with a source NAS network environment; and when the network environment is successfully communicated, modifying the configuration information of the NAS service in the service takeover virtual machine according to the NAS backup configuration information in the backup point data so that the service takeover virtual machine takes over the service request of the service system. After the service takeover virtual machine is communicated with the source NAS network environment and the configuration information of the NAS service in the service takeover virtual machine is modified according to the backup point data, the service takeover virtual machine can be normally accessed by the service system and can provide the same function as the source NAS, so that the service of the service system can be ensured to be normally performed, and the service continuity is ensured.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a storage medium for NAS data disaster recovery.
Background
A Network Attached Storage (NAS) is a device connected to a Network and having a data Storage function, and is also called a "Network Attached Storage", and is a special data Storage server. The NAS is widely applied to various industries, and is generally used for centrally storing business data and daily office data of organizations such as finance, government, school, hospital, enterprise, and the like. If the NAS fails and cannot be accessed normally, normal business handling and daily office work are seriously influenced, so that the guarantee of the business continuity of the NAS is particularly important.
The existing restoration method for NAS backup comprises the following steps: and backing up the data of the NAS, and providing services for the outside after completely recovering the backed-up data after the NAS device fails. The method has the following disadvantages: the NAS is used as a special data storage server, the data volume is usually huge, the data volume of common small and medium-sized enterprises is Terabyte (TB) level, the recovery time is usually in days, and the service continuity cannot be guaranteed in the recovery process.
The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.
Disclosure of Invention
The invention mainly aims to provide a method, a device, equipment and a storage medium for NAS data disaster recovery, and aims to solve the technical problem that service continuity cannot be guaranteed due to overlong NAS recovery time in the prior art.
In order to achieve the above object, the present invention provides a NAS data disaster recovery method, including the following steps:
when detecting that a source network storage (NAS) is abnormal, searching backup point data corresponding to the source NAS in a preset storage space;
establishing a service takeover virtual machine according to the backup point data, and communicating the service takeover virtual machine with the source NAS network environment;
and when the network environment is successfully communicated, modifying the configuration information of the NAS service in the service takeover virtual machine according to the NAS backup configuration information in the backup point data so that the service takes over the service request of the service system taken over by the virtual machine.
Optionally, after the step of modifying the configuration information of the NAS service in the service takeover virtual machine according to the NAS backup configuration information in the backup point data when the network environment is successfully connected, so that the service takeover virtual machine takes over the service request of the service system, the method further includes:
reversely synchronizing the data in the service takeover virtual machine to a target NAS;
and when the data synchronization is completed, switching to the service request of taking over the service system by the target NAS.
Optionally, before the step of modifying the configuration information of the NAS service in the service takeover virtual machine according to the NAS backup configuration information in the backup point data when the network environment is successfully connected, so that the service takeover virtual machine takes over the service request of the service system, the method further includes:
starting a file modification monitoring program in the service takeover virtual machine;
correspondingly, the step of reversely synchronizing the data in the service takeover virtual machine to the target NAS includes:
reversely synchronizing backup point data corresponding to the source NAS to a target NAS;
acquiring a file modification record of the file modification monitoring program record during the target NAS reconstruction;
and reversely synchronizing the data in the service takeover virtual machine to a target NAS according to the file modification record.
Optionally, before the step of switching to the service request that is taken over by the target NAS for the service system when the data synchronization is completed, the method further includes:
judging whether a file modification record exists during the period of reversely synchronizing the data in the service takeover virtual machine to the target NAS according to the file modification monitoring program;
and when no file modification record exists during the period of reversely synchronizing the data in the service takeover virtual machine to the target NAS, judging that the data synchronization is completed.
Optionally, after the step of determining whether a file modification record exists during a period of reversely synchronizing the data in the service takeover virtual machine to the target NAS according to the file modification monitoring program, the method further includes:
and when a file modification record exists during the period of reversely synchronizing the data in the service takeover virtual machine to the target NAS, returning to the step of reversely synchronizing the data in the service takeover virtual machine to the target NAS according to the file modification record.
Optionally, before the step of searching backup point data corresponding to the source NAS in a preset storage space when the source network storage NAS is detected to be abnormal, the method further includes:
when a file backup instruction is detected, setting a backup system for a source NAS, and acquiring network configuration information, NAS account information, user permission information and NAS backup data of the source NAS;
establishing NAS backup configuration information according to the network configuration information, the NAS account information and the user permission information;
and constructing backup point data according to the NAS backup data, the NAS backup configuration information set and the backup system and storing the backup point data to a preset storage space.
Optionally, the step of creating a service takeover virtual machine according to the backup point data includes:
obtaining NAS backup data and a backup system in the backup point data;
and creating a service takeover virtual machine in a preset virtual machine platform according to the NAS backup data and the backup system.
In addition, in order to achieve the above object, the present invention further provides a NAS data disaster recovery apparatus, including the following modules:
the data acquisition module is used for searching backup point data corresponding to a source Network Access Stratum (NAS) in a preset storage space when the NAS is detected to be abnormal;
the network connection module is used for creating a service takeover virtual machine according to the backup point data and communicating the service takeover virtual machine with the source NAS network environment;
and the configuration modification module is used for modifying the configuration information of the NAS service in the service takeover virtual machine according to the NAS backup configuration information in the backup point data when the network environment is successfully communicated, so that the service takeover virtual machine takes over the service request of the service system.
In addition, to achieve the above object, the present invention further provides a NAS data disaster recovery device, where the NAS data disaster recovery device includes: the NAS data disaster recovery system comprises a memory, a processor and a NAS data disaster recovery program stored on the memory and operable on the processor, wherein the NAS data disaster recovery program implements the steps of the NAS data disaster recovery method when executed by the processor.
In addition, in order to achieve the above object, the present invention further provides a computer-readable storage medium, where a NAS data disaster recovery program is stored, and when the NAS data disaster recovery program is executed, the steps of the NAS data disaster recovery method are implemented.
When detecting that the source network storage NAS is abnormal, searching backup point data corresponding to the source NAS in a preset storage space; establishing a service takeover virtual machine according to the backup point data, and communicating the service takeover virtual machine with a source NAS network environment; and when the network environment is successfully communicated, modifying the configuration information of the NAS service in the service takeover virtual machine according to the NAS backup configuration information in the backup point data so that the service takeover virtual machine takes over the service request of the service system. After the service takeover virtual machine is communicated with the source NAS network environment and the configuration information of the NAS service in the service takeover virtual machine is modified according to the backup point data, the service takeover virtual machine can be normally accessed by the service system and can provide the same function as the source NAS, so that the service of the service system can be ensured to be normally performed, and the service continuity is ensured.
Drawings
Fig. 1 is a schematic structural diagram of an electronic device in a hardware operating environment according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a NAS data disaster recovery method according to a first embodiment of the present invention;
FIG. 3 is a flowchart illustrating a NAS data disaster recovery method according to a second embodiment of the present invention;
fig. 4 is a schematic flow chart illustrating a process of reversely synchronizing data in a service takeover virtual machine to a target NAS in a second embodiment of the NAS data disaster recovery method according to the present invention;
fig. 5 is a block diagram of a NAS data disaster recovery apparatus according to a first embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Referring to fig. 1, fig. 1 is a schematic structural diagram of a NAS data disaster recovery device in a hardware operating environment according to an embodiment of the present invention.
As shown in fig. 1, the electronic device may include: a processor 1001, such as a Central Processing Unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a WIreless interface (e.g., a WIreless-FIdelity (WI-FI) interface). The Memory 1005 may be a Random Access Memory (RAM) Memory, or may be a Non-Volatile Memory (NVM), such as a disk Memory. The memory 1005 may alternatively be a storage device separate from the processor 1001.
Those skilled in the art will appreciate that the configuration shown in fig. 1 does not constitute a limitation of the electronic device and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
As shown in fig. 1, a storage 1005, which is a kind of storage medium, may include an operating system, a network communication module, a user interface module, and a NAS data disaster tolerance program.
In the electronic apparatus shown in fig. 1, the network interface 1004 is mainly used for data communication with a network server; the user interface 1003 is mainly used for data interaction with a user; the processor 1001 and the memory 1005 in the electronic device of the present invention may be disposed in the NAS data disaster recovery device, and the electronic device calls the NAS data disaster recovery program stored in the memory 1005 through the processor 1001 and executes the NAS data disaster recovery method provided in the embodiment of the present invention.
An embodiment of the present invention provides a NAS data disaster recovery method, and referring to fig. 2, fig. 2 is a schematic flow diagram of a first embodiment of a NAS data disaster recovery method according to the present invention.
In this embodiment, the NAS data disaster recovery method includes the following steps:
step S10: when detecting that a source network storage (NAS) is abnormal, searching backup point data corresponding to the source NAS in a preset storage space;
it should be noted that, an execution subject of this embodiment may be the NAS data disaster recovery device, and the NAS data disaster recovery device may be an electronic device such as a personal computer, a server, and the like, or may also be other devices that can achieve the same or similar functions.
It should be noted that the source NAS may be a device or apparatus that mainly provides a data storage function. The backup point data may be backup data constructed in advance from data, a configuration file, a system, and the like of the source NAS, and the backup point data may be created by performing a backup operation in advance.
Further, in order to construct backup point data in advance, before step S10, the method may further include:
when a file backup instruction is detected, setting a backup system for a source NAS, and acquiring network configuration information, NAS account information, user permission information and NAS backup data of the source NAS; establishing NAS backup configuration information according to the network configuration information, the NAS account information and the user permission information; and constructing backup point data according to the NAS backup data, the NAS backup configuration information set and the backup system and storing the backup point data to a preset storage space.
It should be noted that the NAS data disaster recovery device may execute a file backup operation when detecting a file backup instruction, where the file backup instruction may be sent to the NAS data disaster recovery device by another device, or may be automatically generated when the NAS data disaster recovery device detects that an instruction generation condition is satisfied, where the instruction generation condition may be a preset condition, for example: the file backup operation is performed every 30 minutes. The network configuration information of the source NAS may include configuration information of networks such as the internet and a local area network, the user permission information may include information such as a login account number, a login password, and an accessible path of the user, the NAS backup data may include a backup of all data in the source NAS, and the backup system may be a system identical to an original NAS operating system or a different system that may implement the same function. The preset storage space mentioned in this step may be the preset storage space in step S10, and storing the backup point data in the preset storage space may facilitate searching the backup point data corresponding to the source NAS in step S10.
In actual use, because the data volume of the source NAS is too large, if all data backup is carried out each time, the time is too long, so that historical backup point data can be searched in a preset storage space during file backup operation, and if the historical backup point data exists, the difference between the data of the current source NAS and the NAS backup data in the historical backup point data can be compared, and incremental updating is carried out to obtain NAS backup data required by the current backup operation; if no historical backup point data exists, all data backup can be performed to obtain NAS backup data.
Step S20: establishing a service takeover virtual machine according to the backup point data, and communicating the service takeover virtual machine with the source NAS network environment;
it should be noted that the service takeover virtual machine may be a virtual machine that is created according to the backup point data and that is the same as the data included in the source NAS and that can achieve the same function, and the communicating between the service takeover virtual machine and the source NAS network environment is to enable the service takeover virtual machine and the source NAS network environment to be in the same network environment, so as to ensure that the service system that previously sends the service request to the source NAS may also send the service request to the service takeover virtual machine.
In actual use, Virtual Local Area Network (VLAN) technology may be used to connect the traffic takeover Virtual machine with the source NAS Network environment.
Further, in order to facilitate management of the virtual machine, the step of creating a service takeover virtual machine according to the backup point data in this embodiment may include:
obtaining NAS backup data and a backup system in the backup point data; and creating a service takeover virtual machine in a preset virtual machine platform according to the NAS backup data and the backup system.
It should be noted that the preset virtual machine platform may be a preset virtual machine management platform, the preset virtual machine platform may be software running in the NAS data disaster recovery device, a virtual machine may be constructed and run in the preset virtual machine platform according to a specified system and a specified running directory, and each virtual machine running in the preset virtual machine platform may be uniformly managed by the preset virtual machine platform.
In actual use, the NAS backup data and the backup system in the backup point data can be obtained, the virtual machine system is specified in the preset virtual machine platform according to the backup system, the operation directory of the virtual machine is specified according to the NAS backup data, and the service takeover virtual machine is created, so that the service takeover virtual machine can achieve the same function as the source NAS and contain the same data.
Step S30: and when the network environment is successfully communicated, modifying the configuration information of the NAS service in the service takeover virtual machine according to the NAS backup configuration information in the backup point data so that the service takes over the service request of the service system taken over by the virtual machine.
It can be understood that, after the service takeover virtual machine is started, the configuration information of the NAS service in the service takeover virtual machine may be modified according to the NAS backup configuration information, the network configuration, the user permission configuration, and the like are modified to be consistent with the source NAS, and then the service takeover virtual machine is used to take over the service request of the service system, so that it may be ensured that the user may directly use the service of the service takeover virtual machine, and there is no difference from using the service of the source NAS.
In the embodiment, when the source network storage NAS is detected to be abnormal, backup point data corresponding to the source NAS is searched in a preset storage space; establishing a service takeover virtual machine according to the backup point data, and communicating the service takeover virtual machine with a source NAS network environment; and when the network environment is successfully communicated, modifying the configuration information of the NAS service in the service takeover virtual machine according to the NAS backup configuration information in the backup point data so that the service takeover virtual machine takes over the service request of the service system. After the service takeover virtual machine is communicated with the source NAS network environment and the configuration information of the NAS service in the service takeover virtual machine is modified according to the backup point data, the service takeover virtual machine can be normally accessed by the service system and can provide the same function as the source NAS, so that the service of the service system can be ensured to be normally performed, and the service continuity is ensured.
Referring to fig. 3, fig. 3 is a flowchart illustrating a NAS data disaster recovery method according to a second embodiment of the present invention.
Based on the first embodiment, after step S30, the NAS data disaster recovery method in this embodiment further includes:
step S40: reversely synchronizing the data in the service takeover virtual machine to a target NAS;
it can be understood that, after the service takeover virtual machine takes over the service request of the service system, the NAS in the formal environment may be reconstructed, the target NAS may be the source NAS, or may be an NAS reconstructed in the software production environment, and after the reconstruction is completed, the target NAS may operate normally, but before switching to the service request where the target NAS takes over the service system, data modified, added, or deleted during the reconstruction of the target NAS needs to be synchronized into the target NAS.
Further, in order to facilitate the data reverse synchronization, before step S30, the method may further include:
starting a file modification monitoring program in the service takeover virtual machine;
accordingly, step S40 of this embodiment may include:
reversely synchronizing backup point data corresponding to the source NAS to the target NAS; acquiring a file modification record recorded by the file modification monitoring program during the target NAS reconstruction; and reversely synchronizing the data in the service takeover virtual machine to a target NAS according to the file modification record.
It should be noted that the file modification monitoring program may record all file modification records in the service takeover virtual machine, for example: file addition records, file deletion records, file content modification records, and the like. According to the file modification record during the target NAS reconstruction, after the target NAS reconstruction is completed, the data difference between the service takeover virtual machine and the target NAS is obtained, namely the data difference between the target NAS and the service takeover virtual machine after the target NAS reconstruction is completed, the data in the service takeover virtual machine can be reversely synchronized into the target NAS according to the data difference, and the data consistency between the service takeover virtual machine and the target NAS is guaranteed.
Step S50: and when the data synchronization is completed, switching to the service request of taking over the service system by the target NAS.
It can be understood that when the data synchronization is completed, it can be said that the data and functions of the target NAS and the service takeover virtual machine are all agreed, and therefore, the service request for the service system to be taken over by the target NAS is switched at this time, so that normal operation of the service can be ensured, service interruption is not caused, and service continuity can be ensured.
Further, in order to better perform data synchronization, before step S50, the present embodiment may further include:
judging whether a file modification record exists during the period of reversely synchronizing the data in the service takeover virtual machine to the target NAS according to the file modification monitoring program; and when no file modification record exists during the period of reversely synchronizing the data in the service takeover virtual machine to the target NAS, judging that the data synchronization is completed.
It can be understood that there may be a service request during the reverse synchronization of the data in the service takeover virtual machine to the target NAS, and the data in the service takeover virtual machine may be modified again, so that the data synchronization needs to be continued.
In actual use, whether a file modification record exists during the period of reversely synchronizing the data in the service takeover virtual machine to the target NAS can be judged through the file modification record recorded by the file modification monitoring program, and if the file modification record does not exist during the period of reversely synchronizing the data in the service takeover virtual machine to the target NAS, it can be shown that the data in the target NAS and the data in the service takeover virtual machine are consistent, so that the completion of data synchronization can be judged.
Further, in order to describe how to process when a file modification record exists during reverse synchronization of data in the service takeover virtual machine to the target NAS, after the step of determining, according to the file modification monitoring program, whether a file modification record exists during reverse synchronization of data in the service takeover virtual machine to the target NAS, the method may further include:
and when a file modification record exists during the period of reversely synchronizing the data in the service takeover virtual machine to the target NAS, returning to the step of reversely synchronizing the data in the service takeover virtual machine to the target NAS according to the file modification record.
It can be understood that, when a file modification record exists during reverse synchronization of data in the service takeover virtual machine to the target NAS, it may be stated that data is modified during data synchronization, at this time, data of the target NAS and the service takeover virtual machine are not completely synchronized, and if it is determined that data synchronization is completed and a service request of the service system is taken over by the target NAS, data loss and the like may be caused. Therefore, the step of reversely synchronizing the data in the service takeover virtual machine to the target NAS according to the file modification record can be returned to continue the secondary synchronization of the data, and the phenomena of data loss and the like are avoided.
For example: as shown in fig. 4, fig. 4 is a schematic flowchart of the flow of reversely synchronizing data in the service takeover virtual machine to the target NAS in this embodiment.
In the embodiment, data in the service takeover virtual machine is reversely synchronized to the target NAS; and when the data synchronization is completed, switching to the service request of the service system taken over by the target NAS. The data can be ensured to be consistent with the data of the service takeover virtual machine after the target NAS is recovered to be normal, the service request of the service system can be normally taken over, and the service continuity is ensured not to be interrupted. And when the data synchronization is completed, the file modification record in the process of reversely synchronizing the data in the service takeover virtual machine to the target NAS is verified before the service request of the service takeover service system is switched to be taken over by the target NAS, and when the file modification record exists in the process of reversely synchronizing the data in the service takeover virtual machine to the target NAS, the data is secondarily synchronized, so that the phenomena of data loss and the like are avoided, and the service continuity and the data safety are further ensured.
In addition, an embodiment of the present invention further provides a storage medium, where a NAS data disaster recovery program is stored on the storage medium, and when executed by a processor, the NAS data disaster recovery program implements the steps of the NAS data disaster recovery method described above.
Referring to fig. 5, fig. 5 is a block diagram of a NAS data disaster recovery apparatus according to a first embodiment of the present invention.
As shown in fig. 5, a NAS data disaster recovery apparatus according to an embodiment of the present invention includes:
the data obtaining module 501 is configured to, when detecting that a source network storage NAS is abnormal, search backup point data corresponding to the source NAS in a preset storage space;
a network connection module 502, configured to create a service takeover virtual machine according to the backup point data, and connect the service takeover virtual machine with the source NAS network environment;
and a configuration modification module 503, configured to modify, according to the NAS backup configuration information in the backup point data, configuration information of an NAS service in the service takeover virtual machine when the network environment is successfully connected, so that the service takeover virtual machine takes over a service request of the service system.
In the embodiment, when the source network storage NAS is detected to be abnormal, backup point data corresponding to the source NAS is searched in a preset storage space; establishing a service takeover virtual machine according to the backup point data, and communicating the service takeover virtual machine with a source NAS network environment; and when the network environment is successfully communicated, modifying the configuration information of the service takeover virtual machine according to the NAS backup configuration information in the backup point data so as to enable the service takeover virtual machine to take over the service request of the service system. The service takeover virtual machine can be normally accessed by the service system and can provide the same function as the source NAS after being communicated with the source NAS network environment and modifying the configuration information of the service takeover virtual machine according to the backup point data, so that the service of the service system can be ensured to be normally performed, and the service continuity is ensured.
Further, the configuration modification module 503 is further configured to reversely synchronize data in the service takeover virtual machine to the target NAS; and when the data synchronization is completed, switching to the service request of taking over the service system by the target NAS.
Further, the configuration modification module 503 is further configured to start a file modification monitoring program in the service takeover virtual machine;
the configuration modification module 503 is further configured to reversely synchronize backup point data corresponding to the source NAS to a target NAS; acquiring a file modification record of the file modification monitoring program record during the target NAS reconstruction; and reversely synchronizing the data in the service takeover virtual machine to a target NAS according to the file modification record.
Further, the configuration modification module 503 is further configured to determine, according to the file modification monitoring program, whether a file modification record exists during a period of reversely synchronizing data in the service takeover virtual machine to the target NAS; and when no file modification record exists during the period of reversely synchronizing the data in the service takeover virtual machine to the target NAS, judging that the data synchronization is completed.
Further, the configuration modification module 503 is further configured to, when a file modification record exists during the period of reversely synchronizing the data in the service takeover virtual machine to the target NAS, return to the step of reversely synchronizing the data in the service takeover virtual machine to the target NAS according to the file modification record.
Further, the data obtaining module 501 is further configured to set a backup system for the source NAS when detecting the file backup instruction, and obtain network configuration information, NAS account information, user right information, and NAS backup data of the source NAS; establishing NAS backup configuration information according to the network configuration information, the NAS account information and the user permission information; and constructing backup point data according to the NAS backup data, the NAS backup configuration information set and the backup system and storing the backup point data to a preset storage space.
Further, the network connection module 502 is further configured to obtain NAS backup data and a backup system in the backup point data; and creating a service takeover virtual machine in a preset virtual machine platform according to the NAS backup data and the backup system.
It should be understood that the above is only an example, and the technical solution of the present invention is not limited in any way, and in a specific application, a person skilled in the art may set the technical solution as needed, and the present invention is not limited thereto.
It should be noted that the above-described work flows are only exemplary, and do not limit the scope of the present invention, and in practical applications, a person skilled in the art may select some or all of them to achieve the purpose of the solution of the embodiment according to actual needs, and the present invention is not limited herein.
In addition, the technical details that are not described in detail in this embodiment may refer to the NAS data disaster recovery method provided in any embodiment of the present invention, and are not described herein again.
Further, it is to be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention or portions thereof that contribute to the prior art may be embodied in the form of a software product, where the computer software product is stored in a storage medium (e.g. Read Only Memory (ROM)/RAM, magnetic disk, optical disk), and includes several instructions for enabling a terminal device (e.g. a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A NAS data disaster recovery method is characterized by comprising the following steps:
when detecting that a source network storage (NAS) is abnormal, searching backup point data corresponding to the source NAS in a preset storage space;
establishing a service takeover virtual machine according to the backup point data, and communicating the service takeover virtual machine with the source NAS network environment;
and when the network environment is successfully communicated, modifying the configuration information of the NAS service in the service takeover virtual machine according to the NAS backup configuration information in the backup point data so that the service takes over the service request of the service system taken over by the virtual machine.
2. The NAS data disaster recovery method according to claim 1, wherein after the step of modifying the configuration information of the NAS service in the service takeover virtual machine according to the NAS backup configuration information in the backup point data when the network environment is successfully connected, so that the service takeover virtual machine takes over the service request of the service system, the method further comprises:
reversely synchronizing the data in the service takeover virtual machine to a target NAS;
and when the data synchronization is completed, switching to the service request of taking over the service system by the target NAS.
3. The NAS data disaster recovery method according to claim 2, wherein before the step of modifying the configuration information of the NAS service in the service takeover virtual machine according to the NAS backup configuration information in the backup point data when the network environment is successfully connected, so that the service takeover virtual machine takes over the service request of the service system, the method further comprises:
starting a file modification monitoring program in the service takeover virtual machine;
correspondingly, the step of reversely synchronizing the data in the service takeover virtual machine to the target NAS includes:
reversely synchronizing backup point data corresponding to the source NAS to a target NAS;
acquiring a file modification record of the file modification monitoring program record during the target NAS reconstruction;
and reversely synchronizing the data in the service takeover virtual machine to a target NAS according to the file modification record.
4. The NAS data disaster recovery method according to claim 3, wherein before the step of switching to the service request of the service system taken over by the target NAS when the data synchronization is completed, the method further comprises:
judging whether a file modification record exists during the period of reversely synchronizing the data in the service takeover virtual machine to the target NAS according to the file modification monitoring program;
and when no file modification record exists during the period of reversely synchronizing the data in the service takeover virtual machine to the target NAS, judging that the data synchronization is completed.
5. The NAS data disaster recovery method according to claim 4, wherein after the step of determining whether a file modification record exists during a period of reversely synchronizing the data in the service takeover virtual machine to the target NAS according to the file modification monitoring program, the method further comprises:
and when a file modification record exists during the period of reversely synchronizing the data in the service takeover virtual machine to the target NAS, returning to the step of reversely synchronizing the data in the service takeover virtual machine to the target NAS according to the file modification record.
6. The NAS data disaster recovery method according to any one of claims 1 to 5, wherein before the step of searching backup point data corresponding to a source NAS in a preset storage space when detecting that the source network storage NAS is abnormal, the method further comprises:
when a file backup instruction is detected, setting a backup system for a source NAS, and acquiring network configuration information, NAS account information, user permission information and NAS backup data of the source NAS;
establishing NAS backup configuration information according to the network configuration information, the NAS account information and the user permission information;
and constructing backup point data according to the NAS backup data, the NAS backup configuration information set and the backup system and storing the backup point data to a preset storage space.
7. The NAS data disaster recovery method according to any one of claims 1 to 5, wherein said step of creating a service takeover virtual machine according to the backup point data comprises:
obtaining NAS backup data and a backup system in the backup point data;
and creating a service takeover virtual machine in a preset virtual machine platform according to the NAS backup data and the backup system.
8. An NAS data disaster recovery device, comprising:
the data acquisition module is used for searching backup point data corresponding to a source Network Access Stratum (NAS) in a preset storage space when the NAS is detected to be abnormal;
the network connection module is used for creating a service takeover virtual machine according to the backup point data and communicating the service takeover virtual machine with the source NAS network environment;
and the configuration modification module is used for modifying the configuration information of the NAS service in the service takeover virtual machine according to the NAS backup configuration information in the backup point data when the network environment is successfully communicated, so that the service takeover virtual machine takes over the service request of the service system.
9. A NAS data disaster recovery device, comprising: a memory, a processor, and a NAS data disaster recovery program stored on the memory and executable on the processor, the NAS data disaster recovery program when executed by the processor implementing the steps of the NAS data disaster recovery method according to any one of claims 1 to 7.
10. A computer-readable storage medium, having stored thereon a NAS data disaster recovery program, which when executed performs the steps of the NAS data disaster recovery method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011555678.8A CN112596951A (en) | 2020-12-24 | 2020-12-24 | NAS data disaster tolerance method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011555678.8A CN112596951A (en) | 2020-12-24 | 2020-12-24 | NAS data disaster tolerance method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112596951A true CN112596951A (en) | 2021-04-02 |
Family
ID=75202115
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011555678.8A Pending CN112596951A (en) | 2020-12-24 | 2020-12-24 | NAS data disaster tolerance method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112596951A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114625575A (en) * | 2022-05-16 | 2022-06-14 | 深圳市科力锐科技有限公司 | Business system synchronization method, device, equipment and storage medium |
| CN114968667A (en) * | 2022-05-30 | 2022-08-30 | 江苏安超云软件有限公司 | Backup management method and system |
| CN116382974A (en) * | 2023-03-21 | 2023-07-04 | 安芯网盾(北京)科技有限公司 | Customized data protection processing method |
| CN116610500A (en) * | 2023-07-20 | 2023-08-18 | 深圳市科力锐科技有限公司 | Data backup method, device, equipment and storage medium |
| CN116755930A (en) * | 2023-05-22 | 2023-09-15 | 中工数保(北京)科技有限公司 | Production service continuous protection method and device for industrial control system |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140229695A1 (en) * | 2013-02-13 | 2014-08-14 | Dell Products L.P. | Systems and methods for backup in scale-out storage clusters |
| CN105159944A (en) * | 2015-08-10 | 2015-12-16 | 北京思特奇信息技术股份有限公司 | Database emergency handling method and system |
| CN106357787A (en) * | 2016-09-30 | 2017-01-25 | 郑州云海信息技术有限公司 | Storage disaster tolerant control system |
| CN111143114A (en) * | 2018-11-02 | 2020-05-12 | 深信服科技股份有限公司 | Virtualization platform disaster tolerance method, system, server and storage medium |
| CN111381931A (en) * | 2018-12-29 | 2020-07-07 | 中兴通讯股份有限公司 | Disaster recovery method, device and system |
-
2020
- 2020-12-24 CN CN202011555678.8A patent/CN112596951A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140229695A1 (en) * | 2013-02-13 | 2014-08-14 | Dell Products L.P. | Systems and methods for backup in scale-out storage clusters |
| CN105159944A (en) * | 2015-08-10 | 2015-12-16 | 北京思特奇信息技术股份有限公司 | Database emergency handling method and system |
| CN106357787A (en) * | 2016-09-30 | 2017-01-25 | 郑州云海信息技术有限公司 | Storage disaster tolerant control system |
| CN111143114A (en) * | 2018-11-02 | 2020-05-12 | 深信服科技股份有限公司 | Virtualization platform disaster tolerance method, system, server and storage medium |
| CN111381931A (en) * | 2018-12-29 | 2020-07-07 | 中兴通讯股份有限公司 | Disaster recovery method, device and system |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114625575A (en) * | 2022-05-16 | 2022-06-14 | 深圳市科力锐科技有限公司 | Business system synchronization method, device, equipment and storage medium |
| CN114968667A (en) * | 2022-05-30 | 2022-08-30 | 江苏安超云软件有限公司 | Backup management method and system |
| CN116382974A (en) * | 2023-03-21 | 2023-07-04 | 安芯网盾(北京)科技有限公司 | Customized data protection processing method |
| CN116755930A (en) * | 2023-05-22 | 2023-09-15 | 中工数保(北京)科技有限公司 | Production service continuous protection method and device for industrial control system |
| CN116610500A (en) * | 2023-07-20 | 2023-08-18 | 深圳市科力锐科技有限公司 | Data backup method, device, equipment and storage medium |
| CN116610500B (en) * | 2023-07-20 | 2024-04-09 | 深圳市科力锐科技有限公司 | Data backup method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112596951A (en) | NAS data disaster tolerance method, device, equipment and storage medium | |
| CN104679534B (en) | System application installation package loading processing method, apparatus and terminal | |
| EP3477914A1 (en) | Data recovery method and device, and cloud storage system | |
| US9275060B1 (en) | Method and system for using high availability attributes to define data protection plans | |
| CN110619226A (en) | Platform-based data processing method, system, equipment and storage medium | |
| CN111143114A (en) | Virtualization platform disaster tolerance method, system, server and storage medium | |
| CN112380057A (en) | Data recovery method, device, equipment and storage medium | |
| CN112214351A (en) | Backup data recovery method and device, electronic equipment and storage medium | |
| CN111158957B (en) | Virtual machine file recovery method, system, device and storage medium | |
| CN114238495A (en) | Method and device for switching main cluster and standby cluster of database, computer equipment and storage medium | |
| CN113886143A (en) | Virtual machine continuous data protection method and device and data recovery method and device | |
| CN103838589A (en) | Plug-in unit deleting and recovering method and client side | |
| CN110972497A (en) | Disaster recovery method and device for virtualization platform | |
| CN106897063B (en) | Method and system for permanently adding OS boot entry to BIOS based on EFI | |
| CN115221156A (en) | Database cluster capacity expansion method and device, computer equipment and storage medium | |
| CN107623705B (en) | Storage mode upgrading method, device and system based on video cloud storage system | |
| CN108681494B (en) | Backup data restoration method and device, user equipment and storage medium | |
| CN114676118B (en) | Database switching method, device, equipment and storage medium | |
| CN115174596A (en) | Equipment remote copying method, device and medium | |
| CN116389233A (en) | Container cloud management platform active-standby switching system, method and device and computer equipment | |
| CN114995958A (en) | Virtualization platform information consistency control method, device and medium | |
| CN113342579A (en) | Data restoration method and device | |
| CN114064674A (en) | Data synchronization method, device, computer equipment, storage medium and product | |
| CN108509252B (en) | Virtual machine starting device and method and host | |
| CN111858175A (en) | Method and equipment for backing up cloud platform data based on mobile storage device |
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 |