VMware snapshots are widely used for different purpose, but the main reason why they exist in vSphere is to help backup programs: using VADP a backup can start a VM snapshot in order to have a frozen file, copy it (or copy only the changed block with CBT and virtual hardware 7 or greater) and then release the snapshot. Other usage are to have a just in point rollback during patches or big changes, but a recommended practice is to release the snapshot as soon as possible. Large snapshots or broken or invalid snapshots are […]
If you are planning an in-place upgrade of a vCenter Server (the Windows installable version) you have to read carefully the vSphere Upgrade Center resources to avoid possible issues. Of course you can choose to install a new vCenter Server instance a move all to the new one. Maybe could be the right moment to switch to the vCenter Server Appliance (there is also a Flings to move your vCenter Windows data to a VCSA instance). But sometimes it’s not possible and should be preferable an in-place upgrade.
If you have installed (or upgraded to) VMware vSphere 6.0 and you still use the old legacy vSphere client you may have some false positives about VM snapshots. All VMs seems to have some snapshots, also if they don’t (and using consolidate does not fix it, because there aren’t snapshots to be fixed). But this apper only with the Windows vSphere Client:
VMware vSphere design is something important for VMware beginner, VMware engineer, VMware SME, or VMware architect. It’s not only related to know well the technologies, but understand how use it in the right way (in the right cases). VMware vSphere Design Essentials is a short book (only 176 pages), but with a good approach for design an IT environment, particularly a VMware vSphere based.
Recently I’ve got a strange issue on ESXi 6.0: after an host reboot the ESXi hosts display a false positive warning: Deprecated VMFS volume(s) found on the host. Please consider upgrading volume(s) to the latest version Starting with vSphere 6.0 the VMFS3 version is now deprecated, but in my case all block based datastores were already at VMFS version 5!
After an upgrade to VMware vSphere 5.5 on a Dell PowerEdge R710, I’ve got strange occasion issues, where the hosts got completly disconnected from vCenter (with the ESXi/ESX host’s status as Not Responding or Disconnected in vCenter Server) and there was no way to reconnect, also after restarting the management services. Locking in the ESXi console those kind of errors where notable: Bootbank cannot be found at path ‘/bootbank’. The only temporally solution was power-off the VMs and restart the host. But the issue can randomly came back.
In previous posts (see ESXi – Partitions layout of system disk and ESXi – More on partitions) I’ve described how are handles the partitions table on the destination installation media of ESXi 5.x (both in the case of a hard disk or a SD/USB disk). With the new ESXi 6.0 the partition tables is similar in the case of a 1 or 2 GB destination device (like a previous SD media), but has some changes in the case of larger devices. Core partitions remain the same with standard size:
Due to the changes in the new vCenter Server 6.0 architecture, the SSO has now been incorporated in the new VMware Platform Services Controller “role”. But the concepts of a global SSO accounts still exist and remain important to manage the infrastructure (and more important during installation and upgrade). If you forget the SSO admin password you can have some trouble. I’ve already wrote on how reset the VMware SSO password in the vSphere 5.1 and 5.5 versions and the procedure remain almost the same also in the 6.0 version.
In previous post we have already see how add custom drivers to an ESXi installation ISO and how use ImageBuilder to make custom ESXi ISO, but in other cases you may need to define some custom settings during the installation or add custom vib files. Booting from CD is not the only way, but custom ISO could be used also for boot from USB or for boot from virtual devices (like the iDRAC or ILOE). In case you need to build custom ISO with custom option this post could help you: How to Create Bootable ESXi […]
Compatibility remain one of major reason for wait before a major upgrade, but now several backup products are compatible with vSphere 6.0 (see Backup products and vSphere 6.0 compatibility – Updated). Same for several other 3rd part software. But in the backup space there are still some issues that may limiting the choice of running (yet) vSphere 6.0 in production environments. As written in VMware vSphere 6.0 – Upgrade or not upgrade post one was related in CBT in ESXi 6.0 that can impact your environment also if your backup program will already support vSphere […]
Also some months after the release the new vSphere 6.0, one of the main reason to don’t use in a production environment remain the compatibility aspect. If most of the VMware products it’s fine from this point, it isn’t the same for the 3rd part backup products. One month ago I’ve wrote a post Backup products and vSphere 6.0 compatibility were only few products were available. Now there are some changes in this list.