So it is OK to do it while th system is powered on, not sure why it failed th efirst time, but
I can try it again. I will follow up, thanks
Re: move vcenter to another datastore
Re: move vcenter to another datastore
you should try disconnect vcenter's host from cluster and re-connect host to cluster
Re: move vcenter to another datastore
Hello Dave,
The best way in your situation I can recommend to do cloning of the vCenter server. Or you may perform v2v conversion.
Re: move vcenter to another datastore
Stroage vmotion is the best option, I'm not sure why would ever do a v2v conversion for somethign this simple.Vmotion failed because of the bluescreen, if it happens again you have more problems then just storage vmotioning vcenter. I'd open a ticket with support.
Re: move vcenter to another datastore
Another option is to move the it manually
How to migrate vCenter VM to a different datastore without Vmotion - Spiceworks
VM is stored in two different Datastores
Hello,
How can I Tell which Datastore my VM is using? I have 2 Datastores and one of the datastores (Datastore 2) have ALL the current files in it whereas the other (Datastore 1) only has one vmdk and modified date of 2016. I am not sure how this was created. Is it safe to assume that I can delete this old file in Datastore 1? I've looked at the disks that the server uses and they all point to the datastore 2.
Delete old VMDK from Datastore
Hell VMWare gurus,
I have a file server that had this configuration (windows server 2012 R2)
E: drive = 6TB
D: Drive = 3 virtual disks with 2 TB each
c: Drive = 100 GB
Originally, it only had 2 drives.. C and E:. But since we were looking into Azure Site Repication, it couldn't support a single drive over 4TB. This is why I created D: drive with 3 x 2TB drives. I have since deleted and removed E: drive from the vm and would like to free up the 6TB from its Datastore. How do I safely go about deleting the old vmdk so that I can reclaim the disk storage back.
Re: VM is stored in two different Datastores
Re: VM is stored in two different Datastores
Re: Delete old VMDK from Datastore
Hi,
You said you have deleted and removed the "E" Drive , you mean to say its only removed from the VM but it is still sitting in the Datastore.
Re: VM is stored in two different Datastores
No, vMotion wouldn't cause that.
Re: Delete old VMDK from Datastore
Is that a thin or think provisioned disk. If the virtual disk is thick provisioned then the data space will be automatically released.
Re: Delete old VMDK from Datastore
Re: Delete old VMDK from Datastore
Hello Suresh,
It is Thin provisioned.
Re: Delete old VMDK from Datastore
If the disk is still shown in DS then you might have removed from the VM from settings rather deleting completely. If you are sure about the name of the disk, you can delete the disk from datastore browser. That will clear the space.
Re: Delete old VMDK from Datastore
If its powered on, and if the drive is in use, vmware won't let you delete it. I'd make sure you have a good backup, but you can delete it. Another thing you may want to do to be sure is run a script like this
Orphaned files and folders - Spring cleaning - LucD notes
This will find any file that is not associated with a VM and tell you the location. If it shows up in that list its safe to delete, again to cover your self I'd make sure you have backups of anything you are going to delete.
Re: Delete old VMDK from Datastore
You're asking about reclaiming the space, previously occupied by a large VMDK file, from the datastore itself. For this, you will need to issue the UNMAP command to the datastore if it is VMFS-5. Starting with VMFS-6, the UNMAP command is issued automatically. For that, you will need to use the command esxcli storage vmfs unmap to issue the UNMAP to the datastore.
vCenter 6.5 Linked Mode HTML Web Client
Our plug-in supports linked mode by processing requests locally and forwarding to the other vCenters that are linked.
In the Flex web client, the url is something like: https://10.117.60.58:9443/vsphere-client/foo-war-4.2.0-SNAPSHOT/rest/abouts/local and it works.
In the HTML web client, the url is something like: https://10.117.60.58:9443/vsphere-ui/foo-war-4.2.0-SNAPSHOT/rest/abouts/local and it gets a HTTP 404.
Tough to support Linked Mode if we can't talk with the other vCenters.
Any ideas?
Re: vCenter 6.5 Linked Mode HTML Web Client
The HTML5-based web client doesn't listen on port 9443 like the Flex client does. The URL string supporting your plug-in should probably be https://<FQDN>/ui/foo-war-etc/etc/etc/
Deploy OVF failed with strange error
Hi,
Here is what I get when I try to deploy an OVF on a 6.5 (see attachment)
https://gyazo.com/1296eee85e9dac86432f107290047054
Anyone encountered the same error already ?
Thanks.
Eric