Notes about interesting problems that I've come across and their solutions. Focused on Virtualization and the accompanying technologies that make it all possible!
2017 vExpert
Get link
Facebook
X
Pinterest
Email
Other Apps
I'm proud to announce that I've been selected as a 2017 vExpert! Thanks for the recognition and congrats to all of the other vExperts, particularly my coworkers Jeff and Dennis!
One of my customers is standardizing the configurations on their HP C7000 enclosures (they've been set up at various sites by various administrators with varying involvement from the architecture team). As such, we need to stand up some temporary resources so that we can take down the main enclosure for reconfiguration. That's fine, we can easily ship a smaller enclosure to each site for temporary compute resources. Some of the sites are using Standard vSwitches, so we need to be able to quickly copy the networking configuration over from their existing blades to these new, slightly different blades. As I see it, we had 2 good options: 1) Capture a Host Profile with the desired vSwitch configuration. Delete every other component of the Host Profile so that only the networking section is applied; design the new ESXi hosts so that the vSwitches'll work with the old vmnic-to-vswitch configurations. 2) Write a script to clone the vSwitch from ones ESXi host...
(8/10/2015) Update: Unfortunately, some backend things have changed since I originally cobbled this script together and it doesn't work any more. I'll fix it if I get the chance, but in the meantime, there's a free utility called RVTools that can identify orphaned VMDK files (which are entertainingly called Zombie VMDKs on the vHealth tab of the application). That's a great application to be aware of anyway, as it makes it very easy to get access to a lot of important information that the vSphere client obscures. (11/9/2015) Update: I went ahead and put together a post detailing how I used RVTools and a helper script to identify, rename and then delete orphaned VMDK files . Every organization has to wrestle with orphaned VMDK files. What is an orphaned VMDK file, you ask? It's a VMDK file that's sitting on your SAN, consuming expensive storage, but isn't actually being used by any VM. They're notoriously hard to find (especially...
1/26/2016 Update: We've learned that this script doesn't elegantly handle the situation where multiple VM folders have the same name (but different parent folders). I've put together a basic script that should help recover from that (in the comments), but I haven't had a chance to thoroughly test it. That script is built to move all VMs from the "Discovered Virtual Machine" Folder back into their correct locations. I'm working on an updated pair of scripts that will handle this whole situation better. 2/9/2016 Update: I've published an updated version of the vCenter Migration Scripts - check it out instead of these! One of my customers wanted to export their VM Folder structure and the associated permissions from one vCenter to another, in preparation for a vCenter forklift. Once the destination vCenter was fully prepared, the goal would be to migrate ESXi hosts with VMs into the new vCenter, then move the VMs into the appropriate folders....
Comments
Post a Comment
Sorry guys, I've been getting a lot of spam recently, so I've had to turn on comment moderation. I'll do my best to moderate them swiftly after they're submitted,