Administrator Guide

Steps
1. If you are connected to a Data Collector, select a Storage Center from the drop-down list in the left navigation pane of Unisphere
Central.
2. Click Summary.
The Summary view is displayed.
3. Click (More Actions) and select Space Reclamation.
The Space Reclamation wizard opens.
4. Select the storage type on which to perform a space reclamation assessment and click Next.
5. (Optional) If the wizard finds volumes in the recycle bin, select the volumes to delete, and click Next.
6. (Optional) If the wizard finds unmapped volumes, select the volumes to delete, and click Next.
7. (Optional) If the wizard finds volumes that are destinations for replication, select the volumes to delete, and click Next.
8. (Optional) If the wizard finds volumes with snapshot overhead that is larger than 1 GB, select the volumes with snapshots that can be
expired, and click Next.
For each volume selected, select the snapshots to expire and click Next.
NOTE:
The active snapshot and the latest snapshot cannot be expired.
9. (Optional) If the wizard finds volumes that can be migrated to another storage type, select the destination storage type, select the
volumes to migrate, and click Next.
10. On the Confirmation page, review the selected space reclamation actions.
To perform the actions, select the I have reviewed all of the actions checkbox and click Next.
11. On the Summary page, view the status of the space reclamation actions and click Finish when the actions are complete.
Managing Virtual Volumes With Unisphere Central
VVols is VMware’s storage management and integration framework, which is designed to deliver a more efficient operational model for
attached storage. This framework encapsulates the files that make up a virtual machine (VM) and natively stores them as objects on an
array.
The VVols architecture enables granular storage capabilities to be advertised by the underlying storage. Storage containers, which defined
the available storage capabilities, can be created for vSphere Storage Policy-Based Management.
Related concepts
VVols
Configuring VVols in Unisphere Central
VMware vSphere 6 or later is required to run VVols in a storage environment with Unisphere Central.
Requirements and Recommendations for Configuring VVols in
Unisphere Central
The following requirements and recommendations apply to setting up Unisphere Central to use VVols:
Unisphere Central must be installed on a clustered hypervisor of choice with high-availability (HA) enabled.
Fault Tolerance is recommended.
Unisphere Central must not be deployed or moved to a VVol datastore on the managed Storage Center. Unisphere Central must be
installed and remain on a traditional SAN volume
Unisphere Central must be installed on a separate management cluster.
VVols is supported with the iSCSI and Fibre Channel interfaces only. FCoE and front end SAS are not supported for VVols.
The network card must support the Secondary LUNID feature. For more information, search for I/O Devices with the Secondary
LUNID in the VMware Compatibility Guide, available from http://www.vmware.com/resources/compatibility/search.php.
Safeguarding VVols Data
A critical component of the total VVols solution is VVols the VM metadata.VMware's ESXi reads and writes this metadata on a per-VVol
basis during control plane operations, such as power-on, power-off, and snapshots.
The Data Collector stores the VVols metadata written by the VASA provider in a database.
62
Storage Center Administration