Blah, Cloud.

Adventures in architectures

  • Twitter
  • GitHub
  • Home
  • Blog
  • Kubernetes on vSphere
  • Multi-tenant IaaS Networking
  • Me
    • About
    • CV
    • Contact
Home » Blog » Infrastructure » Veeam Hot-Add Mode Fails – Mismatching VMFS block size

Veeam Hot-Add Mode Fails – Mismatching VMFS block size

17/09/2013 by Myles Gray Leave a Comment

Recently had a problem were Veeam was giving bother on one VM that had a dedicated datastore, not allowing hot-add virtual appliance mode to work.

I originally thought it was a problem with CBT (changed block tracking) so I disabled that, with no luck, as it transpires there were a few (all datastore formatting related) problems:

  • The Veeam proxy‘s datastore was formatted in VFMS-3 with a 2MB block size and upgraded to VMFS-5 (retaining its 2MB block size of course – otherwise a reformat would be needed).
  • The source machine‘s datastore was formatted in VMFS-3 with an 8MB block size and later upgraded to VMFS-5 (retaining its 8MB block size).
  • The target datastore was formatted in VMFS-5 natively with a unified 1MB block size.

So when the proxy tries to hot-add the disk the VMFS block size on the source machine‘s datastore is larger than the proxy‘s datastore block size and the hot-add fails.

VMFS v5

One solution was to put it in network mode but this can be slow and it’s not a nice way of doing things, so I wanted to run it in VA mode.

What I ended up doing was shutting down the source machine, migrating it to a VMFS-5 datastore, reformatting it’s original datastore to native VMFS-5 (native VMFS-5 volumes are all created with a unified 1MB block size) and migrating the source VM back to its original location.

The hot-add then worked as expected. In an ideal world one would reformat all their datastores to VMFS-5 with the standard 1MB block size and this is what I am working towards.

“What about the VMDK file size limit tied to block size?” I hear you say – well, as of VMFS-5 the 1MB block size now supports 2TB .vmdk files:

The limits that apply to VMFS-5 datastores are:

The maximum virtual disk (VMDK) size is 2 TB minus 512 B. The maximum
virtual-mode RDM size is 2 TB minus 512 B. Physical-mode RDMs are
supported up to 64 TB.

As of VSphere 5.5 this will change to 64TB – though why you would want a .vmdk this size beats me – i’d have the disk split and clustered, if it was a Windows box e.g. SBS, Exchange or SQL – though, if you need this disk size you’re likely already using RDM for those.

Any input on this however is welcome.

Why not follow @mylesagray on Twitter for more like this!

Show some love:

  • Reddit
  • Twitter
  • Pocket
  • LinkedIn
  • Email
  • Telegram

Similar things I've written

Filed Under: Infrastructure, Virtualisation Tagged With: CBT, hot-add, RDM, Veeam, vmfs, vsphere

About Myles Gray

Hi! I'm Myles, and I'm a Dev Advocate at VMware. Focused primarily on content generation, product enablement and feedback from customers and field to engineering.

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Myles Gray

Hi! I'm Myles, and I'm a Dev Advocate at VMware. Focused primarily on content generation, product enablement and feedback from customers and field to engineering. Read More…

Categories

Tags

active directory authentication CBT cisco datastore dell design esxi fortigate iscsi jumbo frame kubernetes lab linux load-balancing lun md3000i mtu networking NginX nic nsx openSUSE osx pxe readynas san sdelete serial teaming ubuntu vcenter vcloud director vcsa vexpert video VIRL vmdk vmfs vmware vsan vsphere vsphere 6 vsphere beta windows

Subscribe to Blog via Email

Copyright © 2021 · News Pro Theme on Genesis Framework · WordPress · Log in

loading Cancel
Post was not sent - check your email addresses!
Email check failed, please try again
Sorry, your blog cannot share posts by email.