Tag: VMWare

Leave a reply

Guest OS reporting error during quiescing

My storage engineer recently approached me about a couple of VMs that were failing to backup because it could not quiesce.  We were seeing:

 

My storage engineer recently approached me about a couple of VMs that were failing to backup because it could not quiesce.  We were seeing:

“An error occurred while saving the snapshot: Failed to quiesce the virtual machine.”

An open call to EMC said to run an extended Snapshot, however, that is only available starting with vSphere 6.5.  Despite that, running a manual snapshot using the vCenter MOB was successful.

Running scheduled and unscheduled backups failed with the same message.

However, after digging into the logs, I saw a very specific error message:

The guest OS has reported an error during quiescing. The error code was: 5 The error message was: ‘VssSyncStart’ operation failed: IDispatch error #8472 (0x80042318)

A quick search shows that this can be resolved by a number of ways, re-registering the VSS Components and re-configure VMTools.

for my purposes, re-registering the VSS Components did the trick.  Instead of running each of the following commands separately, I put them into a batch script.

cd /d %windir%\system32
net stop vss
net stop swprv
regsvr32 /s ole32.dll
regsvr32 /s oleaut32.dll
regsvr32 /s vss_ps.dll
vssvc /register
regsvr32 /s /i swprv.dll
regsvr32 /s /i eventcls.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s vssui.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml4.dll
vssvc /register
net start swprv
net start vss

Leave a reply

Reusing Computer Names in a Full Clone Pool

For the few of us using Full Clones in their Horizon View environment, we’ve always run into the issue of not being able to reuse computer names like you can in a Linked Clone pool.

However, I came across a VMWare KB that explains how to do this.  I’d advise you fully read the KB as it involves modifying the ADAM database.  I don’t have to tell you what can potentially happen if that get’s corrupted.  So backup and/ or snapshot before making changes.

So basically, you need to modify the following value in the ADAM database for the pool in question.

pae-VMNameReuseAllowed = 1

You would need to remote onto one of you connection servers, and  open up ADSI Edit from Administrative Tools, select the ADAM Database, go to OU=Server Groups, right click the pool in question and find the above attribute and change it to 1.

Have fun!

For reference here is the KB:

https://kb.vmware.com/s/article/2138714

 

 


Leave a reply

ending the week on a high note

nothing like ending the week on a high note. Been running RecoverPoint for VM for the past few weeks with lack luster results with the same level of support. Replication was painfully slow along with a UI that was severely lacking in features. However, after setting up Zerto, which took about 15 minutes or so, I was already replicating a 9.4TB VPG, with an ETA of 20h.  This same VPG in RP4VM nearly took 2 weeks to replicate.  Even after increasing the RPA resources to 8vCPU and 16GB RAM, we only ever got 11MB/sec at best.  With Zerto I’m seeing 112MB/sec constant.

 

Next week, I’ll have enough information to make the case to go with Zerto and drop RP4VM

 


Leave a reply

using Runonce to move VM to different OU

If you are using Horizon View and creating full clones, undoubtedly you’ve run into the issue of having the VM joining the domain but placed in the wrong OU.   To get around this you either moved it yourself, have a GPO do it or some VBScript.

After many searches and trial and errors, I’ve finally got it working in my environment.

In the customization specification, I have the VM join the domain using the UPN format, user@domain.com, then in the Runonce field I have the following:

cmd.exe /c dsmove -u user@domain.com cn=%computername%,cn=computers,dc=domain,dc=com -d domain.com -newparent "ou=NEW OU,dc=domain,dc=com" -p "P@ssword"

To get this to work, you’ll need to copy dsmove.exe and dsmove.exe.mui from a another computer that has AD tools installed.

You’ll need to copy dsmove.exe from c:\windows\system32 and dsmove.exe.mui from  c:\windows\system32\en-us and place them in the same folders on your image\template.

Please keep in mind this tested and verified on Windows 7,  other Windows versions may be different.  So please test thoroughly.

Hope this helps anyone using Horizon View using full desktops or manual pools.


Leave a reply

multiple sVmotions via powercli

I’m currently working on a project to move our server VM infrastructure from our old VMAX3 to a new all flash VMAX 250F SAN.   So for my own sanity sake, and to save myself from one less Google search, below is what I used to sVmotion all VMs from the “old” LUN to the new LUN

get-datastore “old-datastore” | get-vm | move-vm -datastore(get-datastore “new-datastore”)

 


Leave a reply

Reclaiming Free Space

I was tasked earlier in the week to reclaim free space from VMs that have been deleted or from snapshots that have been consolidated.

What I discovered was that from vSphere 5.0 to 5.5 had the ability but was disabled by default due to performance issues on the arrays during reclamation.  However, reclamation can still be done manually by issuing the following command

esxcli storage vmfs unmap -l <datastore name>

What is happening here is that when a VM is either deleted, moved due to SvMotion, or snapshots deleted/ consolidated, the VMFS datastore sees that space has been freed up, but not reported back to the array, and still holds on to that space.  So in the vCenter client, you’ll see the amount of free space available to you right away, but you’ll the LUN reporting a different number. I think this is normally not an issue as long as your datastores don’t fill up or if you’re running alerts against the datastores and not the array.

In any case the above command reclaims the space, but depending on how big the LUN is, it can take long time.

For example, to reclaim 50% of free space from a 8TB LUN took about 11 hours.

Good news, VMware had re-implemented the SCSI UNMAP commands in 6.5

Please keep in mind the scsi unmap command needs to be run from the host console.


Leave a reply

MacOS on vSphere ESXi 6.0

I recently installed MacOS High Sierra (10.13) on ESXi 6.0 for a developer I work with.  The steps I used were from a number of sources found on the InterWebs.

First off you need a Mac to download the installer. On the Mac, go to the App Store and and download MacOS.  While that is downloading, you’ll need to run the Unlocker script found at insanelymac.com.  Please read the notes thoroughly, and yes, a reboot of the host is needed.

After the installer is downloaded, you will need to create the ISO. The following steps are all done on the Mac

Mount the installer:
hdiutil attach /Applications/Install\ macOS\ High\ Sierra.app/Contents/SharedSupport/InstallESD.dmg -noverify -nobrowse -mountpoint /Volumes/install_app

Then create a blank ISO
hdiutil create -o /tmp/HighSierra.cdr -size 7316m SPUD -fs HFS+J

Then mount the blank ISO
hdiutil attach /tmp/HighSierra.cdr.dmg -noverify -nobrowse -mountpoint /Volumes/install_build

Then restore the base image to the blank ISO
asr restore -source /Applications/Install\ macOS\ High\ Sierra.app/Contents/SharedSupport/BaseSysyem.dmg -target /Volumes/install_build -noprompt -noverify -erase

copy the install dependencies
cp /tmp/HighSierra.dmg /Volumes/OS\ X\ Base\ System/

unmount installer image
hdiutil detach /Volumes/OS\ X\ Base\ System

convert to iso
hdiutil convert /tmp/sierra.cdr.dmg -format UDTO -o /tmp/HighSierra.iso

rename to iso and place on Desktop
mv /tmp/HighSierra/iso.cdr ~/Desktop/HighSierra.iso

Enjoy on non Apple Hardware!

 

 

 

 


Leave a reply

Power settings for ESXi hosts

About 2 weeks ago, I noticed in vRealize Operations Manager that one of my VDI hosts was experiencing higher than normal CPU contention. What was more interesting was that 90% of all VMs on that host had high cpu usage.  Moving a VM off the host, brought down CPU utilization, however, any VM moving to that host, started experiencing the same behavior.  After a few searches it turned out that the host’s power setting was set to balanced.  After setting the to Static High Performance Mode, the CPU contention dropped to below threshold and CPU demand on the host dropped as well.

So note to self and to others, when setting up hosts, set the power to high performance.  Luckily for me a reboot was not required.  This may be differ among vendors though.

 

Week of 9/24

high_cpu_contention.PNG

Past 7 Days

normal_cpu_contention.PNG

You can see above where I made the change.


Leave a reply

Edge Gateway Firewall in vCloud Director

Had an interesting issue with a client today. He had created quite a few edge gateway firewall rules with success. However a few VMs in his VPGs could not get out to the internet.  After much clicking around and testing different settings, it turns out that to allow all outbound traffic, the protocol on the firewall rule needs to be set to ANY and not TCP.


%d bloggers like this:
Bitnami