I love creative and challenging projects in the emerging technology product space. I have a background in tech, innovation, and product development, especially as applied to web and mobile apps in the entrepreneurship arena, but have recently moved into marketing. In my role as a product marketer, I have gravitated toward digital marketing as well as analytics/data mining. It fits well with my techie geek bent as well as my cloud angle on The Backup Window. (Be sure to catch my posts on Innovation Station too!) Outside of work at EMC, I enjoy exploring Boston’s culinary and jazz scene (often in combination), and travel as much as I can (35 countries and counting).
“You are the master of your destiny. You can influence, direct, and control your own environment.”
–Quote from Napoleon Hill, Think and Grow Rich
Napoleon Hill is considered to be one of the greatest writers on success in history. And, while this quote is specifically related to one’s ability to achieve high levels of personal success, the sentiment behind it is also a basic premise for the new VMware support announced as part of the enhancements to the EMC Data Protection Suite.
To remain agile and flexible, data owners—in this case, VMware Administrators—have moved to their own processes and tools for protecting their environments. This has contributed to the ‘accidental architecture’ discussed in Stephen Manley’s blogs. This movement disenfranchises the backup team, making it impossible for them to ensure SLAs at a corporate level.
EMC recognizes this need and is addressing it through the Protection Storage Architecture. The Protection Storage Architecture enables an open and modular approach to data protection that, among other benefits, provides visibility and control for data owners, while also enabling IT to move closer to an ITaaS model. There is almost no better example of what we are delivering than the tight integration with VMware vCenter™ engineered into both Avamar 7 and NetWorker 8.1.
Effectively, through the enhancements to VMware protection in both solutions, VMware administrators have the ability to choose the policies, as set by IT, that best fits the vm’s or vm containers in their environment and apply them. Further, they are using their own native tool, the vSphere Web Client, for the administration. From the vSphere Web Client, via the EMC Backup and Recovery plug-in, they are also able to process image backup and recovery and run reports, among other activities. Alternatively, backup administrators set corporate policy from their native UI and have the visibility to monitor and report on the corporate infrastructure. Finally, the EMC Data Protection Restore Client web user interface enables any system administrator with privileges to run file level recoveries from the image backups.
You can see how the tight integration with VMware vCenter in NetWorker 8.1 and Avamar 7 offers a best-of-both-worlds scenario and enables each administrator to literally be the master of their environment. We invite you to watch the demo of how this works in NetWorker 8.1. Or, if you prefer to read about the capabilities, please take a look at the complete Solution Overview.
Our Backup to the Future launch event was awesome. More than 23,500 of you (and counting) have viewed the event since July 10, and many of you have asked questions of our experts.
And what’s great is that all the products we announced, including the new midrange Data Domain Systems and the updates to EMC Data Protection Suite (Avamar 7, NetWorker 8.1) will be available with VSPEX Proven Infrastructures this quarter.
Why is this important?
EMC backup supercharges the VSPEX value prop. You’ll be able to complete backups within windows (up to 90% less time required) and data will be recoverable (via our Data Invulnerability Architecture).
Without backup as a bottleneck (or worry), you’ll have the confidence to go full speed with virtualization – and do more. More virtualization… more app rollouts… more IT projects that drive revenue. And this means more free time for you. Win-win!
One last thing…
That’s real money that keeps accruing to the bottom line after just two quarters. It’s a backup future anyone can like.
I am fortunate to have two musical children who are both very talented at their respective instruments. When they play or practice alone they are able to control the tempo and volume of the piece independently. However put them with others in an orchestra and suddenly they need to coordinate not only their tempo, but with that of their section and other instruments. This would be impossible without the conductor.
The conductor has visibility to all the scores of music, they are able to bring in and fade out sections of instruments to achieve a perfect balance. Much the same as a backup administrator should be able to do. The backup admin perhaps does not have the individual skill to backup the Oracle Database, or the Exchange Database. Or perhaps does not have the precise tool to backup the virtual servers.
To read the full post on our sister site Thought Feast, click here.
There’s a common operating practice in firefighting called the two-in, two-out rule. It’s a backup plan for firefighters.
Two-in establishes common operating procedures for firefighters inside hazard areas (e.g., firefighters operate must operate in a Buddy System); two-out pairs the inside team with an outside team for additional protection.
For the rule to work, communication between inside and outside teams is critical. Two-in teams have to maintain voice or visual contact with each other at all times, and one person on the two-out team is accountable for its two-in team at all times.
The other member can take on additional responsibilities at the scene but can’t take on tasks that are critical to the safety and health of any other firefighter.
There’s no room for communication gaps. The stakes are too high.
So, what if there was some sort of two-in, two-out rule for IT? What would the rules be? What would the teams look like? How would the rules affect common IT operating practices? What would the effects be on your business?
Over the next few posts, we’ll explore these questions. We’ll look at the communication gap that exists today between IT teams and, importantly, between IT teams and the business, we’ll define the teams and we’ll establish some rules of engagement in and among these teams.
And, lastly, we’ll look at some of the tools (products, architectures, etc.) organizations can leverage to help bridge some of gaps within their organizations.
Why do this? That’s simple: Transformation is going to happen with or without you.
So, who’s got your back?