Abstract: Methods and systems for Vserver migration are provided. One method includes maintaining a state of a migrate operation for migrating a plurality of source storage volumes managed by a source storage virtual machine (Vserver) of a source cluster to a plurality of destination storage volumes of a destination cluster of a networked storage environment; restarting a process at a healthy node of the source cluster or the destination cluster to continue the migrate operation, in response to detecting an unhealthy node at the source cluster or the destination cluster executing the process; retrying a task associated with the migrate operation experiencing intermittent failure for a certain number of times, and upon successful execution, continuing the migration operation; and checking the state of the migrate operation and in response to the state of the migrate operation, continuing the migrate operation or restarting the migration operation.

Abstract: Methods and systems for processing input/output (“I/O”) requests are disclosed. One method includes identifying, a the target, a granular size to split a write request into a plurality of write requests, based on utilization of a processor of the target configured to process input/output (I/O) requests, the granular size indicating a number of the plurality of write requests; generating, by the target, a plurality of read requests to a storage server, each read request corresponding one of the plurality of write requests; issuing, by the target, the plurality of write requests to a storage device controller, in response to receiving data for the plurality of read requests from the storage server; and transmitting, by the target, a completion notification indicating completion of the write request to the storage server, in response to the storage device controller writing data for each of the plurality of write requests.

Abstract: Methods and systems for Vserver migration are provided. One method includes executing a transfer phase of a migrate operation for migrating a Vserver of a source cluster to a destination cluster, using asynchronous baseline transfer to transfer a plurality of source storage volumes configured in a consistency group (CG) for the migrate operation to a plurality of destination storage volumes of a destination cluster; updating a state of each of the plurality of source storage volumes to a sync state indicating completion of a pre-commit phase of the migrate operation to initiate a commit phase of the migrate operation; and generating a snapshot of the plurality of destination storage volumes for performing data integrity checks between data stored at the source cluster and migrated data at destination cluster, after completing a commit phase of the migrate operation.

Abstract: Methods and systems for Vserver migration are provided. Update after claims are finalized. One method includes generating a consistency group (CG) having a plurality of source storage volumes of a source storage virtual machine (Vserver) of a source cluster for a migrate operation to migrate the source storage volumes as a group to a plurality of destination storage volumes of a destination cluster; establishing a mirroring relationship between the source and destination cluster for managing asynchronous transfer of the source storage volumes in the CG to the destination storage volumes during a transfer phase of the migrate operation; replicating a logical interface of the source cluster to the destination cluster, the logical interface providing a network address to access the source cluster; and automatically selecting a destination port at the destination cluster, associated with the replicated logical interface.

Abstract: Methods, non-transitory machine readable media, and computing devices that manage storage operations directed to dual-port solid state disks (SSDs) coupled to multiple hosts are disclosed. With this technology, context metadata comprising a checksum is retrieved based on a first physical address mapped, in a cached zoned namespace (ZNS) mapping table, to a logical address. The logical address is extracted from a request to read a portion of a file. A determination is made when the checksum is valid based on a comparison to identification information extracted from the request and associated with the file portion. At least the first physical address is replaced in the cached ZNS mapping table with a second physical address retrieved from an on-disk ZNS mapping table, when the determination indicates the checksum is invalid. The file portion retrieved from a dual-port SSD using the second physical address is returned to service the request.

Abstract: Methods and systems for restoring a tenant database of a multitenant database system with multiple tenant databases is provided. In response to a request to restore a first tenant database, a system verifies that the first tenant database is present in the multitenant system database system with a same identifier when a backup of the first tenant database was taken during a backup operation and when the restore request was received. A restore method is selected based on a storage type used for storing the first tenant database. The selected restore method is executed for restoring the first tenant database utilizing an internal file associated with the first tenant database, while processing requests for other tenant databases.

Abstract: Systems, methods, and machine-readable media are disclosed for collecting, maintaining, and retrieving use and limit data for connected resources, as well as determining an optimal location for creating a new volume (or volumes) on a storage platform and placing the volume at the determined location. A resource tracker collects resource use and/or limits data and stores it in a database. A volume placement service receives a volume deployment specification having constraints for creating a new volume. The volume placement service retrieves the data from the database. The volume placement service identifies an optimal location for the volume based at least in part on given constraints from the specification and the resource usage data. The system places the requested volume at the determined location.

Abstract: Systems and methods for scaling application and/or storage system functions of a distributed storage system based on a heterogeneous resource pool are provided. According to one embodiment, the distributed storage system has a composable, service-based architecture that provides scalability, resiliency, and load balancing. The distributed storage system includes a cluster of nodes each potentially having differing capabilities in terms of processing, memory, and/or storage. The distributed storage system takes advantage of different types of nodes by selectively instating appropriate services (e.g., file and volume services and/or block and storage management services) on the nodes based on their respective capabilities. Furthermore, disaggregation of these services, facilitated by interposing a frictionless layer (e.g.

Abstract: Systems and methods are described for a non-disruptive planned failover from a primary copy of data at a primary storage system to a mirror copy of the data at a cross-site secondary storage system. According to an example, a planned failover feature of a multi-site distributed storage system provides an order of operations such that a primary copy of a first data center continues to serve I/O operations until a mirror copy of a second data center is ready. This planned failover feature improves functionality and efficiency of the distributed storage system by providing non-disruptiveness during planned failover - even if various failures occur. The planned failover feature also includes a persistent fence to avoid serving I/O operations during a timing window when both primary data storage and secondary data storage are attempting to have a master role to serve I/O operations and this avoids a split-brain situation.

Abstract: Techniques are provided for persistent memory file system reconciliation. As part of the persistent memory file system reconciliation, high level file system metadata associated with a persistent memory file system of persistent memory is reconciled. Client access to the persistent memory file system is inaccessible until reconciliation of the high level file system metadata has completed. A first scanner is executed to traverse pages of the persistent memory in order to fix local inconsistencies associated with the pages. A local inconsistency of a first set of metadata or data of a page is fixed using a second set of metadata or data of the page. The first scanner is executed asynchronously in parallel with processing client I/O directed to the persistent memory file system.

Abstract: Methods, non-transitory computer readable media, computing devices and systems for persistent indexing and space management for flat directory include creating, using at least one of said at least one processors, an index file to store mapping information, computing, using at least one of said at least one processor, a hash based on a lookup filename, searching, using at least one of said at least one processor, the index file to find all matching directory cookies based on the computed hash, selecting, using at least one of said at least one processor, the directory entity associated with the lookup filename from among the matched directory cookies, and returning, using at least one of said at least one processor, the determined directory entity.

Abstract: Techniques are provided for managing objects within an object store. An object is maintained within an object store. The object is used to store data of a snapshot of a file system hosted by a remote computing device. A determination is made that the snapshot was deleted by the remote computing device. Bitmaps describing objects within the object store that are related to snapshots of the file system are evaluated to determine that the object is unique to the deleted snapshot. The object is freed from storage within the object store.

Abstract: Systems and methods are provided for bringing a volume of a consistency group (CG) into an in-synchronization (InSync) state while other volumes of the CG remain in the InSync state. According to an example, in order to support recovery from disruptive events in a manner that ensures a zero recovery point objective (RPO) guarantee and insulates an application making use of the CG from adverse impacts, responsive to a triggering event, a Fast Resync process may first be attempted to promptly bring an affected volume back into an in-synchronization (InSync) state from an out of synchronization (OOS) state while allowing other members of the CG to remain in the InSync state. Should the Fast resync process be unsuccessful in bringing the volume back into the InSync state within a predetermined or configurable time threshold, then a second type of resynchronization process may be employed at the CG level.

Abstract: Systems and methods for quality of service management are provided. According to one embodiment, a non-transitory computer-readable medium comprises instructions that when executed by the processing resource cause the processing resource to receive, in a normalizing agent, one or more compute load parameters from one or more background compute processes executing on the one or more computer systems and one or more Quality of Service (QoS) parameters for one or more client compute processes executing on the one or more computer systems, convert the one or more compute load parameters to one or more normalized utilization metrics, and execute instructions that cause a processor to adjust a compute resource allocation dedicated to the one or more background compute processes based at least in part on the one or more normalized utilization metrics and the one or more QoS parameters.

Abstract: Techniques are provided for implementing data requests associated with objects of an object store. A data connector component may be instantiated as a container for processing data requests associated with backup data stored within objects of an object store. The data connector component may evaluate the object store to identify snapshots stored as the backup data within the objects of the object store according to an object format. The data connector component may provide a client device with access to backup data of the snapshots.

Abstract: Presented herein are methods, non-transitory computer readable media, and devices triggering a metadata recovery process within a network storage system, which include: dividing metadata into metadata segments, wherein each of the metadata segments is tasked to perform a specific file system operation function, validating each of the metadata segments during the specific file system operation function; upon failure to validate at least one of the metadata segments, triggering an automatic repair process while maintaining the operation function tasked to the metadata segment, and upon finalizing the automatic repair process, resuming the specific file system operation function tasked to the metadata segment.

Abstract: Methods and systems for a networked storage system are provided. One method includes predicting an IOPS limit for a plurality of storage pools based on a maximum allowed latency of each storage pool, the maximum allowed latency determined from a relationship between the retrieved latency and a total number of IOPS from a resource data structure; identifying a storage pool whose utilization has reached a threshold value, the utilization based on a total number of IOPS directed towards the storage pool and a predicted IOPS limit; detecting a bully workload based on a numerical value determined from a total number of IOPS issued by the bully workload for the storage pool and a rising step function; and implementing a corrective action to reduce an impact of the bully workload on a victim workload.

Abstract: Methods and systems for a storage environment are provided. One method includes copying a data unit from a first temporary storage location corresponding to each zoned solid-state drive (ZNS SSD) of a first ZNS SSD set of a storage system to a first XOR module, while determining a first partial horizontal parity using the data unit stored in the first temporary storage location; and determining a vertical parity for each ZNS SSD of the first ZNS SSD set using the data unit provided to the first XOR module in a current cycle and vertical parity determined from a previous cycle.

Abstract: Techniques are provided for asynchronous semi-inline deduplication. A multi-tiered storage arrangement comprises a first storage tier, a second storage tier, etc. An in-memory change log of data recently written to the first storage tier is evaluate to identify a fingerprint of a data block recently written to the first storage tier. A donor data store, comprising fingerprints of data blocks already stored within the first storage tier, is queried using the fingerprint. If the fingerprint is found, then deduplication is performed for the data block to create deduplicated data based upon a potential donor data block within the first storage tier. The deduplicated data is moved from the first storage tier to the second storage tier, such as in response to a determination that the deduplicated data has not been recently accessed. The deduplication is performed before cold data is moved from first storage tier to second storage tier.

Abstract: Techniques are provided for object store mirroring. Data within a storage tier of a node may be determined as being data to tier out to a primary object store based upon a property of the data. A first object is generated to comprise the data. A second object is generated to comprise the data. The first object is transmitted to the primary data store for storage in parallel with the second object being transmitted to a mirror object store for storage. Tiering of the data is designated as successful once acknowledgements are received from both the primary object that the first object was stored and the mirror object store that the second object was stored.