CN114416299A - Openstack-based local container mirror image management method and application - Google Patents

Openstack-based local container mirror image management method and application Download PDF

Info

Publication number
CN114416299A
CN114416299A CN202210060863.2A CN202210060863A CN114416299A CN 114416299 A CN114416299 A CN 114416299A CN 202210060863 A CN202210060863 A CN 202210060863A CN 114416299 A CN114416299 A CN 114416299A
Authority
CN
China
Prior art keywords
image
slave
mirror
mirror image
node
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
CN202210060863.2A
Other languages
Chinese (zh)
Inventor
彭昊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Anchaoyun Software Co ltd
Original Assignee
Shanghai Anchaoyun Software Co ltd
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 Shanghai Anchaoyun Software Co ltd filed Critical Shanghai Anchaoyun Software Co ltd
Priority to CN202210060863.2A priority Critical patent/CN114416299A/en
Publication of CN114416299A publication Critical patent/CN114416299A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45562—Creating, deleting, cloning virtual machine instances

Landscapes

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

Abstract

The invention discloses a local container mirror image management method based on Openstack and application thereof, wherein the method comprises the following steps: the first node creates a slave mirror image and establishes a corresponding relation between a master mirror image and the slave mirror image; the first node downloads an available image file to a local storage and establishes a corresponding relation between the available image file and the slave image; and the first node uploads the data of the slave image to the Docker image. The method can associate the same mirror images of different nodes in the Openstack cluster by establishing the corresponding relation between the master mirror image and the slave mirror image in the database, so that the management of the mirror images is facilitated; and one-time uploading of the mirror images and repeated multiplexing among all nodes can be realized according to the corresponding relation between the master mirror image and the slave mirror image.

Description

Openstack-based local container mirror image management method and application
Technical Field
The invention relates to the field of cloud computing, in particular to a method and application for managing local container images based on Openstack.
Background
In the process of creating a container by a distributed cluster, an image needs to be acquired to create the image, and the image can be stored in a local or image repository.
In the existing local mirror image storage scheme, after a mirror image is uploaded from a certain physical node, the mirror image can only be used at the node, and when other nodes need the mirror image, the mirror image needs to be manually uploaded again. The scheduling method can lead to that under the condition that the resources are sufficient, the container is created by being concentrated on a certain node, and the waste of network bandwidth resources is caused. When a large number of containers are created concurrently, the containers at the end of the queue wait too long while other physical nodes are not being used efficiently.
The information disclosed in this background section is only for enhancement of understanding of the general background of the invention and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.
Disclosure of Invention
The invention aims to provide a local container mirror image management method based on Openstack and application thereof, and solves the problems that the same mirror image needs to be manually uploaded to different nodes, and the mirror image cannot be effectively managed due to a large number of repeated mirror images.
To achieve the above object, an embodiment of the present invention provides a method for managing a local container image based on Openstack.
In one or more embodiments of the invention, the method comprises: the first node creates a slave mirror image and establishes a corresponding relation between a master mirror image and the slave mirror image; the first node downloads an available image file to a local storage and establishes a corresponding relation between the available image file and the slave image; and the first node uploads the data of the slave image to the Docker image.
In one or more embodiments of the present invention, the downloading, by the first node, an available image file to a local storage, and establishing a correspondence between the available image file and the slave image, includes: the first node searches for a node with the available mirror image file under the main mirror image; and copying the available image file in the node to the slave image.
In one or more embodiments of the invention, the method further comprises: and when the slave mirror image of the first node fails, the first node performs data recovery according to other slave mirror image states under the master mirror image corresponding to the slave mirror image.
In one or more embodiments of the present invention, the performing, by the first node, data recovery according to other slave image states under a master image corresponding to the slave image includes: inquiring other slave mirror image states under the master mirror image corresponding to the slave mirror image; and copying the other slave image data having the same MD5 value into the slave image.
In another aspect of the present invention, an apparatus for Openstack-based local container mirror management is provided, which includes a creation module, a download module, and an upload module.
And the creating module is used for creating the slave mirror image by the first node and establishing the corresponding relation between the master mirror image and the slave mirror image.
And the downloading module is used for downloading the available image file to a local storage by the first node and establishing the corresponding relation between the available image file and the slave image.
And the uploading module is used for uploading the mirrored data to the Docker mirror image by the first node.
In one or more embodiments of the present invention, the download module is further configured to: the first node searches for a node with the available mirror image file under the main mirror image; and copying the available image file in the node to the slave image.
In one or more embodiments of the present invention, the download module is further configured to: and when the slave mirror image of the first node fails, the first node performs data recovery according to other slave mirror image states under the master mirror image corresponding to the slave mirror image.
In one or more embodiments of the present invention, the download module is further configured to: inquiring other slave mirror image states under the master mirror image corresponding to the slave mirror image; and copying the other slave image data having the same MD5 value into the slave image.
In another aspect of the present invention, there is provided an electronic device including: at least one processor; and a memory storing instructions that, when executed by the at least one processor, cause the at least one processor to perform a method of Openstack-based local container image management as described above.
In another aspect of the present invention, a computer readable storage medium is provided, having stored thereon a computer program, which when executed by a processor, performs the steps of the method for Openstack-based local container mirror management as described.
Compared with the prior art, according to the method and the application for managing the Openstack-based local container mirror images, the same mirror images of different nodes in an Openstack cluster can be associated by establishing the corresponding relation between the master mirror image and the slave mirror image in the database, so that the management of the mirror images is facilitated; and one-time uploading of the mirror images and repeated multiplexing among all nodes can be realized according to the corresponding relation between the master mirror image and the slave mirror image.
Drawings
FIG. 1 is a flow diagram of a method of Openstack-based local container mirroring management according to an embodiment of the invention;
FIG. 2 is a mirror structure diagram of a method for Openstack-based local container mirror management according to an embodiment of the invention;
FIG. 3 is a schematic data transmission diagram of a method for Openstack-based local container mirroring management according to an embodiment of the invention;
FIG. 4 is an exemplary diagram of a method of Openstack-based local container mirroring management according to an embodiment of the invention;
FIG. 5 is a flow diagram of a method for Openstack-based local container mirroring management according to an embodiment of the invention;
FIG. 6 is a block diagram of an apparatus for Openstack-based local container mirroring management according to an embodiment of the invention;
FIG. 7 is a hardware block diagram of a computing device for Openstack-based local container mirror management according to an embodiment of the invention.
Detailed Description
The following detailed description of the present invention is provided in conjunction with the accompanying drawings, but it should be understood that the scope of the present invention is not limited to the specific embodiments.
Throughout the specification and claims, unless explicitly stated otherwise, the word "comprise", or variations such as "comprises" or "comprising", will be understood to imply the inclusion of a stated element or component but not the exclusion of any other element or component.
The technical solutions provided by the embodiments of the present invention are described in detail below with reference to the accompanying drawings.
Example 1
As shown in fig. 1 to 4, a method for Openstack-based local container mirror management according to an embodiment of the present invention is described, which includes the following steps.
In step S101, the first node creates a slave image, and establishes a correspondence relationship between the master image and the slave image.
And adding master mirror image information and slave mirror image information in an Openstack cluster database, and mapping the slave mirror image to the master mirror image in the database. By establishing the corresponding relation between the master mirror image and the slave mirror image in the database, the same mirror images of different nodes can be associated, and the management of the mirror images is convenient.
The sphere is a module in charge of image management in the Openstack cluster, and is used for managing and scheduling container images, and functions of the sphere include searching, registering, retrieving and the like of virtual machine images. Glance may save images to a variety of back-end stores, such as a simple file store or object store.
The Glance service is in charge of managing the mirror images, is not in charge of storing the mirror images, and stores the mirror images under a certain directory of a server operated by the Glance service or is in butt joint with different back ends, so that a mirror image storage mode needs to be specified after the Glance service.
The master mirror is a virtual mirror object managed by the company and used for describing the mirror object, the master mirror is an abstract mirror object and stores the common information of the slave mirror, and the common information includes but is not limited to the description of the mirror type, the size of the mirror and the type of the mirror, and does not store actual mirror data.
The slave mirror is an actual mirror object used for creating a container and storing in a local mirror resource, and different slave mirrors have independent metadata and store actual mirror data.
In step S102, the first node downloads the available image file to the local storage, and establishes a corresponding relationship between the available image file and the slave image.
The Glance service can acquire an available image file through a corresponding slave image under the master image and transmit the available image file to the corresponding slave image. And further, one-time uploading of the mirror image and repeated multiplexing among all the nodes are realized.
The first node inquires other slave mirror image states under the master mirror image corresponding to the slave mirror image, respectively calculates MD5 values of other slave mirror images according to an MD5 algorithm, acquires data of other slave mirror images with the same MD5 value, wherein the data is an available mirror image file, and copies the mirror image file to the slave mirror image of the first node. When different nodes use the same image file, only the data of other slave images under the corresponding master image needs to be copied through the MD5 algorithm.
The image file may comprise a complete operating system environment in which the desired application may be installed, and the image file may be used to create a Container (Container) with which to run the application. The image file is a Read-only template, and can be regarded as a uniform view of a plurality of Read-only layers (Read-only layers).
In step S103, the first node uploads the data from the mirror to the Docker mirror.
Docker is an open source application container engine, can pack application and dependence package to a portable container, and then release this to the machine of Linux or Windows operating system, can also realize virtualization, the container is the complete use sandbox mechanism, do not have any interface each other.
When services are developed or deployed, Docker files need to be added in projects, packaged services are constructed into Docker mirrors according to the Docker files, and then containers are generated through layout files of kubernets to be managed.
The Glance service accesses the DockeraPI and loads the slave image data into the Docker image. Docker has three types of APIs: docker RegistryAPI, Docker HubAPI, and Docker Remote API. In this embodiment, a Docker registry API is selected, and because the Docker registry API is an API of a Docker mirror warehouse, the mirror warehouse can be freely, automatically and programmatically managed by operating the Docker registry API.
Taking fig. 4 as an example, the user sends a request to copy from mirror 01 to any node M. The Glance service of node M creates the information of the slave image 02 to the database and binds the relationship between the slave image 02 and the master image. The Glance service of the node M inquires other slave images of the master image corresponding to the slave image 02 in the database, inquires the node N with the actual data of the slave image 01, and copies the mirror image data in the node N to the node M. The Glance service of the node M uploads the data copied from the node N to the Docker mirror through the Docker.
Example 2
Referring to fig. 5, a method for Openstack-based local container mirror management according to an embodiment of the present invention is described, which includes the following steps.
In step S201, the first node creates a slave image, and establishes a correspondence relationship between the master image and the slave image.
And adding master mirror image information and slave mirror image information in an Openstack cluster database, and mapping the slave mirror image to the master mirror image in the database. By establishing the corresponding relation between the master mirror image and the slave mirror image in the database, the same mirror images of different nodes can be associated, and the management of the mirror images is convenient.
The sphere is a module in charge of image management in the Openstack cluster, and is used for managing and scheduling container images, and functions of the sphere include searching, registering, retrieving and the like of virtual machine images. Glance may save images to a variety of back-end stores, such as a simple file store or object store.
The Glance service is in charge of managing the mirror images, is not in charge of storing the mirror images, and stores the mirror images under a certain directory of a server operated by the Glance service or is in butt joint with different back ends, so that a mirror image storage mode needs to be specified after the Glance service.
The master mirror is a virtual mirror object managed by the company and used for describing the mirror object, the master mirror is an abstract mirror object and stores the common information of the slave mirror, and the common information includes but is not limited to the description of the mirror type, the size of the mirror and the type of the mirror, and does not store actual mirror data.
The slave mirror is an actual mirror object used for creating a container and storing in a local mirror resource, and different slave mirrors have independent metadata and store actual mirror data.
In step S202, when the slave mirror of the first node fails, the first node performs data recovery according to the other slave mirror states in the master mirror corresponding to the slave mirror.
Because the Glance service establishes the corresponding relation between the master mirror image and the slave mirror image in the database, when the slave mirror image of a certain node in the cluster sends a fault, only the data is acquired from other slave mirror images under the master mirror image corresponding to the fault slave mirror image, and the data does not need to be uploaded to the slave mirror image again, so that one-time uploading of the mirror image and repeated multiplexing among the nodes are realized.
In step S203, other slave image data having the same MD5 value is copied into the slave image.
The principle of the MD5 algorithm can be briefly described as: the MD5 code processes incoming information in 512-bit packets, each of which is divided into 16 32-bit sub-packets, and after processing, the output of the algorithm consists of four 32-bit packets, which are concatenated to produce a 128-bit hash value.
Specifically, (1) filling: the length of the input information (bit) is first padded so that the result of the remainder of 512 equals 448. The method of padding is to pad one 1 and n 0. (2) Length of recorded information: the pre-padding information length is stored with 64 bits. The 64 bits are added to the padding result, and the information length becomes N × 512+448+64 ═ N +1 × 512 bits. (3) Load standard magic number: the standard magic numbers are (a ═ 01234567)16, B ═ 89ABCDEF)16, C ═ FEDCBA98)16, D ═ 76543210) 16. If defined in the procedure, is (a ═ 0X67452301L, B ═ 0 xefclab 89L, C ═ 0X98BADCFEL, D ═ 0X 10325476L). (4) Four-wheel cycle operation: the number of cycles is the number of packets (N + 1).
When the slave mirror of the first node fails, other slave mirror states under the master mirror corresponding to the slave mirror of the first node are inquired, the MD5 values of other slave mirrors are respectively calculated according to the MD5 algorithm, and the data of other slave mirrors with the same MD5 value are copied to the first node.
In step S204, the first node uploads the data from the mirror into the Docker mirror.
Docker is an open source application container engine, can pack application and dependence package to a portable container, and then release this to the machine of Linux or Windows operating system, can also realize virtualization, the container is the complete use sandbox mechanism, do not have any interface each other.
When services are developed or deployed, Docker files need to be added in projects, packaged services are constructed into Docker mirrors according to the Docker files, and then containers are generated through layout files of kubernets to be managed.
The Glance service accesses the DockeraPI and loads the slave image data into the Docker image. Docker has three types of APIs: docker RegistryAPI, Docker HubAPI, and Docker Remote API. In this embodiment, a Docker registry API is selected, and because the Docker registry API is an API of a Docker mirror warehouse, the mirror warehouse can be freely, automatically and programmatically managed by operating the Docker registry API.
Fig. 6 illustrates an apparatus for Openstack-based local container mirror management according to an embodiment of the present invention.
In an embodiment of the present invention, the apparatus for Openstack-based local container image management includes a creation module 601, a download module 602, and an upload module 603.
The creating module 601 is configured to create a slave image for a first node, and establish a corresponding relationship between a master image and the slave image.
The downloading module 602 is configured to provide the first node to download the available image file to the local storage, and establish a corresponding relationship between the available image file and the slave image.
An upload module 603, configured to upload data from the mirror to the Docker mirror by the first node.
The download module 602 is further configured to: the first node searches for a node with an available mirror image file under the main mirror image; and copying the available image files in the node into the slave image.
The download module 602 is further configured to: and when the slave mirror image of the first node fails, the first node performs data recovery according to other slave mirror image states under the master mirror image corresponding to the slave mirror image.
The download module 602 is further configured to: inquiring other slave mirror image states under the master mirror image corresponding to the slave mirror image; and copying other slave image data having the same MD5 value into the slave image.
FIG. 7 illustrates a hardware block diagram of a computing device 70 for Openstack-based local container mirror management according to embodiments of the present description. As shown in fig. 7, computing device 70 may include at least one processor 701, storage 702 (e.g., non-volatile storage), memory 703, and communication interface 704, and the at least one processor 701, storage 702, memory 703, and communication interface 704 are connected together via a bus 705. The at least one processor 701 executes at least one computer readable instruction stored or encoded in the memory 702.
It should be appreciated that the computer-executable instructions stored in the memory 702, when executed, cause the at least one processor 701 to perform the various operations and functions described above in connection with fig. 1-7 in the various embodiments of the present description.
In embodiments of the present description, computing device 70 may include, but is not limited to: personal computers, server computers, workstations, desktop computers, laptop computers, notebook computers, mobile computing devices, smart phones, tablet computers, cellular phones, Personal Digital Assistants (PDAs), handheld devices, messaging devices, wearable computing devices, consumer electronics, and so forth.
According to one embodiment, a program product, such as a machine-readable medium, is provided. A machine-readable medium may have instructions (i.e., elements described above as being implemented in software) that, when executed by a machine, cause the machine to perform various operations and functions described above in connection with fig. 1-7 in the various embodiments of the present specification. Specifically, a system or apparatus may be provided which is provided with a readable storage medium on which software program code implementing the functions of any of the above embodiments is stored, and causes a computer or processor of the system or apparatus to read out and execute instructions stored in the readable storage medium.
According to the method and the application for managing the local container mirror image based on the Openstack, the same mirror images of different nodes in an Openstack cluster can be associated by establishing the corresponding relation between the master mirror image and the slave mirror image in the database, so that the management of the mirror images is facilitated; and one-time uploading of the mirror images and repeated multiplexing among all nodes can be realized according to the corresponding relation between the master mirror image and the slave mirror image.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The foregoing descriptions of specific exemplary embodiments of the present invention have been presented for purposes of illustration and description. It is not intended to limit the invention to the precise form disclosed, and obviously many modifications and variations are possible in light of the above teaching. The exemplary embodiments were chosen and described in order to explain certain principles of the invention and its practical application to enable one skilled in the art to make and use various exemplary embodiments of the invention and various alternatives and modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the claims and their equivalents.

Claims (10)

1. A method for Openstack-based local container mirror management, the method comprising:
the first node creates a slave mirror image and establishes a corresponding relation between a master mirror image and the slave mirror image;
the first node downloads an available image file to a local storage and establishes a corresponding relation between the available image file and the slave image; and
and the first node uploads the data of the slave image to the Docker image.
2. The method for Openstack-based local container image management according to claim 1, wherein the downloading, by the first node, an available image file to a local storage and establishing a correspondence between the available image file and the slave image comprises:
the first node searches for a node with the available mirror image file under the main mirror image; and
copying the available image file in the node to the slave image.
3. The method for Openstack-based local container mirror management as claimed in claim 1, wherein the method further comprises:
and when the slave mirror image of the first node fails, the first node performs data recovery according to other slave mirror image states under the master mirror image corresponding to the slave mirror image.
4. The method for Openstack-based local container mirror management according to claim 3, wherein the performing, by the first node, data recovery according to the other slave mirror states under the master mirror corresponding to the slave mirror comprises:
inquiring other slave mirror image states under the master mirror image corresponding to the slave mirror image; and
copying the other slave image data having the same MD5 value into the slave image.
5. An apparatus for Openstack-based local container mirroring management, the apparatus comprising:
the creating module is used for creating a slave mirror image by a first node and establishing a corresponding relation between a master mirror image and the slave mirror image;
the downloading module is used for the first node to download the available image file to a local storage and establish the corresponding relation between the available image file and the slave image; and
and the uploading module is used for uploading the mirrored data to the Docker mirror image by the first node.
6. The apparatus of Openstack-based local container image management of claim 5, wherein the download module is further to:
the first node searches for a node with the available mirror image file under the main mirror image; and
copying the available image file in the node to the slave image.
7. The apparatus of Openstack-based local container image management of claim 5, wherein the download module is further to:
and when the slave mirror image of the first node fails, the first node performs data recovery according to other slave mirror image states under the master mirror image corresponding to the slave mirror image.
8. The apparatus of Openstack-based local container image management of claim 7, wherein the download module is further to:
inquiring other slave mirror image states under the master mirror image corresponding to the slave mirror image; and
copying the other slave image data having the same MD5 value into the slave image.
9. An electronic device, comprising:
at least one processor; and
a memory storing instructions that, when executed by the at least one processor, cause the at least one processor to perform the method of Openstack-based local container image management of any of claims 1 to 4.
10. A computer-readable storage medium, having stored thereon a computer program which, when being executed by a processor, carries out the steps of the method for Openstack-based local container mirror management according to any one of claims 1 to 4.
CN202210060863.2A 2022-01-19 2022-01-19 Openstack-based local container mirror image management method and application Pending CN114416299A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210060863.2A CN114416299A (en) 2022-01-19 2022-01-19 Openstack-based local container mirror image management method and application

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210060863.2A CN114416299A (en) 2022-01-19 2022-01-19 Openstack-based local container mirror image management method and application

Publications (1)

Publication Number Publication Date
CN114416299A true CN114416299A (en) 2022-04-29

Family

ID=81274473

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210060863.2A Pending CN114416299A (en) 2022-01-19 2022-01-19 Openstack-based local container mirror image management method and application

Country Status (1)

Country Link
CN (1) CN114416299A (en)

Similar Documents

Publication Publication Date Title
US10664493B2 (en) Replication of data objects from a source server to a target server
US9110603B2 (en) Identifying modified chunks in a data set for storage
US9811424B2 (en) Optimizing restoration of deduplicated data
US9792306B1 (en) Data transfer between dissimilar deduplication systems
US8806489B2 (en) Virtual machine image distribution network
US9641598B1 (en) Contextually unique identifier generation service
US10747458B2 (en) Methods and systems for improving efficiency in cloud-as-backup tier
CN104636437A (en) Event notification method and device and monitor processing method
US20200099745A1 (en) Storage segment server covered cache
US10783073B2 (en) Chronologically ordered out-of-place update key-value storage system
CN104580428A (en) Data routing method, data management device and distributed storage system
US9684668B1 (en) Systems and methods for performing lookups on distributed deduplicated data systems
US10496493B1 (en) Method and system for restoring applications of particular point in time
CN111858156A (en) Mirror image management method and device and electronic equipment
US20140214768A1 (en) Reducing backup bandwidth by remembering downloads
CN114416299A (en) Openstack-based local container mirror image management method and application
US10346422B2 (en) Use of proxy objects for integration between a content management system and a case management system
US20190155919A1 (en) Performing deduplication on cloud-resident encrypted data
US9348853B2 (en) Mobile application cache based on extreme scale technology
US11520664B2 (en) Metadata based data replication
US20230091577A1 (en) Heterogenous replication in a hybrid cloud database
US11514016B2 (en) Paging row-based data stored as objects
US20230097507A1 (en) Data backup optimization
CN116339625A (en) Data storage method and device
CN117763053A (en) Component processing method and device, electronic equipment and computer readable storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination