Patent Application
20210240911
This application relates to optimizing page size associated with a snapshot tree in a distributed storage system.
Various types of content addressable storage systems are known. Some content addressable storage systems allow data pages of one or more logical storage volumes to be accessed using content-based signatures that are computed from content of respective ones of the data pages. Some content addressable storage systems are arranged in a distributed storage system without a shared central memory.
Described below is a technique for use in for optimizing page size associated with a snapshot tree associated with a storage array, which technique may be used to provide, collecting current page size information associated with the snapshot tree, determining an optimal page size for the snapshot tree, and creating a new snapshot tree based on the snapshot tree, the new snapshot tree comprising the optimal page size.
As described herein, in at least one embodiment of the current technique, a snapshot tree generator collects current page size information, for example, from an application executing on a storage array, and determines an optimal page size for a snapshot tree associated with the executing application. The snapshot tree generator creates a new snapshot tree based on the (existing) snapshot tree, where the new snapshot tree has the optimal page size. The snapshot tree generator copies the snapshot tree to the new snapshot tree. The snapshot tree generator then modifies a pointer to point from the snapshot tree to the new snapshot tree and deletes the snapshot tree.
Conventional technologies may have a determined page size that is used for addressing, metadata, deduplication, etc., and may maintain that determined page size regardless of the page size of the input/output (I/O) generated by an application. Conventional technologies do not provide the capacity to change the page size online and/or optimize the page size according to the workload. Thus, conventional technologies waste resources. For example, if the determined page size is 4 k and the typical I/O size for the workload is 32 k, for each operation, the system must update 8 pieces of metadata, transmit 8 I/Os to the disk, and maintain the 8 pieces of metadata either in RAM or residing on the disk (resulting in 8 times the number of pointers that are needed). If, instead, the page size could be changed to 32 k (for example, after the typical I/O size for that workload has been determined to be 32 k), the system would only have to update 1 piece of metadata. Conversely, if the determined page size for an application is 32 k and the typical I/O for that application is 4 k, then the 4 k of I/O is written to the 32 k page. In a system that uses addressing when creating a hash of the page, the hash has now effectively changed, and must be updated. This requires a read-modify-write operation that uses additional resources because 4 k was written to the storage array, yet a 32 k read and a 32 k write is required, thus amplifying the I/O by a factor of 16.
Therefore, it would be beneficial to determine an optimal page size. The optimal page size avoids the wastefulness of pages too small or pages too large. In addition, there may be multiple applications sharing a storage array. The optimal page size may be different for each of the applications. Conventional technologies do not provide a solution for optimizing page size associated with a snapshot tree for each of the multiple applications sharing a storage array. Therefore, it would be beneficial to optimize page size for each application associated with a snapshot tree.
By contrast, in at least some implementations in accordance with the current technique as described herein, a snapshot tree generator collects current page size information associated with the snapshot tree. The snapshot tree generator determines an optimal page size for the snapshot tree, and creates a new snapshot tree based on the snapshot tree, where the new snapshot tree comprises the optimal page size.
Thus, a goal of the current technique is to provide a method and a system for optimizing page size associated with a snapshot tree. Another goal is to reduce the resources wasted when the current page size is too big or too small for the workload on the storage system. Another goal is to determine the optimized page size for one or more of the applications sharing the storage array. Yet another goal is to change the page size online, for example, to the optimized page size for each application sharing the storage array.
In at least some implementations in accordance with the current technique described herein, optimizing page size associated with a snapshot tree can provide one or more of the following advantages: changing the determined page size according to application(s) operating on the storage system, optimizing the page size for each snapshot tree, changing a previously optimized page size to a newly optimized page size based on a changing workload, and optimizing use of resources and avoiding unnecessary waste of resources.
In contrast to conventional technologies, in at least some implementations in accordance with the current technique as described herein, a snapshot tree generator collects current page size information associated with the snapshot tree. The snapshot tree generator determines an optimal page size for the snapshot tree, and creates a new snapshot tree based on the snapshot tree, where the new snapshot tree comprises the optimal page size.
In an example embodiment of the current technique, the snapshot tree generator modifies a pointer to point from the snapshot tree to the new snapshot tree and deletes the snapshot tree.
In an example embodiment of the current technique, the snapshot tree generator monitors Input/Output (I/O) size of data during execution of at least one application.
In an example embodiment of the current technique, the snapshot tree generator determines an optimal page size for an application executing on a volume comprising the snapshot tree, where the storage array comprises the volume.
In an example embodiment of the current technique, the snapshot tree generator determines a respective optimal page size for each snapshot tree of a plurality of snapshot trees associated with the storage array.
In an example embodiment of the current technique, the snapshot tree generator creates the new snapshot tree with the optimal page size, where the new snapshot tree comprises a snapshot tree structure associated with the snapshot tree. The snapshot tree generator copies the snapshot tree to the new snapshot tree.
In an example embodiment of the current technique, the snapshot tree generator traverses the snapshot tree and copies each node from the snapshot tree to the new snapshot tree.
In an example embodiment of the current technique, the snapshot tree generator splits a page of the current page size into a plurality of pages of the optimal page size, and writes the plurality of pages to the new snapshot tree.
In an example embodiment of the current technique, the snapshot tree generator merges a plurality of pages into a page of the optimal page size and writes the page of the optimal page size to the new snapshot tree.
In an example embodiment of the current technique, the snapshot tree generator merges a plurality of consecutive pages into the page of the optimal page size.
In an example embodiment of the current technique, for each hash handle in each node of the snapshot tree, the snapshot tree generator reads a page associated with the hash handle and writes the data associated with the page associated with the hash handle to a node in the new snapshot tree, where the data is written according to the optimal page size.
In an example embodiment of the current technique, the snapshot tree generator calculates a new hash handle for each page written to the new snapshot tree.
In an example embodiment of the current technique, the snapshot tree generator determines a changeset in the snapshot tree and updates the new snapshot tree with the changeset to synchronize the new snapshot tree with the snapshot tree.
In an example embodiment of the current technique, the snapshot tree generator creates a new snapshot of the snapshot tree that includes the changeset and copies the new snapshot to the new snapshot tree.
In an example embodiment of the current technique, the new snapshot is created when the changeset does not meet a threshold.
In an example embodiment of the current technique, the snapshot tree generator scans entries associated with the data in the snapshot tree and updates the new snapshot tree with the data in the snapshot tree.
In an example embodiment of the current technique, the entries associated with data in the snapshot tree are scanned when the changeset exceeds a threshold.
In an example embodiment of the current technique, the snapshot tree generator detects an update to data associated with an entry that has been scanned and updates both the snapshot tree and the new snapshot tree with the updated data.
In an example embodiment of the current technique, the snapshot tree generator detects an update to data associated with an entry that has not been scanned and updates the new snapshot tree with the updated data when the entry is scanned.
Illustrative embodiments will be described herein with reference to exemplary information processing systems and associated computers, servers, storage devices and other processing devices. It is to be appreciated, however, that these and other embodiments are not restricted to the particular illustrative system and device configurations shown. Accordingly, the term “information processing system” as used herein is intended to be broadly construed, so as to encompass, for example, processing systems comprising cloud computing and storage systems, as well as other types of processing systems comprising various combinations of physical and virtual processing resources. An information processing system may therefore comprise, for example, at least one data center or other cloud-based system that includes one or more clouds hosting multiple tenants that share cloud resources. Numerous different types of enterprise computing and storage systems are also encompassed by the term “information processing system” as that term is broadly used herein.
Each of the storage systems 102 is illustratively associated with a corresponding set of one or more of the host devices 101. The host devices 101 illustratively comprise servers or other types of computers of an enterprise computer system, cloud-based computer system or other arrangement of multiple compute nodes associated with respective users.
The host devices 101 in some embodiments illustratively provide compute services such as execution of one or more applications on behalf of each of one or more users associated with respective ones of the host devices. Such applications illustratively generate input-output (IO) operations that are processed by a corresponding one of the storage systems 102. The term “input-output” as used herein refers to at least one of input and output. For example, IO operations may comprise write requests and/or read requests directed to stored data of a given one of the storage systems 102.
The storage systems 102 illustratively comprise respective processing devices of one or more processing platforms. For example, the storage systems 102 can each comprise one or more processing devices each having a processor and a memory, possibly implementing virtual machines and/or containers, although numerous other configurations are possible.
The storage systems 102 can additionally or alternatively be part of cloud infrastructure such as an Amazon Web Services (AWS) system. Other examples of cloud-based systems that can be used to provide at least portions of the storage systems 102 include Google Cloud Platform (GCP) and Microsoft Azure.
The storage systems 102 may be implemented on a common processing platform, or on separate processing platforms.
The host devices 101 are illustratively configured to write data to and read data from the storage systems 102 in accordance with applications executing on those host devices for system users.
The term “user” herein is intended to be broadly construed so as to encompass numerous arrangements of human, hardware, software or firmware entities, as well as combinations of such entities. Compute and/or storage services may be provided for users under a Platform-as-a-Service (PaaS) model, an Infrastructure-as-a-Service (IaaS) model and/or a Function-as-a-Service (FaaS) model, although it is to be appreciated that numerous other cloud infrastructure arrangements could be used. Also, illustrative embodiments can be implemented outside of the cloud infrastructure context, as in the case of a stand-alone computing and storage system implemented within a given enterprise.
The network 104 is assumed to comprise a portion of a global computer network such as the Internet, although other types of networks can be part of the network 104, including a wide area network (WAN), a local area network (LAN), a satellite network, a telephone or cable network, a cellular network, a wireless network such as a WiFi or WiMAX network, or various portions or combinations of these and other types of networks. The network 104 in some embodiments therefore comprises combinations of multiple different types of networks each comprising processing devices configured to communicate using Internet Protocol (IP) or other communication protocols.
As a more particular example, some embodiments may utilize one or more high-speed local networks in which associated processing devices communicate with one another utilizing Peripheral Component Interconnect express (PCIe) cards of those devices, and networking protocols such as InfiniBand, Gigabit Ethernet or Fibre Channel. Numerous alternative networking arrangements are possible in a given embodiment, as will be appreciated by those skilled in the art.
The source storage system 102S comprises a plurality of storage devices 106S and an associated storage controller 108S. The storage devices 106S store storage volumes 110S. The storage volumes 110S illustratively comprise respective logical units (LUNs) or other types of logical storage volumes.
Similarly, the target storage system 102T comprises a plurality of storage devices 106T and an associated storage controller 108T. The storage devices 106T store storage volumes 110T, at least a portion of which represent respective LUNs or other types of logical storage volumes that are replicated from the source storage system 102S to the target storage system 102T in accordance with an asynchronous replication process.
The storage devices 106 of the storage systems 102 illustratively comprise solid state drives (SSDs). Such SSDs are implemented using non-volatile memory (NVM) devices such as flash memory. Other types of NVM devices that can be used to implement at least a portion of the storage devices 106 include non-volatile random access memory (NVRAM), phase-change RAM (PC-RAM) and magnetic RAM (MRAM). These and various combinations of multiple different types of NVM devices may also be used. For example, hard disk drives (HDDs) can be used in combination with or in place of SSDs or other types of NVM devices.
However, it is to be appreciated that other types of storage devices can be used in other embodiments. For example, a given storage system as the term is broadly used herein can include a combination of different types of storage devices, as in the case of a multi-tier storage system comprising a flash-based fast tier and a disk-based capacity tier. In such an embodiment, each of the fast tier and the capacity tier of the multi-tier storage system comprises a plurality of storage devices with different types of storage devices being used in different ones of the storage tiers. For example, the fast tier may comprise flash drives or other types of SSDs while the capacity tier comprises HDDs. The particular storage devices used in a given storage tier may be varied in other embodiments, and multiple distinct storage device types may be used within a single storage tier. The term “storage device” as used herein is intended to be broadly construed, so as to encompass, for example, SSDs, HDDs, flash drives, hybrid drives or other types of storage devices.
In some embodiments, at least one of the storage systems 102 illustratively comprises a scale-out all-flash content addressable storage array such as an XtremIO™ storage array from Dell EMC of Hopkinton, Mass. Other types of storage arrays, including by way of example VNX® and Symmetrix VMAX® storage arrays also from Dell EMC, can be used to implement storage systems 102 in other embodiments.
The term “storage system” as used herein is therefore intended to be broadly construed, and should not be viewed as being limited to content addressable storage systems or flash-based storage systems. A given storage system as the term is broadly used herein can comprise, for example, network-attached storage (NAS), storage area networks (SANs), direct-attached storage (DAS) and distributed DAS, as well as combinations of these and other storage types, including software-defined storage.
Other particular types of storage products that can be used in implementing storage systems 102 in illustrative embodiments include all-flash and hybrid flash storage arrays such as Unity™, software-defined storage products such as ScaleIO™ and ViPR®, cloud storage products such as Elastic Cloud Storage (ECS), object-based storage products such as Atmos®, and scale-out NAS clusters comprising Isilon® platform nodes and associated accelerators, all from Dell EMC. Combinations of multiple ones of these and other storage products can also be used in implementing a given storage system in an illustrative embodiment.
In some embodiments, communications between the host devices 101 and the storage systems 102 comprise Small Computer System Interface (SCSI) commands. Other types of SCSI or non-SCSI commands may be used in other embodiments, including commands that are part of a standard command set, or custom commands such as a “vendor unique command” or VU command that is not part of a standard command set. The term “command” as used herein is therefore intended to be broadly construed, so as to encompass, for example, a composite command that comprises a combination of multiple individual commands. Numerous other commands can be used in other embodiments.
The storage controller 108S of source storage system 102S in the
Similarly, the storage controller 108T of target storage system 102T includes replication control logic 112T and a snapshot tree generator 114T.
Although not explicitly shown in the figure, additional components can be included in the storage controllers 108, such as signature generators utilized in generating content-based signatures of data pages.
The instances of replication control logic 112S and 112T are collectively referred to herein as replication control logic 112. Such replication control logic instances are also referred to herein as individually or collectively comprising at least a portion of a “replication engine” of the system 100.
The replication control logic 112 of the storage systems 102 controls performance of the asynchronous replication process carried out between those storage systems, which as noted above in some embodiments further involves at least one of the host devices 101. The data replicated from the source storage system 102S to the target storage system 102T can include all of the data stored in the source storage system 102S, or only certain designated subsets of the data stored in the source storage system 102S, such as particular designated sets of LUNs or other logical storage volumes. Different replication processes of different types can be implemented for different parts of the stored data. Also, the storage systems 102 can be configured to operate in different replication modes of different types at different times. For example, the storage systems 102 can transition from an asynchronous replication mode to a synchronous replication mode and vice versa.
A given storage volume designated for replication from the source storage system 102S to the target storage system 102T illustratively comprises a set of one or more LUNs or other instances of the storage volumes 110S of the source storage system 102S. Each such LUN or other storage volume illustratively comprises at least a portion of a physical storage space of one or more of the storage devices 106S. The corresponding replicated LUN or other storage volume of the storage volumes 110T of the target storage system 102T illustratively comprises at least a portion of a physical storage space of one or more of the storage devices 106T.
The replication control logic 112 of the storage systems 102 in some embodiments is configured to control the performance of corresponding portions of an asynchronous replication process. At least one of the host devices 101 in some embodiments can also include one or more instances of replication control logic and possibly also one or more snapshot tree generators 114, as well as additional or alternative components such as a signature generator.
The storage controllers 108 of the storage systems 102 should also be understood to include additional modules and other components typically found in conventional implementations of storage controllers and storage systems, although such additional modules and other components are omitted from the figure for clarity and simplicity of illustration.
It will be assumed for the following description of the
The asynchronous replication process more particularly comprises a cycle-based asynchronous replication process in which a consistency group comprising one or more storage volumes is replicated from the source storage system 102S to the target storage system 102T over a plurality of asynchronous replication cycles. Such an arrangement is illustratively configured to guarantee data consistency between the storage volumes of the consistency group on the source and their corresponding replicated versions on the target. The asynchronous replication is performed periodically over the multiple cycles. The asynchronous replication is illustratively implemented at least in part by or otherwise under the control of the source and target instances of replication control logic 112S and 112T. Other types of replication arrangements can be used in other embodiments.
The source storage system 102S generates a current snapshot set for a consistency group comprising a plurality of storage volumes subject to replication from the source storage system 102S to the target storage system 102T.
It is assumed for the present embodiment that the given replication cycle is a non-initial replication cycle of an ongoing asynchronous replication process, such that there is a previous snapshot set already available from a previous cycle. In an initial replication cycle, the entire content of the current snapshot set is illustratively transferred to from the source to the target. The current snapshot set for the initial replication cycle becomes the previous snapshot set for the next replication cycle.
The current snapshot set and other snapshot sets referred to the context of some embodiments herein are illustratively generated for a consistency group that comprises multiple storage volumes. A snapshot tree of the consistency group in such embodiments illustratively comprises multiple individual snapshot trees for respective ones of the storage volumes, each generally having the same topology of nodes. Accordingly, generation of a snapshot set for a consistency group illustratively comprises generating a plurality of snapshots for respective ones of the multiple storage volumes. Such snapshot sets and associated versions of the consistency group vary over time and are represented by nodes of the snapshot tree of the consistency group. Again, the snapshot tree for the consistency group may be viewed as illustratively comprising multiple superimposed snapshot trees for the respective storage volumes of the consistency group with each such storage volume snapshot tree having substantially the same topology as the consistency group snapshot tree.
A given one of the snapshot trees corresponding to a particular one of the storage volumes more particularly comprises a root node, at least one branch node, and a plurality of leaf nodes, with a given one of the branch nodes representing a particular version of the storage volume from which a corresponding snapshot is taken. A first one of the leaf nodes which is a child of the given branch node represents a subsequent version of the storage volume, and a second one of the leaf nodes which is a child of the given branch node comprises the corresponding snapshot providing a point-in-time (PIT) copy of the particular version of the storage volume.
In some embodiments, the snapshot trees comprise or are otherwise associated with additional information also arranged in the form of a tree structure. For example, a given one of the snapshot trees may be associated with one or more additional trees including at least one of a “dirty” tree that characterizes updates to logical addresses of the corresponding storage volume, and a hash tree comprising content-based signatures of respective ones of the logical addresses of the corresponding storage volume. All nodes of a given snapshot tree in some embodiments, including both branch nodes and leaf nodes, may each be associated with corresponding metadata of both a dirty tree and a hash tree.
A wide variety of other types of snapshot trees and possibly one or more associated additional trees can be used in other embodiments. Also, the term “tree” as used herein is intended to be broadly construed so as to comprise any type of data structure characterizing a plurality of nodes and a plurality of edges interconnecting respective pairs of the nodes.
The content-based signatures of the above-noted hash tree associated with a given storage volume in some embodiments comprise hash digests of their respective pages, each generated by application of a hash function such as the well-known Secure Hashing Algorithm 1 (SHA1) to the content of its corresponding page. Other types of secure hashing algorithms, such as SHA2 or SHA256, or more generally other hash functions, can be used in generating content-based signatures herein.
A given hash digest in illustrative embodiments is unique to the particular content of the page from which it is generated, such that two pages with exactly the same content will have the same hash digest, while two pages with different content will have different hash digests. It is also possible that other types of content-based signatures may be used, such as hash handles of the type described elsewhere herein. A hash handle generally provides a shortened representation of its corresponding hash digest. More particularly, the hash handles are shorter in length than respective hash digests that are generated by applying a secure hashing algorithm to respective ones of the data pages. Hash handles are considered examples of “content-based signatures” as that term is broadly used herein.
In embodiments in which the storage systems 102 comprise content addressable storage systems, address metadata is illustratively utilized to provide content addressable storage functionality within those systems. The address metadata in some embodiments comprises at least a portion of one or more logical layer mapping tables that map logical addresses of respective ones of the data pages of the storage volume to corresponding content-based signatures of the respective data pages. Examples of logical layer mapping tables and other metadata structures maintained by at least the storage controller 108T of target storage system 102T will be described elsewhere herein.
As mentioned previously, the term “storage volume” as used herein is intended to be broadly construed, and should not be viewed as being limited to any particular format or configuration. The term “consistency group” as used herein is also intended to be broadly construed, and may comprise one or more storage volumes.
The storage systems 102 in the
The storage systems 102 may be implemented on respective distinct processing platforms, although numerous other arrangements are possible. At least portions of their associated host devices may be implemented on the same processing platforms as the storage systems 102 or on separate processing platforms.
The term “processing platform” as used herein is intended to be broadly construed so as to encompass, by way of illustration and without limitation, multiple sets of processing devices and associated storage systems that are configured to communicate over one or more networks.
For example, distributed implementations of the system 100 are possible, in which certain components of the system reside in one data center in a first geographic location while other components of the system reside in one or more other data centers in one or more other geographic locations that are potentially remote from the first geographic location. Thus, it is possible in some implementations of the system 100 for the storage systems 102 to reside in different data centers. Numerous other distributed implementations of the storage systems 102 and their respective associated sets of host devices are possible.
Additional examples of processing platforms utilized to implement storage systems and possibly their associated host devices in illustrative embodiments will be described in more detail below in conjunction with
It is to be appreciated that these and other features of illustrative embodiments are presented by way of example only, and should not be construed as limiting in any way.
Accordingly, different numbers, types and arrangements of system components such as host devices 101, storage systems 102, network 104, storage devices 106, storage controllers 108 and storage volumes 110 can be used in other embodiments.
It should be understood that the particular sets of modules and other components implemented in the system 100 as illustrated in
For example, in other embodiments, at least portions of the functionality for optimizing page size associated with a snapshot tree can be implemented in one or more host devices, or partially in a host device and partially in a storage system. Illustrative embodiments are not limited to arrangements in which all such functionality is implemented in source and target storage systems or a host device, and therefore encompass various hybrid arrangements in which the functionality is distributed over one or more storage systems and one or more associated host devices, each comprising one or more processing devices. References herein to “one or more processing devices” configured to implement particular operations or other functionality should be understood to encompass a wide variety of different arrangements involving one or more processing devices of at least one storage system and/or at least one host device.
As another example, it is possible in some embodiments that the source storage system and the target storage system can comprise different portions of the same storage system. In such an arrangement, a replication process is illustratively implemented to replicate data from one portion of the storage system to another portion of the storage system. The terms “source storage system” and “target storage system” as used herein are therefore intended to be broadly construed so as to encompass such possibilities.
The operation of the information processing system 100 will now be described in further detail with reference to the flow diagram of the illustrative embodiment of
At 200, the snapshot tree generator 114 collects current page size information associated with the snapshot tree. In an example embodiment, the snapshot tree generator 114 monitors Input/Output (I/O) size of data during execution of at least one application. In an example embodiment, as the application executes, the snapshot tree generator 114 collects statistics on, for example, typical pages sizes and typical write sizes. The snapshot tree generator 114 may then use the statistics to determine the optimized page size and then convert the volume's metadata to be the optimized page size. In an example embodiment, the snapshot tree may represent data from a collection of related volumes where the snapshot tree contains snapshots from the related volumes. In this example embodiment, it is important to create a new snapshot tree for the snapshot tree because the collection of related volumes may contain the same type of data (for example, data from a particular database application, thus the optimal page size will be the same), and because it would be impractical to have different page sizes for different nodes of the snapshot tree.
At 202, the snapshot tree generator 114 determines an optimal page size for the snapshot tree. In an example embodiment, the snapshot tree generator 114 determines an optimal page size for an application executing on a volume comprising the snapshot tree, where the storage array comprises the volume. In an example embodiment, the volume may have been initially set to have a page size of 8 k. In an example embodiment, the snapshot tree generator 114 monitors the execution of an application, and determines that, for example, the optimal page size of the application is 32 k. In another example embodiment, the snapshot tree generator 114 determines a respective optimal page size for each snapshot tree of a plurality of snapshot trees associated with the storage array.
At 204, the snapshot tree generator 114 creates a new snapshot tree based on the snapshot tree, the new snapshot tree comprising the optimal page size. In an example embodiment, the snapshot tree generator 114 traverses the snapshot tree breadth first traversal to create the new snapshot tree based on the snapshot tree. In an example embodiment, if the current page size is larger than the optimal page size, the snapshot tree generator 114 splits the pages into multiple pages of the optimal page size. In an example embodiment, during the splitting, the snapshot tree generator 114 checks the parent node (i.e., the original snapshot) for the hash handle of one or more of the split pages. If the hash handles of any of the split pages match the hash handles of pages in the patent node, then the snapshot tree generator discards the duplicated hash handles, and maintains the changed hash handles. For example, the snapshot tree generator 114 may discard the hash handles of the split pages that are duplicated at the parent node. If the current page size is smaller than the optimal page size, the snapshot tree generator 114 merges several pages into one page of the optimal page size. In other words, the snapshot tree generator 114 creates the new snapshot tree with the optimal page size, where the new snapshot tree comprises a snapshot tree structure associated with the snapshot tree. The snapshot tree generator 114 then copies the snapshot tree to the new snapshot tree. In an example embodiment, the snapshot tree generator 114 traverses the snapshot tree and copies each node from the snapshot tree to the new snapshot tree. In an example embodiment, for each hash handle in each node of the snapshot tree, the snapshot tree generator 114 reads a page associated with the hash handle and writes data associated with the page associated with the hash handle to a node in the new snapshot tree, where the data is written according to the optimal page size. The snapshot tree generator 114 then calculates a new hash handle for each page written to the new snapshot tree. In an example embodiment, the hash may also include the page size, for example, to prevent collisions between hash handles.
In an example embodiment, the snapshot tree generator 114 splits a page of the current page size into a plurality of pages of the optimal page size and writes the plurality of pages to the new snapshot tree. In an example embodiment, if an inactive volume has a 32 k page size, and the snapshot tree generator 114 determines the optimized page size is 8 k, the snapshot tree generator 114 splits the 32 k pages into multiple pages of 8 k each. For example, the snapshot tree generator 114 traverses the volume current snapshot, reads a 32 k page, and constructs 4 pages of 8 k. The snapshot tree generator 114 calculates the hash for each of the 4 pages, and writes the 4 pages (of 8 k each) to a new volume (created by the snapshot tree generator 114). The snapshot tree generator 114 performs these steps until the current volume snapshot has been traversed. The snapshot tree generator 114 deletes the old volume, and points to the new volume.
In another example embodiment, the snapshot tree generator 114 merges a plurality of pages into a page of the optimal page size and writes the page of the optimal page size to the new snapshot tree. In another example embodiment, the snapshot tree generator 114 merges a plurality of consecutive pages into the page of the optimal page size. For example, if an inactive volume (or the internal nodes of the snapshot tree) has/have an 8 k page size, and the snapshot tree generator 114 determines the optimized page size is 32 k, the snapshot tree generator 114 merges 4 of the 8 k pages into a 32 k page. For example, the snapshot tree generator 114 traverses the volume current snapshot. In this example embodiment, the snapshot tree generator 114 reads 8 consecutive pages, and constructs a 32 k page. The snapshot tree generator 114 calculates the hash for the 32 k page, and writes that page to a new volume (created by the snapshot tree generator 114) as a 32 k page. In another example embodiment, the snapshot tree generator 114 determines that 32 k is the optimal page size. The snapshot tree generator 114 reads a 4 k page, and then reads the parent snapshot tree for 28 k of data (i.e., the remainder of the 32 k) to be merged into the 32 k page. Thus, the snapshot tree generator efficiently reads the remaining 28 k data at the parent node once, versus reading the 7 remaining 4 k pages. The snapshot tree generator 114 performs these steps until the current volume snapshot has been traversed. The snapshot tree generator 114 deletes the old volume, and points to the new volume.
In an example embodiment, with an active volume, the data that has been copied to the snapshot tree at the leaf level may change (for example, the data on the volume may change) while the snapshot tree generator 114 is traversing the remainder of the snapshot tree (i.e., splitting or merging pages into optimized pages in the new snapshot tree) resulting in a new snapshot tree that has a different data set than the snapshot tree. In this example scenario, the snapshot tree generator 114 determines a changeset in the snapshot tree as illustrated in
In an example embodiment, with an active volume, the data that has been copied to the new snapshot tree may change (for example, the data on the volume may change) while the snapshot tree generator 114 is traversing the remainder of the snapshot tree (i.e., splitting or merging pages into optimized pages in the new snapshot tree). In this example embodiment, the changeset may meet or exceed a threshold. For example, the changeset may be considered a large changeset. In an example embodiment, the changeset may be large enough that the iterative process described above might not be efficient, in that the iterative process might not result in a changeset small enough such that this process would be effective, meaning that multiple iterations of creating and copying the new snapshot might not reduce the changeset to a small size. In other words, the changeset is too large to “catch up” the changes between the snapshot tree and the new snapshot tree using the iterative “creating and copying the new snapshot” process. In this example embodiment at 210, the snapshot tree generator 114 uses a scanning process to update new snapshot tree with the changes that have occurred in the volume during the time the new snapshot tree was being created and populated. In an example embodiment, the snapshot tree generator 114 scans entries associated with data in the snapshot tree and updates the new snapshot tree with the data in the snapshot tree. In this example embodiment, the entries associated with data in the snapshot tree are scanned when the changeset exceeds a threshold, for example, when the changeset is a large changeset. In an example embodiment, the snapshot tree generator 114 detects an update to data associated with an entry that has been scanned and updates the snapshot tree and the new snapshot tree with the updated data. In another example embodiment, the snapshot tree generator 114 detects an update to data associated with an entry that has not been scanned and updates the new snapshot tree with the updated data when the entry is scanned. In an example embodiment, the snapshot tree generator 114 uses a pivot to identify a scanning location during the scanning process. As the snapshot tree generator 114 updates the new snapshot tree with changes that have occurred in the snapshot tree (for example, I/Os coming into the snapshot tree), if the changes to the snapshot tree occur at locations that the pivot has already scanned, the snapshot tree generator 114 updates both the snapshot tree and the new snapshot tree with those changes. If the changes to the snapshot tree occur at locations that the pivot has yet to scan, then the snapshot tree generator 114 waits to update the new snapshot tree until the pivot reaches that location. Thus, the snapshot tree and the new snapshot tree are synchronized by the time the scanning process has completed.
In other words, if the changeset is small, the snapshot tree generator 114 uses a synchronous replication process, and if the changeset is large, the snapshot tree generator 114 uses an asynchronous replication process.
Once the data has been copied from the snapshot tree to the new snapshot tree, the snapshot tree generator 114 modifies a pointer to point from the snapshot tree to the new snapshot tree and deletes the snapshot tree.
A given storage volume snapshot tree having a format of the type shown in
References herein to first and second nodes in illustrative embodiments refer to respective branch nodes of a snapshot tree. A given such branch node generally has at least one corresponding leaf node. It is also possible that at least one of the first and second nodes can alternatively comprise a leaf node.
Terms such as “root node” and “non-root node,” “start node” and “stop node,” and “first node” and “second node” as used herein are all intended to be broadly construed. A non-root node is considered to be any snapshot tree node that is not a root node. Start node and stop node designations for a given snapshot tree in some embodiments can be reversed relative to the designation arrangements referred to above in conjunction with the examples of
The particular processing operations and other system functionality described in conjunction with the flow diagram of
Functionality such as that described in conjunction with the flow diagram of
For example, storage controllers such as storage controllers 108 of storage systems 102 that are configured to control performance of one or more steps of the
In some implementations of the
An address-to-hash (“A2H”) utilized in some embodiments comprises a plurality of entries accessible utilizing logical addresses as respective keys, with each such entry of the A2H table comprising a corresponding one of the logical addresses, a corresponding hash handle, and possibly one or more additional fields.
A hash-to-data (“H2D”) table utilized in some embodiments comprises a plurality of entries accessible utilizing hash handles as respective keys, with each such entry of the H2D table comprising a corresponding one of the hash handles, a physical offset of a corresponding one of the data pages, and possibly one or more additional fields.
A hash metadata (“HMD”) table utilized in some embodiments comprises a plurality of entries accessible utilizing hash handles as respective keys. Each such entry of the HMD table comprises a corresponding one of the hash handles, a corresponding reference count and a corresponding physical offset of one of the data pages. A given one of the reference counts denotes the number of logical pages in the storage system that have the same content as the corresponding data page and therefore point to that same data page via their common hash digest. The HMD table may also include one or more additional fields.
A physical layer based (“PLB”) table utilized in some embodiments illustratively comprises a plurality of entries accessible utilizing physical offsets as respective keys, with each such entry of the PLB table comprising a corresponding one of the physical offsets, a corresponding one of the hash digests, and possibly one or more additional fields.
As indicated above, the hash handles are generally shorter in length than the corresponding hash digests of the respective data pages, and each illustratively provides a short representation of the corresponding full hash digest. For example, in some embodiments, the full hash digests are 20 bytes in length, and their respective corresponding hash handles are illustratively only 4 or 6 bytes in length.
Also, it is to be appreciated that terms such as “table” and “entry” as used herein are intended to be broadly construed, and the particular example table and entry arrangements described above can be varied in other embodiments. For example, additional or alternative arrangements of entries can be used.
In some embodiments, the storage system comprises an XtremIO™ storage array or other type of content addressable storage system suitably modified to incorporate functionality for optimizing page size associated with a snapshot tree as disclosed herein.
An illustrative embodiment of such a content addressable storage system will now be described with reference to
Although it is assumed that both the source storage system 102S and the target storage system 102T are content addressable storage systems in some embodiments, other types of storage systems can be used for one or both of the source storage system 102S and the target storage system 102T in other embodiments. For example, it is possible that at least one of the storage systems 102 in an illustrative embodiment need not be a content addressable storage system and need not include an ability to generate content-based signatures. In such an embodiment, at least portions of the functionality, associated′ with optimizing page size associated with a snapshot tree, of the one or more storage systems can be implemented in a host device.
The storage controller 408 in the present embodiment is configured to implement functionality for optimizing page size associated with a snapshot tree of the type previously described in conjunction with
The storage controller 408 includes distributed modules 412 and 414, which are configured to operate in a manner similar to that described above for respective corresponding replication control logic 112 and snapshot tree generators 114 of the storage controllers 108 of system 100. Module 412 is more particularly referred to as distributed replication control logic, and illustratively comprises multiple replication control logic instances on respective ones of a plurality of distinct nodes. Module 414 is more particularly referred to as a distributed snapshot tree generator 114, and illustratively comprises multiple snapshot tree generation instances on respective ones of the distinct nodes.
The content addressable storage system 405 in the
The storage controller 408 of the content addressable storage system 405 is implemented in a distributed manner so as to comprise a plurality of distributed storage controller components implemented on respective ones of the storage nodes 415. The storage controller 408 is therefore an example of what is more generally referred to herein as a “distributed storage controller.” In subsequent description herein, the storage controller 408 is referred to as distributed storage controller 408.
Each of the storage nodes 415 in this embodiment further comprises a set of processing modules configured to communicate over one or more networks with corresponding sets of processing modules on other ones of the storage nodes 415. The sets of processing modules of the storage nodes 415 collectively comprise at least a portion of the distributed storage controller 408 of the content addressable storage system 405.
The modules of the distributed storage controller 408 in the present embodiment more particularly comprise different sets of processing modules implemented on each of the storage nodes 415. The set of processing modules of each of the storage nodes 415 comprises at least a control module 408C, a data module 408D and a routing module 408R. The distributed storage controller 408 further comprises one or more management (“MGMT”) modules 408M. For example, only a single one of the storage nodes 415 may include a management module 408M.
It is also possible that management modules 408M may be implemented on each of at least a subset of the storage nodes 415. A given set of processing modules implemented on a particular one of the storage nodes 415 therefore illustratively includes at least one control module 408C, at least one data module 408D and at least one routing module 408R, and possibly a management module 408M.
Communication links may be established between the various processing modules of the distributed storage controller 408 using well-known communication protocols such as IP, Transmission Control Protocol (TCP), and remote direct memory access (RDMA). For example, respective sets of IP links used in data transfer and corresponding messaging could be associated with respective different ones of the routing modules 408R.
Although shown as separate modules of the distributed storage controller 408, the modules 412 and 414 in the present embodiment are assumed to be distributed at least in part over at least a subset of the other modules 408C, 408D, 408R and 408M of the storage controller 408. Accordingly, at least portions of the optimizing page size associated with a snapshot tree functionality of the modules 412 and 414 may be implemented in one or more of the other modules of the storage controller 408. In other embodiments, the modules 412 and 414 may be implemented as stand-alone modules of the storage controller 408.
The storage devices 406 are configured to store metadata pages 420 and user data pages 422, and may also store additional information not explicitly shown such as checkpoints and write journals. The metadata pages 420 and the user data pages 422 are illustratively stored in respective designated metadata and user data areas of the storage devices 406. Accordingly, metadata pages 420 and user data pages 422 may be viewed as corresponding to respective designated metadata and user data areas of the storage devices 406.
A given “page” as the term is broadly used herein should not be viewed as being limited to any particular range of fixed sizes. In some embodiments, a page size of 8 kilobytes (KB) is used, but this is by way of example only and can be varied in other embodiments. For example, page sizes of 4 KB, 16 KB or other values can be used. Accordingly, illustrative embodiments can utilize any of a wide variety of alternative paging arrangements for organizing the metadata pages 420 and the user data pages 422.
The user data pages 422 are part of a plurality of LUNs configured to store files, blocks, objects or other arrangements of data, each also generally referred to herein as a “data item,” on behalf of users of the content addressable storage system 405. Each such LUN may comprise particular ones of the above-noted pages of the user data area. The user data stored in the user data pages 422 can include any type of user data that may be utilized in the system 100. The term “user data” herein is therefore also intended to be broadly construed.
A given storage volume for which content-based signatures are generated using modules 412 and 414 illustratively comprises a set of one or more LUNs, each including multiple ones of the user data pages 422 stored in storage devices 406.
The content addressable storage system 405 in the embodiment of
Each of the metadata pages 420 characterizes a plurality of the user data pages 422. For example, a given set of user data pages representing a portion of the user data pages 422 illustratively comprises a plurality of user data pages denoted User Data Page 1, User Data Page 2, . . . User Data Page n. Each of the user data pages in this example is characterized by a LUN identifier, an offset and a content-based signature. The content-based signature is generated as a hash function of content of the corresponding user data page. Illustrative hash functions that may be used to generate the content-based signature include the above-noted SHA1 secure hashing algorithm, or other secure hashing algorithms known to those skilled in the art, including SHA2, SHA256 and many others. The content-based signature is utilized to determine the location of the corresponding user data page within the user data area of the storage devices 406.
Each of the metadata pages 420 in the present embodiment is assumed to have a signature that is not content-based. For example, the metadata page signatures may be generated using hash functions or other signature generation algorithms that do not utilize content of the metadata pages as input to the signature generation algorithm. Also, each of the metadata pages is assumed to characterize a different set of the user data pages.
A given set of metadata pages representing a portion of the metadata pages 420 in an illustrative embodiment comprises metadata pages denoted Metadata Page 1, Metadata Page 2, . . . Metadata Page m, having respective signatures denoted Signature 1, Signature 2, . . . Signature m. Each such metadata page characterizes a different set of n user data pages. For example, the characterizing information in each metadata page can include the LUN identifiers, offsets and content-based signatures for each of the n user data pages that are characterized by that metadata page. It is to be appreciated, however, that the user data and metadata page configurations described above are examples only, and numerous alternative user data and metadata page configurations can be used in other embodiments.
Ownership of a user data logical address space within the content addressable storage system 405 is illustratively distributed among the control modules 408C.
The functionality of optimizing page size associated with a snapshot tree is provided by modules 412 and 414 in this embodiment is assumed to be distributed across multiple distributed processing modules, including at least a subset of the processing modules 408C, 408D, 408R and 408M of the distributed storage controller 408.
For example, the management module 408M of the storage controller 408 may include a replication control logic instance that engages corresponding replication control logic instances in all of the control modules 408C and routing modules 408R in order to implement an asynchronous replication process.
In some embodiments, the content addressable storage system 405 comprises an XtremIO™ storage array suitably modified to incorporate optimizing page size associated with a snapshot tree functionality as disclosed herein.
In arrangements of this type, the control modules 408C, data modules 408D and routing modules 408R of the distributed storage controller 408 illustratively comprise respective C-modules, D-modules and R-modules of the XtremIO™ storage array. The one or more management modules 408M of the distributed storage controller 408 in such arrangements illustratively comprise a system-wide management module (“SYM module”) of the XtremIO™ storage array, although other types and arrangements of system-wide management modules can be used in other embodiments. Accordingly, optimizing page size associated with a snapshot tree functionality in some embodiments is implemented under the control of at least one system-wide management module of the distributed storage controller 408, utilizing the C-modules, D-modules and R-modules of the XtremIO™ storage array.
In the above-described XtremIO™ storage array example, each user data page has a fixed size such as 8 KB and its content-based signature is a 20-byte signature generated using the SHA1 secure hashing algorithm. Also, each page has a LUN identifier and an offset, and so is characterized by <lun_id, offset, signature>.
The content-based signature in the present example comprises a content-based digest of the corresponding data page. Such a content-based digest is more particularly referred to as a “hash digest” of the corresponding data page, as the content-based signature is illustratively generated by applying a hash function such as the SHA1 secure hashing algorithm to the content of that data page. The full hash digest of a given data page is given by the above-noted 20-byte signature. The hash digest may be represented by a corresponding “hash handle,” which in some cases may comprise a particular portion of the hash digest. The hash handle illustratively maps on a one-to-one basis to the corresponding full hash digest within a designated cluster boundary or other specified storage resource boundary of a given storage system. In arrangements of this type, the hash handle provides a lightweight mechanism for uniquely identifying the corresponding full hash digest and its associated data page within the specified storage resource boundary. The hash digest and hash handle are both considered examples of “content-based signatures” as that term is broadly used herein.
As mentioned previously, storage controller components in an XtremIO™ storage array illustratively include C-module, D-module and R-module components. For example, separate instances of such components can be associated with each of a plurality of storage nodes in a clustered storage system implementation.
The distributed storage controller in this example is configured to group consecutive pages into page groups, to arrange the page groups into slices, and to assign the slices to different ones of the C-modules. For example, if there are 1024 slices distributed evenly across the C-modules, and there are a total of 16 C-modules in a given implementation, each of the C-modules “owns” 1024/16=64 slices. In such arrangements, different ones of the slices are assigned to different ones of the control modules 408C such that control of the slices within the storage controller 408 of the storage system 405 is substantially evenly distributed over the control modules 408C of the storage controller 408.
The D-module allows a user to locate a given user data page based on its signature. Each metadata page also has a size of 8 KB and includes multiple instances of the <lun_id, offset, signature> for respective ones of a plurality of the user data pages. Such metadata pages are illustratively generated by the C-module but are accessed using the D-module based on a metadata page signature.
The metadata page signature in this embodiment is a 20-byte signature but is not based on the content of the metadata page. Instead, the metadata page signature is generated based on an 8-byte metadata page identifier that is a function of the LUN identifier and offset information of that metadata page.
If a user wants to read a user data page having a particular LUN identifier and offset, the corresponding metadata page identifier is first determined, then the metadata page signature is computed for the identified metadata page, and then the metadata page is read using the computed signature. In this embodiment, the metadata page signature is more particularly computed using a signature generation algorithm that generates the signature to include a hash of the 8-byte metadata page identifier, one or more ASCII codes for particular predetermined characters, as well as possible additional fields. The last bit of the metadata page signature may always be set to a particular logic value so as to distinguish it from the user data page signature in which the last bit may always be set to the opposite logic value.
The metadata page signature is used to retrieve the metadata page via the D-module. This metadata page will include the <lun_id, offset, signature> for the user data page if the user page exists. The signature of the user data page is then used to retrieve that user data page, also via the D-module.
Write requests processed in the content addressable storage system 405 each illustratively comprise one or more 10 operations directing that at least one data item of the storage system 405 be written to in a particular manner. A given write request is illustratively received in the storage system 405 from a host device over a network. In some embodiments, a write request is received in the distributed storage controller 408 of the storage system 405, and directed from one processing module to another processing module of the distributed storage controller 408. For example, a received write request may be directed from a routing module 408R of the distributed storage controller 408 to a particular control module 408C of the distributed storage controller 408. Other arrangements for receiving and processing write requests from one or more host devices can be used.
The term “write request” as used herein is intended to be broadly construed, so as to encompass one or more IO operations directing that at least one data item of a storage system be written to in a particular manner. A given write request is illustratively received in a storage system from a host device.
In the XtremIO™ context, the C-modules, D-modules and R-modules of the storage nodes 415 communicate with one another over a high-speed internal network such as an InfiniBand network. The C-modules, D-modules and R-modules coordinate with one another to accomplish various IO processing tasks.
The write requests from the host devices identify particular data pages to be written in the storage system 405 by their corresponding logical addresses each comprising a LUN ID and an offset.
As noted above, a given one of the content-based signatures illustratively comprises a hash digest of the corresponding data page, with the hash digest being generated by applying a hash function to the content of that data page. The hash digest may be uniquely represented within a given storage resource boundary by a corresponding hash handle.
The content addressable storage system 405 utilizes a two-level mapping process to map logical block addresses to physical block addresses. The first level of mapping uses an address-to-hash (“A2”) table and the second level of mapping uses a hash metadata (“HMD”) table, with the A21 and HMD tables corresponding to respective logical and physical layers of the content-based signature mapping within the content addressable storage system 405. The HMD table or a given portion thereof in some embodiments disclosed herein is more particularly referred to as a hash-to-data (“H2D”) table.
The first level of mapping using the A2H table associates logical addresses of respective data pages with respective content-based signatures of those data pages. This is also referred to as logical layer mapping.
The second level of mapping using the HMD table associates respective ones of the content-based signatures with respective physical storage locations in one or more of the storage devices 106. This is also referred to as physical layer mapping.
Examples of these and other metadata structures utilized in illustrative embodiments were described above. These particular examples include respective A2H, H2D, HMD and PLB tables. In some embodiments, the A2M and H2D tables are utilized primarily by the control modules 408C, while the HMD and PLB tables are utilized primarily by the data modules 408D.
For a given write request, hash metadata comprising at least a subset of the above-noted tables is updated in conjunction with the processing of that write request.
The A2H, H2D, HMD and PLB tables described above are examples of what are more generally referred to herein as “mapping tables” of respective distinct types. Other types and arrangements of mapping tables or other content-based signature mapping information may be used in other embodiments.
Such mapping tables are still more generally referred to herein as “metadata structures” of the content addressable storage system 405. It should be noted that additional or alternative metadata structures can be used in other embodiments. References herein to particular tables of particular types, such as A2H, H2D, HMD and PLB tables, and their respective configurations, should be considered non-limiting and are presented by way of illustrative example only. Such metadata structures can be implemented in numerous alternative configurations with different arrangements of fields and entries in other embodiments.
The logical block addresses or LBAs of a logical layer of the storage system 405 correspond to respective physical blocks of a physical layer of the storage system 405. The user data pages of the logical layer are organized by LBA and have reference via respective content-based signatures to particular physical blocks of the physical layer.
Each of the physical blocks has an associated reference count that is maintained within the storage system 405. The reference count for a given physical block indicates the number of logical blocks that point to that same physical block.
In releasing logical address space in the storage system, a dereferencing operation is generally executed for each of the LBAs being released. More particularly, the reference count of the corresponding physical block is decremented. A reference count of zero indicates that there are no longer any logical blocks that reference the corresponding physical block, and so that physical block can be released.
It should also be understood that the particular arrangement of storage controller processing modules 408C, 408D, 408R and 408M as shown in the
Alternative arrangements of these and other storage node processing modules of a distributed storage controller in a content addressable storage system can be used in other embodiments.
Illustrative embodiments of a storage system with optimizing page size associated with a snapshot tree functionality as disclosed herein can provide a number of significant advantages relative to conventional arrangements.
In some embodiments, the source and target storage systems are illustratively implemented as respective content addressable storage systems, but in other embodiments one or more of the storage systems can instead be a traditional storage array, which does not support any type of content addressable storage functionality, with any missing functionality being provided by a host device.
Accordingly, functionality for optimizing page size associated with a snapshot tree as disclosed herein can be implemented in a storage system, in a host device, or partially in a storage system and partially in a host device.
It is to be appreciated that the particular advantages described above and elsewhere herein are associated with particular illustrative embodiments and need not be present in other embodiments. Also, the particular types of information processing system features and functionality as illustrated in the drawings and described above are exemplary only, and numerous other arrangements may be used in other embodiments.
Illustrative embodiments of processing platforms utilized to implement host devices and storage systems with optimizing page size associated with a snapshot tree functionality will now be described in greater detail with reference to
The cloud infrastructure 500 comprises multiple virtual machines (VMs) and/or container sets 502-1, 502-2, . . . 502-L implemented using virtualization infrastructure 504. The virtualization infrastructure 504 runs on physical infrastructure 505, and illustratively comprises one or more hypervisors and/or operating system level virtualization infrastructure. The operating system level virtualization infrastructure illustratively comprises kernel control groups of a Linux operating system or other type of operating system.
The cloud infrastructure 500 further comprises sets of applications 510-1, 510-2, . . . 510-L running on respective ones of the VMs/container sets 502-1, 502-2, . . . 502-L under the control of the virtualization infrastructure 504. The VMs/container sets 502 may comprise respective VMs, respective sets of one or more containers, or respective sets of one or more containers running in VMs.
In some implementations of the
An example of a hypervisor platform that may be used to implement a hypervisor within the virtualization infrastructure 504 is the VMware® vSphere® which may have an associated virtual infrastructure management system such as the VMware® vCenter™. The underlying physical machines may comprise one or more distributed processing platforms that include one or more storage systems.
In other implementations of the
As is apparent from the above, one or more of the processing modules or other components of system 100 may each run on a computer, server, storage device or other processing platform element. A given such element may be viewed as an example of what is more generally referred to herein as a “processing device.” The cloud infrastructure 500 shown in
The processing platform 600 in this embodiment comprises a portion of system 100 and includes a plurality of processing devices, denoted 602-1, 602-2, 602-3, . . . 602-K, which communicate with one another over a network 604.
The network 604 may comprise any type of network, including by way of example a global computer network such as the Internet, a WAN, a LAN, a satellite network, a telephone or cable network, a cellular network, a wireless network such as a WiFi or WiMAX network, or various portions or combinations of these and other types of networks.
The processing device 602-1 in the processing platform 600 comprises a processor 610 coupled to a memory 612.
The processor 610 may comprise a microprocessor, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), graphics processing unit (GPU) or other type of processing circuitry, as well as portions or combinations of such circuitry elements.
The memory 612 may comprise random access memory (RAM), read-only memory (ROM), flash memory or other types of memory, in any combination. The memory 612 and other memories disclosed herein should be viewed as illustrative examples of what are more generally referred to as “processor-readable storage media” storing executable program code of one or more software programs.
Articles of manufacture comprising such processor-readable storage media are considered illustrative embodiments. A given such article of manufacture may comprise, for example, a storage array, a storage disk or an integrated circuit containing RAM, ROM, flash memory or other electronic memory, or any of a wide variety of other types of computer program products. The term “article of manufacture” as used herein should be understood to exclude transitory, propagating signals. Numerous other types of computer program products comprising processor-readable storage media can be used.
Also included in the processing device 602-1 is network interface circuitry 614, which is used to interface the processing device with the network 604 and other system components, and may comprise conventional transceivers.
The other processing devices 602 of the processing platform 600 are assumed to be configured in a manner similar to that shown for processing device 602-1 in the figure.
Again, the particular processing platform 600 shown in the figure is presented by way of example only, and system 100 may include additional or alternative processing platforms, as well as numerous distinct processing platforms in any combination, with each such platform comprising one or more computers, servers, storage devices or other processing devices.
For example, other processing platforms used to implement illustrative embodiments can comprise converged infrastructure such as VxRai™, VxRack™, VxRack™ FLEX, VxBlock™, or Vblock® converged infrastructure from VCE, the Virtual Computing Environment Company, now the Converged Platform and Solutions Division of Dell EMC.
It should therefore be understood that in other embodiments different arrangements of additional or alternative elements may be used. At least a subset of these elements may be collectively implemented on a common processing platform, or each such element may be implemented on a separate processing platform.
As indicated previously, components of an information processing system as disclosed herein can be implemented at least in part in the form of one or more software programs stored in memory and executed by a processor of a processing device. For example, at least portions of the optimizing page size associated with a snapshot tree functionality of one or more components of a storage system as disclosed herein are illustratively implemented in the form of software running on one or more processing devices.
It should again be emphasized that the above-described embodiments are presented for purposes of illustration only. Many variations and other alternative embodiments may be used. For example, the disclosed techniques are applicable to a wide variety of other types of information processing systems, host devices, storage systems, storage nodes, storage devices, storage controllers, asynchronous replication processes, snapshot tree generators and associated control logic and metadata structures. Also, the particular configurations of system and device elements and associated processing operations illustratively shown in the drawings can be varied in other embodiments. Moreover, the various assumptions made above in the course of describing the illustrative embodiments should also be viewed as exemplary rather than as requirements or limitations of the disclosure. Numerous other alternative embodiments within the scope of the appended claims will be readily apparent to those skilled in the art.
