Quantcast
Channel: VMware Communities: Message List
Viewing all 218216 articles
Browse latest View live

Re: Use existing virtual disk on another VM

$
0
0

Andre

 

  • I don't need the VM snapshots, i will delete all.
  • Target VM is on the same host but on a different datastore.

 

"What can be done once the virtual disk has been consolidated (i.e. doesn't have snapshots any more), is to detach it from the current VM, move the virtual disk's files (PLHQFS_1.vmdk, and PLHQFS_1-flat.vmdk) to the target VM's folder, rename them, and then attach the virtual disk to the target VM"

 

What about PLHQFS_1-000001.vmdk - this holds all the 2018 files?

 

P.S.

The point of attaching this drive to another VM is so i can run Azure Site Recovery and move the files to Azure.

My Veeam server is also in Azure so won't be able to back this up...

 

Touran


Re: Use existing virtual disk on another VM

$
0
0
What about PLHQFS_1-000001.vmdk - this holds all the 2018 files?

With deleting the snapshots, all data will be merged into the base (flat) .vmdk file, and the snapshot files (*-00000x.vmdk) will be deleted.

 

The point of attaching this drive to another VM is so i can run Azure Site Recovery and move the files to Azure.

 

For me to understand this correctly. Will this virtual disk be used permanently on the new VM, or only for the migration to Azure?

 

André

Re: Use existing virtual disk on another VM

$
0
0

Andre

 

It will be used only for migration to Azure.

 

I have been detaching and re attaching the other disks from PLHQFS to other VM's and migrating to Azure but when i tried with PLHQFS_1 it caused this big problem.

 

P.S.

I would migrate this server to Azure but its on Server 2003 and not compatible with ASR.

What Happens When a Node Fails?

$
0
0

hello - VMs set for FTT=1. Three nodes in the cluster (E-Nodes). What happens when one node fails? What do you lose? What wont you be able to do? Can someone paint a detailed picture of what to expect?

Re: Keyboard and Mouse not working in VMWare Fusion guests

$
0
0

While this solution works to solve this issue, it is not a viable and secure solution. Why on earth would it be the virtual machine which should be authorized to control the host computer instead of the opposite? There is something very wrong with this settings as it allows the virtual machine to force the host to go in hibernation when you want it to be on continuously.  So if somebody from Vmware could read this and tell us why is the guest controlling the host just to get access to the guest, I am all ears/eyes!

Re: Use existing virtual disk on another VM

$
0
0

In this case I'd go ahead, and:

  1. shutdown the Windows 2003 server (assuming you don't need it up, and running)
  2. run "Delete All" from the Snapshot Manager
  3. once finished, ensure that the virtual disk's name in the VM's settings shows up as "PLHQFS_1.vmdk", and detach it from the Windows 2003 server
  4. attach "PLHQFS_1.vmdk" disk to the new server

 

André

vSphere Upgrade Failed

$
0
0

Hi, Am trying to upgrade the env.

 

vCetner 6.0 U3c to 6.7.

 

Getting following error at prechecks. Not sure what is causing the issue. No KB article as such. Any help with be appreciated.

 

 

Error

VMware Tools driver is not initialized

 

 

Resolution

Make sure that VMware Tools driver is initialized and is running properly on the source vCenter Server Appliance (1XXXXXX). Also make sure that the ESXi host which contains the source vCenter Server Appliance is not under heavy load. Contact VMware support in case the issue cannot be resolved.

 

Re: Use existing virtual disk on another VM

$
0
0

WAIT!

I have been detaching and re attaching the other disks from PLHQFS to other VM's and migrating to Azure ...

Are these virtual disks still attached to other VM's??? In this case deleting the snapshots (if it doesn't error out anyway) may cause issues with the other VMs!

 

André


Re: vSphere Upgrade Failed

$
0
0

Just a guess, did you already try and reboot the source vCSA to see whether this solves the issue?


André

Re: Use existing virtual disk on another VM

$
0
0

Andre

 

All the VM's have been migrated with the relevant data so are all off anyway.

 

This is the only VM left.

 

Let me try and report back.

Redimensionar HD no VMWare Player

$
0
0

Meus amigos.

Estou utilizando o VMWare Workstation Player 15 e gostaria de saber de consigo aumentar o tamanho do HD virtual.

Quando seleciono o HD o botão de Expandir fica Desativado.

Seria uma limitação do Player?

 

Obrigado.

 

Taveira

Re: What Happens When a Node Fails?

$
0
0

Hello RSEngineer,

 

 

"What do you lose?"

You shouldn't lose access to anything provided all Objects are FTT=1 and compliant with their Storage Policy.

 

"What wont you be able to do?"

You won't be able to create (compliant) FTT=1 Objects until you have the node back up and participating in the cluster - this is why .vswp Objects have Force-Provisioning=1 so that they dynamically create FTT=0 Objects if there are not enough Fault Domains (nodes here) to make FTT=1 Objects and thus allowing VMs to be powered on with only 2/3 nodes online.

 

"Can someone paint a detailed picture of what to expect?"

If a host has a sudden hard failure then all of the VMs that re running on it are going to go down with and provided you have HA set-up correctly and enough compute resources it will restart the VMs on the remaining nodes.

Once the absent node comes back the changes that have been applied to the remaining data copies are synced.

 

Relatively old articles but the fundamentals remains the same:

https://cormachogan.com/2013/09/17/vsan-part-9-host-failure-scenarios-vsphere-ha-interop/

How VSAN handles a disk or host failure

 

 

Bob

Re: What Happens When a Node Fails?

$
0
0

Duncan write dozen of articles about vSAN. Take a look to Search for "vsan" - 56/58 - Yellow Bricks

 

10154498566_d0e1dbcc15[1].jpg

 

If the VM runs on another host... nothing happends but you will lose the Disk redundancy.

 

If the VM runs on the affected host.... HA kicks in and restart the VM as long as one Data copy and Witness or both Data copys are available.

 

If you have one Host in maintenance mode and during this period you loose disk you have  problem. This is why most ppl prefer to start with 4 or more Hosts and vCenter Foundation was changed to 4 managable Hosts.

 

If you lose a cache device... the whole diskgroup goes offline.

If you lose a capacity device.... the data will be recreated on host #4  if you have it.

 

Regards,

Joerg

Re: What Happens When a Node Fails?

$
0
0

Thanks, Bob.

 

Can you please elaborate a bit more on this phrase: "this is why .vswp Objects have Force-Provisioning=1 so that they dynamically create FTT=0 Objects if there are not enough Fault Domains (nodes here) to make FTT=1 Objects and thus allowing VMs to be powered on with only 2/3 nodes online."?'

 

Also, with only 2 out of 3 nodes online, can you create a VM with an FTT=0 during that outage? I know this isn't advisable because there is no protection, but I am just wondering if it's possible.

 

Also, when you mentioned the VMs migrating to the surviving nodes from the failed node, what VMware feature is doing that? is it vSphere HA? Does that automatically come with vSAN or is it an added license?

 

 

Re: What Happens When a Node Fails?

$
0
0

Thanks to you, too, Joerg. Good stuff. I am asking all these questions because I have a client (I'm a pre-sales SE) who is balking at the price of a 4-node cluster. He has a small environment, but it runs all his mission critical apps, so I configured 4 nodes to be safe and as flexible as possible. I am wondering if I should just take out a node


Re: vSphere Upgrade Failed

$
0
0

yes. I tried that. Did not help.

Re: vSphere Upgrade Failed

Re: Horizon Client, Error: Timeout was reached.

$
0
0

It's 2019 and I'm just now for the first time in my over half-century of existence here noticed this error message.

 

There doesn't seem to be a set time frame as to when the error message occurs after "safely removing " a usb flash stick.

 

The error does not happen on any machine except those tester laptops that have mint 19 installed.   I have experimented with 19 on and off for a couple of months now (maybe longer) and cannot recall if the error ever happened in the 32 bit version of mint 19.  I can, however attest to the error in the 64 bit version.

 

Oddly enough, nothing happens when I click the "x" in the upper-right hand corner of the error message.    The message only offers one option, which is "OK".

 

OK!?!

 

Again this only happens with 19 and have installed it on an octocore desktop (which is getting wiped tonight for another purpose), and a couple of laptops (most of which were 2 core processors).

 

The error does not appear to cause noticeable, as of yet, harm to data.  The bug does not appear to transpose itself through the network.

 

If anybody in this century knows of a fix, that would be great.

Re: vSphere Upgrade Failed

VMName - Virtual Machine swap object : Physical disk placement

$
0
0

Hi All,

 

Recently we have deployed one vSAN setup. All went well except one error on vSAN  virtual object tab as below. Can anyone help to fix this.

 

 

Thanks,

Suhag

Viewing all 218216 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>