WO2024008024A1 - 一种基于对象存储服务的跨区域转储方法及相关装置 - Google Patents

一种基于对象存储服务的跨区域转储方法及相关装置 Download PDF

Info

Publication number
WO2024008024A1
WO2024008024A1 PCT/CN2023/105273 CN2023105273W WO2024008024A1 WO 2024008024 A1 WO2024008024 A1 WO 2024008024A1 CN 2023105273 W CN2023105273 W CN 2023105273W WO 2024008024 A1 WO2024008024 A1 WO 2024008024A1
Authority
WO
WIPO (PCT)
Prior art keywords
data bucket
dumped
management platform
bucket
cloud management
Prior art date
Application number
PCT/CN2023/105273
Other languages
English (en)
French (fr)
Inventor
肖庚
李婷婷
Original Assignee
华为云计算技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为云计算技术有限公司 filed Critical 华为云计算技术有限公司
Publication of WO2024008024A1 publication Critical patent/WO2024008024A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0604—Improving or facilitating administration, e.g. storage management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
    • G06F3/0647—Migration mechanisms
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]

Definitions

  • the present application relates to the field of cloud technology, and in particular to a cross-region dump method and related devices based on object storage services.
  • Archive storage is a safe and low-cost storage method for cold data. It is suitable for data with low access frequency and requiring persistent storage, such as log audit data, security monitoring data, etc.
  • tenants generate a large amount of data. After a period of time, these data are rarely accessed. Considering that the data needs to be stored for a long time, and in order to save energy and reduce storage costs, these data are generally dumped. For archival storage.
  • Data centers or storage devices are usually established in the western region, which requires data from the eastern region to be dumped to the west. In regional data centers or storage devices, data can be stored in the east or in the west.
  • This application provides a cross-regional dump method based on object storage services, which solves the high-cost problem of data centers in data-producing regions. It can automatically migrate data that needs long-term storage to other low-cost data centers and solve the problem of national Eastern data. The problem of Xicun.
  • this application provides a cross-region dump method based on object storage services.
  • the method is applied to a cloud management platform.
  • the cloud management platform is used to manage the infrastructure that provides object storage services.
  • the infrastructure Including a first object storage service data bucket set in the first area and a second object storage service data bucket set in the second area, the method includes:
  • the cloud management platform provides a configuration interface.
  • the configuration interface is used to receive the dump policy configured by the tenant.
  • the dump policy includes the identity of the source data bucket, the identity of the destination data bucket, and the data to be dumped in the source data bucket. Trigger conditions for objects to be dumped into the destination data bucket, where the source data bucket and the destination data bucket are located in different areas, and storage in the destination data bucket is implemented in the infrastructure after dumping
  • the medium is a tape or an optical disk; the cloud management platform detects the occurrence of the trigger condition, and transfers the objects of the source data bucket to the destination data bucket across regions according to the dump policy.
  • this application provides a cross-region dump method based on object storage services. Tenants can configure the dump strategy through the cloud management platform.
  • the cloud management platform dumps the objects to be dumped from one area to Another area, and the storage medium of the objects to be dumped in the destination data bucket after dumping is tape or optical disk.
  • Implementing this application can realize cross-regional dumping of objects, which can solve the problem of data storage in the country's east and west, reduce storage costs, reduce tenants' storage billing fees, and improve user experience.
  • the cloud management platform receives the tenant's access request for the object to be dumped in the source data bucket; the cloud management platform transfers the object to be dumped from The destination data bucket is migrated across regions to the region where the source data bucket is located, and the objects to be dumped in the region where the source data bucket is located are provided to the tenant.
  • the cloud management platform can also migrate the objects to be dumped from the destination data bucket across regions back to the region where the source data bucket is located, and provide the objects to be dumped to the tenants without affecting the tenants. usage of.
  • the storage medium implemented in the source data bucket in the infrastructure is a mechanical hard disk or a solid state hard disk.
  • the billing fee charged by the cloud management platform to the tenant for the source data bucket is higher than the billing fee charged to the tenant for the destination data bucket.
  • the triggering condition includes any one or more of the following:
  • the triggering condition includes an identification of the object to be dumped in the source data bucket.
  • the identification of the object to be dumped includes specific characters included in the name of the object to be dumped.
  • the area where the destination data bucket is located and/or the destination data bucket is specified by the tenant or automatically selected by the cloud management platform.
  • this application provides a cloud management platform, which is used to manage an infrastructure that provides object storage services.
  • the infrastructure includes a first object storage service data bucket and settings provided in the first area.
  • the second object storage service data bucket in the second region includes:
  • the configuration interface is used to receive the dump policy configured by the tenant.
  • the dump policy includes the identity of the source data bucket, the identity of the destination data bucket, and dumps the objects to be dumped in the source data bucket to Trigger conditions in the destination data bucket, wherein the source data bucket and the destination data bucket are located in different areas, and the storage medium of the destination data bucket implemented in the infrastructure after dumping is a tape or CD;
  • a detection module configured to detect the occurrence of the trigger condition, and transfer the objects of the source data bucket to the destination data bucket across regions according to the dump policy.
  • the cloud management platform also includes:
  • a communication module configured to receive an access request from the tenant for the object to be dumped in the source data bucket
  • a migration module used by the cloud management platform to migrate the object to be dumped from the destination data bucket across regions to the region where the source data bucket is located;
  • the communication module is also configured to provide the object to be dumped in the area where the source data bucket is located to the tenant.
  • the storage medium implemented in the source data bucket in the infrastructure is a mechanical hard disk or a solid state hard disk.
  • the billing fee charged by the cloud management platform to the tenant for the source data bucket is higher than the billing fee charged to the tenant for the destination data bucket.
  • the triggering condition includes any one or more of the following:
  • the triggering condition includes an identification of the object to be dumped in the source data bucket.
  • the identification of the object to be dumped includes specific characters included in the name of the object to be dumped.
  • the area where the destination data bucket is located and/or the destination data bucket is specified by the tenant or automatically selected by the cloud management platform.
  • Each functional module of the second aspect is used to implement the method described in the first aspect or any possible implementation of the first aspect.
  • the present application provides a computing device cluster, including at least one computing device, each of the at least one computing device including a memory and a processor, and the processor of the at least one computing device is configured to execute the The instructions stored in the memory of the at least one computing device enable the computing device cluster to execute the method described in the above first aspect or any possible implementation of the first aspect.
  • the present application provides a computer-readable storage medium, including program instructions.
  • the program instructions When the program instructions are executed by a computing device cluster, the computing device cluster executes the above first aspect or any one of the first aspects. Possible implementations of the methods described.
  • this application provides a system, including a cloud management platform, a first object storage service data bucket set in a first area, and a second object storage service data bucket set in a second area.
  • the cloud management platform It is the cloud management platform described in the above first aspect or any possible implementation manner of the first aspect.
  • Figure 1 is a schematic diagram of a system architecture provided by this application.
  • Figure 2 is a schematic structural diagram of an object storage service system provided by this application.
  • Figure 3 is a schematic diagram of a scenario provided by this application.
  • Figure 4 is a schematic flow chart of a cross-region dump method based on object storage services provided by this application;
  • FIG. 5 is a schematic diagram of an interface provided by this application.
  • Figure 6 is a schematic flow chart of a method for transferring objects to be dumped across regions provided by this application;
  • Figure 7 is a schematic diagram of a cross-region dump process provided by this application.
  • Figure 8 is a schematic flow chart of another cross-region dump method based on object storage services provided by this application.
  • Figure 9 is a schematic flow chart of another method for transferring objects to be dumped across regions provided by this application.
  • FIG. 10 is a schematic diagram of another cross-region dump process provided by this application.
  • Figure 11 is a schematic structural diagram of a cloud management platform provided by this application.
  • Figure 12 is a schematic structural diagram of a computing device provided by this application.
  • Figure 13 is a schematic structural diagram of a computing device cluster provided by this application.
  • Figure 14 is a schematic structural diagram of another computing device cluster provided by this application.
  • the cloud storage system is a distributed storage system.
  • the cloud storage system includes one or more object storage service systems.
  • Each object storage service system may include one or more object storage service systems.
  • cloud storage device may include one or more object storage service systems.
  • the multiple object storage service systems may be located in different areas.
  • the multiple object storage service systems include a first object storage service system and a second object storage service system.
  • the first object storage service system is located in the eastern region
  • the second object storage service system is located in the western region.
  • the area where the first object storage service system and the second object storage service system are located is only used as an example.
  • Multiple object storage service systems can also be located in other areas, which is not limited in this application.
  • the cloud storage system may also include a cloud management platform, which is responsible for managing data in each cloud storage device in multiple object storage service systems. For example, tenants can log in to the cloud management platform to delete or migrate data in a cloud storage device in an object storage service system.
  • the cloud management platform can be located on any computing device in any area, and the computing device can be, for example, a bare metal server, a container, etc.
  • the cost of data storage in different areas is not the same.
  • the cost of establishing an object storage service system and using the object storage service system in different areas is not the same. Some areas have higher costs, and some areas have lower costs.
  • the storage cost includes the capital cost of establishing an object storage service system and using the object storage service system. For example, the storage cost of establishing an object storage service system in the eastern region is higher, while the storage cost of establishing an object storage service system in the western region is lower.
  • Figure 1 is a schematic diagram of another system architecture provided by this application.
  • the system involves a terminal device 110, a network device 120 and a cloud storage system 130.
  • the cloud storage system 130 is a cloud storage system in the above system architecture, and may include one or more object storage service systems, and multiple object storage service systems may be located in different areas.
  • Each object storage service system includes one or more cloud storage devices.
  • a cloud storage device refers to a device that stores data in the form of objects.
  • it may be an object storage device (object storage service, OBS).
  • OBS object storage service
  • the object storage device may also be called an OBS bucket.
  • Cloud storage devices are used to receive and store data sent by tenants through terminal devices.
  • the terminal device 110 can be a mobile phone, desktop computer, notebook, etc. used by the tenant under the cloud storage system 130, or it can be a virtual machine, container or bare metal purchased by the tenant under the cloud storage system 130. Server (bare metal server, BMS), etc.
  • the terminal device 110 is installed with application software (application, referred to as app) or applet.
  • Tenants can manage data through the application software or applet, such as uploading data to the cloud storage system 130 through the application software or applet.
  • the application software or applet downloads data on the cloud storage system 130 and deletes one or more data on the cloud storage system 130 through the application software or applet.
  • a tenant uploads data the data will be uploaded to the object storage service system in the region where the tenant is located, and the data will not be stored across regions to the object storage service system in other regions. For example, if the tenant is located in Guangdong province, the tenant will upload the data to the object storage service system in the Guangdong province region.
  • a tenant uploads data he or she selects the object storage service system in the region where the tenant is located, and uploads the data to the bucket by creating a new bucket or selecting a bucket.
  • the bucket is a container for storing objects in the cloud storage system 130 . When a bucket is created, you need to choose the region in which the bucket is created, which determines the region to which the bucket belongs.
  • the region to which the bucket belongs is the Guangdong province region. It should be noted that buckets cannot cross regions. It can be understood that buckets have attributes, and the attributes of the bucket include, for example, the area to which the bucket belongs.
  • the network device 120 is used to transmit data between the terminal device 110 and the cloud storage system 130 through a communication network of any communication mechanism/communication standard.
  • the communication network may be a wide area network, a local area network, a point-to-point connection, or any combination thereof.
  • FIG. 2 is a schematic structural diagram of an object storage service system provided by this application.
  • the object storage service system includes a business access module, a life cycle management module, a cross-region replication module, a metadata management module and a storage module. The functions of each module are introduced below.
  • the business access module is used to provide application programming interface (API) for external services and provide authentication and authentication functions.
  • API application programming interface
  • tenants upload data through terminal devices, they first access the business access module, which authenticates them. After passing the authentication, the data is written to the storage module. Among them, data is stored in the form of objects in cloud storage devices.
  • the metadata management module is used to generate metadata of the data after the data is written to the storage module.
  • the metadata includes the object name, object storage location, object size, upload time, owner, etc.
  • a metadata list is stored in the metadata management module.
  • the metadata list includes mapping relationships between object names, object storage locations, object sizes, upload times, owners, etc.
  • the metadata management module is also used to manage metadata, such as updating the metadata list when data is written to the storage module or when data is deleted.
  • Storage module used to store data.
  • Data has two storage states in the storage module: standard storage and archive storage. For data with relatively high access frequency, it is suitable to store it in the standard storage state; for data with relatively low or extremely low access frequency, it is suitable to store it in the archive storage state.
  • the storage module includes standard storage media and archive storage media.
  • the standard storage medium can be a mechanical hard disk (HDD) or a solid state drive (SSD).
  • the archive storage medium can be a tape or an optical disk.
  • the storage media here are only used as examples. , this application does not limit the storage medium.
  • the storage state of objects in the object storage service system can also be in other states, which is not limited in this application.
  • it can be a low-frequency storage state.
  • the low-frequency storage state refers to a state between the standard storage state and the archive storage state. Data with lower access frequency but higher access frequency than the archive storage state can be stored in the low-frequency storage state.
  • cold data can be stored in an archive storage state
  • hot data can be stored in a standard storage state
  • warm data can be stored in a low-frequency storage state.
  • this application There is no limitation. In actual applications, they can be divided according to specific application scenarios. Low-frequency storage media are not limited in this application.
  • the life cycle management module is used to manage the life cycle of objects in the storage module according to the life cycle management policy configured by the tenant.
  • Tenants can configure life cycle management policies for objects in cloud storage devices through the cloud management platform to achieve life cycle management.
  • tenants can log in to the cloud management platform, select the target object in the target cloud storage device, and configure the life cycle management policy for the target object.
  • the life cycle management policy includes time management and storage status management. For example, after how many days will the target object be stored by standard storage? The state is changed to the archive storage state. Another example is to change the target object from the archive storage state to the standard storage state.
  • the life cycle management module is used to monitor the objects in the storage module based on the life cycle management policy configured by the tenant. After the monitoring reaches the configured time, the storage state transition is performed.
  • the cross-region replication module is used to copy and send data from one region to another region to achieve cross-region data distribution or backup. For example, some objects in area 1 can be copied and sent to area 2, and stored in the form of objects in area 2. It can be understood that tenants can log in to the cloud management platform, select the objects that need to be dumped, and copy the selected objects to the target region through the cross-region replication module.
  • bucket is a logical concept.
  • the objects in a bucket can all be in the standard storage state, or they can all be in the archive storage state, or some of the objects can be in the standard storage state and some of the objects can be in the archive storage state.
  • This application analyzes the location of the objects in the bucket. The status is not limited.
  • each functional module in Figure 2 can be deployed on one cloud storage device in an object storage service system, or can be distributed on multiple cloud storage devices in an object storage service system. For example, some modules It is deployed on one of the cloud storage devices in an object storage service system, and the remaining modules are deployed on another cloud storage device.
  • This application does not limit the deployment location of each module.
  • the division of each functional module in the object storage service system is just an example. In actual applications, it can be divided into more or fewer modules according to specific functions, which is not limited in this application.
  • This application provides a cross-region dump method based on the object storage service OBS.
  • the following describes the cross-region dump method based on the object storage service OBS provided by this application in conjunction with the scene diagram shown in Figure 3.
  • region 1 can be the eastern region and region 2 can be the western region.
  • This application provides a cross-region dump method, which method includes but is not limited to the description below.
  • the tenant selects the data in bucket 1 of region 1, and copies the data to region 2 through the cross-region replication module.
  • the objects are stored in the standard storage state in region 2.
  • objects can be copied from bucket 1 in area 1 to area 2 through a dedicated line or through the public network, which is not limited in this application.
  • the tenant configures the life cycle management policy on bucket 2 in area 2, and the life cycle management module converts the object from the standard storage state to the archive storage state according to the life cycle management policy.
  • the life cycle management policy configured by the tenant includes converting the objects in bucket 2 from the standard storage state to the archive storage state after 30 days.
  • the life cycle management module performs time monitoring based on the life cycle management policy. When 30 days are reached, bucket 2 will be transferred to the archive storage state. Objects in are converted to archive storage status.
  • the objects in bucket 1 in region 1 can be deleted.
  • this cross-region dump method requires tenants to manually select the objects to be dumped from bucket 1 in region 1, copy the objects to be dumped to bucket 2 in region 2, and configure bucket 2 in region 2. Life cycle management strategy, and then configure the deletion strategy on bucket 1 in area 1. The operation is cumbersome when the amount of data is large, and because it is not sure when the objects in bucket 1 will be copied, the life of bucket 2 is not sure.
  • the cycle management policy can be configured, there may be a time lag between the completion of object replication and the configuration of the life cycle management policy on bucket 2, resulting in a longer dump time.
  • this solution is more complicated to implement because when the object in area 1 is copied to area 2, the object storage location changes, but the belonging bucket information of the data recorded in the tenant's terminal device is not updated, so it is possible This causes tenants to fail when accessing data. It is very difficult to implement real-time updates of the bucket information of the data in the terminal device.
  • humans need to first transfer the data from the archive storage state in area 2 to the standard storage state, and then copy it from area 2 to area 1, which is a complicated operation.
  • FIG. 4 is a flow chart of a cross-region dump method based on an object storage service provided by this application. The method is Including but not limited to the following descriptions.
  • the cloud management platform receives the dump policy configured by the tenant.
  • the dump policy is used to instruct dumping objects to be dumped in the first object storage service system to the second object storage service system.
  • the cloud storage system includes multiple object storage service systems.
  • the multiple object storage service systems include a first object storage service system and a second object storage service system.
  • the first object storage service system and the second object storage service system are located in In different areas of the cloud storage system, the storage cost of data in the area where the first object storage service system is located is higher than the storage cost of data in the area where the second object storage service system is located.
  • the cloud management platform targets data stored in the first object storage service system.
  • the charging fees in the object storage service system are higher than the charging fees when the data is stored in the second object storage service system.
  • the first object storage service system is located in the eastern region
  • the second object storage service system is located in the western region.
  • the tenant logs in to the cloud management platform and configures the dump policy on the cloud management platform.
  • the cloud management platform receives the dump policy configured by the tenant. It can be understood that the cloud management platform provides a configuration interface, and the configuration interface is used to receive the dump policy configured by the tenant.
  • the dump policy is used to instruct to dump the objects to be dumped in the first object storage service system to the second object storage service system.
  • the dump policy may include the identity of the source data bucket, the identity of the destination data bucket and the source data. The triggering condition for dumping the objects to be dumped in the bucket to the destination data bucket.
  • the triggering condition may include the identification of the object to be dumped in the source data bucket, where the identification of the object to be dumped may be, for example, the name of the object to be dumped.
  • the object to be dumped may be an object whose name contains specific characters.
  • the object to be dumped can be determined based on the specific characters contained in the object name. For example, in bucket 1 in the first object storage service system, the object whose object name contains the specific character abc is determined to be the object to be dumped. For example, In bucket 1 in the first object storage service system, objects whose object names are prefixed by the specific character abc are determined as objects to be dumped, etc.
  • the specific character can be any character and is not limited in this application.
  • the objects to be dumped can also be determined based on other conditions. For example, the data uploaded before a certain day, month, and year can be determined as objects to be dumped, etc. This application does not limit it.
  • the area where the destination data bucket is located refers to the object storage service system to which the object to be dumped is dumped, or the area to which the object to be dumped is dumped.
  • the destination area may be the second Object storage service system or second object storage service system area.
  • the region where the destination data bucket is located can be specified by the tenant.
  • the tenant specifies the region where the destination data bucket is located as region 2, or it can be automatically selected by the cloud management platform.
  • the target area selection strategy or algorithm is preset in the cloud management platform.
  • the target area selection strategy or algorithm can be related to the dump cost.
  • the dump cost can include, for example, the transmission time, the network bandwidth consumed by the transmission, and the location of the object in the target area.
  • One or more of the storage costs, the selection strategy or algorithm can also be determined in other ways, and this application does not limit it.
  • the identity of the destination data bucket can be specified by the tenant or automatically selected by the cloud management platform.
  • Trigger conditions can include any one or more of the following: 1) The duration is calculated starting from the configured dump policy, and the duration reaches the preset duration; 2) The occupied capacity in the source data bucket reaches the threshold.
  • a threshold for the occupied capacity of the source data bucket can be set, and when the occupied capacity in the source data bucket reaches the threshold, a dump is performed.
  • the preset duration and occupied capacity thresholds can be set according to specific scenarios, and are not limited in this application.
  • the triggering condition can also be other conditions, which are not limited in this application.
  • the object to be dumped Before the dump, the object to be dumped is in the standard storage state in the first object storage service system. After the dump, the object to be dumped is in the archive storage state in the second object storage service system. Optionally, if the object to be dumped needs to be in the standard storage state in the second object storage service system, it can also be set to the standard storage state.
  • the dump policy includes the identifier of the source data bucket.
  • the bucket identifier can uniquely identify a bucket in the cloud storage system.
  • the identifier of each bucket is unique in the entire cloud storage system.
  • the identifiers of the buckets may be, for example, bucket 1, bucket 2, and bucket 3, or they may be bucket a, bucket b, bucket c, or other identifiers, which are not limited in this application. It can be understood that according to the identifier of the bucket, the data in which bucket needs to be dumped can be determined, and according to the identifier of the object to be dumped, it can be determined which data in which bucket needs to be dumped.
  • Figure 5 is an interface example diagram provided by this application.
  • the dump policy is configured on the cloud management platform.
  • the object to be dumped includes the prefix of the object name: For objects with characters abc, the dump time is 30 days later. Select to immediately configure the dumped state as archive storage state, and select area 2 as the target area.
  • the schematic diagram of the interface for configuring the dump policy provided in Figure 5 is only an example and does not constitute any limitation on this application.
  • the interface for configuring the dump policy can also be in other forms, and the interface can also include more or fewer functions. Fields are not limited in this application.
  • the dump policy is a name defined according to the function.
  • the dump policy is essentially the above-mentioned life cycle management policy.
  • the dump policy is for a certain object in a certain object storage service system. It is configured on a bucket. In other words, the dump policy is configured on the bucket.
  • the execution of the dump policy is performed by the life cycle management module, cross-region replication module, metadata management module, storage module and business layer access module in the first object storage service system, and the life cycle module in the second object storage service system.
  • the management module, cross-region replication module, metadata management module, storage module and business layer access module are jointly implemented.
  • the cloud management platform detects the occurrence of a trigger condition and transfers the objects in the source data bucket to the destination data bucket across regions according to the dump policy.
  • the cloud management platform monitors the trigger conditions, and when the trigger conditions are detected, the objects to be dumped in the source data bucket are transferred to the destination data bucket according to the dump policy. It should be noted that after the transfer, the objects to be dumped in the source data bucket no longer exist.
  • the cloud management platform detects the occurrence of a trigger condition and transfers the objects in the source data bucket to the destination data bucket across regions according to the dump policy.
  • This step includes but is not limited to the contents of S1021 to S1022. describe.
  • Figure 6 is a schematic flow chart of a method for transferring objects to be dumped across regions provided by this application.
  • the cloud management platform sends the dump policy to the first object storage service system.
  • the first object storage service system receives the dump policy sent by the cloud management platform.
  • the cloud management platform monitors the triggering conditions, and when detecting that the triggering conditions are met, sends the dump policy to the first object storage service system, so that the first object storage service system can execute the dump policy according to the dump policy.
  • the identifier of the source data bucket, the identifier of the destination data bucket and the object to be dumped are included in the method, and the object to be dumped is transferred to the second object storage service system.
  • the cloud management platform after receiving the dump policy configured by the tenant, the cloud management platform immediately sends the dump policy to the first object storage service system, and the first object storage service system itself performs the triggering conditions Monitor, and when the trigger condition is detected, the object to be dumped will be transferred to the second object storage service system.
  • the first object storage service system transfers the object to be dumped to the second object storage service system according to the dump policy.
  • the second object storage service system receives the object to be dumped.
  • the first object storage service system determines the object to be dumped based on the identification of the source data bucket and the identification of the object to be dumped in the dump policy.
  • the life cycle management module monitors the dump time. After the dump time is reached, the object to be dumped is The storage object is dumped to the destination area.
  • the destination area is the second object storage service system or the area where the second object storage service system is located, and the object to be dumped is placed in the second object storage service system according to the dump strategy. Specified state storage.
  • the object to be dumped can be copied to the second object storage service system through the cross-region copy module in the first object storage service system, and the object to be dumped can be stored as an archive in the second object storage service system. State storage.
  • the object to be dumped can be transferred to the second object storage service system through a private network or a public network, which is not limited in this application.
  • the object to be dumped is transferred to the second object storage service system, there will be no object to be dumped in the first object storage service system.
  • the data to be dumped in the first object storage service system is deleted.
  • the first object storage service system After the first object storage service system dumps the object to be dumped to the second object storage service system, the first object storage service system updates the metadata.
  • the metadata includes the location of the object to be dumped in the first object storage service system before the dump.
  • a mapping relationship between at least one of the position in the second object storage service system, the position of the object to be dumped in the second object storage service system after dumping, and the current storage state of the object to be dumped For example, see Table 1, which is an example list of metadata provided in this application.
  • the original bucket name indicates the location of the object before dumping
  • the target information indicates the location of the object after dumping.
  • Object 1 Object 2 and Object 3 were dumped from Bucket 1 in Region 1 to Bucket 2 in Region 2, and were in the archive storage state after dumping; Object 4 was not dumped.
  • object 4 is located in bucket 1 of area 1 and is in the standard storage state in bucket 1.
  • each field is only examples.
  • the mapping relationship between the original bucket name, object name, target information and storage status is an exemplary representation.
  • the names of each field and the relationship between them are The mapping relationship between can also be in other forms, and Table 1 does not constitute a limitation of this application.
  • the operation of updating metadata in the first object storage service system can be performed by the metadata management module in the first object storage service system.
  • the second object storage service system After receiving the object to be dumped, the second object storage service system stores the object to be dumped in the storage module in an archive storage state, and updates the metadata.
  • the metadata includes the location of the object to be dumped in the second object storage service system. Location.
  • FIG 7 is a schematic diagram of the cross-region dump process provided by this application.
  • the first step is to configure the dump policy (life cycle management policy) for bucket 1 in area 1.
  • the dump policy includes the object to be dumped, dump time, destination area and after dump.
  • the destination area here is area 2.
  • the storage state of the object to be dumped in the destination area is the archive storage state.
  • the life cycle management module dumps bucket 1. Time is monitored.
  • the object to be dumped is copied to area 2 through the cross-region copy module.
  • the object to be dumped is stored in the storage module, and Archive storage state storage; after storing the object to be stored in the storage module, the metadata management module of area 2 updates the metadata.
  • the metadata includes the location of the object to be dumped in area 2.
  • the object to be dumped is located in area 2. in bucket 2; in the third step, the metadata management module of area 1 updates the metadata.
  • the metadata includes the location of the object to be dumped in area 1 before the dump, and the location of the object to be dumped in area 2 after the dump. The mapping relationship between the location and the storage status of the object to be dumped in area 2.
  • this application provides a cross-region dump method based on object storage services.
  • the method can realize cross-region dump of objects.
  • the tenant only needs to configure the dump policy for the target bucket on the cloud management platform to trigger the dump.
  • the cloud storage system can automatically implement the dump task according to the dump policy, so that the objects in the standard storage state in the first area can be dumped to the second area, and stored in the archive storage state in the second area, realizing By integrating data in the east and memory in the west, storage costs can be reduced.
  • the object to be dumped is stored in the second object storage service system, and there is no object to be dumped in the first object storage service system.
  • the object is dumped, but the metadata of the object to be dumped is recorded in the first object storage service system.
  • the metadata includes the location of the object to be dumped in the first object storage service system before dumping, the location of the object to be dumped after dumping, and the location of the object to be dumped after dumping.
  • the location of the stored object in the second object storage service system Therefore, according to the metadata in the first object storage service system, the tenant can also access the object to be dumped.
  • the embodiment of this application provides a cross-region dump method based on object storage service.
  • the method describes how to access the object to be dumped. See Figure 8.
  • Figure 8 is another object storage service-based method provided by this application.
  • Process diagram of cross-region dump method The method includes, but is not limited to, the following description.
  • the cloud management platform receives a request from the tenant, and the request is used to indicate a request to access the object to be dumped.
  • the tenant sends a request to the cloud management platform through the application software on the terminal device, and the request is used to indicate the request to access the object to be dumped.
  • the cloud management platform receives the request sent by the tenant through the terminal device.
  • the request carries the tenant's identity and the data identity requested by the tenant.
  • the cloud management platform migrates the objects to be dumped from the destination data bucket to the source data bucket across regions, and provides the objects to be dumped in the source data bucket to the tenant.
  • This step may include but is not limited to the description of the contents in S2021 to S2025.
  • Figure 9 is a schematic flow chart of a method provided by this application for migrating objects to be dumped from a destination data bucket to a source data bucket across regions.
  • the cloud management platform sends the request to the first object storage service system.
  • the first object storage service system receives the request sent by the cloud management platform.
  • the first object storage service system requests the object to be converted from the second object storage service system according to the request.
  • the first object storage service system receives the request sent by the cloud management platform, queries metadata according to the request, determines the area or object storage service system where the data requested by the tenant is located, and sends a request to the object storage service system.
  • the object to be dumped is located in the second object storage service system, and the first object storage service system sends a request to the second object storage service system.
  • the second object storage service system returns the object to be converted to the first object storage service system.
  • the second object storage service system After receiving the request, the second object storage service system returns the object to be dumped to the first object storage service system according to the request. After receiving the object to be dumped, the first object storage service system stores the object to be dumped in a standard storage state. .
  • the cross-region copy module in the second object storage service system may copy the object to be dumped to the first object storage service system.
  • the first object storage service system sends a prompt message to the cloud management platform.
  • the prompt message is used to prompt the first object storage service system to complete obtaining the object to be dumped from the second object storage service system.
  • the first object storage service system After obtaining the object to be dumped, the first object storage service system sends a prompt message to the cloud management platform.
  • the prompt message is used to prompt the first object storage service system to complete the acquisition of the object to be dumped from the second object storage service system.
  • the cloud management platform sends a prompt message to the tenant.
  • the cloud management platform sends a prompt message to the terminal device where the tenant is located, so that the tenant can download the object to be dumped from the first object storage service system to the terminal device. After the terminal device where the tenant is located receives the prompt message, the tenant can download the object to be dumped to the terminal device.
  • the tenant only needs to click to obtain the data on the terminal device, and the object to be dumped can be copied from the second object storage service system to the first object storage service system across regions, so that The data is stored in the first object storage service system, and the tenant can download the data in the first object storage service system through the terminal device.
  • steps S2021 to S2025 are imperceptible to tenants.
  • FIG 10 is a schematic diagram of retrieving data provided by an embodiment of the present application.
  • the cloud management platform receives a request from a tenant, the request is used to indicate a request to access the object to be archived, and the data dumped to area 2 and stored in archive storage state needs to be retrieved to area 1.
  • the objects to be dumped in the archive storage state are copied from area 2 to area 1, and stored in the standard storage state in area 1; in the second step, area 1
  • a prompt message is sent to the tenant through the cloud management platform. The prompt message is used to remind that the object to be dumped has been copied from area 2 to area 1.
  • the tenant can access the object to be dumped through the business access module.
  • the tenant retrieves data
  • the data can be dumped from the first object storage service system to the second object storage service system, so that the data can be stored in the second object storage system.
  • the service system is stored in archive storage state, and the entire dump process is unaware of tenants.
  • the tenant needs to access data, he can click on the terminal device to obtain the data. After the data is obtained successfully, the terminal device receives a prompt message, and the tenant can download the data to the terminal device according to the prompt message to obtain the data. It can be seen that the data dump does not affect the tenant's use of cloud services.
  • FIG 11 is a schematic structural diagram of a cloud management platform 200 provided by this application.
  • the cloud management platform 200 is used to manage the infrastructure that provides object storage services.
  • the infrastructure includes a third server located in the first area.
  • the configuration interface 210 is used to receive the dump policy configured by the tenant.
  • the dump policy includes the identity of the source data bucket, the identity of the destination data bucket, and dumps the objects to be dumped in the source data bucket to the destination data bucket.
  • the trigger condition where the source data bucket and the destination data bucket It is located in different regions, and the storage medium that is implemented in the destination data bucket in the infrastructure after dumping is tape or optical disk;
  • the detection module 220 is used to detect the occurrence of trigger conditions and transfer the objects in the source data bucket to the destination data bucket across regions according to the dump policy.
  • cloud management also includes:
  • the communication module 230 is used to receive the tenant's access request for the object to be dumped in the source data bucket;
  • the migration module 240 is used by the cloud management platform to migrate objects to be dumped from the destination data bucket across regions to the region where the source data bucket is located;
  • the communication module 230 is also configured to provide the objects to be dumped in the area where the source data bucket is located to the tenant.
  • the storage medium implemented in the source data bucket in the infrastructure is a mechanical hard disk or a solid state disk.
  • the cloud management platform charges the tenant for the source data bucket higher than the billing fee for the destination data bucket.
  • triggering conditions include any one or more of the following:
  • the triggering condition includes the identification of the object to be dumped in the source data bucket.
  • the identification of the object to be dumped includes specific characters contained in the name of the object to be dumped.
  • the region where the destination data bucket is located and/or the destination data bucket is specified by the tenant or automatically selected by the cloud management platform.
  • the configuration interface 210, the detection module 220, the communication module 230, and the migration module 240 can all be implemented by software, or can be implemented by hardware. Illustratively, the following takes the detection module 220 as an example to introduce the implementation of the detection module 220 . Similarly, the implementation of the configuration interface 210, the communication module 230, and the migration module 240 can refer to the implementation of the detection module 220.
  • the detection module 220 may include code running on the cloud management platform.
  • the cloud management platform may be a computing device in a cloud service, where the computing device may be, for example, a bare metal server, a virtual machine, a container, etc. Further, the computing device may be one or more.
  • detection module 220 may include code running on multiple cloud management platforms. It should be noted that multiple computing devices used to run the code can be distributed in the same region (region) or in different regions. Further, multiple computing devices used to run the code can be distributed in the same availability zone (AZ) or in different AZs. Each AZ includes a data center or multiple geographically close locations. of data centers. Among them, usually a region can include multiple availability zones AZ.
  • VPC virtual private cloud
  • multiple computing devices used to run the code can be distributed in the same virtual private cloud (VPC) or across multiple VPCs.
  • VPC virtual private cloud
  • Cross-region communication between two VPCs in the same region and between VPCs in different regions requires a communication gateway in each VPC, and the interconnection between VPCs is realized through the communication gateway. .
  • the detection module 220 may include at least one computing device, such as a server, a virtual machine, a container, etc.
  • the detection module 220 may also be a device implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD).
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above-mentioned PLD can be a complex programmable logical device (CPLD), a field-programmable gate array (field-programmable gate array, FPGA), a general array logic (generic array logic, GAL), or any combination thereof.
  • CPLD complex programmable logical device
  • FPGA field-programmable gate array
  • GAL general array logic
  • Multiple computing devices included in the detection module 220 may be distributed in the same region or in different regions. Multiple computing devices included in the detection module 220 may be distributed in the same AZ or in different AZs. Similarly, multiple computing devices included in the detection module 220 may be distributed in the same VPC or in multiple VPCs.
  • the plurality of computing devices may be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.
  • the detection module 220 can be used to perform any steps in a cross-region dump method based on object storage services.
  • the configuration interface 210, the detection module 220, the communication module 230, and the migration module 240 Can be used to perform any steps in a cross-region dump method based on object storage services.
  • the steps responsible for implementation by the configuration interface 210, the detection module 220, the communication module 230, and the migration module 240 can be specified as needed, through the configuration interface 210 , the detection module 220, the communication module 230, and the migration module 240 respectively implement different steps in a cross-region dump method based on object storage services to realize all functions of the cloud management platform 200.
  • FIG 12 is a schematic structural diagram of a computing device 300 provided by this application.
  • the computing device 300 is such as a bare metal server, a virtual machine, a container, etc.
  • the computing device 300 can be configured as a cloud management platform in the method embodiment.
  • Computing device 300 includes: bus 302, processor 304, memory 306, and communication interface 308.
  • the processor 304, the memory 306 and the communication interface 308 communicate through the bus 302. It should be understood that this application does not limit the number of processors and memories in the computing device 300.
  • the bus 302 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, or the like.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus can be divided into address bus, data bus and control bus wait. For ease of presentation, only one line is used in Figure 12, but it does not mean that there is only one bus or one type of bus.
  • Bus 302 may include a path that carries information between various components of computing device 300 (eg, memory 306, processor 304, communications interface 308).
  • the processor 304 may include a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP) or a digital signal processor (DSP). any one or more of them.
  • CPU central processing unit
  • GPU graphics processing unit
  • MP microprocessor
  • DSP digital signal processor
  • Memory 306 may include volatile memory, such as random access memory (RAM).
  • RAM random access memory
  • the processor 304 may also include non-volatile memory (non-volatile memory), such as read-only memory (ROM), flash memory, mechanical hard disk drive (hard disk drive, HDD) or solid state drive (solid state drive). drive, SSD).
  • ROM read-only memory
  • HDD hard disk drive
  • SSD solid state drive
  • the memory 306 stores executable program code, and the processor 304 executes the executable program code to realize the functions of the aforementioned configuration interface 210, detection module 220, communication module 230, and migration module 240, thereby realizing an object-based storage system.
  • Cross-region dump method for services That is, the memory 306 stores instructions for executing a cross-region dump method based on an object storage service.
  • the communication interface 308 uses transceiver modules such as, but not limited to, network interface cards and transceivers to implement communication between the computing device 300 and other devices or communication networks.
  • the communication module 230 may be located in the communication interface 308, for example.
  • An embodiment of the present application also provides a computing device cluster.
  • the computing device cluster includes at least one computing device.
  • the computing device may be a server, a virtual machine, or a container, such as a central server or an edge server.
  • Figure 13 is a schematic structural diagram of a computing device cluster provided by this application.
  • the computing device cluster includes at least one computing device 300.
  • the same instructions for executing a cross-region dump method based on an object storage service may be stored in the memory 306 of one or more computing devices 300 in the computing device cluster.
  • the memory 306 of one or more computing devices 300 in the computing device cluster may also store partial instructions for executing a cross-region dump method based on an object storage service.
  • a combination of one or more computing devices 300 may be used to jointly execute instructions for a cross-region dump method based on an object storage service.
  • the memory 306 in different computing devices 300 in the computing device cluster can store different instructions, respectively used to execute some functions of the cloud management platform. That is, the instructions stored in the memory 306 in different computing devices 300 can implement one or more of the storage resource provision module 201, the intra-host management module 202, the partitioning module 203, the inter-host management module 204, and the communication module 205. Function.
  • one or more computing devices in a cluster of computing devices may be connected through a network.
  • the network may be a wide area network or a local area network, etc.
  • Figure 14 shows a possible implementation. As shown in Figure 14, two computing devices 300A and 300B are connected through a network. Specifically, the connection to the network is made through a communication interface in each computing device.
  • instructions for executing the functions of the configuration interface 210 and the communication module 230 are stored in the memory 306 of the computing device 300A.
  • instructions for executing the functions of the detection module 220 and the migration module 240 are stored in the memory 306 of the computing device 300B.
  • the connection method between computing device clusters shown in Figure 14 is that the computing device 300A includes a configuration interface 210 and a communication module 230.
  • the processor 304 on the computing device 300A can execute the code of the configuration interface 210 and the communication module 230 in the memory 306.
  • the code is used to implement the interaction between the cloud management platform and the tenant.
  • the computing device 300A is used to receive the dump policy configured by the tenant, and is also used to receive the tenant's access request.
  • the processor 304 on the computing device 300B can execute The code of the detection module 220 and the code of the migration module 240 in the memory 306 are used to monitor the dump strategy and are also used to implement cross-region transfer or migration of objects.
  • the functions of the computing device 300A shown in FIG. 14 can also be completed by multiple computing devices 300, or the cloud management platform includes multiple computing devices with the same functions as the computing device 300A.
  • the functions of the computing device 300B can also be completed by multiple computing devices 300, or the cloud management platform includes multiple computing devices with the same functions as the computing device 300B.
  • the embodiment of the present application also provides another computing device cluster.
  • the connection relationship between the computing devices in the computing device cluster can be similar to the connection method of the computing device cluster described in FIG. 13 and FIG. 14 .
  • the memory 306 of one or more computing devices 300 in the computing device cluster may store different instructions for executing a cross-region dump method based on an object storage service.
  • the memory 306 of one or more computing devices 300 in the computing device cluster may also store partial instructions for executing a cross-region dump method based on an object storage service.
  • a combination of one or more computing devices 300 may jointly execute instructions for performing a cross-region dump method based on an object storage service.
  • An embodiment of the present application also provides a computer program product containing instructions.
  • the computer program product may be a software or program product containing instructions capable of running on a computing device or stored in any available medium.
  • the computer program product is run on at least one computing device, at least one computing device is caused to execute a cross-region dump method based on an object storage service.
  • An embodiment of the present application also provides a computer-readable storage medium.
  • the computer-readable storage medium may be a computing device capable of storing Any available media or a data storage device such as a data center containing one or more available media.
  • the available media may be magnetic media (eg, floppy disk, hard disk, tape), optical media (eg, DVD), or semiconductor media (eg, solid state drive), etc.
  • the computer-readable storage medium includes instructions that instruct a computing device or a cluster of computing devices to perform a cross-region dump method based on an object storage service.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

本申请提供了一种基于对象存储服务的跨区域转储方法及相关装置，所述方法应用于对象存储领域，包括：云管理平台提供配置接口，配置接口用于接收租户配置的转储策略，转储策略包括源数据桶的标识、目的数据桶的标识、将源数据桶中的待转储对象转储至目的数据桶中的触发条件，其中，源数据桶和目的数据桶位于不同区域，且转储后在基础设施中实现在目的数据桶的存储介质为磁带或光盘；云管理平台检测触发条件发生，根据转储策略将源数据桶的待转储对象跨区域转移至目的数据桶中。实施本申请，解决了数据产生地区数据中心的高成本问题，可以把需要长期存储的数据自动迁移到其他低成本的数据中心，解决国家东数西存的问题。

Description

一种基于对象存储服务的跨区域转储方法及相关装置
本申请要求于2022年07月04日提交中国专利局、申请号为202210779562.5、申请名称为“一种基于对象存储服务OBS的跨区域转储系统”的中国专利申请的优先权，以及要求于2022年09月30日提交中国专利局、申请号为202211215542.1、申请名称为“一种基于对象存储服务的跨区域转储方法及相关装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及云技术领域，尤其涉及一种基于对象存储服务的跨区域转储方法及相关装置。
背景技术
归档存储是一种针对冷数据安全且低成本的存储方式，适用于访问频率低、需要持久存储的数据，如日志审计数据，安防监控数据等。租户在使用云服务的过程中，产生大量的数据，这些数据经过一段时间后，被访问的频率很少，考虑到数据需要长期存储，且为了节能、降低存储成本，一般会将这些数据转储为归档存储。
国内云服务数据的产生大部分是在东部地区，但东部地区建立数据中心或存储设备的成本较高，数据中心或存储设备通常建立在西部地区，这就需要将东部地区的数据转储到西部地区的数据中心或存储设备中，以实现东数西存。
发明内容
本申请提供了一种基于对象存储服务的跨区域转储方法，解决了数据产生地区数据中心的高成本问题，可以把需要长期存储的数据自动迁移到其他低成本的数据中心，解决国家东数西存的问题。
第一方面，本申请提供了一种基于对象存储服务的跨区域转储方法，所述方法应用于云管理平台，所述云管理平台用于管理提供对象存储服务的基础设施，所述基础设施包括设置在第一区域的第一对象存储服务数据桶和设置在第二区域的第二对象存储服务数据桶，所述方法包括：
云管理平台提供配置接口，所述配置接口用于接收租户配置的转储策略，所述转储策略包括源数据桶的标识、目的数据桶的标识、将所述源数据桶中的待转储对象转储至所述目的数据桶中的触发条件，其中，所述源数据桶和所述目的数据桶位于不同区域，且转储后在所述基础设施中实现在所述目的数据桶的存储介质为磁带或光盘；所述云管理平台检测所述触发条件发生，根据所述转储策略将所述源数据桶的对象跨区域转移至所述目的数据桶中。
可以看到，本申请提供了一种基于对象存储服务的跨区域转储方法，租户可通过云管理平台配置转储策略，云管理平台根据转储策略将待转储对象从一个区域转储至另一个区域，且转储后实现待转储对象在目的数据桶的存储介质为磁带或光盘。实施本申请，可实现对象的跨区域转储，能够解决国家东数西存的问题，降低存储成本，降低租户的存储计费费用，提升用户使用体验。
基于第一方面，在可能的实现方式中，所述云管理平台接收所述租户针对所述源数据桶中的待转储对象的访问请求；所述云管理平台将所述待转储对象从所述目的数据桶跨区域迁移至所述源数据桶所在的区域，并将所述源数据桶所在的区域中的所述待转储对象提供给所述租户。
可以看到，在跨区域转储之后，云管理平台还可以将待转储对象从目的数据桶中跨区域迁移回源数据桶所在的区域，并将待转储对象提供给租户，不影响租户的使用。
基于第一方面，在可能的实现方式中，在所述基础设施中实现在所述源数据桶的存储介质为机械硬盘或固态硬盘。
基于第一方面，在可能的实现方式中，所述云管理平台针对所述源数据桶向所述租户收取的计费费用高于针对所述目的数据桶向所述租户收取的计费费用。
可以理解，有些区域的基础设备所需的存储成本高，有些区域的基础设备所需的存储成本低，通过实施本申请，将存储成本高的区域的数据转移至存储成本低的区域，可以降低租户的计费费用，提高用户的 使用体验。
基于第一方面，在可能的实现方式中，所述触发条件包括下述任意一种或多种：
i)从配置所述转储策略开始计算时长，时长达到预设时长；
ii)所述源数据桶中已占用容量达到阈值。
基于第一方面，在可能的实现方式中，所述触发条件包括所述源数据桶中待转储对象的标识。
基于第一方面，在可能的实现方式中，所述待转储对象的标识包括待转储对象名称中包含特定字符。
基于第一方面，在可能的实现方式中，所述目的数据桶所在的区域和/或所述目的数据桶由所述租户指定或由所述云管理平台自动选择。
第二方面，本申请提供了一种云管理平台，所述云管理平台用于管理提供对象存储服务的基础设施，所述基础设施包括设置在第一区域的第一对象存储服务数据桶和设置在第二区域的第二对象存储服务数据桶，包括：
配置接口，所述配置接口用于接收租户配置的转储策略，所述转储策略包括源数据桶的标识、目的数据桶的标识、将所述源数据桶中的待转储对象转储至所述目的数据桶中的触发条件，其中，所述源数据桶和所述目的数据桶位于不同区域，且转储后在所述基础设施中实现在所述目的数据桶的存储介质为磁带或光盘；
检测模块，用于检测所述触发条件发生，根据所述转储策略将所述源数据桶的对象跨区域转移至所述目的数据桶中。
基于第二方面，在可能的实现方式中，所述云管理平台还包括：
通信模块，用于接收所述租户针对所述源数据桶中的待转储对象的访问请求；
迁移模块，用于所述云管理平台将所述待转储对象从所述目的数据桶跨区域迁移至所述源数据桶所在的区域；
所述通信模块还用于，并将所述源数据桶所在的区域中的所述待转储对象提供给所述租户。
基于第二方面，在可能的实现方式中，在所述基础设施中实现在所述源数据桶的存储介质为机械硬盘或固态硬盘。
基于第二方面，在可能的实现方式中，所述云管理平台针对所述源数据桶向所述租户收取的计费费用高于针对所述目的数据桶向所述租户收取的计费费用。
基于第二方面，在可能的实现方式中，所述触发条件包括下述任意一种或多种：
i)从配置所述转储策略开始计算时长，时长达到预设时长；
ii)所述源数据桶中已占用容量达到阈值。
基于第二方面，在可能的实现方式中，所述触发条件包括所述源数据桶中待转储对象的标识。
基于第二方面，在可能的实现方式中，所述待转储对象的标识包括待转储对象名称中包含特定字符。
基于第二方面，在可能的实现方式中，所述目的数据桶所在的区域和/或所述目的数据桶由所述租户指定或由所述云管理平台自动选择。
第二方面的各个功能模块用于实现上述第一方面或第一方面的任意一种可能的实现方式所述的方法。
第三方面，本申请提供了一种计算设备集群，包括至少一个计算设备，所述至少一个计算设备中的每个计算设备包括存储器和处理器，所述至少一个计算设备的处理器用于执行所述至少一个计算设备的存储器中存储的指令，使得所述计算设备集群执行上述第一方面或第一方面的任意一种可能的实现方式所述的方法。
第四方面，本申请提供了一种计算机可读存储介质，包括程序指令，当所述程序指令由计算设备集群执行时，所述计算设备集群执行上述第一方面或第一方面的任意一种可能的实现方式所述的方法。
第五方面，本申请提供了一种系统，包括云管理平台、设置在第一区域的第一对象存储服务数据桶和设置在第二区域的第二对象存储服务数据桶，所述云管理平台为上述第一方面或第一方面的任意一种可能的实现方式中所述的云管理平台。
附图说明
图1为本申请提供的一种系统架构示意图；
图2为本申请提供的一种对象存储服务系统的结构示意图；
图3为本申请提供的一种场景示意图；
图4为本申请提供的一种基于对象存储服务的跨区域转储方法的流程示意图；
图5为本申请提供的一种界面示意图；
图6为本申请提供的一种将待转储对象跨区域转移的方法流程示意图；
图7为本申请提供的一种跨区域转储过程的示意图；
图8为本申请提供的又一种基于对象存储服务的跨区域转储方法的流程示意图；
图9为本申请提供的又一种将待转储对象跨区域转移的方法流程示意图；
图10为本申请提供的又一种跨区域转储过程的示意图；
图11为本申请提供的一种云管理平台的结构示意图；
图12为本申请提供的一种计算设备的结构示意图；
图13为本申请提供的一种计算设备集群的结构示意图；
图14为本申请提供的又一种计算设备集群的结构示意图。
具体实施方式
本申请提供了一种云存储系统，所述云存储系统为分布式存储系统，所述云存储系统中包括一个或多个对象存储服务系统，其中每个对象存储服务系统中可以包括一个或多个云存储设备。
在云存储系统包括多个对象存储服务系统的情况下，多个对象存储服务系统可以位于不同的区域，比如，多个对象存储服务系统包括第一对象存储服务系统、第二对象存储服务系统，其中，第一对象存储服务系统位于东部地区，第二对象存储服务系统位于西部地区。第一对象存储服务系统和第二对象存储服务系统所位于的区域仅仅用于举例，多个对象存储服务系统还可以位于其他区域，本申请不做限定。
云存储系统还可以包括云管理平台，云管理平台用于负责对多个对象存储服务系统中的各个云存储设备中的数据进行管理。比如，租户可以通过登录云管理平台，对某个对象存储服务系统中的某个云存储设备中的数据进行删除或迁移等。云管理平台可以位于任一区域中的任一计算设备上，计算设备例如可以是裸金属服务器、容器等。
可以理解，数据在不同区域的存储代价并不相同，例如，在不同区域建立对象存储服务系统和使用对象存储服务系统的代价并不相同，有的区域代价较高，有的区域代价较低，其中存储代价包括建立对象存储服务系统和使用对象存储服务系统的资金成本。比如，在东部地区建立对象存储服务系统的存储代价较高，在西部地区建立对象存储服务系统的存储代价较低。
本申请提供了又一种系统，参见图1所示，图1为本申请提供的又一种系统架构示意图，该系统涉及终端设备110、网络设备120和云存储系统130。
云存储系统130为上述系统架构中的云存储系统，可以包括一个或多个对象存储服务系统，多个对象存储服务系统可以位于不同的区域。每个对象存储服务系统中包括一个或多个云存储设备。本申请中，云存储设备指的是以对象的形式存储数据的设备，例如可以是对象存储设备(object storage service，OBS)，对象存储设备又可称为OBS桶。云存储设备用于接收并存储租户通过终端设备发送的数据。
终端设备110，可以是位于云存储系统130下的租户所使用的手机、台式计算机、笔记本等，也可以是云存储系统130下的租户在云存储系统130所购买的虚拟机、容器或裸金属服务器(bare metal server，BMS)等。终端设备110上安装有应用软件(application，简称app)或小程序，租户可以通过该应用软件或小程序对数据进行管理，比如通过该应用软件或小程序向云存储系统130上传数据，通过该应用软件或小程序在云存储系统130上下载数据，通过该应用软件或小程序删除云存储系统130上的某个或某些数据。
可以理解，在通常情况下，租户在上传数据时，将数据上传至租户所在区域的对象存储服务系统中，而不会跨区域将数据存储至其他区域的对象存储服务系统中。例如，租户所在的区域为广东省，则租户会将数据上传至广东省区域的对象存储服务系统中。租户在上传数据时，选择租户所在区域的对象存储服务系统，通过新建一个桶(bucket)或者选择一个桶，将数据上传至该桶中。其中，桶是云存储系统130中存储对象的容器。桶在被创建时，需要选择在哪个区域创建桶，即确定了桶所归属的区域，例如，在广东省区域所在的对象存储服务系统中创建桶，桶所归属的区域为广东省区域。需要说明的是，桶不能够跨区域。可以理解，桶是具有属性的，桶的属性比如包括桶所归属的区域。
网络设备120用于终端设备110通过任何通信机制/通信标准的通信网络与云存储系统130之间传输数据。其中，通信网络可以是广域网、局域网、点对点连接等方式，或它们的任意组合。
本申请还提供了一种云存储设备，参见图2，图2为本申请提供的一种对象存储服务系统的结构示意图。对象存储服务系统包括业务接入模块、生命周期管理模块、跨区域复制模块、元数据管理模块和存储模块，下面介绍一下各个模块的功能。
业务接入模块，用于提供对外服务的应用程序编程接口(application programming interface，API)，并提供认证鉴权等功能。租户在通过终端设备上传数据时，先访问业务接入模块，业务接入模块对其进行认证鉴权，认证鉴权通过后，将数据写入存储模块。其中，数据在云存储设备中是以对象的形式存储的。
元数据管理模块，用于在数据写入存储模块之后，生成数据的元数据，其中元数据包括对象名称、对象存储位置、对象大小、上传时间、所有者等。元数据管理模块中存储有元数据列表，元数据列表中包括对象名称、对象存储位置、对象大小、上传时间、所有者等之间的映射关系。元数据管理模块还用于对元数据进行管理，比如在有数据写入存储模块的情况下或者在有数据被删除的情况下，更新元数据列表。
存储模块，用于存储数据。数据在存储模块中存在两种存储状态：标准存储和归档存储。对于访问频率比较高的数据，适宜存储为标准存储状态，对于访问频率比较低或极低的数据，适宜存储为归档存储状态。实际应用中，可以根据具体应用场景和具体访问频率，确定哪些数据适宜标准存储哪些数据适宜归档存储，本申请对访问频率的具体划分界限不做限定。可选的，存储模块中包括标准存储介质和归档存储介质，标准存储介质可以是机械硬盘(HDD)或固态硬盘(SSD)，归档存储介质可以是磁带或光盘，关于存储介质这里仅仅用于举例，本申请对于存储介质不做限定。
可以理解，对象存储服务系统中对象的存储状态还可以是其他状态，本申请不做限定。例如可以是低频存储状态，低频存储状态指的是介于标准存储状态和归档存储状态之间的一个状态，可以将访问频率较低但访问频率高于处于归档存储状态的数据存储为低频存储状态。例如，在一种示例中，可以将冷数据存储为归档存储状态，将热数据存储为标准存储状态，将温数据存储为低频存储状态，关于冷数据、热数据、温数据的划分界限本申请不做限定，实际应用中，可以根据具体应用场景具体划分。低频存储介质本申请不做限定。生命周期管理模块，用于根据租户配置的生命周期管理策略对存储模块中的对象进行生命周期管理。租户可以通过云管理平台对云存储设备中的对象配置生命周期管理策略，实现生命周期管理。比如，租户可以登录云管理平台，选择目标云存储设备中的目标对象，对目标对象配置生命周期管理策略，生命周期管理策略包括时间管理和存储状态管理，例如，多少天后将目标对象由标准存储状态转为归档存储状态，又例如，将目标对象由归档存储状态转为标准存储状态。具体的，生命周期管理模块用于基于租户配置的生命周期管理策略对存储模块中的对象进行监控，在监控达到配置的时间后，执行存储状态转换。
跨区域复制模块，用于将数据从一个区域复制发送到另一个区域中，实现跨区域的数据分发或备份。例如，可以将区域1中的部分对象复制发送至区域2中，在区域2中以对象的形式存储。可以理解，租户可以通过登录云管理平台，选择需要转储的对象，将选择的对象通过跨区域复制模块复制至目标区域。
可以理解，租户在配置生命周期管理策略时，一般是针对桶进行配置，也即在桶上配置生命周期管理策略，可以选择一个桶中的某个对象，配置这个对象的生命周期管理策略，也可以从一个桶中选择部分对象或全部对象，针对选择的部分对象或全部对象配置生命周期管理策略。选择部分对象时可以根据对象名称进行选择，例如选择一个桶中对象名称包括特定字符的这些对象，比如，可以是对象名称以abc字符为前缀的对象，可以是对象名称中包括abc字符的对象，等等；选择对象时还可以根据数据上传时间进行选择，例如选择数据上传时间在某年某月某日之前上传的数据；选择对象时还可以根据其他条件进行选择，比如，选择创建时间大于或等于30天的对象，本申请对如何选择对象不做限定。
可以理解，桶是一个逻辑概念。一个桶中的对象可以全部是处于标准存储状态的对象，也可以全部是处于归档存储状态的对象，也可以部分对象处于标准存储状态部分对象处于归档存储状态，本申请对桶中对象所处的状态不做限定。可以理解，图2中各个功能模块可以部署在一个对象存储服务系统中的一台云存储设备上，也可以分布式部署在一个对象存储服务系统中的多台云存储设备上，比如，部分模块部署在一个对象存储服务系统中的其中一台云存储设备上，剩余模块部署在另一台云存储设备上，本申请对各个模块的部署位置不做限定。图2中，对象存储服务系统中各个功能模块的划分仅仅是一种示例，实际应用中，可以根据具体功能具体划分为更多或更少的模块，本申请不做限定。
本申请提供了一种基于对象存储服务OBS的跨区域转储方法，下面结合图3所示的场景示意图，描述本申请提供的一种基于对象存储服务OBS的跨区域转储方法。
如图3所示，欲将区域1中的桶1中的对象跨区域转储至区域2中，且目前对象在桶1中处于标准存 储状态，转储后对象在桶2中处于归档存储状态，其中，对象在区域1的存储代价高于在区域2的存储代价，例如，区域1可以是东部地区，区域2可以是西部地区。
本申请提供了一种跨区域转储方法，所述方法包括但不限于以下内容的描述。
1)租户选择区域1的桶1中的数据，将数据通过跨区域复制模块，将数据复制至区域2中，对象在区域2中是以标准存储状态存储的。可选的，对象由区域1的桶1复制至区域2可以通过专用线路，也可以通过公网，本申请不做限定。
其中，待转储对象复制至区域2中后，具体存储在区域2中的哪个桶中是由云存储系统分配确定的，不是由租户选择确定的。这里，假设待转储对象存储在区域2中的桶2中。
2)租户在区域2的桶2上配置生命周期管理策略，生命周期管理模块根据生命周期管理策略将对象由标准存储状态转为归档存储状态。例如，租户配置的生命周期管理策略包括在30天后将桶2中的对象由标准存储状态转为归档存储状态，生命周期管理模块根据生命周期管理策略进行时间监控，在达到30天时，将桶2中的对象转为归档存储状态。
3)删除区域1中桶1中的对象。
为了降低存储成本，在将桶1中的对象转储至桶2中进行归档存储后，可以将区域1中桶1中的对象删除。可选的，可以选择经过一段时间后再删除桶1中的对象，或者配置删除策略，设置在一段时间后再删除。
可以理解，这种跨区域转储方法，需要租户从区域1中的桶1中人工选择待转储对象，将待转储对象复制至区域2的桶2中，对区域2中的桶2配置生命周期管理策略，再在区域1的桶1上配置删除策略，在数据量很大的情况下操作比较繁琐，且由于不确定桶1中的对象什么时候复制完成，因此不确定桶2的生命周期管理策略什么时候可以配置，这就导致对象复制完成与在桶2上配置生命周期管理策略可能存在时间间隔，从而导致转储时间较长。另外，该方案实施起来比较复杂，因为当将区域1中的对象复制至区域2后，对象存储位置发生了变化，但是租户的终端设备中记录的数据的归属桶信息并未更新，因此有可能导致租户在访问数据时访问失败，若要实时更新终端设备中数据的归属桶信息，实施起来非常困难。数据取回时，需要人为先将数据从区域2的归档存储状态转为标准存储状态，再由区域2中复制至区域1中，操作复杂。
本申请还提供了一种基于对象存储服务的跨区域转储方法，参见图4所示，图4为本申请提供的一种基于对象存储服务的跨区域转储方法的流程示意图，所述方法包括但不限于以下内容的描述。
S101、云管理平台接收租户配置的转储策略，转储策略用于指示将第一对象存储服务系统中的待转储对象转储至第二对象存储服务系统中。
云存储系统中包括多个对象存储服务系统，多个对象存储服务系统中包括第一对象存储服务系统和第二对象存储服务系统，其中，第一对象存储服务系统和第二对象存储服务系统位于云存储系统中的不同区域，数据在第一对象存储服务系统所在区域的存储代价高于数据在第二对象存储服务系统所在区域的存储代价，换句话说，云管理平台针对数据存储在第一对象存储服务系统中的计费费用，高于所述数据存储在第二对象存储服务系统中的计费费用。例如，第一对象存储服务系统所在区域为东部地区，第二对象存储服务系统所在区域为西部地区。
租户登录云管理平台，在云管理平台上配置转储策略，云管理平台接收租户配置的转储策略。可以理解，云管理平台上提供了配置接口，配置接口用于接收租户配置的转储策略。转储策略用于指示将第一对象存储服务系统中的待转储对象转储至第二对象存储服务系统中，转储策略中可以包括源数据桶的标识、目的数据桶的标识和源数据桶中待转储对象转储至目的数据桶中的触发条件。
触发条件可以包括源数据桶中待转储对象的标识，其中，待转储对象的标识例如可以是待转储对象的名称，例如，待转储对象可以是对象名称中包含特定字符的对象。
待转储对象可以根据对象名称中包含的特定字符来确定，比如，将第一对象存储服务系统中的桶1中，对象名称中包含特定字符abc的对象确定为待转储对象，又比如，将第一对象存储服务系统中的桶1中，对象名称的前缀为特定字符abc的对象确定为待转储对象，等等，特定字符可以是任意字符，本申请不做限定。待转储对象还可以根据其他条件来确定，比如，根据上传时间在某年某月某日之前上传的数据确定为待转储对象等，本申请不做限定。
目的数据桶所在的区域指的是待转储对象转储至哪个对象存储服务系统中，或者指的是待转储对象转储至哪个区域中，例如，本申请中，目的区域可以是第二对象存储服务系统或者是第二对象存储服务系统 所在的区域。目的数据桶所在的区域可以由租户指定，比如，租户指定目的数据桶所在的区域为区域2，也可以由云管理平台自动选择。云管理平台中预先设置了目标区域的选择策略或算法，目标区域的选择策略或算法可以是与转储成本相关，转储成本例如可以包括传输时间、传输所消耗的网络带宽、对象在目标区域的存储成本中的一项或多项，选择策略或算法还可以通过其他方式确定，本申请不做限定。可选的，目的数据桶的标识可以由租户指定，也可以由云管理平台自动选择。
触发条件可以包括以下任意一种或多种：1)从配置转储策略开始计算时长，时长达到预设时长的条件下；2)源数据桶中已占用容量达到阈值。在一种示例中，可以设置预设时长(也可称为转储时间)为0，即配置完转储策略后立即进行转储，将源数据桶中的待转储对象转储至目的数据桶中；也可以设置预设时长为多少天后转储，比如，30天后转储，则从配置转储策略开始计算，达到30天时将源数据桶中的待转储对象转储至目的数据桶中。在又一种示例中，可以设置源数据桶的已占用容量的阈值，当源数据桶中已占用容量达到阈值的情况下，则执行转储。本示例中，预设时长、已占用容量的阈值可以根据具体场景具体设置，本申请不做限定。触发条件还可以是其他条件，本申请不做限定。
转储前，待转储对象在第一对象存储服务系统中处于标准存储状态，转储后，待转储对象在第二对象存储服务系统中处于归档存储状态。可选的，若需要待转储对象在第二对象存储服务系统中处于标准存储状态，也可以设置为标准存储状态。
可选的，转储策略中包括源数据桶的标识，桶的标识能够唯一标识云存储系统中的一个桶，换言之，在整个云存储系统中，每个桶的标识是唯一的。桶的标识例如可以是桶1、桶2、桶3，也可以是桶a、桶b、桶c，还可以是其他标识等，本申请不做限定。可以理解，根据桶的标识，可以确定是哪个桶中的数据需要转储，根据待转储对象的标识可以确定哪个桶中的哪些数据需要转储。
参见图5所示，图5为本申请提供的一种界面示例图，租户登录云管理平台后，在云管理平台上配置转储策略，本示例中，待转储对象包括对象名称的前缀为字符abc的对象，转储时间为30天后，选择立即配置转储后的状态为归档存储状态，目标区域选择为区域2。图5提供的配置转储策略的界面示意图仅仅是一种示例，并不构成对本申请的任何限定，配置转储策略的界面还可以是其他形式，界面中还可以包括更多或更少的功能字段，本申请不做限定。
需要说明的是，本申请中，转储策略是根据功能定义的一个名称，实际中，转储策略本质上是上述的生命周期管理策略，转储策略是针对某个对象存储服务系统中的某个桶进行配置的，换句话说，转储策略是配置在桶上的。转储策略的执行是由第一对象存储服务系统中的生命周期管理模块、跨区域复制模块、元数据管理模块、存储模块和业务层接入模块，以及第二对象存储服务系统中的生命周期管理模块、跨区域复制模块、元数据管理模块、存储模块和业务层接入模块共同配合实现的。
S102、云管理平台检测触发条件发生，根据转储策略将源数据桶的对象跨区域转移至目的数据桶中。
云管理平台对触发条件进行监控，在检测达到触发条件的情况下，根据转储策略将源数据桶中的待转储对象转移至目的数据桶中。需要说明的是，转移后源数据桶中的待转储对象已不存在。
可选的，在一种实现方式中，云管理平台检测触发条件发生，根据转储策略将源数据桶的对象跨区域转移至目的数据桶中，这一步骤包括但不限于S1021至S1022内容的描述。如图6所示，图6为本申请提供的一种将待转储对象跨区域转移的方法流程示意图。
S1021、云管理平台将转储策略发送至第一对象存储服务系统，相应地，第一对象存储服务系统接收云管理平台发送的转储策略。
在一种实现方式中，云管理平台对触发条件进行监控，在检测达到触发条件的情况下，将转储策略发送至第一对象存储服务系统，以使第一对象存储服务系统根据转储策略中包括的源数据桶的标识、目的数据桶的标识和待转储对象，将待转储对象转移至第二对象存储服务系统中。
可选的，在一种实现方式中，云管理平台接收到租户配置的转储策略后，立即将转储策略发送至第一对象存储服务系统中，第一对象存储服务系统自身对触发条件进行监控，在检测达到触发条件的情况下，将待转储对象转移至第二对象存储服务系统中。
S1022、第一对象存储服务系统根据转储策略将待转储对象转移至第二对象存储服务系统中，相应地，第二对象存储服务系统接收待转储对象。
第一对象存储服务系统根据转储策略中源数据桶的标识和待转储对象的标识确定待转储对象，生命周期管理模块对转储时间进行监控，在达到转储时间后，将待转储对象转储至目的区域，本申请中目的区域为第二对象存储服务系统或第二对象存储服务系统所在的区域，并将待转储对象在第二对象存储服务系统中以转储策略中指定的状态存储。
可选的，可以通过第一对象存储服务系统中的跨区域复制模块将待转储对象复制至第二对象存储服务系统中，并将待转储对象在第二对象存储服务系统中以归档存储状态存储。
可选的，将待转储对象转移至第二对象存储服务系统中，可以通过专用网络或公网，本申请不做限定。
需要说明的是，将待转储对象转移至第二对象存储服务系统后，第一对象存储服务系统中不存在待转储对象。可选的，在将待转储对象转移至第二对象存储服务系统后，将第一对象存储服务系统中的待转储数据删除。
第一对象存储服务系统将待转储对象转储至第二对象存储服务系统后，第一对象存储服务系统更新元数据，元数据中包括转储前待转储对象在第一对象存储服务系统中的位置、转储后待转储对象在第二对象存储服务系统中的位置、待转储对象当前的存储状态中的至少一个之间的映射关系。例如，参见表1，表1为本申请提供的一种元数据的示例列表。
表1
表1中，原桶名表示转储前对象所在的位置，目标信息表示转储后对象所在的位置。由表1可看出，对象1、对象2和对象3进行了转储，由区域1的桶1转储至区域2的桶2，且转储后处于归档存储状态；对象4未进行转储，对象4位于区域1的桶1中，在桶1中处于标准存储状态。
需要说明的是，表1中，各个字段的名称仅仅是一种示例，原桶名、对象名称、目标信息和存储状态之间的映射关系是一种示例性的表示，各个字段名称及它们之间的映射关系还可以是其他形式，表1并不构成对本申请的限定。
可选的，第一对象存储服务系统中更新元数据的操作，可由第一对象存储服务系统中的元数据管理模块执行。
第二对象存储服务系统接收到待转储对象后，将待转储对象以归档存储状态存储至存储模块中，更新元数据，元数据中包括待转储对象在第二对象存储服务系统中的位置。
需要说明的是，在整个转储过程中，租户是无感知的。
参见图7所示，图7为本申请提供的跨区域转储过程的示意图。将区域1的桶1中处于标准存储状态的对象跨区域转储至区域2中，使转储后的对象处于归档存储状态。如图6中标注所示，第一步，对区域1中的桶1配置转储策略(生命周期管理策略)，转储策略中包括待转储对象、转储时间、目的区域和转储后待转储对象在目的区域的存储状态，这里目的区域为区域2，转储后待转储对象在目的区域的存储状态为归档存储状态；第二步，生命周期管理模块对桶1的转储时间进行监控，在达到转储时间后，通过跨区域复制模块将待转储对象复制至区域2中，区域2接收到待转储对象后，将待转储对象存储至存储模块中，并以归档存储状态存储；在将待存储对象存储至存储模块后，区域2的元数据管理模块更新元数据，元数据中包括待转储对象在区域2中的位置，比如待转储对象位于区域2的桶2中；第三步，区域1的元数据管理模块更新元数据，元数据中包括转储前待转储对象在区域1中的位置、转储后待转储对象在区域2中的位置、待转储对象在区域2中的存储状态之间的映射关系。
可以看到，本申请提供了一种基于对象存储服务的跨区域转储方法，所述方法能够实现跨区域转储对象，只需租户在云管理平台上针对目标桶配置转储策略，触发转储任务，云存储系统可按照转储策略自动实现转储任务，从而能够将第一区域中处于标准存储状态的对象转储至第二区域中，在第二区域中以归档存储状态存储，实现了东数西存，能够降低存储成本。
在将待转储对象从第一对象存储服务系统转储至第二对象存储服务系统后，待转储对象是存储在第二对象存储服务系统中的，第一对象存储服务系统中不存在待转储对象，但是第一对象存储服务系统中记录了待转储对象的元数据，元数据中包括了转储前待转储对象在第一对象存储服务系统中的位置、转储后待转储对象在第二对象存储服务系统中的位置。因此，根据第一对象存储服务系统中的元数据，租户还可以访问到待转储对象。本申请实施例提供了一种基于对象存储服务的跨区域转储方法，所述方法描述了如何访问待转储对象，参见图8，图8为本申请提供的又一种基于对象存储服务的跨区域转储方法的流程示意 图，所述方法包括但不限于以下内容的描述。
S201、云管理平台接收租户的请求，请求用于指示请求访问待转储对象。
租户通过终端设备上的应用软件向云管理平台发送请求，请求用于指示请求访问待转储对象。相应地，云管理平台接收到租户通过终端设备发送的请求。其中，请求中携带了租户的标识、租户所请求的数据标识。
S202、云管理平台将待转储对象从目的数据桶跨区域迁移至源数据桶，并将源数据桶中的待转储对象提供给租户。
本步骤可以包括但不限于S2021至S2025中内容的描述。如图9所示，图9为本申请提供的一种将待转储对象从目的数据桶跨区域迁移至源数据桶的方法流程示意图。
S2021、云管理平台将请求发送至第一对象存储服务系统，相应地，第一对象存储服务系统接收云管理平台发送的请求。
S2022、第一对象存储服务系统根据请求向第二对象存储服务系统请求待转档对象。
第一对象存储服务系统接收到云管理平台发送的请求，根据请求查询元数据，确定租户所请求的数据所位于的区域或对象存储服务系统，并向该对象存储服务系统发送请求。例如，本申请中，待转储对象位于第二对象存储服务系统，第一对象存储服务系统向第二对象存储服务系统发送请求。
S2023、第二对象存储服务系统向第一对象存储服务系统返回待转档对象。
第二对象存储服务系统接收到请求后，根据请求向第一对象存储服务系统返回待转储对象，第一对象存储服务系统接收到待转储对象后，将待转储对象以标准存储状态存储。
可选的，该步骤可以由第二对象存储服务系统中的跨区域复制模块将待转储对象复制至第一对象存储服务系统中。
S2024、第一对象存储服务系统向云管理平台发送提示消息，提示消息用于提示第一对象存储服务系统从第二对象存储服务系统获取待转储对象完成。
第一对象存储服务系统在获取到待转储对象后，向云管理平台发送提示消息，提示消息用于提示第一对象存储服务系统从第二对象存储服务系统获取待转储对象完成。
S2025、云管理平台将提示消息发送至租户。
云管理平台将提示消息发送至租户所在的终端设备，以便租户将待转储对象从第一对象存储服务系统下载至终端设备中。租户所在的终端设备接收到提示消息后，租户可将待转储对象下载至终端设备上。
需要说明的是，本实施中，租户只需在终端设备上执行点击获取数据的操作，即可实现待转储对象由第二对象存储服务系统跨区域复制至第一对象存储服务系统中，使数据存储在第一对象存储服务系统中，租户可通过终端设备在第一对象存储服务系统中下载数据。换句话说，步骤S2021至步骤S2025对于租户来说是不感知的。
参见图10，图10为本申请实施例提供的取回数据的示意图。当云管理平台接收到租户发送的请求的情况下，请求用于指示请求访问待转档对象，需要将转储至区域2中以归档存储状态存储的数据取回至区域1中。参见图8中的标注所示，第一步，将处于归档存储状态的待转储对象从区域2中复制至区域1中，并在区域1中以标准存储状态存储；第二步，区域1通过云管理平台向租户发送提示消息，提示消息用于提示待转储对象已经从区域2复制至区域1中复制完成；第三步，租户可以通过业务接入模块访问待转储对象。
可以看到，租户在取回数据时，只需在终端设备上进行简单操作，即可成功取回数据。可以理解，对于需要长期存储但访问频率很低的数据来说，为了降低存储成本，可以将数据从第一对象存储服务系统转储至第二对象存储服务系统中，使数据在第二对象存储服务系统中以归档存储状态存储，整个转储过程对租户是无感知的。当租户需要访问数据时，可在终端设备上执行点击获取数据的操作，待数据获取成功后，终端设备接收到提示消息，租户可根据提示消息将数据下载至终端设备上，从而获得数据。由此可以看到，数据转储不影响租户对云服务的使用。
参见图11，图11为本申请提供的一种云管理平台200的结构示意图，所述云管理平台200用于管理提供对象存储服务的基础设施，所述基础设施包括设置在第一区域的第一对象存储服务数据桶和设置在第二区域的第二对象存储服务数据桶，包括：
配置接口210，配置接口210用于接收租户配置的转储策略，转储策略包括源数据桶的标识、目的数据桶的标识、将源数据桶中的待转储对象转储至目的数据桶中的触发条件，其中，源数据桶和目的数据桶 位于不同区域，且转储后在基础设施中实现在目的数据桶的存储介质为磁带或光盘；
检测模块220，用于检测触发条件发生，根据转储策略将源数据桶的对象跨区域转移至目的数据桶中。
在可能的实现方式中，云管理还包括：
通信模块230，用于接收租户针对源数据桶中的待转储对象的访问请求；
迁移模块240，用于云管理平台将待转储对象从目的数据桶跨区域迁移至源数据桶所在的区域；
通信模块230还用于，并将源数据桶所在的区域中的待转储对象提供给租户。
在可能的实现方式中，在基础设施中实现在源数据桶的存储介质为机械硬盘或固态硬盘。
在可能的实现方式中，云管理平台针对源数据桶向租户收取的计费费用高于针对目的数据桶向租户收取的计费费用。
在可能的实现方式中，触发条件包括下述任意一种或多种：
i)从配置转储策略开始计算时长，时长达到预设时长；
ii)源数据桶中已占用容量达到阈值。
在可能的实现方式中，触发条件包括源数据桶中待转储对象的标识。
在可能的实现方式中，待转储对象的标识包括待转储对象名称中包含特定字符。
在可能的实现方式中，目的数据桶所在的区域和/或目的数据桶由租户指定或由云管理平台自动选择。
其中，配置接口210、检测模块220、通信模块230、迁移模块240均可以通过软件实现，或者可以通过硬件实现。示例性的，接下来以检测模块220为例，介绍检测模块220的实现方式。类似的，配置接口210、通信模块230、迁移模块240的实现方式可以参考检测模块220的实现方式。
模块作为软件功能单元的一种举例，检测模块220可以包括运行在云管理平台上的代码。其中，云管理平台可以是云服务中的计算设备，其中计算设备例如可以是裸金属服务器、虚拟机、容器等，进一步地，计算设备可以是一台或多台。例如，检测模块220可以包括运行在多个云管理平台上的代码。需要说明的是，用于运行该代码的多个计算设备可以分布在相同的区域(region)中，也可以分布在不同的region中。进一步地，用于运行该代码的多个计算设备可以分布在相同的可用区(availability zone，AZ)中，也可以分布在不同的AZ中，每个AZ包括一个数据中心或多个地理位置相近的数据中心。其中，通常一个区域region可以包括多个可用区AZ。
同样，用于运行该代码的多个计算设备可以分布在同一个虚拟私有云(virtual private cloud，VPC)中，也可以分布在多个VPC中。其中，通常一个VPC设置在一个region内，同一region内两个VPC之间，以及不同region的VPC之间跨区通信需在每个VPC内设置通信网关，经通信网关实现VPC之间的互连。
模块作为硬件功能单元的一种举例，检测模块220可以包括至少一个计算设备，如服务器、虚拟机、容器等。或者，检测模块220也可以是利用专用集成电路(application-specific integrated circuit，ASIC)实现、或可编程逻辑器件(programmable logic device，PLD)实现的设备等。其中，上述PLD可以是复杂程序逻辑器件(complex programmable logical device，CPLD)、现场可编程门阵列(field-programmable gate array，FPGA)、通用阵列逻辑(generic array logic，GAL)或其任意组合实现。
检测模块220包括的多个计算设备可以分布在相同的region中，也可以分布在不同的region中。检测模块220包括的多个计算设备可以分布在相同的AZ中，也可以分布在不同的AZ中。同样，检测模块220包括的多个计算设备可以分布在同一个VPC中，也可以分布在多个VPC中。其中，所述多个计算设备可以是服务器、ASIC、PLD、CPLD、FPGA和GAL等计算设备的任意组合。
需要说明的是，在其他实施例中，检测模块220可以用于执行一种基于对象存储服务的跨区域转储方法中的任意步骤，配置接口210、检测模块220、通信模块230、迁移模块240均可以用于执行一种基于对象存储服务的跨区域转储方法中的任意步骤,配置接口210、检测模块220、通信模块230、迁移模块240负责实现的步骤可根据需要指定，通过配置接口210、检测模块220、通信模块230、迁移模块240分别实现一种基于对象存储服务的跨区域转储方法中不同的步骤，来实现云管理平台200的全部功能。
参见图12，图12为本申请提供的一种计算设备300的结构示意图，计算设备300例如裸金属服务器、虚拟机、容器等，该计算设备300可以配置为方法实施例中的云管理平台，计算设备300包括：总线302、处理器304、存储器306和通信接口308。处理器304、存储器306和通信接口308之间通过总线302通信。应理解，本申请不限定计算设备300中的处理器、存储器的个数。
总线302可以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。总线可以分为地址总线、数据总线、控制总线 等。为便于表示，图12中仅用一条线表示，但并不表示仅有一根总线或一种类型的总线。总线302可包括在计算设备300各个部件(例如，存储器306、处理器304、通信接口308)之间传送信息的通路。
处理器304可以包括中央处理器(central processing unit，CPU)、图形处理器(graphics processing unit，GPU)、微处理器(micro processor，MP)或者数字信号处理器(digital signal processor，DSP)等处理器中的任意一种或多种。
存储器306可以包括易失性存储器(volatile memory)，例如随机存取存储器(random access memory，RAM)。处理器304还可以包括非易失性存储器(non-volatile memory)，例如只读存储器(read-only memory，ROM)，快闪存储器，机械硬盘(hard disk drive，HDD)或固态硬盘(solid state drive，SSD)。
存储器306中存储有可执行的程序代码，处理器304执行该可执行的程序代码以分别实现前述配置接口210、检测模块220、通信模块230、迁移模块240的功能，从而实现一种基于对象存储服务的跨区域转储方法。也即，存储器306上存有用于执行一种基于对象存储服务的跨区域转储方法的指令。
通信接口308使用例如但不限于网络接口卡、收发器一类的收发模块，来实现计算设备300与其他设备或通信网络之间的通信。可选的，例如通信模块230可以位于通信接口308中。
本申请实施例还提供了一种计算设备集群。该计算设备集群包括至少一台计算设备。该计算设备可以是服务器、虚拟机、容器，例如是中心服务器、边缘服务器。
如图13所示，图13为本申请提供的一种计算设备集群的结构示意图，所述计算设备集群包括至少一个计算设备300。计算设备集群中的一个或多个计算设备300中的存储器306中可以存有相同的用于执行一种基于对象存储服务的跨区域转储方法的指令。
在一些可能的实现方式中，该计算设备集群中的一个或多个计算设备300的存储器306中也可以分别存有用于执行一种基于对象存储服务的跨区域转储方法的部分指令。换言之，一个或多个计算设备300的组合可用于共同执行一种基于对象存储服务的跨区域转储方法的指令。
需要说明的是，计算设备集群中的不同的计算设备300中的存储器306可以存储不同的指令，分别用于执行云管理平台的部分功能。也即，不同的计算设备300中的存储器306存储的指令可以实现存储资源提供模块201、主机内管理模块202、划分模块203、主机间管理模块204以及通信模块205中的一个或多个模块的功能。
在一些可能的实现方式中，计算设备集群中的一个或多个计算设备可以通过网络连接。其中，所述网络可以是广域网或局域网等等。图14示出了一种可能的实现方式。如图14所示，两个计算设备300A和300B之间通过网络进行连接。具体地，通过各个计算设备中的通信接口与所述网络进行连接。在这一类可能的实现方式中，计算设备300A中的存储器306中存有执行配置接口210、通信模块230的功能的指令。同时，计算设备300B中的存储器306中存有执行检测模块220、迁移模块240的功能的指令。
图14所示的计算设备集群之间的连接方式，计算设备300A中包含了配置接口210和通信模块230，计算设备300A上的处理器304可执行存储器306中配置接口210的代码和通信模块230的代码，用于实现云管理平台与租户之间的交互，例如，计算设备300A用于接收租户配置的转储策略，还用于接收租户的访问请求，计算设备300B上的处理器304可执行存储器306中检测模块220的代码和迁移模块240的代码，用于对转储策略进行监控，还用于实现对象的跨区域转移或迁移。
应理解，图14中示出的计算设备300A的功能也可以由多个计算设备300完成，或者云管理平台中包括多个与计算设备300A具有相同功能的计算设备。同样，计算设备300B的功能也可以由多个计算设备300完成，或者云管理平台中包括多个与计算设备300B具有相同功能的计算设备。
本申请实施例还提供了另一种计算设备集群。该计算设备集群中各计算设备之间的连接关系可以类似的参考图13和图14所述计算设备集群的连接方式。不同的是，该计算设备集群中的一个或多个计算设备300中的存储器306中可以存有不同的用于执行一种基于对象存储服务的跨区域转储方法的指令。在一些可能的实现方式中，该计算设备集群中的一个或多个计算设备300的存储器306中也可以分别存有用于执行一种基于对象存储服务的跨区域转储方法的部分指令。换言之，一个或多个计算设备300的组合可以共同执行用于执行一种基于对象存储服务的跨区域转储方法的指令。
本申请实施例还提供了一种包含指令的计算机程序产品。所述计算机程序产品可以是包含指令的，能够运行在计算设备上或被储存在任何可用介质中的软件或程序产品。当所述计算机程序产品在至少一个计算设备上运行时，使得至少一个计算设备执行一种基于对象存储服务的跨区域转储方法。
本申请实施例还提供了一种计算机可读存储介质。所述计算机可读存储介质可以是计算设备能够存储 的任何可用介质或者是包含一个或多个可用介质的数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘)等。该计算机可读存储介质包括指令，所述指令指示计算设备或计算设备集群执行一种基于对象存储服务的跨区域转储方法。
以上实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的保护范围。

Claims (19)

  1. 一种基于对象存储服务的跨区域转储方法，其特征在于，所述方法应用于云管理平台，所述云管理平台用于管理提供对象存储服务的基础设施，所述基础设施包括设置在第一区域的第一对象存储服务数据桶和设置在第二区域的第二对象存储服务数据桶，所述方法包括：
    云管理平台提供配置接口，所述配置接口用于接收租户配置的转储策略，所述转储策略包括源数据桶的标识、目的数据桶的标识、将所述源数据桶中的待转储对象转储至所述目的数据桶中的触发条件，其中，所述源数据桶和所述目的数据桶位于不同区域，且转储后在所述基础设施中实现所述目的数据桶的存储介质为磁带或光盘；
    所述云管理平台检测所述触发条件发生，根据所述转储策略将所述源数据桶的待转储对象跨区域转移至所述目的数据桶中。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述云管理平台接收所述租户针对所述源数据桶中的待转储对象的访问请求；
    所述云管理平台将所述待转储对象从所述目的数据桶跨区域迁移至所述源数据桶所在的区域，并将所述源数据桶所在的区域中的所述待转储对象提供给所述租户。
  3. 根据权利要求1或2所述的方法，其特征在于，在所述基础设施中实现在所述源数据桶的存储介质为机械硬盘或固态硬盘。
  4. 根据权利要求1至3任一项所述的方法，其特征在于，所述云管理平台针对所述源数据桶向所述租户收取的计费费用高于针对所述目的数据桶向所述租户收取的计费费用。
  5. 根据权利要求1至4任一项所述的方法，其特征在于，所述触发条件包括下述任意一种或多种：
    i)从配置所述转储策略开始计算时长，时长达到预设时长；
    ii)所述源数据桶已占用容量达到阈值。
  6. 根据权利要求1至5任一项所述的方法，其特征在于，所述触发条件包括所述源数据桶中待转储对象的标识。
  7. 根据权利要求6所述的方法，其特征在于，所述待转储对象的标识包括待转储对象名称中包含特定字符。
  8. 根据权利要求1-7任一项所述的方法，其特征在于，所述目的数据桶所在的区域和/或所述目的数据桶由所述租户指定或由所述云管理平台自动选择。
  9. 一种云管理平台，其特征在于，所述云管理平台用于管理提供对象存储服务的基础设施，所述基础设施包括设置在第一区域的第一对象存储服务数据桶和设置在第二区域的第二对象存储服务数据桶，包括：
    配置接口，所述配置接口用于接收租户配置的转储策略，所述转储策略包括源数据桶的标识、目的数据桶的标识、将所述源数据桶中的待转储对象转储至所述目的数据桶中的触发条件，其中，所述源数据桶和所述目的数据桶位于不同区域，且转储后在所述基础设施中实现所述目的数据桶的存储介质为磁带或光盘；
    检测模块，用于检测所述触发条件发生，根据所述转储策略将所述源数据桶的对象跨区域转移至所述目的数据桶中。
  10. 根据权利要求9所述的云管理平台，其特征在于，所述云管理平台还包括：
    通信模块，用于接收所述租户针对所述源数据桶中的待转储对象的访问请求；
    迁移模块，用于所述云管理平台将所述待转储对象从所述目的数据桶跨区域迁移至所述源数据桶所在的区域；
    所述通信模块还用于，并将所述源数据桶所在的区域中的所述待转储对象提供给所述租户。
  11. 根据权利要求9或10所述的云管理平台，其特征在于，在所述基础设施中实现在所述源数据桶的存储介质为机械硬盘或固态硬盘。
  12. 根据权利要求9至11任一项所述的云管理平台，其特征在于，所述云管理平台针对所述源数据桶向所述租户收取的计费费用高于针对所述目的数据桶向所述租户收取的计费费用。
  13. 根据权利要求9至12任一项所述的云管理平台，其特征在于，所述触发条件包括下述任意一种或多种：
    i)从配置所述转储策略开始计算时长，时长达到预设时长；
    ii)所述源数据桶中已占用容量达到阈值。
  14. 根据权利要求9至13任一项所述的云管理平台，其特征在于，所述触发条件包括所述源数据桶中 待转储对象的标识。
  15. 根据权利要求14所述的云管理平台，其特征在于，所述待转储对象的标识包括待转储对象名称中包含特定字符。
  16. 根据权利要求9-15任一项所述的云管理平台，其特征在于，所述目的数据桶所在的区域和/或所述目的数据桶由所述租户指定或由所述云管理平台自动选择。
  17. 一种计算设备集群，其特征在于，包括至少一个计算设备，所述至少一个计算设备中的每个计算设备包括存储器和处理器，所述至少一个计算设备的处理器用于执行所述至少一个计算设备的存储器中存储的指令，使得所述计算设备集群执行如权利要求1至8任一项所述的方法。
  18. 一种计算机可读存储介质，其特征在于，包括程序指令，当所述程序指令由计算设备集群执行时，所述计算设备集群执行如权利要求1至8任一项所述的方法。
  19. 一种系统，其特征在于，包括云管理平台、设置在第一区域的第一对象存储服务数据桶和设置在第二区域的第二对象存储服务数据桶，所述云管理平台为权利要求1-8任一项所述的云管理平台。
PCT/CN2023/105273 2022-07-04 2023-06-30 一种基于对象存储服务的跨区域转储方法及相关装置 WO2024008024A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202210779562.5 2022-07-04
CN202210779562 2022-07-04
CN202211215542.1A CN117389460A (zh) 2022-07-04 2022-09-30 一种基于对象存储服务的跨区域转储方法及相关装置
CN202211215542.1 2022-09-30

Publications (1)

Publication Number Publication Date
WO2024008024A1 true WO2024008024A1 (zh) 2024-01-11

Family

ID=89436119

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/105273 WO2024008024A1 (zh) 2022-07-04 2023-06-30 一种基于对象存储服务的跨区域转储方法及相关装置

Country Status (2)

Country Link
CN (1) CN117389460A (zh)
WO (1) WO2024008024A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180107723A1 (en) * 2016-10-13 2018-04-19 International Business Machines Corporation Content oriented analysis of dumps
WO2019127234A1 (zh) * 2017-12-28 2019-07-04 华为技术有限公司 一种对象迁移的方法、设备和系统
CN110309233A (zh) * 2018-03-28 2019-10-08 腾讯科技（深圳）有限公司 数据存储的方法、装置、服务器和存储介质
US20210143991A1 (en) * 2019-11-07 2021-05-13 Salesforce.Com, Inc. System for securing memory dumps
CN114629921A (zh) * 2020-12-14 2022-06-14 华为云计算技术有限公司 云平台及其提供的对象存储服务的桶管理方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180107723A1 (en) * 2016-10-13 2018-04-19 International Business Machines Corporation Content oriented analysis of dumps
WO2019127234A1 (zh) * 2017-12-28 2019-07-04 华为技术有限公司 一种对象迁移的方法、设备和系统
CN110309233A (zh) * 2018-03-28 2019-10-08 腾讯科技（深圳）有限公司 数据存储的方法、装置、服务器和存储介质
US20210143991A1 (en) * 2019-11-07 2021-05-13 Salesforce.Com, Inc. System for securing memory dumps
CN114629921A (zh) * 2020-12-14 2022-06-14 华为云计算技术有限公司 云平台及其提供的对象存储服务的桶管理方法

Also Published As

Publication number Publication date
CN117389460A (zh) 2024-01-12

Similar Documents

Publication Publication Date Title
US10911540B1 (en) Recovering snapshots from a cloud snapshot lineage on cloud storage to a storage system
US11199985B2 (en) Tracking storage capacity usage by snapshot lineages using metadata in a multi-level tree structure
US11392497B1 (en) Low latency access to data sets using shared data set portions
US20210255994A1 (en) Intelligent file system with transparent storage tiering
US9251187B2 (en) Metadata-driven version management service in pervasive environment
US11550713B1 (en) Garbage collection in distributed systems using life cycled storage roots
US10747458B2 (en) Methods and systems for improving efficiency in cloud-as-backup tier
CA3093681C (en) Document storage and management
US11112986B2 (en) Systems and methods for storing information within hybrid storage with local and cloud-based storage devices
CN106331075B (zh) 用于存储文件的方法、元数据服务器和管理器
US20230046983A1 (en) Snapshot shipping to multiple cloud destinations
US11593270B1 (en) Fast distributed caching using erasure coded object parts
US20210173815A1 (en) Automatically dispositioning of copies of data
CN107566405B (zh) 一种快速访问和拷贝的存储资源池化方法
US11537553B2 (en) Managing snapshots stored locally in a storage system and in cloud storage utilizing policy-based snapshot lineages
US11288134B2 (en) Pausing and resuming copying of snapshots from a local snapshot lineage to at least one cloud snapshot lineage
WO2024008024A1 (zh) 一种基于对象存储服务的跨区域转储方法及相关装置
US11086557B2 (en) Continuous asynchronous replication from on-premises storage to cloud object stores
WO2023109934A1 (zh) 一种对象存储桶的数据访问方法以及云管理平台
US11630736B2 (en) Recovering a storage volume associated with a snapshot lineage from cloud storage
US20210286761A1 (en) Generating configuration data enabling remote access to portions of a snapshot lineage copied to cloud storage
US11366600B2 (en) Moving snapshots from a local snapshot lineage on a storage system to a cloud snapshot lineage on cloud storage
US11907163B1 (en) Cloud snapshot lineage mobility between virtualization software running on different storage systems
US20230376386A1 (en) Backup management for synchronized databases
US20220004459A1 (en) Metadata based data replication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23834791

Country of ref document: EP

Kind code of ref document: A1