The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Search the VMware Knowledge Base (KB)
View by Article ID
Managing out of space issues on Mirage volumes (2031632)
Purpose
This article provides best practices and options to handle situations when your Mirage volumes are full.
Resolution
Clean existing volumes
Identify files that can be removed from the Single-Instance Storage (SIS).
File a support request with VMware Technical Support to request a ServerCvdReport to identify file extensions/directories that can be eliminated from the SIS, and note this Knowledge Base article ID (2031632) in the problem description. For more information, see Filing a Support Request in My VMware (2006985).
Update upload policy: exclude files/directories.
Note: Changing the update policy does not affect snapshot data, therefore all data previously stored in snapshots will continue to exist until overwritten. Snapshots are overwritten after the number of snapshots exceeds the configured number allowed.
Decrease the configured number of snapshots maintained by Mirage in the system configuration.
Sync all devices and wait for uploads to complete.
Compress existing volumes
Consider compression options on affected volumes:
NTFS storage:
If the volume is located on a Windows machine, compress the content of Mirage's volume root directory.
Note: One example implementation reported an average of 30% savings due to NTFS compression. The example also indicated a negligible increase in CPU utilization.
NetApp storage:
NetApp supports two types of storage compression, LZO and fixed-size block dedupe.
Adding volumes
Adding additional volumes is a simple solution for space issues:
Add a new volume.
Use the CVD view to identify large CVDs that can be moved from the full volume.
Move the CVDs to the new volume.
Notes:
Only the unique files are removed from the source volume when moving a CVD.
Moving CVDs can be a lengthy process. The duration is extremely dependent on the number of files in the CVD being moved. To expedite the move, VMware recommends creating several move tasks (which will run concurrently), and to run the move during off-hours (for example, on the weekend).
Replacing volumes
When replacing a full volume with larger storage, the normal procedure is:
Unmount the full volume.
Copy the content of the full volume to the new storage.
Change the volume path from the old volume path to the new volume path by editing the volume information in the Mirage Management Console.
Mount the new volume.
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.
