Abstract: A virtual volume is initially provided from a first storage appliance within a cluster of storage appliances by providing access to the virtual volume over a data path between a host computer and a protocol endpoint hosted on the first storage appliance, based on an initial binding between the virtual volume and the protocol endpoint hosted on the first storage appliance. A rebind request is conveyed to the host computer, and in response to receiving a bind request for the virtual volume, a new binding is created between the virtual volume and a protocol endpoint hosted by the second storage appliance. The virtual volume is subsequently provided from the second storage appliance by providing the host computer with access to the virtual volume over a data path between the host computer and the protocol endpoint hosted on the second storage appliance based on the newly created binding.

Abstract: A data storage system in a cluster of storage systems provides virtual-volume data storage to virtual-computing (VC) hosts. A storage container is created for use as a logical grouping of virtual volumes (VVols), and \the storage container is paired as a source storage container with a target storage container on a remote target data storage system. The pairing identifies the target storage container to be used for storing a replica of a replication group of VVols to be stored in the source storage container. When a VVol having a requirement for protection by replication is created, it is placed in a replication group of the source storage container. Subsequently, based on the VVol being a member of the replication group of the source storage container, the VVol is replicated to a target replication group of the target storage container of the remote data storage system.

Abstract: A primary copy and one or more shadow copies of a logical volume are created and discovered by a host rescan performed when the logical volume is initially created. Data storage resources are allocated to the primary copy, but not to the shadow copy. The initial path state of the logical volume describes the path to the primary copy as active, and the path to the shadow copy as unavailable for accessing the logical volume. Movement of the logical volume to the storage appliance providing the shadow copy can be performed without an additional host rescan, by making the shadow copy the new primary copy, making the primary copy a new shadow copy, and updating the path state of the logical volume to indicate i) that the path to the new primary copy is active, and ii) that the path to the new shadow copy is unavailable.

Abstract: A virtual volume is initially provided from a first storage appliance within a cluster of storage appliances by providing access to the virtual volume over a data path between a host computer and a protocol endpoint hosted on the first storage appliance, based on an initial binding between the virtual volume and the protocol endpoint hosted on the first storage appliance. A rebind request is conveyed to the host computer, and in response to receiving a bind request for the virtual volume, a new binding is created between the virtual volume and a protocol endpoint hosted by the second storage appliance. The virtual volume is subsequently provided from the second storage appliance by providing the host computer with access to the virtual volume over a data path between the host computer and the protocol endpoint hosted on the second storage appliance based on the newly created binding.

Abstract: Data storage systems of a cluster associate virtual volumes (VVols) with protocol endpoints (PEs) organized into host-specific initiator groups. From the perspective of the hosts, the PEs are specialized SCSI LUNs that aggregate the VVols bound thereto. In operation, a host directs VVol access requests to the host-specific PEs, and a data storage system processes the VVol requests as received via the corresponding PEs.

Abstract: A method, computer program product, and computing system for defining a UIS layer within a storage management application, wherein the UIS layer is configured to perform operations including object management within a storage system. A System API layer is defined within the storage management application, wherein the System API layer is positioned beneath the UIS layer and is configured to perform operations including persistence object management within the storage system.

Abstract: Systems and method are disclosed for provisioning storage for a logical storage device. At least one storage capability profile is provided. A request to provision the storage for the logical storage device is received. A plurality of candidate storage resource configurations are determine based on the at least one storage capability profile and the storage policy profile, where a first candidate storage resource configuration specifies thick provisioning in a first storage pool and a second candidate storage resource configuration specifies thin provisioning in the first storage pool. A ranking of the plurality of candidate storage resource configurations is provided, the ranking indicating the first candidate storage resource configuration has a higher priority than the second candidate storage resource configuration. It is determined that the first storage pool has insufficient storage for thick provisioning.

Abstract: A technique for acquiring information about a data storage system employs compiled software constructs and an uncompiled file external to the compiled software constructs. The uncompiled file stores data inquiry definitions, such as select query and view definitions. The compiled software constructs incorporate the data inquiry definitions from the uncompiled file into database language instructions, which the compiled software constructs send to a database for processing. Results of processing the database language instructions are returned to the compiled software constructs, which return the results to an application program or other client that requested them.