File Server Datastore Provisioning assistance

[vipclubber]

I am building a Win2012R2 File Server.

Datastore1 = 800GB

Datastore2 = 12TB

Datastore1 is taken. Datastore2 will have about 2TB space used for storage of copies of VMs. The rest is for File Server.

What provision is recommended to use for a growing File Server? Thick or Thin?

Is it ok to OVER allocate on Datastore2 space?

If other data on Datastore2 (other than File Server) begins to grow how will the File Server make up for the difference?

Thanks in advance.

[vipclubber]

Thanks. I had a backup so I restored it. However, while trying to MOVE the VM between local Datastores located on the same host I ran into an error. Any idea?

PS. To resolve below I had to reboot host. When I did the VM that was in process of MOVING was intact and I was able to successfully MOVE it again with no issues.

[a_p_]

To find out what exactly caused the PSOD, you may likely need to open a support call with VMware.

However, there have been lots of fixes (including network issues, and Emulex devices) since ESXi 5.5 Update 1 was released, so you may consider to update/patch the host(s). It's also worth checking whether the hardware vendor (HPE in this case) offers a custom ESXi image for your system(s) which contain hardware related drivers, other than those provided with the default VMware image.

André

[vipclubber]

This is the custom image from HP. I found out that this is a known issue. Should I go straight to version 6?

Also, what are some good ways to transfer VMs between same Datastores on the SAME host and VMs between the HOSTS?

The scp command is great but very slow and the MOVE option only works between the datastores on the same host.

Any advice is appreciated.

Thanks in advance...

[a_p_]

This is the custom image from HP. I found out that this is a known issue. Should I go straight to version 6?

It depends on whether your hardware supports ESXi 6.0. In case it does I'd suggest you go straight to the HPE Custom Image for ESXi 6.0 Update 2‌. Please keep in mind that this upgrade requires new license keys, and - in case you are managing the hosts through vCenter Server - vCenter Server has to be upgraded first!

Also, what are some good ways to transfer VMs between same Datastores on the SAME host and VMs between the HOSTS?

If the hosts are being managed by vCenter Server you can easily migrate the VMs using the vSphere Client, or Web Client. With vSphere Essentials Plus (or better) migrations between hosts - even without shared storage - can be done with the VMs powered on. For migrations between standalone hosts (without vCenter Server in place), I'd suggest you either restore the VM on the new host from your backup, or export the VM to OVF/OVA from the source host, and import it on the target host.

The scp command is great but very slow and the MOVE option only works between the datastores on the same host.

SCP and other native Linux commands put high load on the VMFS file system, and should not be used for large .vmdk files. If you need to copy a .vmdk file from one datastore to another, use the vmkfstools command instead.

André

[vipclubber]

Can you provide a sample of vmkfstools command to move VM folder WORLD1 between separate hosts?

Example to copy WORLD1 from 10.1.1.4 datastore1 to 10.1.1.7 datastore2.

Also, what is the best way to shut down individual VMs? Should I log in into each VM and shut it down manually OR can I use vShpere shut down guest option?

Thanks in advance...

[a_p_]

As mentioned before, vmkfstools can be used to copy a virtual disk from one datastore to another. However, both datastores need to be accessible from the same host. For examples see e.g. https://kb.vmware.com/kb/1028042‌

To migrate VMs between standalone hosts (no shared datastores) use backup/restore, or export/import.

Also, what is the best way to shut down individual VMs? Should I log in into each VM and shut it down manually OR can I use vShpere shut down guest option?

Whatever you want. With VMware Tools installed in the guest OS, "Shut down guest" will gracefully shut down the guest OS.

André

[vipclubber]

Thanks.

Like with SCP command the vmkfstools command will work in SSH Putty?

If not, how to enter vCLI prompt?

Also, I see the command as follows:

vmkfstools -i "/vmfs/volumes/Datastore/examplevm/examplevm.vmdk" "/vmfs/volumes/Datastore 2/newexamplevm/newexamplevm.vmdk" -d thin -a buslogic

Where to obtain this information:

-d thin -a buslogic

Also what if I am coping the entire VM folder and not a single file?

[vipclubber]

Also  in addition to my post, can the vmkfstools command be used to copy files/folders between HOSTS?

[a_p_]

To get an overview of the available command line option, run either vmkfstools --help from the command line (i.e. through a putty session), or take a look at the documentation (e.g. vmkfstools). You can use this tool to clone virtual disks from one datastore to another on the same host. To copy other files use either the cp command or the datastore browser.

André

[vipclubber]

Thanks but if I am reading it correctly vmkfstools are used to CLONE the .vmdk file from THIN to THICK provision, for example and not as much as to copy VMs.

Can you please confirm?

[a_p_]

'vmkfstools' can be used for different tasks. Cloning a virtual disk from one datastore to another, without changing the disk format is actually the same a copying it. However, 'vmkfstools' works differently compared to e.g. the native 'cp' command.

'vmkfstools' allocates the required disk space first, and then starts copying data blocks. The 'cp' command (as well as other tools) allocate disk space on demand (i.e. the file size on the target grows with copying data), which puts a high load on the VMFS file system.

André

[vipclubber]

Understood but the article only provides a CLONE option not the COPY command.

The clone option requires partition information line thin and thick formats.

For example:

vmkfstools -i "/vmfs/volumes/Datastore/examplevm/examplevm.vmdk" "/vmfs/volumes/Datastore 2/newexamplevm/newexamplevm.vmdk" -d thin -a buslogic

Is there a sample command for just copy and what would it look like please, if possible?

[a_p_]

Understood but the article only provides a CLONE option not the COPY command.

That doesn't really matter, as long as the result is the same. Don't you agree?

For valid options run the man vmkfstools command.

vmkfstools -i source target -d disk_format -a adapter_type

The target disk_format depends on what you want/need, and the adapter_type is one that's supported by the guest OS. It's lsilogic for most OSs nowadays. However, you can check the current settings in e.g. the source .vmdk's descriptor file. If you omit these two options, the target format should be the same as the source.

André