Archive for the ‘sqlpass’ Category
VM Replication Is The New P2V (Planning V4DR and V4BC)
Because of the prevalence of virtual infrastructure these days, I’ll make the argument that virtual machine (VM) replication, both for business continuity (BC) and disaster recovery (DR) purposes, is the new P2V (physical to virtual migration) project. Not in the literal migration of physical to virtual, but in the same P2V concepts of infrastructure consolidation and capacity planning. I’m also talking similarity of process and in the frequency in which it is occurring. Simply put, IT shops that performed P2V migrations several years ago are now exploring how they can accomplish their DR site fail over or their BC needs with their virtual machines.
Let’s call these new generation of projects V4DR (virtualization for disaster recovery) or V4BC (virtualization for business continuity).
The comparison
If I rewind 3 to 5 years ago in my career, capacity planning for server consolidation was a weekly project and topic of discussion. Customers were either in the process of converting physical servers to virtual machines or they were exploring the possibility to do so. In both cases, capacity planning scenario spreadsheets and reports were frequent “ground zero documents” to almost every project plan I was involved in.
Just like P2V projects, VM replication today also requires some of the same considerations for job scalability and times to complete – i.e. using multiple hosts as targets and making sure the network can support getting the job done as quick as possible. Not to mention ip addressing, VLAN assignments, and application connectivity after the fact. Thank goodness we no longer have to deal with hardware drivers and other unneeded software a second time. Hopefully, VM alignment is a thing of the past too!
I’m not seeing the same “ground zero documents” for replication projects, however.
Use the same capacity planning tools?
So, I’ll ask the question: Read the rest of this entry »
vSphere 4.1 U1 Released. Fixes Specific For VM Backups
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.
For a great overview of the entire U1 release check out Rick Vanover’s post vSphere 4.1 update 1 released from his Rickatron Blog and via his Servers and Storage Column/Blog at TechRepublic.
The rest of this post contains cut and pastes from the Release Notes and some commentary about them from me. I want to stress again that these are issues that have now been fixed!
Finally, I’ll point out the one huge VM backup issue (that I can think of right now) that still does not appear to be resolved.
Use Event Badge To Repair Broken Backpack Or Luggage Zippers
The average virtualization admin, engineer, manager, and general IT person probably goes to half a dozen events a year where they receive a name badge. I’m just guessing, but at least 2/3 of those event badges are now in the form of a necklace/lanyard. Just guessing again, but I’d be willing to bet that 99% of all the lanyards get thrown away shortly after. That same average IT person probably attends 1 or 2 big events or conferences a year where they are lucky enough to receive a backpack, computer bag, or other schwag with zippers. Unfortunately, the pull tabs on the zippers more than likely will break off leaving an awkward and often painful to pull open/closed zipper head. I’ve stopped using several otherwise very functional bags just for this reason. But, while planning for a recent vacation, an idea so simple struck me that I was amazed I hadn’t thought of it already.
I did not want to take my full computer bag on the vacation. It’s an oversized bag designed for an entire file cabinet and a night’s change of clothes. One of my old backpacks was perfect for my notebook, iPad, magazines, and the various accessories my wife and I would need on the plane and while sightseeing. When I went to grab a backpack in my basement I noticed the nail of badges hanging above them.
For some reason, I can not bring myself to throw away my event badges. I can’t tell you why. I just knew I would do something with them one day. But now I have a new purpose for them, and I am quickly reducing the bulk hanging on that nail. Besides, you never would have seen a headline like “North Georgia Man Saves Family From Burning House With A Linked Lanyard Ladder”, now would you?
So if you are like me you already have what you need to repair your luggage, backpacks, and various other pull zippers around the house. Here’s my quick how to and list of tools needed:
Play #PEX3WORD Win Prizes #PEX2011
What was once just a fun Twitter game (OK, annoying to some) at previous VMware VMworld and Partner Exchange Conferences is now a chance to win real prizes at VMware’s Partner Exchange 2011 (PEX2011) next week in Orlando, FL. Thanks to several vendors and individuals that responded to Kelly Culwell (@kculw) and my last minute requests, if you are an attendee at PEX2011 and play PEX3WORD you can win the following prizes in the following ways:
- EMC Iomega IX2 – awarded to the best #pex3word tweet with a twit pic of Chad Sakac (@sakacc). Chad knows of this requirement to win, but he prefers the twit pic be one where he does not know it is being taken. Chad will help judge the winner. BTW, it doesn’t have to be an actual “twitpic”. Use whatever tweet photo service you want, but just follow the #pex3word game rules.
- VMware Workstation or Fusion - awarded to the most informative or insightful #pex3word tweet. John Troyer (@jtroyer) has thrown these licenses in the pot for the game, and he will help us decide a winner for this category. Use 3 words to express your thoughts during a keynote, breakout session, lab, or just when you experience a general technological epiphany!
- Train Signal vSphere Troubleshooting DVD – awarded to the best / funniest /entertaining #pex3word conversation. David Davis (@davidmdavis) will help us decide the winner from the many series of #pex3word RTs and linked replies. Be sure to adhere to the rules of 3word tweeting! If you don’t know already, the Train Signal series of video training is awesome training to have on your shelf or on your iPod/iPad/iPhone or smartphone, and the latest vSphere Troubleshooting DVD dives even deeper into VMware vSphere management.
- VMware vSphere Design by Forbes Guthrie, Scott Lowe, and Maish Saidel-Keesing. – awarded to the most frequent #pex3word tweeter. Scott Lowe (@scott_lowe) has agreed to ship this winner a copy when the books comes out! By frequent tweets we mean relevant and unique. Tweeting “one two three” a million times for example won’t win you anything, but Scott will ultimately help us decide this winner. No bots or scripts either. To be fair, we are only counting number of tweets between Tues and Thurs during the conference for this award. That way, those showing up early for boot camps and meetings do not have an unfair advantage.
Finally, we have several miscellaneous items such as t-shirts, umbrellas, bottle openers, etc. from Veeam and InterWorks for those #pex3word tweeters that don’t win anything above. This is not the booth swag that anyone can get at the conference, but these items were donated specifically for this game.
How to play and General Game Info
Install Androidx86 in a VMware Workstation VM
I was inspired to try a full install of the Androidx86 OS in a VMware Workstation VM after Eric Sloof created a video of the Androidx86 LiveCD running in a vSphere VM. I’ve documented building the VM and configuring it to run in this post. I also list some navigation tips for getting around inside Androidx86. Finally check out my video of the working VM.
Since most are probably wondering I’ll mention this now, once the VM is connected to the Internet you can download a very limited selection of Apps, but I had sporadic success with the various Apps I tried. For the few that I did get to install, I wasn’t able to get all of them running. So, use an Androidx86 VM as a way to get a feel for what an Android device is like. Maybe it will help you make a decision about buying a Tablet like the Samsung Galaxy Tab.
Browsing the web worked great. I do not test email.
Download, Create New VM, and Install Androidx86 from .ISO
Download the latest revision of the Androidx86 .ISO here:
http://www.androidx86.org/downloads.html
Build a new “typical” VMware Workstation VM (this should work just the same with the free VMware Player), and when you point the install wizard at the Androidx86 .iso the OS type FreeBSD is auto detected. I chose to install the operating system later as I did not want to invoke the auto download of the VMware Tools.
This choice forces you to manually specify FreeBSD from the next screen of the wizard.
I kept the default disk size of 8GB and to chose to store the virtual disk as a single file.
I customized the virtual hardware and did the following
- bumped the RAM to 512 mb. The Workstation wizard suggested 256 mb.
- deleted the floppy
- pointed the vCD/DVD at the Androidx86 .iso and made sure it was connected at power on.
- changed the vNIC to Bridged. NAT should work just fine too. (Note that additional networking changes need to be made later)
Once your ready, boot your new VM and choose to install to harddisk when prompted by the Android Installer.
Replication Bandwidth Calculator From Virtualize Planet
Figuring out whether you can replicate your VMs across your WAN to a DR site is never easy. There are many factors to consider, but luckily, one of my Veeam peers and a fellow VMware vExpert, Ricky El -Qasem has created a Replication Calculator to help figure it out.
From the post on the Virtualize Planet Blog: Replication Bandwidth Calculator | Virtualize Planet
ReplicaCalc
How many times do you get asked “how do I work out if VM Replication will work with my internet link” Well I wanted to demonstrate some way of providing a calculator without working it out in my head every time. So I made a Replication Calculation tool. It is assumed that you provide it with 3 values:
- Average Rate of Change.
- The Link speed – this value should reflect the upload speed at the source site or the download speed at the target if this is less. So for example if the upload at the source is 6Mbs and 10Mbs download at the target then go for 6Mbs
- Bandwidth % – which is the amount of bandwidth as % which achievable from the link speed specified.
Download and install ReplicaCalc from here > ReplicaCalc
Ricky describes the needed values in more detail in his post so be sure to read it all there. He also demonstrates how to use Veeam Backup and Replication to get the VM dynamic rate of change. The tool is useful whether using Veeam to replicate your VMs or not, however.
Thanks Ricky!
For more on this topic, I’ve blogged about using a bandwidth calculator to figure out whether your current WAN link is adequate or not for your replication jobs before.
Consolidate Helper Snapshot Appears On vSphere VM
Your vSphere VMs may be running from snapshots even though you didn’t create them. That is, if a scheduled job which auto creates snapshots runs into a datastore with insufficient free space. In this scenario a special Consolidate Helper snapshot will be created.
The following screenshot shows the mysterious snapshot as I found it on my lab domain controller
In my case, the scheduled job that needs to create and then normally commit the snapshot is a Veeam Backup and Replication job. At some point in the life of my lab I did run out of space, and although it’s not an issue anymore, the snapshot still exists even when the jobs aren’t running! I was a bit surprised that backup jobs could even complete with this snapshot in place.
VMware KB article 1003302 explains that the Consolidate Helper snapshot is actually created when trying to commit (delete all) a snapshot.









