It is not new that VMware vCenter Server Appliance (VCSA) is a very popular option, especially for small businesses which can save money on an additional Windows Server license. It is a prepackaged and preconfigured virtual appliance with PostgreSQL database, vCenter server 6.5 components and also (in case you deploy “all-in-one” VM) Platform services Controller that contain all of the necessary services for running vCenter Server such as vCenter Single Sign-On, License service, and VMware Certificate Authority.

It is quite surprising how many companies migrate virtual workload nowadays. There could be different reasons – expiring contract with the service provider, move to the new office, consolidation of resources to minimize Capex and Opex, but in every case, companies need efficient and flexible V2V migration solution. Very often people think of migration in terms of moving data from one place to another. However, migration is much more than that. For instance, you would probably want VMs to keep the same IP addresses after the migration. Which means you need to consider stretching VLANs between the source and target locations in case you cannot migrate all VMs in particular subnet in one go. You must plan a network cutover too.

Veeam Backup Entreprise Manager is an optional component that enables to consolidate several Veeam Backup & Replication server through a single pane of glass. Veeam Backup Enterprise Manager provides a web-based interface to centrally control and manage all jobs. You can edit job, monitor them and have a consolidated view of the reporting of all Veeam Backup & Replication server. In this topic, we’ll see how to configure Veeam Backup Enterprise Manager.

In the previous topics, we have installed and updated Veeam B&R 9.5. Then we have connected Veeam to vCenter 6.5 to get visibility on VMware VM and backup them. To finish, we have added a backup repository to store backup files. Now we can backup a virtual machine. Once we have some restore points, we can also recover the VM.

In Part II we will review the remaining improvements in vSphere Availability and Resource Management brought by vSphere 6.5.

In the previous topic, we have seen how to install and update Veeam Backup & Replication 9.5. In this topic, we will prepare the environment. We will connect to vCenter to be able to backup virtual machines and we will add a backup repository. In my lab environment, I have deployed a vCenter Server Appliance 6.5 (VCSA). The VCSA FQDN is admin.vsphere.lab.

As many admins of virtual infrastructures know, for the first time ever, VMware vSphere 6.5 received the long awaited encryption feature of both virtual disks content and vMotion hot migrations. The VMs encryption works based on AES-NI algorithm, and the key management is carried out based on KMIP 1.1 standard. When I/O operation comes to the disk of the virtual machine, it is immediately encrypted on-the-fly, which provides complete security against data security attack.

Capacity planning is one of the tasks that every IT organization need to do, but most do very poorly. This is not out of bad will or lack of skills. Most often, it is because they lack a good way of dealing with all the changes, past, present and future. Most of them are also done reactively. Statistics may be pulled from vCenter and put into word or excel where graphs of past data points from a historical trend. This is then used to predict the future growth and based there of cluster sizing and purchasing decisions are made. Alternatively, the all too familiar, “we are out of resources. Hurry we need to buy more”, scenario comes into play. None of these capacity technics are very good. There is most properly a need to do things smarter.

VMware vSphere 6.5 has been released few weeks back and many users would like to hit the upgrade button. Not so fast. In this post I’ll talk a little bit about what to consider before upgrading to vSphere 6.5. One of the good news is that there are no new license keys needed for vSphere 6.5 so if you’re currently on vSphere 6.0 you don’t need to enter new license keys.