Disaster recovery system client configuration method, device, equipment, medium and product

Abstract

The embodiment of the invention discloses a disaster recovery system client configuration method and device, equipment, a medium and a product, and the method comprises the steps: responding to a disaster recovery system node creation instruction, displaying a node creation interaction interface of a disaster recovery system, responding to a selection instruction of any node function role in a disaster recovery system node function role list, and displaying the node creation interaction interface of the disaster recovery system; determining a target function role of the to-be-created node and displaying a node parameter configuration interface corresponding to the target function role; and in the node parameter configuration interface, in response to the parameter configuration operation, determining node configuration parameters of the to-be-created node, and sending the node configuration parameters to the target disaster recovery system client to complete the configuration of the disaster recovery system client. According to the technical scheme provided by the embodiment of the invention, the problem that the configuration speed is influenced by various configuration items of the current disaster recovery system client is solved, the parameter configuration flexibility and the adaptability with different function nodes can be improved by providing the parameter configuration nodes matched with the node function roles, and the configuration efficiency is improved.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of computer technology, and in particular, to a method, device, equipment, medium and product for configuring a disaster recovery system client. Background Art

[0002] With the continuous development of information technology, information systems play an important and irreplaceable role in the core businesses of various industries. In actual production, it is necessary to ensure the integrity of information and business continuity. Especially in fields such as finance, e-commerce, government affairs, and healthcare, data damage and business interruption are unacceptable. Therefore, in order to ensure data integrity and business continuity, a reliable and efficient disaster recovery solution is an essential part of the system business.

[0003] In the current disaster recovery system, nodes are installed as clients on the source machines to be protected or on the standby machines of the backup servers. Then the nodes are registered with the disaster recovery platform, and various protection rules are added and tasks are controlled and scheduled through the disaster recovery platform.

[0004] With the continuous upgrade and iteration of the disaster recovery system, the functions that nodes need to implement gradually become more complex from being single, and the node configuration items that need to be maintained on the disaster recovery platform also become more and more numerous. Users often feel complex and even confused when maintaining nodes in the face of numerous configuration items. At the same time, the nodes registered by users on the disaster recovery platform have different production functions, and not all configuration items are required to be displayed and configured. Summary of the Invention

[0005] Embodiments of the present invention provide a method, device, equipment, medium and product for configuring a disaster recovery system client, which can configure nodes by providing parameters matching the functional roles of the nodes, improve the flexibility of parameter configuration and the adaptability to different functional nodes, and improve the configuration efficiency.

[0006] In a first aspect, embodiments of the present invention provide a method for configuring a disaster recovery system client, the method including:

[0007] Responding to a disaster recovery system node creation instruction, presenting a node creation interaction interface of the disaster recovery system; wherein, the node creation interaction interface is provided with a list of disaster recovery system node functional roles;

[0008] On the node creation interaction interface, in response to a selection instruction for any node functional role in the list of disaster recovery system node functional roles, determining the target functional role of the node to be created, and presenting a node parameter configuration interface corresponding to the target functional role;

[0009] In the node parameter configuration interface, in response to a parameter configuration operation, determine the node configuration parameters of the node to be created, and send the node configuration parameters to the target disaster recovery system client to complete the configuration of the disaster recovery system client.

[0010] In a second aspect, an embodiment of the present invention provides a disaster recovery system client configuration device, which includes:

[0011] A role list display module, configured to display a node creation interaction interface of the disaster recovery system in response to a disaster recovery system node creation instruction; wherein, the node creation interaction interface is provided with a list of node function roles of the disaster recovery system;

[0012] A configuration interface display module, configured to determine the target function role of the node to be created in the node creation interaction interface in response to a selection instruction for any node function role in the list of node function roles of the disaster recovery system, and display the node parameter configuration interface corresponding to the target function role;

[0013] A configuration parameter sending module, configured to determine the node configuration parameters of the node to be created in the node parameter configuration interface in response to a parameter configuration operation, and send the node configuration parameters to the target disaster recovery system client to complete the configuration of the disaster recovery system client.

[0014] In a third aspect, an embodiment of the present invention further provides a computer device, which includes:

[0015] One or more processors;

[0016] A memory for storing one or more programs;

[0017] When the above one or more programs are executed by the one or more processors, the one or more processors implement the disaster recovery system client configuration method provided in any embodiment of the present invention.

[0018] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, it implements the disaster recovery system client configuration method provided in any embodiment of the present invention.

[0019] In a fifth aspect, an embodiment of the present invention further provides a computer program product, including a computer program, and when the computer program is executed by a processor, it implements the disaster recovery system client configuration method provided in any embodiment of the present invention.

[0020] The embodiments in the above invention have the following advantages or beneficial effects:

[0021] The embodiment of the present invention displays a node creation interactive interface of the disaster recovery system in response to a disaster recovery system node creation instruction; wherein the node creation interactive interface is provided with a disaster recovery system node function role list; in the node creation interactive interface, in response to a selection instruction for any node function role in the disaster recovery system node function role list, the target function role of the node to be created is determined, and a node parameter configuration interface corresponding to the target function role is displayed; in the node parameter configuration interface, in response to a parameter configuration operation, the node configuration parameters of the node to be created are determined, and the node configuration parameters are sent to the target disaster recovery system client to complete the configuration of the disaster recovery system client. The technical solution of the embodiment of the present invention solves the problem that the configuration speed is affected by the large number of configuration items of the current disaster recovery system client, and can improve the flexibility of parameter configuration and the adaptability to different function nodes and the configuration efficiency by providing parameter configuration nodes that match the node function roles. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 It is a flow chart of a method for configuring a client of a disaster recovery system provided by an embodiment of the present invention;

[0023] Figure 2 It is a flow chart of a method for configuring a client of a disaster recovery system provided by an embodiment of the present invention;

[0024] Figure 3 This is a schematic diagram of a node creation interaction interface provided by an embodiment of the present invention;

[0025] Figure 4 This is a schematic diagram of a node creation interaction interface provided by an embodiment of the present invention;

[0026] Figure 5 This is a schematic diagram of a node parameter configuration interface provided by an embodiment of the present invention;

[0027] Figure 6 This is a schematic diagram of a node parameter configuration interface provided by an embodiment of the present invention;

[0028] Figure 7 This is a schematic diagram of a disaster recovery system node list page provided by an embodiment of the present invention;

[0029] Figure 8 It is a structural diagram of a disaster recovery system client configuration system provided by an embodiment of the present invention;

[0030] Figure 9 It is a structural schematic diagram of a computer device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0031] The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It can be understood that the specific embodiments described herein are only for explaining the present invention, rather than limiting the present invention. Additionally, it should be noted that for the convenience of description, only the parts related to the present invention rather than all the structures are shown in the drawings.

[0032] Figure 1 The following is a flowchart of a method for configuring a disaster recovery system client provided by an embodiment of the present invention. This embodiment is applicable to the scenario of configuring a disaster recovery system client. This method can be executed by a disaster recovery system client configuration device, which can be implemented in software and / or hardware and integrated in a computer device with application development functions.

[0033] As Figure 1 shown, the method for configuring a disaster recovery system client in this embodiment includes the following steps:

[0034] S110. In response to a disaster recovery system node creation instruction, display a node creation interaction interface for the disaster recovery system.

[0035] A disaster recovery platform node refers to a physical device or virtual resource instance that can perform data processing during the disaster recovery process, and can be installed as a client on the source machine to be protected or as a standby machine of a backup server.

[0036] The user triggers a node creation instruction on the preset management interface of the disaster recovery system, and the system displays a node creation interaction interface according to the node creation instruction. The node creation interaction interface is used to create a node, that is, to register the node to be managed into the disaster recovery system.

[0037] The node creation interaction interface is provided with a list of disaster recovery system node function roles, and at least two selectable node function role items are displayed in the list of disaster recovery system node function roles for the user to select.

[0038] S120. On the node creation interaction interface, in response to a selection instruction for any node function role in the list of disaster recovery system node function roles, determine the target function role of the node to be created, and display a node parameter configuration interface corresponding to the target function role.

[0039] The list of disaster recovery system node function roles may include at least two selectable node function roles. The selected node function role is determined as the target function role of the node to be created, and according to the preset correspondence between the function role and the configuration interface, a node parameter configuration interface corresponding to the target function role is displayed.

[0040] It can be understood that for different nodes, due to different production functions of the devices, the configuration items required by the nodes are also different. If all possible configuration items that may need to be set are displayed each time a node is created, it will increase the user's configuration time, reduce the efficiency of node creation, and during the setting process, the user may miss the items that must be set, affecting the effect of parameter configuration. Therefore, in this embodiment, according to the preset functional roles, the necessary configuration items for the functional roles are determined, and a node parameter configuration interface is created based on the necessary configuration items. When the user selects a target functional role, according to the corresponding relationship between the preset functional role and the configuration interface, the node parameter configuration interface corresponding to the target functional role is displayed.

[0041] S130. In the node parameter configuration interface, in response to a parameter configuration operation, determine the node configuration parameters of the node to be created, and send the node configuration parameters to the target disaster recovery system client to complete the configuration of the disaster recovery system client.

[0042] In the node parameter configuration interface, in response to the parameter configuration result input and submitted by the user, determine the node configuration parameters of the node to be created, and send the node configuration parameters to the target disaster recovery system client corresponding to the node according to the preset communication protocol. The disaster recovery system client implements the configuration parameter setting according to the received node configuration parameters.

[0043] The technical solution of this embodiment, by responding to a disaster recovery system node creation instruction, displays a node creation interaction interface of the disaster recovery system; wherein, the node creation interaction interface is provided with a list of disaster recovery system node functional roles; in the node creation interaction interface, in response to a selection instruction for any node functional role in the list of disaster recovery system node functional roles, determine the target functional role of the node to be created, and display the node parameter configuration interface corresponding to the target functional role; in the node parameter configuration interface, in response to a parameter configuration operation, determine the node configuration parameters of the node to be created, and send the node configuration parameters to the target disaster recovery system client to complete the configuration of the disaster recovery system client. The technical solution of the embodiment of the present invention solves the problem that the current disaster recovery system client has a large number of configuration items affecting the configuration speed, and can improve the flexibility of parameter configuration and the adaptability to different functional nodes by providing a parameter configuration node matching the node functional role, thereby improving the configuration efficiency.

[0044] Figure 2 It is a flowchart of a method for configuring a disaster recovery system client provided by an embodiment of the present invention. This embodiment and the method for configuring a disaster recovery system client in the above embodiment belong to the same inventive concept, and further describe the process of node management. This method can be executed by a disaster recovery system client configuration device, and the device can be implemented in a software and / or hardware manner and integrated in a computer device with application development functions.

[0045] As Figure 2As shown in the figure, the method for configuring the disaster recovery system client in this embodiment includes the following steps:

[0046] S210. In response to the disaster recovery system node creation instruction, display the node creation interaction interface of the disaster recovery system.

[0047] The node creation interaction interface is provided with a list of functional roles of the disaster recovery system nodes. As Figure 3 shown, the list of functional roles of the disaster recovery system nodes can be displayed in the form of a tab, that is, Figure 3 the "Role Setting" tab in . In the "Role Setting" tab, the node functional role is a required option, and the default role can be set according to actual needs, that is, the node functional role control that is default selected after entering the "Role Setting" tab.

[0048] In an alternative embodiment, the functional roles in the list of functional roles of the disaster recovery system nodes include: disaster recovery host, migration source machine, migration target machine, backup client, backup server, full server backup management software client, data copy management software client, and proxy virtual machine.

[0049] Different node functional roles have different production functions. For example, the disaster recovery host is used to take over the business in case of a disaster to ensure business continuity. The migration source machine is used to provide the data and applications to be migrated and cooperate to complete backup or migration. The migration target machine is used to receive and run the migrated data and applications to achieve business transition. The backup client is used to collect data and status information, backup according to the policy and receive instructions. The backup server is used to store backup data, manage backup tasks, and provide data recovery. The full server backup management software client is used to cooperate with the software to comprehensively manage the server backup. The data copy management software client is used to manage the creation, storage, and use of data copies. The proxy virtual machine is used to simulate the real environment and assist in completing tasks such as testing and backup.

[0050] S220. On the node creation interaction interface, in response to the selection instruction for any node functional role in the list of functional roles of the disaster recovery system nodes, determine the target functional role of the node to be created, and display the node parameter configuration interface corresponding to the target functional role.

[0051] As Figure 4 shown, Figure 4 in , the selectable node functional role controls are provided through the node creation interaction interface. If the user selects the "Backup Client" control, it is determined that the target functional role of the node to be created is the backup client.

[0052] In response to the user's selection instruction for the node functional role, such as the selection instruction generated by the tick operation, display the node parameter configuration interface corresponding to the target functional role. The node parameter configuration interface can include one or more parameter configuration tabs. As Figure 4The "Backup Client" role is selected as shown, and then the "SAN Settings" tab is displayed, and is displayed side by side with the "Role Settings" tab, the "Basic Settings" tab, and the "Monitoring and Alarms" tab. The "Role Settings" tab, the "Basic Settings" tab, and the "Monitoring and Alarms" tab are the default display tabs. For different node function roles, the associated role tabs may include the same role tabs. For example, the node parameter configuration interfaces for the "Backup Client" role and the "Backup Server" role may both include the "SAN Settings" tab.

[0053] In an alternative embodiment, when the target function role is a backup server, the node parameter configuration interface includes:

[0054] Backup set metadata directory configuration control, backup set metadata retention policy configuration control, backup data cache directory configuration control, backup data cache upper limit configuration control, and cache disk remaining lower limit configuration control.

[0055] As Figure 5 shown, the "Backup Server" is bound to both the "Backup Server Settings" and "SAN Settings" tabs.

[0056] The configuration items included in the "Backup Server Settings" tab are all or all required configuration items in the "Backup Server Settings" and "SAN Settings" tabs. In the "Backup Server" tab, according to the specific functions, it is further divided into three sub-tabs: "Server Settings", "ETCD Access Settings", and "Backup Data Security", which further improves the flexibility of the display of node role configuration items.

[0057] The "Server Settings" sub-tab includes a backup set metadata directory configuration control, a backup set metadata retention policy configuration control, a backup data cache directory configuration control, a backup data cache upper limit configuration control, and a cache disk remaining lower limit configuration control.

[0058] The control can be an input box and an optional list, or other form controls, which are not limited in this embodiment. In the backup set metadata retention policy configuration control, selection prompts are also displayed in the optional items according to different roles. For example, the selected item includes a prompt content of "Backup Client + Backup Server Recommendation".

[0059] In an alternative embodiment, when the target function role is a disaster recovery host, the node parameter configuration interface includes:

[0060] Data cache directory configuration control, memory usage upper limit configuration control, disk usage upper limit configuration control, and disk remaining space threshold configuration control.

[0061] As Figure 6As shown, when the target functional role is a disaster recovery host, the node parameter configuration interface includes a disaster recovery host settings tab, and the disaster recovery host settings tab includes a data cache directory configuration control, a memory usage upper limit configuration control, a disk usage upper limit configuration control, and a disk remaining space threshold configuration control.

[0062] In an alternative embodiment, the target functional role of the node to be created includes two or more functional roles in the disaster recovery system node functional role list.

[0063] In the "Role Settings" tab, one or more target functional roles can be selected for the node to be created.

[0064] S230. In the node parameter configuration interface, in response to a parameter configuration operation, determine the node configuration parameters of the node to be created, and send the node configuration parameters to the target disaster recovery system client to complete the configuration of the disaster recovery system client.

[0065] S240. In response to a node management interface trigger operation, display the disaster recovery system node list page.

[0066] Among them, the list items on the disaster recovery system node list page include node functional roles.

[0067] The list items on the disaster recovery system node list page include the name of each disaster recovery system node and the node information of the disaster recovery system node. As Figure 7 shown, the node information may include node functional roles, node addresses, node status, operating systems, software versions, etc. Different icons can be used to represent different power-saving functional roles. For example, icon A represents the migration target machine, icon B represents the backup server, and icon C represents the backup client. Then the node functional roles of node 1 are the migration target machine and the backup server, and the node functional role of node 2 is the backup client.

[0068] S250. In response to a management operation on at least one disaster recovery system node in the disaster recovery system node list page, complete the management of the disaster recovery system node.

[0069] Among them, the management operations include any one of new creation, deletion, batch registration, batch modification, refresh, information export, and quick new creation.

[0070] As Figure 7 shown, selecting any one of the new creation, batch registration, refresh, information export, and quick new creation controls can complete the operation represented by the control name.

[0071] Select the row corresponding to at least one node, and select deletion or batch modification in the following controls to perform the deletion and batch modification operations on the corresponding nodes.

[0072] The technical solution of this embodiment is to display the node creation interaction interface of the disaster recovery system in response to the disaster recovery system node creation instruction; wherein, the node creation interaction interface is provided with a list of function roles of the disaster recovery system nodes; in the node creation interaction interface, in response to the selection instruction of any node function role in the list of function roles of the disaster recovery system nodes, determine the target function role of the node to be created, and display the node parameter configuration interface corresponding to the target function role; in the node parameter configuration interface, in response to the parameter configuration operation, determine the node configuration parameters of the node to be created, and send the node configuration parameters to the target disaster recovery system client to complete the configuration of the disaster recovery system client; in response to the node management interface trigger operation, display the disaster recovery system node list page; wherein, the list items of the disaster recovery system node list page include node function roles; in response to the management operation on at least one disaster recovery system node in the disaster recovery system node list page, complete the management of the disaster recovery system node; wherein, the management operation includes any one of new creation, deletion, batch registration, batch modification, refresh, information export, and quick new creation. The technical solution of the embodiment of the present invention solves the problem that the current disaster recovery system client has a large number of configuration items, which affects the configuration speed. By providing parameter configuration nodes that match the node function roles, the flexibility of parameter configuration and the adaptability to different function nodes can be improved, the configuration efficiency can be improved, and by displaying the node function roles in the node management node, users can quickly obtain the business functions of the nodes, and the efficiency of node management can be improved.

[0073] Figure 8 FIG. 4 is a schematic structural diagram of a disaster recovery system client configuration device provided by an embodiment of the present invention. This embodiment is applicable to the scenario of disaster recovery system client configuration. The disaster recovery system client configuration device can be implemented in a software and / or hardware manner and integrated in a computer terminal device with application development functions.

[0074] As Figure 8 shown, the disaster recovery system client configuration device includes: a role list display module 310, a configuration interface display module 320, and a configuration parameter sending module 330.

[0075] Among them, the role list display module 310 is configured to display the node creation interaction interface of the disaster recovery system in response to the disaster recovery system node creation instruction; wherein, the node creation interaction interface is provided with a list of function roles of the disaster recovery system nodes; the configuration interface display module 320 is configured to, in the node creation interaction interface, in response to the selection instruction of any node function role in the list of function roles of the disaster recovery system nodes, determine the target function role of the node to be created, and display the node parameter configuration interface corresponding to the target function role; the configuration parameter sending module 330 is configured to, in the node parameter configuration interface, in response to the parameter configuration operation, determine the node configuration parameters of the node to be created, and send the node configuration parameters to the target disaster recovery system client to complete the configuration of the disaster recovery system client.

[0076] The technical solution of this embodiment is to display the node creation interactive interface of the disaster recovery system in response to the disaster recovery system node creation instruction; wherein the node creation interactive interface is provided with a list of node function roles of the disaster recovery system; in the node creation interactive interface, in response to the selection instruction of any node function role in the list of node function roles of the disaster recovery system, the target function role of the node to be created is determined, and the node parameter configuration interface corresponding to the target function role is displayed; in the node parameter configuration interface, in response to the parameter configuration operation, the node configuration parameters of the node to be created are determined, and the node configuration parameters are sent to the target disaster recovery system client to complete the configuration of the disaster recovery system client. The technical solution of the embodiment of the present invention solves the problem that the configuration speed is affected by the large number of configuration items of the current disaster recovery system client, and can improve the flexibility of parameter configuration and the adaptability to different function nodes and the configuration efficiency by providing parameter configuration nodes that match the node function roles.

[0077] In an optional implementation, the functional roles in the disaster recovery system node functional role list include: disaster recovery host, migration source machine, migration target machine, backup client, backup server, full server backup management software client, data copy management software client and proxy virtual machine.

[0078] In an optional implementation, when the target functional role is a disaster recovery host, the node parameter configuration interface includes: a data cache directory configuration control, a memory usage upper limit configuration control, a disk usage upper limit configuration control, and a disk remaining space threshold configuration control.

[0079] In an optional implementation, when the target functional role is a backup server, the node parameter configuration interface includes: a backup set metadata directory configuration control, a backup set metadata retention policy configuration control, a backup data cache directory configuration control, a backup data cache upper limit configuration control, and a cache disk remaining lower limit configuration control.

[0080] In an optional embodiment, the device further comprises:

[0081] The node management module is used to respond to the node management interface trigger operation and display the disaster recovery system node list page; wherein, the list items of the disaster recovery system node list page include node function roles; in response to the management operation of at least one disaster recovery system node in the disaster recovery system node list page, the management of the disaster recovery system node is completed; wherein, the management operation includes any one of new creation, deletion, batch registration, batch modification, refresh, information export and quick new creation.

[0082] In an optional implementation manner, the target functional role of the node to be created includes two or more functional roles in the disaster recovery system node functional role list.

[0083] The disaster recovery system client configuration device provided by the embodiments of the present invention can execute the disaster recovery system client configuration method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects for executing the method.

[0084] Figure 9 It is a schematic structural diagram of a computer device provided by an embodiment of the present invention. Figure 9 The block diagram of an exemplary computer device 12 suitable for implementing the embodiments of the present invention is shown. Figure 9 The displayed computer device 12 is only an example and should not bring any limitations to the functions and usage scope of the embodiments of the present invention. The computer device 12 can be any terminal device with computing capabilities, such as intelligent controllers, servers, mobile phones and other terminal devices.

[0085] Such as Figure 9 As shown, the computer device 12 is presented in the form of a general-purpose computing device. The components of the computer device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 connecting different system components (including the system memory 28 and the processing unit 16).

[0086] The bus 18 represents one or more of several types of bus structures, including a memory bus or a memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any bus structure in a variety of bus structures. For example, these architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

[0087] The computer device 12 typically includes a variety of computer system-readable media. These media can be any available media accessible by the computer device 12, including volatile and non-volatile media, removable and non-removable media.

[0088] The system memory 28 may include computer system-readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. The computer device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 34 can be used for reading and writing non-removable, non-volatile magnetic media ( Figure 9 not shown, commonly referred to as a "hard disk drive"). Although Figure 9not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., "floppy disk") and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., CD-ROM, DVD-ROM or other optical media) may be provided. In these cases, each drive may be connected to the bus 18 through one or more data medium interfaces. The system memory 28 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of the embodiments of the present invention.

[0089] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in the system memory 28. Such program modules 42 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include the implementation of a network environment. The program modules 42 generally perform the functions and / or methods in the embodiments described in the present invention.

[0090] The computer device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), and may also communicate with one or more devices that enable a user to interact with the computer device 12, and / or communicate with any device that enables the computer device 12 to communicate with one or more other computing devices (e.g., network card, modem, etc.). Such communication may be through the input / output (I / O) interface 22. Also, the computer device 12 may communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public network, such as the Internet) through the network adapter 20. As shown, the network adapter 20 communicates with other modules of the computer device 12 through the bus 18. It should be understood that although Figure 9 not shown, other hardware and / or software modules may be used in conjunction with the computer device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0091] The processing unit 16 executes various functional applications and data processing by running programs stored in the system memory 28, such as implementing the disaster recovery system client configuration method provided by the embodiments of the present invention. The method includes:

[0092] In response to a disaster recovery system node creation instruction, presenting a node creation interaction interface for the disaster recovery system; wherein, the node creation interaction interface is provided with a list of functional roles of the disaster recovery system nodes;

[0093] Create an interactive interface for nodes. In response to a selection instruction for any node function role in the list of node function roles of the disaster recovery system nodes, determine the target function role of the node to be created, and display the node parameter configuration interface corresponding to the target function role;

[0094] In the node parameter configuration interface, in response to a parameter configuration operation, determine the node configuration parameters of the node to be created, and send the node configuration parameters to the target disaster recovery system client to complete the configuration of the disaster recovery system client.

[0095] An embodiment of the present invention also provides a computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, it implements the disaster recovery system client configuration method provided in any embodiment of the present invention. The method includes:

[0096] In response to a disaster recovery system node creation instruction, display an interactive interface for creating nodes of the disaster recovery system; wherein, the interactive interface for creating nodes is provided with a list of node function roles of the disaster recovery system;

[0097] In the interactive interface for creating nodes, in response to a selection instruction for any node function role in the list of node function roles of the disaster recovery system nodes, determine the target function role of the node to be created, and display the node parameter configuration interface corresponding to the target function role;

[0098] In the node parameter configuration interface, in response to a parameter configuration operation, determine the node configuration parameters of the node to be created, and send the node configuration parameters to the target disaster recovery system client to complete the configuration of the disaster recovery system client.

[0099] The computer storage medium of the embodiment of the present invention may adopt any combination of one or more computer-readable media. The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium may be, for example, but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples (non-exhaustive list) of the computer-readable storage medium include: an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, the computer-readable storage medium may be any tangible medium that contains or stores a program, which can be used by or in combination with an instruction execution system, apparatus, or device.

[0100] A computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device.

[0101] The program code contained on a computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0102] The computer program code for performing the operations of the present invention may be written in one or more programming languages or combinations thereof. The programming languages include object-oriented programming languages such as Java, Smalltalk, Python, C++, and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, executed as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., by using an Internet service provider to connect through the Internet).

[0103] Embodiments of the present invention also provide a computer program product, including a computer program that, when executed by a processor, implements the disaster recovery system client configuration method provided in any embodiment of the present application.

[0104] In the process of implementing the computer program product, the computer program code for performing the operations of the present invention can be written in one or more programming languages or combinations thereof. The programming languages include object-oriented programming languages such as Java, Smalltalk, Python, C++, and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, executed as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network - including a local area network (LAN) or a wide area network (WAN) - or, alternatively, can be connected to an external computer (e.g., by connecting through the Internet using an Internet service provider).

[0105] Those of ordinary skill in the art should understand that the above-mentioned modules or steps of the present invention can be implemented with a general-purpose computing device. They can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Optionally, they can be implemented with program code executable by a computer device, so that they can be stored in a storage device and executed by the computing device, or they can be separately fabricated into individual integrated circuit modules, or multiple modules or steps among them can be fabricated into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0106] Note that the above is only the preferred embodiment of the present invention and the technical principles applied. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein. Various obvious changes, re-adjustments, and substitutions can be made by those skilled in the art without departing from the protection scope of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments. Without departing from the concept of the present invention, more other equivalent embodiments can be included, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A method for configuring a client of a disaster recovery system, characterized in that: include: In response to the disaster recovery system node creation instruction, display the disaster recovery system node creation interactive interface; wherein the node creation interactive interface is provided with a disaster recovery system node function role list; In the node creation interactive interface, in response to a selection instruction for any node function role in the disaster recovery system node function role list, a target function role of the node to be created is determined, and a node parameter configuration interface corresponding to the target function role is displayed; In the node parameter configuration interface, in response to the parameter configuration operation, the node configuration parameters of the node to be created are determined, and the node configuration parameters are sent to the target disaster recovery system client to complete the disaster recovery system client configuration.

2. The method according to claim 1, characterized in that The functional roles in the disaster recovery system node functional role list include: disaster recovery host, migration source machine, migration target machine, backup client, backup server, full server backup management software client, data copy management software client and proxy virtual machine.

3. The method according to claim 1 or 2, characterized in that: When the target functional role is a disaster recovery host, the node parameter configuration interface includes: Data cache directory configuration controls, memory usage upper limit configuration controls, disk usage upper limit configuration controls, and disk remaining space threshold configuration controls.

4. The method according to claim 1 or 2, characterized in that: When the target functional role is a backup server, the node parameter configuration interface includes: Backup set metadata directory configuration control, backup set metadata retention policy configuration control, backup data cache directory configuration control, backup data cache upper limit configuration control and cache disk remaining lower limit configuration control.

5. The method according to claim 1, characterized in that The method further comprises: In response to a node management interface trigger operation, a disaster recovery system node list page is displayed; wherein the list items of the disaster recovery system node list page include node function roles; In response to a management operation on at least one disaster recovery system node in the disaster recovery system node list page, the management of the disaster recovery system node is completed; wherein the management operation includes any one of new creation, deletion, batch registration, batch modification, refresh, information export and quick new creation.

6. The method according to claim 2, characterized in that The target functional role of the node to be created includes two or more functional roles in the disaster recovery system node functional role list.

7. A disaster recovery system client configuration device, characterized in that: include: A role list display module is used to display a node creation interactive interface of the disaster recovery system in response to a disaster recovery system node creation instruction; wherein the node creation interactive interface is provided with a disaster recovery system node function role list; A configuration interface display module, used to create an interactive interface at the node, determine a target function role of the node to be created in response to a selection instruction for any node function role in the disaster recovery system node function role list, and display a node parameter configuration interface corresponding to the target function role; The configuration parameter sending module is used to determine the node configuration parameters of the node to be created in response to the parameter configuration operation on the node parameter configuration interface, and send the node configuration parameters to the target disaster recovery system client to complete the disaster recovery system client configuration.

8. A computer device, characterized in that: The computer device comprises: one or more processors; A memory for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the disaster recovery system client configuration method as described in any one of claims 1-6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method for configuring a client of a disaster recovery system as described in any one of claims 1 to 6 is implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the computer program implements the method for configuring a client of a disaster recovery system as described in any one of claims 1 to 6.

Images