WO2016209313A1 - Exécution de tâches dans un réseau de stockage san - Google Patents

Exécution de tâches dans un réseau de stockage san Download PDF

Info

Publication number
WO2016209313A1
WO2016209313A1 PCT/US2015/067030 US2015067030W WO2016209313A1 WO 2016209313 A1 WO2016209313 A1 WO 2016209313A1 US 2015067030 W US2015067030 W US 2015067030W WO 2016209313 A1 WO2016209313 A1 WO 2016209313A1
Authority
WO
WIPO (PCT)
Prior art keywords
storage
blocks
range
task
san
Prior art date
Application number
PCT/US2015/067030
Other languages
English (en)
Inventor
Dhanaraj MARUTHACHALAM
Shanmugaraja NALLASAMY
Piyush Prakash MOGHE
Original Assignee
Hewlett-Packard Development Company, L.P.
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 Hewlett-Packard Development Company, L.P. filed Critical Hewlett-Packard Development Company, L.P.
Publication of WO2016209313A1 publication Critical patent/WO2016209313A1/fr

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/061—Improving I/O performance
    • 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/0662—Virtualisation aspects
    • G06F3/0665—Virtualisation aspects at area level, e.g. provisioning of virtual or logical volumes
    • 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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Definitions

  • a Storage Area Network is a high-speed network that may connect multiple storage devices with multiple servers.
  • a SAN provides block-level storage that may be accessed by applications running on any associated server.
  • a storage area network removes storage from servers and consolidates it in a manner that each server in a SAN may access shared storage as if it is directly attached to the server.
  • a SAN thus serves as a pool of storage for servers in the network.
  • FIG. 1 is a block diagram of an example Storage Area Network (SAN);
  • SAN Storage Area Network
  • FIG. 2 is a diagram of an example computing device for executing a task in a Storage Area Network (SAN);
  • SAN Storage Area Network
  • FIG. 3 is a block diagram of an example method for executing a task in a Storage Area Network (SAN).
  • SAN Storage Area Network
  • FIG. 4 is a block diagram of an example system for executing a task in a Storage Area Network (SAN). Detailed Description
  • a Storage Area Network typically includes a network of storage devices that are generally not accessible through the local area network (LAN) by other devices.
  • a SAN may present shared pools of storage devices to one or more host devices (for example, servers).
  • host devices for example, servers.
  • physical storage space provided by storage devices in a SAN may be presented as a logical storage space to host devices.
  • Such logical storage space may be identified using a "Logical Unit Number" (LUN).
  • LUNs may be used to identify individual or collections of physical disk devices for address by a protocol associated with a SCSI, iSCSI, Fibre Channel (FC), and the like.
  • the existing SAN features may be performed on an entire LUN, and each LUN may be dedicated to a specific purpose. This is not an ideal situation since it may lead to additional computation overhead and additional disk space utilization, and may also affect the performance of a storage device (for example, a storage array) in a SAN.
  • a storage device for example, a storage array
  • a host device may be allowed to dynamically select a range of blocks on a Logical Unit Number (LUN) of a storage system in a Storage Area Network (SAN). Further to the selection, a task may be performed at the storage system on the range of blocks selected by the host.
  • LUN Logical Unit Number
  • SAN Storage Area Network
  • FIG. 1 is a diagram of a Storage Area Network (SAN) 100, according to an example.
  • Storage Area Network (SAN) 100 may include a plurality of host devices 104, 106, 108, and 110, and a plurality of storage devices 120, 122, 124, and 126. Although only four devices and four storage devices are shown in FIG. 1, other examples of this disclosure may include more or fewer number of host devices and storage devices.
  • Host devices 104, 106, 108, and 110 may be communicatively coupled to storage devices 120, 122, 124, and 126, for example, via a SAN "fabric" 112.
  • the SAN fabric may interconnect host devices 104, 106, 108, and 110, and storage devices 120, 122, 124, and 126.
  • SAN fabric 112 may include one or more network devices, for example, hubs, network switches, network routers, virtual switches, virtual routers, cables, and the like.
  • a host device (for example, 104, 106, 108, and 110) may connect to the SAN fabric 112 via one or more Host Bus Adaptors (HBAs).
  • HBAs Host Bus Adaptors
  • Some example communication protocols that may be used by host devices 104, 106, 108, and 110, to communicate with storage devices 120, 122, 124, and 126 via SAN fabric 112 may include Fibre Channel (FC), Ethernet, Internet Small Computer System Interface (iSCSI), HyperSCSI, ATA over Ethernet (AoE), and Fibre Channel over Ethernet (FCoE).
  • FC Fibre Channel
  • iSCSI Internet Small Computer System Interface
  • iE HyperSCSI
  • AoE ATA over Ethernet
  • FCoE Fibre Channel over Ethernet
  • one or more client computing devices may be communicatively coupled to one or more host devices 104, 106, 108, and 110, for example, via a network.
  • the network may be a wired or wireless network.
  • the network may be a Local Area Network (LAN), a Wireless Local Area Network (WAN), a Metropolitan Area Network (MAN), a public network (for example, the Internet) or a private network (for example, an intranet).
  • Host devices 104, 106, 108, and 110 thus may act as a point of interface between client computing devices and storage devices 120, 122, 124, and 126.
  • Host devices 104, 106, 108, and 110 may each represent any type of computing system capable of reading machine-executable instructions. Examples of host devices 104, 106, 108, and 110 may include, without limitation, a server, a desktop computer, a notebook computer, a tablet computer, a thin client, a mobile device, a personal digital assistant (PDA), a phablet, and the like. Host devices 104, 106, 108, and 110 may each include one or more computer applications (machine-executable instructions). Some non-limiting examples of the applications may include a file system, a database, an email application, and the like. Host devices 104, 106, 108, and 110 may use one or more storage devices 120, 122, 124, and 126, for example, for storage, modification, retrieval, and transfer of data, snapshot data, replication data, backup data, or other data.
  • storage devices 120, 122, 124, and 126 for example, for storage, modification, retrieval, and transfer of
  • host device 104 may include a selection module 114 and a task module 116.
  • module may refer to a software component (machine readable instructions), a hardware component or a combination thereof.
  • a module may include, by way of example, components, such as software components, processes, tasks, co-routines, functions, attributes, procedures, drivers, firmware, data, databases, data structures, Application Specific Integrated Circuits (ASIC) and other computing devices.
  • a module may reside on a volatile or non-volatile storage medium and configured to interact with a processor of a computing device.
  • host device 104 is shown to include a selection module 114 and a task module 116.
  • any or all of the other host devices i.e. 106, 108, and 110
  • Storage devices 120, 122, 124, and 126 may be, for example, a storage array, which may include one or more storage drives (for example, hard disk drives, solid state drives, etc.), a storage tape, a solid state drive, a USB drive, a Serial Advanced Technology Attachment (SATA) disk drive, a Fibre Channel (FC) disk drive, a Serial Attached SCSI (SAS) disk drive, a magnetic tape drive, an optical jukebox, a Redundant Array of Independent Disks (RAID), and the like.
  • storage devices 120, 122, 124, and 126 may handle storage traffic from, for example, host devices 104, 106, 108, and 110.
  • Storage devices 120, 122, 124, and 126 may be used, for example, for storage of data, snapshot data, replication data, backup data, or other data.
  • physical storage space provided by storage devices 120, 122, 124, and 126 may be presented as a logical storage space to host devices 104, 106, 108 and 110.
  • Such logical storage space also referred as “logical volume”, “virtual disk”, or “storage volume”
  • LUN Logical Unit Number
  • physical storage space provided by storage devices 120, 122, 124, and 126 may be presented as multiple logical volumes to host devices 104, 106, 108, and 110.
  • each of the logical storage spaces may be referred to by a separate LUN.
  • a LUN may refer to the entire physical disk, or a subset of the physical disk or disk volume.
  • physical storage space provided by the disk drives may be aggregated as a logical storage space.
  • the aggregated logical storage space may be divided into multiple logical storage volumes, wherein each logical storage volume may be referred to by a separate LUN.
  • LUNs may be used to identify individual or collections of physical disk devices for address by a protocol associated with, for example, a SCSI, iSCSI, or Fibre Channel (FC).
  • FIG. 2 is a block diagram of an example computing device 200 for executing a task in a Storage Area Network (SAN).
  • computing device 200 may be analogous to any of the host devices 104, 106, 108 and 110 of FIG. 1, in which like reference numerals correspond to the same or similar, though perhaps not identical, components.
  • components or reference numerals of FIG. 2 having a same or similarly described function in FIG. 1 are not being described in connection with FIG. 2. Said components or reference numerals may be considered alike.
  • Computing device 200 may represent any type of computing system capable of reading machine-executable instructions. Examples of computing device 200 may include, without limitation, a server, a desktop computer, a notebook computer, a tablet computer, a thin client, a mobile device, a personal digital assistant (PDA), a phablet, and the like.
  • Examples of computing device 200 may include, without limitation, a server, a desktop computer, a notebook computer, a tablet computer, a thin client, a mobile device, a personal digital assistant (PDA), a phablet, and the like.
  • PDA personal digital assistant
  • computing device 200 may include a selection module 114 and a task module 116.
  • Selection module 114 may dynamically select a range of blocks on a Logical Unit Number (LUN) of a storage system in a Storage Area Network (SAN) (for example, 100).
  • LUN Logical Unit Number
  • SAN Storage Area Network
  • physical storage space provided by the storage system may be presented as a logical storage space to computing device 200.
  • the logical storage space (or storage volume) may be identified using a Logical Unit Number (LUN).
  • the storage system may provide block level storage.
  • a logical storage space (or logical volume) may be divided into blocks.
  • a "block” may be defined as a sequence of bytes or bits, having a nominal length (a block size). Data (for example, a file) may be organized into a block.
  • a block may be of fixed length or variable length.
  • a block may be defined at a logical storage level or at physical storage disk level.
  • an application on computing device 200 may dynamically select one or more blocks on a Logical Unit Number (LUN) of the storage system for executing a task.
  • the selected blocks may include consecutive blocks.
  • the storage system may include a plurality of storage devices.
  • the physical storage space provided by individual storage devices may be presented as multiple logical volumes to computing device 200.
  • each of the logical storage spaces may be referred to by a separate LUN.
  • the storage system is a storage array comprising multiple storage disk drives
  • physical storage space provided by the disk drives may be aggregated as a logical storage space.
  • the aggregated logical storage space may be divided into multiple logical storage volumes, wherein each logical storage volume may be referred to by a separate LUN.
  • an application on computing device 200 may dynamically select one or more blocks on any of the LUNs of the storage system for performing an action.
  • Task module 116 may execute, at the storage system, a task on the range of blocks selected by the computing device.
  • a task on the range of blocks selected by the computing device In other words, once the computing device selects one or more blocks on a Logical Unit Number (LUN) of the storage system in the Storage Area Network (SAN) (for example, 100), task module 116 may perform an action or operation on the selected blocks at the storage system.
  • Task module may perform a variety of tasks or actions on the selected blocks. Some non-limiting examples are enumerated below.
  • task module 116 may generate a snapshot of the blocks selected by the computing device 200. Snapshot may be defined as a mechanism to record the state of a storage system at a given point of time. A snapshot may create a point-in-time copy of the data in the blocks selected by the computing device 200. Task module 116 may create a snapshot of the selected blocks using different methodologies. For example, task module may use "Copy-on-write" approach. In this method, task module 116 may create a snapshot of a storage volume in a pre- designated storage space. When an application writes to a block, the contents of the original block that is to be overwritten are moved to a new location in the snapshot file.
  • the original data block may be moved to the snapshot storage volume, prior to the write onto the block.
  • a subsequent read request may be directed to the original volume. If a request relates to changed data, the request may be directed to blocks in the snapshot file. If a request pertains to unchanged data, it may be served by the original volume.
  • task module 116 may use "Redirect-on-write" for generating a snapshot of the selected blocks.
  • a new write to the original data may be redirected to another location earmarked for snapshot.
  • redirect-on-write the original data is "frozen” and any write changes to the original data i.e. "changed data” is written elsewhere on the disk. This eliminates the three step “read, rewrite and write” process associated with copy-on-write and reduces snapshots to just one "write” step.
  • task module 116 may replicate data in the blocks selected by the computing device 200 to another storage device(s), which in an instance, may be present at a remote location(s) relative to the computing device 200.
  • task module 116 may create a backup of the blocks selected by the computing device 200 to another storage device(s), which may be present at a local site or a remote location(s) relative to the computing device 200.
  • the backup of the blocks may be carried out on a storage device such as, but not limited to, a magnetic tape, a disk, a storage array, and the like.
  • task module 116 may generate a mirrorclone of the blocks selected by the computing device 200.
  • a live copy of the selected blocks may be generated that maintains a relationship with the selected blocks since they are always kept in sync.
  • a mirrorclone may be automatically updated whenever the source is updated.
  • task module 116 may perform thin provisioning or thick provisioning on the blocks selected by the computing device 200.
  • task module may dynamically set the selected blocks to a thin or thick provisioning mode.
  • Thin provisioning may be called as "just-in-time" provisioning.
  • Thin provisioning (TP) optimizes the efficiency with which the available space may be utilized in a storage device.
  • Thin provisioning may allow allocation of selected blocks in a flexible manner among multiple clients (for example, LUNs).
  • Thin provisioning may enable provisioning of more storage on a LUN than what may be currently available on a volume.
  • a thin provisioned storage system may include a virtual storage capacity and a real storage capacity.
  • the amount of storage capacity on a disk is pre-allocated on physical storage at the time the disk is created.
  • Thick provisioning may pre-allocate storage capacity on a disk rather than on need basis.
  • Disks in this format may be created with the entire size of the disk pre-allocated on physical storage at the time the disk is created.
  • task module 116 may perform a deduplication on data in the blocks selected by the computing device 200.
  • Data deduplication may be defined as a technique for eliminating redundant data. Data deduplication eliminates duplicate copies of blocks of data. Data deduplication may eliminate additional copies, and save just one copy of the data. The additional copies may be replaced with pointers that lead back to the original copy. By performing data deduplication, task module 116 may eliminate duplicate copies of the selected blocks from the storage system.
  • FIG. 3 is a block diagram of an example method 300 for executing a task in a Storage Area Network (SAN).
  • the method 300 may be partially executed on a computing device such as host devices 104, 106, 108, and 100 of FIG. 1 or computing device 200 of FIG. 2. However, other suitable computing devices may execute method 300 as well.
  • a host device may be allowed to dynamically select a range of blocks on a Logical Unit Number (LUN) of a storage system in a Storage Area Network (SAN).
  • LUN Logical Unit Number
  • SAN Storage Area Network
  • a task may be executed at the storage system on the range of blocks selected by the host.
  • FIG. 4 is a block diagram of an example system 400 for executing a task in a Storage Area Network (SAN).
  • System 400 includes a processor 402 and a machine- readable storage medium 404 communicatively coupled through a system bus.
  • system 400 may be analogous to host devices 104, 106, 108 and 110 of FIG. 1 or computing device 200 of FIG. 2.
  • Processor 402 may be any type of Central Processing Unit (CPU), microprocessor, or processing logic that interprets and executes machine-readable instructions stored in machine-readable storage medium 404.
  • Machine-readable storage medium 404 may be a random access memory (RAM) or another type of dynamic storage device that may store information and machine-readable instructions that may be executed by processor 402.
  • RAM random access memory
  • machine-readable storage medium 404 may be Synchronous DRAM (SDRAM), Double Data Rate (DDR), Rambus DRAM (RDRAM), Rambus RAM, etc. or storage memory media such as a floppy disk, a hard disk, a CD-ROM, a DVD, a pen drive, a flash memory, and the like.
  • machine-readable storage medium may be a non-transitory machine-readable medium.
  • Machine-readable storage medium 404 may store instructions 406 and 408.
  • instructions 406 may be executed by processor 402 to allow an application to dynamically select a range of blocks on a LUN of a storage system in a Storage Area Network (SAN).
  • Instructions 408 may be executed by processor 402 to execute, at the storage system, a task on the range of blocks selected by the host.
  • the example method of FIG. 3 is shown as executing serially, however it is to be understood and appreciated that the present and other examples are not limited by the illustrated order.
  • the example systems of FIGS. 1, 2 and 4, and method of FIG. 3 may be implemented in the form of a computer program product including computer-executable instructions, such as program code, which may be run on any suitable computing device in conjunction with a suitable operating system (for example, Microsoft Windows, Linux, UNIX, and the like).
  • a suitable operating system for example, Microsoft Windows, Linux, UNIX, and the like.
  • Embodiments within the scope of the present solution may also include program products comprising non-transitory computer-readable media for carrying or having computer-executable instructions or data structures stored thereon.
  • Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer.
  • Such computer-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROM, magnetic disk storage or other storage devices, or any other medium which can be used to carry or store desired program code in the form of computer-executable instructions and which can be accessed by a general purpose or special purpose computer.
  • the computer readable instructions can also be accessed from memory and executed by a processor.

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

Selon des modes de réalisation donnés à titre d'exemple, la présente invention concerne l'exécution d'une tâche dans un réseau de stockage SAN. Dans un exemple, un dispositif hôte peut être autorisé à sélectionner de manière dynamique une plage de blocs sur un numéro d'unité logique (LUN) d'un système de mémorisation dans un réseau de stockage SAN. Une tâche peut être exécutée au niveau du système de mémorisation sur la plage de blocs sélectionnée par le dispositif hôte.
PCT/US2015/067030 2015-06-23 2015-12-21 Exécution de tâches dans un réseau de stockage san WO2016209313A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN3150CH2015 2015-06-23
IN3150/CHE/2015 2015-06-23

Publications (1)

Publication Number Publication Date
WO2016209313A1 true WO2016209313A1 (fr) 2016-12-29

Family

ID=57585251

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2015/067030 WO2016209313A1 (fr) 2015-06-23 2015-12-21 Exécution de tâches dans un réseau de stockage san

Country Status (1)

Country Link
WO (1) WO2016209313A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10452503B2 (en) 2017-09-29 2019-10-22 Hewlett Packard Enterprise Development Lp Bidirectional replication
US10732903B2 (en) 2018-04-27 2020-08-04 Hewlett Packard Enterprise Development Lp Storage controller sub-LUN ownership mapping and alignment

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130275690A1 (en) * 2005-05-24 2013-10-17 Hitachi, Ltd. Storage system and operation method of storage system
US20130318228A1 (en) * 2012-05-23 2013-11-28 Vmware, Inc. Fabric Distributed Resource Scheduling
US20140157046A1 (en) * 2012-11-30 2014-06-05 International Business Machines Corporation Techniques for dynamically tracking logical units moving between input/output ports of a storage area network target
US20140304239A1 (en) * 2013-04-05 2014-10-09 Netapp, Inc. Systems and methods for scheduling deduplication of a storage system
US20150113183A1 (en) * 2008-02-28 2015-04-23 International Business Machines Corporation Zoning of Devices in a Storage Area Network with LUN Masking/Mapping

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130275690A1 (en) * 2005-05-24 2013-10-17 Hitachi, Ltd. Storage system and operation method of storage system
US20150113183A1 (en) * 2008-02-28 2015-04-23 International Business Machines Corporation Zoning of Devices in a Storage Area Network with LUN Masking/Mapping
US20130318228A1 (en) * 2012-05-23 2013-11-28 Vmware, Inc. Fabric Distributed Resource Scheduling
US20140157046A1 (en) * 2012-11-30 2014-06-05 International Business Machines Corporation Techniques for dynamically tracking logical units moving between input/output ports of a storage area network target
US20140304239A1 (en) * 2013-04-05 2014-10-09 Netapp, Inc. Systems and methods for scheduling deduplication of a storage system

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10452503B2 (en) 2017-09-29 2019-10-22 Hewlett Packard Enterprise Development Lp Bidirectional replication
US10732903B2 (en) 2018-04-27 2020-08-04 Hewlett Packard Enterprise Development Lp Storage controller sub-LUN ownership mapping and alignment

Similar Documents

Publication Publication Date Title
US10001947B1 (en) Systems, methods and devices for performing efficient patrol read operations in a storage system
US9009724B2 (en) Load balancing data access in virtualized storage nodes
US9928003B2 (en) Management of writable snapshots in a network storage device
US11561949B1 (en) Reconstructing deduplicated data
US8521685B1 (en) Background movement of data between nodes in a storage cluster
US7778960B1 (en) Background movement of data between nodes in a storage cluster
US10691354B1 (en) Method and system of disk access pattern selection for content based storage RAID system
US20180275919A1 (en) Prefetching data in a distributed storage system
US9665306B1 (en) Method and system for enhancing data transfer at a storage system
US9870176B2 (en) Storage appliance and method of segment deduplication
US20130311429A1 (en) Method for controlling backup and restoration, and storage system using the same
CN107111531B (zh) 使用分配图的数据恢复的系统、方法和存储介质
US20180260281A1 (en) Restoring a storage volume from a backup
US9727485B1 (en) Metadata rewrite and flatten optimization
US20170277729A1 (en) Application aware export to object storage of low-reference data in deduplication repositories
US10585763B2 (en) Rebuild rollback support in distributed SDS systems
US10503426B2 (en) Efficient space allocation in gathered-write backend change volumes
JP2017531892A (ja) ブロックレベル記憶デバイスのスナップショットを実行するための改善された装置および方法
US20150261465A1 (en) Systems and methods for storage aggregates and infinite storage volumes
US10956273B2 (en) Application aware export to object storage of low-reference data in deduplication repositories
US11157198B2 (en) Generating merge-friendly sequential IO patterns in shared logger page descriptor tiers
WO2016209313A1 (fr) Exécution de tâches dans un réseau de stockage san
WO2017034610A1 (fr) Reconstruction de volumes de stockage
CN113535467B (zh) 用于备份对象的方法、机器可读存储介质和计算设备
US20180165037A1 (en) Storage Reclamation in a Thin Provisioned Storage Device

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: 15896591

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15896591

Country of ref document: EP

Kind code of ref document: A1