Windows VSS

Integration with Microsoft VSS allows the array to manage snapshots and replication for VSS-compliant applications such as Backup Exec. VSS snapshots function the same for both iSCSI and Fibre Channel arrays.

Attention:
  • Check compatibility with array OS.
  • VSS snapshots cannot be taken of iSCSI volumes that have CHAP enabled.
  • VSS Hardware Provider does not work with iSCSI HBAs.
  • VSS Hardware Provider version 4.x does not support arrays running the array OS prior to version 4.1.0.0.
  • VSS Hardware Requestor must be version 4.x or later to support Hyper-V.
  • The toolkit must be version 5.0.0 or later to support HPE Storage VSS for Virtual Volumes (vVols). VSS for vVols support Microsoft Exchange Server and Microsoft SQL Server applications. Exchange-verified snapshots are not supported in Fibre Channel-based vVol environments.
  • The toolkit must be version 6.0.0 or later if you are using Group Scoped Targets (GST).
  • Starting with toolkit 7.0.0, you must provide the Windows host with the array credentials if you want to use the VSS. If you did not do this when you installed toolkit, you can use PowerShell cmdlet Set-Configuration to provide the credentials used by the array.
    NOTE: If you do not provide the array credentials, all application-synchronized snapshot creation operations will fail.
  • The default REST port is 5392.

    There is an option to modify the REST port by setting a DWORD value in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Nimble Storage\Rest Port. The port number on the array must also be updated to match. Contact HPE Support to change the port number on the array.

    The modified REST port and port 4210 must be open for outbound connections.

    If you modify the REST port in the registry, you must restart HPE VSS Hardware Provider to use the modified port.

Table 1. VSS with FC and iSCSI
  HPE VSS snapshots for SQL (VSS sync on volume collection) HPE VSS snapshots for Exchange (VSS sync on volume collection) Using VSS provider through third party backup applications Notes (related to backup)
Physical Environment
iSCSI Full functionality Full functionality Full functionality  
FC Full functionality Full functionality Full functionality Host must have management IP connectivity to send API calls.
Virtual environment

Guest attached iSCSI

(VMware or Hyper-V)		 Full functionality Full functionality Full functionality  

iSCSI pRDM

(VMware)		 Full functionality Full functionality Full functionality
  • No third-party applications for any protocol are supported with VVols.
  • No DSM should be set to claim any HPE Storage device
  • A snapshot of the pRDM is mounted as a guest-attached iSCSI LUN.
  • Set-Configuration must be run in the VM to configure the array group management IP
  • The host should have volume access and the guest should have snapshot access
iSCSI pass-through (Hyper-V) Full functionality Full functionality Full functionality
  • No third-party applications for any protocol are supported with VVols.
  • No DSM should be set to claim any HPE device
  • A snapshot of the pRDM is mounted as a guest attached iSCSI LUN.
  • Set-Configuration must be run in the VM to configure the array group management IP
  • The host should have volume access and the guest should have snapshot access

FC pRDM

(VMware)		 Full functionality
Attention: Exchange snapshots with verification turned on do not function. Log truncation cannot be achieved.

Snapshots with verification turned off (copy backup) will work.

 Snapshots cannot be mounted on the same server
  • No third-party applications for any protocol are supported with VVols.
  • No DSM should be set to claim any HPE device
  • Cannot mount a snapshot of a pRDM as a pRDM.
  • Set-Configuration must be run in the VM to configure the array group management IP.
  • A proxy backup host with FC connectivity can be set up for snapshot mount (off-host backup) with third party backup applications.
FC pass through (Hyper-V) Full functionality Full functionality Full functionality
  • No DSM should be set to claim any HPE device on the guest OS
  • Cannot mount a snapshot of a pass through disk as a pass through disk, snapshot will be mounted through virtual FC HBA
  • Set-Configuration must be run in the VM to configure the HPE group management IP.
  • Host should be given access to parent volume and guest vFC initiator should have snapshot access

vFC

(Hyper-V)		 Full functionality Full functionality Full functionality