Data processing method, apparatus, device, and medium

By automatically mounting the target copy volume to an available mount point directory and loading it into the original data structure when a data operation task trigger command is detected, the problem of users manually mounting copy volumes is solved, simplifying the operation process and improving the user experience.

CN115168107BActive Publication Date: 2026-01-20INFORMATION2 SOFTWARE SHANGHAI
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202210876265.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-07-25
Publication Date
2026-01-20
Estimated Expiration
2042-07-25

AI Technical Summary

Technical Problem

In existing technologies, users need to manually specify and mount the copied volume to the target location of the backup server's file system, which is complex, error-prone, and degrades the user experience.

Method used

When a trigger command for a data operation task is detected, the pre-acquired target copy volume is automatically mounted to an available mount point directory, and the mount point directory is loaded into the corresponding raw data structure to execute the data operation task.

Benefits of technology

It automatically creates directories and mounts copied volumes to available mount point directories, simplifying user operations, improving user experience, and reducing the probability of errors.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115168107B_ABST
    Figure CN115168107B_ABST
Patent Text Reader

Abstract

This invention discloses a data processing method, apparatus, device, and medium. The method includes: upon detecting a trigger command for a data operation task, automatically mounting a pre-acquired target copy volume to an idle mount point directory; and loading the mount point directory into the corresponding raw data structure to execute the corresponding data operation task. This embodiment of the invention, by automatically mounting a pre-acquired target copy volume to an idle mount point directory and loading the mount point directory into the corresponding raw data structure upon detecting a trigger command for a data operation task, solves the problem of users needing to manually mount the copy volume to the backup server's file system. It achieves automatic directory creation and automatic mounting of the copy volume to an idle mount point directory, simplifying user operations, improving user experience, and reducing the probability of user errors.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a data processing method, apparatus, device, and medium. Background Technology

[0002] In existing technologies, during data backup tasks, users need to specify the target location for the backup. In most cases, the target location is a directory within the file system. If the target location is a copy volume, the user usually needs to manually specify a target location, and the copy volume will be mounted to this target location under the backup server's file system. After successful mounting, the mount point directory is then entered into the task settings.

[0003] In reality, users often don't care what the mount point directory actually is. As long as the data can be correctly backed up to the replicated volume and restored correctly, the simpler the operation, the better. Currently, the existing operations of mounting the replicated volume, recording the mount point directory, and entering the mount point directory into the data backup task settings are often performed manually by the user. This not only reduces the user experience but also increases the probability of user errors. Summary of the Invention

[0004] This invention provides a data processing method, apparatus, device, and medium to automatically create directories and automatically mount copied volumes to available mount point directories, simplifying user operations, improving user experience, and reducing the probability of user errors.

[0005] According to one aspect of the present invention, a data processing method is provided, the method comprising:

[0006] When a trigger command for a data operation task is detected, the pre-acquired target copy volume is automatically mounted to an available mount point directory.

[0007] The mount point directory is loaded into the corresponding raw data structure to execute the corresponding data operation task.

[0008] According to another aspect of the present invention, a data processing apparatus is provided, the apparatus comprising:

[0009] The mount module is used to automatically mount the pre-acquired target copy volume to an available mount point directory when a trigger command for a data operation task is detected.

[0010] The loading execution module is used to load the mount point directory into the corresponding raw data structure to execute the corresponding data operation tasks.

[0011] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0012] At least one processor; and

[0013] A memory communicatively connected to the at least one processor; wherein,

[0014] The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the data processing method according to any embodiment of the present invention.

[0015] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the data processing method described in any embodiment of the present invention.

[0016] The technical solution of this invention automatically mounts the pre-acquired target copy volume to an idle mount point directory when a trigger command for a data operation task is detected, and loads the mount point directory into the corresponding original data structure to execute the corresponding data operation task. This solves the problem that users need to manually mount the copy volume to the backup server's file system, realizes the automatic creation of directories and automatic mounting of the copy volume to an idle mount point directory, simplifies user operations, improves user experience, and reduces the probability of user errors.

[0017] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 A flowchart of a data processing method is provided in one embodiment of the present invention;

[0020] Figure 2 A flowchart illustrating a data processing method provided in an embodiment of the present invention;

[0021] Figure 3 A flowchart illustrating another data processing method provided in an embodiment of the present invention;

[0022] Figure 4 A flowchart illustrating another data processing method provided in an embodiment of the present invention.

[0023] Figure 5 This is a schematic diagram of the structure of a data processing device according to an embodiment of the present invention;

[0024] Figure 6 A schematic diagram of an electronic device that can be used to implement embodiments of the present invention is shown. Detailed Implementation

[0025] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0026] It should be noted that the terms "first," "second," "target," etc., used in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0027] In one embodiment, Figure 1 This invention provides a flowchart of a data processing method according to an embodiment of the present invention. This embodiment is applicable to situations involving data processing. The method can be executed by a data processing device, which can be implemented in hardware and / or software and can be configured in an electronic device. Figure 1 As shown, the method includes:

[0028] S110. When a trigger command for a data operation task is detected, the pre-acquired target copy volume is automatically mounted to an available mount point directory.

[0029] In this context, data manipulation tasks can be understood as data backup, data recovery, and other related data operation tasks. The target copy volume can be understood as a pre-acquired and configured target storage space. Automatic mounting can be understood as automatically assigning a drive letter to a pre-configured disk partition. Mounting can be understood as attaching a pre-assigned target copy volume to an existing mount point directory, allowing access to the target copy volume through this mount point directory. Of course, disk partitioning also includes partitioning virtual disks, which can be understood as creating a directory and then using `MOUNT` and the corresponding format parameters to mount the hard drive or partition to a pre-created mount point directory. The mount point directory can be understood as the entry directory of the disk file system in Linux, similar to drive letters like C:, D:, E:, etc., used to access different partitions in Windows. The created directory can be understood as the mount point directory.

[0030] In this embodiment, upon detecting a trigger command for a data operation task, the pre-acquired target copy volume can be automatically mounted to an available mount point directory based on the trigger command for different data operation tasks, such as a data backup task. It should be noted that the pre-acquired target copy volume can be generated based on the preset storage space in the received relevant copy volume creation command, or it can be obtained by receiving copy volume information sent by a web server; this embodiment does not impose any limitations. It should be understood that automatically mounting the target copy volume to an available mount point directory can be understood as automatically specifying an available mount point directory; if the directory does not exist, it is created, and then the pre-acquired target copy volume is automatically mounted to this specified available mount point directory.

[0031] In this embodiment, before performing the mounting action, a unique mount point directory can be automatically generated according to the relevant algorithm and the directory can be created. This ensures that the mount point directory is idle.

[0032] In one embodiment, the data operation task includes one of the following: a data backup task; a data recovery task.

[0033] Data backup is the foundation of disaster recovery. It involves copying all or part of the data set from the application host's hard drive or array to other storage media to prevent data loss due to operational errors or system failures. Data recovery can be understood as the process of retrieving data and restoring information when computer storage media is damaged, resulting in the inaccessibility of some or all data. Data recovery can not only recover lost files but also repair physically damaged disk data.

[0034] In this embodiment, data manipulation tasks may include data backup tasks and / or data recovery tasks. Exemplarily, data manipulation tasks can be applied to tasks in different scenarios. For example, in a hospital scenario, a data backup task may be a registration data backup task; in a community image acquisition scenario, a data backup task may be an image data backup task; and in a teaching scenario, a data backup task may be an audio data backup task. This embodiment does not impose any limitations. A data recovery task may be a task for recovering image data or a task for recovering data documents. This embodiment does not impose any limitations.

[0035] In this embodiment, when any trigger command of a data backup task and / or data recovery task is detected, the pre-acquired target copy volume can be automatically mounted to an idle mount point directory according to the trigger command corresponding to the data backup task and / or data recovery task.

[0036] It should be noted that when the trigger command for data backup task and data recovery task is detected, the order in which the data backup task and data recovery task are executed is not important. The data backup task can be executed first and then the data recovery task, or the data recovery task can be executed first and then the data backup task, or the data recovery task and data backup task can be executed simultaneously.

[0037] In one embodiment, the method for determining the target replication volume includes: automatically generating a corresponding target replication volume based on a received replication volume creation instruction; or receiving a target replication volume sent by a web server.

[0038] The copy volume creation command can be understood as the command used to create storage space. A web server, also known as a website server, can be understood as a program residing on a certain type of computer on the Internet. It can handle requests from web clients such as browsers and return corresponding responses; it can also store website files for browsing; and it can store data files for downloading.

[0039] In this embodiment, the web server can provide several web pages, and users can manage the entire data backup system according to these pages, which may include managing the computer nodes in the data backup system.

[0040] In this embodiment, the determination of the target replication volume can include two methods: First, the target replication volume can be automatically generated based on the relevant instructions received during replication volume creation; second, the target replication volume can be obtained by receiving replication volume information sent by the web server. Specifically, the target replication volume can be generated based on the relevant storage capacity carried in the replication volume creation instruction, or all replication volumes mounted on the corresponding backup node can be displayed through the web server's display interface, and free replication volumes can be identified from all replication volumes based on user operations, and the identified free replication volumes can be used as the target replication volume.

[0041] In this embodiment, after determining the target copy volume, the target copy volume can be automatically mounted to an idle mount point directory based on the detected data operation tasks, such as data backup or data recovery tasks. The mount point directory is then loaded into the corresponding original data structure to execute the corresponding data operation tasks.

[0042] In one embodiment, automatically generating a corresponding target replicated volume based on a received replicated volume creation instruction includes:

[0043] Identify and extract the preset storage capacity carried in the received copy volume creation instruction; extract the second storage space corresponding to the preset storage capacity from the first storage space; wherein the storage capacity of the second storage space is less than or equal to the storage capacity of the first storage space;

[0044] Generate the corresponding target copy volume based on the second storage space.

[0045] The preset storage capacity can be understood as the storage capacity of the target replicated volume to be generated. This preset storage capacity includes parameters such as the storage server address and volume space. The first storage space can be understood as the total storage space available for creating the replicated volume, which is also the total space of the storage pool. The second storage space can be understood as the storage space corresponding to the preset storage capacity, which is the allocated space for the target replicated volume. It is known that both the first and second storage spaces have corresponding storage capacities, and the storage capacity of the second storage space is less than or equal to the storage capacity of the first storage space.

[0046] In this embodiment, the pre-set storage capacity carried in the received copy volume creation instruction can be extracted through identification and extraction. A second storage space corresponding to the pre-set storage capacity is then extracted from the first storage space, and a corresponding target copy volume is generated based on the extracted second storage space. It should be noted that the scheme of creating the target copy volume through the copy volume creation instruction can be implemented by a data backup node.

[0047] In one embodiment, the process of determining the target replication volume via a web server includes:

[0048] When the web server detects a target storage location selection instruction corresponding to a data operation task, it displays all the replicated volumes mounted on the corresponding backup node through the web server's display interface.

[0049] In response to the user's selection, identify a free copy volume from all copy volumes to be used as the target copy volume.

[0050] The target storage location can be understood as the storage location corresponding to the data backup and data recovery tasks in the data operation tasks. An idle replication volume can be understood as an unused replication volume.

[0051] In this embodiment, when the web server detects a target storage location selection instruction corresponding to a data operation task, it can display all the replica volumes mounted on the corresponding backup node through the web server's interface. Based on the user's selection, a free replica volume can be identified from all the replica volumes and used as the target replica volume. It should be noted that the scheme of creating the target replica volume through a replica volume creation instruction can be implemented through a web server.

[0052] It should be noted that there is no uniform principle for users to select the copy volume; they can choose according to their needs. For example, a hospital could choose to create a "Registration Data Backup" task to back up all registration data to the first copy volume, and then create an "Imaging Data Backup" task to back up all imaging data to the second copy volume; alternatively, it could choose to create a "Daily Data Backup" task to back up the day's data to copy volume 1, and then use a "Historical Data Backup" task to back up historical data to copy volume 2, and so on. This embodiment does not impose any limitations. Of course, each copy task will include a target copy volume field, which needs to specify a copy volume. Users can create different copy volume data operation tasks as needed, and different copy volume data operations have corresponding target copy volumes, which can be the same copy volume or different copy volumes.

[0053] S120. Load the mount point directory into the corresponding raw data structure to execute the corresponding data operation task.

[0054] The original data structure can be understood as a set of data elements that have one or more relationships with each other, and the relationships between the data elements in the set. In other words, it studies the logical structure, storage structure and operation of data, and can be used to reflect the internal composition of a data.

[0055] In this embodiment, the mount point directory can be loaded into the corresponding original data structure to execute the corresponding data backup and / or data recovery tasks. It should be noted that each data backup / recovery task's data structure contains a data item for the mount point directory.

[0056] In this embodiment, when a trigger command for a data operation task is detected, the corresponding data operation task is executed. For example, when a trigger command for a data backup task is detected, the data backup task is executed. The backup target node can automatically convert the vendor name, the unique identifier of the replicated volume, and the replicated volume name into a mount point directory according to a pre-set conversion method, such as $WORK_DIR / mnt_volumes / $VOLUME_UUID. Then, the obtained mount point directory is filled into the original "mount point directory" data structure of the data backup task, and then the data backup task is executed according to the corresponding process.

[0057] It's important to note that during a data recovery task within a data operation task, the web server interface will list all replicated volumes mounted on the backup node. Users can then select one of these volumes as the data source for the data recovery task based on their needs and the data content stored on the replicated volume. Correspondingly, when executing the data recovery task, the backup node will convert the vendor name, replicated volume identifier, and replicated volume name into a mount point directory according to a pre-set conversion method, filling this information into the corresponding original data structure. Then, the data recovery task will be executed according to the appropriate process. Of course, since the replicated volume has been migrated to a new backup node, even if the original backup node fails, the new backup node can still generate a mount point directory according to the pre-set conversion method. This new mount point directory does not need to be the same as the original node's mount point directory. The new mount point directory will then be set in the task settings for both the data backup and data recovery tasks, and the data backup and data recovery tasks will be executed according to the appropriate process.

[0058] The technical solution of this invention automatically mounts the pre-acquired target copy volume to an idle mount point directory when a trigger command for a data operation task is detected, and loads the mount point directory into the corresponding original data structure to execute the corresponding data operation task. This solves the problem that users need to manually mount the copy volume to the backup server's file system, realizes the automatic creation of directories and automatic mounting of the copy volume to an idle mount point directory, simplifies user operations, improves user experience, and reduces the probability of user errors.

[0059] In one embodiment, Figure 2This is a flowchart of a data processing method provided in one embodiment of the present invention. This embodiment further refines the above embodiments. It should be noted that since the automatically created mount point directory and the mount point directory used when the trigger command for the data operation task is detected can be the same node or different nodes, the execution order of S210 and S230 can be adjusted according to whether they are on the same node. This embodiment takes the case where the automatically created mount point directory and the mount point directory used when the trigger command for the data operation task is detected are the same node, i.e., S210 is executed first and then S230 is executed, as an example.

[0060] It should be noted that this embodiment describes the case where the pre-obtained mount point directory does not exist.

[0061] like Figure 2 As shown, the method includes:

[0062] S210. Upon receiving a copy volume creation instruction from the Web server, automatically create a mount point directory according to a preset conversion method.

[0063] In this embodiment, the preset conversion method can be understood as a pre-set conversion method that automatically creates mount point directories. For example, the preset conversion method could be ` / var / $vendor_name / volumes / $replicated_volume_ID`. Here, the "$" symbol represents a specific string. For instance, assuming the vendor name is EMC or Huawei, the replicated volume name is `VOLUME1`, and its corresponding replicated volume identifier is a UUID, and the replicated volume name is `VOLUME2`, the preset conversion method could be represented as ` / var / EMC / volumes / VOLUME1_UUID`, ` / var / Huawei / volumes / VOLUME2_UUID`, etc. Strictly speaking, the last part of the path is the replicated volume identifier, not the replicated volume name.

[0064] In this embodiment, upon receiving a copy volume creation instruction from the web server, a mount point directory can be automatically created according to a pre-set conversion method. Specifically, the system can obtain its own vendor name, copy volume identifier, and copy volume name, etc., and combine these information according to a pre-set conversion method to obtain the corresponding mount point directory.

[0065] It should be noted that when the automatically created mount point directory and the mount point directory used when the trigger command for the data operation task is detected are the same node, the execution order of S230 must be after the execution of S210; when the automatically created mount point directory and the mount point directory used when the trigger command for the data operation task is detected are not the same node, the execution order of S230 and S210 is not important, S230 can be executed first and then S210, or S210 can be executed first and then S230, or S230 and S210 can be executed simultaneously.

[0066] In one embodiment, automatically creating a mount point directory according to a preset conversion method includes:

[0067] Obtain the vendor name to which you belong, as well as the copy volume identifier and copy volume name in the copy volume creation command;

[0068] The manufacturer name, replicated volume identifier, and replicated volume name are combined according to the preset conversion method to obtain the corresponding mount point directory.

[0069] Here, "vendor name" can be understood as the name of the manufacturer; for example, the vendor name could be EMC, Huawei, Apple, etc. "Replicated volume identifier" can also be called the replicated volume ID. It should be noted that the replicated volume identifier is a unique identifier for the replicated volume. For example, the replicated volume identifier can be represented as VOLUME1_UUID or VOLUME2_UUID; this embodiment does not impose any limitations. "Replicated volume name" can be understood as the name corresponding to the replicated volume.

[0070] In this embodiment, the system can obtain its own vendor name, as well as the copy volume identifier and copy volume name from the copy volume creation instruction. The vendor name, copy volume identifier, and copy volume name are then combined according to a pre-set conversion method to obtain the corresponding mount point directory. It should be noted that since the elements that combine to form the mount point directory are unique—that is, the copy volume identifier is the unique identifier of the copy volume—the resulting mount point directory is also unique.

[0071] S220. When a trigger command for a data operation task is detected, the pre-acquired target copy volume is automatically mounted to an available mount point directory.

[0072] S230. Load the mount point directory into the corresponding raw data structure to execute the corresponding data operation task.

[0073] The technical solution described in this embodiment of the invention automatically mounts the pre-acquired target copy volume to an idle mount point directory when a trigger command for a data operation task is detected; the mount point directory is then loaded into the corresponding original data structure to execute the corresponding data operation task. Upon receiving a copy volume creation command from the web server, the mount point directory is automatically created according to a preset conversion method, further realizing automatic directory creation and automatic mounting of the copy volume to an idle mount point directory. This simplifies user operations, improves user experience, and reduces the probability of user errors.

[0074] Of course, if the pre-configured or assembled mount point directory already exists, the mount operation can be performed directly, that is, the target copy volume is mounted to the available mount point directory. The mount operation can be performed once or multiple times; this embodiment does not impose any restrictions. However, the mount point directory creation operation is performed only once.

[0075] In one embodiment, Figure 3 This is a flowchart illustrating another data processing method provided in an embodiment of the present invention. This embodiment can be considered a preferred embodiment to further illustrate a data processing method. This embodiment can be applied to scenarios involving data backup and data recovery, performing automatic mounting and the entire usage process. Figure 3 As shown, the console is the web server in the above embodiment. The specific steps of a data processing method can be as follows:

[0076] S310. Based on the data operation task, list all the replicated volumes mounted on this node for the user to select.

[0077] The data operation tasks include data backup tasks and data recovery tasks. On the console interface, when a user selects the target replication volume for a data backup task, all replication volumes mounted on that node are listed for the user to choose from.

[0078] S320: The console sends the command to mount the replicated volume to the node. The node automatically creates a directory using a preset conversion method and uses it to mount the replicated volume.

[0079] In this embodiment, on the existing console interface, when a user creates a replicated volume, the "mount point" can only be selected from a directory tree on the node. In this embodiment, an "automatic" option is added. If the user selects "automatic," the console will send the instruction to create the replicated volume to the node, and the node will automatically create a directory using a preset conversion method and use it to mount the replicated volume.

[0080] S330. When executing a data backup task, the volume name to be copied is converted into a mount point directory according to a preset conversion method, and the mount point directory is filled into the data structure corresponding to the data backup task to execute the corresponding data operation task.

[0081] The replicated volume name includes the vendor name, replicated volume identifier, and replicated volume name. In this embodiment, when the data backup task is executed, the backup target node will automatically combine the vendor name, replicated volume identifier, and replicated volume name according to a preset conversion method, such as $WORK_DIR / mnt_volumes / $VOLUME_UUID, and convert it into a mount point directory. This directory is then filled into the existing "mount point directory" data structure of the data backup task, which can also be called the corresponding original data structure. After that, the data backup task can be executed according to the existing process.

[0082] S340. When executing a data recovery task, the control machine interface lists all the replicated volumes mounted on the backup node. The user selects one of them as the source replicated volume, converts it into a mount point directory according to a preset conversion method, and stores it in the corresponding data structure to execute the corresponding data recovery task.

[0083] In this embodiment, when restoring data, the control interface will also list all volumes mounted on the backup node, and the user can select one of them as the data source for the restoration task. Correspondingly, when the backup node executes the restoration task, it will combine the vendor name, replicated volume identifier, and replicated volume name according to a preset conversion method, and convert them into a mount point directory, filling in the existing data structure, which can also be called the corresponding original data structure. Then, the data restoration task can be executed according to the existing process.

[0084] It should be noted that even if the backup node fails and the replicated volume is migrated to a new backup node, the new node can still generate a mount point directory according to a preset conversion method. This new directory does not need to be the same as the original node's mount point directory. The new directory is then set in the data backup and data recovery task settings, and the data backup and data recovery tasks are executed according to the existing process. This embodiment of the invention, by converting the volume name and mount point directory within the node logic, solves the problem of users needing to manually mount the replicated volume to the backup server's file system. It automatically creates the directory and automatically mounts the replicated volume to an available mount point directory, simplifying user operations, improving user experience, and reducing the probability of user errors.

[0085] It should be noted that the execution order of S330 and S340 is not important. S330 can be executed first and then S340; or S340 can be executed first and then S330; or S330 and S340 can be executed simultaneously.

[0086] In one embodiment, Figure 4 This is a flowchart illustrating another data processing method provided in an embodiment of the present invention, wherein the control unit is represented by a web server, such as... Figure 4 As shown, the controller specifies the volume name to be copied, generates a mount point directory according to the preset conversion method, and loads the mount point directory into the corresponding original data structure to execute the corresponding data operation task.

[0087] In one embodiment, Figure 5 This is a schematic diagram of a data processing apparatus according to an embodiment of the present invention. This apparatus is suitable for processing data and can be implemented in hardware or software. It can be configured in an electronic device to implement a data processing method according to an embodiment of the present invention. Figure 5 As shown, the device includes: a mounting module 510 and a loading execution module 520. (As indicated...) Figure 5 As shown, the device includes:

[0088] Mounting module 510 is used to automatically mount the pre-acquired target copy volume to an idle mount point directory when a trigger command for a data operation task is detected.

[0089] The loading execution module 520 is used to load the mount point directory into the corresponding original data structure to execute the corresponding data operation task.

[0090] In one embodiment, the data processing apparatus further includes:

[0091] The directory creation module is used to automatically create mount point directories according to a preset conversion method when a copy volume creation instruction is received from the web server.

[0092] In one embodiment, the directory creation module includes:

[0093] The information acquisition unit is used to acquire its own vendor name, as well as the copy volume identifier and copy volume name in the copy volume creation instruction when it receives the copy volume creation instruction sent by the Web server.

[0094] The directory acquisition unit is used to combine the vendor name, the replicated volume identifier, and the replicated volume name according to a preset conversion method to obtain the corresponding mount point directory.

[0095] The method for determining the target copy volume includes:

[0096] The corresponding target copy volume is automatically generated based on the received copy volume creation command;

[0097] Alternatively, it can receive the target replicated volume sent by the web server.

[0098] In one embodiment, automatically generating the corresponding target replicated volume according to the received replicated volume creation instruction includes:

[0099] Identify and extract the preset storage capacity carried in the received copy volume creation instruction;

[0100] Extract the second storage space corresponding to the preset storage capacity from the first storage space; wherein the storage capacity of the second storage space is less than or equal to the storage capacity of the first storage space;

[0101] Generate the corresponding target copy volume based on the second storage space.

[0102] In one embodiment, the process of determining the target replication volume via the web server includes:

[0103] When the web server detects a target storage location selection instruction corresponding to a data operation task, it displays all the replicated volumes mounted on the corresponding backup node through the web server's display interface.

[0104] In response to a user selection, an idle copy volume is identified from all the copy volumes to be used as the target copy volume.

[0105] In one embodiment, the data operation task includes one of the following: a data backup task; a data recovery task.

[0106] The data processing apparatus provided in the embodiments of the present invention can execute the data processing method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of executing the method.

[0107] In one embodiment, Figure 6 A schematic diagram of an electronic device that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0108] like Figure 6As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0109] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0110] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as data processing methods.

[0111] In some embodiments, the data processing method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or mounted on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the data processing method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the data processing method by any other suitable means (e.g., by means of firmware).

[0112] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0113] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0114] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0115] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0116] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0117] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0118] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0119] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A data processing method, characterized in that, include: When a trigger command for a data operation task is detected, the pre-acquired target copy volume is automatically mounted to an available mount point directory. The mount point directory is loaded into the corresponding raw data structure to execute the corresponding data operation task; The target copy volume is the target storage space that has been pre-acquired and configured; The method for determining the target copy volume includes: The corresponding target copy volume is automatically generated based on the received copy volume creation command; The step of automatically generating the corresponding target copy volume based on the received copy volume creation instruction includes: Identify and extract the preset storage capacity carried in the received copy volume creation instruction; Extract the second storage space corresponding to the preset storage capacity from the first storage space; wherein the storage capacity of the second storage space is less than or equal to the storage capacity of the first storage space; Generate the corresponding target copy volume based on the second storage space.

2. The method according to claim 1, characterized in that, The method further includes: Upon receiving a copy volume creation command from the web server, the mount point directory is automatically created according to the preset conversion method.

3. The method according to claim 2, characterized in that, The automatic creation of mount point directories according to a preset conversion method includes: Obtain the vendor name to which it belongs, as well as the copy volume identifier and copy volume name in the copy volume creation instruction; The manufacturer name, the replicated volume identifier, and the replicated volume name are combined according to a preset conversion method to obtain the corresponding mount point directory.

4. The method according to claim 1 or 2, characterized in that, The method for determining the target copy volume includes: Receive the target copy volume sent by the web server.

5. The method according to claim 4, characterized in that, The process of determining the target replication volume through the web server includes: When the web server detects a target storage location selection instruction corresponding to a data operation task, it displays all the replicated volumes mounted on the corresponding backup node through the web server's display interface. In response to a user selection, an idle copy volume is identified from all the copy volumes to be used as the target copy volume.

6. The method according to claim 1, characterized in that, The data operation tasks include one of the following: data backup task; data recovery task.

7. A data processing apparatus, characterized in that, include: The mount module is used to automatically mount the pre-acquired target copy volume to an available mount point directory when a trigger command for a data operation task is detected. The loading execution module is used to load the mount point directory into the corresponding raw data structure to execute the corresponding data operation tasks; The target copy volume is the target storage space that has been pre-acquired and configured; The method for determining the target copy volume includes: The corresponding target copy volume is automatically generated based on the received copy volume creation command; The step of automatically generating the corresponding target copy volume based on the received copy volume creation instruction includes: Identify and extract the preset storage capacity carried in the received copy volume creation instruction; Extract the second storage space corresponding to the preset storage capacity from the first storage space; wherein the storage capacity of the second storage space is less than or equal to the storage capacity of the first storage space; Generate the corresponding target copy volume based on the second storage space.

8. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the data processing method according to any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the data processing method according to any one of claims 1-6.