Abstract: In at least one embodiment, a method of fault monitoring data storage devices in a multiple-data-storage-devices enclosure is disclosed. The method includes: receiving a storage access request; identifying a first data storage device as being targeted by the storage access request, wherein the enclosure includes two or more data storage devices including the first data storage device; performing an access operation according to the storage access request on the first data storage device; and updating a record of a fault sensor assigned to the first data storage device by monitoring the performing of the access operation.

Abstract: A network storage server implements a method to limit simultaneous data transfers and efficient throttle management. The number of processes that can be simultaneously performed in the network storage server is limited. For the processes that do not exceed the limiting number, and are therefore allowed to be simultaneously performed, a throttle control is implemented on each of the processes to limit the amount of system resources that can be allocated to each of the processes. The processes are performed on the network storage server, and a total amount of system resources allocated to these processes does not exceed the available system resources of the network storage server.

Abstract: Techniques for virtual machine migration are described. An apparatus may comprise a script generation component operative to generate a first script, the first script to migrate a guest operating system running on a first virtual machine to run on a second virtual machine. The first script may be operative to collect configuration information of the guest operating system, generate a second script based on the collected configuration information, and configure the guest operating system to execute the second script, the configuration information collected while the guest operating system is running on the first virtual machine, the guest operating system configured for the execution of the second script to occur while the guest operating system is running on the second virtual machine. Other embodiments are described and claimed.

Abstract: Techniques for self-repairing configuration service are described. An apparatus may comprise a self-repairing configuration service component to execute a self-repairing configuration service for a guest operating system executing on a virtual machine. The self-repairing configuration service to detect a guest operating system executing on the virtual machine, detect a change to a host hypervisor of the virtual machine, and reconfigure one or more network interfaces and one or more disks of the virtual machine for the guest operating system upon startup of the guest operating system on the virtual machine in response to the change in the host hypervisor of the virtual machine. Other embodiments are described and claimed.

Abstract: Techniques for virtual machine shifting are described. An apparatus may comprise shifting component operative to shift a virtual machine (VM) between a hypervisor having one type of hypervisor platform and a destination hypervisor having an alternative type of hypervisor platform through use of a clone of the VM. The shifting is bi-directional between the host and the destination hypervisor. The apparatus may comprise a universal application programming interface (API) used for reconfiguring one or more network interfaces and one or more disks of the VM onto the destination hypervisor. Other embodiments are described and claimed.

Abstract: Storage system workload data associated with a storage system is analyzed. The workload data comprises indications of input and output operations associated with the storage system. A storage system configuration is determined based, at least in part, on said analyzing of the storage system workload data. An implementation plan comprising one or more operations for implementing the storage system configuration is generated.

Abstract: Many applications and computing environments, such as data storage systems, provide data backup and restoration features. It may be advantageous to provide file level backups that may be accessible to a user through a directory structure of a file system. Accordingly, fileshots comprising backup data of a file may be stored as metadata of the file. For example, a fileshot may be stored within a stream directory as a hidden stream linked off of the file. Fileshots may be associated within a directory interface (e.g., a command prompt or graphical user interface), which may be presented to a user. In this way, the user may access and/or manage fileshots through the directory interface (e.g., the user may create fileshots, restore files with fileshots, copy fileshots, etc.). Additionally, fileshot metadata may be maintained for fileshots. The fileshot metadata may be used to locate fileshot and/or perform fileshot commands.

Abstract: A clustered network-based storage system includes a host server, multiple high availability system controller pairs, and multiple storage devices across multiple arrays. Two independent storage array subsystems each include a quorum drive copy and are each controlled by a HA pair, with remote volume mirroring links coupling the separate HA pairs. The host server includes a virtualization agent that identifies and prioritizes communication paths, and also determines capacity across all system nodes. A system storage management agent determines an overall storage profile across the system. The virtualization agent, storage management agent, quorum drive copies and remote volume mirroring link all operate to provide increased redundancy, load sharing, or both between the separate first and second arrays of storage devices.

Abstract: A system and method for providing a substantially constant-time copy operation for file system objects managed by a storage server begins by generating a snapshot of at least a portion of a data set managed by the storage server. The system then performs a copy operation in the storage server to generate a copy of the data set separate from the snapshot, on a set of block locations containing a predetermined reference value. During the copy operation to generate the copy of the data set separate from the snapshot, the system can receive from a requester a first read request directed to the copy of the data set that the copy operation is to generate. In response to the first data request, the system provides data from the snapshot to the requester by the storage server.

Abstract: Techniques for detecting data loss during site switchover are disclosed. An example method includes storing at NVRAM of a first node a plurality of operations of a second node, the first and second nodes being disaster recovery partners. The method also includes during a switchover from the second node to the first node, receiving an indication of a first number of operations yet to be completed. The method further includes comparing the first number to a second number of operations in the plurality of operations stored at the NVRAM of the first node. The method also includes in response to the comparing, determining whether at least one operation is missing from the plurality of operations stored in the NVRAM of the first node. The method further includes in response to determining that at least one operation is missing, failing at least one volume.

Abstract: A system and method for adaptive data placement in a distributed file system is provided. Upon creation of a new subdirectory, a first heuristic procedure is formed to determine whether the newly created subdirectory should be created locally or on a remote flexible volume. Should it be determination be made to create or store the subdirectory on a remote flexible volume, a second heuristic procedure determines which of a plurality of flexible volumes should store the newly created subdirectory.

Abstract: Techniques for recovering from a failure at a disaster recovery site are disclosed. An example method includes receiving an indication to shift control of a set of volumes of a plurality of volumes. The set of volumes is originally owned by a second storage node. The first storage node is a disaster recovery partner of the second storage node. The method includes shifting control of the set of volumes. The method further includes during the shifting, changing a status of a flag corresponding to a progress of the shifting. The method also includes during a reboot of the first storage node, determining the status of the flag and determining, based on the status of the flag, whether to mount the set of volumes during reboot at the first storage node.

Abstract: Methods, systems, and computer program products for preventing non-detectable data loss during site switchover are disclosed. A computer-implemented method may include receiving a request to perform a switchover from a first node to a second node, determining whether to place a storage volume involved in the switchover in a suspended state, setting the storage volume in the suspended state based on determining that the storage volume is to be placed in the suspended state, and maintaining the storage volume in the suspended state after completing the switchover. In an example, the storage volume may be placed in a suspended state based on examining a volume-specific attribute indicating whether the storage volume is to be suspended when involved in a switchover. In one example, each storage volume involved in a switchover may be placed in a suspended state when indicated as part of a switchover request.

Abstract: One or more techniques and/or systems are provided for mirroring a caching log data structure from a primary storage controller to a secondary storage controller over multiple interconnect paths. The secondary storage controller may be configured as a backup or failover storage controller for the primary storage controller in the event the primary storage controller fails. Data and/or metadata describing the data may be mirrored from the primary storage controller to the secondary storage controller over one or more interconnect paths. The caching log data structure may be parsed into a plurality of streams. The streams may be assigned to interconnect paths between the primary storage controller and the secondary storage controller. A data ordering rule is enforced during mirroring of storage information of the streams across the interconnect paths (e.g., the secondary storage controller is to receive data in the order it was sent by respective streams).

Abstract: One or more techniques and/or systems are provided for interconnect failover between a primary storage controller and a secondary storage controller. The secondary storage controller may be configured as a backup or failover storage controller for the primary storage controller in the event the primary storage controller fails. Data and/or metadata describing the data (e.g., data and/or metadata stored within a write cache) may be mirrored from the primary storage controller to the secondary storage controller over one or more interconnect paths. Responsive to identifying a failover trigger for a failed interconnect path, the secondary storage controller is instructed to fence (e.g., block) I/O operations from the failed interconnect path. Streams of data and/or metadata that were affected by the failure may be instructed to transmit such data and/or metadata over one or more non-failed interconnect paths to the secondary storage controller during failover of the failed interconnect path.

Abstract: The present invention is a system and method which allows for a VTL system that supports thin provisioning to implicitly unmap unused storage. Such unmap operations may occur even though the VTL system does not receive any explicit unmap requests from its initiators. For example, if a system administrator knows that once a virtual tape drive of the VTL system has been partially overwritten, all previously written data sets on that virtual tape drive will never again be accessed, the system administrator may configure the VTL system so that it unmaps the entire remainder of the virtual tape drive on the first data overwrite.

Abstract: A storage server receives a write request from a client system including new data and a location to store the new data. The storage server transmits a copy instruction to a storage subsystem to relocate old data at the location and transmits a write instruction to the storage subsystem to overwrite the old data with the new data. The storage subsystem includes fast stable storage in which the copy instruction and the write instruction are stored. After receiving each instruction, the storage subsystem sends an acknowledgement to the storage server. When both instructions have been acknowledged, the storage server sends an acknowledgement to the client system. The storage subsystem performs the instructions asynchronously from the client system's write request.

Abstract: While current solutions for cloning virtual machines can involve copying and duplicating files associated to a virtual machine (VM), systems and techniques can be devised to create thin clones of a VM using the VM's associated storage system to copy and deduplicate storage for the VMs. One can create a base VM in a directory of a storage container attached to a hypervisor, and then map the storage container to a volume on a storage system. One can clone the base VM using a snapshot of respective files associated to the base VM, which can comprise creating metadata that identified a physical storage location of the files. Further, the metadata can then be copied to a desired location on the storage container, to create a VM clone. Once copied, the cloned VM can be customized and registered within the hypervisor.

Abstract: In one embodiment, a node is a member of a cluster having a plurality of nodes, where each node is coupled to one or more storage arrays of solid state drives (SSDs) that serve as main storage. The node executed a storage input/output (I/O) stack having a redundant array of independent disks (RAID) layer that organizes the SSDs within the one or more storage arrays as one or more RAID groups. Configuration information is stored as a cluster database. The configuration information identifies (i) one or more RAID groups associated with an extent store, (ii) SSDs within each RAID group, and (iii) an identification of a node that owns the extent store. The cluster database is stored separate and apart from the main storage.

Abstract: A network storage server includes a tool for detecting and fixing errors while the network storage server remains online (available for servicing client requests), which includes enabling a user to approve or disapprove remedial changes before the changes are committed. The technique bypasses the usual consistency point process for new or modified data blocks representing potential remedial changes. At a consistency point, dirty data blocks representing the potential remedial changes are written to a change log file residing outside the volume. The modified data blocks are written in sequential order to logical blocks of the change log file. In response to a user input indicating that a potential change should be committed, the corresponding modified data blocks are read from the change log file in the order in which they were written to the change log file, and they are written to persistent storage in that order.