Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Virtualization Manager (VMAN) > VMAN Documentation > VMAN 8.2 Administrator Guide > Optimizing virtual resources > Evaluate VMs using the Sprawl dashboard > Manage orphan VMDK files

Manage orphan VMDK files

Table of contents
No headers
Created by Caroline Juszczak, last modified by Caroline Juszczak on Dec 01, 2017

Views: 81 Votes: 0 Revisions: 3

Updated: November 30, 2017

VMAN continues tracking VMDK files, listing all located orphan VMDK files with detailed information. You can select the datastore to review more information and determine if the VMDK should be deleted.

If you do not monitor all virtual systems as nodes in the Orion Web Console, the listed datastore files could be used by unmonitored hosts. Prior to deleting these datastores, verify if the VMDK file can be cleanly deleted.

In this example, you may review all orphaned VMDKs once a month to reclaim misused resources and remove obsolete data. With VMs removed, you no longer require these VMDK files. In this example, you review these VMDK files and remove those determined obsolete.

  1. Click My Dashboard > Virtualization > Sprawl.
  2. Locate the Orphaned VMDKs resource.

    This resource lists the orphaned VMDKs per VM, including all associated VM datastore info, the size, and an option to delete the datastore. Reviewing this information, the rio-vcenter and riovcenter VMDKs should be removed. The VMs were deleted at the beginning of the month, leaving these files taking up a large amount of space with an associated VM.

    File:Success_Center/Reusable_content_-_InfoDev/VMAN/VMAN_8.1_Admin_Guide/0020-Optimizing_virtual_resources/0010-Evaluate_VMs_using_the_Sprawl_dashboard/0020-Manage_orphan_VMDK_files/orphan-vmdk-resource.png

  3. To delete the orphans, click Delete datastore file for rio-vcenter.

    A message displays verifying if you want to delete the VMDK.

    File:Success_Center/Reusable_content_-_InfoDev/VMAN/VMAN_8.1_Admin_Guide/0020-Optimizing_virtual_resources/0010-Evaluate_VMs_using_the_Sprawl_dashboard/0020-Manage_orphan_VMDK_files/virt-deletedatastore.png

  4. Click Delete.

    Repeat the process for the Riovcenter VMDK. VMAN deletes the orphaned VMDK files from the environment.

 
Last modified

Tags

Classifications

Public