The vSphere Management Assistant (vMA) runs a 64 bit operating system (RedHat Enterprise Linux) and features the VMware vCLI in addition to vSphere SDK for Perl, Java JRE, CIM vSphere profiles, VMware tools and an SNMP agent. The vMA virtual machine requires a single vCPU with 512MB memory and a 5GB virtual disk. If you are studying for the VCAP-DCA exam then you will need to know how to install and use the vMA to manage a vSphere environment. The best way to learn how to use the vMA is to setup your own home lab. I’ve already posted an article on building a whitebox VMware vSphere server for your home lab (click here), otherwise you can always use VMware Workstation on your PC or laptop.
If you are involved in DR for your organisations IT infrastructure and are replicating virtual machine VMFS datastores then you may be familiar with DisallowSnapshotLUN in ESX 3.x. Let’s start with a background on what these advanced settings are and why they are there.
Since virtualization changed the landscape for disaster recovery some time ago now, most businesses have embraced SAN storage replication for DR (see my other post). This is old news now, but unless your SAN vendor integrates with something like VMware Site Recovery Manager (SRM) then you will have a number of manual tasks involved in your DR recovery process.