2,187
edits
Difference between revisions of "Script Extracts and Examples (PowerCLI)"
Jump to navigation
Jump to search
Script Extracts and Examples (PowerCLI) (view source)
Revision as of 11:16, 24 December 2010
, 11:16, 24 December 2010→VM's with Snapshots Running: Updated for Get-Snapshot size bug
(→Script Extracts: Added "ESX BIOS, NIC and HBA Driver Versions") |
(→VM's with Snapshots Running: Updated for Get-Snapshot size bug) |
||
| Line 449: | Line 449: | ||
=== VM's with Snapshots Running === | === VM's with Snapshots Running === | ||
Be aware that there's a bug in the way <code>Get-Snapshot</code> handles VM's in VI4, in that for the snapshot size it tends to report the maximum size a snapshot file could become, not the actual size that it is. As a result there is a workaround to found here - http://blogs.vmware.com/vipowershell/2010/09/snapshot-size.html. I've found that this reports smaller sizes for VI3 snapshots as well (which match the actual disk usage in the few occasions I've bothered to check). | |||
<source lang="powershell"> | <source lang="powershell"> | ||
| Line 523: | Line 524: | ||
Log "Completed!" | Log "Completed!" | ||
</source> | </source> | ||
To implement the <code>Get-Snapshot</code> size bug, download the workaround file from the link above. I've placed it in a sub-folder called <code>lib</code>, hence I've included it into my main script by using... | |||
<source lang="powershell"> | |||
. .\lib\getsnapshotsize-1.ps1 | |||
</source> | |||
...then I've just replaced <code>Get-Snapshot</code> with <code>CalculateVMSnapshotsSizeMB</code> | |||
=== VM's Effective CPU Shares === | === VM's Effective CPU Shares === | ||