An edge cloud Android instance backup distribution recovery method, device and medium

Abstract

The application discloses an edge cloud Android instance backup distribution recovery method and device and medium, relates to the technical field of cloud computing backup recovery, and comprises the following steps: distributing and importing the backup content in the cause-effect closed consistency backup record, checking the received content with the cause-effect closed recovery position, encapsulating the received content that passes the consistency check according to the target node recovery interface requirement to form a target node recovery content package; based on the target node recovery content package, delimiting an isolated recovery position, respectively constructing a source identity inheritance recovery path and a target identity reconstruction recovery path and executing start playback, tracking application access exceptions and screening effective segments, segmenting and connecting the effective segments and performing closed playback, connecting the effective segments that pass the closed playback to the formal application data position to form a backup recovery life cycle record. The application reduces the application access interruption risk and improves the cross-node recovery continuity.

Description

Technical Field

[0001] This invention relates to the field of cloud computing backup and recovery technology, and in particular to a method, device and medium for backup, distribution and recovery of edge cloud Android instances. Background Technology

[0002] With the development of edge computing, containerized operating environments, and distributed storage technologies, Android instance backup has gradually evolved from single-node file copying to combined backup of content and configuration content across different storage disks. Common solutions save backup content through snapshots, object storage, or cross-node synchronization, and establish a correspondence between backup content and instances using instance UUID, backup UUID, storage path, and task identifier. During the recovery phase, the backup content is first distributed to the target node, and then a recovery payload is generated based on the target node's recovery interface to execute instance recovery, thereby supporting application scenarios such as original instance overwriting, new instance recovery, and disaster recovery node takeover.

[0003] Existing solutions typically focus on whether backup files have been generated, whether the target node has been loaded, and whether the recovery task can be started. In scenarios where edge cloud Android instances contain multiple storage disk contents and configuration contents and need to be distributed and restored across storage locations, each content is often extracted and transmitted separately as an independent backup object. If adjacent backup locations happen to fall on the mount boundary, the file integrity check may still pass, but the storage connection between the end content of the previous backup location and the beginning content of the next backup location may be truncated. After recovery to the target node, it will be affected by the reconnection and identity reconstruction of the target storage location, which will cause the application access to be interrupted during the startup and playback process. The reason is that the existing verification mainly focuses on the existence and loadability of single backup contents, and does not verify whether the reconnection or withdrawal operation can simultaneously repair the original break and avoid the formation of new connection breaks around the cross-disk boundary. Summary of the Invention

[0004] In view of the aforementioned existing problems, the present invention is proposed.

[0005] Therefore, this invention provides a method for backup, distribution and recovery of edge cloud Android instances to solve the problems of content continuity breakage and application access interruption in cross-disk backup and recovery of edge cloud Android instances.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution:

[0007] In a first aspect, the present invention provides a method for backup, distribution and recovery of Android instances in an edge cloud, comprising:

[0008] The system receives backup requests from edge cloud Android instances and establishes backup UUIDs and backup task identifiers. Based on the instance UUID, it locates the content to be backed up, divides backup locations according to business affiliation and storage assignment, verifies the affiliation of each backup location, and fills in any missing parts, forming an Android instance backup object record. Based on this record, it locates backup boundary truncation points, constructs forward patching segments and reverse rollback segments, and defines a candidate backup range. It copies the content to be backed up within the candidate backup range to form a temporary candidate backup copy and performs bidirectional closed replay, filtering out abnormal segments. The remaining segments are then added to the candidate backup range in replay order, and causal closed recovery is defined. The backup location is restored to form a causal closed-loop consistent backup record. The backup content in the causal closed-loop consistent backup record is distributed and imported. The consistency of the received content with the causal closed-loop recovery location is checked. The received content that passes the consistency check is encapsulated according to the target node recovery interface requirements to form a target node recovery content package. Based on the target node recovery content package, the isolated recovery location is defined. The source identity inheritance recovery path and the target identity reconstruction recovery path are constructed and start-up replay is performed. Application access anomalies are tracked and valid segments are selected. The valid segments are segmented and replayed in a closed loop. The valid segments that pass the closed loop replay are connected to the formal application data location to form a backup recovery lifecycle record.

[0009] As a preferred embodiment of the edge cloud Android instance backup, distribution, and recovery method described in this invention, the step of locating the content to be backed up based on the instance UUID is as follows:

[0010] Receive an edge cloud Android instance backup request, extract the instance UUID, create a backup UUID and backup task identifier for the edge cloud Android instance backup request, and associate the backup UUID, backup task identifier and instance UUID to form a backup request mapping table;

[0011] Based on the backup request mapping table, the corresponding edge cloud Android instance is located according to the instance UUID. The content to be backed up is extracted along the existing content mounting location and storage receiving location of the edge cloud Android instance. Content that does not belong to the current edge cloud Android instance is removed to obtain the content to be backed up.

[0012] As a preferred embodiment of the edge cloud Android instance backup, distribution, and recovery method of the present invention, the step of forming an Android instance backup object record is as follows:

[0013] The business affiliation of the content to be backed up is identified, and the backup locations are divided according to the storage location and the direction of the backup content. The content to be backed up that has the same business affiliation and is handled by the same storage location is assigned to the corresponding backup location to form a backup location list.

[0014] The backup location list is checked for ownership and missing items are filled in. Backup locations with consistent business ownership and continuous storage succession are retained. Missing backup content is filled into the corresponding backup location, and each backup location is connected according to the backup UUID to form an Android instance backup object record.

[0015] As a preferred embodiment of the edge cloud Android instance backup, distribution, and recovery method of the present invention, the construction of the forward patching segment and the reverse rollback segment is specifically as follows:

[0016] Based on the backup object record of the Android instance, the backup locations corresponding to the system disk content, data disk content and configuration content in the same edge cloud Android instance are extracted. According to the mounting order and backup order of each item in the edge cloud Android instance, the previous backup location is sequentially connected with the next backup location to form a cross-disk connection chain.

[0017] The adjacent backup positions are located one by one along the cross-disk connection chain. The end content of the previous backup position is extended to the next backup position, and the beginning content of the next backup position is reversed and connected back to the previous backup position. The connection positions where there are still content gaps and the connection positions where the content cannot be connected continuously are located by bidirectional boundary splicing, and these are marked as backup boundary truncation positions.

[0018] Based on the backup boundary truncation position, backtrack to the previous continuous continuation position and construct a forward supplementary segment that crosses the truncation position. Then, track the backup content that continues from the broken state, truncate it to the position of re-continuation and reverse the arrangement to construct a reverse withdrawal segment. The backup content before and after the two types of segments are included in the candidate backup range.

[0019] As a preferred embodiment of the edge cloud Android instance backup, distribution, and recovery method of the present invention, the step of forming a causal closed-loop consistent backup record is specifically as follows:

[0020] According to the candidate backup range, the backup content before and after the backup boundary cutoff position is extracted, the cross-disk connection position and the continuation order are retained and copied to form a temporary copy of the candidate backup. The forward supplementary segment is connected along the cross-disk connection direction and the forward closed playback is performed. The corresponding backup content is removed according to the reverse withdrawal segment in the opposite direction and the reverse closed playback is performed. The segments that have not been repaired in the original state and those that have caused new state breaks are screened out. The retained segments are continuated in the playback order to form a closed playback screening list.

[0021] Following the playback order in the closed playback filter list, the retained forward patch segments are accessed and the broken subsequent content corresponding to the retained reverse withdrawal segments is removed. The content to be backed up is continued along the cross-disk connection relationship. The continuous connection position is marked as the causal closure recovery position, and the continued content to be backed up is written to the corresponding position of the backup UUID to form a causal closure consistent backup record.

[0022] As a preferred embodiment of the edge cloud Android instance backup, distribution, and recovery method of the present invention, the step of forming the target node recovery content package is specifically as follows:

[0023] The backup content is extracted along the causal closed-loop consistency backup record. The storage location is extracted from the backup location carried by the backup content and marked as the source storage location. The target node recovery interface is called to obtain the target storage location. The causal closed-loop recovery location is attached to the corresponding target storage location to form a backup distribution location chain.

[0024] Along the backup distribution location chain, the backup content is distributed and arranged according to the playback order in the causal closure consistency backup record, and each backup content is connected to the source storage location, target storage location and causal closure recovery location to form a backup distribution sequence;

[0025] According to the backup distribution sequence, the backup content is distributed from the source storage location to the target storage location, and imported into the target storage location in the playback order to form the received content;

[0026] According to the playback order, the received content is connected to the corresponding causal closure recovery position one by one. The adjacent received content is checked according to the connection relationship after the forward supplementary segment is connected and the reverse withdrawn segment is removed. The position of the received content that deviates from the order is adjusted and the sequence is continued to form the restored continuation content.

[0027] According to the target node recovery interface requirements, the recovery continuation content, backup UUID, target storage location, causal closure recovery location, and playback order are encapsulated to form the target node recovery content package.

[0028] As a preferred embodiment of the edge cloud Android instance backup, distribution, and recovery method described in this invention, the execution of the startup replay is specifically as follows:

[0029] The source identity inheritance of the recovery continuation content in the recovery content package of the target node is performed. The recovery continuation of the recovery continuation content corresponding to the same source identity is maintained according to the backup UUID and the causal closure recovery position, and the source identity inheritance recovery path is constructed.

[0030] The target identity is reconstructed and orchestrated for the restored content. The restored content is reconnected according to the target storage location and the target node recovery interface. The target identity reconstruction recovery path is constructed. The two recovery paths are connected to the isolated recovery location. The restored content is loaded item by item in the playback order. After the restored content is loaded, the edge cloud Android instance is started. The application access is triggered sequentially along the two recovery paths to form the application access playback trajectory.

[0031] As a preferred embodiment of the edge cloud Android instance backup, distribution, and recovery method of the present invention, the step of segmenting and replaying the effective continuation segment is as follows:

[0032] The application access process in the two recovery paths is traced along the application access replay trajectory. The locations where the application access changes from a continuous state to an interrupted state and where the source identity and target identity deviate from the connection are marked as application access anomaly locations.

[0033] Around the location of the application access anomaly, trace backward to the location of continuous application access, and trace backward to the location of renewed application access. Extract the recovery and continuation content that can connect the application access before and after the anomaly location and whose identities are consistent, to form an effective continuation segment.

[0034] According to the order of application access anomalies, the valid segments are segmented and connected. At the isolation recovery position, the recovery connection content is loaded sequentially from the first valid segment to the last valid segment and the application access is triggered. Valid segments that still have the original application access anomalies and valid segments that cause new application access anomalies are filtered out, forming valid segments that pass closed replay and forming recovery connection content that passes closed replay.

[0035] According to the segmented continuation order of the effective continuation segments, the effective continuation segments that have been closed and replayed are connected to the formal application data location. The source identity inheritance recovery path, target identity reconstruction recovery path, application access anomaly location, effective continuation segments that have been closed and replayed, segmented continuation order, and backup task identifier are connected to the backup UUID to form a backup recovery lifecycle record.

[0036] In a second aspect, the present invention provides a computer device including a memory and a processor, wherein the memory stores a computer program, wherein: when the computer program is executed by the processor, it implements any step of the edge cloud Android instance backup, distribution and recovery method as described in the first aspect of the present invention.

[0037] Thirdly, the present invention provides a computer-readable storage medium having a computer program stored thereon, wherein: when the computer program is executed by a processor, it implements any step of the edge cloud Android instance backup, distribution and recovery method as described in the first aspect of the present invention.

[0038] The beneficial effects of this invention are as follows: by locating the backup boundary truncation position, constructing forward patching segments and reverse withdrawal segments, and performing bidirectional closed replay in the candidate backup temporary copy, the original state break and the newly added state break are synchronously checked, abnormal segments are screened out, and the retained segments are connected to the candidate backup range according to the replay order and the causal closed recovery position is marked, so that the cross-disk backup content is continuously connected, providing a closed and consistent backup basis for subsequent distribution, import and recovery, thereby reducing the risk of application access interruption and improving the continuity of cross-node recovery. Attached Figure Description

[0039] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the 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.

[0040] Figure 1 A flowchart illustrating the backup, distribution, and recovery method for edge cloud Android instances.

[0041] Figure 2 A flowchart for locating backup boundaries.

[0042] Figure 3 This is a flowchart for bidirectional closed playback.

[0043] Figure 4 This is a flowchart for restoring path playback. Detailed Implementation

[0044] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0045] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of the invention. Therefore, the invention is not limited to the specific embodiments disclosed below.

[0046] Secondly, the term "one embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it a single or selective embodiment that is mutually exclusive with other embodiments.

[0047] Reference Figures 1-4This is one embodiment of the present invention, which provides a method for backup, distribution and recovery of edge cloud Android instances, including the following steps:

[0048] S1: Receive the edge cloud Android instance backup request and establish the backup UUID and backup task identifier. Locate the content to be backed up based on the instance UUID, divide the backup location according to business ownership and storage undertaking relationship, verify the ownership of each backup location and fill in any missing parts, and form an Android instance backup object record.

[0049] S1.1: Receive the backup request for the edge cloud Android instance, extract the instance UUID, establish a backup UUID and a backup task identifier for the edge cloud Android instance backup request, and assign the backup UUID, backup task identifier and instance UUID to form a backup request mapping table.

[0050] The Edge Cloud Android Instance Backup Request is a request content used to specify an Edge Cloud Android instance and trigger a backup operation. The Edge Cloud Android Instance Backup Request carries the instance UUID.

[0051] Furthermore, after receiving an edge cloud Android instance backup request, the instance UUID is extracted from the edge cloud Android instance backup request. A backup UUID and a backup task identifier are generated for the same edge cloud Android instance backup request. The backup UUID is used to continue the corresponding backup content, and the backup task identifier is used to mark the backup process of the corresponding edge cloud Android instance backup request. In accordance with the receiving order of the edge cloud Android instance backup requests, the backup UUID, backup task identifier and instance UUID are written to the same corresponding position to form a backup request mapping table.

[0052] S1.2: Based on the backup request mapping table, locate the corresponding edge cloud Android instance according to the instance UUID, extract the content to be backed up along the existing content mounting location and storage receiving location of the edge cloud Android instance, remove the content that does not belong to the current edge cloud Android instance, and obtain the content to be backed up.

[0053] Furthermore, after receiving the edge cloud Android instance backup request, the instance UUID is extracted from the edge cloud Android instance backup request, and a backup UUID and a backup task identifier are generated for the edge cloud Android instance backup request respectively. The backup UUID, backup task identifier and instance UUID are written into the same corresponding position and arranged sequentially to form a backup request mapping table.

[0054] Then, the corresponding edge cloud Android instance is located according to the instance UUID in the backup request mapping table. The content is extracted item by item along the existing content mounting location and storage receiving location of the edge cloud Android instance. The correspondence between the extracted content and the instance UUID is verified. Content that does not belong to the current edge cloud Android instance is removed to obtain the content to be backed up.

[0055] It should be noted that the content mounting location is the location where the content to be backed up is connected to the edge cloud Android instance and made accessible to the edge cloud Android instance.

[0056] The storage succession location is the actual location where the content to be backed up is stored and is continuously connected according to the storage succession relationship.

[0057] S1.3: Determine the business affiliation of the content to be backed up, divide the backup locations according to the storage location and the direction of the backup, and assign the content to be backed up that has the same business affiliation and is handled by the same storage location to the corresponding backup location to form a backup location list.

[0058] Business attribution is determined by the location where the content to be backed up belongs to the edge cloud Android instance, and is used to distinguish the content to be backed up carried by different edge cloud Android instances.

[0059] The edge cloud Android instance is located by the instance UUID. The content mounting location of the content to be backed up is compared with the existing content mounting location of the edge cloud Android instance. The content to be backed up with the same content mounting location is marked as belonging to the same business. Then, the content to be backed up is arranged according to the storage location of the content to be backed up.

[0060] The backup direction is determined based on the sequential order of the content to be backed up in the storage location. Content with the same business affiliation, the same storage location, and a continuous backup direction is grouped into the same backup location. Content with different business affiliation, different storage locations, and discontinuous backup directions is grouped into different backup locations. The backup locations are arranged according to their sequential order to form a backup location list.

[0061] It should be noted that the storage continuity relationship is jointly carried by the content mounting position, storage continuity position, and sequential order of adjacent content to be backed up. When the end position of the previous content to be backed up can be connected to the start position of the next content to be backed up according to the content mounting position and storage continuity position, the storage continuity relationship between adjacent content to be backed up is considered continuous. When the end position of the previous content to be backed up cannot be connected to the start position of the next content to be backed up, the storage continuity relationship between adjacent content to be backed up is considered interrupted.

[0062] S1.4: Verify the ownership of the backup location list and fill in any missing parts. Retain backup locations with consistent business ownership and continuous storage succession. Fill in the missing backup content into the corresponding backup location and connect each backup location according to the backup UUID to form an Android instance backup object record.

[0063] Furthermore, based on the backup location list, the business affiliation and storage connection relationship are extracted item by item along each backup location. The backup content carried by the backup location is matched with the business affiliation marked in the previous step, and the continuity of the storage connection relationship is checked according to the order of the backup locations. Backup locations with consistent business affiliation and continuous storage connection relationship are retained.

[0064] For the reserved backup locations, the continuity of the backup content is checked item by item along the storage succession relationship. When there is a gap between the backup content, the backup content that is consistent with the business affiliation of the gap location and has a continuous storage succession relationship is extracted from the backup content obtained in the previous step. The extracted backup content is then added to the corresponding backup location. Each backup location is connected according to the backup UUID, and each backup location is arranged along the storage succession relationship so that the backup content carried by each backup location is continuously connected, forming an Android instance backup object record.

[0065] S2: Based on the Android instance backup object record, locate the backup boundary truncation position, construct forward patching segments and reverse rollback segments and define the candidate backup range, copy the content to be backed up within the candidate backup range to form a candidate backup temporary copy and perform bidirectional closed playback, filter out abnormal segments, and insert the retained segments into the candidate backup range according to the playback order, and mark the causal closure recovery position to form a causal closure consistent backup record.

[0066] S2.1: Based on the backup object record of the Android instance, extract the backup locations corresponding to the system disk content, data disk content and configuration content in the same edge cloud Android instance, and connect the previous backup location with the next backup location in sequence according to the mounting order and backup order of each item in the edge cloud Android instance to form a cross-disk connection chain.

[0067] The system disk contains the operating system files, basic runtime files, and startup files required for the edge cloud Android instance to start and run. The data disk contains application and business content stored independently of the system disk. The configuration content records the startup, content mounting, and application running configurations of the edge cloud Android instance.

[0068] Furthermore, the backup locations corresponding to the same edge cloud Android instance are extracted from the Android instance backup object record. The backup locations are arranged according to the mounting locations of the system disk content, data disk content, and configuration content in the edge cloud Android instance. Then, the adjacent relationships are checked item by item according to the backup order of each backup location. The backup location with the first content mounting location and the first backup order is marked as the previous backup location, and the backup location immediately following the previous backup location is marked as the next backup location.

[0069] Extract the end content of the previous backup location and the beginning content of the next backup location. Connect the end content of the previous backup location to the beginning content of the next backup location. Then, use the next backup location as the next backup location to continue the process until all backup locations are connected in sequence according to the content mounting location and backup order, forming a cross-disk connection chain.

[0070] It should be noted that the cross-disk continuation relationship is the continuation relationship between adjacent backup positions formed by the system disk content, data disk content, and configuration content in the same edge cloud Android instance according to the content mounting location and backup order. The cross-disk continuation chain is connected item by item according to adjacent backup positions and is used to locate the backup boundary truncation position between the end content of the previous backup position and the beginning content of the next backup position.

[0071] S2.2: Locate adjacent backup locations one by one along the cross-disk connection chain, extend the end content of the previous backup location to the next backup location, and reverse the start content of the next backup location back to the previous backup location. Locate the connection locations where there are still content gaps and where the content cannot be continuously connected by bidirectional boundary splicing, and mark them as backup boundary truncation locations.

[0072] Furthermore, following the order of backup positions in the cross-disk relay chain, starting from the first backup position, the current backup position and the next backup position immediately following the current backup position are selected sequentially. The current backup position is marked as the previous backup position, and the next backup position is marked as the next backup position. When there are no other backup positions between the current backup position and the next backup position, the previous backup position and the next backup position are positioned as adjacent backup positions.

[0073] Extract the end content of the previous backup location and the beginning content of the next backup location. Define the boundary check interval from the end boundary of the previous backup location to the beginning boundary of the next backup location. Extend the end content of the previous backup location to the next backup location item by item according to the continuation direction in the cross-disk continuation chain. At the same time, reconnect the beginning content of the next backup location to the previous backup location item by item according to the opposite continuation direction. Mark the forward extension coverage area, the reverse reconnection coverage area, and the overlapping part of the two coverage areas respectively.

[0074] Calculate the following expression: Content gap length corresponding to adjacent backup locations in the group:

[0075] ;

[0076] In the formula, Indicates the first The length of the content gap corresponding to adjacent backup locations in the group. This indicates the length of the boundary verification interval between the end boundary of the previous backup location and the start boundary of the next backup location. Indicates the length of the forward-extending coverage area. Indicates the length of the reverse reconnection coverage area. This indicates the length of the overlapping portion between the forward extension coverage and the reverse reconnection coverage. This indicates the sequence number of adjacent backup locations in the cross-disk relay chain. , , , and Use the same unit for byte length, storage block length, or logical offset length.

[0077] The length of the boundary verification interval is obtained based on the storage receiving position corresponding to the end boundary of the previous backup position and the start boundary of the next backup position. The length of the forward extension coverage range is obtained based on the range that the end content of the previous backup position can continuously extend to the next backup position. The length of the reverse reconnection coverage range is obtained based on the range that the start content of the next backup position can continuously reconnect to the previous backup position. The length of the overlapping part is obtained based on the storage receiving position jointly covered by the forward extension coverage range and the reverse reconnection coverage range.

[0078] When the content gap length is greater than zero, the position not covered by the forward extension coverage range and the reverse back-up coverage range is marked as the content gap position. When the content gap length is equal to zero, the connection relationship between the end content of the previous backup position and the beginning content of the next backup position is checked according to the storage connection relationship. When the end content of the previous backup position cannot be connected to the beginning content of the next backup position, the corresponding connection position is marked as the position where the content before and after cannot be connected continuously, and the content gap position and the position where the content before and after cannot be connected continuously are marked as the backup boundary truncation position.

[0079] It should be noted that the boundary verification interval is the storage coverage interval between the end boundary of the previous backup location and the start boundary of the next backup location used to perform bidirectional boundary splicing. The boundary verification interval carries the forward extension coverage range, the reverse reconnection coverage range, and the overlapping part of the two coverage ranges, and is used to calculate the length of the content gap that has not yet been covered between adjacent backup locations.

[0080] S2.3: Based on the backup boundary truncation position, backtrack to the previous continuous continuation position and construct a forward supplementary segment that crosses the truncation position. Track the backup content that continues to be inherited from the broken state, truncate it to the position of re-continuation and reverse the arrangement to construct a reverse withdrawal segment. Include the backup content before and after the two types of segments in the candidate backup range.

[0081] Furthermore, starting from the backup boundary truncation position, the backup content is traced back item by item along the cross-disk continuation chain. The continuation of adjacent backup content is checked according to the storage continuation relationship until adjacent backup content that can be continuously continuated is located. The corresponding continuation position is marked as the previous continuous continuation position. For the content gap position in the backup boundary truncation position, the backup content with the same business affiliation and that can respectively continuate the backup content before and after the gap position is extracted from the Android instance backup object record. The content gap position is then connected according to the storage continuation relationship. The backup content corresponding to the previous continuous continuation position, the backup boundary truncation position, and the starting position of the next backup position is extracted. The original continuation order of the backup content is maintained. The backup content after the previous continuous continuation position is connected to the backup boundary truncation position, and the backup content after the backup boundary truncation position is connected to the starting content of the next backup position, thus constructing a forward supplementary segment that crosses the backup boundary truncation position.

[0082] Starting from the backup boundary truncation point, trace back along the cross-disk continuation chain item by item from the broken state to the next backup content until a position is located where it can be reconnected with the subsequent backup content. Mark the backup content between the backup boundary truncation point and the reconnected position as the subsequent content of the broken state. Extract the backup position corresponding to the subsequent content of the broken state and arrange the subsequent content of the broken state and the corresponding backup position in the opposite direction of the cross-disk continuation chain to construct a reverse pullback segment. The reverse pullback segment is used to remove the subsequent content of the broken state item by item according to the corresponding backup position and the reverse arrangement order. Include the backup content before and after the forward patch segment and the reverse pullback segment in the candidate backup range.

[0083] It should be noted that the candidate backup range is the coverage area of ​​the content to be backed up around the backup boundary truncation position. The candidate backup range starts from the previous continuous continuation position and ends at the re-continuation continuation position. It carries the forward supplementary segments, the reverse withdrawal segments, and the content to be backed up before and after the backup boundary truncation position. It is used to form a temporary copy of the candidate backup and perform bidirectional closed playback.

[0084] S2.4: According to the candidate backup range, extract the content to be backed up before and after the backup boundary truncation position, retain the cross-disk connection position and continuation order and copy it to form a temporary copy of the candidate backup. Connect the forward supplementary segment along the cross-disk connection direction and perform forward closed playback. Move out the corresponding content to be backed up in the opposite direction according to the reverse withdrawal segment and perform reverse closed playback. Filter out segments that have not been repaired for the original state break and segments that have caused new state break. Continuate the retained segments according to the playback order to form a closed playback screening list.

[0085] Furthermore, according to the candidate backup range, the content to be backed up between the previous continuous connection position and the new continuous connection position is extracted, the cross-disk connection position and the sequence of the content to be backed up are retained, and the extracted content to be backed up is copied in the original arrangement to form a temporary copy of the candidate backup.

[0086] Along the cross-disk connection direction, the forward-connected segments are connected to the backup boundary truncation position. The fragments are then replayed from the previous continuous connection position to the reconnected position. In the opposite direction, the fragments are removed one by one in the order of the reverse withdrawal segments. The fragments are then replayed from the reconnected position to the previous continuous connection position. The original state fracture position, the repaired original state fracture position, and the newly added state fracture position are marked respectively.

[0087] Calculate the first segment in the forward append segment and the reverse retraction segment according to the following expression. Number of consecutive connection points after closed playback of a segment:

[0088] ;

[0089] In the formula, Indicates the first The number of consecutive positions after a segment is played back in closed loop. This indicates the total number of connection locations within the candidate backup range that participate in the storage succession relationship verification. This indicates the number of fracture locations in the original state before closed playback. This indicates the number of break points that allow for a continuous replay of the original state after a closed loop. This indicates the number of newly added break points where the playback transitions from continuous to interrupted after a closed playback. This indicates the sequence number of the segments participating in the two-way closed playback, with each item using the number of positions as the unit.

[0090] The total number of connection points is calculated item by item based on the connection points between adjacent contents to be backed up within the candidate backup range. The number of original state break points is calculated based on the location where the storage connection relationship was interrupted before bidirectional closed playback. The number of original state break points that have been repaired and the number of newly added state break points are calculated based on the changes in the storage connection relationship after the fragment is accessed or the content following the break is moved out.

[0091] When the number of consecutive receiving positions is the same as the total number of successive receiving positions, it indicates that the original state fracture has been completely repaired and no new state fracture has been caused. The corresponding segment is retained. When the number of consecutive receiving positions is less than the total number of successive receiving positions, the corresponding segment is filtered out, and the retained segment is connected with the corresponding playback sequence to form a closed playback screening list.

[0092] It should be noted that the original state break is the interruption of the existing storage continuity relationship at the backup boundary truncation position before bidirectional closed playback. The new state break is the interruption of the storage continuity relationship formed at the original continuous continuity position after the forward supplementary segment is connected or the subsequent content of the break is moved out. When the backup boundary truncation position is restored to continuous continuity after bidirectional closed playback, the original state break is considered to have been repaired. When the original continuous continuity position is interrupted, it is considered to have triggered a new state break.

[0093] S2.5: According to the playback order in the closed playback filter list, access the reserved forward supplementary segments and remove the broken subsequent content corresponding to the reserved reverse withdrawal segments. Continue the content to be backed up along the cross-disk connection relationship, mark the continuous connection position as the causal closure recovery position, and write the continued content to be backed up into the corresponding position of the backup UUID to form a causal closure consistent backup record.

[0094] Following the playback order in the closed playback filter list, starting from the previous consecutive continuation position of the candidate backup range, the retained forward supplementary segments are extracted item by item. The starting content of the forward supplementary segment is connected to the previous consecutive continuation position, and the ending content of the forward supplementary segment is connected to the backup content after the backup boundary truncation position, so that the forward supplementary segment crosses the backup boundary truncation position and connects the backup content before and after it.

[0095] Locate the reverse retraction segment coverage position according to the playback order. Following the reverse arrangement order of the reverse retraction segments, move out the broken subsequent content item by item from the re-continuous continuation position to the backup boundary truncation position. Then, connect the content to be backed up before and after the moved-out position adjacent to each other according to the cross-disk continuation relationship. Starting from the previous continuous continuation position along the cross-disk continuation relationship, connect the content to be backed up item by item. Mark the position where the forward supplementary segment is connected and the broken subsequent content is moved out as the causal closure recovery position. Write the connected content to be backed up into the corresponding position of the backup UUID according to the continuation order to form a causal closure consistent backup record.

[0096] It should be noted that the causal closure consistent backup record is a backup record formed after forward patching of segments, reverse withdrawal of segments, and continuation of cross-disk continuation relationship. The causal closure consistent backup record carries the backup content after continuation, the causal closure recovery location, the playback order, and the backup UUID correspondence. It is used to distribute the backup content according to the continuous continuation relationship and to connect the backup content to the corresponding causal closure recovery location.

[0097] S3: Distribute and import the backup content in the causal closed-loop consistency backup record, verify the consistency between the received content and the causal closed-loop recovery location, and encapsulate the received content that has passed the consistency verification according to the target node recovery interface requirements to form the target node recovery content package.

[0098] S3.1: Extract backup content along the causal closed-loop consistency backup record, extract the storage location from the backup location carried by the backup content and mark it as the source storage location, call the target node recovery interface to obtain the target storage location, and attach the causal closed-loop recovery location to the corresponding target storage location to form a backup distribution location chain.

[0099] Furthermore, the backup content is extracted item by item in the playback order of the causal closed-loop consistency backup record. The backup location of each backup content is found according to the backup UUID continuation relationship. The backup location has been divided according to the storage location of the content to be backed up. Therefore, the storage location carried by the backup location is directly extracted and the storage location is marked as the source storage location of the corresponding backup content.

[0100] For each backup item, the target node recovery interface is called. The storage location provided by the target node recovery interface is received item by item according to the order of the backup items in the playback sequence. The storage location provided by the target node recovery interface is connected with the corresponding backup item and marked as the target storage location, so that each backup item has a source storage location and a target storage location.

[0101] Extract the causal closure recovery location corresponding to each backup item from the causal closure consistency backup record. Attach the causal closure recovery location to the corresponding target storage location according to the backup UUID and playback order. Then, connect the source storage location, target storage location, and causal closure recovery location consecutively according to the order of the backup content to form a backup distribution location chain.

[0102] S3.2: Distribute and arrange the backup content along the backup distribution location chain according to the playback order in the causal closure consistency backup record, and connect each backup content with the source storage location, target storage location and causal closure recovery location to form a backup distribution sequence.

[0103] Starting from the first source storage location along the backup distribution location chain, the corresponding backup content is extracted item by item according to the playback order in the causal closed consistency backup record. The backup content is then arranged according to the playback order to ensure that the backup content after the forward patch fragment is added maintains the corresponding order and that the subsequent broken content after the reverse withdrawal fragment is removed does not enter the distribution arrangement, thus completing the distribution and arrangement of the backup content.

[0104] For each backup item after sorting, the backup item is first connected to the source storage location in the backup distribution location chain, and then linked to the corresponding target storage location along the backup distribution location. The causal closure recovery location attached to the target storage location is used as the connection location after the backup item is imported, so that each backup item corresponds to the source storage location, the target storage location and the causal closure recovery location respectively.

[0105] The backup contents and their corresponding locations are sequentially arranged according to the playback order, ensuring that the previous backup contents are distributed in a continuous order with the next backup contents. The backup contents, source storage location, target storage location, and causal closure recovery location are arranged in sequence to form a backup distribution sequence.

[0106] S3.3: Distribute the backup content from the source storage location to the target storage location according to the backup distribution sequence, and import it into the target storage location in the playback order to form the received content.

[0107] Furthermore, the source and target storage locations corresponding to the backup content are located one by one along the backup distribution sequence. The corresponding backup content is extracted from the source storage location and sent to the target storage location in the order of the backup distribution sequence. The next backup content is sent after the previous backup content is sent, so that the backup content maintains the sequential relationship in the playback order.

[0108] The target storage location receives backup content item by item according to the order of receipt, and writes the received backup content to the corresponding target storage location according to the playback order. The written backup content is then arranged in order so that adjacent backup content is received continuously in the playback order to form the received content.

[0109] It should be noted that the playback order is the order of operations retained in the bidirectional closed playback. First, the retained forward supplementary segments are connected along the cross-disk connection direction, and then the broken subsequent content corresponding to the retained reverse withdrawal segments is moved out along the opposite direction. Then, the remaining content to be backed up is continued along the cross-disk connection relationship to maintain the order of subsequent backup content distribution, import and restoration.

[0110] S3.4: According to the playback order, the received content is connected to the corresponding causal closure recovery position one by one. The adjacent received content is checked according to the connection relationship after the forward supplementary segment is connected and the reverse withdrawn segment is removed. The position of the received content that deviates from the order is adjusted and the order is continued to form the restored continuation content.

[0111] Furthermore, the received content is extracted item by item in the playback order, obtaining the starting offset of the first causal closure recovery position, the actual starting offset of each received content after being written to the target storage location, and the length occupied by the preceding received content. The length of the first received content is then calculated according to the following expression. Position adjustment offset of the received content:

[0112] ;

[0113] In the formula, Indicates the first Adjust the offset of the position of the received content. This indicates the initial offset of the first causal closure recovery position. Indicates the first The sequence number of the received content in the playback order. Indicates the position in the playback order. The first item before receiving content The length of the received content, Indicates the first The actual starting offset after the received content is written to the target storage location. Indicates the sequence number of the received content. Indicates that it is located at the th The sequence number of the received content preceding the item received. , , and Use the same unit for byte length, storage block length, or logical offset length.

[0114] The starting offset of the first causal closure recovery position is extracted from the causal closure consistency backup record, the sequence number is extracted from the playback order, the length of the received content is obtained according to the start and end positions of the corresponding received content, and the actual starting offset is extracted from the storage position corresponding to the received content after it is written to the target storage location.

[0115] The initial offset of the first causal closure recovery position is accumulated with the length occupied by each preceding received content to obtain the first... The starting offset that the received content should be accessed in the playback order is determined. When the position adjustment offset is equal to zero, the current access position of the received content is retained. When the position adjustment offset is greater than zero, the received content is adjusted in the direction of increasing logical offset. When the position adjustment offset is less than zero, the received content is adjusted in the direction of decreasing logical offset.

[0116] The received content that has deviated from its original order is reconnected according to the starting offset after the position adjustment, so that the end position of the previous received content is continuously connected to the starting position of the next received content. Then, all received content is sequentially connected along the causal closure recovery position to form the restored and continuous content.

[0117] S3.5: According to the target node recovery interface requirements, encapsulate the recovery continuation content, backup UUID, target storage location, causal closure recovery location, and playback order to form the target node recovery content package.

[0118] Furthermore, the recovery continuation content is extracted item by item in the playback order, and each recovery continuation content is continuated with the corresponding backup UUID, target storage location and causal closure recovery location, and continuously encapsulated in the receiving order specified by the target node recovery interface.

[0119] Before encapsulation, the starting offset of the restored continuation content after position adjustment is extracted, and the access starting offset of the corresponding causal closure restoration position in the target storage position is determined according to the playback order. The two starting offsets and the sequential relationship of adjacent restored continuation content are checked item by item. When the starting offsets are consistent and the end of the previous restored continuation content can be continuously connected to the starting position of the next restored continuation content, the corresponding restored continuation content is encapsulated to form the target node restored content package.

[0120] It should be noted that the target node recovery content package carries the recovery continuation content, backup UUID, target storage location, causal closure recovery location, and replay order. The source identity is jointly carried by the backup UUID and the causal closure recovery location, and the target identity is jointly carried by the target storage location and the replay order. When the two starting offsets are consistent and the adjacent recovery continuation content is continuously connected, the source identity and the target identity are considered to correspond consistently. When the starting offsets are inconsistent or the adjacent recovery continuation content cannot be continuously connected, the source identity and the target identity are considered to have deviated from the connection.

[0121] S4: Based on the target node recovery content package, define the isolation recovery location, construct the source identity inheritance recovery path and the target identity reconstruction recovery path respectively, and execute the start-up replay. Track application access anomalies and filter valid segments. Perform segmented continuation and closed replay on the valid segments. Connect the valid segments that have passed the closed replay to the formal application data location to form a backup and recovery lifecycle record.

[0122] S4.1: Perform source identity inheritance orchestration on the recovery continuation content in the target node recovery content package, and maintain the continuous continuation of the recovery continuation content corresponding to the same source identity according to the backup UUID and the causal closure recovery position, and construct the source identity inheritance recovery path.

[0123] Furthermore, the backup UUID and causal closure recovery position corresponding to each recovery continuation content are extracted from the recovery content package of the target node item by item. The start and end positions of each recovery continuation content are respectively attached to the corresponding causal closure recovery position. The same backup UUID is maintained from the first recovery continuation content to the last recovery continuation content, and the continuation order of the recovery continuation content is fixed according to the playback order to form a source identity inheritance recovery path.

[0124] S4.2: Perform target identity reconstruction and orchestration on the restored content, reconnect the restored content according to the target storage location and target node recovery interface, construct the target identity reconstruction recovery path, connect the two recovery paths to the isolated recovery location, and load the restored content item by item in the playback order. After the restored content is loaded, start the edge cloud Android instance, trigger application access along the two recovery paths in sequence, and form an application access playback trajectory.

[0125] Furthermore, the target storage location and playback order corresponding to each recovery continuation content are extracted from the target node recovery content package. The target storage location and playback order are marked as the target identity of the recovery continuation content. The recovery continuation content is reconstructed and arranged according to the target identity. The recovery continuation content is then reconnected according to the target storage location and target node recovery interface to construct the target identity reconstruction recovery path.

[0126] The source identity inheritance recovery path and the target identity reconstruction recovery path are respectively connected to the isolated recovery location. The recovery continuation content is loaded item by item along the two recovery paths in the playback order. After the recovery continuation content is loaded, the edge cloud Android instance is started. First, the application access is triggered along the source identity inheritance recovery path, and then the application access is triggered along the target identity reconstruction recovery path. The application access locations are connected in the order of application access triggering to form the application access playback trajectory.

[0127] It should be noted that the application access replay trajectory is an access process record formed by sequentially triggering application access along the source identity inheritance recovery path and the target identity reconstruction recovery path after the edge cloud Android instance starts up, in the order of replay. It is used to locate the application access interruption point and the position where the source identity and target identity deviate from each other.

[0128] The isolated recovery location is a recovery location separated from the formal application data location from the target storage location. It is used to load recovery continuation content, start the edge cloud Android instance, and trigger application access. The recovery continuation content in the isolated recovery location is then connected to the formal application data location after closed playback.

[0129] S4.3: Track the application access process in the two recovery paths along the application access replay trajectory, and mark the positions where the application access changes from continuous to interrupted state and the positions where the source identity and target identity deviate as application access anomaly positions.

[0130] Furthermore, following the playback order in the application access playback trajectory, the application access process in the source identity inheritance recovery path and the target identity reconstruction recovery path is tracked respectively. Starting from the first recovery continuation content, each item is checked to see if the application access to the previous recovery continuation content can continue after the application access is completed. This ensures that the application access process proceeds according to the continuation order of the recovery continuation content. When the application access to the previous recovery continuation content can be completed but the application access to the next recovery continuation content cannot continue according to the playback order, the continuation position where the application access changes from a continuous state to an interrupted state is marked as the application access interruption position, and the application access playback trajectory is continued to be tracked until the application access becomes continuous again.

[0131] According to the causal closure recovery position, each item corresponds to the recovery continuation content in the source identity inheritance recovery path and the target identity reconstruction recovery path. The source identity maintained in the source identity inheritance recovery path and the target identity continued in the target identity reconstruction recovery path are checked for the same recovery continuation content. When the source identity and target identity cannot be continuously matched, it is marked as an identity continuation deviation position. The application access interruption position and the identity continuation deviation position are marked as application access abnormal positions. The application access abnormal position includes the application access interruption position and the identity continuation deviation position. The application access interruption position is used to indicate the continuation position where the previous recovery continuation content can trigger application access but the subsequent recovery continuation content cannot continue to trigger application access in the replay order. The identity continuation deviation position is used to indicate the position where the source identity and target identity corresponding to the same recovery continuation content cannot maintain a consistent correspondence.

[0132] S4.4: Based on the abnormal application access location, backtrack to the continuous application access location and trace to the re-continuation of application access location. Extract the recovery continuation content that can inherit the application access before and after the abnormal location and whose identity is consistent, to form an effective continuation segment.

[0133] Furthermore, focusing on the abnormal application access location, the system traces back item by item along the application access playback trajectory to restore the continuous content, and verifies whether adjacent restored continuous content can trigger application access continuously in the playback order, until the position where application access remains continuous is located, and the position where application access remains continuous is taken as the stop position for forward tracing.

[0134] Starting from the location of the application access anomaly, trace back along the application access playback trajectory to restore the continuous content item by item. Check whether the application access after the interruption can be triggered continuously in the playback order until the location of the application access re-continuity is located, and use the re-continuity location of the application access as the stop position for tracing backward.

[0135] Extract the recovery continuation content between the continuous application access position and the re-continuous application access position. According to the source identity, inherit the recovery path and reconstruct the recovery path. Verify the identity correspondence of the recovery continuation content. Retain the recovery continuation content that can take over the application access before and after the abnormal application access position and whose source identity and target identity correspond to the same. Then, continue the continuation in the replay order to form a valid continuation segment.

[0136] S4.5: Segment the valid access segments according to the order of application access anomaly locations. At the isolation recovery location, load the recovery continuation content sequentially from the first valid access segment to the last valid access segment and trigger application access. Filter out valid access segments that still have the original application access anomaly and valid access segments that cause new application access anomalies, forming valid access segments that pass closed replay and forming recovery continuation content that passes closed replay.

[0137] Based on the order of application access anomaly locations in the application access replay trajectory, each valid segment is arranged sequentially. Valid segments between the previous continuous application access location and the next re-continuous application access location are grouped into the same continuation part, and then each continuation part is sequentially connected according to the arrangement order. Starting from the first valid segment, the recovery continuation content carried by the valid segment is loaded to the isolation recovery location in the replay order. Application access is triggered along the valid segment from the continuous application access location, passing through the application access anomaly location and continuing to the re-continuous application access location. Subsequent valid segments are then loaded and replayed in the same manner.

[0138] Verify whether the original application access anomaly can be eliminated after replaying each valid segment, and check for any new application access anomalies along the continuation positions before and after the valid segments. Filter out valid segments that still have the original application access anomaly and valid segments that caused new application access anomalies. Mark the remaining valid segments as valid segments that have passed closed replay. According to the segment continuation order of the valid segments, extract the recovery continuation content carried by the valid segments that have passed closed replay. Continuously concatenate the end of the previous recovery continuation content with the start position of the next recovery continuation content to form the recovery continuation content that has passed closed replay.

[0139] S4.6: According to the segmented continuation order of the effective continuation segments, the effective continuation segments that have been closed and replayed are connected to the formal application data location, and the source identity inheritance recovery path, target identity reconstruction recovery path, application access anomaly location, effective continuation segments that have been closed and replayed, segmented continuation order, and backup task identifier are connected to the backup UUID to form a backup recovery lifecycle record.

[0140] Furthermore, following the segmented continuation sequence of the effective successor segments, starting from the first effective successor segment that has passed closed replay, the recovery continuation content carried by the effective successor segment that has passed closed replay is connected to the formal application data location. Then, the next effective successor segment that has passed closed replay is connected to the end of the previous effective successor segment that has passed closed replay, until all effective successor segments that have passed closed replay have been connected.

[0141] Based on the backup UUID, the source identity is inherited and the target identity is reconstructed for recovery. Then, the application access anomaly location is continued along the application access replay trajectory. The effective segments that pass through the closed replay are arranged in the segmented continuation order of the effective segments. The backup task identifier corresponding to the backup UUID is extracted from the backup request mapping table and the backup task identifier is continued to the corresponding backup UUID position. This allows the backup UUID to continuously inherit the backup task identifier, the two recovery paths, the application access anomaly location, and the effective segments that pass through the closed replay, forming a backup recovery lifecycle record.

[0142] It should be noted that the backup and recovery lifecycle record is a recovery process record formed according to the backup UUID succession source identity inheritance recovery path, target identity reconstruction recovery path, application access anomaly location, effective continuation segment through closed replay, and segmented continuation sequence. It is used to track the complete process of recovery continuation content from identity inheritance, identity reconstruction, application access anomaly screening to access of formal application data location.

[0143] The formal application data location is the location where the application access to restore the continuous content is provided when the edge cloud Android instance is running normally. After the effective segment of the closed playback is connected to the formal application data location, it is used for the formal application access of the edge cloud Android instance.

[0144] This embodiment also provides a computer device applicable to the edge cloud Android instance backup, distribution and recovery method, including: a memory and a processor; the memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions to implement the edge cloud Android instance backup, distribution and recovery method proposed in the above embodiment.

[0145] The computer device can be a terminal, comprising a processor, memory, communication interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, carrier networks, NFC (Near Field Communication), or other technologies. The display screen can be an LCD screen or an e-ink screen. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad on the computer device's casing, or an external keyboard, touchpad, or mouse.

[0146] This embodiment also provides a storage medium storing a computer program that, when executed by a processor, implements the edge cloud Android instance backup, distribution, and recovery method proposed in the above embodiments. The storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, disk, or optical disk.

[0147] In summary, this invention achieves synchronous verification of original state breaks and newly added state breaks by: locating the backup boundary truncation position, constructing forward patching segments and reverse pullback segments, and performing bidirectional closed replay in the candidate backup temporary copy, thereby filtering out abnormal segments, and inserting the remaining segments into the candidate backup range according to the replay order and marking the causal closed recovery position. This ensures the continuous continuation of cross-disk backup content, providing a closed and consistent backup foundation for subsequent distribution, import, and recovery, thus reducing the risk of application access interruption and improving the continuity of cross-node recovery.

[0148] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A method for backup, distribution, and recovery of Android instances in an edge cloud, characterized in that, include: Receive edge cloud Android instance backup requests and establish backup UUID and backup task identifier. Locate the content to be backed up based on the instance UUID, divide the backup location according to business ownership and storage undertaking relationship, verify the ownership of each backup location and fill in any missing parts, and form an Android instance backup object record. Based on the Android instance backup object record, locate the backup boundary truncation position, construct forward patching segments and reverse rollback segments and define the candidate backup range, copy the content to be backed up within the candidate backup range to form a candidate backup temporary copy and perform bidirectional closed playback, filter out abnormal segments, and insert the remaining segments into the candidate backup range according to the playback order, and mark the causal closure recovery position to form a causal closure consistent backup record. The backup content in the causal closed-loop consistency backup record is distributed and imported. The consistency of the received content with the causal closed-loop recovery location is checked. The received content that has passed the consistency check is encapsulated according to the recovery interface requirements of the target node to form the target node recovery content package. Based on the target node recovery content package, the isolation recovery location is defined, and the source identity inheritance recovery path and the target identity reconstruction recovery path are constructed and executed for startup replay. Application access anomalies are tracked and valid segments are selected. The valid segments are segmented and replayed in a closed loop. The valid segments that have passed the closed loop replay are connected to the formal application data location to form a backup and recovery lifecycle record.

2. The edge cloud Android instance backup, distribution, and recovery method as described in claim 1, characterized in that, The process of locating the content to be backed up based on the instance UUID is as follows: Receive an edge cloud Android instance backup request, extract the instance UUID, create a backup UUID and backup task identifier for the edge cloud Android instance backup request, and associate the backup UUID, backup task identifier and instance UUID to form a backup request mapping table; Based on the backup request mapping table, the corresponding edge cloud Android instance is located according to the instance UUID. The content to be backed up is extracted along the existing content mounting location and storage receiving location of the edge cloud Android instance. Content that does not belong to the current edge cloud Android instance is removed to obtain the content to be backed up.

3. The edge cloud Android instance backup, distribution, and recovery method as described in claim 2, characterized in that, The process of creating the Android instance backup object record is as follows: The business affiliation of the content to be backed up is identified, and the backup locations are divided according to the storage location and the direction of the backup content. The content to be backed up that has the same business affiliation and is handled by the same storage location is assigned to the corresponding backup location to form a backup location list. The backup location list is checked for ownership and missing items are filled in. Backup locations with consistent business ownership and continuous storage succession are retained. Missing backup content is filled into the corresponding backup location, and each backup location is connected according to the backup UUID to form an Android instance backup object record.

4. The edge cloud Android instance backup, distribution, and recovery method as described in claim 3, characterized in that, The construction of the forward patching segment and the reverse withdrawal segment is as follows: Based on the backup object record of the Android instance, the backup locations corresponding to the system disk content, data disk content and configuration content in the same edge cloud Android instance are extracted. According to the mounting order and backup order of each item in the edge cloud Android instance, the previous backup location is sequentially connected with the next backup location to form a cross-disk connection chain. The adjacent backup positions are located one by one along the cross-disk connection chain. The end content of the previous backup position is extended to the next backup position, and the beginning content of the next backup position is reversed and connected back to the previous backup position. The connection positions where there are still content gaps and the connection positions where the content cannot be connected continuously are located by bidirectional boundary splicing, and these are marked as backup boundary truncation positions. Based on the backup boundary truncation position, backtrack to the previous continuous continuation position and construct a forward supplementary segment that crosses the truncation position. Then, track the backup content that continues from the broken state, truncate it to the position of re-continuation and reverse the arrangement to construct a reverse withdrawal segment. The backup content before and after the two types of segments are included in the candidate backup range.

5. The edge cloud Android instance backup, distribution, and recovery method as described in claim 4, characterized in that, The content to be backed up within the candidate backup range is copied to form a temporary copy of the candidate backup and a two-way closed replay is performed to filter out abnormal segments, as follows: According to the candidate backup range, the backup content before and after the backup boundary cutoff position is extracted, the cross-disk connection position and the continuation order are retained and copied to form a temporary copy of the candidate backup. The forward supplementary segment is connected along the cross-disk connection direction and the forward closed playback is performed. The corresponding backup content is removed along the opposite direction according to the reverse withdrawal segment and the reverse closed playback is performed. The segments that have not been repaired in the original state and those that have caused new state breaks are screened out. The retained segments are continuated in the playback order to form a closed playback screening list. Following the playback order in the closed playback filter list, the retained forward patch segments are accessed and the broken subsequent content corresponding to the retained reverse withdrawal segments is removed. The content to be backed up is continued along the cross-disk connection relationship. The continuous connection position is marked as the causal closure recovery position, and the continued content to be backed up is written to the corresponding position of the backup UUID to form a causal closure consistent backup record.

6. The edge cloud Android instance backup, distribution, and recovery method as described in claim 5, characterized in that, The formation of the target node recovery content package is as follows: The backup content is extracted along the causal closed-loop consistency backup record. The storage location is extracted from the backup location carried by the backup content and marked as the source storage location. The target node recovery interface is called to obtain the target storage location. The causal closed-loop recovery location is attached to the corresponding target storage location to form a backup distribution location chain. Along the backup distribution location chain, the backup content is distributed and arranged according to the playback order in the causal closure consistency backup record, and each backup content is connected to the source storage location, target storage location and causal closure recovery location to form a backup distribution sequence; According to the backup distribution sequence, the backup content is distributed from the source storage location to the target storage location, and imported into the target storage location in the playback order to form the received content; According to the playback order, the received content is connected to the corresponding causal closure recovery position one by one. The adjacent received content is checked according to the connection relationship after the forward supplementary segment is connected and the reverse withdrawn segment is removed. The position of the received content that deviates from the order is adjusted and the sequence is continued to form the restored continuation content. According to the target node recovery interface requirements, the recovery continuation content, backup UUID, target storage location, causal closure recovery location, and playback order are encapsulated to form the target node recovery content package.

7. The edge cloud Android instance backup, distribution, and recovery method as described in claim 6, characterized in that, The execution of the replay is as follows: The source identity inheritance of the recovery continuation content in the recovery content package of the target node is performed. The recovery continuation of the recovery continuation content corresponding to the same source identity is maintained according to the backup UUID and the causal closure recovery position, and the source identity inheritance recovery path is constructed. The target identity is reconstructed and orchestrated for the restored content. The restored content is reconnected according to the target storage location and the target node recovery interface. The target identity reconstruction recovery path is constructed. The two recovery paths are connected to the isolated recovery location. The restored content is loaded item by item in the playback order. After the restored content is loaded, the edge cloud Android instance is started. The application access is triggered sequentially along the two recovery paths to form the application access playback trajectory.

8. The edge cloud Android instance backup, distribution, and recovery method as described in claim 7, characterized in that, The segmented continuation and closed replay of the effective connecting segments are as follows: The application access process in the two recovery paths is traced along the application access replay trajectory. The locations where the application access changes from a continuous state to an interrupted state and where the source identity and target identity deviate from the connection are marked as application access anomaly locations. Around the location of the application access anomaly, trace backward to the location of continuous application access, and trace backward to the location of renewed application access. Extract the recovery and continuation content that can connect the application access before and after the anomaly location and whose identities are consistent, to form an effective continuation segment. According to the order of application access anomalies, the valid segments are segmented and connected. At the isolation recovery position, the recovery connection content is loaded sequentially from the first valid segment to the last valid segment and the application access is triggered. Valid segments that still have the original application access anomalies and valid segments that cause new application access anomalies are filtered out, forming valid segments that pass closed replay and forming recovery connection content that passes closed replay. According to the segmented continuation order of the effective continuation segments, the effective continuation segments that have been closed and replayed are connected to the formal application data location. The source identity inheritance recovery path, target identity reconstruction recovery path, application access anomaly location, effective continuation segments that have been closed and replayed, segmented continuation order, and backup task identifier are connected to the backup UUID to form a backup recovery lifecycle record.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the edge cloud Android instance backup, distribution and recovery method according to any one of claims 1 to 8.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the edge cloud Android instance backup, distribution and recovery method according to any one of claims 1 to 8.

Images