Release Notes

24 Dell Virtual Storage Manager: Installation Considerations and Local Data Protection | 2079-BP-V-VSM
1. From the VSM Inventory > Datastores page, highlight a datastore to resize, and then click the Delete Dell
Datastore icon . Alternatively, right click a datastore and select Delete Dell Datastore from the context
menu.
2. A verification dialog is displayed, with the warning ALL DATA WILL BE LOST! Select the checkbox to
acknowledge the deletion and enable the OK button allowing you to proceed.
Figure 8 Datastore deletion warning
3. When you click OK, VSM performs all the necessary tasks within vCenter to unmount the datastore from all of
the hosts, log the iSCSI initiators out, take the datastore offline and delete the datastore volume from the PS
Series array.
vVol datastores can be deleted in the same manner.
3.3.5 VMFS datastore access policy
Access to iSCSI volumes is restricted by an Access Control List (ACL) entry. When creating a datastore through VSM, two
options are presented for restricting access to the volume in the ACL Source section: Auto-generate ACL and Specify
ACL.
Auto-generate ACL behaves differently depending on the version of array firmware. For all versions of firmware 6.0 and
prior, Auto-generate ACL creates an ACL entry or entries consisting of the selected host(s) IQN. For arrays running
firmware 7.0 and above, Auto-generate ACL uses the new Access Policies feature. If an existing Access Control Policy or
Access Control Policy Group meets the access needs of the selected cluster or hosts, it will be used. If not, a new Access
Control Policy or Access Control Policy Group is created to meet the access needs of the cluster or hosts. For more
information on Access Policies, see the document, Access Control Policies.
3.3.5.1 Creating a new ACL template
ACL templates provide a way to predefine the access policy used for a volume on an iSCSI array. Typically, in a
virtualized environment, all hosts in a cluster access the same volumes, so a single ACL template would be created to
reflect this. This results in one ACL template for each vSphere cluster in the environment. Occasionally, there may be
exceptions where access to a datastore is limited to only a few hosts in a cluster or where access to a datastore is
required from hosts in multiple clusters. ACL templates can be created to reflect these requirements.