Object storage cluster-oriented disaster recovery processing method and storage medium

Abstract

The embodiment of the invention discloses a disaster recovery processing method oriented to an object storage cluster. Comprising the steps that in response to an event representing that an object storage main cluster is abnormal, an object storage cluster access link is switched from a main cluster link to a standby cluster link, an object storage cluster comprises an object storage main cluster and an object storage reserve cluster, the main cluster link corresponds to the object storage main cluster, and the standby cluster link corresponds to the object storage reserve cluster; the standby cluster link corresponds to the object reserve cluster; in response to a first data access request for the object storage cluster, determining a first access sequence of first physical buckets for the first physical buckets storing to-be-accessed first target data in the object storage cluster corresponding to an access link of the object storage cluster; and based on the first access sequence, sequentially accessing the first target data stored in the first physical buckets respectively. According to the technical scheme, disaster recovery processing can be carried out on the object storage cluster.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of data storage, and in particular to a disaster recovery processing method and storage medium for an object-oriented storage cluster. Background Art

[0002] With the rapid development of internet technology, data volumes are exploding, ushering in the era of big data. Much of this exploding data consists of unstructured data, such as images, videos, audio, and documents. Object storage, as a scalable, low-cost, and highly reliable cloud storage service, is becoming the industry's mainstream storage method due to its suitability for storing unstructured data. However, due to the demands of specific application scenarios, object storage clusters require a lifecycle-based approach.

[0003] However, object storage cluster failures have occurred frequently in recent years, and how to perform disaster recovery for object storage clusters needs to be solved urgently. Summary of the Invention

[0004] The embodiment of the present invention provides a disaster recovery processing method and storage medium for an object storage cluster, so as to perform disaster recovery processing on the object storage cluster.

[0005] According to one aspect of the present invention, a disaster recovery processing method for an object storage cluster is provided, comprising:

[0006] In response to an event indicating an abnormality in the primary object storage cluster, switching an access link to the object storage cluster from a primary cluster link to a backup cluster link, wherein the object storage cluster includes a primary object storage cluster and a backup object storage cluster, the primary cluster link corresponds to the primary object storage cluster, and the backup cluster link corresponds to the backup object storage cluster;

[0007] In response to a first data access request to the object storage cluster, determining a first access order for each first physical bucket in the object storage standby cluster corresponding to the object storage cluster access link and storing first target data to be accessed;

[0008] Based on the first access order, the first target data respectively stored in the first physical buckets are accessed in sequence.

[0009] According to another aspect of the present invention, a computer-readable storage medium is provided, on which computer instructions are stored. The computer instructions are used to enable a processor to implement any disaster recovery processing method for an object-oriented storage cluster provided by any embodiment of the present invention when executed.

[0010] The technical solution of an embodiment of the present invention includes, in response to an event characterizing an abnormality of an object storage primary cluster, switching the object storage cluster access link from a primary cluster link to a backup cluster link, wherein the object storage cluster includes an object storage primary cluster and an object storage backup cluster, the primary cluster link corresponds to the object storage primary cluster, and the backup cluster link corresponds to the object storage backup cluster, so as to promptly switch to the object storage backup cluster in the event of a failure of the object storage primary cluster to ensure the availability of the object storage cluster and the business continuity of the upper-layer application system; in response to a first data access request to the object storage cluster, determining a first access order of each first physical bucket storing first target data to be accessed in the object storage backup cluster corresponding to the object storage cluster access link, so that by determining the access order of the physical buckets, physical buckets in the hot physical area can be accessed first, thereby improving data storage efficiency; based on the first access order, the first target data stored in each first physical bucket is accessed in sequence, so as to realize access to data in the object storage through the object storage backup cluster in the event of a failure of the object storage primary cluster. The above technical solution, when the object storage main cluster is abnormal, accesses data from the first physical bucket in the object storage backup cluster based on the determined first access order, thereby realizing disaster recovery processing for the object storage cluster.

[0011] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present invention, nor is it intended to limit the scope of the present invention. Other features of the present invention will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0013] Figure 1 This is a flow chart of a disaster recovery processing method for an object storage cluster provided according to an embodiment of the present invention;

[0014] Figure 2 is a flowchart of another disaster recovery processing method for an object storage cluster provided according to an embodiment of the present invention;

[0015] Figure 3 This is a flowchart of another disaster recovery processing method for an object storage cluster provided according to an embodiment of the present invention;

[0016] Figure 4This is a general framework diagram of a disaster recovery processing device as a specific example in another disaster recovery processing method for an object storage cluster provided in an embodiment of the present invention;

[0017] Figure 5 This is a diagram of an operation framework of a disaster recovery processing device according to a specific example of another disaster recovery processing method for an object storage cluster provided in an embodiment of the present invention when the object storage main cluster is operating normally;

[0018] Figure 6 This is a workflow diagram of a client parsing unit according to a specific example of another disaster recovery processing method for an object storage cluster provided in an embodiment of the present invention;

[0019] Figure 7 This is a diagram of an operation framework of a disaster recovery processing device in the case of abnormal operation of an object storage main cluster, which is a specific example of another disaster recovery processing method for an object storage cluster provided by an embodiment of the present invention;

[0020] Figure 8 This is a flowchart of a disaster recovery switching process according to a specific example of another disaster recovery processing method for an object storage cluster provided in an embodiment of the present invention;

[0021] Figure 9 This is a diagram of an operation framework of a disaster recovery processing device when an object storage master cluster resumes normal operation, according to a specific example of another disaster recovery processing method for an object storage cluster provided by an embodiment of the present invention;

[0022] Figure 10 This is a flowchart of a disaster recovery and switchback workflow of a specific example in another disaster recovery processing method for an object storage cluster provided in an embodiment of the present invention;

[0023] Figure 11 This is a workflow diagram of a data access unit in a specific example of another disaster recovery processing method for an object storage cluster provided in an embodiment of the present invention;

[0024] Figure 12 This is a structural block diagram of a disaster recovery processing device for an object storage cluster provided according to an embodiment of the present invention;

[0025] Figure 13 It is a structural diagram of an electronic device for implementing the disaster recovery processing method for an object-oriented storage cluster according to an embodiment of the present invention. DETAILED DESCRIPTION

[0026] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0027] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. The situations of "target", "original", etc. are similar and will not be repeated here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or that are inherent to these processes, methods, products or devices.

[0028] Figure 1 This is a flow chart of a method for disaster recovery for an object storage cluster, provided in an embodiment of the present invention. This embodiment is applicable to situations where disaster recovery is performed on an object storage cluster. The method can be performed by a disaster recovery device for an object storage cluster, provided in an embodiment of the present invention. This device can be implemented in software and / or hardware and integrated into an electronic device, such as a user terminal or server.

[0029] See also Figure 1 The method of the embodiment of the present invention specifically includes the following steps:

[0030] S110. In response to an event indicating an abnormality in the primary object storage cluster, switch the object storage cluster access link from the primary cluster link to the backup cluster link, wherein the object storage cluster includes the primary object storage cluster and the backup object storage cluster, the primary cluster link corresponds to the primary object storage cluster, and the backup cluster link corresponds to the backup object storage cluster.

[0031] Among them, the object storage cluster can be understood as a storage cluster for objects, which can include two levels: data buckets (equivalent to directories and folders) and objects (equivalent to files). The data buckets are containers for storing various objects, and the structure inside the same data bucket is flat, without a directory hierarchy. Optionally, the object storage cluster can be composed of multiple physical areas (Regions) and isolated from each other. At the same time, due to disaster recovery construction and life cycle construction, the object storage cluster can include an object storage primary cluster and an object storage backup cluster. The data of an upper-level application system may exist in physical buckets under many types of regions, such as the primary cluster hot region, the primary cluster warm region, the primary cluster cold region, the backup cluster hot region, the backup cluster warm region, and the backup cluster cold region, etc. At the same time, the life cycle of a physical bucket corresponds to the type of physical region where the physical bucket is located. For example, the life cycle of a physical bucket in the hot region of a standby cluster can be 1 week, and the life cycle of a physical bucket in the warm region of a standby cluster can be 1 month, and so on. Among them, objects with high data access frequency will remain in the physical bucket under the hot region, objects with average access frequency will flow to the physical bucket under the warm region, and objects with very low access frequency will flow to the physical bucket under the cold region.

[0032] The primary cluster link can be understood as a link for accessing data in the primary object storage cluster; the backup cluster link can be understood as a link for accessing data in the backup object storage cluster.

[0033] In response to an abnormality in the object storage primary cluster, in order to ensure the smooth operation of the object storage, the object storage cluster access link can be switched from the primary cluster link to the backup cluster link, and data can be accessed from the object storage backup cluster to achieve disaster recovery processing for the object storage cluster.

[0034] S120 . In response to a first data access request to the object storage cluster, determine a first access order for first physical buckets storing first target data to be accessed in the object storage backup cluster corresponding to the object storage cluster access link.

[0035] Among them, the first data access request can be understood as a request sent by the application system for accessing data in the object storage backup cluster. Optionally, the first data access request can be a data storage request, a data deletion request, a data extraction request, etc. The first data access request may include the application system number, the logical bucket number, and the data list of the first target data to be accessed, etc. The application system that sent the first data access request can be determined by the application system number. A logical bucket can correspond to multiple types of physical buckets. The first physical bucket that needs to be accessed can be determined by the logical bucket number. The first target data that needs to be accessed can be determined by the data list, and an access connection can be established with the first physical bucket.

[0036] The first physical bucket can be understood as the physical bucket that stores the first target data to be accessed. Physical buckets are used in an object storage cluster for actual data storage. Optionally, the first physical bucket can include physical buckets in multiple regions. The first access order can be understood as the priority order for accessing the first physical bucket.

[0037] In response to a first data access request to the object storage cluster, the received first data access request is parsed, and a first physical bucket requiring data access and a first access order for the first physical bucket are determined from the object storage cluster.

[0038] S130 . Based on the first access order, sequentially access the first target data respectively stored in the first physical buckets.

[0039] After obtaining the first access sequence and the first physical buckets, the first target data respectively stored in the first physical buckets may be accessed sequentially according to the first access sequence to complete data access to the object storage cluster.

[0040] The technical solution of an embodiment of the present invention includes, in response to an event characterizing an abnormality of an object storage primary cluster, switching the object storage cluster access link from a primary cluster link to a backup cluster link, wherein the object storage cluster includes an object storage primary cluster and an object storage backup cluster, the primary cluster link corresponds to the object storage primary cluster, and the backup cluster link corresponds to the object storage backup cluster, so as to promptly switch to the object storage backup cluster in the event of a failure of the object storage primary cluster to ensure the availability of the object storage cluster and the business continuity of the upper-layer application system; in response to a first data access request to the object storage cluster, determining a first access order of each first physical bucket storing first target data to be accessed in the object storage backup cluster corresponding to the object storage cluster access link, so that by determining the access order of the physical buckets, physical buckets in the hot physical area can be accessed first, thereby improving data storage efficiency; based on the first access order, the first target data stored in each first physical bucket is accessed in sequence, so as to realize access to data in the object storage through the object storage backup cluster in the event of a failure of the object storage primary cluster. The above technical solution, when the object storage main cluster is abnormal, accesses data from the first physical bucket in the object storage backup cluster based on the determined first access order, thereby realizing disaster recovery processing for the object storage cluster.

[0041] Figure 2 It is a flowchart of another disaster recovery processing method for an object storage cluster provided by an embodiment of the present invention. This embodiment is optimized based on the above-mentioned technical solutions. In this embodiment, optionally, in response to the first data access request to the object storage cluster, for the first physical bucket storing the first target data to be accessed in the object storage backup cluster corresponding to the object storage cluster access link, the first access order of each first physical bucket is determined, including: in response to the first data access request to the object storage cluster, the first physical bucket storing the first target data to be accessed is determined, wherein the first physical bucket is the physical bucket in the object storage backup cluster corresponding to the object storage cluster access link; according to the life cycle corresponding to each first physical bucket, the first access order of each first physical bucket is determined. Among them, the explanation of the terms that are the same as or corresponding to the above-mentioned embodiments will not be repeated here.

[0042] For details, see Figure 2 The object storage cluster-oriented disaster recovery processing method of this embodiment may specifically include the following steps:

[0043] S210. In response to an event indicating an abnormality in the primary object storage cluster, switch the object storage cluster access link from the primary cluster link to the backup cluster link, wherein the object storage cluster includes the primary object storage cluster and the backup object storage cluster, the primary cluster link corresponds to the primary object storage cluster, and the backup cluster link corresponds to the backup object storage cluster.

[0044] S220. In response to a first data access request for the object storage cluster, determine a first physical bucket storing first target data to be accessed, wherein the first physical bucket is a physical bucket in the object storage backup cluster corresponding to the object storage cluster access link.

[0045] S230 : Determine a first access sequence for each first physical bucket according to the life cycles corresponding to each first physical bucket.

[0046] The lifecycle can be understood as the lifecycle corresponding to each first physical bucket. Physical buckets in different regions have different lifecycles. For example, a physical bucket in a hot region of a standby cluster may have a lifecycle of one week, while a physical bucket in a warm region of a standby cluster may have a lifecycle of one month. The length of the lifecycle corresponds to the type of physical region in which the first physical bucket resides. The lifecycle can be used to determine the first access order for each first physical bucket. For example, when determining the first access order, first physical buckets with shorter lifecycles may be prioritized.

[0047] S240 . Based on the first access order, sequentially access the first target data respectively stored in the first physical buckets.

[0048] The technical solution of the embodiment of the present invention can accurately and orderly access the first physical bucket by determining the first physical bucket and the first access order, thereby improving data access efficiency.

[0049] An optional technical solution, in response to a first data access request to an object storage cluster, determines a first physical bucket storing first target data to be accessed, specifically including: in response to a first data access request initiated by an application system to an object storage cluster, determines a logical bucket accessed by the application system, and determines a first physical bucket corresponding to the logical bucket, wherein the first physical bucket is a physical bucket storing the first target data to be accessed.

[0050] Among them, for the upper-level application system connected to the object storage cluster, it is necessary to determine the corresponding logical data bucket when accessing data. The logical bucket may correspond to multiple physical buckets of different types. The first data access request includes the logical bucket number. The first physical bucket can be obtained by parsing the logical bucket.

[0051] The above technical solution can accurately determine the first physical bucket through the logical bucket.

[0052] Figure 3This is a flowchart of another disaster recovery method for an object storage cluster, provided in an embodiment of the present invention. This embodiment is optimized based on the aforementioned technical solutions. Optionally, this embodiment further includes: in response to an event indicating recovery of the primary object storage cluster, after successfully accessing the first target data stored in each first physical bucket, synchronizing the access result to the primary object storage cluster. Explanations of terms that are identical or corresponding to those in the aforementioned embodiments are not repeated here.

[0053] For details, see Figure 3 The object storage cluster-oriented disaster recovery processing method of this embodiment may specifically include the following steps:

[0054] S310. In response to an event indicating an abnormality in the primary object storage cluster, switch the object storage cluster access link from the primary cluster link to the backup cluster link, wherein the object storage cluster includes the primary object storage cluster and the backup object storage cluster, the primary cluster link corresponds to the primary object storage cluster, and the backup cluster link corresponds to the backup object storage cluster.

[0055] S320 : In response to a first data access request to the object storage cluster, determine a first access order for each first physical bucket in the object storage backup cluster corresponding to the object storage cluster access link, storing first target data to be accessed.

[0056] S330 : Based on the first access order, sequentially access the first target data respectively stored in the first physical buckets.

[0057] S340 : In response to an event indicating recovery of the object storage primary cluster, after successfully accessing the first target data respectively stored in the first physical buckets, synchronize the access result to the object storage primary cluster.

[0058] Among them, when the object storage main cluster is restored, after the first target data stored in each first physical bucket is successfully accessed, it is necessary to synchronize data on the object storage main cluster and synchronize the access results to the object storage main cluster to ensure data synchronization between the object storage main cluster and the object storage backup cluster.

[0059] The technical solution of the embodiment of the present invention can ensure data synchronization between the primary object storage cluster and the backup object storage cluster after the primary object storage cluster returns to normal.

[0060] An optional technical solution is applied to a disaster recovery processing cluster, which is a cluster different from the object storage cluster.

[0061] The disaster recovery processing cluster is a different cluster from the object storage cluster. Therefore, during the synchronization of access results through the disaster recovery processing cluster, the access results can be directly synchronized with the primary object storage cluster through the disaster recovery processing cluster, without occupying the bandwidth of the backup object storage cluster and ensuring the normal operation of the backup object storage cluster. Alternatively, during the synchronization of access results with the backup object storage cluster, the access results can also be directly synchronized with the backup object storage cluster through the disaster recovery processing cluster, without occupying the bandwidth of the primary object storage cluster and ensuring the normal operation of the primary object storage cluster.

[0062] The above technical solution synchronizes access results through the disaster recovery processing cluster instead of directly synchronizing access results between the object storage primary cluster and the object storage backup cluster, which can avoid occupying the bandwidth of the object storage backup cluster.

[0063] Another optional technical solution also includes: in response to an event indicating that all data between the primary object storage cluster and the backup object storage cluster are consistent, switching the object storage cluster access link from the backup cluster link to the primary cluster link.

[0064] Among them, when the object storage primary cluster returns to normal and all data between the object storage primary cluster and the object storage backup cluster are consistent, the object storage primary cluster continues to be used for data access, and the object storage cluster access link is switched from the backup cluster link to the primary cluster link and then back to the object storage primary cluster module to ensure that data access is still performed in the object storage primary cluster when the object storage primary cluster is normal.

[0065] The above technical solution switches back the access link when the object storage primary cluster returns to normal and data synchronization is completed, which can ensure that data can still be accessed in the object storage primary cluster when the object storage primary cluster is normal.

[0066] On this basis, an optional method further includes: in response to an event indicating the recovery of the object storage primary cluster, starting a scheduled comparison task, so as to use the scheduled comparison task to regularly compare whether all data are consistent; if all data are consistent, triggering an event indicating that all data are consistent.

[0067] Among them, when the object storage primary cluster is restored, data synchronization with the object storage primary cluster is required. At this time, a scheduled comparison task is started between the object storage primary cluster and the object storage backup cluster to regularly compare whether all data is consistent. If all data is consistent, it indicates that data synchronization between the object storage primary cluster and the object storage backup cluster has been completed, and an event indicating that all data is consistent is triggered.

[0068] The above technical solution can timely determine whether the data between the object storage primary cluster and the object storage backup cluster is synchronized through regular comparison.

[0069] Another optional method also includes: in response to a second data access request for the object storage cluster, determining a second access order for each second physical bucket in the object storage main cluster corresponding to the object storage cluster access link that stores the second target data to be accessed; and accessing the second target data stored in each second physical bucket in sequence according to the second access order.

[0070] The second data access request may be understood as a data access request to the object storage primary cluster.

[0071] The second physical bucket can be understood as a physical bucket determined from the object storage main cluster based on the second data access request, and storing the second target data to be accessed.

[0072] When no abnormality occurs in the object storage main cluster, the second access order of the second physical bucket and the second physical bucket is determined from the object storage main cluster through the object storage cluster access link, and finally the second target data stored in each second physical bucket is accessed in sequence according to the second access order through the data access module.

[0073] The above technical solution can implement access to the second target data in the second physical bucket in the object storage main cluster when the object storage main cluster is normal.

[0074] On this basis, optionally, the method further includes: after successfully accessing the second target data respectively stored in each second physical bucket, synchronizing the access result to the object storage backup cluster.

[0075] The above technical solution synchronizes the access result to the object storage backup cluster after the second target data is successfully accessed, thereby ensuring data synchronization between the primary and backup clusters.

[0076] In order to better understand the above-mentioned technical solutions as a whole, the following is an exemplary description of the above-mentioned technical solutions with reference to specific examples. In this specific example, the overall framework diagram of the disaster recovery processing device for the object storage cluster is as follows: Figure 4 As shown, it includes a client parsing unit, a disaster recovery switching unit, and a data access unit. The specific steps are as follows:

[0077] 1. When the object storage main cluster is operating normally, Figure 5 As shown, the online access request (ie, the second data access request) enters the client parsing unit. The workflow diagram of the client parsing unit is as follows: Figure 6As shown, when an application system sends an online access request containing an application system number, a logical bucket number, and a repository list, it first searches the cache to see if the corresponding client set (i.e., the set of access connections for accessing the physical bucket corresponding to the logical bucket) exists. If so, the client set is directly returned. Otherwise, the obtained repository list is traversed and parsed. When the list boundary is not reached, client information (i.e., the access connection for accessing the physical bucket corresponding to the logical bucket) is generated based on information such as the Region type, tenant type, and security certificate of each record in the repository list. Finally, the access priority of each physical bucket is determined based on the Region type, following the priority principle of "hot Region>warm Region>cold Region". The client set is updated, and the second physical bucket set and the second access order of the second physical bucket in the object storage primary cluster to be accessed by the logical bucket are parsed. The online access module in the data access unit actually reads and writes data according to the second access order of the second physical bucket set and the second physical bucket. After successfully accessing the second target data stored in each second physical bucket, the data is asynchronously written to the object storage backup cluster through the near real-time synchronization module, thereby achieving near real-time synchronization of the primary and backup clusters.

[0078] 2. If the object storage main cluster is running abnormally, such as Figure 7 As shown, the disaster recovery switching is performed through the disaster recovery switching module in the disaster recovery switching unit. The disaster recovery switching flow chart is as follows Figure 8 As shown, the access link of the object storage cluster is switched from the main cluster link to the backup cluster link, and the configuration is pushed to the online access module; when an online access request enters the client parsing unit, the first physical bucket set and the first access order of the first physical bucket in the object storage backup cluster to be accessed by the logical bucket are parsed; the online access module in the data access unit performs actual data reading and writing according to the first physical bucket set and the first access order of the first physical bucket.

[0079] 3. When the object storage primary cluster resumes normal operation, Figure 9 As shown, when the primary cluster recovers, disaster recovery is switched back. The disaster recovery switchback workflow is as shown in Figure 10 As shown, the cluster being accessed at this time is still the object storage backup cluster, and the switch for switching back is on. When the switch for switching back is on, a task is started in the background to periodically compare the consistency of the primary and backup data (i.e., to compare whether all the data in the object storage primary cluster and the object storage backup cluster are consistent). Only when the primary and backup data are consistent will the switch for switching back be closed, the type of access cluster will also be changed to the object storage primary cluster, and the configuration will be pushed to the online access module. Afterwards, data access and data synchronization are performed in the object storage primary cluster through the data access unit. The workflow diagram of the data access unit is shown in the figure below. Figure 11As shown, the online access request is first verified, including the verification of the application system, interface permissions and logical buckets. If the verification fails, it returns directly; otherwise, it continues to obtain the corresponding physical bucket client set (i.e., the set of access connections for accessing the physical bucket corresponding to the logical bucket) according to the accessed cluster type (object storage primary cluster or object storage backup cluster); data access is dynamically performed according to the priority of the physical bucket client (i.e., the access order). For example, for a deletion operation, the deletion is first performed in the physical bucket with the highest priority, and then the deletion is continued in the physical bucket with the next priority, and so on; the data upload operation is directly uploaded to the physical bucket with the highest priority; if the data access operation fails, it ends directly, otherwise it is determined whether the failback preparation switch is turned on. If the failback preparation switch is turned on, it means that the object storage primary cluster has just recovered to normal and data needs to be synchronized to the object storage primary cluster; if the failback preparation switch is turned off, if the access cluster type at this time is the object storage primary cluster, it means that the object storage primary cluster is working normally and data is synchronized to the object storage backup cluster; otherwise, it means that the object storage primary cluster is abnormal and the object storage backup cluster is being accessed. No data synchronization is required and it ends directly.

[0080] The above specific example implements disaster recovery processing for the object storage cluster.

[0081] Figure 12 This is a block diagram of the structure of the object-oriented storage cluster disaster recovery processing device provided in an embodiment of the present invention. The device is used to execute the object-oriented storage cluster disaster recovery processing method provided in any of the above embodiments. The device and the object-oriented storage cluster disaster recovery processing method of each of the above embodiments belong to the same inventive concept. For details not fully described in the embodiment of the object-oriented storage cluster disaster recovery processing device, please refer to the embodiment of the object-oriented storage cluster disaster recovery processing method. Figure 12 The device may specifically include: a standby cluster link switching module 410, a first access sequence determination module 420 and a first target data access module 430.

[0082] The backup cluster link switching module 410 is configured to, in response to an event indicating an abnormality in the primary object storage cluster, switch the object storage cluster access link from the primary cluster link to the backup cluster link, wherein the object storage cluster includes the primary object storage cluster and the backup object storage cluster, the primary cluster link corresponds to the primary object storage cluster, and the backup cluster link corresponds to the backup object storage cluster;

[0083] A first access order determining module 420 is configured to determine, in response to a first data access request to the object storage cluster, a first access order for each first physical bucket in the object storage backup cluster corresponding to the object storage cluster access link and storing first target data to be accessed;

[0084] The first target data access module 430 is configured to sequentially access the first target data respectively stored in the first physical buckets based on a first access order.

[0085] Optionally, the first access sequence determination module 420 includes:

[0086] A first physical bucket determining submodule is configured to determine, in response to a first data access request to the object storage cluster, a first physical bucket storing first target data to be accessed, wherein the first physical bucket is a physical bucket in the object storage backup cluster corresponding to the object storage cluster access link;

[0087] The first access sequence determining submodule is configured to determine a first access sequence of each first physical bucket according to the life cycles corresponding to each first physical bucket.

[0088] On this basis, optionally, the first physical bucket determination submodule is specifically configured to:

[0089] In response to a first data access request initiated by an application system for an object storage cluster, a logical bucket accessed by the application system is determined, and a first physical bucket corresponding to the logical bucket is determined, wherein the first physical bucket is a physical bucket storing first target data to be accessed.

[0090] Another optional option also includes:

[0091] The object storage master cluster synchronization module is configured to, in response to an event indicating recovery of the object storage master cluster, synchronize access results to the object storage master cluster after successfully accessing the first target data stored in each first physical bucket.

[0092] On this basis, optional items also include:

[0093] The primary cluster link switching module is configured to switch the object storage cluster access link from the backup cluster link to the primary cluster link in response to an event indicating that all data between the primary object storage cluster and the backup object storage cluster are consistent.

[0094] On this basis, one can optionally also include:

[0095] A timed comparison module is configured to start a timed comparison task in response to an event indicating recovery of the primary object storage cluster, so as to use the timed comparison task to periodically compare all data to determine whether they are consistent.

[0096] The event trigger module is used to trigger an event indicating that all data are consistent when all data are consistent.

[0097] Another option also includes:

[0098] a second access order determining module configured to determine, in response to a second data access request for the object storage cluster, a second access order for each second physical bucket in the object storage primary cluster corresponding to the object storage cluster access link and storing second target data to be accessed;

[0099] The second target data access module is used to sequentially access the second target data respectively stored in the second physical buckets according to a second access sequence.

[0100] On this basis, it also includes:

[0101] The object storage backup cluster synchronization module is used to synchronize the access result to the object storage backup cluster after successfully accessing the second target data respectively stored in each second physical bucket.

[0102] Based on any of the above, optionally, it is applied to a disaster recovery processing cluster, which is a cluster different from the object storage cluster.

[0103] The object storage cluster disaster recovery processing device provided by an embodiment of the present invention switches the object storage cluster access link from the primary cluster link to the backup cluster link in response to an event indicating an abnormality of the object storage primary cluster through a backup cluster link switching module. The object storage cluster includes a primary object storage cluster and a backup object storage cluster, the primary cluster link corresponds to the primary object storage cluster, and the backup cluster link corresponds to the backup object storage cluster. In the event of a failure of the primary object storage cluster, the device promptly switches to the backup object storage cluster to ensure the availability of the object storage cluster and the business continuity of the upper-layer application system. In response to a first data access request to the object storage cluster, the device determines a first access order for each first physical bucket in the backup object storage cluster corresponding to the object storage cluster access link, storing first target data to be accessed. By determining the access order of the physical buckets, physical buckets in a hot physical area can be preferentially accessed, thereby improving data storage efficiency. In the event of a failure of the primary object storage cluster, the device accesses the first target data stored in each first physical bucket in sequence through the backup object storage cluster. The above device, when the object storage main cluster is abnormal, accesses data from the first physical bucket in the object storage backup cluster based on the determined first access order, thereby realizing disaster recovery processing for the object storage cluster.

[0104] The object-oriented storage cluster disaster recovery processing device provided by the embodiment of the present invention can execute the object-oriented storage cluster disaster recovery processing method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0105] It is worth noting that in the above-mentioned embodiment of the disaster recovery processing device for the object-oriented storage cluster, the various units and modules included are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of the present invention.

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

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

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

[0109] The processor 11 can be any general-purpose and / or specialized processing component with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various specialized artificial intelligence (AI) computing chips, various processors that run machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as the disaster recovery processing method for an object storage cluster.

[0110] In some embodiments, the disaster recovery processing method for an object-oriented storage cluster may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the disaster recovery processing method for an object-oriented storage cluster described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to execute the disaster recovery processing method for an object-oriented storage cluster in any other appropriate manner (for example, by means of firmware).

[0111] Various embodiments of the systems and techniques described herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system-on-chip systems (SOCs), programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include being implemented in one or more computer programs that are executable and / or interpreted on a programmable system that includes at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

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

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

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

[0115] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0116] A computing system may include clients and servers. The clients and servers are typically remote from each other and typically interact via a communication network. This client-server relationship arises through computer programs running on the respective computers, creating a client-server relationship. The server may be a cloud server, also known as a cloud computing server or cloud host. This server is a hosting product within the cloud computing service ecosystem that addresses the management difficulties and limited scalability of traditional physical hosting and VPS services.

[0117] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in the present invention can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solution of the present invention can be achieved. This is not limited herein.

[0118] The above specific embodiments do not limit the scope of protection of the present invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may be made based on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention are intended to be included within the scope of protection of the present invention.

Claims

1. A disaster recovery processing method for an object storage cluster, characterized in that: include: In response to an event indicating an abnormality in a primary object storage cluster, switching an access link to the object storage cluster from a primary cluster link to a backup cluster link, wherein the object storage cluster includes a primary object storage cluster and a backup object storage cluster, the primary cluster link corresponds to the primary object storage cluster, and the backup cluster link corresponds to the backup object storage cluster; In response to a first data access request to the object storage cluster, determining a first access order for first physical buckets storing first target data to be accessed in the object storage backup cluster corresponding to the object storage cluster access link; Based on the first access order, the first target data respectively stored in the first physical buckets are accessed in sequence.

2. The method according to claim 1, characterized in that In response to a first data access request to the object storage cluster, determining, for first physical buckets storing first target data to be accessed in the object storage backup cluster corresponding to the object storage cluster access link, a first access order for each of the first physical buckets, including: In response to a first data access request for the object storage cluster, determining a first physical bucket storing first target data to be accessed, wherein the first physical bucket is a physical bucket in the object storage backup cluster corresponding to the object storage cluster access link; A first access sequence of each of the first physical buckets is determined according to the life cycles corresponding to the first physical buckets.

3. The method according to claim 2, characterized in that The step of determining, in response to a first data access request to the object storage cluster, a first physical bucket storing first target data to be accessed, specifically includes: In response to a first data access request initiated by an application system for the object storage cluster, a logical bucket accessed by the application system is determined, and a first physical bucket corresponding to the logical bucket is determined, wherein the first physical bucket is a physical bucket storing the first target data to be accessed.

4. The method according to claim 1, wherein Also includes: In response to an event indicating recovery of the object storage primary cluster, after successfully accessing the first target data respectively stored in the first physical buckets, the access result is synchronized to the object storage primary cluster.

5. The method according to claim 4, characterized in that Also includes: In response to an event indicating that all data between the primary object storage cluster and the backup object storage cluster are consistent, the object storage cluster access link is switched from the backup cluster link to the primary cluster link.

6. The method according to claim 5, characterized in that Also includes: In response to an event indicating recovery of the primary object storage cluster, starting a scheduled comparison task to periodically compare all the data to determine whether they are consistent using the scheduled comparison task; When all the data are consistent, an event indicating that all the data are consistent is triggered.

7. The method according to claim 5, characterized in that Also includes: In response to a second data access request for the object storage cluster, determining a second access order for each second physical bucket in the object storage main cluster corresponding to the object storage cluster access link and storing second target data to be accessed; The second target data respectively stored in the second physical buckets are accessed in sequence according to the second access order.

8. The method according to claim 7, characterized in that Also includes: After successfully accessing the second target data respectively stored in each of the second physical buckets, the access result is synchronized to the object storage backup cluster.

9. The method according to any one of claims 1 to 8, characterized in that Applied to a disaster recovery processing cluster, where the disaster recovery processing cluster is a cluster different from the object storage cluster.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the disaster recovery processing method for an object-oriented storage cluster as described in any one of claims 1 to 9 when executed.

Images