Cloud-side collaborative remote backup management method and device

Abstract

The invention provides a cloud edge collaborative remote backup management method and device, which is applied to a cloud edge collaborative scene comprising a central cloud and at least one edge cloud, and comprises the following steps: issuing a deployment instruction of a backup program and a product resource to a target edge cloud node, triggering the target edge cloud node to complete warehouse storage and mirror image preparation of the backup program; according to the backup configuration parameter, generating a corresponding deployment task and sending the deployment task to the target edge cloud node to indicate the target edge cloud node to complete parameterized deployment and starting of the backup program in a corresponding edge cluster; and according to a preset return strategy, initiating a backup result acquisition request to the target edge cloud node so as to receive and store a backup result file periodically generated by the backup program. According to the scheme, unified deployment, parameterized configuration and automatic result return of the edge backup by the center cloud are realized through a productization and automation process; the problems that manual operation is low in efficiency and prone to errors are solved, and backup management efficiency and consistency are improved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a remote backup management method and apparatus for cloud-edge collaboration. Background Technology

[0002] With the deep integration of edge computing and IoT technologies, data processing and analysis tasks are being massively moved to edge cloud nodes closer to data sources, leading to a dramatic increase in the volume of data generated and accumulated at the edge. To ensure the security and traceability of this critical business data distributed across wide-area edge environments, regular and reliable backups have become a fundamental and necessary technical requirement.

[0003] Current edge cloud backup management uses a manual deployment model, meaning that edge-side backup programs mostly rely on manual installation or local configuration. However, this manual configuration method has significant shortcomings: it is inefficient and difficult to scale when dealing with a large number of nodes; manual configuration is prone to errors, leading to inconsistent strategies; the overall process depends on manual intervention, lacks automated linkage, has high operation and maintenance costs, and cannot achieve centralized management and status tracking. Summary of the Invention

[0004] This application provides a cloud-edge collaborative remote backup management method and device, which realizes unified deployment, parameterized configuration and automatic result feedback of edge backup from the central cloud through artifactization and automation process, solves the problems of low efficiency and easy error in manual operation, and improves backup management efficiency and consistency.

[0005] In a first aspect, embodiments of this application provide a remote backup management method for cloud-edge collaboration, applied in a cloud-edge collaboration scenario comprising a central cloud and at least one edge cloud, wherein the method is executed by a central cloud node, and the method includes:

[0006] Deployment instructions and artifact resources for the backup program are sent to the target edge cloud node to trigger the target edge cloud node to complete the repository storage and image preparation of the backup program;

[0007] Based on the backup configuration parameters configured by the user, a corresponding deployment task is generated and sent to the target edge cloud node to instruct the target edge cloud node to complete the parameterized deployment and startup of the backup program in the corresponding edge cluster.

[0008] According to the preset backhaul strategy, a backup result retrieval request is initiated to the target edge cloud node to receive and store the backup result files periodically generated by the backup program.

[0009] Secondly, embodiments of this application also provide a remote backup management device for cloud-edge collaboration, applied in a cloud-edge collaboration scenario comprising a central cloud and at least one edge cloud. The device is executed by a central cloud node and includes:

[0010] The backup program distribution module is used to distribute deployment instructions and artifact resources of the backup program to the target edge cloud node, so as to trigger the target edge cloud node to complete the warehouse storage and image preparation of the backup program.

[0011] The deployment task sending module is used to generate a corresponding deployment task based on the backup configuration parameters configured by the user and send it to the target edge cloud node, so as to instruct the target edge cloud node to complete the parameterized deployment and startup of the backup program in the corresponding edge cluster.

[0012] The backup result receiving module is used to initiate a backup result retrieval request to the target edge cloud node according to a preset backhaul strategy, so as to receive and store the backup result files periodically generated by the backup program.

[0013] Thirdly, embodiments of this application also provide an electronic device, which includes:

[0014] One or more processors;

[0015] Storage device for storing one or more programs.

[0016] When one or more programs are executed by one or more processors, the one or more processors implement a cloud-edge collaborative remote backup management method as described in any of the embodiments of this application.

[0017] Fourthly, embodiments of this application also provide a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform a cloud-edge collaborative remote backup management method as described in any of the embodiments of this application.

[0018] This application provides a cloud-edge collaborative remote backup management method, applied in a cloud-edge collaborative scenario comprising a central cloud and at least one edge cloud. The method is executed by a central cloud node and includes: issuing deployment instructions and artifact resources for a backup program to a target edge cloud node to trigger the target edge cloud node to complete the repository storage and image preparation of the backup program; generating a corresponding deployment task according to user-configured backup configuration parameters and sending it to the target edge cloud node to instruct the target edge cloud node to complete the parameterized deployment and startup of the backup program in the corresponding edge cluster; and initiating a backup result retrieval request to the target edge cloud node according to a preset return strategy to receive and store the backup result files periodically generated by the backup program. The technical solution of this application, by artifactizing the backup program and automatically generating deployment tasks in combination with user-configured parameters, realizes one-click, standardized distribution and parameterized deployment of the backup program from the central cloud to the edge cloud, effectively solving the problems of low deployment efficiency and easy configuration errors in the traditional manual mode. At the same time, by automatically triggering the acquisition and integrity verification of backup results through preset return strategies, it realizes the fully automated closed-loop management from edge backup execution to central result collection, significantly improving the management efficiency, policy consistency and operation and maintenance automation level of massive edge node backup tasks, and reducing the cost of manual intervention and operational risks. Attached Figure Description

[0019] To more clearly illustrate the technical solutions of the exemplary embodiments of this application, the accompanying drawings used in describing the embodiments are briefly introduced below. Obviously, the accompanying drawings described are only a portion of the embodiments to be described in this application, and not all of them. For those skilled in the art, other drawings can be obtained from these drawings without any creative effort.

[0020] Figure 1 A flowchart illustrating a cloud-edge collaborative remote backup management method provided in an embodiment of this application;

[0021] Figure 2 A flowchart illustrating yet another cloud-edge collaborative remote backup management method provided in this application embodiment;

[0022] Figure 3 This is a schematic diagram of the system architecture of the remote backup management method involved in this embodiment;

[0023] Figure 4 A schematic diagram of a cloud-edge collaborative remote backup management device provided in an embodiment of this application;

[0024] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0025] The present application will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the application and not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present application, not the entire structure.

[0026] Before introducing the technical solution provided in this application embodiment, the application scenario of the solution can be described first. This embodiment is applicable to scenarios requiring unified and automated backup management of large-scale distributed edge cloud data in various cloud-edge collaboration scenarios. Currently, deployment methods relying on manual distribution of packages and manual modification of configurations are widely used in program distribution to edge environments, but traditional methods have obvious limitations. In practical applications, due to the large number of edge cloud nodes, their geographically dispersed nature, and the complex network environment, and because backup management needs to take into account multiple aspects such as program deployment, configuration distribution, task scheduling, and result feedback, traditional manual management modes are difficult to achieve large-scale and standardized operations, easily leading to problems such as low deployment efficiency, inconsistent configurations, high operation and maintenance costs, and uncontrollable result recovery. Therefore, there is an urgent need for a backup method that can achieve unified control on the central side, automated execution on the edge side, and closed-loop process management to improve the overall efficiency, reliability, and consistency of backup management. This embodiment uses a central cloud node as a unified control hub. Based on the completion of artifact packaging and parameterized configuration, it achieves centralized and standardized backup task management for massive edge cloud nodes through command-based issuance, automated deployment, and policy-based feedback. This ensures a high degree of automation and controllability in the backup process, effectively improving the reliability, scalability, and operational efficiency of data backup in a cloud-edge collaborative environment.

[0027] Example 1

[0028] Figure 1 This is a flowchart illustrating a cloud-edge collaborative remote backup management method provided in an embodiment of this application. This embodiment is applicable to various cloud-edge collaborative scenarios that require unified and automated backup management of large-scale distributed edge cloud data. The method can be executed by a cloud-edge collaborative remote backup management device, which can be implemented in the form of software and / or hardware. The hardware can be a controller, such as a mobile terminal, PC, or server.

[0029] The remote backup management method provided in this embodiment is applied to a cloud-edge collaborative scenario consisting of a central cloud and at least one edge cloud. The method is executed by the central cloud node. A cloud-edge collaborative scenario refers to a distributed computing architecture model, which includes a central cloud serving as a centralized control and core computing hub, and one or more geographically dispersed edge clouds located closer to the data source or business site. The two are connected via a network and coordinate resource, task, and data operations according to a unified strategy. The central cloud focuses on global management, task scheduling, and data aggregation, while the edge cloud focuses on localized, real-time data processing and backup execution, together forming a logically unified, physically distributed collaborative backup management system. This can be understood as follows: the entire remote backup management process operates from the perspective of the central cloud. The central cloud node acts as the sole active scheduler and controller, implementing centralized management of its subordinate edge cloud nodes. All critical logic is completed sequentially by the software entities within the central cloud node. The edge cloud nodes passively receive instructions from the central cloud and execute corresponding actions locally, without deciding when to start backup, how to configure it, or how to handle the results. Therefore, the entire cloud-edge collaborative backup system uses the central cloud as the unified brain and the edge cloud as the controlled end, forming a one-way governance model of central command and edge response.

[0030] Before implementing this solution, the following steps may be included: in response to a product listing request, determine the product resources to be listed; store the product resources to be listed in the central cloud product warehouse for unified management.

[0031] Among them, the product listing request refers to the operation command submitted by the central cloud user to the system through the management interface, which aims to formally include product resources into the central cloud product warehouse for unified management and version control.

[0032] Among them, artifact resources refer to standardized software packages that are pre-made and packaged for backup management functions and are available for distribution and deployment. Specifically, these include container image files that integrate backup programs and HTTP service programs, as well as parameterized chart packages that define how the container image is started and configured in the edge cluster. These resources are the basic entities for realizing the automated deployment and operation of backup programs in cloud-edge collaborative scenarios. Specifically, the container image of the backup program and HTTP service program refers to a single deployable software unit that conforms to containerization standards, which packages and encapsulates the backup program that executes data backup logic and the HTTP service program that provides file access services, along with the operating system environment, dependency libraries, and configuration files required for its operation. This image can be started directly in the container runtime environment of the edge cloud, enabling the backup program and the HTTP service that provides result file indexing and download functions to work together as a whole. A Chart package containing container image startup parameter definitions is a template file package used to describe and configure how to deploy and run the aforementioned container images in an edge cluster. It explicitly defines the various parameters required when the container starts, such as resource limits, environment variables, service ports, and storage volume mounts, enabling the container images to be deployed in a parameterized, repeatable, and automated manner according to specific backup task requirements.

[0033] like Figure 1 As shown, the cloud-edge collaborative remote backup management method provided in this embodiment of the invention includes the following steps:

[0034] S110: Issue deployment instructions and artifact resources for the backup program to the target edge cloud node to trigger the target edge cloud node to complete the repository storage and image preparation of the backup program.

[0035] In this context, the target edge cloud node refers to a computing service entity within a specific edge cloud, designated by the user in the central cloud management interface as the destination for the deployment and execution of the backup program during the backup management operation initiated by the central cloud. It represents the specific recipient and execution environment of the central cloud management instructions and backup tasks. The backup program is a software module pre-installed in a container image that automatically performs tasks such as data collection, compression, and log file generation on the edge cloud side according to the user-configured backup cycle and path. It is the core logical unit for realizing the local backup function of edge data.

[0036] The deployment command refers to the control command generated by the central cloud node and sent to the target edge cloud node to instruct it to perform specific operations to obtain and prepare backup program artifact resources. The command includes specific instructions for pulling artifact resources from the central cloud artifact repository and preliminary operational requirements for subsequent storage in the edge local repository.

[0037] Repository storage and image preparation refer to two related operations performed by the target edge cloud node after receiving instructions from the central cloud node. Repository storage refers to pulling and persistently saving the artifact resources of the backup program to the local artifact repository of the edge cloud to establish a localized resource copy; while image preparation specifically refers to ensuring, based on the above repository storage, that the container image has completed the necessary loading or caching in the container runtime environment of the edge cloud, so that it is in a ready state that can be directly called by subsequent deployment tasks.

[0038] Specifically, the central cloud node pushes the artifact resources consisting of the container image and its chart package, which carry backup capabilities, along with deployment instructions that clearly indicate how to pull and where to store them, to the selected target edge cloud node. This push action itself does not directly complete the backup, but serves as a start signal, enabling the target edge cloud node to automatically create or update its own artifact repository copy according to the instructions, and load the container image into the local image repository. This completes all material readiness checks before operation, laying the environmental foundation for subsequent parameterized deployment and the start of the backup process.

[0039] In this embodiment, optionally, the specific steps for issuing deployment instructions for backup programs and artifact resources to the target edge cloud node may include:

[0040] S1. Based on the user's selection operation in the central cloud management interface, determine the target edge cloud node.

[0041] In practical applications, the central cloud node presents a list of operable edge cloud nodes or a graphical resource view in its central cloud management interface. Users can actively specify an edge cloud node as the destination for subsequent backup tasks within this interface by clicking, checking, dragging, or other interactive methods. The central cloud node captures and parses this user selection operation in real time, marks the selected edge cloud node as the target edge cloud node, and thus accurately locks the sending range of subsequent artifact resource retrieval and deployment instructions to this node, realizing single-point target confirmation triggered by user visual operation.

[0042] S2. Based on the storage location of the artifact resources in the central cloud artifact warehouse, generate artifact resource retrieval and deployment instructions for the target edge cloud nodes.

[0043] Among them, the artifact repository refers to a dedicated storage service established in the central cloud environment for centralized storage and management of backup management program artifact resources. It is responsible for versioning and uniformly controlling access to various artifacts, including container images and chart packages.

[0044] The artifact resource retrieval command is a specific operation command that instructs the target edge cloud node to obtain artifact resources such as backup program container images and chart packages from its local artifact repository or a specified source, such as a central cloud artifact repository. The deployment command refers to the configuration and execution commands that instruct the target edge cloud node to start and run the backup program container in its edge cluster according to specific parameters after the resources are ready.

[0045] In this embodiment, after identifying the target edge cloud node, the central cloud node immediately queries the unique internal path and access method corresponding to the container image and Chart package that have been uniformly stored in the central cloud artifact repository. Based on the storage location, it automatically assembles an artifact resource retrieval instruction that can be parsed and executed by the target edge cloud node. At the same time, it attaches deployment instructions that specify the naming, tagging and Chart package startup parameters after the image is imported into the local repository. This allows the target edge cloud node to accurately retrieve the corresponding artifact resources according to the instructions and complete local storage and image preparation without manual intervention.

[0046] S3. Send artifact resource retrieval and deployment instructions to the target edge cloud node to instruct the target edge cloud node to acquire artifact resources and complete storage and image preparation in its local artifact repository.

[0047] Specifically, the central cloud node pushes the artifact resource retrieval instructions, which carry the central cloud artifact repository access path, container image identifier, and chart package location information, as well as the deployment instructions describing the naming method, startup parameters, and storage directory rules after image import, to the target edge cloud node through its internal control channel. Upon receiving the instructions, the target edge cloud node actively connects to the central cloud artifact repository, retrieves the specified container image and chart package to its local machine, and completes image import, tag setting, and local artifact repository registration according to the deployment instructions. This ensures that all materials required for the backup program to run are in place and ready without relying on manual operation.

[0048] For example, when a user selects a target edge cloud node named "East China Edge Cloud" on the central cloud management interface and confirms the deployment, the central cloud node will generate and send an artifact resource retrieval instruction containing a specific resource address and a preliminary deployment instruction to the "East China Edge Cloud" node. This instruction instructs the "East China Edge Cloud" node to retrieve artifact resources such as the container image of the backup program and the Chart package from its local artifact repository or from the central cloud artifact repository according to the address, and persistently save them to the local artifact repository of the "East China Edge Cloud". At the same time, it ensures that the container image is loaded in its container runtime environment, thereby preparing for subsequent parameterized deployment.

[0049] S120. Based on the backup configuration parameters configured by the user, generate the corresponding deployment task and send it to the target edge cloud node to instruct the target edge cloud node to complete the parameterized deployment and startup of the backup program in the corresponding edge cluster.

[0050] Among them, backup configuration parameters refer to a set of customizable runtime variables set by the user for a specific backup task in the central cloud management interface. They specifically define the behavior rules of the backup program when it is executed in the edge cloud, including but not limited to the time period for triggering backup operations, the source storage path of the data to be backed up, and the network port for the HTTP service to provide access to the outside world, etc.

[0051] The deployment task refers to a work unit generated by the central cloud node based on the backup configuration parameters configured by the user. It contains specific deployment instructions and parameterized configuration information and carries a complete operation plan that instructs the target edge cloud node on how to start and run the backup program container in the corresponding edge cluster.

[0052] Among them, an edge cluster refers to a distributed computing resource pool that is organized by multiple computing nodes (servers) through container orchestration technology in a localized environment managed by a target edge cloud node, and can be uniformly scheduled and managed.

[0053] In this embodiment, the central cloud node reads the backup configuration parameters filled in by the user in the central cloud management interface, injects these variable values ​​that determine the backup scope, frequency, retention policy, resource quota, storage location, and HTTP service port into the template defined in the Chart package, renders and generates an executable deployment task, and then sends the deployment task to the target edge cloud node through the control channel. After receiving the deployment task, the target edge cloud node instantiates the container image in its edge cluster according to the content of the deployment task, automatically fills in the parameters into the environment variables, configuration files, and command line parameters, and completes the scheduling, mounting, network, and startup settings of the backup program, so that the backup program officially runs according to the parameter conditions specified by the user and begins periodic backups.

[0054] For example, a user configures backup configuration parameters for a specific backup task in the central cloud management interface, such as a backup cycle of 2:00 AM every day, a backup path of " / data / applogs", and an HTTP service port of "8080". The central cloud node will generate a specific deployment task based on these parameters. This task includes using the artifact resources (container image and chart package) that have been distributed to the target edge cloud, and instructs the target edge cloud node to start and run the backup program container in its edge cluster by executing at 2:00 AM every day, accessing the " / data / applogs" path, and exposing the HTTP service to the "8080" port.

[0055] S130. According to the preset backhaul strategy, initiate a backup result acquisition request to the target edge cloud node to receive and store the backup result files periodically generated by the backup program.

[0056] Among them, the preset backhaul strategy refers to a set of rules or plans pre-configured on the central cloud node side. It defines when, how, and under what conditions the central cloud initiates a request to the target edge cloud node to obtain the backup result file generated by the edge cloud backup program. This strategy is the core control logic that guides the central cloud to actively pull and reclaim edge backup data.

[0057] Among them, the backup result retrieval request refers to the network request instruction initiated by the central cloud node to the HTTP service module exposed by the backup program on the target edge cloud node according to the preset backhaul strategy, which aims to download the specified backup result file. It is the key operation command that triggers the transmission of backup data from the edge cloud to the central cloud.

[0058] The backup result file refers to the final output file collection generated by the backup program deployed on the edge cloud after execution according to the configured backup cycle. It contains compressed target data and related operation logs. The file is stored in the HTTP service directory specified by the backup program and can be accessed and downloaded by the central cloud node through the HTTP service module.

[0059] Specifically, the central cloud node proactively sends backup result retrieval requests to the target edge cloud node through the management channel, according to the time, frequency, and priority specified by the internally pre-set backhaul strategy. After receiving the request, the target edge cloud node backs the backup result files periodically generated during the local operation of the backup program to the central cloud node as requested. The central cloud node then stores the received backup result files in the central persistent space, realizing the centralized archiving and unified management of the backup results from the edge side to the central side.

[0060] For example, the preset backhaul strategy in the central cloud node is "actively retrieve the backup files generated by the edge cloud the previous day at 10:00 AM every day". Then, at 10:00 AM every day, the central cloud node will initiate a backup result retrieval request to the target edge cloud node (such as "North China Edge Cloud") that has deployed the backup program, pointing to its HTTP service port. After receiving the request, the edge cloud node will transmit the latest backup result files (such as data compressed packages and log files) to the central cloud through its HTTP service module. After receiving the files, the central cloud node will perform integrity verification and then store the successfully verified files in its own storage module.

[0061] Based on the above embodiments, optionally, the remote backup management method provided in this embodiment further includes the following steps:

[0062] (1) Based on the reception and verification results of the backup result file, determine whether the backup result acquisition process was successful.

[0063] In this embodiment, after receiving the backup result file returned by the target edge cloud node, the central cloud node can check the backup result file according to the preset integrity verification mechanism. Only when the backup result file is completely received and passes the consistency verification, the central cloud node will determine that the backup result acquisition process is successful. Otherwise, it will be judged as a failure and will proceed to the subsequent retry or alarm process.

[0064] (2) When it is determined that the backup result acquisition process has failed, the automatic retry process is started based on the preset retry strategy.

[0065] In this embodiment, when it is determined that the backup result acquisition process has failed, the pre-set retry conditions are determined based on the reason for the failure of the backup result acquisition. When the retry conditions are met, subsequent retry tasks are scheduled according to the pre-set maximum number of retries and retry interval.

[0066] Specifically, once the central cloud node determines that the acquisition has failed based on the reception and verification results of the backup result file, it immediately invokes the internally pre-set retry policy. This retry policy specifies the retry interval, number of times, and backoff margin. The central cloud node automatically generates a new round of backup result acquisition requests according to these rules and initiates them again to the target edge cloud node. This process is repeated without manual intervention until the retry limit is reached or the verified backup result file is successfully received, thus constituting an automatic retry process.

[0067] (3) If the backup result is still not successfully obtained after the automatic retry process is completed, a task failure alarm message will be sent to the administrator based on the preset alarm configuration.

[0068] In this embodiment, after the central cloud node attempts round by round according to the retry policy, if all retry opportunities are exhausted and a backup result file that has passed verification is still not obtained, it is determined that the backup result acquisition has completely failed. At this time, the corresponding notification channel, alarm level and receiving object in the preset alarm configuration are read immediately, and a task failure alarm message containing task identifier, failure reason and timestamp is automatically generated and pushed to the administrator via email, SMS or console prompt, prompting the administrator to manually intervene.

[0069] Based on the above embodiments, optionally, the remote backup management method provided in this embodiment further includes the following steps:

[0070] (1) Receive backup execution exception information pushed by the target edge cloud node through its HTTP service.

[0071] Among them, backup execution exception information refers to real-time notification messages that are proactively pushed to the central cloud node to report specific error conditions and causes.

[0072] In this embodiment, the central cloud node continuously listens for and captures the abnormal reports actively issued by the HTTP service program embedded in the target edge cloud node. When an error occurs during the backup program, the report is encapsulated in real time into backup execution abnormal information in a pre-defined format and pushed directly to the central cloud node via the HTTP channel. This allows the central cloud node to obtain the details of the abnormality occurring on the edge side in real time without polling, achieving zero-latency abnormality perception.

[0073] (2) Based on the received abnormal information, determine the type of execution failure of the backup program in the edge cloud.

[0074] Among them, the execution failure type refers to the specific error category that is identified after analyzing and classifying the received backup execution anomaly information, which causes the backup program to fail to complete the backup task normally in the edge cloud. Such as data source access failure, insufficient resources or configuration errors, etc. This type classification helps the central cloud node to perform accurate status updates and alarm responses.

[0075] Specifically, after receiving backup execution exception information pushed by the target edge cloud node through its HTTP service, the central cloud node immediately matches the error code, exception stage, resource status, and log keyword fields carried in the exception information with the internally pre-set fault feature library. This allows the exceptions occurring in the edge cloud backup program to be classified as network interruption, storage full, insufficient permissions, image startup failure, or other defined fault categories, thereby forming a clear execution fault type and providing a standardized basis for subsequent task status updates and alarm policy triggering.

[0076] (3) Based on the type of execution failure, update the status of the corresponding backup task and trigger an alarm.

[0077] In this embodiment, after the central cloud node determines the execution failure type of the backup program in the edge cloud, it immediately changes the running status of the backup task recorded on the central side from in progress or successful to a failure status that matches the failure type, according to the preset rules corresponding to the failure type. At the same time, it automatically generates and sends alarm information according to the notification method, level and recipient set for this failure type in the alarm configuration, so that the administrator can simultaneously perceive the task abnormality and intervene in a timely manner.

[0078] This application provides a cloud-edge collaborative remote backup management method, applied in a cloud-edge collaborative scenario comprising a central cloud and at least one edge cloud. The method is executed by a central cloud node and includes: issuing deployment instructions and artifact resources for a backup program to a target edge cloud node to trigger the target edge cloud node to complete the repository storage and image preparation of the backup program; generating a corresponding deployment task according to user-configured backup configuration parameters and sending it to the target edge cloud node to instruct the target edge cloud node to complete the parameterized deployment and startup of the backup program in the corresponding edge cluster; and initiating a backup result retrieval request to the target edge cloud node according to a preset return strategy to receive and store the backup result files periodically generated by the backup program. The technical solution of this application, by artifactizing the backup program and automatically generating deployment tasks in combination with user-configured parameters, realizes one-click, standardized distribution and parameterized deployment of the backup program from the central cloud to the edge cloud, effectively solving the problems of low deployment efficiency and easy configuration errors in the traditional manual mode. At the same time, by automatically triggering the acquisition and integrity verification of backup results through preset return strategies, it realizes the fully automated closed-loop management from edge backup execution to central result collection, significantly improving the management efficiency, policy consistency and operation and maintenance automation level of massive edge node backup tasks, and reducing the cost of manual intervention and operational risks.

[0079] Example 2

[0080] Figure 2 This is a schematic diagram of a cloud-edge collaborative remote backup management method provided in this application embodiment. Based on the foregoing embodiments, this embodiment provides a more detailed description of steps S120-S130. For specific implementation details, please refer to the technical solution of this embodiment. Technical terms that are the same as or corresponding to those in the above embodiments will not be repeated here.

[0081] like Figure 2 As shown, the method specifically includes the following steps:

[0082] S210: Issue deployment instructions and artifact resources for the backup program to the target edge cloud node to trigger the target edge cloud node to complete the repository storage and image preparation of the backup program.

[0083] S220: Determine backup configuration parameters based on user-inputted custom configuration information.

[0084] The backup configuration parameters include at least the backup execution cycle, the source path of the data to be backed up, and the HTTP service listening port. The backup execution cycle refers to the time interval or specific time rule set in the user-defined configuration information to control the automatic execution of backup operations by the backup program in the edge cluster. It defines the repetitive time pattern at which backup tasks are triggered. The source path of the data to be backed up refers to the original storage location or directory that the backup program needs to access and read when executing backup tasks in the edge cluster. This path is explicitly specified by the user in the custom configuration information and serves as the source data location identifier for the backup operation. The HTTP service listening port refers to the specific network port number bound to the HTTP service module integrated in the backup program's container image. This port is specified by the user in the custom configuration information and is used to receive network connection requests from the central cloud node or other clients to provide access to the index list of backup result files and file download services.

[0085] In this embodiment, the central cloud node reads the various custom configuration information filled in by the user for a specific backup task in the central cloud management interface. This information includes the backup execution cycle, the source path of the data to be backed up, the HTTP service listening port, and other optional limiting conditions. After the central cloud node performs legality checks and formatting on the above inputs according to the preset verification and conversion rules, it solidifies them into a set of standardized backup configuration parameters, which are used to associate with artifact resources and drive the edge-side backup program to run according to the user's wishes.

[0086] S230. Associate and bind the backup configuration parameters with the artifact resources to generate a deployment task containing specific parameter values.

[0087] In this embodiment, the central cloud node writes the backup configuration parameters determined by the user into the reserved variable positions in the Chart package one by one, so that the specific parameter values ​​such as the backup execution cycle, the source path of the data to be backed up, and the HTTP service listening port are logically matched with the artifact resources composed of the container image and the Chart package. Then, the filled template, image reference, task scheduling policy, data access permission and network access endpoint are encapsulated into an executable, deployable and traceable deployment task, which is used to drive the edge cluster to complete the instantiation and startup of the backup program according to the predetermined parameters.

[0088] Based on the above embodiments, optionally, the specific implementation steps for associating and binding backup configuration parameters with artifact resources to generate deployment tasks containing specific parameter values ​​may include:

[0089] (1) Based on the backup execution cycle and source path parameters, determine the task scheduling strategy and data access permissions of the backup execution module running in the edge cluster.

[0090] Among them, the task scheduling strategy refers to a set of explicit instructions generated by the deployment task and passed to the edge cluster backup execution module according to the backup execution cycle configured by the user. This strategy specifies the repetitive time rules for the backup task to be triggered and is the core logic for controlling the automated operation rhythm of the backup program.

[0091] Data access permissions refer to the authentication and operation permission credentials configured for the backup execution module running in the edge cluster based on the source path of the data to be backed up, which are used to legally read and operate the data under that path. It is a necessary security configuration to ensure that the backup program can successfully access the target data source.

[0092] In this embodiment, the central cloud node converts the backup execution cycle into a timed or periodic triggering rule that the edge cluster can recognize, and generates a corresponding read-only or read-write access range based on the data location identified by the source path parameters. Then, these two parts of information are combined into the task scheduling strategy and data access permissions that the backup execution module actually follows in the edge cluster, ensuring that the backup task starts at a predetermined time and can only access the allowed data to be backed up.

[0093] (2) Based on the HTTP service listening port parameters, determine the network access endpoint of the HTTP service module running in the edge cluster.

[0094] Among them, the network access endpoint refers to the specific network address and port combination determined by the HTTP service module of the backup program in the edge cluster according to the HTTP service listening port parameters configured by the user, which can be addressed and communicated by the external network. It is the network service entry point for the central cloud node to obtain backup result files.

[0095] Specifically, the central cloud node writes the HTTP service listening port parameter specified by the user into the deployment task. When the edge cluster starts the container image, it opens the corresponding container port and node port according to the port value, so that the HTTP service module obtains a fixed external listening address on the edge side. The central cloud node constructs subsequent file download requests based on this address, thereby uniquely determining the accessible network access endpoint.

[0096] (3) Encapsulate the task scheduling strategy, data access permissions, network access endpoints and artifact resources into deployment tasks.

[0097] In this embodiment, the central cloud node packages the task scheduling policy generated based on the backup execution cycle and source path parameters, the data access permissions granted based on the source path parameters, and the network access endpoints determined based on the HTTP service listening port parameters, along with artifact resources containing container images and chart packages, into a structured description. This description is then sent to the target edge cloud node as a unified deployment task. After parsing, the edge-side deployment agent can simultaneously obtain the scheduling rules, permission scope, access address, and runtime materials, thus achieving complete parameterized deployment and startup of the backup program in the edge cluster.

[0098] S240. Send a deployment task to the target edge cloud node to instruct the deployment agent program corresponding to the target edge cloud node to complete the parameterized deployment and startup of the backup program in the edge cluster according to the artifact resources and backup configuration parameters bound in the deployment task.

[0099] Specifically, the central cloud node distributes the pre-packaged deployment task to the target edge cloud node through the control channel. After receiving the task, the deployment agent parses the artifact resources and backup configuration parameters carried in it, and sequentially completes the container image pull, instance creation, environment variable injection, port exposure and scheduling policy application within the edge cluster. This enables the backup program to automatically start and enter the running state according to the parameters set by the user, realizing parameterized deployment and self-starting on the edge side.

[0100] S250: Generate a backup result retrieval request based on the preset backhaul strategy and the backup execution status of the target edge cloud.

[0101] Among them, the backup execution status refers to the dynamic information about the current or most recent backup task execution status fed back by the backup program deployed on the target edge cloud during its operation, either by the program itself or by the edge cloud management component. This information includes real-time status such as whether it is being executed, whether it has been completed, or whether it has failed. The central cloud node uses this status information to decide whether and when to generate a backup result retrieval request.

[0102] Specifically, the central cloud node determines whether the backup task has generated an available result file based on the timing, frequency, and priority specified by the internally pre-set backhaul strategy, combined with the backup execution status reported in real time by the target edge cloud node. Once the strategy conditions are met, a backup result retrieval request is automatically generated for that edge node to initiate the subsequent file download and verification process.

[0103] S260. Based on the access configuration of the HTTP service module in the backup program, construct the corresponding file download request and send it to the target edge cloud node.

[0104] Among them, the file download request refers to the network request message constructed and sent by the central cloud node based on the backup result retrieval request and according to the access configuration of the HTTP service module in the backup program, which aims to obtain a specific backup result file from the target edge cloud node. This request specifically points to the file access interface provided by the HTTP service module.

[0105] Specifically, the central cloud node extracts the access address, path, and protocol of the backup program's HTTP service module from the HTTP service listening port and other network parameters written during the deployment phase. Based on these access configurations, it automatically generates a file download request containing the target file name, download path, and necessary authentication information, and sends the request to the target edge cloud node through the network channel to pull the backup result file.

[0106] S270. Receive the backup result file from the target edge cloud node, perform an integrity check on the backup result file, and determine the integrity check result.

[0107] The integrity verification result refers to the final judgment on whether the file has been corrupted during transmission, determined by comparing the characteristics of the received data digest with those of the pre-recorded source data digest after performing an integrity verification operation on the received backup result file.

[0108] Specifically, after a file download request is issued, the central cloud node continuously receives the backup result file returned by the target edge cloud node through the previously established transmission channel. At the same time, during or after the reception, it compares and verifies the data digest characteristics of the backup result file according to the preset integrity verification mechanism to determine whether the file is damaged or missing during the transmission process, thereby obtaining the integrity verification result of success or failure, and providing a basis for subsequent determination of whether it meets the storage standards.

[0109] Based on the above embodiments, optionally, the specific implementation steps for performing file integrity verification may include:

[0110] (1) Obtain the received data digest characteristics of the backup result file.

[0111] In this embodiment, after the central cloud node fully receives the backup result file from the target edge cloud node, it immediately performs a one-way hash calculation on the file content according to a predetermined digest algorithm, thereby extracting the received data digest feature that can uniquely identify the file data content. This feature is then compared with the pre-recorded source data digest feature to determine whether the file has been damaged or tampered with during transmission.

[0112] (2) Based on the comparison between the characteristics of the received data digest and the characteristics of the pre-recorded source data digest, determine whether the file has been corrupted during transmission.

[0113] Among them, the source data digest feature refers to the feature value that is pre-calculated and recorded by the backup program or service module of the edge cloud based on the content of the original backup result file before the backup result file is transmitted from the edge cloud node to the central cloud node. This feature value is used by the central cloud node as a benchmark reference to verify whether the received file is consistent.

[0114] In this embodiment, after receiving the backup result file, the central cloud node compares the received data digest features it calculates in real time with the source data digest features that the edge side records in advance and provides with the file when the file is generated. If the two are completely consistent, it is determined that the file content has remained intact and unmodified in the transmission link. If any difference occurs, it is considered that the file has been corrupted, and the conclusion of verification success or failure is drawn accordingly.

[0115] (3) If it is determined that the file has been corrupted, the integrity check result is determined to be a failure; if it is determined that the file has not been corrupted, the integrity check result is determined to be a success.

[0116] Specifically, after receiving the backup result file, the central cloud node compares the received data digest features it calculates in real time with the source data digest features that the edge side records in advance and provides with the file when it is generated. If the two are completely consistent, it is determined that the file content has remained intact and unmodified in the transmission link. If any difference occurs, it is considered that the file has been corrupted, and the conclusion of verification success or failure is drawn accordingly.

[0117] S280. Based on the integrity verification results, determine whether the backup result file meets the storage standards.

[0118] In this embodiment, after obtaining the integrity verification result of the backup result file, the central cloud node uses the successful verification as the sole criterion. If the integrity verification result shows that the verification is successful, it is determined that the backup result file has remained intact and undamaged during the transmission process, meets the pre-set storage standards, and is allowed to enter the subsequent persistent storage stage. If the integrity verification result shows that the verification fails, it is determined that the file does not meet the storage standards, is directly rejected from being stored, and the corresponding retransmission or alarm process is triggered.

[0119] S290. When the storage standard is met, the backup result file is persistently stored in the central cloud storage module, and the backup task status corresponding to the central cloud management interface is updated based on the file reception status.

[0120] The backup task status refers to the progress indicators recorded in the central cloud management interface to describe and track the entire process of a specific backup task from deployment to final result return. These indicators include "Deploying", "Backup in progress", "Waiting for return", "Return successful" or "Return failed". This status is updated in real time based on key events such as file reception status.

[0121] In this embodiment, after the integrity verification result shows that the backup result file meets the storage standard, the central cloud node immediately writes the file into the central cloud storage module for long-term preservation. At the same time, based on the fact that the file has been successfully received, the running status of the corresponding backup task on the central cloud management interface is refreshed to complete or successful, ensuring that the interface display is consistent with the background data.

[0122] For example, Figure 3 This is a schematic diagram of the system architecture of the remote backup management method involved in this embodiment. Figure 3 As shown. This system includes a central cloud and at least one edge cloud, which are connected via network communication to form a cloud-edge collaborative architecture. The central cloud node, as the unified management and control terminal, is responsible for the artifactification, deployment, and backup result retrieval of backup programs, specifically including:

[0123] The artifact management module handles the artifactization and lifecycle management of backup programs. It responds to artifact deployment requests, receives and version-manages container images containing the backup program and HTTP service program, along with their corresponding Chart packages. Based on user selections, it issues artifact synchronization commands to the target edge cloud node to trigger the node to pull and store artifact resources. Further, based on user-inputted custom configuration information (including at least the backup execution cycle, the path to the data source to be backed up, and the HTTP service listening port), this module determines backup configuration parameters, associates and binds them with artifact resources, generates a deployment task containing specific parameter values, and then sends this deployment task to the target edge cloud node to drive it to complete the parameterized deployment and startup of the backup program.

[0124] Backup Result Receiving Module: This module actively acquires and verifies edge backup results. Based on a preset backhaul strategy and the backup execution status of the target edge cloud, it generates a backup result retrieval request. Using the access configuration of the HTTP service module in the backup program, it constructs a specific file download request and sends it to the target edge cloud node. Upon receiving the backup result file from the edge cloud node, it performs an integrity verification. This involves comparing the received data digest characteristics with the pre-recorded source data digest characteristics to determine if data corruption occurred during transmission, thus obtaining the integrity verification result. Based on this result, it judges whether the file conforms to storage standards.

[0125] Storage Module: Used for persistent storage of valid backup data. When a backup result file is determined to meet storage standards, this module will persistently store the file and update the status of the corresponding backup task in the central cloud management interface based on the file's final reception status.

[0126] Edge cloud nodes, acting as command execution and data processing terminals, are used to receive and run backup programs, specifically including:

[0127] Artifact Agent Module: This module acts as an execution agent in collaboration with the central cloud. Upon receiving artifact synchronization instructions, it pulls the specified backup program container image and Chart package from the central cloud artifact repository and pushes them to the local artifact repository on the edge cloud, completing repository storage and image preparation. After receiving a deployment task from the central cloud, this module, based on the artifact resources and backup configuration parameters bound to the deployment task, completes the parameterized deployment and startup of the backup program in the corresponding edge cluster by encapsulating task scheduling policies, data access permissions, and network access endpoints.

[0128] Backup Execution Module: As the core execution unit of the backup logic, after deployment and startup in the edge cluster, this module strictly follows the backup execution cycle defined in the deployment task, accesses the specified data source path to be backed up, performs backup operations, and generates a backup result file containing data compressed packages and log files.

[0129] The HTTP service module serves as the unified interface for accessing backup results. This module runs on the HTTP service listening port specified by the deployment task, stores the backup result files generated by the backup execution module in a designated directory of its service, and provides a file index list. It responds to file download requests initiated by the central cloud, providing the specified backup result files to the central cloud backup result receiving module for download, and also provides source data digest characteristics for integrity verification.

[0130] The technical solution of this application embodiment generates a corresponding deployment task and sends it to the target edge cloud node based on the backup configuration parameters configured by the user. The backup configuration parameters are determined based on the user-input custom configuration information. The backup configuration parameters include at least the backup execution cycle, the source path of the data to be backed up, and the HTTP service listening port. Then, the backup configuration parameters are associated and bound with artifact resources to generate a deployment task containing specific parameter values. The deployment task is then sent to the target edge cloud node to instruct the deployment agent program corresponding to the target edge cloud node to complete the parameterized deployment and startup of the backup program in the edge cluster according to the artifact resources and backup configuration parameters bound in the deployment task. The technical solution of this application dynamically associates and binds user-defined backup configuration parameters tailored to specific business scenarios with standardized encapsulated artifact resources, generating highly parameterized and immediately executable deployment tasks. This enables the central cloud to drive the deployment agent program on the edge side with unified and automated instructions, accurately adapting and deploying general backup programs to diverse edge environments without manual intervention. Ultimately, it achieves cloud-edge collaborative backup capabilities of one-time configuration, automatic deployment, and on-demand operation, greatly improving the flexibility, accuracy, and efficiency of edge backup task deployment.

[0131] The technical solution of this application embodiment, when initiating a backup result retrieval request to the target edge cloud node according to a preset backhaul strategy to receive and store the backup result file periodically generated by the backup program, generates a backup result retrieval request based on the preset backhaul strategy and the backup execution status of the target edge cloud; constructs a corresponding file download request based on the access configuration of the HTTP service module in the backup program and sends it to the target edge cloud node; receives the backup result file from the target edge cloud node and performs an integrity check on the backup result file to determine the integrity check result; determines whether the backup result file meets the storage standard based on the integrity check result; when it meets the storage standard, persistently stores the backup result file in the central cloud storage module, and updates the corresponding backup task status on the central cloud management interface based on the file reception status. The technical solution of this application combines a preset automated backhaul strategy with the real-time edge backup execution status to intelligently trigger and construct precise file download requests. It utilizes the HTTP service module built into the backup program as a standardized data channel to achieve controllable and orderly retrieval of backup result files from the edge to the center. On this basis, it ensures the accuracy of transmitted data by performing strict integrity checks, and automatically completes persistent storage and task status synchronization in the central cloud after verification. This constructs a closed-loop, reliable, and automated cloud-edge data recycling and unified management process, effectively guaranteeing the final consistency and auditability of backup data and the automation level of the entire backup system's operation and maintenance.

[0132] Example 3

[0133] Figure 4 This is a schematic diagram of a cloud-edge collaborative remote backup management device provided in an embodiment of this application. It is applied in a cloud-edge collaborative scenario comprising a central cloud and at least one edge cloud. The method is executed by a central cloud node. The device includes:

[0134] The backup program distribution module 310 is used to distribute deployment instructions and artifact resources of the backup program to the target edge cloud node, so as to trigger the target edge cloud node to complete the warehouse storage and image preparation of the backup program.

[0135] The deployment task sending module 320 is used to generate a corresponding deployment task according to the backup configuration parameters configured by the user and send it to the target edge cloud node, so as to instruct the target edge cloud node to complete the parameterized deployment and startup of the backup program in the corresponding edge cluster.

[0136] The backup result receiving module 330 is used to initiate a backup result acquisition request to the target edge cloud node according to a preset backhaul strategy, so as to receive and store the backup result file periodically generated by the backup program.

[0137] This application provides a cloud-edge collaborative remote backup management device. When in use, the device sends deployment instructions and artifact resources of the backup program to the target edge cloud node to trigger the target edge cloud node to complete the repository storage and image preparation of the backup program. Then, according to the backup configuration parameters configured by the user, the device generates a corresponding deployment task and sends it to the target edge cloud node to instruct the target edge cloud node to complete the parameterized deployment and startup of the backup program in the corresponding edge cluster. Then, according to the preset return strategy, the device initiates a backup result acquisition request to the target edge cloud node to receive and store the backup result files periodically generated by the backup program. The technical solution of this application, by artifactizing the backup program and automatically generating deployment tasks in combination with user-configured parameters, realizes one-click, standardized distribution and parameterized deployment of the backup program from the central cloud to the edge cloud, effectively solving the problems of low deployment efficiency and easy configuration errors in the traditional manual mode. At the same time, by automatically triggering the acquisition and integrity verification of backup results through preset return strategies, it realizes the fully automated closed-loop management from edge backup execution to central result collection, significantly improving the management efficiency, policy consistency and operation and maintenance automation level of massive edge node backup tasks, and reducing the cost of manual intervention and operational risks.

[0138] Optionally, based on the above-mentioned device, the device further includes: a product resource listing module, used to respond to a product listing request and determine the product resources to be listed; wherein, the product resources include a container image integrating a backup program and an HTTP service program, and a Chart package containing the startup parameter definition of the container image; and the product resources to be listed are stored in the product warehouse of the central cloud for unified management.

[0139] Optionally, based on the above-mentioned device, the backup program distribution module 310 is specifically used to determine the target edge cloud node based on the user's selection operation in the central cloud management interface; generate product resource retrieval instructions and deployment instructions for the target edge cloud node according to the storage location of the product resources in the central cloud product warehouse; and send the product resource retrieval instructions and deployment instructions to the target edge cloud node to instruct the target edge cloud node to obtain the product resources and complete storage and image preparation in its local product warehouse.

[0140] Optionally, based on the above-mentioned device, a deployment task sending module 320 is used to determine backup configuration parameters based on user-inputted custom configuration information; wherein, the backup configuration parameters include at least the backup execution cycle, the source path of the data to be backed up, and the HTTP service listening port; associate and bind the backup configuration parameters with the artifact resources to generate a deployment task containing specific parameter values; and send the deployment task to the target edge cloud node to instruct the deployment agent program corresponding to the target edge cloud node to complete the parameterized deployment and startup of the backup program in the edge cluster according to the artifact resources bound in the deployment task and the backup configuration parameters.

[0141] Optionally, based on the above-mentioned device, the deployment task sending module 320 is further configured to determine the task scheduling strategy and data access permissions of the backup execution module running in the edge cluster based on the backup execution cycle and source path parameters; determine the network access endpoint of the HTTP service module running in the edge cluster based on the HTTP service listening port parameters; and encapsulate the task scheduling strategy, the data access permissions, the network access endpoint, and the artifact resources into a deployment task.

[0142] Based on the above-mentioned device, optionally, the backup result receiving module 330 is specifically used to generate a backup result acquisition request according to the preset backhaul strategy and the backup execution status of the target edge cloud; construct a corresponding file download request and send it to the target edge cloud node based on the access configuration of the HTTP service module in the backup program; receive the backup result file from the target edge cloud node, and perform integrity verification on the backup result file to determine the integrity verification result; determine whether the backup result file meets the storage standard based on the integrity verification result; when it meets the storage standard, persist the backup result file to the central cloud storage module, and update the backup task status corresponding to the central cloud management interface based on the file receiving status.

[0143] Based on the above-mentioned device, optionally, the backup result receiving module 330 is further used to obtain the received data digest characteristics of the backup result file; compare the received data digest characteristics with the pre-recorded source data digest characteristics to determine whether the file has been corrupted during transmission; if it is determined that the file has been corrupted, the integrity verification result is determined to be a verification failure; if it is determined that the file has not been corrupted, the integrity verification result is determined to be a verification success.

[0144] Optionally, based on the above-mentioned device, the device further includes: a result retry acquisition module, used to determine whether the current backup result acquisition process is successful based on the reception and verification results of the backup result file; when it is determined that the current backup result acquisition process has failed, to start an automatic retry process based on a preset retry strategy; and after the automatic retry process is completed, if the backup result acquisition is still unsuccessful, to send a task failure alarm message to the administrator based on a preset alarm configuration.

[0145] Optionally, based on the above-mentioned device, the device further includes: a backup exception execution module, configured to receive backup execution exception information pushed by the target edge cloud node through its HTTP service; determine the execution failure type of the backup program in the edge cloud based on the received exception information; and update the status of the corresponding backup task and trigger an alarm based on the execution failure type.

[0146] The cloud-edge collaborative remote backup management device provided in this application embodiment can execute the cloud-edge collaborative remote backup management method provided in any embodiment of this application, and has the corresponding functional modules and beneficial effects of the execution method.

[0147] It is worth noting that the various units and modules included in the above system are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the protection scope of the embodiments of this application.

[0148] Example 4

[0149] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 5 A block diagram is shown of an exemplary electronic device 40 suitable for implementing embodiments of the present application. Figure 5 The electronic device 40 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0150] like Figure 5 As shown, the electronic device 40 is represented in the form of a general-purpose computing device. The components of the electronic device 40 may include, but are not limited to: one or more processors or processing units 401, system memory 402, and bus 403 connecting different system components (including system memory 402 and processing unit 401).

[0151] Bus 403 represents one or more of several bus architectures, including memory buses or memory electronics, peripheral buses, graphics acceleration ports, processors, or local buses using any of the various bus architectures. Examples of these architectures include, but are not limited to, the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MAC) bus, the Enhanced ISA bus, the Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnect (PCI) bus.

[0152] Electronic device 40 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by electronic device 40, including volatile and non-volatile media, removable and non-removable media.

[0153] System memory 402 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 404 and / or cache memory 405. Electronic device 40 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 406 may be used to read and write non-removable, non-volatile magnetic media (… Figure 5 Not shown; usually referred to as a "hard drive"). Although Figure 5As not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk") and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 403 via one or more data media interfaces. Memory 402 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 this application.

[0154] A program / utility 408 having a set (at least one) of program modules 407 may be stored, for example, in memory 402. Such program modules 407 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 an implementation of a network environment. Program modules 407 typically perform the functions and / or methods described in the embodiments of this application.

[0155] Electronic device 40 can also communicate with one or more external devices 409 (e.g., keyboard, pointing device, display 410, etc.), and with one or more devices that enable a user to interact with electronic device 40, and / or with any device that enables electronic device 40 to communicate with one or more other computing devices (e.g., network card, modem, etc.). This communication can be performed via input / output (I / O) interface 411. Furthermore, electronic device 40 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 412. As shown, network adapter 412 communicates with other modules of electronic device 40 via bus 403. It should be understood that, although... Figure 5 Not shown, other hardware and / or software modules may be used in conjunction with electronic device 40, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0156] The processing unit 401 executes various functional applications and page processing by running programs stored in the system memory 402, such as implementing the cloud-edge collaborative remote backup management method provided in the embodiments of this application.

[0157] Example 5

[0158] This application embodiment also provides a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to perform a cloud-edge collaborative remote backup management method, applied in a cloud-edge collaborative scenario comprising a central cloud and at least one edge cloud. The method is executed by a central cloud node and includes:

[0159] Deployment instructions and artifact resources for the backup program are sent to the target edge cloud node to trigger the target edge cloud node to complete the repository storage and image preparation of the backup program;

[0160] Based on the backup configuration parameters configured by the user, a corresponding deployment task is generated and sent to the target edge cloud node to instruct the target edge cloud node to complete the parameterized deployment and startup of the backup program in the corresponding edge cluster.

[0161] According to the preset backhaul strategy, a backup result retrieval request is initiated to the target edge cloud node to receive and store the backup result files periodically generated by the backup program.

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

[0163] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, capable of sending, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device.

[0164] The program code contained on a computer-readable medium may be transmitted using any suitable medium, including—but not limited to—wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0165] Computer program code for performing the operations of the embodiments of this application can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages—such as Java, Smalltalk, and C++—and 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, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0166] Note that the above description is merely a preferred embodiment and the technical principles employed in this application. Those skilled in the art will understand that this application is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of this application. Therefore, although this application has been described in detail through the above embodiments, this application is not limited to the above embodiments. Many other equivalent embodiments may be included without departing from the concept of this application, and the scope of this application is determined by the scope of the appended claims.

Claims

1. A cloud-edge collaborative remote backup management method, characterized in that, Applied to a cloud-edge collaboration scenario including a center cloud and at least one edge cloud, the method is executed by a center cloud node, and the method comprises: issuing a backup program deployment instruction and artifact resources to a target edge cloud node to trigger the target edge cloud node to complete warehouse storage and image preparation of the backup program; generating a corresponding deployment task according to a user-configured backup configuration parameter and sending it to the target edge cloud node to instruct the target edge cloud node to complete parameterized deployment and start of the backup program in a corresponding edge cluster; according to a preset backhaul strategy, initiating a backup result acquisition request to the target edge cloud node to receive and store the backup result file periodically generated by the backup program.

2. The method of claim 1, wherein, Before the backup program deployment instruction and artifact resources are issued to the target edge cloud node, the method further comprises: in response to an artifact onboarding request, determining artifact resources to be on-boarded; wherein the artifact resources include a container image integrated with a backup program and an HTTP service program, and a Chart package containing definition of startup parameters of the container image; storing the artifact resources to be on-boarded to the artifact warehouse of the center cloud for unified management.

3. The method of claim 1, wherein, The backup program deployment instruction and artifact resources issued to the target edge cloud node comprise: determining a target edge cloud node based on a selection operation of a user on a center cloud management interface; generating artifact resource pull instructions and deployment instructions for the target edge cloud node according to the storage location of the artifact resources in the center cloud artifact warehouse; sending the artifact resource pull instructions and deployment instructions to the target edge cloud node to instruct the target edge cloud node to obtain the artifact resources and complete storage and image preparation in its local artifact warehouse.

4. The method of claim 1, wherein, The generation of a corresponding deployment task according to a user-configured backup configuration parameter and the sending of the deployment task to the target edge cloud node comprise: determining backup configuration parameters based on user-input custom configuration information; wherein the backup configuration parameters at least include a backup execution period, a source path of data to be backed up, and an HTTP service listening port; associating and binding the backup configuration parameters with the artifact resources to generate a deployment task containing specific parameter values; sending the deployment task to the target edge cloud node to instruct a corresponding deployment agent program of the target edge cloud node to complete parameterized deployment and start of the backup program in an edge cluster according to the artifact resources and the backup configuration parameters bound in the deployment task.

5. The method of claim 4, wherein, The association and binding of the backup configuration parameters with the artifact resources to generate a deployment task containing specific parameter values comprise: determining a task scheduling strategy and data access permission of a backup execution module running in an edge cluster based on the backup execution period and source path parameters; determining a network access endpoint of an HTTP service module running in an edge cluster based on the HTTP service listening port parameter; packaging the task scheduling strategy, the data access permission, the network access endpoint, and the artifact resources into a deployment task.

6. The method of claim 1, wherein, The backup result acquisition request is initiated to the target edge cloud node according to the preset backup transmission strategy, and backup result files periodically generated by the backup program are received and stored, including: According to the preset backup transmission strategy and the backup execution state of the target edge cloud, a backup result acquisition request is generated; Based on the access configuration of the HTTP service module in the backup program, a corresponding file download request is constructed and sent to the target edge cloud node; Backup result files from the target edge cloud node are received, and integrity verification of the backup result files is performed to determine the integrity verification result; Based on the integrity verification result, it is determined whether the backup result file meets the storage standard; When the storage standard is met, the backup result file is stored in the central cloud storage module, and the backup task state of the central cloud management interface is updated based on the file receiving state.

7. The method of claim 6, wherein, The integrity verification of the file is performed to determine the integrity verification result, including: Obtain the receiving data digest feature of the backup result file; Based on the comparison between the receiving data digest feature and the pre-recorded source data digest feature, it is determined whether data damage occurs in the file during transmission; If it is determined that the file has data damage, the integrity verification result is determined as verification failure; If it is determined that the file has no data damage, the integrity verification result is determined as verification success.

8. The method of claim 1, wherein, The method further comprises: Based on the receiving and verification result of the backup result file, it is determined whether the current backup result acquisition process is successful; When it is determined that the current backup result acquisition process fails, based on the preset retry strategy, an automatic retry process is started; After the automatic retry process is completed, if the backup result acquisition is still unsuccessful, based on the preset alarm configuration, task failure alarm information is sent to the administrator.

9. The method of claim 1, wherein, The method further comprises: Receiving backup execution exception information pushed by the HTTP service of the target edge cloud node; Based on the received exception information, the execution failure type of the backup program in the edge cloud is determined; Based on the execution failure type, the state of the corresponding backup task is updated and an alarm is triggered.

10. A cloud-edge collaborative remote backup management apparatus, characterized by, The device is applied to a cloud-edge collaborative scenario including a central cloud and at least one edge cloud, and is executed by the central cloud node. The device comprises: A backup program issuing module is configured to issue deployment instructions and artifact resources of a backup program to a target edge cloud node to trigger the target edge cloud node to complete warehouse storage and image preparation of the backup program; A deployment task sending module is configured to generate a corresponding deployment task according to user-configured backup configuration parameters and send the deployment task to the target edge cloud node to instruct the target edge cloud node to complete parameterized deployment and start of the backup program in a corresponding edge cluster; A backup result receiving module is configured to initiate a backup result acquisition request to the target edge cloud node according to a preset backup transmission strategy to receive and store backup result files periodically generated by the backup program.

Images