So I am no scripting master, my PowerShell knowledge is still something I want to expand. During an install last week I had a number of hosts to setup from scratch, so I decided to do this via PowerCLI, as a lot of the tasks were repetitive. Setting up the vSwitch networking and iSCSI configuration for each host
For those of you new to scripting, I’ve included screenshots to accompany the commands so you can see whats going on in the GUI.
Note: the full code without the breaks is at the end of this post
#Setup which host to target
$VMhost = 'hostname'
Continue reading PowerCLI – Setup Host networking and storage ready for ISCSI LUNs
Following on from the recent (November 2015) ESXi 6.0 CBT bug, which has now been fixed in the latest released patch ESXi600-201511401-BG, some further information has come to light, provided by Anton Gostev, of Veeam.
You can read the snippet of important information from the Veeam forum post following the issue (Official Veeam KB2075);
All, we have completed the first day of testing in the same exact lab and using the same heavy write I/O test that made the original issue easily reproducible. After a few TB of increments, the above-mention patch appears to fully resolve the original issue when installed on ESX 6.0 Update 1a build 3073146.
However, we found that simply installing the patch is not sufficient, and CBT reset is required for all of your VMs. This is because existing CBT map files may contain issues created earlier due to the original bug, which may result in inconsistent full backups in future. Having CBT reset will also force the following job run use "full scan" incremental pass, thus fixing any existing inconsistencies in backups and replicas, as discussed earlier in this topic.
Provided CBT reset has been performed, Active Full backups is not required.
Performing Active Full backups by itself cannot be considered as a substitute to CBT reset with this particular CBT issue.
You can either follow the CBT Reset instructions from Veeam or look over to Chris Wahl’s latest blog post “Resetting VMware’s Changed Block Tracking (CBT) File with PowerCLI”.
I wrote about the latest CBT issue (November edition) a couple of days ago, and as promised by VMware a patch has been released.
Original issue – KB 2136854
Patch to resolve the issue – ESXi600-201511001 (2137545)
Note: Before applying this patch on HP Proliant Gen 9 servers, see VMware ESXi 6.0 host fails to detect local disk after patching or applying Update 1 on HP Proliant Gen 9 servers (2120539).
Cheers VMware, lets hope this is the last of the CBT issues!!!
I have currently spent a lot of time visiting different customer sites and working with them to build up a picture of their environment and such. Usually with the aim to provide a design around architectural changes that we would recommend to move their environments forward.
So I thought I’d give a short list of some of my day-to-day tools, this isn’t a comprehensive list, and I spend most of my time working with VMware. So take this with a pinch of salt!
Wera 10000v Screwdriver set – Handy set of screwdrivers, I know most people opt for a multi-driver, but I’ve been on some sites where the cabling and power has been questionable. I wouldn’t say these are the toughest tip drivers around, but I’ve had them a few years and they have lasted.
Continue reading My daily tool kit – IT gadgets and software – #vDM30in30
So here we are again, rounding the year off with yet another change block tracking warning.
I’ve written posts previously on the CBT bugs found in 5.5 and below and those found when vSphere 6.0 was released into the wild.
So whats the issue this time?
Basically it is the same as last time, the wrong sectors of data locations are returned by CBT when requested by your backup software. Meaning it targets the wrong data to backup.
Here is the official VMware KB 2136854. Which describes the following;
When running virtual machine backups which utilize Changed Block Tracking (CBT) in ESXi 6.0, you experience these symptoms:
- The CBT API call QueryDiskChangedAreas() API call can sometimes return incorrect changed sectors, which results in inconsistent incremental virtual machine backups.
- Inconsistent virtual machine backups
All incremental backups which utilize CBT are potentially affected.
Anton Gostev, Veeam, has released a lengthy email to Veeam customers and Gostev lovers stating the following (you can follow the veeam forum post here); Continue reading Yet again, ESXi 6.0, CBT issues #vDM30in30