Data synchronization method and file system
By deploying the main cloud storage node and backup cloud storage node on the cloud storage node, and using full snapshots and file logs to achieve asynchronous data replication, the problem of data synchronization solutions in the existing technology requires installation of additional software and interruption of business operations, and improves the problem of data synchronization solutions in the existing technology. Data access experience and operation ease.
Patent Information
- Application Number
- CN202311103648.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-05-16
- Filing Date
- 2023-08-30
- Publication Date
- 2024-11-22
AI Technical Summary
The existing data synchronization solution requires the installation of additional data copy software and needs to interrupt the operation of business personnel in copying data, resulting in poor data access experience and unable to effectively meet users' disaster recovery needs.
By deploying the primary cloud storage node and backup cloud storage node on the cloud storage node, using full snapshots and file logs to achieve asynchronous data replication, ensuring that the data replication process does not affect business operations, and there is no need to install proprietary data copy software, reducing technology Complexity.
It improves the convenience of data synchronization operations and the data access experience of business personnel, ensuring that the data replication process is transparent to business personnel and does not require advanced software usage capabilities.
Smart Images

Figure CN119002794A_ABST
Abstract
Description
[0001] This application claims priority to a Chinese patent application filed with the China Patent Office on May 16, 2023, with application number 202310552745.8 and application name “A method, device and other equipment for data synchronization”, the entire contents of which are incorporated by reference in this application. Technical Field
[0002] The present application relates to the technical field of cloud computing, and in particular to a data synchronization method and a file system. Background Art
[0003] With the popularization of cloud computing, users' demand for data disaster recovery is gradually increasing. At present, in order to meet users' data disaster recovery needs, one data synchronization solution is: before synchronizing data, the data synchronization personnel first install the data copy software on the terminal device used; when the data copy software is installed, the data synchronization personnel can complete the data synchronization by operating the data copy software according to the data synchronization requirements. However, this data synchronization solution requires the data synchronization personnel to install additional data copy software on the terminal device, and requires the data synchronization personnel to have certain software usage capabilities. In addition, during the process of copying data, this data synchronization solution needs to interrupt the business personnel (such as data access users) from performing related operations on the copied data (such as viewing, modifying or writing the copied data), which makes the data access experience of the business personnel poor.
[0004] Therefore, the current data synchronization solution cannot meet the users' disaster recovery needs well and needs further research. Summary of the invention
[0005] The present application provides a data synchronization method and a file system to effectively improve the convenience of data synchronization operations and improve the data access experience of business personnel.
[0006] In a first aspect, the present application provides a data synchronization method, which is used for a file system, and the file system is deployed on at least one cloud storage node, and the at least one cloud storage node includes a primary cloud storage node and at least one backup cloud storage node, and the at least one backup cloud storage node and the primary cloud storage node are respectively deployed in different availability zones, and the different availability zones are located in the same area or in different areas. Exemplarily, the cloud storage node can be a computing device (or a computing device cluster) having the functions required to implement the method, or it can also be a functional element (such as a plug-in, component, chip or circuit, etc.) in a computing device (or a computing device cluster) having the functions required to implement the method, or it can also be any other device having the functions required to implement the method. Among them, the method may include the following steps:
[0007] The primary cloud storage node first creates a full snapshot of the file system of the primary cloud storage node, and can provide the full snapshot of the file system to the target cloud storage node, wherein the target cloud storage node and the primary cloud storage node are deployed in the same availability zone in the same region. Afterwards, the backup cloud storage node can asynchronously obtain the file data of the full snapshot from the target cloud storage node. When the file of the file system is updated, the primary cloud storage node can obtain the file log, wherein the file log is used to record the updated file data in the file system. Then, the backup cloud storage node can synchronously obtain the file log from the primary cloud storage node, and can update the file data corresponding to the file log in the file system of the backup cloud storage node.
[0008] In this method, after the primary cloud storage node provides the target cloud storage node with a full snapshot of the file system of the primary cloud storage node, the backup cloud storage node can asynchronously obtain the file data in the file system of the primary cloud storage node from the target cloud storage node, so as to ensure that the data replication of the file system of the primary cloud storage node will not affect or interrupt the business personnel (or other personnel who need to use the primary cloud storage node) related operations on the file system of the primary cloud storage node (such as viewing, modifying or writing data to the file data in the file system), so that the business personnel (or other personnel who need to use the primary cloud storage node) can effectively improve the data access experience of the primary cloud storage node, and ensure that the business personnel (or other personnel who need to use the primary cloud storage node) will not perceive the data replication process during the use of the primary cloud storage node. In addition, the method can complete the data replication of the file system of the primary cloud storage node through the interaction between the backup cloud storage node and the target cloud storage node, without the need to install proprietary data copy software, and without the need for data synchronization personnel to have certain software usage capabilities, so that data synchronization operations can be made more convenient.
[0009] In a possible design, the backup cloud storage node asynchronously obtains file data of a full snapshot from the target cloud storage node, including: the backup cloud storage node may first send a first request to the target cloud storage node, wherein the first request is used to request to obtain attribute information of a root directory, wherein the attribute information of the root directory includes at least one sub-item located at the next level of the root directory, and after receiving the attribute information of the root directory from the target cloud storage node, the backup cloud storage node may traverse the at least one sub-item in sequence, and when it is determined that the type of the traversed target sub-item is a directory, the backup cloud storage node may send a second request to the target cloud storage node, wherein the second request is used to request to obtain attribute information of the target sub-item, and after receiving the attribute information of the target sub-item from the target cloud storage node, the backup cloud storage node may traverse the at least one sub-item included in the attribute information of the target sub-item in sequence, or, when it is determined that the type of the traversed target sub-item is a file, the backup cloud storage node may send a third request to the target cloud storage node, wherein the third request is used to request to obtain file data corresponding to the target sub-item, and the backup cloud storage node may receive file data corresponding to the target sub-item from the target cloud storage node.
[0010] In the above design, the backup cloud storage node interacts with the target cloud storage node multiple times by adopting data interaction (or information interaction), and can effectively copy the file data of the file system of the primary cloud storage node from the target cloud storage node in full.
[0011] In one possible design, the backup cloud storage node asynchronously obtains file data of the full snapshot from the target cloud storage node, including: the backup cloud storage node can first send a fourth request to the target cloud storage node, wherein the fourth request is used to request to obtain a multi-branch tree of the target cloud storage node, and the multi-branch tree is constructed according to the directory identifier and the file identifier included in the full snapshot of the file system of the primary cloud storage node. After receiving the multi-branch tree from the target cloud storage node, the backup cloud storage node can use the root node of the multi-branch tree as the starting point of data traversal to obtain the file data of the full snapshot from the target cloud storage node without affecting the business personnel (or other personnel who need to use the primary cloud storage node) related operations on the file system of the primary cloud storage node, thereby improving the data access experience of the business personnel (or other personnel who need to use the primary cloud storage node).
[0012] In the above design, the backup cloud storage node can timely and accurately complete the full replication of file data of the file system of the primary cloud storage node by recursively traversing the multi-branch tree obtained from the target cloud storage node.
[0013] In one possible design, the backup cloud storage node asynchronously obtains file data of a full snapshot from a target cloud storage node, including: the backup cloud storage node may first send a fifth request to the target cloud storage node, wherein the fifth request is used to request the target cloud storage node to use the root directory of the target cloud storage node as a data traversal starting point, and to traverse the file data of the full snapshot of the file system of the primary cloud storage node in sequence; thereafter, the backup cloud storage node may receive the file data of the full snapshot from the target cloud storage node in sequence according to the traversal order of the file data of the full snapshot.
[0014] In the above design, the backup cloud storage node sends an indication request to the target cloud storage node, so that the target cloud storage node takes the root directory as the starting point of data traversal, and accurately and completely sends the traversed file data to the backup cloud storage node in sequence, so that the backup cloud storage node can store the file data in the traversal order, so that the backup cloud storage node can fully obtain the file data in the full snapshot, thereby avoiding missing file data in the full snapshot and helping to ensure the integrity of data replication.
[0015] In one possible design, the backup cloud storage node updates file data corresponding to a file log in a file system of the backup cloud storage node, including: the backup cloud storage node can read the file log obtained from the primary cloud storage node, and obtain the file identifier and the update operation corresponding to the file identifier included in the file log, wherein the file identifier is used to identify the file; thereafter, the backup cloud storage node can determine whether the file data corresponding to the file identifier exists in the file system of the backup cloud storage node; when the file data corresponding to the file identifier exists in the file system of the backup cloud storage node, the backup cloud storage node can update the file data corresponding to the file identifier in the file system of the backup cloud storage node according to the update operation corresponding to the file identifier; when the file data corresponding to the file identifier does not exist in the file system of the backup cloud storage node, the backup cloud storage node can obtain the file data corresponding to the file identifier from the target cloud storage node, and can update the file data corresponding to the file identifier according to the update operation corresponding to the file identifier.
[0016] In the above design, the backup cloud storage node can timely update the corresponding file data in the file system of the backup cloud storage node based on the file log from the primary cloud storage node, thereby ensuring that the file data stored in the file system of the backup cloud storage node is consistent with the file data stored in the file system of the primary cloud storage node.
[0017] In one possible design, after the backup cloud storage node asynchronously obtains the file data of the full snapshot from the target cloud storage node, it may also send an indication message to the target cloud storage node, so that the target cloud storage node can promptly delete the full snapshot in the target cloud storage node according to the indication message, which helps to release the cache of the target cloud storage node so that the target cloud storage node can store full snapshots of other file systems, wherein the indication message can be used to indicate that the file data synchronization of the full snapshot in the target cloud storage node is complete, or the indication message can also be used to instruct the target cloud storage node to delete the full snapshot.
[0018] In the second aspect, the present application provides a possible file system. Optionally, the file system can be deployed on at least one cloud storage node, and the at least one cloud storage node can include a primary cloud storage node and at least one backup cloud storage node. The at least one backup cloud storage node can be deployed in different availability zones from the primary cloud storage node, and different availability zones can be located in the same region or in different regions. Wherein, when at least one cloud storage node is used to implement the function corresponding to the behavior of the cloud storage node in the method example of the first aspect above, the beneficial effects can be referred to the corresponding description in the first aspect above, and will not be repeated here. The function can be implemented by hardware, or by hardware executing the corresponding software implementation. The hardware or software may include one or more modules (or units) corresponding to the above functions. In a possible design, the primary cloud storage node is used to create a full snapshot of the file system of the primary cloud storage node, and is also used to provide a full snapshot to the target cloud storage node, wherein the target cloud storage node and the primary cloud storage node are deployed in the same availability zone in the same region. The backup cloud storage node is used to asynchronously obtain the file data of the full snapshot from the target cloud storage node. The primary cloud storage node is also used to obtain a file log when the file of the file system of the primary cloud storage node is updated, wherein the file log records the file data updated in the file system. The backup cloud storage node is also used to synchronously obtain the file log from the primary cloud storage node, and is also used to update the file data corresponding to the file log in the file system of the backup cloud storage node. These cloud storage nodes can perform the corresponding functions in the first aspect above, and the detailed description in the method example is specifically referred to, which will not be repeated here.
[0019] In a third aspect, the present application provides a possible computing device, which has the function of implementing the behavior of the cloud storage node (such as a primary cloud storage node, a backup cloud storage node, or a target cloud storage node) in the method example of the first aspect above. The beneficial effects can be found in the description of the first aspect and will not be repeated here. The computing device includes a communication interface, a memory, and a processor. Among them, the communication interface is used to communicate with other devices, the memory is used to store computer programs or instructions, and the processor is coupled to the memory and the communication interface. When the processor executes the computer program or instructions, the computing device executes the method in any possible design of the first aspect above.
[0020] In a fourth aspect, the present application provides a possible computing device cluster, which has the function of implementing the behavior of the cloud storage node (such as a primary cloud storage node, a backup cloud storage node, or a target cloud storage node) in the method example of the first aspect above. The beneficial effects can be found in the description of the first aspect and will not be repeated here. The computing device cluster includes at least one computing device, any computing device includes a communication interface, a processor, and a memory, and the processor in any computing device is configured to support the cloud storage node (such as a primary cloud storage node, a backup cloud storage node, or a target cloud storage node) to perform part or all of the functions of the method in any possible design of the first aspect above. The memory is coupled to the processor, which stores the necessary computer program instructions and data of the cloud storage node (such as a primary cloud storage node, a backup cloud storage node, or a target cloud storage node).
[0021] In a fifth aspect, the present application provides a computer-readable storage medium, which stores computer program instructions. When the computer program instructions are executed by a computing device, the computing device executes the method in any possible design of the first aspect above.
[0022] In a sixth aspect, the present application provides a computer program product comprising instructions, which, when executed on a computing device, enables the computing device to execute a method in any possible design of the first aspect described above.
[0023] In a seventh aspect, the present application further provides a computer chip, which is coupled to a memory, and is used to read a computer program stored in the memory to execute a method in any possible design of the first aspect above.
[0024] In an eighth aspect, the present application further provides a chip system, the chip system comprising a processor for supporting a computer device to implement the method in any possible design of the first aspect. In one possible design, the chip system further comprises a memory, the memory being used to store the necessary programs and data of the computer device. The chip system may be composed of a computer chip, or may include a computer chip and other discrete devices.
[0025] Based on the implementations provided in the above aspects, the present application can also be further combined to provide more implementations. BRIEF DESCRIPTION OF THE DRAWINGS
[0026] Figure 1 A schematic diagram of a possible application scenario provided by an embodiment of the present application is exemplified;
[0027] Figure 2 A schematic diagram exemplarily illustrates a flow chart of a data synchronization method provided in an embodiment of the present application;
[0028] Figure 3 A schematic diagram of a multi-branch tree provided in an embodiment of the present application is exemplarily shown;
[0029] Figure 4 A schematic diagram showing a possible structure of a file system provided by an embodiment of the present application is exemplified;
[0030] Figure 5 A schematic diagram showing a possible structure of a computing device provided by an embodiment of the present application is exemplified;
[0031] Figure 6 A schematic diagram showing a possible computing device cluster structure provided by an embodiment of the present application is exemplified;
[0032] Figure 7 A schematic diagram illustrating the structure of another possible computing device cluster provided in an embodiment of the present application is exemplified. DETAILED DESCRIPTION
[0033] Before introducing the technical solution provided by the present application, some of the terms involved in the present application are first explained to facilitate understanding by those skilled in the art.
[0034] It should be noted that in the description of the present application, "at least one" refers to one or more, and "multiple" refers to two or more. "And / or" describes the association relationship of the associated objects, indicating that there may be three relationships, for example, A and / or B, which can represent: the situation where A exists alone, A and B exist at the same time, and B exists alone, wherein A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are an "or" relationship. "At least one of the following (individuals)" or its similar expression refers to any combination of these items, including any combination of single items (individuals) or plural items (individuals). For example, "at least one of A, B and C" includes A, B, C, AB, AC, BC or ABC. And, unless otherwise specified, the ordinal numbers such as "first", "second", and "third" mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the order, timing, priority or importance of multiple objects. In addition, the terms "including", "comprising", "having" and their variations appearing in the present application all mean "including but not limited to", unless otherwise specifically emphasized in other ways.
[0035] (1) Snapshot: A fully available copy of a specified data set, which includes an image of the corresponding data at a certain point in time (the time when the copy starts). A snapshot can record the data of a storage device at a certain point in time without affecting the data reading and writing of the storage device. Therefore, snapshot technology is used in backup, data analysis, application testing, etc.
[0036] (2) File: An independent logical linear space used to store user data, occupying data space.
[0037] (3) Directory: It is an entity that collects files and identifies parent-child relationships.
[0038] (4) Region: Based on the geographical location and network latency, the same region shares public services such as elastic computing, block storage, object storage, virtual private cloud (VPC) network, elastic public IP (elastic IP, EIP), and mirroring. Regions are divided into general regions and dedicated regions. General regions refer to regions that provide general cloud services to public users; dedicated regions refer to dedicated regions that only carry the same type of business or only provide business services to specific users. Generally, one or more hosts (for example, a host can be used as a node) can be deployed in the same region to provide one or more services (or can be called businesses).
[0039] (5) Availability zone (AZ): An AZ is a collection of one or more physical data centers with independent power supply. Within an AZ, computing, network, storage and other resources can be logically divided into multiple clusters. Multiple AZs in a region are connected by high-speed optical fibers to meet the needs of users to build high-performance applications across AZs. Generally, one or more hosts can be deployed in the same AZ to provide at least one service.
[0040] The embodiments of the present application will be described in detail below with reference to the accompanying drawings.
[0041] The following describes possible application scenarios to which the data synchronization method provided by the present application is applicable. It should be noted that these descriptions are intended to facilitate understanding by those skilled in the art and do not limit the scope of protection claimed by the present application.
[0042] Figure 1 A possible application scenario schematic diagram provided by an embodiment of the present application is exemplified. In this application scenario, the backup cloud storage node and the main cloud storage node are respectively located in different availability zones (such as availability zone AZ1 and availability zone AZ2) in the same region as an example. For example, the backup cloud storage node is deployed in availability zone AZ2, and the main cloud storage node is deployed in availability zone AZ1. Exemplarily, the backup cloud storage node can be deployed through one or more computing devices (or can be called service nodes, or can be called computer devices) in availability zone AZ2, and the main cloud storage node can be deployed through one or more computing devices in availability zone AZ1. Optionally, a file system is deployed on the main cloud storage node, and a file system is deployed on the backup cloud storage node. Among them, one or more instances can be run on each computing device. For example, taking the backup cloud storage node as an example, the backup cloud storage node can be deployed through one or more instances in availability zone AZ2. Exemplarily, an instance can be any one or more combinations of computing resources of different granularities such as virtual machines, containers or hosts. Among them, the main cloud storage node or the backup cloud storage node is used to provide data storage services (such as services such as writing data, deleting data, modifying data or viewing data) for users. For example, when the primary cloud storage node encounters a disaster (such as virus invasion, hardware failure, human error or natural disaster, etc.) and becomes abnormal or fails, the provider of data storage services can switch from the primary cloud storage node to the backup cloud storage node, and users can perform corresponding data operations (such as writing data, deleting data, modifying data or viewing data, etc.) by using the file system of the backup cloud storage node.
[0043] For example, in one example, when the user needs to configure disaster recovery for the file system of the primary cloud storage node, it is necessary to fully copy (or fully synchronize) the multiple file data included in the file system of the primary cloud storage node. In another example, when the data synchronization relationship between the primary cloud storage node and the backup cloud storage node is in a disconnected state, if the communication connection between the primary cloud storage node and the backup cloud storage node is re-established, it is necessary to fully copy the multiple file data included in the file system of the primary cloud storage node. Optionally, the user can first deploy (or create) a target cloud storage node in the availability zone AZ1, and then the backup cloud storage node can complete the full copy of the file data in the file system of the primary cloud storage node through the target cloud storage node. For example, when deploying the target cloud storage node, the user can first take a snapshot of the full file data in the file system of the primary cloud storage node to obtain a full snapshot (or a consistent full snapshot) corresponding to the primary cloud storage node. Among them, the full snapshot includes multiple file data. Afterwards, the user can deploy the target cloud storage node in the availability zone AZ1 according to the full snapshot. For example, the user can select one or more computing devices from other computing devices included in the availability zone AZ1 except for one or more computing devices used to deploy the primary cloud storage node to deploy the target cloud storage node. Then, the backup cloud storage node can obtain multiple file data included in the full snapshot from the target cloud storage node after establishing a communication connection with the target cloud storage node. The target cloud storage node stores the same full data as the primary cloud storage node. For example, the backup cloud storage node can establish a data synchronization channel with the target cloud storage node, and obtain multiple file data included in the full snapshot from the target cloud storage node through the data synchronization channel.
[0044] It should be noted that Figure 1 Only one possible application scenario is provided schematically, and this schematic application scenario is to more clearly illustrate the technical solution of the embodiment of the present application, and does not limit the application scenario of the data synchronization method provided by the present application. In addition, those skilled in the art will know that with the evolution of the application scenario, the technical solution provided by the embodiment of the present application is also applicable to similar technical problems.
[0045] The following is based on Figure 1 The application scenario shown is used to introduce the specific implementation of the data synchronization method in the embodiment of the present application in detail.
[0046] Figure 2 The following is a flow chart showing a data synchronization method provided by an embodiment of the present application. Figure 1The application scenario illustrated. Optionally, the method is applied to a file system, and the file system is deployed on at least one cloud storage node. The at least one cloud storage node may include a primary cloud storage node and at least one backup cloud storage node. The at least one backup cloud storage node may be deployed in different availability zones from the primary cloud storage node, and the different availability zones may be located in the same area or in different areas. Exemplarily, the cloud storage node may be a computing device (or a computing device cluster) having the functions required to implement the method, or it may be a functional element (such as a plug-in, component, chip or circuit, etc.) in a computing device (or a computing device cluster) having the functions required to implement the method, or it may be any other device having the functions required to implement the method. Optionally, in order to facilitate the introduction of the technical solution provided in the embodiments of the present application, the following takes the primary cloud storage node and the backup cloud storage node as an example to introduce the process of implementing the data synchronization method through data interaction between the primary cloud storage node and the backup cloud storage node. As Figure 2 As shown, the method includes:
[0047] Step 201: The primary cloud storage node creates a full snapshot of the file system of the primary cloud storage node.
[0048] In a data disaster recovery scenario, when disaster recovery backup is performed for file data in the file system of the primary cloud storage node, in order to achieve full replication of file data in the file system of the primary cloud storage node to the backup cloud storage node without affecting the related operations of business personnel (or other personnel who need to use the cloud storage node) on the file data in the file system of the primary cloud storage node, users (such as operation and maintenance personnel) can deploy target cloud storage nodes in the availability zone where the primary cloud storage node is located, so that the backup cloud storage node can complete the full replication of file data in the file system of the primary cloud storage node through the target cloud storage node. Among them, disaster recovery backup of file data in the file system of the primary cloud storage node can ensure that when the primary cloud storage node encounters a disaster, the user can complete the corresponding data operations by using the backup cloud storage node, thereby ensuring the continuous availability of the data storage service and the smooth operation of related data services, and can ensure that the user is not affected when using the data storage service provided by the cloud storage node. In addition, disaster recovery backup of file data in the file system of the primary cloud storage node can also protect data security.
[0049] For example, when a user needs to deploy a target cloud storage node in the availability zone where the primary cloud storage node is located, the primary cloud storage node can first take a snapshot of the full data in the file system of the primary cloud storage node to obtain the full snapshot corresponding to the primary cloud storage node. The full snapshot contains multiple file data, which is also the full data in the file system of the primary cloud storage node.
[0050] Step 202: The primary cloud storage node provides a full snapshot to the target cloud storage node, and the target cloud storage node receives the full snapshot.
[0051] After creating a full snapshot of the file system of the primary cloud storage node, the primary cloud storage node can provide the full snapshot to the target cloud storage node. In one example, after receiving the full snapshot, the target cloud storage node can cache the full snapshot, such as the target cloud storage node can store the full snapshot in local memory or other cache areas. At this time, the target cloud storage node stores the same full file data as the file system of the primary cloud storage node. In another example, a file system is also deployed on the target cloud storage node. After receiving the full snapshot, the target cloud storage node can store the full snapshot in the file system. At this time, the target cloud storage node stores the same full file data as the file system of the primary cloud storage node.
[0052] Among them, the target cloud storage node and the primary cloud storage node can be deployed in the same availability zone in the same region, and the primary cloud storage node and the backup cloud storage node can be deployed in different availability zones respectively. Among them, the different availability zones can be located in the same region (or can be called a physical service area), or the different availability zones can be located in different regions. For example, taking a primary cloud storage node and a backup cloud storage node as an example, in one example, the primary cloud storage node and the backup cloud storage node are deployed in two different availability zones in the same region, and in another example, the primary cloud storage node is deployed in an availability zone in one region, and the backup cloud storage node is deployed in an availability zone in another region. Among them, different availability zones in the same region are physical areas isolated from each other by power or network.
[0053] Step 203: The backup cloud storage node asynchronously obtains the file data of the full snapshot from the target cloud storage node.
[0054] In a possible implementation, the backup cloud storage node may establish a communication connection with the target cloud storage node, and after the communication connection is established, the backup cloud storage node may asynchronously obtain the file data of the full snapshot of the file system of the primary cloud storage node from the target cloud storage node. Exemplarily, the backup cloud storage node may establish a data synchronization channel (or may be referred to as a data communication channel or a data transmission channel) with the target cloud storage node, and the backup cloud storage node obtains the file data of the full snapshot of the file system of the primary cloud storage node from the target cloud storage node through the data synchronization channel.
[0055] In another possible implementation, the backup cloud storage node may also establish a communication connection with the primary cloud storage node, and after the communication connection is established, the backup cloud storage node may synchronously obtain from the primary cloud storage node the file log generated when a file is updated in the file system of the primary cloud storage node. Exemplarily, the backup cloud storage node may also establish a data synchronization channel with the primary cloud storage node, and the backup cloud storage node obtains the file log from the primary cloud storage node through the data synchronization channel.
[0056] The following describes the implementation process of synchronizing (or loading) the file data of the full snapshot from the target cloud storage node after the backup cloud storage node establishes a communication connection with the target cloud storage node through the following possible implementation methods.
[0057] Implementation method one: The backup cloud storage node may send a first request to the target cloud storage node. The first request is used to request to obtain the attribute information of the root directory, and the attribute information of the root directory may include at least one sub-item located at the next level of the root directory. Optionally, the attribute information of the root directory may also include directory data corresponding to the root directory. Exemplarily, the type of the sub-item is one of the following: file or directory. After receiving the first request, the target cloud storage node may send the attribute information of the root directory to the backup cloud storage node. After receiving the attribute information of the root directory, the backup cloud storage node may traverse at least one sub-item in turn. Optionally, when the attribute information of the root directory includes directory data corresponding to the root directory, the backup cloud storage node may store the directory data corresponding to the root directory.
[0058] In one example, when it is determined that the type of the traversed target sub-item is a directory, the backup cloud storage node may send a second request to the target cloud storage node. The second request is used to request to obtain the attribute information of the target sub-item, and the attribute information of the target sub-item may include at least one sub-item located at the next level of the target sub-item. Optionally, the attribute information of the target sub-item may also include directory data corresponding to the target sub-item. Exemplarily, the type of the target sub-item is one of the following: file or directory. After receiving the second request, the target cloud storage node sends the attribute information of the target sub-item to the backup cloud storage node. The target sub-item is any one of the at least one sub-item.
[0059] After receiving the attribute information of the target sub-item, the backup cloud storage node may store the directory data corresponding to the target sub-item when the attribute information of the target sub-item includes the directory data corresponding to the target sub-item. In addition, the backup cloud storage node may also sequentially traverse at least one sub-item included in the attribute information of the target sub-item. When it is determined that the type of the traversed sub-item is a file, the backup cloud storage node may send a file data acquisition request to the target cloud storage node. The file data acquisition request is used to request to obtain the file data corresponding to the sub-item, and the sub-item is any one of the at least one sub-item included in the attribute information of the target sub-item. After receiving the file data acquisition request, the target cloud storage node may send the file data corresponding to the sub-item to the backup cloud storage node. When it is determined that the type of the traversed sub-item is a directory, the backup cloud storage node may send a property information acquisition request to the target cloud storage node. The property information acquisition request is used to request to obtain the property information of the sub-item, and the property information of the sub-item may include at least one sub-item located at the next level of the sub-item. Optionally, the attribute information of the sub-item may also include directory data corresponding to the sub-item. Exemplarily, the type of the sub-item is one of the following: file or directory. After receiving the attribute information acquisition request, the target cloud storage node sends the attribute information of the sub-item to the backup cloud storage node. After receiving the attribute information of the sub-item, when the attribute information of the sub-item includes the directory data corresponding to the sub-item, the backup cloud storage node may store the directory data corresponding to the sub-item. In addition, the backup cloud storage node may also traverse at least one sub-item included in the attribute information of the sub-item in turn until all sub-items are traversed.
[0060] In another example, when it is determined that the type of the traversed target sub-item is a file, the backup cloud storage node may send a third request to the target cloud storage node. The third request is used to request to obtain the file data corresponding to the target sub-item. After receiving the third request, the target cloud storage node may send the file data corresponding to the target sub-item to the backup cloud storage node.
[0061] In addition, each time the target cloud storage node sends the corresponding data corresponding to the root directory requested by the backup cloud storage node to the backup cloud storage node, the corresponding data corresponding to the root directory (such as the directory data of the root directory) can also be deleted, or each time the target cloud storage node sends the corresponding data corresponding to a sub-item requested by the backup cloud storage node to the backup cloud storage node, the corresponding data corresponding to the sub-item can be deleted, until the corresponding data corresponding to the root directory and multiple sub-items (i.e., multiple file data) are all deleted, which indicates that the synchronization process of multiple file data has been completed.
[0062] Figure 3 A multi-branch tree provided in an embodiment of the present application is exemplified. Figure 3 There are 9 nodes, namely, the root node / , node a, node b, node c, node d, node e, node file1, node file2 and node file3. Among them, the root directory name corresponding to the root node / is / , the root directory identifier (or can be called number or index) corresponding to the root node / is 1, the directory name corresponding to the node a is a, the directory identifier corresponding to the node a is 10, the directory name corresponding to the node b is b, the directory identifier corresponding to the node b is 11, the directory name corresponding to the node c is c, the directory identifier corresponding to the node c is 12, the directory name corresponding to the node d is d, the directory identifier corresponding to the node d is 20, the file name corresponding to the node file2 is file2, the file identifier corresponding to the node file2 is 21, the file name corresponding to the node file3 is file3, the file identifier corresponding to the node file3 is 22, the directory name corresponding to the node e is e, the directory identifier corresponding to the node e is 23, the file name corresponding to the node file1 is file1, and the file identifier corresponding to the node file1 is 30. Among them, subitems a, b, and c are located at the next level of the root directory / , subitems d and file2 are located at the next level of subitem a, file1 is located at the next level of subitem d, file3 is located at the next level of subitem b, and e is located at the next level of subitem c.
[0063] When the backup cloud storage node obtains the attribute information of the root directory / , it can store the directory data of the root directory / , and can sequentially traverse the sub-item a, sub-item b, and sub-item c located at the next level of the root directory / .
[0064] For example, taking the traversal of sub-item a located at the next level of the root directory / as an example, when traversing to sub-item a and determining that the type of sub-item a is a directory, a request for obtaining the attribute information of sub-item a can be sent to the target cloud storage node. After receiving the request, the target cloud storage node sends the attribute information of sub-item a to the backup cloud storage node. Exemplarily, the attribute information of sub-item a may include directory data corresponding to sub-item a and sub-item d and sub-item file2 located at the next level of sub-item a. After receiving the attribute information of sub-item a, the backup cloud storage node may store the directory data corresponding to sub-item a included in the attribute information of sub-item a, and may traverse sub-item d and sub-item file2 located at the next level of sub-item a in sequence.
[0065] When traversing to sub-item d and determining that the type of sub-item d is a directory, a request for obtaining the attribute information of sub-item d can be sent to the target cloud storage node. After receiving the request, the target cloud storage node sends the attribute information of sub-item d to the backup cloud storage node. Exemplarily, the attribute information of sub-item d may include directory data corresponding to sub-item d and sub-item file1 located at the next level of sub-item d. After receiving the attribute information of sub-item d, the backup cloud storage node may store the directory data corresponding to sub-item d included in the attribute information of sub-item d, and may traverse sub-item file1 located at the next level of sub-item d. When determining that the type of sub-item file1 is a file, a request for obtaining the file data corresponding to sub-item file1 can be sent to the target cloud storage node. After receiving the request, the target cloud storage node may send the file data corresponding to sub-item file1 to the backup cloud storage node.
[0066] When the sub-item file2 is traversed and the type of the sub-item file2 is determined to be a file, a request for obtaining the file data corresponding to the sub-item file2 may be sent to the target cloud storage node. After receiving the request, the target cloud storage node may send the file data corresponding to the sub-item file2 to the backup cloud storage node.
[0067] Optionally, the technical solution provided by the above implementation method 1 can be encapsulated into a scan and load task. After the backup cloud storage node establishes a communication connection with the target cloud storage node, the scan and load task can be executed to load one or more data included in the full snapshot in the target cloud storage node into the backup cloud storage node.
[0068] Implementation method two: The backup cloud storage node may send a fourth request to the target cloud storage node. The fourth request is used to request to obtain a multi-branch tree of the target cloud storage node, and the multi-branch tree is constructed by the primary cloud storage node or the target cloud storage node or the computing device cluster used to deploy the primary cloud storage node or the computing device cluster used to deploy the target cloud storage node according to the directory identifier and the file identifier included in the full snapshot of the file system of the primary cloud storage node, and the nodes included in the multi-branch tree correspond to the directory identifier (or may be called the directory number or the target index) or the file identifier (or may be called the file number or the file index). After receiving the fourth request, the target cloud storage node may construct a multi-branch tree according to the directory identifier and the file identifier included in the full snapshot, and send the multi-branch tree to the backup cloud storage node, or may also send the stored constructed multi-branch tree to the backup cloud storage node. Afterwards, after receiving the multi-branch tree, the backup cloud storage node can use the node (such as the root node) at the starting position in the multi-branch tree as the starting point of the data traversal, and recursively traverse the multiple nodes included in the multi-branch tree in sequence through the depth-first search algorithm (DFS). When traversing to the target node in the multi-branch tree, the backup cloud storage node can load the data corresponding to the target node (such as directory data or file data) from the target cloud storage node, and store the data corresponding to the target node. Among them, the target node is any node among the multiple nodes included in the multi-branch tree. Then, the backup cloud storage node can traverse the other nodes in the multi-branch tree except the target node in sequence until at least one leaf node in the multi-branch tree is traversed, thereby realizing the loading of the data corresponding to the multiple nodes included in the multi-branch tree into the backup cloud storage node. In addition, when the target cloud storage node determines that the backup cloud storage node loads the data corresponding to a node to the backup cloud storage node each time, the data corresponding to the node can be deleted until the data corresponding to multiple nodes are all deleted, which can indicate that the full synchronization process of the data corresponding to multiple nodes has been completed.
[0069] For example, continuing with the above Figure 3 As an example of the multi-branch tree shown in the figure, the backup cloud storage node obtains Figure 3 After the multi-branch tree shown in the figure, we can Figure 3The root node / in the illustrated multi-branch tree is used as the traversal starting point, and the multiple nodes included in the multi-branch tree are traversed in sequence according to the depth-first search algorithm. Exemplarily, the traversal order of the multiple nodes included in the multi-branch tree according to the depth-first search algorithm of the backup cloud storage node can be root node / →node a→node d→node file1→node file2→node b→node file3→node c→node e. Afterwards, the backup cloud storage node can traverse the multiple nodes in sequence according to the traversal order of the multiple nodes included in the multi-branch tree, and load the data corresponding to each traversed node from the target cloud storage node. For example, taking the traversal of the root node / as an example, when the root node / is traversed, the backup cloud storage node can load the directory data corresponding to the directory identifier of the root node / as 1 (or the directory name is / ) from the target cloud storage node. For another example, taking the traversal of node a as an example, when the node a is traversed, the backup cloud storage node can load the directory data corresponding to the directory identifier of node a as 10 (or the directory name is a) from the target cloud storage node. For another example, taking the traversal of node file1 as an example, when traversing to node file1, the backup cloud storage node can load the file data with the file identifier 30 (or the file name file1) corresponding to node file1 from the target cloud storage node.
[0070] Optionally, the technical solution provided by the second implementation method can also be encapsulated into a scan and load task. After the backup cloud storage node establishes a communication connection with the target cloud storage node, the scan and load task can be executed to load one or more data included in the full snapshot in the target cloud storage node into the backup cloud storage node.
[0071] Implementation method three: The backup cloud storage node can send a fifth request to the target cloud storage node. Among them, the fifth request is used to request the target cloud storage node to use the root directory as the starting point of data traversal, and start to traverse the data included in the full snapshot in sequence (such as directory data or file data). After receiving the fifth request, the target cloud storage node can use the root directory as the starting point of data traversal, start to traverse the data included in the full snapshot in sequence, and send the traversed data included in the full snapshot to the backup cloud storage node in sequence. Then, the backup cloud storage node can receive the data included in the full snapshot from the target cloud storage node in sequence according to the traversal order of the data included in the full snapshot. In addition, each time the target cloud storage node sends a piece of data to the backup cloud storage node, the data can be deleted until multiple data are all deleted, which can indicate that the synchronization process of the data included in the full snapshot has been completed.
[0072] Optionally, the technical solution provided by the third implementation method can also be encapsulated into a scan and load task. After the backup cloud storage node establishes a communication connection with the target cloud storage node, the scan and load task can be executed to load one or more data included in the full snapshot in the target cloud storage node into the backup cloud storage node.
[0073] In a possible implementation, after the backup cloud storage node asynchronously obtains the file data of the full snapshot from the target cloud storage node, the backup cloud storage node may also send an indication message to the target cloud storage node. Exemplarily, the indication message may be used to indicate that the file data synchronization of the full snapshot in the target cloud storage node is complete, or the indication message may also be used to indicate the deletion of the full snapshot.
[0074] In one example, when the indication information is used to indicate that the file data synchronization of the full snapshot in the target cloud storage node is completed, the target cloud storage node can choose to delete the full snapshot in the target cloud storage node after receiving the indication information, or can also choose to close the data synchronization channel between the backup cloud storage node and the target cloud storage node.
[0075] In another example, when the indication information is used to indicate the deletion of the full snapshot, the target cloud storage node can delete the full snapshot in the target cloud storage node after receiving the indication information. Optionally, the target cloud storage node can also choose to close the data synchronization channel between the backup cloud storage node and the target cloud storage node.
[0076] In another possible implementation, after the backup cloud storage node asynchronously obtains the file data of the full snapshot from the target cloud storage node, the user (such as an operation and maintenance personnel or a data synchronization personnel) can send an instruction message to the backup cloud storage node through a terminal device. Exemplarily, the instruction message can be used to indicate that the file data synchronization of the full snapshot in the target cloud storage node is complete, or the instruction message can also be used to indicate the closure or deletion of the data synchronization channel between the backup cloud storage node and the target cloud storage node, or the instruction message can also be used to indicate the disconnection of the communication connection between the backup cloud storage node and the target cloud storage node.
[0077] In one example, when the indication information is used to indicate that the file data synchronization of the full snapshot in the target cloud storage node is completed, the target cloud storage node may choose to close or delete the data synchronization channel between the backup cloud storage node and the target cloud storage node after receiving the indication information. Optionally, the target cloud storage node may also choose to disconnect the communication connection between the backup cloud storage node and the target cloud storage node after receiving the indication information.
[0078] In another example, when the indication information is used to indicate closing or deleting the data synchronization channel between the backup cloud storage node and the target cloud storage node, the target cloud storage node may close or delete the data synchronization channel between the backup cloud storage node and the target cloud storage node after receiving the indication information.
[0079] In another example, when the indication information is used to indicate disconnection of the communication connection between the backup cloud storage node and the target cloud storage node, the target cloud storage node may disconnect the communication connection between the backup cloud storage node and the target cloud storage node after receiving the indication information.
[0080] By way of example, the implementation process of establishing a data synchronization channel between a backup cloud storage node and a target cloud storage node is introduced below through the following possible implementation methods.
[0081] Method 1: The target cloud storage node has been deployed in the area where the primary cloud storage node is located. When the backup cloud storage node obtains the first indication information, the backup cloud storage node can establish a data synchronization channel with the target cloud storage node according to the first indication information.
[0082] Among them, the first indication information is used to instruct the backup cloud storage node to copy (or synchronize) the file data in the file system of the primary cloud storage node from the target cloud storage node, and the data synchronization channel is used to realize cross-region data synchronization between the backup cloud storage node and the target cloud storage node.
[0083] For example, the first indication information can be sent by the user to the backup cloud storage node through a terminal device (such as a smart phone, tablet computer, desktop computer, computer with wireless transceiver function (such as a laptop computer, etc.) or a vehicle-mounted device, etc.), or it can be sent by the main cloud storage node to the backup cloud storage node when the main cloud storage node senses that the target cloud storage node has been established.
[0084] Based on the above method 1, the implementation process of establishing a data synchronization channel between the backup cloud storage node and the target cloud storage node is introduced through the following possible examples.
[0085] Example 1: The backup cloud storage node can establish a data synchronization channel between the backup cloud storage node and the target cloud storage node according to the address of the backup cloud storage node (such as an IP address or a domain name address, etc.) and the address of the target cloud storage node (such as an IP address or a domain name address, etc.).
[0086] Example 2: The backup cloud storage node and the target cloud storage node each correspond to a data connection service. The data connection service is used to help establish a data synchronization channel. When the backup cloud storage node needs to establish a data synchronization channel with the target cloud storage node, a data synchronization channel establishment request can be sent to the corresponding data connection service. The data synchronization channel establishment request is used to request the establishment of a data synchronization channel between the backup cloud storage node and the target cloud storage node. After receiving the data synchronization channel establishment request, the data connection service can send the data synchronization channel establishment request to the data connection service corresponding to the target cloud storage node. After receiving the data synchronization channel establishment request, the data connection service corresponding to the target cloud storage node sends a response message to the data connection service corresponding to the backup cloud storage node to establish a data synchronization channel between the backup cloud storage node and the target cloud storage node. Optionally, the response message is used to indicate consent to establish a data synchronization channel between the backup cloud storage node and the target cloud storage node.
[0087] Method 2: The backup cloud storage node and the target cloud storage node have established a data synchronization channel, but when the network signal is unstable, the network equipment (such as routers or switches) fails, or the network is congested, the network connection will be disconnected, resulting in the data synchronization relationship between the backup cloud storage node and the target cloud storage node being disconnected. Afterwards, when the network connection returns to normal, when the backup cloud storage node determines that the data synchronization relationship between the backup cloud storage node and the target cloud storage node is disconnected, in order to be able to re-copy file data from the target cloud storage node, the backup cloud storage node can re-establish a data synchronization channel with the target cloud storage node.
[0088] Method 3: A master-slave data synchronization relationship has been established between the backup cloud storage node and the primary cloud storage node, but the target cloud storage node is not deployed in the area where the primary cloud storage node is located, or the target cloud storage node is deployed in the area where the primary cloud storage node is located but is not used.
[0089] The following describes the implementation process of establishing a data synchronization channel between the backup cloud storage node and the target cloud storage node in the third method described above through the following possible examples.
[0090] Example 1: When the master-slave data synchronization relationship between the backup cloud storage node and the primary cloud storage node is disconnected due to unstable network signals, failure of network equipment (such as routers or switches), or network congestion, when the target cloud storage node is not deployed in the area where the primary cloud storage node is located, the operation and maintenance personnel can deploy the target cloud storage node in the area where the primary cloud storage node is located. After that, after the operation and maintenance personnel have deployed the target cloud storage node in the area where the primary cloud storage node is located, they can send a second indication message to the backup cloud storage node through the corresponding terminal device. Then, when the backup cloud storage node determines that the master-slave data synchronization relationship between the backup cloud storage node and the primary cloud storage node is disconnected, if the backup cloud storage node receives the second indication message, it can establish a data synchronization channel with the target cloud storage node. Among them, the second indication message is used to indicate that the target cloud storage node has been deployed in the area where the primary cloud storage node is located, and the file data in the file system of the primary cloud storage node can be fully copied from the target cloud storage node.
[0091] Example 2: When the master-slave data synchronization relationship between the backup cloud storage node and the primary cloud storage node is disconnected due to unstable network signals, failure of network equipment (such as routers or switches), or network congestion, when the target cloud storage node is deployed in the area where the primary cloud storage node is located but not in use, in order to be able to re-copy the file data in the file system of the primary cloud storage node without affecting the business personnel's related operations on the file data in the file system of the primary cloud storage node, the user (such as operation and maintenance personnel or related users of the backup cloud storage node, etc.) can send a third indication message to the backup cloud storage node through the corresponding terminal device. Afterwards, when the backup cloud storage node determines that the master-slave data synchronization relationship between the backup cloud storage node and the primary cloud storage node is in a disconnected state, if the backup cloud storage node receives the third indication message, it can establish a data synchronization channel with the target cloud storage node. Among them, the third indication message is used to indicate that the target cloud storage node deployed in the area where the primary cloud storage node is located can be used, and the file data in the file system of the primary cloud storage node can be copied from the target cloud storage node. Optionally, when a target cloud storage node is deployed in the area where the primary cloud storage node is located but is not in use, if the backup cloud storage node learns that a target cloud storage node is deployed in the area where the primary cloud storage node is located, it can also actively establish a data synchronization channel with the target cloud storage node so as to fully copy the file data in the file system of the primary cloud storage node from the target cloud storage node.
[0092] Step 204: When a file in the file system is updated, the primary cloud storage node obtains a file log.
[0093] Step 205: The standby cloud storage node synchronously obtains the file log from the primary cloud storage node.
[0094] In response to the user's corresponding update operation on the file data in the file system of the primary cloud storage node, the primary cloud storage node can obtain a file log (or can be called an operation log or a logical log). Optionally, the file log records the change information (or can be called modification information or update information) of the file system of the primary cloud storage node, that is, it records the modification process of the file system of the primary cloud storage node. Exemplarily, taking file A included in the file system of the primary cloud storage node as an example, in response to the user's corresponding update operation on file A, the primary cloud storage node can obtain a file log for file A. Among them, the file log for file A records the user's update process of file A, and the subsequent backup cloud storage node can complete the update of file A stored in the file system of the backup cloud storage node by replaying the file log, which helps to ensure that file A included in the file system of the backup cloud storage node is consistent with file A included in the file system of the primary cloud storage node.
[0095] For example, one or more business personnel (or other personnel who need to use the cloud storage node) perform corresponding update operations (such as modification or writing) on one or more data in the file system of the primary cloud storage node while using the primary cloud storage node. In response to the business personnel's corresponding update operations on the one or more data, the primary cloud storage node will record the one or more business personnel's corresponding update operation process on the data (such as recording the business personnel's operation process of modifying, deleting, updating or writing data) and generate a corresponding file log.
[0096] In one example, the primary cloud storage node can actively push the corresponding file log to the backup cloud storage node. For example, a data synchronization channel can be established between the primary cloud storage node and the backup cloud storage node, and then the primary cloud storage node can push the corresponding file log to the backup cloud storage node through the data synchronization channel. In this way, after the primary cloud storage node generates the corresponding file log, it will push the file log to the backup cloud storage node in a timely manner. Exemplarily, the file log records the change information of the business personnel (or other personnel who need to use the cloud storage node) to the file data in the file system of the primary cloud storage node (that is, the data modification process, such as what content has been modified and how the modification is performed specifically).
[0097] In another example, the backup cloud storage node may also send a file log acquisition request to the primary cloud storage node. The file log acquisition request is used to request to obtain the file log. After receiving the file log acquisition request, the primary cloud storage node may send the corresponding file log to the backup cloud storage node.
[0098] Step 206: The backup cloud storage node updates the file data corresponding to the file log in the file system of the backup cloud storage node.
[0099] After receiving the corresponding file log, the backup cloud storage node can read the file log, or parse the file log to obtain the file identifier (such as the identifier of a certain file) and the update operation corresponding to the file identifier (or can be understood as data operation logic) included in the file log. Among them, the file identifier is used to identify the file. Optionally, the file log may also include a directory identifier (such as the identifier of a certain directory) and an update operation corresponding to the directory identifier. Among them, the directory identifier is used to identify the directory. Exemplarily, the update operation may include but is not limited to: a sql write statement in which the business personnel writes the corresponding data in the primary cloud storage node, a sql delete statement in which the business personnel deletes the corresponding data in the primary cloud storage node, a sql update statement in which the business personnel updates the corresponding data in the primary cloud storage node, or other forms of operation logic.
[0100] The following takes the file log including the file identifier and the update operation corresponding to the file identifier as an example to introduce the implementation process of the backup cloud storage node updating the file data corresponding to the file identifier in the file system of the backup cloud storage node through the following possible implementation methods.
[0101] Method 1: When it is determined that the file data corresponding to the file identifier does not exist in the file system of the backup cloud storage node, the backup cloud storage node can load the file data corresponding to the file identifier from the target cloud storage node, and store the file data corresponding to the file identifier in the file system of the backup cloud storage node. Afterwards, the backup cloud storage node can update the file data corresponding to the file identifier included in the file system of the backup cloud storage node according to the update operation corresponding to the file identifier, so that the file data corresponding to the file identifier included in the file system of the backup cloud storage node can be consistent with the file data corresponding to the file identifier included in the file system of the primary cloud storage node. For example, the backup cloud storage node can synchronize the relevant data changes in the file system of the primary cloud storage node to the file system of the backup cloud storage node by replaying the update operation corresponding to the file identifier or replaying the file log, thereby ensuring that the file data included in the file system of the backup cloud storage node is consistent with the file data included in the file system of the primary cloud storage node.
[0102] Method 2: When it is determined that file data corresponding to the file identifier exists in the file system of the backup cloud storage node, the backup cloud storage node can update the file data corresponding to the file identifier in the file system of the backup cloud storage node according to the update operation corresponding to the file identifier. In this way, the file data included in the file system of the backup cloud storage node can be consistent with the file data included in the file system of the primary cloud storage node.
[0103] For example, the above Figure 3Taking the file file3 corresponding to the node file3 as an example, a business person modifies the file name file3 of the file file3 to the file name file4 during the use of the primary cloud storage node, that is, the file file3 becomes the file file4, and the file identifier 22 of the file file3 becomes the file identifier 25. In response to the relevant operations of the business person on the file file3, the primary cloud storage node will record the operation process of the business person on the file file3 and generate a file log for the file file3. After that, the primary cloud storage node can send the file log for the file file3 to the backup cloud storage node. Among them, the file log for the file file3 records the change information of the business person on the file file3 (for example, the modification process of the business person modifying the file identifier 22 and the name of the file file3 corresponding to the file identifier 22). After receiving the file log, the backup cloud storage node can parse the file log to obtain the file identifier 22 and the update operation corresponding to the file identifier 22 (that is, the file name file3 of the file file3 is modified to the file name file4, and the file identifier 22 of the file file3 is modified to the modification process of the file identifier 25).
[0104] When it is determined that file data corresponding to file identifier 22 exists in the file system of the backup cloud storage node, the backup cloud storage node can modify the file name file3 of file file3 to file name file4 and modify the file identifier 22 of file file3 to file identifier 25 by replaying the update operation corresponding to file identifier 22 (or the file log for file file3). This ensures that the data included in the file system of the backup cloud storage node is consistent with the data included in the file system of the primary cloud storage node.
[0105] When it is determined that the file data corresponding to the file identifier 22 does not exist in the file system of the backup cloud storage node, the backup cloud storage node can load the file data corresponding to the file identifier 22 from the target cloud storage node and store the file data corresponding to the file identifier 22. Afterwards, the backup cloud storage node can modify the file name file3 of the file file3 to the file name file4 and modify the file identifier 22 of the file file3 to the file identifier 25 by replaying the data operation logic corresponding to the file identifier 22 (or the file log for the file file3), so as to ensure that the data included in the file system of the backup cloud storage node is consistent with the data included in the file system of the primary cloud storage node.
[0106] Optionally, the technical solution provided in step 206 can be packaged into a fixed-point loading task. After the backup cloud storage node establishes a communication connection with the target cloud storage node, the fixed-point loading task can be executed to update the corresponding data in the file system of the backup cloud storage node.
[0107] In addition, it should be noted that, when the backup cloud storage node is executing the implementation method 1, implementation method 2, or implementation method 3 in the above step 203, if the backup cloud storage node receives the file log from the primary cloud storage node, the technical solution provided in the above step 206 may also be executed. Optionally, when the technical solution provided in step 206 is executed in parallel with the technical solution provided in the above implementation method 1, implementation method 2, or implementation method 3, if the backup cloud storage node is executing the technical solution provided in the above implementation method 1, implementation method 2, or implementation method 3, when it is determined that there is data corresponding to the file log (such as directory data or file data) in the file system of the backup cloud storage node, the corresponding data included in the file system of the backup cloud storage node may be updated according to the file log. When it is determined that there is no data corresponding to the file log in the file system of the backup cloud storage node, the backup cloud storage node may obtain the data corresponding to the file log from the target cloud storage node, and after obtaining the data corresponding to the file log, the corresponding data included in the file system of the backup cloud storage node may be updated according to the file log.
[0108] It can be seen from the above steps 201 to 206 that by deploying the target cloud storage node according to the full snapshot of the file system of the primary cloud storage node, the backup cloud storage node can be made to fully synchronize the file data in the file system of the primary cloud storage node from the target cloud storage node after establishing a communication connection with the target cloud storage node. In this way, the method can ensure that the replication of file data in the file system of the primary cloud storage node will not affect or interrupt the relevant operations of the business personnel (or other personnel who need to use the cloud storage node) on the file data in the file system of the primary cloud storage node, so that the data access experience of the business personnel (or other personnel who need to use the cloud storage node) to the primary cloud storage node can be effectively improved, and it can be ensured that the business personnel (or other personnel who need to use the cloud storage node) will not perceive the data replication process during the use of the primary cloud storage node. In addition, the method can complete the replication of file data in the file system of the primary cloud storage node through the interaction between the backup cloud storage node and the target cloud storage node, without the need to install proprietary data copy software, and without the need for data synchronization personnel to have certain software usage capabilities, so that data synchronization operations can be made more convenient.
[0109] It should be noted that each step involved in the above embodiments can be performed by a corresponding device, or by a chip, processor, or chip system in the device, and the embodiments of the present application do not limit them. The above embodiments are only described by taking the corresponding device as an example.
[0110] It should be noted that in the above embodiments, some steps can be selected for implementation, and the order of the steps in the diagram can be adjusted for implementation, and this application does not limit this. It should be understood that executing some steps in the diagram, adjusting the order of the steps, or combining them for specific implementation all fall within the scope of protection of this application.
[0111] It is understandable that, in order to implement the functions in the above embodiments, the various devices involved in the above embodiments include hardware structures and / or software modules corresponding to the execution of the various functions. It should be easily appreciated by those skilled in the art that, in combination with the units and method steps of the various examples described in the embodiments disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.
[0112] It should be noted that the "steps" in the embodiments of the present application are only for illustration, and are a method of expression used to better understand the embodiments, and do not constitute a substantial limitation on the execution of the scheme of the present application. For example, the "steps" can also be understood as "features". In addition, the steps do not constitute any limitation on the execution order of the scheme of the present application. Any changes in the order of steps, step merging, or step splitting made on this basis that do not affect the implementation of the overall scheme, and the resulting new technical solutions are also within the scope of the disclosure of the present application.
[0113] Based on the same concept, the present application embodiment also provides a possible file system, which is suitable for Figure 1 In the application scenario illustrated. Optionally, the file system is deployed on at least one cloud storage node, and the at least one cloud storage node may include a primary cloud storage node and at least one backup cloud storage node. The at least one backup cloud storage node may be deployed in different availability zones from the primary cloud storage node, and different availability zones may be located in the same area or in different areas. Exemplarily, the cloud storage node may be a computing device (or a computing device cluster) having the functions required to implement the method, or it may be a functional element (such as a plug-in, component, chip or circuit, etc.) in a computing device (or a computing device cluster) having the functions required to implement the method, or it may be any other device having the functions required to implement the method.
[0114] See also Figure 4, the file system 400 includes a primary cloud storage node 401 and a backup cloud storage node 402 .
[0115] When the file system 400 is used to implement the above Figure 2 The functions of the cloud storage node (such as the primary cloud storage node or the backup cloud storage node) in the method embodiment shown are:
[0116] The primary cloud storage node 401 is used to create a full snapshot of the file system of the primary cloud storage node and to provide the full snapshot to the target cloud storage node, wherein the target cloud storage node and the primary cloud storage node are deployed in the same availability zone in the same region.
[0117] The backup cloud storage node 402 is used to asynchronously obtain the file data of the full snapshot from the target cloud storage node.
[0118] The primary cloud storage node 401 is also used to obtain a file log when a file in the file system of the primary cloud storage node is updated, wherein the file log records the updated file data in the file system.
[0119] The backup cloud storage node 402 is also used to synchronously obtain the file log from the primary cloud storage node, and is also used to update the file data corresponding to the file log in the file system of the backup cloud storage node.
[0120] Wherein, when the file system 400 is used to implement Figure 2 When the functions of the cloud storage nodes (such as the primary cloud storage nodes or the backup cloud storage nodes) in the method embodiment shown in FIG. 4 are described in more detail, the primary cloud storage nodes 401 or the backup cloud storage nodes 402 may be referred to in the above Figure 2 The relevant descriptions about the primary cloud storage node or the backup cloud storage node in the method embodiment shown are not repeated here.
[0121] Optional, above Figure 4 The primary cloud storage node and the backup cloud storage node shown can be implemented by software, or can be implemented by hardware. Exemplarily, the implementation method of the backup cloud storage node is introduced below, taking the backup cloud storage node as an example. Similarly, the implementation method of the primary cloud storage node can refer to the implementation method of the backup cloud storage node, which will not be repeated here.
[0122] When implemented by software, the backup cloud storage node may include an application or code block running on a computer device. The computer device may be at least one of a physical host, a virtual machine, a container, and other computing devices. Furthermore, the above-mentioned computer device may be one or more. For example, the backup cloud storage node may include an application running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the application may be distributed in the same AZ or in different AZs. The multiple hosts / virtual machines / containers used to run the application may be distributed in the same region or in different regions. Typically, a region may include multiple AZs.
[0123] Similarly, multiple hosts / virtual machines / containers for running the application can be distributed in the same VPC or in multiple VPCs. Typically, a region can include multiple VPCs, and a VPC can include multiple AZs.
[0124] When implemented by hardware, the backup cloud storage node may include at least one computing device, such as a server, etc. Alternatively, the backup cloud storage node may also be a device implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.
[0125] The multiple computing devices included in the backup cloud storage node can be distributed in the same AZ or in different AZs. The multiple computing devices included in the backup cloud storage node can be distributed in the same region or in different regions. Similarly, the multiple computing devices included in the backup cloud storage node can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.
[0126] Based on the same concept, the present application embodiment also provides a possible computing device for executing the data synchronization method shown in the above method embodiment. The relevant features can be found in the above method embodiment and will not be described in detail here. Figure 5 As shown, the computing device 500 includes: a bus 501, a processor 502 and a memory 504. Optionally, the computing device 500 may also include a communication interface 503. The processor 502, the communication interface 503 and the memory 504 communicate with each other through the bus 501. The computing device 500 may be a server or a terminal device. It should be understood that the present application does not limit the number of processors and memories in the computing device 500.
[0127] The bus 501 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 The bus 501 is represented by only one line, but it does not mean that there is only one bus or one type of bus. The bus 501 may include a path for transmitting information between various components of the computing device 500 (for example, the memory 504, the processor 502, and the communication interface 503).
[0128] The processor 502 may include any one or more of a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).
[0129] The memory 504 may include a volatile memory, such as a random access memory (RAM). The processor 502 may also include a non-volatile memory, such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD), or a solid state drive (SSD).
[0130] The memory 504 stores executable program codes, and the processor 502 executes the executable program codes to respectively implement the functions of the aforementioned primary cloud storage node and the backup cloud storage node, thereby implementing the data synchronization method provided in the embodiment of the present application. That is, the memory 504 stores computer program instructions for executing the data synchronization method.
[0131] Alternatively, the memory 504 stores executable code, and the processor 502 executes the executable code to respectively implement the functions of the aforementioned primary cloud storage node and the backup cloud storage node, thereby implementing the data synchronization method provided in the embodiment of the present application. That is, the memory 504 stores computer program instructions for executing the data synchronization method provided in the embodiment of the present application.
[0132] The communication interface 503 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computing device 500 and other devices or a communication network.
[0133] Based on the same concept, the embodiment of the present application also provides a possible computing device cluster for executing the method shown in the above method embodiment. The relevant features can be found in the above method embodiment, which will not be repeated here. The computing device cluster includes at least one computing device. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop, a laptop, or a smart phone.
[0134] like Figure 6 As shown, the computing device cluster 600 includes at least one computing device 500. The memory 504 in one or more computing devices 500 in the computing device cluster 600 may store the same instructions for executing the data synchronization method provided in the embodiment of the present application.
[0135] In some possible implementations, the memory 504 of one or more computing devices 500 in the computing device cluster 600 may also store partial instructions for executing the data synchronization method. In other words, the combination of one or more computing devices 500 may jointly execute instructions for executing the data synchronization method.
[0136] It should be noted that the memory 504 in different computing devices 500 in the computing device cluster 600 may store different instructions, which are respectively used to execute part of the functions of the primary cloud storage node (or backup cloud storage node). That is, the instructions stored in the memory 504 in different computing devices 500 may implement the functions of the primary cloud storage node (or backup cloud storage node).
[0137] In some possible implementations, one or more computing devices in the computing device cluster 600 may be connected via a network, which may be a wide area network or a local area network. Figure 7 A possible implementation is shown. Figure 7 As shown, two computing devices 500A and 500B are connected via a network. Specifically, the network is connected via a communication interface in each computing device. In this type of possible implementation, the memory 504 in the computing device 500A stores instructions for executing the functions of the primary cloud storage node. At the same time, the memory 504 in the computing device 500B stores instructions for executing the functions of the backup cloud storage node.
[0138] It should be understood that Figure 7 The functions of the computing device 500A shown in FIG. 5A may also be completed by multiple computing devices 500. Similarly, the functions of the computing device 500B may also be completed by multiple computing devices 500.
[0139] The present application embodiment also provides another computing device cluster. The connection relationship between the computing devices in the computing device cluster can be similar to that of Figure 6 and Figure 7 The connection mode of the computing device cluster is different in that the memory 504 in one or more computing devices 500 in the computing device cluster may store the same instructions for executing the data synchronization method.
[0140] In some possible implementations, the memory 504 of one or more computing devices 500 in the computing device cluster may also store partial instructions for executing the data synchronization method. In other words, the combination of one or more computing devices 500 may jointly execute instructions for executing the data synchronization method.
[0141] It should be noted that the memory 504 in different computing devices 500 in the computing device cluster can store different instructions for executing some functions of the file system. That is, the instructions stored in the memory 504 in different computing devices 500 can implement the functions of one or more devices in the primary cloud storage node and the backup cloud storage node.
[0142] Based on the same concept, an embodiment of the present application also provides a computer program product including instructions. The computer program product may be a software or program product including instructions that can be run on a computing device or stored in any available medium. When the computer program product is run on at least one computing device, the at least one computing device executes the data synchronization method provided in the embodiment of the present application.
[0143] Based on the same concept, an embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that a computing device can store or a data storage device such as a data center containing one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk). The computer-readable storage medium includes instructions that instruct the computing device to execute the data synchronization method provided in the embodiment of the present application.
[0144] Based on the same concept, an embodiment of the present application further provides a computer chip, which is coupled to a memory and is used to read a computer program stored in the memory and execute a data synchronization method provided in an embodiment of the present application.
[0145] Based on the same concept, an embodiment of the present application also provides a chip system, which includes a processor for supporting a computer device to implement the data synchronization method provided in an embodiment of the present application. In a possible design, the chip system also includes a memory, which is used to store the necessary programs and data of the computer device. The chip system can be composed of a computer chip, or it can include a computer chip and other discrete devices.
[0146] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the protection scope of the technical solutions of the embodiments of the present application.
Claims
1. A data synchronization method, It is characterized in that The method is used for a file system, the file system is deployed on at least one cloud storage node, the at least one cloud storage node includes a primary cloud storage node and at least one backup cloud storage node, the at least one backup cloud storage node and the primary cloud storage node are respectively deployed in different availability zones, the different availability zones are located in the same area or in different areas, and includes: The primary cloud storage node creates a full snapshot of the file system of the primary cloud storage node; The primary cloud storage node provides the full snapshot to the target cloud storage node, and the target cloud storage node and the primary cloud storage node are deployed in the same availability zone in the same region; The backup cloud storage node asynchronously obtains the file data of the full snapshot from the target cloud storage node; When a file in the file system is updated, the primary cloud storage node obtains a file log, and the file log records the updated file data in the file system; The backup cloud storage node synchronously obtains the file log from the primary cloud storage node; The backup cloud storage node updates the file data corresponding to the file log in the file system of the backup cloud storage node.
2. The method according to claim 1, It is characterized in that The backup cloud storage node asynchronously obtains the file data of the full snapshot from the target cloud storage node, including: The backup cloud storage node sends a first request to the target cloud storage node, where the first request is used to request to obtain attribute information of a root directory, where the attribute information of the root directory includes at least one sub-item located at a level below the root directory; The backup cloud storage node receives the attribute information of the root directory from the target cloud storage node, and traverses the at least one sub-item in sequence; When it is determined that the type of the traversed target sub-item is a directory, the backup cloud storage node sends a second request to the target cloud storage node, the second request is used to request to obtain the attribute information of the target sub-item, receive the attribute information of the target sub-item from the target cloud storage node, and traverse at least one sub-item included in the attribute information of the target sub-item in sequence; or When it is determined that the type of the traversed target sub-item is a file, the backup cloud storage node sends a third request to the target cloud storage node, and the third request is used to request to obtain the file data corresponding to the target sub-item, and receive the file data corresponding to the target sub-item from the target cloud storage node.
3. The method according to claim 1, It is characterized in that The backup cloud storage node asynchronously obtains the file data of the full snapshot from the target cloud storage node, including: The backup cloud storage node sends a fourth request to the target cloud storage node, where the fourth request is used to request to obtain a multi-branch tree of the target cloud storage node, where the multi-branch tree is constructed according to the directory identifier and the file identifier included in the full snapshot; The backup cloud storage node receives the multi-branch tree from the target cloud storage node; The backup cloud storage node uses the root node of the multi-branch tree as a data traversal starting point to obtain the file data of the full snapshot from the target cloud storage node.
4. The method according to claim 1, It is characterized in that The backup cloud storage node asynchronously obtains the file data of the full snapshot from the target cloud storage node, including: The backup cloud storage node sends a fifth request to the target cloud storage node, where the fifth request is used to request to use the root directory of the target cloud storage node as a data traversal starting point to traverse file data of the full snapshot in sequence; The backup cloud storage node sequentially receives the file data of the full snapshot from the target cloud storage node according to the traversal order of the file data of the full snapshot.
5. The method according to claim 1, It is characterized in that The backup cloud storage node updates the file data corresponding to the file log in the file system of the backup cloud storage node, including: The backup cloud storage node reads the file log, obtains the file identifier included in the file log and the update operation corresponding to the file identifier, wherein the file identifier is used to identify the file; When the file data corresponding to the file identifier exists in the file system of the backup cloud storage node, the backup cloud storage node updates the file data corresponding to the file identifier in the file system of the backup cloud storage node according to the update operation corresponding to the file identifier; When the file data corresponding to the file identifier does not exist in the file system of the backup cloud storage node, the backup cloud storage node obtains the file data corresponding to the file identifier from the target cloud storage node, and updates the file data corresponding to the file identifier according to the update operation corresponding to the file identifier.
6. The method according to any one of claims 1 to 5, It is characterized in that After the backup cloud storage node asynchronously obtains the file data of the full snapshot from the target cloud storage node, the method further includes: The backup cloud storage node sends indication information to the target cloud storage node, where the indication information is used to indicate that synchronization of file data of the full snapshot in the target cloud storage node is complete, or the indication information is used to indicate deletion of the full snapshot; The target cloud storage node deletes the full snapshot in the target cloud storage node according to the instruction information.
7. A file system, It is characterized in that The file system is deployed on at least one cloud storage node, the at least one cloud storage node includes a primary cloud storage node and at least one backup cloud storage node, the at least one backup cloud storage node and the primary cloud storage node are respectively deployed in different availability zones, and the different availability zones are located in the same area or in different areas, including: The primary cloud storage node is used to create a full snapshot of the file system of the primary cloud storage node, and is also used to provide the full snapshot to the target cloud storage node, the target cloud storage node and the primary cloud storage node are deployed in the same availability zone in the same region; The backup cloud storage node is used to asynchronously obtain the file data of the full snapshot from the target cloud storage node; The primary cloud storage node is further configured to obtain a file log when a file in the file system is updated, wherein the file log records updated file data in the file system; The backup cloud storage node is further used to synchronously obtain the file log from the primary cloud storage node, and is also used to update the file data corresponding to the file log in the file system of the backup cloud storage node.
8. The file system according to claim 7, It is characterized in that The backup cloud storage node, when asynchronously acquiring the file data of the full snapshot from the target cloud storage node, is specifically used to: Sending a first request to the target cloud storage node, where the first request is used to request to obtain attribute information of a root directory, where the attribute information of the root directory includes at least one sub-item located at a level below the root directory; Receiving attribute information of the root directory from the target cloud storage node, and traversing the at least one sub-item in sequence; When it is determined that the type of the traversed target sub-item is a directory, a second request is sent to the target cloud storage node, the second request is used to request to obtain the attribute information of the target sub-item, receive the attribute information of the target sub-item from the target cloud storage node, and traverse at least one sub-item included in the attribute information of the target sub-item in sequence; or When it is determined that the type of the traversed target sub-item is a file, a third request is sent to the target cloud storage node, and the third request is used to request to obtain the file data corresponding to the target sub-item, and receive the file data corresponding to the target sub-item from the target cloud storage node.
9. The file system according to claim 7, It is characterized in that The backup cloud storage node, when asynchronously acquiring the file data of the full snapshot from the target cloud storage node, is specifically used to: Sending a fourth request to the target cloud storage node, the fourth request being used to request obtaining a multi-branch tree of the target cloud storage node, the multi-branch tree being constructed according to the directory identifiers and file identifiers included in the full snapshot; Receiving the multi-branch tree from the target cloud storage node; Taking the root node of the multi-branch tree as the data traversal starting point, the file data of the full snapshot is obtained from the target cloud storage node.
10. The file system according to claim 7, It is characterized in that The backup cloud storage node, when asynchronously acquiring the file data of the full snapshot from the target cloud storage node, is specifically used to: Sending a fifth request to the target cloud storage node, the fifth request being used to request to use the root directory of the target cloud storage node as a data traversal starting point to traverse file data of the full snapshot in sequence; The file data of the full snapshot is received sequentially from the target cloud storage node according to the traversal order of the file data of the full snapshot.
11. The file system according to claim 7, It is characterized in that The backup cloud storage node, when updating the file data corresponding to the file log in the file system of the backup cloud storage node, is specifically used to: Read the file log to obtain a file identifier and an update operation corresponding to the file identifier included in the file log, wherein the file identifier is used to identify a file; When the file data corresponding to the file identifier exists in the file system of the backup cloud storage node, the file data corresponding to the file identifier in the file system of the backup cloud storage node is updated according to the update operation corresponding to the file identifier; When the file data corresponding to the file identifier does not exist in the file system of the backup cloud storage node, the file data corresponding to the file identifier is obtained from the target cloud storage node, and the file data corresponding to the file identifier is updated according to the update operation corresponding to the file identifier.
12. The file system according to any one of claims 7 to 11, It is characterized in that The backup cloud storage node is further used to send indication information to the target cloud storage node, where the indication information is used to indicate that synchronization of file data of the full snapshot stored in the target cloud storage node is complete, or the indication information is used to indicate deletion of the full snapshot; The target cloud storage node is used to delete the full snapshot in the target cloud storage node according to the indication information.
13. A computing device, It is characterized in that The computing device includes a processor and a memory; The memory is used to store computer program instructions; The processor calls the computer program instructions stored in the memory to execute the method according to any one of claims 1 to 6.
14. A computing device cluster, It is characterized in that The computing device cluster includes at least one computing device, each computing device includes a processor and a memory; the memory in the at least one computing device is used to store computer program instructions; The processor in the at least one computing device calls the computer program instructions stored in the memory to execute the method according to any one of claims 1 to 6.
15. A computer-readable storage medium, It is characterized in that The method comprises computer program instructions. When the computer program instructions are executed by a computing device, the computing device performs the method according to any one of claims 1 to 6.
16. A computer program product comprising instructions, It is characterized in that When the instructions are executed by a computing device, the computing device is caused to perform the method as claimed in any one of claims 1 to 6.
