I just spent a very useful week looking at how our customers might be able to protect vCenter Operations Manager (vCops) with VMware’s vSphere Replication (vR) and Site Recovery Manager (SRM) products. It was quite tricky to get this to work, if I’m perfectly honest, but that was the whole point of the exercise. What we learnt is being fed back to the various business units within VMware, to see if we can make this more intuitive and less complex to achieve, but if you are interested in knowing how to configure your DR infrastructure to protect vCops, please read on.
Last year I published a list of storage vendors and partners that I was planning to check out at VMworld 2013. This year is no different, with a number of new arrivals on the storage scene, as well as some super new cool products from many of VMware’s partners. Whilst this is no means a definitive list of what’s on show, these are the ones that I am particularly interested in checking out this year.
A week or so ago, Duncan & I were given 4 e-book vouchers each from VMware Press for the Essential VSAN book. We decided that the easiest thing to do was to hold a competition to give-away the vouchers. We asked via twitter to give us a reason why you deserved the e-book, using the #essentialvirtualsan hash-tag. The best 8 tweets (and the ones which made us laugh) would get the e-book. These are the ones we selected:
It’s interesting how a number of conversations tend to pop up around the same issue in a short space of time. I read a very interesting thread from one of our support guys recently about trying to select the correct administrator credentials for the Ruby vSphere Console (RVC). RVC is a command line utility to manage various aspects of vSphere and has been extended to include VSAN functionality. The following day, I saw a thread on the VSAN forums for exactly the same thing – a customer experiencing difficultly logging into RVC on a remote vCenter server as administrator. The bottom line is that the RVC credentials are directly related to the default domain setting in SSO (Single Sign-On). Continue reading
On a recent trip to VMware in Palo Alto, I found some time to visit with a good pal of mine, Vinay Gaonkar, who is now the Product Manager for XtremIO over at EMC. Vinay used to be a storage PM at VMware (he worked on the initial phases of VVols), and we worked together on a number of storage items in various vSphere releases. It’s been almost 2 years since I last spoke to the XtremIO folks (VMworld 2012 in fact, when the product still had not become generally available), so I thought that this would be a good time to catch up with them, as we are in the run up to VMworld 2014.
I’ve done a few posts in the past which discuss the VM Home Namespace object. To recap, the VM Home Namespace is where we store all the virtual machine configuration files, such as the .vmx, .log, digest files, memory snapshots, etc. I also highlighted that the VM Home Namespace is limited to 255GB in size. This led one reader to raise the following observation:
It means that it is not possible to do a snapshot with memory for a VM with 256 GB of RAM.
This is indeed correct. If you attempt to snapshot a VM (with memory) that has a memory configuration that does not fit into the VM Home Namespace (in this case I created a VM with 256 GB of memory), you will hit the following “insufficient disk space on datastore” error:
Are there any plans to decrease VM Home Namespace?
I can’t say too much about futures at this point, but what I can say is that the issue is recognised, and we certainly plan to address it going forward. However, in the meantime, if you have VMs with large memory requirements, and you wish to be able to snapshot those VMs along with the memory, be cognizant of this restriction.
Because of that, Duncan and I decided we will give away 4 e-books each. If you want to win one then please let us know why you feel you deserve to win a copy using the hashtag #essentialvirtualsan on twitter.
Duncan and I will decide which 8 tweets will win an eBook, and of course we will favor the ones that make us laugh – it’s as simple as that!
So just to be clear:
- Tweet why you think you deserve the book
- Use the hashtag #essentialvirtualsan
- Be funny!
The 8 winners will be announced Friday, August 8th, 2014.