I / O OPERATIONS IN LOG-STRUCTURED ARRAYS

The internal copy-on-write mechanism in LSAs addresses performance issues by reducing physical data movements and gaps, enhancing efficiency and extending SSD lifespan.

DE102021130358B4Active Publication Date: 2024-11-28INTERNATIONAL BUSINESS MACHINE CORPORATION
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
DE102021130358
Authority / Receiving Office
DE · DE
Patent Type
Patents
Current Assignee / Owner
Priority Date
2020-12-01
Filing Date
2021-11-19
Publication Date
2024-11-28
Estimated Expiration
2041-11-19

AI Technical Summary

Technical Problem

Existing data storage systems with log-structured arrays (LSAs) face performance issues due to gaps created by internal data movements during copy-on-write operations, leading to increased garbage collection frequency and disruption, particularly in virtual computing environments.

Method used

Implementing an internal copy-on-write (COW) mechanism that moves internal destination pointers from a virtual disk to a flash copy disk, reducing physical data movements and minimizing gaps in the LSA, thereby reducing the frequency of garbage collection operations.

Benefits of technology

This approach enhances performance by minimizing I/O moves, reducing computational time, and extending the lifespan of SSD disks by minimizing gaps in the log-structured array, thus optimizing data management efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

A computer-implemented method (200), comprising: Receiving (210) a write request for a storage disk by a storage controller, wherein the write request includes a data record; Determine (230) on the basis of a target mapping for a flash copy disk that the data set for a target area of ​​the storage disk has not been copied to a target location; Instruct (240) a log-structured array (LSA) to perform an internal copy-on-write (COW) operation on the record during the next input / output (I / O) operation on the storage medium; Move (250), based on the instruction for an internal COW, a first internal pointer of the destination from a virtual disk to the flash copy disk; and Creating a second internal pointer for the data set from the virtual disk to a bitmap for the storage disk.
Need to check novelty before this filing date? Find Prior Art

Description

BACKGROUND

[0001] Some computer storage systems offer point-in-time (POT) data copying capabilities. These capabilities may be available at the block storage level. For example, POT functions might include creating copies of data from an entire disk within a given storage unit. The copy establishes a relationship between a source disk and a destination disk. This established pair of disks acts as a POT, allowing read and write operations on both the source and destination disks. When a write operation is performed on the source disk, data can be copied to a destination, and then new data can be written to the source disk.

[0002] In this technical area, the document US 2017 / 0083250A1 has already been published. It also describes, in principle, a copy-redirect-on-write operation for managing storage using a time-sensitive copy-on-write technique. Despite these improvements already achieved, there remains a need to further optimize copy-on-write operations, especially for virtual computing environments. SUMMARY

[0003] This problem is solved by the subject matter of the independent claims. Further embodiments are described in the respective dependent claims. According to one embodiment described herein, a computer-implemented method for managing input / output operations (I / O operations) in log-structured arrays (LSAs) is provided. The method receives a write request for a storage medium. The write request comprises a data record. Based on a target assignment for a flash copy storage medium, the method determines that the data record for a target area of ​​the storage medium has not been copied to a target location. An LSA is instructed to perform an internal copy-on-write (COW) operation for the data record during the next I / O operation for the storage medium.Based on the instruction for an internal COW, the procedure moves an internal pointer of the destination from a virtual disk to the flash copy disk.

[0004] According to one embodiment described herein, a system for managing input / output (I / O) operations in log-structured arrays (LSAs) is provided. The system comprises one or more processors and a computer-readable storage medium connected to the one or more processors, which stores program instructions that, when executed by the one or more processors, cause the one or more processors to perform operations. The operations receive a write request to a storage medium. The write request includes a data record. Based on a target mapping for a flash copy disk, the operations determine that the data record for a target area of ​​the storage disk has not been copied to a target location.An LSA is instructed to perform an internal copy-on-write (COW) of the data record during the next I / O operation on the storage disk. Based on the instruction for an internal COW, the operations move an internal pointer of the destination from a virtual disk to the flash copy disk.

[0005] According to one embodiment described herein, a computer program product is provided for managing input / output (I / O) operations in log-structured arrays (LSAs). The computer program product comprises a computer-readable storage medium containing program instructions, wherein the program instructions are executable by one or more processors to cause the one or more processors to receive a write request for a storage medium. The write request comprises a data record. Based on a target mapping for a flash copy disk, the computer program product determines that the data record for a target area of ​​the storage medium has not been copied to a target location. An LSA is instructed to perform an internal copy-on-write (COW) operation on the data record during the next I / O operation on the storage medium.Based on the instruction for an internal COW, the computer program product moves an internal pointer of the destination from a virtual disk to the flash copy disk. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] The drawings included in this application are incorporated into the description and form part thereof. They show embodiments of the present disclosure and, together with the description, explain the principles of the disclosure. The drawings are only examples of certain embodiments and do not limit the disclosure. Fig. Figure 1 shows a block diagram of a data processing environment for implementing concepts and computer-aided procedures according to at least one embodiment. Fig. Figure 2 shows a flowchart of a computer-implemented method for managing I / O operations in LSA environments according to at least one embodiment. Fig. Figure 3 shows a flowchart of a computer-implemented method for managing I / O operations in LSA environments according to at least one embodiment. Fig. Figure 4 shows a block diagram of a computer system for managing I / O operations in LSA environments according to at least one embodiment. Fig. Figure 5 is a diagram of a cloud computing environment in which concepts of the present disclosure can be implemented according to an embodiment of the present disclosure. Fig. Figure 6 is a diagram of model layers of a cloud computing environment in which concepts of the present disclosure can be implemented according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0007] This disclosure relates generally to methods for managing I / O operations in LSA environments. In particular, but not exclusively, embodiments of this disclosure relate to a computer-implemented method for managing I / O operations in an LSA during block data backup in unified storage systems. This disclosure further relates to a related system for managing I / O operations in LSA environments and a computer program product for operating such a system.

[0008] Data storage systems and facilities are often built to handle processing challenges quickly and for a relatively large number of users. Some of these systems integrate database, processing, and storage into a single, compact system. These systems can be configured for analytical processing and designed for flexible growth. When analyzing raw data, business intelligence applications using these data storage systems can initiate many read input / output (read I / O) operations to gather data for processing. These applications can also send many write I / O operations to store intermediate data in temporary storage locations. These applications can use data storage system architectures with multiple hosts connected to multiple server blades, which in turn are connected to multiple disk drives.The multiple disks can be storage media visible from the storage system or storage system architecture. Each disk can contain multiple virtual disks. These virtual disks can be visible from higher layers of the system and used for at least temporary data storage. A storage control or storage controller cluster can enable the virtualization of the storage disks. These storage control components can also enable storage-level backups and snapshots, flash copies, or point-in-time data copies of virtual disks. These point-in-time data copies can be performed at the block level and can be used for various purposes.

[0009] When point-in-time copies are used in conjunction with log-structured arrays, write operations performed on point-in-time data copies can introduce gaps due to internal data shifts, creating invalid data locations. As these gaps increase, available memory can decrease. Garbage collection operations are used to remove gaps from the log-structured arrays. Garbage collection operations can be computationally intensive and may interrupt other operations.

[0010] Some data storage systems use file systems with log-structured arrays (LSA file systems). LSA systems can overcome write performance issues in some data storage systems by buffering a sequence of changes to the file system. The changes can be temporarily stored in a cache. Once a suitable number of changes, a certain time period, or another threshold condition is met, the changes can be written sequentially from the cache to a given disk. The sequential write can be performed in a single disk write operation. The changes written to disk can include file data blocks, attributes, index blocks, directories, or other information used to manage the file system.

[0011] Block storage systems can use a similar approach to log-structured block storage. In such systems, logical blocks can be defined for a disk. The logical blocks can point to the actual logical block address (LBA) of the disk. The LBAs of a logical disk (e.g., the LBAs for a virtual disk of the disk) in the block storage system can be managed as a log-structured array to manage write operations for the storage system. Each host write operation can be stored in new logical LBA locations where the data pointers are arranged. In such systems, write I / O operations and seek times for a physical LBA of the storage system can be avoided for each write operation. For example, the block storage system can create a disk from a block storage pool.The disk can be visible to a host application for performing I / O operations on the disk. The disk can have associated logical LBAs (Logical Locations) that internally point to physical LBA locations based on an allocation policy of a storage controller architecture for the block storage system. In this way, the block storage system can have a log-structured mapping at the storage pool level. Furthermore, the block storage system can represent a specific location as a pointer to a location in a ring buffer. When a host initiates a write I / O operation on a disk, the data can be written to the last pointer location of the LBA, and the pointer can be moved to the next logical location.

[0012] When data is written to a ring buffer in this way, each time a pointer is moved to the next location, an invalid location is created in the memory controller's LSA. The invalid data location can be a gap in the LSA. To be removed from the buffer, gaps are subjected to garbage collection operations. While the garbage collection process releases a logical block allocation (LBA) of a physical disk in the LSA, the operations are computationally intensive and cause an interruption in normal I / O operations. Garbage collection operations can be triggered when a threshold number of logical blocks in the LSA are occupied or when the number of gaps exceeds a certain threshold. During garbage collection operations, the logical and physical LBA addresses can be modified to make locations in the mapping of logical LBAs sequential.The LSA pointers can be updated so that the additional free locations of the logical LBAs can be used by the LSA or the storage controller. If garbage collection operations are used or become more frequent, the impact of these operations on the storage system increases.

[0013] Block storage systems can use point-in-time data copy functions, such as flash copies, to create copies of entire disks of data on a storage unit. A flash copy establishes a relationship between a source disk and a destination disk. The flash copy operation also creates a bitmap of the source disk. Once the relationship and the bitmap are created, the destination disk can be accessed as if the data had been physically copied. Similarly, a background process can also copy the traces from the source to the destination disk. The destination, or copy, created by the flash copy operation is a point-in-time copy of the source disk, and both the source and destination disks can be subjected to read and write operations.In some cases, a destination disk can be created as a flash copy when new data is to be written to a source disk. In such cases, the data from the source disk can be copied to the destination at a time T as T0 data. The data to be written to the source disk can be written as T1 data. Writing the T1 data can update a bitmap for a selected I / O location. In this way, an instant copy of the disk is created while actual data is being copied whenever write operations are initiated on the source disk. This operation can be described as a copy-on-write (COW) operation.

[0014] In log-structured arrays, memory-based snapshots can be configured in a storage virtualization using a COW operation. When an I / O write operation is sent to the storage system, a location of the LBA (Logical Copy Allocation) is detected at the logical volume level in a virtualization map. A virtualization engine or storage controller can parse an existing flash copy relationship and make a data move decision. If a source volume receives an I / O write operation and no previous flash copy has been created, the data is moved to the destination volume. A host I / O operation can then be written to the source volume. In these cases, the move from the source volume to the destination volume creates an internal I / O operation that increments an LSA pointer by one. The internal I / O operation also creates a gap in the LSA.When the operation is complete, a host write operation is stored at the last LSA pointer location. This internal shift creates a gap in the LSA. If source disks are write-oriented, the number of gaps in the LSA increases, and a garbage collection operation may be triggered. Repeated garbage collection operations can lead to performance issues and delays for host applications while the garbage collection operations are being processed.

[0015] Embodiments of the present disclosure enable efficient COW handling of data and operations in an LSA and similar implementations of storage systems. Some embodiments of the present disclosure enable a storage system to avoid gaps or empty spaces in a log storage array or log disks of a storage system. The present disclosure can reduce or avoid empty spaces in a log-structured array by enabling data shifts through write operations in a layered manner. In some embodiments, the present disclosure enables a distinction between internal data shifts and write operations of the host applications.Some embodiments of the present disclosure provide a mechanism by which an LSA algorithm distinguishes between COW shifts and write I / O operations to improve performance and data management efficiency in a storage system. In some embodiments, the present disclosure introduces methods and systems that enable the operation of a log-structured array and flash copy service modules in a storage management system. Embodiments of the present disclosure can provide a storage system with information relating to flash copy COW operations and internal data block shifts at the time of COW operations.In some embodiments, the present disclosure enables data exchange between two models in a memory management system for the implementation of incoming and outgoing APLs and enables instruction exchange between functional modules of the memory system.

[0016] Some embodiments of the concepts described herein may take the form of a system or a computer program product. For example, a computer program product may contain program instructions which, when executed by one or more processors of a data processing system, cause the data processing system to perform the operations described above in relation to the computer-implemented method. As another example, the system may include components such as processors and computer-readable storage media. The computer-readable storage media may interact with other components of the system to cause the system to execute program instructions which include operations of the computer-implemented method described herein.For the purposes of this description, a computer-usable or computer-readable medium can be any unit which may contain means for storing, transmitting, distributing or transporting the program for use by the system, device or unit for carrying out the instructions or in connection therewith.

[0017] With reference to Fig. Figure 1 shows a block diagram of an exemplary data processing environment 100. The present disclosure can be implemented in the exemplary data processing environment 100. In some embodiments, the data processing environment 100 can be integrated into or embodied by a computer system as described below. The data processing environment 100 can include a memory management system 102. The memory management system 102 can include a memory controller 110, a flash copy manager 120, and an array component 130. The memory controller 110 receives requests for one or more storage disks and coordinates operations for disks belonging to the memory management system 102. The flash copy manager 120 performs operations with respect to virtual storage disks for disks belonging to the memory management system 102.The array component 130 performs operations on a log-structured array of disks belonging to the memory management system 102. Although they are described as separate components, it is understood that in at least some embodiments the components can be combined or split and / or additional components can be added without deviating from the scope of this disclosure.

[0018] With reference to Fig. Figure 2 shows a flowchart of a computer-implemented method 200. The computer-implemented method 200 is a method for managing I / O operations in LSA environments. In some embodiments, the computer-implemented method 200 can be executed by one or more components of the data processing environment 100, as described in more detail below.

[0019] In Operation 210, the storage controller 110 receives a write request for a storage disk. In some embodiments, the write request includes a data record. The storage disk can be a single storage disk among a plurality of storage disks that the storage management system 102 can access or manage. The write request can be received from a host that interacts with a set of disks or a storage system connected to the storage management system 102. In some embodiments, the host can be a data processing unit operated by a user that interacts with a storage system or set of disks located remotely from the host. For example, the host can transmit a write request to the storage controller 110 over a data transmission network.The 110 storage controller can receive the write request in order to process and implement the write request on a data disk in a cloud-based storage system.

[0020] During Operation 220, Flash Copy Manager 120 determines a Copy-on-Write (COW) status for the storage device affected by the write request. In some embodiments, Flash Copy Manager 120 determines the COW status by detecting that COW functionality is enabled for the storage device in the storage system. Flash Copy Manager can determine the COW status for the storage device based on one or more configuration files for the storage device, a disk that hosts the storage device, or the storage system to which the storage device or disk belongs.

[0021] During operation 230, Flash Copy Manager 120 detects that the data record for the target area of ​​the storage disk was not copied to a destination. Flash Copy Manager 120 can determine that the data record was not copied based on a destination mapping for a flash copy disk. The destination mapping can represent data stored at specified data locations for a target disk. In some cases, the destination mapping represents data in a flash copy of a disk (e.g., a source disk) at a specific point in time. For example, the target disk might be a target disk at T0.

[0022] In some embodiments, the Flash Copy Manager 120 exchanges data with the Array Component 130 using an out-of-band protocol. The Flash Copy Manager 120 can exchange data with the Array Component 130 using reserved fields in a command descriptor block (CDB), such as a SCSI (Small Computer System Interface) CDB. The SCSI CDB can be an information block that describes a command. Each CDB can have a total of 6, 10, 12, or 16 bytes, or any suitable variable length. In some cases, the Flash Copy Manager 120 and the Array Component 130 exchange data using both the out-of-band protocol and the reserved fields in the CDB as layers in the Memory Management System 102.The Flash Copy Manager 120 and the Array Component 130 forward information across layers or using any other suitable independent mechanism. In some embodiments, a heatmap can be transferred from one storage system to another. The heatmap can be transferred to ensure that remote copies, which may fail when accessing remotely located sites, retain certain data on a given storage disk, disk, or SSD.

[0023] In operation 240, array component 130 instructs a log-structured array (LSA) to perform an internal COW operation. The internal COW operation can be performed on the record during the next input / output (I / O) operation on the storage disk. In some embodiments, the flash copy manager 120 transmits instructions to a storage pool configured as an LSA. The instructions specify that the next I / O operation will be an internal COW operation. The internal COW operation can write the record from the write request to a virtual disk (e.g., a source disk). Before writing the record, the internal COW operation can also create a copy of the virtual disk as the flash copy disk (e.g., the destination disk). The instructions can specify that the internal COW operation should be followed by an actual application host I / O write operation.

[0024] In operation 250, the memory controller 110 moves an internal pointer of the destination location from a virtual disk to the flash copy disk. In some embodiments, the internal pointer is moved based on an instruction for an internal COW. In such cases, the instruction for an internal COW is treated as a message to a gap prevention device in the memory controller 110 to move the internal pointer. In embodiments where the data record is written to the source disk and a destination disk is created as a flash copy, the internal pointer of the destination location is moved from a location on the source disk to a location on the destination disk. Moving the internal pointer of the destination location to the destination disk or flash copy disk prevents a gap from occurring in the LSA because the data record of the write request is written to the virtual disk or the source disk, respectively.After the flash copy disk is set up and the internal pointer is moved, the older version of the data in the LSA belonging to the write request is mapped to a pointer that points to the flash copy disk and represents the older logical source LBA.

[0025] In operation 260, array component 130 updates a bitmap for the LSA. In some embodiments, the bitmap is updated in response to a change in the internal pointer. If the internal pointer has been moved, array component 130 can update the bitmap for the LSA and send an instruction to the flash copy manager 120 to make the disk copies consistent across flash copy disks. After the bitmap update is complete and the disk copy consistency is established, a host application can be handled normally, incrementing an LSA pointer and storing data at a new location in a ring buffer. In such cases, a new pointer to the record of the write request can connect the virtual disk or the source disk to the record at the new location in the LSA.

[0026] Since a COW operation moves the internal pointer and creates a new one, the actual data copy to a physical disk is not required. Creating a flash copy using COW and moving pointers reduces I / O movements to physical locations. Reducing I / O movements can decrease the computational time and resources required to functionally execute the write request. Limiting I / O movements can improve the performance of an associated storage system. Furthermore, using COW and moving pointers minimizes gaps in the log-structured array, thereby reducing the frequency of garbage collection operations on the LSA. A reduced garbage collection frequency can also improve the health and lifespan of SSDs.

[0027] Fig. Figure 3 shows a flowchart of an embodiment of a computer-implemented method 300 for managing I / O operations in LSA environments. The method 300 can be performed by or within the data processing environment 100. In some embodiments, the method 300 includes or uses one or more operations of the method 200.

[0028] In Operation 310, the memory controller 110 detects a virtual disk for a storage disk associated with a write request. The virtual disk can be detected in response to the memory controller 110 receiving a write request containing a set of data to be written to the storage disk. In some embodiments, the memory controller 110 works in conjunction with the flash copy manager 120 to detect the virtual disk. The virtual disk can act as a buffer or cache for a physical storage medium (e.g., the storage disk).

[0029] In Operation 320, the storage controller 110 detects a flash copy disk for the storage disk. The flash copy can be a copy of the virtual storage disk at a specific point in time. In some embodiments, the flash copy disk is a previously created copy of the virtual disk. The flash copy disk can contain a complete copy of the data in the virtual disk at a specific point in time. This specific point in time can be any time before the write request is received. If no flash copy disk is detected, the flash copy manager 120 can be instructed to create a flash copy of the virtual disk at a time when the virtual disk is detected by the storage controller 110 or at a time when the write request is received.In some cases, the flash copy disk is detected or created in response to one or more of operations 220 and 230.

[0030] In Operation 330, Array Component 130 overwrites the data record on the virtual disk. In some embodiments, the data record replaces a set of previous values ​​on the virtual disk. In some cases, Array Component 130 overwrites the data record on the virtual disk by inserting the data record into a logical LBA mapping for the virtual disk.

[0031] In Operation 340, the memory controller 110 moves a first internal pointer of the destination from the virtual disk to the flash copy disk. In some embodiments, the first internal pointer is moved based on the instruction for an internal COW. The first internal pointer can be moved in a similar or identical manner to that described with respect to Operation 250.

[0032] In operation 350, the memory controller 110 creates a second internal pointer for the data record in the virtual disk. In some embodiments, the second internal pointer is created such that it points from the data record in the virtual disk to a location in a logical block address mapping (LBA mapping) of a physical disk for the storage disk.

[0033] In Operation 360, the memory controller 110 triggers a bitmap update for the LBA mapping of the physical disk at the LSA. In some embodiments, the bitmap update is triggered based on moving the first internal pointer and creating the second internal pointer.

[0034] Embodiments of the present disclosure can be implemented together with almost any type of computer, regardless of whether the platform is suitable for storing and / or executing a particular program code. Fig. Figure 4 shows as an example a computer system 400 (e.g. a cloud computing system) that is suitable for executing program code in respect of the methods disclosed herein and for managing I / O operations in LSA environments.

[0035] Computer System 400 is only one example of a suitable computer system and is not intended to suggest any limitation regarding the scope or functionality of embodiments of the present disclosure described herein, regardless of whether Computer System 400 can be implemented with and / or perform any of the functionalities set forth above. Computer System 400 includes components that can be used with numerous other general-purpose or specialized data processing system environments or configurations.Examples of known data processing systems, environments, and / or configurations suitable for use with the Computer System / Server 400 include, without limitation, personal computer systems, server computer systems, thin clients, thick clients, handheld or laptop units, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network computers, minicomputer systems, mainframe computer systems, and distributed cloud computing environments comprising any of the above systems or units, and the like. The Computer System / Server 400 can be described in the general context of instructions executable by the Computer System, such as program modules executed by the Computer System 400. In general, the program modules may be routines, programs, objects, components, logic, data structures, and so on.This includes programs that perform specific tasks or implement specific abstract data types. The Computer System / Server 400 can operate in distributed cloud computing environments where tasks are performed by remote processing units connected via a data transmission network. In a distributed cloud computing environment, program modules can reside on both local and remotely located computer system storage media, such as storage units.

[0036] As shown in the figure, the Computer System / Server 400 is depicted as a general-purpose data processing unit. The components of the Computer System / Server 400 may include, but are not limited to, one or more Processors 402 (e.g., processing units), System Memory 404 (e.g., a computer-readable storage medium connected to the one or more Processors), and a Bus 406, which connects various System Components, such as System Memory 404, to Processor 402. The Bus 406 represents one or more of several types of bus structures, such as a Memory Bus or Memory Controller, a Peripheral Bus, an Accelerated Graphics Port, and a Processor or Local Bus, using a variety of bus architectures.Examples of such architectures include, but are not limited to, an ISA bus (Industry Standard Architecture), an MCA bus (Micro Channel Architecture), an EISA bus (Enhanced ISA), a local VESA bus (Video Electronics Standards Association), and a PCI bus (Peripheral Component Interconnects). The Computer System / Server 400 typically includes a variety of media readable by a computer system. Such media can be any available media that the Computer System / Server 400 can access, and they include both volatile and non-volatile media, as well as removable and non-removable media.

[0037] The system memory 404 may include volatile memory media readable by the computer system, such as random access memory (RAM) 408 and / or cache memory 410. The computer system / server 400 may also include other removable / non-removable, volatile / non-volatile storage media of the computer system. By way of example only, a storage system 412 may be provided for reading and writing a non-removable, non-volatile magnetic medium (not shown and commonly referred to as a "hard disk"). Although not shown, a magnetic disk drive may be provided for reading and writing a removable, non-volatile magnetic disk (for example, a "floppy disk"), and an optical disk drive may be provided for reading or writing a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM, or other optical medium.In such cases, these can each be connected to bus 406 via one or more media data interfaces. As further shown and described below, the system memory 404 can contain at least one program product with a set (e.g., at least one) of program modules configured to execute the functions of embodiments of the present disclosure.

[0038] The program / service with a set (at least one) of program modules 416, as well as an operating system, one or more application programs, other program modules, and program data, can be stored in system memory 404, by way of example and without limitation. The program modules can include one or more of the memory controller 110, the flash copy manager 120, and the array component 130, which are located in Fig. Figure 1 shows that the operating system, one or more application programs, other program modules, and program data, and / or a combination thereof, may comprise an implementation of a network environment. The program modules 416 generally perform the functions and / or methods of embodiments of the present disclosure as described herein.

[0039] The computer system / server 400 can also exchange data with one or more external units 418, such as a keyboard, pointing device, display 420, etc.; one or more units that allow a user to interact with the computer system / server 400; and / or one or more units (e.g., a network card, modem, etc.) that allow the computer system / server 400 to exchange data with one or more other computing units. Such data transmission can occur via input / output (I / O) interfaces 414. Furthermore, the computer system / server 400 can exchange data with one or more networks, such as a local area network (LAN), a wide area network (WAN), and / or a public network (e.g., the Internet), via a network adapter 422. As shown, the network adapter 422 can exchange data with the other components of the computer system / server 400 via the bus 406.It is understood that other hardware and / or software components, although not shown, could be used in conjunction with the Computer System / Server 400. Examples include, but are not limited to: microcode, device drivers, redundant processing units, external hard disk arrays, RAID systems, tape drives, and data archiving storage systems, etc.

[0040] It should be clarified from the outset that the implementation of the teachings presented herein is not limited to a cloud computing environment, although this disclosure includes a detailed description of cloud computing. Instead, embodiments of the present invention can be implemented together with any type of data processing environment, now known or subsequently invented.

[0041] Cloud computing is a service delivery model that enables seamless, on-demand network access to a shared pool of configurable computing resources (e.g., networks, network bandwidth, servers, processing power, main memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management overhead or interaction with a service provider. This cloud model can include at least five characteristics, at least three service models, and at least four implementation models.

[0042] Service models can include Software as a Service (SaaS), Platform as a Service (PaaS), and Infrastructure as a Service (IaaS). With SaaS, the functionality provided to the user is to use the provider's applications running in a cloud infrastructure. The applications are accessible from various client devices via a thin-client interface, such as a web browser (e.g., web-based email). The user does not manage or control the underlying cloud infrastructure, including the network, servers, operating systems, storage, or even individual application functions, with the possible exception of limited user-specific application configuration settings. With PaaS, the functionality provided to the user is to use user-created or...to deploy acquired applications in the cloud infrastructure, built using programming languages ​​and tools supported by the provider. The user does not manage or control the underlying cloud infrastructure, including networks, servers, operating systems, or storage, but has control over the deployed applications and potentially over configurations of the application hosting environment. With LaaS (LaaS), the function provided to the user is to provide processing, storage, networking, and other basic data processing resources, enabling the user to deploy and run any software, which may include operating systems and applications. The user does not manage or control the underlying cloud infrastructure, including networks, servers, operating systems, or storage, but has control over the deployed applications and potentially over configurations of the application hosting environment.It does not control the underlying cloud infrastructure, but has control over operating systems, storage, deployed applications and possibly limited control over selected network components (e.g. host firewalls).

[0043] Deployment models can include private cloud, community cloud, public cloud, and hybrid cloud. In a private cloud, the cloud infrastructure is operated solely for one organization. It can be managed by the organization or a third party and can be located on-premises or externally. In a community cloud, the cloud infrastructure is shared by multiple organizations and supports a specific user community with shared concerns (e.g., mission, security requirements, policies, and regulatory compliance considerations). It can be managed by the organizations or a third party, who can be located on-premises or externally. In a public cloud, cloud infrastructure is made available to the general public or a large industry group and is owned by an organization that sells cloud services.In a hybrid cloud, the cloud infrastructure is a composition of two or more clouds (private, community or public) that remain separate entities but are connected by a standardized or proprietary technology that enables data and application portability (e.g. cloud audience distribution for load balancing between clouds).

[0044] A cloud computing environment is service-oriented, focusing on statelessness, low coupling, modularity, and semantic interoperability. At the heart of cloud computing lies an infrastructure that comprises a network of interconnected nodes.

[0045] With reference to Fig. Figure 5 shows an exemplary cloud computing environment 50. As shown, the cloud computing environment 50 has one or more cloud computing nodes 10 with which local data processing units used by cloud users, such as the electronic assistant (PDA, personal digital assistant) or mobile phone 54A, the desktop computer 54B, the laptop computer 54C, and / or the automotive computer system 54N, can exchange data. The nodes 10 can exchange data with each other. They can be grouped physically or virtually into one or more networks, such as private, community, public, or hybrid clouds (not shown), as described above, or into a combination thereof. This enables the cloud computing environment 50 to offer infrastructure, platforms, and / or software as a service, for which a cloud user does not need to maintain resources on a local data processing unit.It should be noted that the types of in . Fig. The data processing units 54A to N shown are merely examples and the data processing nodes 10 and the cloud computing environment 50 can exchange data with any type of computer unit via any type of network and / or any type of network-accessible connection (e.g. using a web browser).

[0046] With reference to Fig. Figure 6 shows a set of functional abstraction layers that are used by the cloud computing environment 50 ( Fig. 5) be provided. It should be clear from the outset that the in Fig. The components, layers, and functions shown in the 6 are intended to be merely exemplary, and embodiments of the disclosure are not limited to them. As shown, the following layers and corresponding functions are provided:

[0047] A hardware and software layer 60 comprises hardware and software components. Examples of hardware components include: mainframe computers 61; servers based on the RISC (Reduced Instruction Set Computer) architecture 62; servers 63; blade servers 64; storage units 65; and networks and network components 66. In some embodiments, software components include network application server software 67 and database software 68.

[0048] A virtualization layer 70 provides an abstraction layer from which the following examples of virtual entities can be provided: virtual servers 71, virtual storage 72, virtual networks 73, including virtual private networks, virtual applications and operating systems 74; and virtual clients 75.

[0049] In one example, the administration layer 80 can provide the functions described below. Resource provisioning 81 provides the dynamic procurement of data processing resources and other resources used to perform tasks within the cloud computing environment. Metering and pricing 82 provides cost tracking for the use of resources within the cloud computing environment and billing for the consumption of these resources. In one example, these resources could include application software licenses. Security provides identity verification for cloud users and tasks, as well as protection for data and other resources. A user portal 83 provides users and system administrators with access to the cloud computing environment.Service scope management (84) provides the allocation and management of cloud computing resources so that the required service objectives are met. Service level agreement (SLA) planning and fulfillment (85) provides the advance planning and procurement of cloud computing resources for which a future requirement is anticipated, in accordance with an SLA.

[0050] A workload layer 90 provides examples of the functionality for which the cloud computing environment can be used. Examples of workloads and functions that can be provided by this layer include: mapping and navigation 91; software development and lifecycle management 92; delivery of training in virtual classrooms 93; data analytics processing 94; transaction processing 95; and storage management processing 96.

[0051] Cloud models can include features such as on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service. With on-demand self-service, a cloud user can unilaterally and automatically procure compute functions such as server time and network storage as needed, without requiring human interaction with the service provider. Broad network access makes functions available over a network through standard mechanisms that support use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs). Resource pooling combines the provider's compute resources to serve multiple users using a multi-tenant model, dynamically allocating and reassigning various physical and virtual resources as needed.There is a perceived location independence, as the user generally has no control over or knowledge of the exact location of the provided resources, but may be able to specify a location at a higher level of abstraction (e.g., country, state, or data center). With rapid elasticity, capabilities for rapid horizontal scaling (scale out) can be provisioned quickly and elastically, in some cases automatically, and released quickly for rapid scaling in. To the user, the capabilities available for provisioning often appear unlimited and can be purchased in any quantity at any time. With measured service, cloud systems automatically control and optimize resource usage by using a measurement function at a certain level of abstraction appropriate for the type of service (e.g., storage, processing, bandwidth, and active user accounts).Resource usage can be monitored, controlled, and reported, thereby creating transparency for both the provider and the user of the service.

[0052] The description of the various embodiments of the present disclosure is given for illustrative purposes only and is not to be considered exhaustive or limited to the disclosed embodiments. Many modifications and variants are obvious to those skilled in the art without deviating from the scope and spirit of the described embodiments. The terminology used herein has been chosen to best describe the principles of the embodiments, their practical application, or their technical improvement over technologies available on the market, or to enable other skilled persons to understand the embodiments disclosed herein.

[0053] The present invention can be implemented as a system, a method, and / or a computer program product. The computer program product can comprise a computer-readable storage medium (or media) containing computer-readable program instructions to induce a processor to execute aspects of the present invention.

[0054] A computer-readable storage medium can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system for propagation. Examples of computer-readable media include semiconductor or solid-state memory, magnetic tape, removable floppy disks, random access memory (RAM), read-only memory (ROM), rigid magnetic disks, and optical disks. Modern examples of optical disks include CD-ROM (Compact Disk Read Only Memory), CD-RW (Compact Disk Read / Write), DVD, and Blu-ray Disc.

[0055] A computer-readable storage medium can be a physical unit capable of retaining and storing instructions for use by a system to execute instructions. For example, a computer-readable storage medium can be an electronic storage unit, a magnetic storage unit, an optical storage unit, an electromagnetic storage unit, a semiconductor storage unit, or any suitable combination thereof, without limitation. A non-exhaustive list of more specific examples of computer-readable storage media includes the following: a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), and erasable programmable read-only memory (EPROM).Flash memory), static random-access memory (SRAM), portable compact storage disk-read-only memory (CD-ROM), DVD (digital versatile disc), USB flash drive, floppy disk, a mechanically coded unit such as punched cards or raised structures in a groove on which instructions are stored, and any suitable combination thereof. A computer-readable storage medium shall not, in its use herein, be understood as volatile signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., light pulses traveling through an optical fiber cable), or electrical signals transmitted by a wire.

[0056] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to individual data processing units or, via a network such as the internet, a local area network, a wide area network, and / or a wireless network, to an external computer or external storage device. The network may include copper transmission cables, fiber optic transmission lines, wireless transmission, routing computers, firewalls, switching units, gateway computers, and / or edge servers. A network adapter card or network interface in each data processing unit receives computer-readable program instructions from the network and forwards them for storage on a computer-readable storage medium within the respective data processing unit.

[0057] Computer-readable program instructions for executing the steps of the present invention can be assembly instructions, ISA (Instruction Set Architecture) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, etc., as well as conventional procedural programming languages ​​such as C or similar languages. The computer-readable program instructions can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server.In the latter case, the remotely located computer can be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be established with an external computer (for example, via the internet using an internet service provider). In some embodiments, electronic circuits, including, for example, programmable logic circuits, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), can execute the computer-readable program instructions by using state information from the computer-readable program instructions to personalize the electronic circuits to perform aspects of the present invention.

[0058] Aspects of the present invention are described herein with reference to flowcharts and / or block diagrams or charts of methods, devices (systems), and computer program products according to embodiments of the invention. It is pointed out that each block of the flowcharts and / or block diagrams or charts, as well as combinations of blocks in the flowcharts and / or block diagrams or charts, can be executed by means of computer-readable program instructions.

[0059] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or another programmable data processing device to create a machine, such that the instructions executed by the processor of the computer or other programmable data processing device generate means for implementing the functions / steps specified in the block(s) of the flowcharts and / or block diagrams or charts.These computer-readable program instructions may also be stored on a computer-readable storage medium capable of controlling a computer, programmable data processing device, and / or other units to function in a particular manner, such that the computer-readable storage medium on which instructions are stored has a manufactured product, including instructions that implement aspects of the function / step specified in the block(s) of the flowchart and / or block diagrams or charts.

[0060] The computer-readable program instructions can also be loaded onto a computer, other programmable data processing devices, or other unit to cause the execution of a series of process steps on the computer or other programmable device or other unit in order to generate a process executed on a computer, such that the instructions executed on the computer, other programmable devices, or other unit implement the functions / steps specified in the block(s) of the flowcharts and / or block diagrams or charts.

[0061] The flowcharts and / or block diagrams or charts in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this context, each block in the flowcharts or block diagrams or charts can represent a module, segment, or part of instructions that includes one or more executable instructions for performing the specific logical function(s). In some alternative embodiments, the functions specified in the block may occur in a different order than shown in the figures. For example, two blocks shown consecutively may in reality be executed essentially simultaneously, or the blocks may sometimes be executed in reverse order depending on the corresponding functionality.It should also be noted that each block of the block diagrams or charts and / or flowcharts, as well as combinations of blocks in the block diagrams or charts and / or flowcharts, can be implemented by special hardware-based systems that perform the specified functions or steps, or execute combinations of special hardware and computer instructions.

[0062] The terminology used herein serves only to describe certain embodiments and is not intended to limit the present disclosure. As used herein, the singular forms "a" and "the" are intended to include the plural forms unless the context clearly indicates otherwise. It is further understood that the terms "indicates" and / or "indicating," when used in this description, indicate the presence of specified features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of further features, integers, steps, operations, elements, components, and / or groups thereof.

Claims

[1] A computer-implemented method (200), comprising: receiving (210) a write request for a storage volume by a storage controller, the write request comprising a data set; determining (230) that the data set for a target area of the storage volume has not been copied to a target location based on a target mapping for a flash copy volume; instructing (240) a log-structured array (LSA) to perform an internal copy-on-write (COW) for the data set during a next input / output (I / O) operation for the storage volume; Moving (250), based on the internal COW instruction, a first internal pointer of the destination location from a virtual volume to the flash copy volume; and Creating a second internal pointer for the record from the virtual disk to a bitmap for the storage disk. [2] The method of claim 1, further comprising: in response to moving the internal pointer, updating (260) a bitmap for the LSA. [3] The method (200) of claim 1, further comprising: Determine a COW status on the storage volume affected by the write request. [4] The method (200) of claim 1, further comprising: Detecting (310) the virtual disk for the storage disk; and Detect (320) the flash copy disk for the storage disk. [5] The method (200) of claim 4, further comprising: Overwriting (330) the data set to the virtual disk, wherein the data set replaces a set of previous values in the virtual disk. [6] The method (200) of claim 5, further comprising: Creating (350) a second internal pointer for the data set in the virtual volume to a location in a logical block address (LBA) map of a physical volume for the storage volume. [7] The method (200) of claim 6, further comprising: Triggering (360) my bitmap update for the LBA mapping of the physical volume at the LSA based on moving (340) the first internal pointer and creating the second internal pointer. [8] System (400), comprising: one or more processors (402); and a computer-readable storage medium connected to the one or more processors (402) and containing program instructions that, when executed by the one or more processors (402), cause the one or more processors (402) to perform the method (200) of any one of claims 1 to 7. [9] A computer program product comprising a computer-readable storage medium having program instructions embodied therein, the program instructions being executable by one or more processors (402) to cause the one or more processors to perform the method (200) of any one of claims 1 to 7.

Citation Information

Patent Citations

  • Copy-redirect on write

    US20170083250A1