• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • Unexplored Territory Podcast
  • HA Deepdive
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

Storage

vStorage

Duncan Epping · Sep 16, 2008 ·

Chad just wrote an amazing article about what vStorage actually is. Besure to read this one!

vStorage has been something that VMware and EMC have been working together on for a long time, in fact, before it was called vStorage (which was recent) – it used to be called VMAS a name only engineers would like.  In fact, we’ve been working on this from almost right after the original acquisition before the program even existed formally.

VMware’s first announcements.

Duncan Epping · Sep 15, 2008 ·

Here it is, VMware’s first announcement this week:

A Virtual Datacenter Operating System is characterized by hardware and location independent applications, service level contracts between the infrastructure and applications and a shared, dynamic infrastructure.

vCenter provides comprehensive management of applications and infrastructure in this flexible, fluid environment and integrates with leading systems management vendors for seamless, end to end datacenter management.

VMware Infrastructure delivers the virtual datacenter OS through the following essential components:

  • Application vServices guarantee the appropriate levels of availability, security and scalability to all applications independent of hardware and location.
  • Infrastructure vServices subtract, aggregate and allocate on-premise servers, storage and network for maximum infrastructure efficiency.
  • Cloud vServices federate the on-premise infrastructure with third party cloud infrastructure.
  • Management vServices allow you to proactively manage the virtual datacenter OS and the applications running on it.

I guess everybody was to tired yesterday or still amazed by the Virtual DataCenter that they forgot to blog about the following, which is atleast as important and spectacular as the above,  cause these new features will(2009) be the backbone for the VDC-OS:

  1. Synchronization and a single-console view of inventory, configuration, roles and permissions between multiple vCenter instances with vCenter Linked Mode.
    So no more maintaining and configuring several VC’s, just link ’em up!
  2. Monitoring and automated remediation of VMware ESX physical host configurations for compliance with standard baseline profiles.
    This is the future, real plug and play, define your ESX host once and just roll it out! I’m starting to see the big picture with ESXi… no more installing at all, just plug it in!
  3. Paravirtualized storage device enables over 200,000 i/o operations per second.
    High i/o servers? No problem…
  4. Distributed Switch simplifies the setup and change of virtual machine networking.
    A single point of administration for your vSwitches, or should I say dSwitches in this case…
  5. Network VMotion enables network statistics and history to travel with a virtual machine as it moves from host to host for better monitoring and security.
  6. Third party virtual switches plug into virtual networks and deliver value added network monitoring, security and QoS.
    So this would be that Cisco vSwitch that everybody was talking about these last couple of days?
  7. VMware Fault Tolerance, a groundbreaking new product provides zero downtime, zero data loss and availability to all applications against x86 hardware failures without the cost and complexity of hardware or software clustering solutions.
    No more need for any  other way of clustering, zero data loss, no more down time!
  8. vStorage Thin Provisioning enables users to reduce storage required for virtual environments by up to 50% by allocating storage only as required while providing the reporting and alerting capabilities needed to track actual usage.
    Besides power, rack space and cooling, save on storage as well!
  9. vStorage Linked Clones reduce the storage required for virtual machines by sharing common OS images while still retaining user specific profile and application data.
    Think about rapid deploying a 1000 VDI desktops… and saving on disk space.
  10. Virtual machines increase in size from 4 way to 8 way SMP, from 64 GB to 256GB of RAM, enabling even the largest, most resource intensive applications to run on  VMware.
  11. Hot add of virtual CPU, memory and network devices enables applications to scale seamlessly without disruption or downtime.
    No more downtime.
  12. vCenter Data Recovery provides quick, simple and cost effective backup and recovery for all applications through:
    Agentless disk based back up and recovery of virtual machines, Incremental backups and dedupe to save disk space, vCenter – integrated virtual machine level or file level restore.
    Doing backups and restores from the same console you are already used to, VirtualCenter!
  13. vApp turns new and existing applications into self-describing and self-managing entities. vApp leverages OVF, an open industry standard, to specify and encapsulate all components of a multi-tier application as well as the operational policies and service levels associated with it. Just like the UPC bar code contains all information about a product, the vApp gives application owners a standard way to describe operational policies for an application which the Virtual Datacenter OS can automatically interpret and execute.

What more can I say than “WOW”! Oh, and another thing… it seems like there’s a rebranding going on: vCenter, vStorage, vApp, vServices.

So with ESXi, host profiles and dSwitches there’s no need to spend a lot of time on configuring. Figure it out once, and just apply it to the rest of the hosts! With hot add CPU, MEM, Networkand with VMotion and Fault Tolerance there’s no need for down time any more. And I’m not even talking about doing backups and restores from within your vCenter and all the cool new storage related features…

Read more @ Scott Lowe, PCWorld, ComputerWorld, VMETC.Com, VMware.

VCB errors

Duncan Epping · Sep 3, 2008 ·

I’ve been doing VMware Consolidated Backup troubleshooting for the last couple of days. A customer ran into problems that I can’t comment on at this moment. But after an upgrade of VCB 1.1 to VCB 1.5 the customer ran into a new limitation of VCB. After 30 VM’s the script stopped working, the following error was thrown at us:

‘vcbMounter’ 5648 error] Error: Cannot mount volume 1, service not accepting new devices.

After a few search actions I noticed the following in the documentation which is clearly a new limit in VCB 1.5:

NOTE Consolidated Backup supports a maximum of 60 concurrently mounted virtual machines. For example, you can concurrently mount 60 virtual machines that have a C: drive, or 30 virtual machines that have a C: and a D: each.

In other words, no more than 60 vmdk’s maybe mounted concurrently. This limit wasn’t in 1.1, well not hard coded anyway… but 1.1 still has it’s limitations!

Clearly, on the part of having more than 5 concurrent VCB dumps, I know that this isn’t a best practice but for this customer it’s what they want and need. I stronly advise against it for any environment though! Follow the best practice of a maximum of 5, and set it up in a way that it involves 5 different datastores!

We are currently investigating other options and trying to find out what the max concurrent connections should be within the environment of this specific customer. Taking all kinds of different factors in consideration like “vmfs locking”, “scsi reservations”, stress on the vmkernel and or service console, diskspace occupation combined with fast growing snapshots etc.

I’ve been looking into VMFS locking associated to snapshots. VMFS locking occurs when metadata changes, in other words it happens with one of the following actions: snapshot file growing, vm starting(cause the file is being locked for read/write), file creation etc.

VMFS Locking means that there is only 1 host able to access the VMFS until the lock is released. So you can imagine what happens when there are 5 vm’s on the same VMFS on five different ESX hosts with snapshots that are growing! It will be like a monday morning traffic jam! So please don’t over do it.

I’ve also got the feeling that VCB is probably the most underrated and misunderstood product out there. I’ll be the first to admit that “file level” backups with VCB isn’t always as convenient as it should be but this is also due to the fact that not every Backup vendor has developed a decent integration module. But for instance CommVault Galaxy has got a special agent for VCB file level backups. This agent makes it possible to do a file level backup via VCB and restore direct to the VM via the agent! Check this PDF for more info on their solution. Full Image backups on the other hand are very useful for DR purposes but can also be used to restore single files again. You can mount the VMDK and browse the folders for the file. You can also use Vizioncore’s vRanger or Veeam’s “Veeam Backup” for a third party add-on to VCB. Both products are definitely worth checking out, and are a great extension to an often overlooked product!

Talking about Full Image Level backup’s besure to read this article, it will save you disk space on your “holding tank” and Tape Library!

Practical guide to Business Continuity and Disaster Recovery

Duncan Epping · Aug 13, 2008 ·

VMware released a 232 page PDF titled “A Practical Guide to Business Continuity & Disaster Recovery with VMware Infrastructure”

This VMware® VMbook focuses on business continuity and disaster recovery (BCDR) and is intended to guide the reader through the step-by-step process to set-up a multisite VMware Infrastructure that is capable of supporting BCDR services for designated virtual machines at time of test or during an actual event that necessitated the declaration of a disaster, resulting in the activation of services in a designated BCDR site.

Be sure to pick up this one and read it, it contains a lot of valuable information for every single one of you out there!

File Level Recovery from within a VMDK backup

Duncan Epping · Jul 24, 2008 ·

Today there was a cool article released on the Storage Nuts & Bolts blog. It’s about file level recovery from within a VMDK based on an NFS datastore. NFS is just mentioned cause this is the preferred way to go for the NetApp family, but it doesn’t matter NFS or VMFS the solution they came up with works for the both of them.

This option was recently discovered and further developed (Registry entries and Batch script) by one of the NetApp SE’s (Mike Arndt) and it’s very effective and free for those customers that already have a CIFS license with their NetApp arrays, which is a very large percentage. The other important factor is that Mike has made it a point-and-click process. Great job Mike!!!

As part of their VMware Disk Developer’s Kit, VMware provides a vmware-mount.exe utility that allows for mounting an existing VMDK on a Windows Driver letter. We’ll be using this utility as well to mount the VMDK as well as some Registry Entries and a Batch Script to further simplify the file recovery process.

I don’t to republish the complete article, so visit the blog and use the script and registry settings these guys created. Especially the first option with registry settings, which give you the possibility to mount a VMDK with just a “right click – mount” action is great!

  • « Go to Previous Page
  • Page 1
  • Interim pages omitted …
  • Page 49
  • Page 50
  • Page 51
  • Page 52
  • Page 53
  • Go to Next Page »

Primary Sidebar

About the Author

Duncan Epping is a Chief Technologist and Distinguished Engineering Architect at Broadcom. Besides writing on Yellow-Bricks, Duncan is the co-author of the vSAN Deep Dive and the vSphere Clustering Deep Dive book series. Duncan is also the host of the Unexplored Territory Podcast.

Follow Us

  • X
  • Spotify
  • RSS Feed
  • LinkedIn

Recommended Book(s)

Advertisements




Copyright Yellow-Bricks.com © 2025 · Log in