Yet another reason to get comfortable and start using the vSphere Web-Client. It appears that in vSphere 5.5 if you are using the c# client and decide to “move” a folder or items using the ‘move’ icon, vSphere will actually create a copy of the files at the destination folder until all data exists at the destination, at which time it will remove the files from the source folder.
Now, there is nothing inherently wrong with this, however if you do not know that this happens, it can put you in a very sticky situation if you try to do a move and are tight on disk space. Let me explain:
If your datastore is 220GB and 218GB used (cutting it kinda close, right?) Well, let’s say you have an ISO that you have in the parent directory and want to move it into another folder on the same datastore. In the case below, the SDT.ISO is 812MB. If I were to use the “Move to” feature in the c# client, it would create another 812MB file in the target folder, thereby increasing my datastore used capacity from 218GB to 219GB / 220GB. Once the copy completes, it will delete the original SDT.ISO and the datastore used capacity will then drop back down to 218GB.
Even though this says “Moving 1 file(s)” it is actually creating a copy first.
So, If you are running tight on disk space in your datastore, what is the best solution for moving files around? it’s the vSphere Web-Client!
This issue seems to only occur when using the c# on 5.5 and does not affect the Web Client at all. a Move through the Web Client is a straight out “move”.
Just one more reason to push yourself toward using the Web Client going forward.