CN112433677A - Method for docking multiple storage back ends by cloud mirror image service - Google Patents
Method for docking multiple storage back ends by cloud mirror image service Download PDFInfo
- Publication number
- CN112433677A CN112433677A CN202011328799.9A CN202011328799A CN112433677A CN 112433677 A CN112433677 A CN 112433677A CN 202011328799 A CN202011328799 A CN 202011328799A CN 112433677 A CN112433677 A CN 112433677A
- Authority
- CN
- China
- Prior art keywords
- mirror image
- cloud
- service
- configuration
- storage
- 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
Links
- 238000003860 storage Methods 0.000 title claims abstract description 81
- 238000000034 method Methods 0.000 title claims abstract description 31
- 238000003032 molecular docking Methods 0.000 title claims abstract description 24
- 230000004044 response Effects 0.000 claims abstract description 7
- 230000008569 process Effects 0.000 claims description 4
- 210000001503 joint Anatomy 0.000 description 5
- 230000006870 function Effects 0.000 description 3
- 230000001965 increasing effect Effects 0.000 description 3
- 238000002955 isolation Methods 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000002184 metal Substances 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
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
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0629—Configuration or reconfiguration of storage systems
-
- 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/065—Replication 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]
Abstract
The invention discloses a method for docking multiple storage back ends by a cloud mirror image service, and belongs to the technical field of cloud computing. The method for docking multiple storage back ends by the cloud mirror image service comprises the following steps: s1, setting configuration rules in the cloud mirror image service configuration file; s2, setting a cloud mirror image service configuration file reading API; s3, setting a cloud mirror image service client; s4, setting a client response interface; s5, setting a restful API stored at the back end of the cloud mirror image service docking; s6, setting a cloud mirror image to create a control flow; and S7, adding keyword description to the hard disk type of the storage service. The method for the cloud mirror image service to be connected with the plurality of storage back ends can greatly improve the support capability of the mirror image service, increase the flexibility of the cloud mirror image service, and has good popularization and application values.
Description
Technical Field
The invention relates to the technical field of cloud computing, and particularly provides a method for docking multiple storage back ends by a cloud mirror image service.
Background
Cloud platform administrators provide customers with various resources of services, including computing, storage, networks, etc., where cloud mirroring is an indispensable resource for providing customers with servers. The cloud image encapsulates solutions to customized needs that customers put forward to product providers, and also encapsulates featured products of the platform. The storage of cloud images plays a crucial role throughout the platform product chain. But current cloud mirroring services can only interface to one storage backend. Namely, the cloud mirror image can only be placed in one storage, and when the storage service is in butt joint with a plurality of storage back ends, due to the limitation of storage types, storage domains and the like, the problems that a server cannot be efficiently created for a client or the time consumption is long in the process of creating the server and the like are solved.
Cloud host: the cloud host is an important component of cloud computing in infrastructure application, is located at the bottom layer of a pyramid of a cloud computing industry chain, and is derived from a cloud computing platform. The cloud computing platform integrates three core elements of internet application: computing, storage, network, and providing a user with a public internet infrastructure service.
Cloud mirroring: is the basis for creating cloud hosts. Like the traditional mirror image, the cloud mirror image is also in a file form, and a plurality of files can be made into a mirror image file. Common image file formats are ISO, BIN, IMG, etc., which have properties similar to ZIP compressed packages. The cloud image is an image file which is provided by a cloud service manufacturer to a client and used for creating a server, the file can contain cloud products provided by the cloud service manufacturer and customized services required by the client, and the cloud image is an intuitive embodiment of the products provided by the cloud service manufacturer to the client. In more detail, the cloud mirror is a server or disk template containing software and necessary configuration, including an operating system or business data, and may further include application software (e.g., database software) and proprietary software. The mirror images are divided into public mirror images, private mirror images, shared mirror images and market mirror images.
Cloud mirroring service: the cloud mirror image service is a management service of cloud mirror images in a cloud management platform and provides life cycle management capabilities of creation, deletion, search and the like of the cloud mirror images of the mirror images. The user can flexibly apply for the elastic cloud server and the bare metal server by using public mirror images, private mirror images or shared mirror images. Meanwhile, the user can create a private mirror image through an existing cloud server or by using an external mirror image file, so that service cloud or cloud migration is realized. The mirror service has the main functions of: 1) providing a common main stream operating system common image; 2) creating a private image by an existing running cloud server or an external import mode; 3) managing common images, such as: searching according to the type/name/ID of the operating system, and checking details such as mirror image ID, system disk size and the like; checking the characteristics supported by the mirror image; 4) managing private images, such as: modifying the mirror image attribute, sharing the mirror image, copying the mirror image and the like; 5) the cloud server is created by mirroring.
Cloud mirror image back end: the back end of the cloud mirror image is the physical storage for storing the mirror image. After the cloud mirror image is uploaded, the cloud mirror image can be stored in a storage back end connected with the mirror image service in a mirror image file mode, when a cloud server is created by using the mirror image and a hard disk is started by using the cloud, the computing service and the storage service can read the mirror image file in the storage connected with the mirror image service, and the cloud resource application action is completed.
With the popularization of cloud computing, the technology is mature, the audience is increased, and the services provided by cloud computing are diversified and complicated. The cloud mirror service is an important component service in the cloud computing service, and the demand for enhancing the functions of the cloud mirror service is increasing. In the currently widely used technology, the cloud mirror service already supports multiple storage backend forms, but at present most only supports docking one of multiple backend types, and does not support docking multiple backend types simultaneously.
In actual production application, corresponding to a set of cloud management platform, the cloud mirror image service can be only connected with one storage back end, and all the customer mirror images are stored in the physical back end. However, as the user group is enlarged and the demand diversification is increased, in order to better achieve user group isolation, prevent mutual influence of users, and ensure exclusive sharing of special user resources, the platform needs to perform classification operations such as private domain division and network isolation for users. For the mirror image service, although the private mirror image can be guaranteed to be used by a special user, for the public mirror image, the partition can cause that downloading operation is needed when the mirror image is read in a cross-domain mode, so that projects for creating a cloud hard disk and a cloud host from the cloud mirror image are limited by network transmission speed, often, due to the ineffectiveness factors such as network delay and large cloud mirror image files, the cloud mirror image acquisition time is too long, and the storage service, the computing service wait for the cloud hard disk and the cloud host to finish creating actions overtime, so that resources cannot be normally provided for the user.
Aiming at another situation, the cloud mirror image service is tried to be directly connected to the storage service, at the moment, the available domain division of the cloud mirror image service is synchronous with the storage service, and the defect that mirror image files are cached across available domains can be avoided. However, the direct docking of the storage service may cause a problem that a cloud image of the storage service across a network region cannot be obtained, and the cloud image still needs to be cached when the storage service crosses a physical storage back end, that is, a problem that the creation of a cloud host and a cloud hard disk fails is still not solved.
Disclosure of Invention
The technical task of the invention is to provide a method for docking a plurality of storage back ends by a cloud mirror image service, which can greatly improve the support capability of the mirror image service and increase the flexibility of the cloud mirror image service.
In order to achieve the purpose, the invention provides the following technical scheme:
a method for docking multiple storage back ends by a cloud mirror image service specifically comprises the following steps:
s1, setting configuration rules in the cloud mirror image service configuration file;
s2, setting a cloud mirror image service configuration file reading API;
s3, setting a cloud mirror image service client;
s4, setting a client response interface;
s5, setting a restfulAPI (application program interface) stored at the back end of the cloud mirror image service docking;
s6, setting a cloud mirror image to create a control flow;
and S7, adding keyword description to the hard disk type of the storage service.
Preferably, in step S1, a backend configuration group is newly added, a configuration item required by personalized configuration in the configuration group is newly added, a default _ backup configuration item is newly added, and an original enabled _ backups configuration item is expanded.
Preferably, the cloud-like mirroring service configuration file reading API is configured to identify a newly added configuration item, a configuration group and an extended configuration item in the configuration file.
Preferably, the cloud mirror image service client is set to operate a new-backup parameter for uploading the cloud mirror image, so that the client layer supports designated back-end storage when uploading the cloud mirror image.
Preferably, the set client response interface identifies a backskend parameter used when the specified back end uploads the cloud image, reads the value of the keyword, and transmits the back end ID as a calling parameter.
Preferably, the set cloud mirror image service extends parameters of restful API stored in the back end, identifies the individualized configuration information transmitted to the configuration group after analyzing the configuration file, and completes the targeted configuration of the storage back end.
Preferably, the cloud mirror image creation control flow assurance back end ID is set to be identified in the control flow as a parameter, and the source file is converted into a mirror image file and stored in the designated back end in the control flow from the source file to the back end.
Preferably, the keyword description is added to the storage service hard disk type, the hard disk type is identified as the hard disk type for the mirror image service, and the cloud mirror image is uploaded to the same storage back end of the cloud hard disk in the cloud mirror image creation process from the cloud hard disk.
In the method for the cloud mirror image service to be connected with the multiple storage back ends, the cloud mirror image service is connected with the multiple back ends in a butt joint mode, and the butt joint mode is a direct butt joint mode for physical storage such as block storage, local storage and the like. And the other is to interface to the physical storage through the storage service in the platform, and the interface mode can interface to all the physical storage available to the storage service, so that the adaptability and the flexibility are improved.
Compared with the prior art, the method for docking various storage back ends by the cloud mirror image service has the following outstanding beneficial effects: the method for the cloud mirror image service to be connected with the multiple storage back ends realizes the copy of the mirror image between the multiple back ends and the back ends by expanding the function of the cloud mirror image service, aims to provide the support for the cloud mirror image service to be connected with the multiple back end storages simultaneously and the support for the mirror image copy of the cross-storage back ends, ensures that the mirror image copies exist at least or can be quickly transmitted into the cross-available domain and the cross-storage back ends, ensures that the perception of a user on the bottom layer service is transparent, can greatly improve the support capability of the mirror image service, increases the flexibility of the cloud mirror image service, lays a foundation for the introduction of subsequent edge cloud computing, and has good popularization and application values.
Drawings
Fig. 1 is a schematic diagram of a configuration mode of a plurality of backend connections of a cloud mirror service in the method for the cloud mirror service to connect a plurality of storage backend connections according to the present invention.
Detailed Description
The method for the cloud mirror image service to interface with multiple storage backend according to the present invention will be described in further detail with reference to the accompanying drawings and embodiments.
Examples
The invention discloses a method for docking multiple storage back ends by cloud mirror image service, which comprises the following steps:
and S1, setting configuration rules in the cloud image service configuration file.
Adding a back-end configuration group, configuring configuration items needed by the back end in the configuration group in a personalized manner, adding a default _ backend configuration item, using the default _ backend configuration item as a default back end for docking cloud mirror image services, using the default back end as a default back end for providing services without designation, and expanding the original enabled _ backends configuration item as a basis for all back ends to be used.
And S2, setting a cloud image service configuration file reading API, so that the API can identify newly added configuration items and configuration groups in the configuration file and expanded configuration items.
S3, setting a cloud mirror image service client, adding a parameter of 'back' for the cloud mirror image uploading operation, and ensuring that the client layer supports designated back-end storage when uploading the cloud mirror image.
S4, setting a client response interface to enable the client response interface to recognize a "- -background" parameter used when the designated back end uploads the cloud image, reading the value of the keyword, and enabling the back end ID to be transmitted as a calling parameter.
S5, the cloud mirror image service is set to be in butt joint with a restful API stored at the back end, parameters of the restful API are expanded, the parameters can be identified to enable the parameters to identify personalized configuration information in the configuration group transmitted after the configuration file is analyzed, and the targeted configuration of the storage back end is completed.
S6, setting a cloud mirror image to create a control flow, ensuring that a back end ID as a parameter can be identified in the control flow, and converting a source file into a mirror image file to be stored at the specified back end in the control flow from the source file to the back end.
S7, adding keyword description in the storage service hard disk type, and identifying the hard disk type as a special hard disk type for the butt-joint mirror image service, so as to ensure that the cloud mirror image is uploaded to the same storage back end as the cloud hard disk in the process of creating the cloud mirror image from the cloud hard disk, ensure the isolation of the back end type, the user group and the available domain, and meet the customization requirement.
As shown in fig. 1, in the method for docking multiple storage backend by using cloud mirror image service, two configuration modes are provided for docking multiple backend by using cloud mirror image service, and one docking mode is direct docking of physical storage, such as block storage and local storage. And the other is to interface to the physical storage through a storage service in the platform, and the interface can interface to all physical storage available to the storage service, such as the input g2, the input g5 and the like, so that the adaptability and the flexibility are improved.
The method for docking the cloud mirror image service to the various storage back ends needs to initialize partial configuration when the cloud computing platform is built, and the specific use method is as follows:
1. and upgrading the cloud mirror image service client to ensure the identification of the newly added parameters.
2. It is clear which back-ends need to be configured.
3. Adding related configuration in the mirror image service, wherein 1) "enabled _ backings" keyword is added with a back end ID as an identification of an available back end, and only the back end appearing after the configuration item is the available back end; 2) the 'default _ backings' keyword is also a back-end ID, only one back-end ID can be written after the configuration item, and the back-end can be used as a default back-end when a cloud mirror image is created by a storage back-end which does not specify a back-end upload mirror image and irrelevant key word identification; 3) a series of configuration groups are further required to be added to embody the backend personalized configurations in the "enable _ backings", and the specific backend configurations are not illustrated here because different backend have different customization requirements.
4. And after the configuration is modified, the cloud mirror image service needs to be restarted, so that the configuration is ensured to be effective.
5. Regarding the special situation of the cloud mirror image service for docking the storage service, a hard disk type for docking the cloud mirror image service needs to be created in the storage service, a special keyword identifier is given to the type, and meanwhile, an upload related configuration item is added to the back end, so that the cloud mirror image is stored in the corresponding back end instead of the default back end when the cloud hard disk creates the cloud mirror image.
The above-described embodiments are merely preferred embodiments of the present invention, and general changes and substitutions by those skilled in the art within the technical scope of the present invention are included in the protection scope of the present invention.
Claims (8)
1. A method for docking multiple storage back ends by a cloud mirror image service is characterized in that: the method specifically comprises the following steps:
s1, setting configuration rules in the cloud mirror image service configuration file;
s2, setting a cloud mirror image service configuration file reading API;
s3, setting a cloud mirror image service client;
s4, setting a client response interface;
s5, setting a restfulAPI (application program interface) stored at the back end of the cloud mirror image service docking;
s6, setting a cloud mirror image to create a control flow;
and S7, adding keyword description to the hard disk type of the storage service.
2. The method for cloud mirroring service interfacing to a plurality of storage backend according to claim 1, wherein: in step S1, a back-end configuration group is newly added, a configuration item required for personalized configuration in the configuration group is newly added, a default _ backup configuration item is newly added, and an original enabled _ backups configuration item is expanded.
3. The method for cloud mirroring service interfacing to a plurality of storage backend according to claim 2, wherein: and reading the API by the cloud mirror image service configuration file to enable the API to identify newly added configuration items, configuration groups and expanded configuration items in the configuration file.
4. The method for cloud mirroring service interfacing to a plurality of storage backend according to claim 3, wherein: the cloud mirror image uploading operation is newly added with a backup parameter by the cloud mirror image service client, so that the client layer supports the designated back-end storage when the cloud mirror image is uploaded.
5. The method for cloud mirroring service interfacing to a plurality of storage backend according to claim 4, wherein: and the set client response interface identifies a backup parameter used when the designated back end uploads the cloud mirror image, reads the value of the keyword, and transmits the back end ID as a calling parameter.
6. The method for cloud mirroring service interfacing to a plurality of storage backend according to claim 5, wherein: the setting cloud mirror image service expands the parameters of restfulAPI stored in the back end, identifies the individualized configuration information transmitted to the configuration group after the configuration file is analyzed, and completes the targeted configuration of the storage back end.
7. The method for cloud mirroring service interfacing to a plurality of storage backend according to claim 6, wherein: and setting a cloud mirror image to establish a control flow, ensuring that a back end ID is identified in the control flow as a parameter, and converting a source file into a mirror image file in the control flow from the source file to the back end to be stored at the appointed back end.
8. The method for cloud mirroring service interfacing to a plurality of storage backend according to claim 7, wherein: the method comprises the steps of adding keyword description to the storage service hard disk type, identifying the hard disk type as the hard disk type for the mirror image service, and ensuring that the cloud mirror image is uploaded to the same storage back end of the cloud hard disk in the cloud mirror image creating process from the cloud hard disk.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011328799.9A CN112433677A (en) | 2020-11-24 | 2020-11-24 | Method for docking multiple storage back ends by cloud mirror image service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011328799.9A CN112433677A (en) | 2020-11-24 | 2020-11-24 | Method for docking multiple storage back ends by cloud mirror image service |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112433677A true CN112433677A (en) | 2021-03-02 |
Family
ID=74693969
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011328799.9A Pending CN112433677A (en) | 2020-11-24 | 2020-11-24 | Method for docking multiple storage back ends by cloud mirror image service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112433677A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113791796A (en) * | 2021-11-15 | 2021-12-14 | 北京金山云网络技术有限公司 | Cross-domain mirror image generation method, mirror image installation method, device and electronic equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120102494A1 (en) * | 2010-10-20 | 2012-04-26 | Microsoft Corporation | Managing networks and machines for an online service |
| US20120102487A1 (en) * | 2010-10-20 | 2012-04-26 | Microsoft Corporation | Creating and deploying service-ready virtual hard disks |
| CN108809733A (en) * | 2018-07-11 | 2018-11-13 | 郑州云海信息技术有限公司 | A kind of system of multinode deployment docking OpenStack cloud management platforms |
| CN109445711A (en) * | 2018-11-07 | 2019-03-08 | 郑州云海信息技术有限公司 | A kind of method and device for business processing based on cloud platform |
| CN109495555A (en) * | 2018-11-01 | 2019-03-19 | 郑州云海信息技术有限公司 | A kind of method and apparatus based on cloud platform creation cloud host |
| CN110673924A (en) * | 2019-09-06 | 2020-01-10 | 北京浪潮数据技术有限公司 | Multi-architecture container cloud mirror image selection method, device, equipment and storage medium |
-
2020
- 2020-11-24 CN CN202011328799.9A patent/CN112433677A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120102494A1 (en) * | 2010-10-20 | 2012-04-26 | Microsoft Corporation | Managing networks and machines for an online service |
| US20120102487A1 (en) * | 2010-10-20 | 2012-04-26 | Microsoft Corporation | Creating and deploying service-ready virtual hard disks |
| CN108809733A (en) * | 2018-07-11 | 2018-11-13 | 郑州云海信息技术有限公司 | A kind of system of multinode deployment docking OpenStack cloud management platforms |
| CN109495555A (en) * | 2018-11-01 | 2019-03-19 | 郑州云海信息技术有限公司 | A kind of method and apparatus based on cloud platform creation cloud host |
| CN109445711A (en) * | 2018-11-07 | 2019-03-08 | 郑州云海信息技术有限公司 | A kind of method and device for business processing based on cloud platform |
| CN110673924A (en) * | 2019-09-06 | 2020-01-10 | 北京浪潮数据技术有限公司 | Multi-architecture container cloud mirror image selection method, device, equipment and storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113791796A (en) * | 2021-11-15 | 2021-12-14 | 北京金山云网络技术有限公司 | Cross-domain mirror image generation method, mirror image installation method, device and electronic equipment |
| CN113791796B (en) * | 2021-11-15 | 2022-03-04 | 北京金山云网络技术有限公司 | Cross-domain mirror image generation method, mirror image installation method, device and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7158482B2 (en) | Method, computer-readable medium, and system for resolution of violations in client synchronization | |
| AU2018220059B2 (en) | Type-to-type analysis for cloud computing technical components | |
| US10585691B2 (en) | Distribution system, computer, and arrangement method for virtual machine | |
| CN103765371B (en) | Derive the data-storage system as the logical volume of storage object | |
| US8495352B2 (en) | System and method for instantiation of distributed applications from disk snapshots | |
| JP2019517043A (en) | Automatic update of hybrid application | |
| US20110196840A1 (en) | System and method for incremental backup storage | |
| US20120079502A1 (en) | Dependency-ordered resource synchronization | |
| CN104050216B (en) | For customizing the file system manager of resource allocation | |
| US20080195827A1 (en) | Storage control device for storage virtualization system | |
| CN106168884A (en) | Access the computer system of object storage system | |
| JP2004046661A (en) | Method and device for virtual unification of plurality of network storages | |
| CN111090498B (en) | Virtual machine starting method and device, computer readable storage medium and electronic equipment | |
| CN106331075B (en) | Method for storing file, metadata server and manager | |
| JP2022549983A (en) | Content item sharing with context | |
| US20140006351A1 (en) | Method, a server, a system and a computer program product for copying data from a source server to a target server | |
| US11144292B2 (en) | Packaging support system and packaging support method | |
| CN112433677A (en) | Method for docking multiple storage back ends by cloud mirror image service | |
| US20210176138A1 (en) | Data center cartography bootstrapping from process table data | |
| US9305000B1 (en) | Creating and publishing service level representations of applications from operational representations | |
| KR102370857B1 (en) | Method and system for selective transfer of organizational data in case of divestiture | |
| CN116233115B (en) | Efficient continuous controlled sharing distribution method and system for mass data files | |
| US11442822B1 (en) | Providing an efficient preview capability for restoring emails backed up to an object storage | |
| WO2016087640A1 (en) | Type-to-type analysis for cloud computing technical components | |
| CN103765370B (en) | Access the computer system of object storage system |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210302 |
|
| RJ01 | Rejection of invention patent application after publication |