Friday, April 15, 2016

TSM Backup Error: An error occurred while saving the snapshot: Failed to quiesce the virtual machine

Problem: TSM backup error; An error occurred while saving the snapshot: Failed to quiesce the virtual machine.
ANS4066W Snapshot operation attempt 1 of 2 for the guest virtual machine 'vmname' failed using "VMware Tools" snapshot.

VMWare Info

Solution: Disable VSS application quiescing using VMware Tools:

1. Open the C:\ProgramData\VMware\VMware Tools\Tools.conf file in a text editor, such as Notepad. If the file does not exist, create it.
2. Add these lines to the file:

vss.disableAppQuiescing = true

3. Save and close the file.
4. Restart the VMware Tools Service for the changes to take effect.
5. Click Start > Run, type services.msc, and click OK.
6. Right-click the VMware Tools Service and click Restart.

TSM Backup Error: ANS1715E A filespace already exists for virtual machine (vmname), but with a different virtual machine UUID

Problem: You've restored a virtual server using TSM and notice your backup is failing with error 4379. Examining the dsmerror. log you find this error; ANS1715E A filespace already exists for virtual machine (vmname), but with a different virtual machine UUID.

Solution: Modify the UUID of the virtual server to match the previous UUID, thus reconnecting the new VM to the TSM Filenode that already exists.

Specifying a UUID for a Virtual Machine
Note: VMware Tools may need to be removed from the virtual machine prior changing the UUID to prevent the UUID from reverting.
In some circumstances you may want to assign a specific UUID to the virtual machine. To do this, you need to override the automatically generated UUID value. Power off the virtual machine and edit its configuration (.vmx) file to set the value of the UUID parameter. Use a text editor to edit the configuration file. The format for the line is:
uuid.bios = ""

The UUID value must be surrounded by quotation marks. A sample configuration line looks like:

uuid.bios = "00 11 22 33 44 55 66 77-88 99 aa bb cc dd ee ff"

After you add this line to the configuration file, power on the virtual machine. The new UUID is used when the virtual machine boots.

Tuesday, April 21, 2015

RDBSS process insomnia preventing Windows 7 sleep mode

I’ve been researching power management in SCCM (reporting and configurations) and came across an interesting problem/resolution that I’d like to share.

In SCCM reports, if you run the Insomnia Report (Reports\Power Management\Power Management – Insomnia Report) against your main workstations collection (choose 30 days), you may notice that a high percentage of your workstations are prevented from sleeping by a process listed as “rdbss”.

For example in this report 166 devices were found that experienced this issue in the last 30 days.

At another location we had 50% (~250+) of our workstation and at another barely any (go figure). Investigating this further I discovered that Windows 7 will by default fail to enter sleep mode if it sees that a network file is open. This issue has been resolved in Windows 8.

I found a group policy modification to correct this behavior and allow sleep mode regardless, thus preventing the “rdbss” condition;

After making this modification to our workstations and rerunning the insomnia report a week later (limited to 7 days) we’re down to only a handful of computers still suffering from “rdbss”.

With the new group policy setting in place this has resulted in massive energy savings. As you can see below, running the Energy Consumption by Day report, we've realized at minimum a 75% decrease in power usage since implementation. That equates to approximately a $28,000 energy savings per year at one site.

 Here's a snapshot before the modification, using the Computer Activity Report in SCCM. Here you can see the computer "on" state in relation to daily usage. It's apparent something is wrong here.

Here's post setting change. This looks much better.

The built in reports in SCCM are priceless.