Connect-NimVolume

The Connect-NimVolume cmdlet helps administrators to connect existing volumes on the group. It has options to assign new disk signatures and clear VSS flags while connecting to avoid Windows disk signature conflicts. You can also assign a drive letter or directory as an access path to the volume, and add the volume to a cluster as a cluster resource or a CSV.

The Connect-NimVolume cmdlet supports the following workflows:

  • Connect any volume or clone to local the host or cluster.
  • Connect and assign a drive letter or directory as an access path to the volume. The -AssignDriveLetter option automatically assigns a drive letter. Use the -AccessPath option if you want to specify a drive letter.
  • Connect and add a volume to a cluster as a cluster resource or as a CSV.
  • Avoid signature conflicts when connecting a clone of a volume to the same host where the original volume resides.
  • Clear all VSS attributes from a volume when connecting a clone created from a VSS snapshot.
  • Make the connection persistent when connecting iSCSI clones.
  • In a Fibre Channel cluster, if you want to connect the clone of a clustered disk to the host where cmdlet is run, but not to all nodes in the cluster using the -AddToCSV or -AddToCluster options, specify the initiator group that has only current host's initiator.
NOTE: When using Windows 2008 R2, the -AddToCluster or -AddToCSV options only creates a cluster resource and adds the resource to the cluster in the offline state. You must to manually connect the volume on other nodes and then try to bring the cluster resource online. Use the -Force option to connect from multiple nodes.

Connect a volume using Connect-NimVolume

Connect an existing volume or clone on the array to the Windows host.

Syntax

Connect-NimVolume -NimbleVolumeName <String[]> [-Force [<SwitchParameter>]] [-AssignNewSignature [<SwitchParameter>]] [-ResetVSSFlags [<SwitchParameter>]] [-GroupMgmtIP <IPAddress>] [-InitiatorGroup <String>] [-AssignDriveLetter [<SwitchParameter>]] [-AccessPath <String[]>] [-AddToCluster [<SwitchParameter>]] [-AddToCSV [<SwitchParameter>]] [-IsPersistent [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [-Confirm [<SwitchParameter>]] [<CommonParameters>]

Connect a volume using -NimVolumeName.

Example

PS C:\Users\Administrator> Connect-NimVolume -NimbleVolumeName "Connect-Clone-Test"

Connect a volume, assign a new disk signature, assign a drive letter, and add the volume to the cluster.

Example


PS C:\Users\Administrator> Connect-NimVolume -NimbleVolumeName "Connect-Clone-Test" -AssignNewSignature -AssignDriveLetter -AddToCluster
DeviceName        : \\.\physicaldrive4
SerialNumber      : 8141876f15c845cb6c9ce900075a810f
GroupManagementIP : 10.18.236.56
NimbleVolumeName  : Connect-Clone-Test
DiskSize          : 6811560
BusType           : iScsi
WindowsVolumes    : {J:\}
FCTargetMappings  : {}
Clone             : True
Snapshot          : False
BaseSnapshotName  : SQLVOLCOLTYPE1-hourly-2016-04-24::10:01:13.946
ParentVolumeName  : SQLVOLTYPE1.1

Connect a volume, reset the VSS flags, assign a drive letter, and add the volume to the cluster.

Example


PS C:\Users\Administrator> Connect-NimVolume -NimbleVolumeName "Connect-Clone-Test" -ResetVSSFlags -AssignDriveLetter -AddToCluster
DeviceName        : \\.\physicaldrive4
SerialNumber      : 8141876f15c845cb6c9ce900075a810f
GroupManagementIP : 10.18.236.56
NimbleVolumeName  : Connect-Clone-Test
DiskSize          : 6811560
BusType           : iScsi
WindowsVolumes    : {J:\}
FCTargetMappings  : {}
Clone             : True
Snapshot          : False
BaseSnapshotName  : Connect-Clone-Snap
ParentVolumeName  : Connect-Clone