Download the EqualLogic Host Integration Toolkit (HIT Kit) for Microsoft from the EqualLogic support site. Install the PowerShell Tools portion of the HIT Kit on the computer you want to manage the SAN from. For a PS4000, this computer doesn’t need access to the iSCSI network as long as it has connectivity to the management network.
The following PowerShell script creates a 36GB thin provisioned volume named mikefrobbins with a snapshot reserve of 100%, sets a description for the volume, allows two specific IP addresses to access the volume and its snapshots, sets up a 1am snapshot schedule that takes place once per day and attempts to keep 7 snapshots as long as the total size of the snapshots doesn’t exceed the snapshot reserved space.
$GrpAddr = "192.168.1.1"
$VolName = "mikefrobbins"
$VolSize = "36864"
$SnapshotReserve = "100"
$Description = "C Drive for mikefrobbins WebServer"
$ThinProvision = "Yes"
$iSCSI1 = "10.0.0.1"
$iSCSI2 = "10.0.0.2"
$ACL = "volume_and_snapshot"
$SchName = "wwwDailySnapshot"
$SchType = "Daily"
$Start = "01:00AM"
$Repeat = "0"
$Count = "7"
Import-Module -name "c:\program files\EqualLogic\bin\EqlPSTools.dll"
Connect-EqlGroup -GroupAddress $GrpAddr -Credential (Get-Credential)
New-EqlVolume -VolumeName $VolName -VolumeSizeMB $VolSize -SnapshotReservePercent `
$SnapshotReserve -VolumeDescription $Description -ThinProvision $ThinProvision
New-EqlVolumeACL -VolumeName $VolName -InitiatorIpAddress $iSCSI1 -ACLTargetType $ACL
New-EqlVolumeACL -VolumeName $VolName -InitiatorIpAddress $iSCSI2 -ACLTargetType $ACL
New-EqlSchedule -VolumeName $VolName -ScheduleName $SchName -ScheduleType $SchType `
-StartTime $Start -TimeFrequency $Repeat -KeepCount $Count
Disconnect-EqlGroup -GroupAddress $GrpAddr
You could use the GUI to accomplish the same task, but GUI’s generally leave too much room for error. Using a PowerShell script allows you to create a volume exactly the same way each time with no chance of forgetting to do something like creating a snapshot job. Nothing worse than having something missed by your backup job and committing yourself to recovering it from a snapshot only to find out: “Oh yeah, I forgot to set that up”.