Watch highlights from the VMworld Conference in Cannes, France (February 2009).
Tuesday, 30 June 2009
In this video, you'll see how a multi-tiered software solution (SugarCRM) can be deployed as an OVF package, how it is customized during deployment, and how it shows up in the vCenter inventory as a vApp icon. The installation experience is customized by the meta-data contained in the OVF package.
Monday, 29 June 2009
I just received a copy of Edward’s new book “VMware vSphere and Virtual Infrastructure Security: Securing the Virtual Environment”. This book reflects the same hands-on approach that made Haletky’s VMware ESX Server in the Enterprise so popular with working professionals. Haletky doesn’t just reveal where you might be vulnerable; he tells you exactly what to do and how to reconfigure your infrastructure to address the problem.
VMware vSphere and Virtual Infrastructure Security begins by reviewing basic server vulnerabilities and explaining how security differs on VMware virtual servers and related products. Next, Haletky drills deep into the key components of a VMware installation, identifying both real and theoretical exploits, and introducing effective countermeasures.
It’s prepping time this week. I’m working my way through the new vSphere 4 ICM instructor guide. Module 11 is fun, I was very curious about the VMware Data Recovery lab. I completed this lab once before at the VMworld 2008 in Cannes together with my blog friend Duncan Epping. I remember the beta worked straight forward, but when I tried to add destination back-up storage in my home lab, I ran into trouble.
The destination storage can be a VMFS datastore, an NFS datastore or a CIFS share. Since I’m using the StorCenter ix2 as CIFS and NFS server, I wanted to add a CIFS network share. Be sure to use the IP address of your CIFS server, the DNS name won’t work. One other thing, if you encounter a "Failed to create snapshot for vCenter, error -3948 ( vcb api exception)" error, keep in mind that for the "3948 ( vcb api exception)" error, you ensure that your appliance is capable of resolving the hostname of your ESX server.
- Network Destinations Must Be specified Using IP Addresses
Using DNS-resolved names to specify network destinations is not supported with Data Recovery. When adding network destinations using Configure > Destinations, enter an IP address. For example, use \\192.0.2.12\share rather than \\example\share.
- Non-English Characters Are not Supported with Network Shares
If a network share name, user name, or password contain non-English characters, attempts to add the network share fail. To avoid this issue, use English characters for share names, user names, and passwords.