How to create/ increase VMDK file size larger than 250GB

yes, I have made 2, 3 or 4 VMDK files then from MS, Disk management combine into one big drive.

Another option if on a SAN is Raw device mapping to get around the 254GB limit

The ONLY way to do what you need is to change the block size as @hanccocka mentions. And, the only way to change the block size is to delete/remove the datastore and re-add it, using the appropriate block size. You obviously need to backup all data off your datastore first because a reformat happens when re-adding the datastore.

~coolsport00

Hi

Thanks all for your quick responds. I know the only way is to delete and recreate Datastore. I'm just trying to know if there is work around because I heard that there is work around without deleting Datastore.

If I can't get to know what is workaround, I think the only easy way I can see for me now is to stripe the volumes. I have don't that before long time ago in physical machine but I can't remember I did for system drive volume (C: and D:) or I did for non system volume (D: and E:) .
I mean C: is my operating system volume.

Could you let me know if I can stripe all volumes including system drive (C: D: E:) to become one big dynamic volume in VM? I just worry of anything will happen to system volume

Thanks

The closest I believe are these articles:
http://kb.vmware.com/kb/1012683
and
http://www.gabesvirtualworld.com/change-blocksize-of-local-vmfs/

That is for a local volume (i.e. same disks that have both ESX/i installed and the VMFS). Except for moving data, removing/re-adding is for the most part your best bet. And, personally, I would even copy/backup my data even before trying to use vmkfstools

~coolsport00

I would not recommend striping a system C: volume. Just stripe a data volume.

Hancoocka,

Anyway can we include C: drive volume together with the rest volume in striping?
It is just risky ?

If it is that we can stripe and just risky, I'll test in another VM first.
Could you let me know if you have done or tested striping C: volume ?
In my case, I need to extend C: volume especially that's why

Thanks

spanning not supported on system, boot drive C:, spanning options not available.

so your options to extend your C: drive would be to increase the virtual disk size requiring blocksize change.

what requirement do you have, could you use Mount in the following empty NTFS folder, if its a filer server? on the c: drive?

A Windows Junction or Unix Style mount point.

Hi hanccocka

I have MSA2012 storage created multiple LUNs.
How can I connect to specific LUNs using Microsoft iSCSI connector ?

Thanks

Enabled Microsoft iSCSI initiator, and assign the iSCSI IQN to the LUN on the SAN.

Hi Hanccocka,

My server is exchanger server, recently database size and logs file size is growing too much.
I think I got an idea. I'll just attach one more VMDK file to the VM and create new database in that VMDK and migrate some mailboxes to it,

Thanks a lot for your help

Personally I would split the datastores across, mutlple LUNs and Disks.

and the database on single virtual disks, and logs on another disks, on different datastores or LUNs