Hi, We are also facing similar problem.Unable to delete or unmount the ISO datastore from any of the ESX host.There is currently no data inside it and also none of the VMs using it.Getting bel...
See more...
Hi, We are also facing similar problem.Unable to delete or unmount the ISO datastore from any of the ESX host.There is currently no data inside it and also none of the VMs using it.Getting below error when try to delete "Remove datastore xxxxxx The resource 'XXXXDSISO' is in use" When trying to unmount it... attached is the message from vCenter.Please note : there are 5 hosts in cluster but while unmount its only showing 3 hosts which are of version ESXi 5.0 Any new suggestions other than posted above ?
I faced similar problem today ..created the 1st VM from the template and edited the Virtual H/W at the same time ....the VM was up and running but i never noticed that its pointing to the templat...
See more...
I faced similar problem today ..created the 1st VM from the template and edited the Virtual H/W at the same time ....the VM was up and running but i never noticed that its pointing to the template vmdk file Could realize the problem when i was not able to create another VM using the same tempalate.It was beacuse the vmdk was locked by the previous VM. The issue was resolved after manually editing 1st VM ....pointed the correct vmdk ..All set now
Dear All, Thanks for the inputs and suggestions on this. In this case ...the Converter was able to het info of source machine and destination ESX ...but the conversion process was getting s...
See more...
Dear All, Thanks for the inputs and suggestions on this. In this case ...the Converter was able to het info of source machine and destination ESX ...but the conversion process was getting stuck after the helper VM boots up and then try to map the provided temp IP.We suspect this to be network related problem.We tested this with different range of IP address and VLANs. Finally concluded that the Converter works fine in production cluster ...but some issues at DMZ cluster.Again it was fine at DC but issues at DR site.The Vendor suggested to apply some patched on vCenter Server and its all ok now
Dear All, I am looking for some information if there is any specific configuration needs to be done if I have to do P2V conversion via the vCenter ? We have been facing issues for SUSE Linu...
See more...
Dear All, I am looking for some information if there is any specific configuration needs to be done if I have to do P2V conversion via the vCenter ? We have been facing issues for SUSE Linux physical machines when we use the standalone converter and specify vCenter as the destination.The conversions have been successful when we choose the ESX server as destination.Conversion job for same ESX as destination fails when its added to the vCenter Server. We are wondering why its failing if we add the same ESXi 5 host in to vCenter 5 and while choosing destination we specify the vCenter ip (then next step the host ip).On both cases the converter is able to identify the source and destination,can customize the source server h/w config ..but the conversion fails showing network related error. Please suggest if there is any specific config needs to be done for vCenter Regards, Sabyasachi
The VM is now recovered by trying the repair option from Windows bootable CD.The same step was tried mor ethan 5 times before ....but it worked finally.Not sure what exactly was the problem ...bu...
See more...
The VM is now recovered by trying the repair option from Windows bootable CD.The same step was tried mor ethan 5 times before ....but it worked finally.Not sure what exactly was the problem ...but certainly its not related to VMware Conversion ...may be the drivers were missing after conversion
Hi, We have been trying resolve a P2V conversion issue where the VM is facing BSOD upon Power ON.The error message on BSOD is "STOP 0x7B INACCESSIBLE_BOOT_DEVICE" which points to the failure o...
See more...
Hi, We have been trying resolve a P2V conversion issue where the VM is facing BSOD upon Power ON.The error message on BSOD is "STOP 0x7B INACCESSIBLE_BOOT_DEVICE" which points to the failure of identifying proper format of the disk.This might be due to the physical SCSI drivers the OS is trying to locate ont he new VM. OS Version : Win 2000 server Physical Server : HP DL 380 G2 (Source for conversion) There are couple of methods of fixign it but we do not want to make any changes to the source Physical server which is in production Attached below is the BSOD message for your reference Please suggest if anything can be tried with the Destination VM which is not booting up at this moment Regds, Sabya
Hey ...Are you talking about the vCenter backup or the VM backup ? The snapshot error you are facing must be while taking a snapshot of Running VM ....i have encountered it few days back.The rea...
See more...
Hey ...Are you talking about the vCenter backup or the VM backup ? The snapshot error you are facing must be while taking a snapshot of Running VM ....i have encountered it few days back.The reason is due to high I/O intesive application on the VM .This can be fixed by removing the VSS option from VMware tools Regarding the vCenter Server backup ...you should not consider shuting down the Server as it can be fully backed up using any backup software Please share what exactly is the chalenge for vCenter
Could you please try to move the VM to other Host and try the same steps ? If you have only a single host ....then try to restart the VMware services on the host #service mgmt-vmware restart
Hey continuum...I am also now looking for such options in a vSphere environment But the challenge we have is there is no VMware infra at the remote DC from where we want to migrate the physica...
See more...
Hey continuum...I am also now looking for such options in a vSphere environment But the challenge we have is there is no VMware infra at the remote DC from where we want to migrate the physical machines.I can think of vmware cold migration (P2V) or plate spin powerconf .But nto sure if those should be adopted for large scare migrations.also heard of Acronis true image Could you please suggest if there is any new tool ?
Dear All, We are looking forward for some server consolidation activities in a large scale.The targeted servers are at different geographical location and different kind of environment. Cou...
See more...
Dear All, We are looking forward for some server consolidation activities in a large scale.The targeted servers are at different geographical location and different kind of environment. Could you suggest any P2V tool other than VMware or any image level backup system which can be imported/exported to our Vmware Infra ? Regards, Sabya
VMware converter option should be used as the 1st option as you do not have any plans to upgrade the ESX servers.Hence I do not see any point to add/remove them to new vCenter
The VMware configuration file or .vmx file can only be obtained by creating a new Virtual machin. ...I believe you are trying to mount this hard drive on a Guest server or want this as a syst...
See more...
The VMware configuration file or .vmx file can only be obtained by creating a new Virtual machin. ...I believe you are trying to mount this hard drive on a Guest server or want this as a system itself.If you want to use it as a Guest VM ....you have to create a new VM on VMware workstation and during the process you have to select the option ...use an existing disk and point to the .vmdk you have The system should come up normally after the new VM creation You can also test the .vmdk by mounting it to an existing Virtual machine which will help you to know if the disk status id fine
Thanks for the detail explanation ...I am also expecting the similar out put and planning the activity on production server. Rather than trusting the backup system ...i would prefer to clone the...
See more...
Thanks for the detail explanation ...I am also expecting the similar out put and planning the activity on production server. Rather than trusting the backup system ...i would prefer to clone the VM before doing this change Does this sounds good ?
Dear Simon, I meant when we had to revert to previous snapshot ....it dumped the other 2 datastore vmdks to the 1st datastore where the snapshot files and .vms files are stored.This is tested ...
See more...
Dear Simon, I meant when we had to revert to previous snapshot ....it dumped the other 2 datastore vmdks to the 1st datastore where the snapshot files and .vms files are stored.This is tested by me already on a test environment Now we are running on a snapshot and our data already grown much ...so if I delete all the snapshots for the VM (online/offline)..is it going to affect the current status of the VM ? will there be any data loss on the additional vmdks ?
Thanks Simon for the nice doc on snapshot I have been testing these since 2-3 days on test machines with multiple datastores.I have found the same issues ..while reverting to the snap shot .....
See more...
Thanks Simon for the nice doc on snapshot I have been testing these since 2-3 days on test machines with multiple datastores.I have found the same issues ..while reverting to the snap shot ...its dumps all vmdks to the parent datastore.Then removing the snapshot removes those vmdk files.This sounds good if this is done soon after creating the snapshot. But in our case its been 3 months and now we have vmdks grown to larger sizes.I suspect there will be issues if we remove the snapshot and if the grown up vmdks also deleted.We are fine if those are moved to their original location
The challenge is while reveting back to the old snapshot.All the vmdks are getting dumped on the 1st Datastore May be this is design error to have each vmdk on a dedicated Datastore....but we ...
See more...
The challenge is while reveting back to the old snapshot.All the vmdks are getting dumped on the 1st Datastore May be this is design error to have each vmdk on a dedicated Datastore....but we are good on all other cases than snapshoting
Dear All, We have vSphere 4.0 environment where we have 2 ESX on cluster and 40-50 VMs (Mostly on production).Our Datastore design is specific to VMs as we have allocated 1 Datastore for each ...
See more...
Dear All, We have vSphere 4.0 environment where we have 2 ESX on cluster and 40-50 VMs (Mostly on production).Our Datastore design is specific to VMs as we have allocated 1 Datastore for each VM and also multiple Datastores for VMs (in case of multiple discs on a Server ...i.e each vmdk comes from separate Datastore --> separate LUN from iSCSI storage) Current Challenge : Now we are facing trouble in case of snapshots.When we take any snapshot and try to revert to that ..all the vmdks of diff datastores are getting stored on the 1st datastore which causing space issue as we have limit for each Datastore Also verified that the old vmdk files are not in use and idle on other datastores and the 1st Datstore size keeps on increasing We have managed to survive by increasing the size of the 1st Datastore to contain all growing vmdk files and we are fine with that. Now we want to remove the Datastores and also snapshots which are not in use for the VM ...what is the best way to do it ..I am sure Server needs to be Shut down for it. Please suggest ... Regards, Sabasachi
In this case ..May be you can crosscheck if there was any alarm enabled at the Host level. In case of a conflict between the Host level and Cluster or vCenter level ,the alarms at host level a...
See more...
In this case ..May be you can crosscheck if there was any alarm enabled at the Host level. In case of a conflict between the Host level and Cluster or vCenter level ,the alarms at host level are applied.