• Buy Now
    • Rackspace Cloud
    • Email & Apps
    • Fanatical Support for AWS
    • Managed Google Cloud Platform
    • Office 365
  • Log In
    • MyRackspace Portal
    • Cloud Control Panel
    • Rackspace Webmail Login
    • Cloud Office Control Panel
  • Rackspace Logo
  • Developer Home
  • Developer Documentation
  • Blogs ▼
    • Technical Blog
    • Rackspace Blog
    • Solve: Thought Leadership
  • Support Documentation

Developer Docs


Let’s Build Something Powerful Together!

End-to-End Multicloud Solutions.   Solving Together.™   Learn more at Rackspace.com

Submit an issue
  • Microsoft Private Cloud Hyper-V Customer Handbook
  • About Microsoft Hyper-V
    • Roles and responsibilities
      • Managed virtual machines
      • Unmanaged virtual machines
    • Licensing
      • Virtual machine licensing
  • Getting started with Microsoft Hyper-V
    • Microsoft Hyper-V architecture
    • Microsoft Hyper-V features
      • Rackspace Hyper-V managed services
    • Microsoft Server 2016
    • Add-on services
      • Hyper-V Replica
        • Hyper-V Extended Replication
        • Requesting a failover
      • Cloud Replication for Hyper-V
        • Requesting a failover
  • Microsoft Hyper-V user manual
    • Manage permissions
      • Assigning permissions by user
      • Assigning permissions by product
      • Managing groups
      • Changing global permissions
    • Credentials management
      • Windows Server 2016 (v2)
        • Rackspace
        • Customer
      • Windows Server 2012 (v1)
        • Rackspace
        • Customer
    • Datastore overhead
      • Why does Rackspace require this?
      • What else can consume space on my datastores?
    • Ordering virtual machines
      • Virtual machine OS images
      • Create a new managed virtual machine
      • Create a new unmanaged virtual machine
      • Converting unmanaged VM to managed
    • Managing virtual machines
      • Start or resume a virtual machine
      • Shut down a virtual machine
      • Checkpoint a virtual machine
        • Reverting a checkpoint
        • Delete a checkpoint
      • Export virtual machines
      • Resize virtual hard disks
      • Making a virtual machine highly available
      • Remove and delete virtual machines
    • Decommissioning virtual machines and hypervisors
    • Virtual Fibre Channel SAN
      • Deploying virtual SAN
    • Migrating from Server 2012 to 2016
  • Frequently asked questions
  • Additional resources
    • SLA information
    • Additional links
  • Disclaimer

Datastore overhead#

Rackspace requires that customers have a certain percentage of each Cluster Shared Volume (CSV) datastore free at all times. We call this datastore overhead. Use the following guidelines to ensure that there is enough datastore overhead:

  • 10% free space, if the partition size is less than 1TB
  • 10% free space, if the partition size is between 1TB and 5TB
  • 10% free space, if the partition size is greater than 5TB

Why does Rackspace require this?#

If a datastore runs out of free space, it causes any VMs running on that datastore to immediately hard stop, causing downtime. Stopped VMs cannot be started until insufficient free space on the datastore us available.

After VMs are stopped, it is possible that a VM might not power on due to insufficient space on the datastore.

VM performance impact is possible when the datastore is critically low on space, and certain Hyper-V features, such as checkpoints, might no longer function.

What else can consume space on my datastores?#

  • Checkpoints: When performing a checkpoint, a delta disk is created for each disk you have on your VM. While the checkpoint is active or a export is in progress, all changes are written to the delta file(s). Delta files can grow rapidly and without your awareness.
  • VM log files: All VM log files are stored within the VM container folder on the datastore. Normal log files are only a few MB in size. However, log files can grow larger in size depending on VM activity.
  • RAM: Powered on VMs have a VM BIN file equivalent in size to the amount of RAM assigned to the VM. If a VM’s AutomaticStopAction is set to Save, Hyper-V reserves disk space equal to the amount of memory used by the VM when it is running. This ensures that memory can be written to disk when the physical computer shuts down. If the VM is powered off, there is no BIN file present, even if the VM is set to save.
Previous Credentials management
Next Ordering virtual machines
Developer Network
  • Developer Center
  • API Documentation and User Guides
  • SDKs
  • Rackspace How-To
Blogs
  • Technical Blog
  • Rackspace Blog
  • Solve: Thought Leadership
Other Information
  • Customer Stories
  • Events
  • Programs
  • Careers
  • Style Guide for Technical Content
©2020 Rackspace US, Inc.
  • ©2020 Rackspace US, Inc.
  • About Rackspace
  • Privacy Statement
  • Website Terms
  • Trademarks