Like everyone else, I have been reviewing the Release Notes for the latest Update 1 release of vSphere 4.1, but I decided to point out specific fixes that will make full image VM backups better for everyone. Note that I work for Veeam Software, but the fixes I am referring to are all VMware resolved issues that surface from time to no matter what backup solution you use. There are numerous other fixes and impovements in the U1 release, but, since most of my world is backup these days, these particular items â€œpopped outâ€ at me.
I am in Seattle, WA for the third GestaltIT Tech Field Day (TFD). This time I am part of the presenting team for Veeam Software, and we are first up on the agenda. As with other recent events, I am using Cover It Live (CiL) to provide real time coverage and of our presentation and the reaction of the delegates (bloggers) attending. The best part about using Cover It Live is the event can be played back in the future, so check it out even if you missed it live.
A scenario involving reverting to an ESX snapshot can result in corrupted incremental backups when using vSphereâ€™s Change Block Tracking (CBT). In summary, â€œthere is a major issue with the way VMware handles the indexing of the ChangeID.â€
It has to be the most common question for those implementing a new virtual infrastructure (VI)Â – “how do we back up our virtual machines?” There are certainly plenty of choices. A company could stay with the (most commonly found in physical environments) system of agent based tape backups, implement VMware Consolidated Backup (VCB), implement […]
This is no joke. Right now southern Indiana is under water. Some organizations I have worked with are fine but Columbus Regional Hospital and many others arenâ€™t. Their data center was in a basement (which isnâ€™t rare) and took on a surge of water. Within what may have been a few hours, it was completely submerged. They had to evacuate all patients to other area hospitals. Theyâ€™ve got a lot to overcome in the next couple of weeks but with the proper infrastructure, the pain can be lessened.
The question of whether or not to do synchronous or asynchronous replication between storage arrays does not come up often but I suspect it will as more and more people expand their business continuity infrastructure. Itâ€™s an important question because it can have a serious impact on the production environment.
Virtualization is seen as the technology that makes it possible to do more with less, but there are many pitfalls to consider when virtualizing server infrastructure. This article suggests planning decisions to be considered that, if overlooked, could ruin the total cost of ownership (TCO) and the return on on investment (ROI) expected from this virtual infrastructure.
VMware SRM software is just the last piece of the total data center recovery â€œmachineâ€. Many organizations may be seeking the semblance of automated site fail over, but have they really considered in detail what it takes to start up their business critical systems at a secondary location?