Veeam is once again blessing the community with their generous holiday spirit, which of course includes gifts! Veeam recently launched version 6 of their flagship Backup and Replication product which now includes support for Microsoft Hyper-V. Those who are heavily active in the Microsoft and/or VMware community and formally recognized as such, are eligible to register for their free gift from Veeam – NFR licensing for Backup and Replication v6.
I will attest that I’ve been using Veeam Backup & Replication to protect valuable data in my home lab for a few years and I’ve had to rely on it for recovery more than once. I also included it as a backup and disaster recovery replication solution in my VCDX design submission which I successfully defended in February 2010.
Below you’ll find two promotions for redeeming the NFR licenses. First is the Hyper-V promotion for MVPs, MCPs, and MCTSs, followed by the VMware promotion for vEXPERTs, VCPs, VCIs, and registered VMUG members (remember, anyone can be a registered VMUG member, it’s free to sign up, so why not do it today?)
Free NFR license for
Veeam Backup & Replication v6 for Hyper-V
Get this holiday gift from Veeam!
If you are a Microsoft Certified Professional (MCP), Microsoft Certified Technology Specialist (MCTS) or a Most Valuable Professional (MVP), you can get a FREE 2-socket NFR* license for Veeam Backup & Replication v6 for your home or work lab.
*An NFR (Not for Resale) license can only be used for evaluation or demonstration purposes. Read EULA for more details.
Free NFR license for
Veeam Backup & Replication v6 for vSphere
Get this holiday gift from Veeam!
If you are a VMware vExpert, VMware Certified Professional (VCP), VMware Certified Instructor (VCI) or VMware User Group (VMUG) member, you can get a FREE 2-socket NFR* license for Veeam Backup & Replication v6 for your home or work lab.
In this round, the vCD cell stopped working properly (single cell server environment). I could log into the vCD provider and organization portals but the deployment of vApps would run for an abnormally long time and then fail after 20 minutes with one of the resulting failure messages being Failed to receive status for task.
Doing some digging in the environment I found a few problems.
Problem #1: None of the cells have a vCenter proxy service running on the cell server.
Problem #2: Performing a Reconnect on the vCenter Server object resulted in Error performing operation and Unable to find the cell running this listener.
I search the Community Forums, talked with Chris Colotti (read his blog) for a bit, and then opened an SR with VMware support. VMware sent me a procedure along with a script to run on the Microsoft SQL Server:
BACKUP the entire SQL Database.
Stop all cells. (service vmware-vcd stop)
Run the attached reset_qrtz_tables_sql_database.sql
– shutdown all cells before executing
delete from qrtz_scheduler_state
delete from qrtz_fired_triggers
delete from qrtz_paused_trigger_grps
delete from qrtz_calendars
delete from qrtz_trigger_listeners
delete from qrtz_blob_triggers
delete from qrtz_cron_triggers
delete from qrtz_simple_triggers
delete from qrtz_triggers
delete from qrtz_job_listeners
delete from qrtz_job_details
Start one cell and verify if issue is resolved. (service vmware-vcd start)
Start the remaining cells.
Before running the script I knew I had to make a few modifications to select the vCloud database first.
When running the script, it failed due to case sensitivity with respect to the table names. Upon installation, vCD creates all tables with upper case names. When the MS SQL Server database was first created by yours truly, case sensitivity, along with accent sensitivity, were enabled with COLLATE Latin1_General_CS_AS which comes straight from page 17 of the vCloud Director Installation and Configuration Guide.
After fixing the script, it looked like this:
– shutdown all cells before executing
delete from QRTZ_SCHEDULER_STATE
delete from QRTZ_FIRED_TRIGGERS
delete from QRTZ_PAUSED_TRIGGER_GRPS
delete from QRTZ_CALENDARS
delete from QRTZ_TRIGGER_LISTENERS
delete from QRTZ_BLOB_TRIGGERS
delete from QRTZ_CRON_TRIGGERS
delete from QRTZ_SIMPLE_TRIGGERS
delete from QRTZ_TRIGGERS
delete from QRTZ_JOB_LISTENERS
delete from QRTZ_JOB_DETAILS
The script ran successfully wiping out all rows in each of the named tables. A little sidebar discussion here.. I talked with @sqlchicken (Jorge Segarra, read his blog here) about the delete from statements in the script. It is sometimes a best practice to use the truncate table statement instead so that the transaction logs are bypassed instead of using the delete from statement which is more resource intensive due to the row by row deletion method and the rows being recorded in the transaction logs. Thank you for that insight Jorge! More on MS SQL Delete vs Truncate here. Jorge was also kind enough to provide a link on the subject matter but credentials will be required to view the content.
I was now able to restart the vCD cell and my problems were gone. Everything was working again. All errors have vanished. I thanked the VMware support staff and then tried to gain a little bit more information about how the problem was resolved by deleting table rows and what exactly are the qrtz tables? I had looked at the table rows myself before they were deleted and the information in there didn’t make a lot of sense to me (but that doesn’t necessarily classify it as transient data). This is what he had to say:
These [vCenter Proxy Service] issues are usually caused by a disconnect from the database, causing the tables to become stale. vCD constantly needs the ability to write to the database and when it cannot, the cell ends up in a state that is similar to the one that you have seen.
The qrtz tables contain information that controls the coordinator service, and lets it know when the coordinator to be dropped and restarted, for cell to cell fail over to another cell in multi cell enviroment.
When the tables are purged it forces the cell on start up to recheck its status and start the coordinator service. In your situation the cell, due to corrupt records in the table was not allowing this to happen.
So by clearing them forced the cell to recheck and to restart the coordinator.
Good information to know going forward. I’m going to keep this in my back pocket. Or on my blog as it were. Have a great weekend!
If you were at VMworld 2011 US and/or Europe, you may have seen or heard of the posters being given away at the Hands On Labs. Supplies were limited at the US conference and if you attended in Copenhagen maybe you didn’t get a chance to get into the labs to grab some posters.
Although VMworld is over, you still have access to the posters.
One way would be to request a Dell Compellent Executive Briefing with me. I brought a few pounds of posters back from Copenhagen and what’s mine is yours if you’re willing to listen to me talk about the great integration points Dell Compellent Storage Center has with VMware’s growing portfolio.
The other option would be to go online and grab a copy of the posters which you can view electronically or have printed at your local copier shop. This blog post was inspired by Xtravirt email bulletin 94 – thanks for pulling together the links guys.
I don’t publish the majority of the press releases which make their way to my inbox but I took a quick look at HotLink SuperVISOR for VMware and what it does is interesting. Watch the video below (feel free to expand to full screen to see the detail) and see how this product is able to pull in various Type 1 hypervisors in a heterogeneous datacenter under the vCenter management umbrella. By now you know VMware isn’t the only player in the hypervisor business. VMware’s competitors have been making their presence known. They remain persistent partly because of their gradual market penetration. And I’ll be the first to admit that the other hypervisors out there are the right fit for some business use cases and requirements. Also, multi vendor policies are not uncommon in large organizations. Whatever the reason, deploying different makes and models of hypervisors in an environment is your business. Managing them with ease is HotLink’s business. Read on.
HotLink Launches Latest Version of HotLink SuperVISOR™ for VMware
Leading enterprises including McAfee and BMC Software adopt HotLink SuperVISOR to seamlessly manage mixed hypervisors inside VMware vCenter console
SUNNYVALE, Calif. – December 15, 2011 – HotLink® Corporation, the market leader in transformation solutions for heterogeneous virtualization management, today announced the newest release of its flagship product, HotLink SuperVISOR™ for VMware. HotLink SuperVISOR is the first and only solution to enable VMware vCenter users to natively manage cross-platform virtual infrastructure spanning Citrix XenServer, Microsoft Hyper-V, and Red Hat Enterprise Linux (KVM). The latest release, HotLink SuperVISOR for VMware 1.2, adds new capabilities focused on enterprise robustness, scalability, configuration and management of multi-hypervisors and workloads.
With its latest release, HotLink customers benefit from an enhanced virtual integration platform that provides total control and performance visibility across all enterprise hypervisors, using the VMware vCenter management console they already have. The new features of HotLink SuperVISOR for VMware 1.2 include:
Enhanced Networking Configuration – Users can now provision and modify virtual switches and network adapters from VMware vCenter and associate these to any enterprise hypervisor —enabling users to manage heterogeneous virtual networking from a single interface.
Expanded Performance Monitoring – The latest release expands the heterogeneous performance statistics and alerts that are gathered and displayed inside the native VMware vCenter performance tab —allowing administrators to quickly identify issues across the mixed hypervisor environment.
Robust Configuration of Virtual Machine Settings – Only HotLink provides the ability to modify the configuration of virtual machine settings such as virtual CPUs and memory assignments natively inside vCenter and apply across all virtual platforms —ensuring the optimum VM configuration regardless of the hypervisor.
“Enterprise IT needs are rapidly evolving as an increasing number of VMware shops are deploying heterogeneous hypervisor environments. Administrators need a single management console that provides a comprehensive view and complete control of all enterprise workloads,” said Lynn LeBlanc, CEO and founder of HotLink. “The latest enhancements to HotLink SuperVISOR extend the VMware vCenter management infrastructure to provide sophisticated and robust management capabilities to Hyper-V, XenServer and KVM – unifying the management of all virtual workloads inside VMware vCenter.”
As virtual infrastructure deployments expand and mature, heterogeneity is being fueled by a combination of economics and maturing of hypervisor alternatives. The most recent Gartner Magic Quadrant for x86 Server Virtualization Infrastructure report included, for the first time, both Citrix and Microsoft alongside VMware in the leaders quadrant. Moreover, Hyper-V grew 62 percent last year compared to ESX’s 21 percent growth and Citrix’s 25 percent, according to IDC. While the proliferation of multiple virtual platforms is accelerating, streamlined infrastructure is needed to unify management. That’s exactly what the latest release of HotLink SuperVISOR for VMware addresses.
“McAfee historically was an all VMware shop, but our business needs have changed so that we now have a mix of vSphere, Hyper-V and XenServer. Utilizing HotLink SuperVISOR for VMware across our virtual environment enables us to increase our usage of other hypervisor platforms while unifying management. By deploying multiple hypervisors and standardizing on VMware vCenter as our primary management interface, we expect to reduce our virtualization cost by over 50 percent and admin costs by 65 percent over the next 3 years,” said Mark Tonnesen, CIO of McAfee. “The foundation of our multi-hypervisor environment is built on the HotLink SuperVISOR platform.”
With the new HotLink SuperVISOR technology, enterprises can tier their virtual infrastructure with cost-effective hypervisors and still unify the management, significantly reducing their licensing and operating costs. With HotLink SuperVISOR, customers can realize the benefits of mixed hypervisors while avoiding overly complicated management systems.
“Like many other IT shops, we are investigating the use of multiple hypervisors to cost effectively support development and test activities for our Tier 2 and Tier 3 business applications. We have been very impressed by HotLink’s SuperVISOR technology and the hypervisor interoperability that it enables. We believe that HotLink will enable us to optimize the use of specific hypervisors for individual workloads without compromising our ability to manage our overall virtual environment,” said Mark Settle, CIO of BMC Software.
Founded in early 2010 by data center software veterans and the founders of FastScale Technology, Inc. (acquired by VMware), HotLink Corporation is on a mission to transform real-world IT with the first true heterogeneous data center system management platform for virtual, cloud and physical computing infrastructure. Early customers include enterprise IT organizations spanning technology, financial services, telecommunications and Internet search. HotLink’s advisory board includes visionary leaders from Informatica, Facebook, E*TRADE, Clorox, Citrix, BMC and Flextronics. HotLink is a privately held, venture capital backed company based in Sunnyvale, California. For more information, visit www.hotlink.com.
I’ve gone a few rounds with VMware vCloud Director in as many weeks recently. I’ve got an upcoming blog post on a vCenter Proxy Service issue I’ve been dealing with but until I collect the remaining details on that, I thought I’d point out VMware KB 1026312 Collecting diagnostic information for VMware vCloud Director. This knowledge base article details the steps required to collect the necessary support logs for both vCD versions 1.0 and 1.5.
The vmware-vcd-support script collects host log information as well as these vCloud Director logs. The script is located in the following folders:
For vCloud Director 1.0, run /opt/vmware/cloud-director/bin/vmware-vcd-support
For vCloud Director 1.5, run /opt/vmware/vcloud-director/bin/vmware-vcd-support
Once executed, the script will bundle the following log files from /opt/vmware/vcloud-director/logs/ into a .tgz tarball saving it in the directory from which the script was run (providing there is enough storage available):
cell.log – Console output from the vCloud Director cell.
diagnostics.log – Cell diagnostics log. This file is empty unless diagnostics logging is enabled in the local logging configuration.
vcloud-container-info.log – Informational log messages from the cell. This log also shows warnings or errors encountered by the cell.
vcloud-container-debug.log – Debug-level log messages from the cell.
vcloud-vmware-watchdog.log – Informational log messages from the cell watchdog. It records when the cell crashes, is restarted, etc.
On the subject of vCD log files, also mentioned in the KB article is VMware KB 1026815 Configuring logging for VMware vCloud Director. The information in this article is useful for specifying the quantity and size of vCD log files to be maintained on the cell server.
Once the log files have been collected, you may analyze them offline or upload them to VMware’s FTP site in association with an SR by following VMware KB 1008525 Uploading diagnostic information to VMware.
Cody Bunch over at ProfessionalVMware has pulled together a whole bunch of fantastic lab resources which he plans to give away to one lucky contest winner at the BrownBag Blow Out – vSphere Lab Give Away. This is a great opportunity to walk away with books, videos, 1×1 VCAP training, storage, laptop PC, VMware Workstation, VMware exam vouchers, a brand new v3 vCalendar from you-know-who, and maybe more (I hear Cody has a book coming…)
1) Create and send a 1 – 3 minute video, explaining who you are and how you think the lab would help you.
2) Shipping to US addresses only.
3) Employees of prize vendors and Cody’s tight friends are ineligible.
4) Entries must be received by midnight 12/13.
5) Winner will be announced between 12/14 and 12/16.
6) The very best of luck to all contestants and may the luckiest and most deserving person win. If you sue Cody or cause trouble for him you will be the biggest loser.
For the Twitter folks… (The Real) Mostafa Khalil (@MostafaVMW, VCDX #2) is now on Twitter. I’d recommend following him as there are some amazing changes brewing on the vSphere storage horizon. Hopefully he’ll privilege us on a semi regular basis with bits from his great storage mind.
For the non Twitter folks… Seven days ago, Mostafa posted the picture shown below. It’s the Getting Started Guide for VMware Workstation 1.0 for Linux. It comes to us from the year 1999.
Seeing this is enough to make a vEvangelist tear up. I’d love to get my hands on this product at some point and take it for a spin. Perhaps I’ll have a chance if the VMTN Subscription makes its return. My VMware journey didn’t start until a year later with Workstation 2.0.2 for Windows. Look at the file size – 5MB.