Transcript of a BriefingsDirect podcast from the HP Software Universe Conference in Washington DC on the backing up a growing volume of enterprise data using HP Data Protector.

1. HP Data Protector, a Case Study on Scale and Completeness
for Total Enterprise Data Backup
Transcript of a BriefingsDirect podcast from the HP Software Universe Conference in
Washington DC on the backing up a growing volume of enterprise data using HP Data Protector.
Listen to the podcast. Find it on iTunes/iPod and Podcast.com. Download the transcript. Sponsor:
HP.
Dana Gardner: Hello and welcome to a special BriefingsDirect podcast series
coming to you from the HP Software Universe 2010 Conference in Washington
DC. We're here the week of June 14, 2010 to explore some major enterprise
software and solutions trends and innovations making news across HP's ecosystem
of customers, partners, and developers.
I'm Dana Gardner, Principal Analyst at Interarbor Solutions, and I'll be your host throughout this
series of HP-sponsored Software Universe Live Discussions.
Our topic for this conversation focuses on the challenges and progress in conducting massive and
comprehensive backups of enterprise live data, applications, and systems. We'll take a look at
how HP Data Protector is managing and safeguarding petabytes of storage per week across HP's
next-generation data centers.
The case-study sheds light on how enterprises can consolidate their storage and backup efforts to
improve response and recovery times ,while also reducing total costs.
To learn more about high-performance enterprise scale storage and reliable backup, please join
me in welcoming Lowell Dale, a technical architect in HP's IT organization. Welcome to
BriefingsDirect, Lowell.
Lowell Dale: Thank you Dana.
Gardner: Lowell, tell me a little bit about the challenges that we're now facing. It seems that we
have ever more storage and requirements around compliance and regulations, as well as the need
to cut cost. Maybe you could just paint a picture for me of the environment that your storage and
backup efforts are involved with.
Dale: One of the things that everyone is dealing with these days is pretty common and that's the
growth of data. Although we have a lot of technologies out there that are evolving --
virtualization and the globalization effect with running business and commerce across the globe
-- what we're dealing with on the backup and recovery side is an aggregate amount of data that's
just growing year after year.

2. Some of the things that we're running into are the effects of consolidation. For
example, we end up trying to backup databases that are getting larger and larger.
Some of the applications and servers that consolidate will end up being more of a
challenge for some of the services such as backup and recovery. It's pretty
common across the industry.
In our environment, we're running about 93,000-95,000 backups per week with an
aggregate data volume of about 4 petabytes of backup data and 53,000 run-time
hours. That's about 17,000 servers worth of backup across 14 petabytes of storage.
Gardner: Tell me a bit about applications. Is this a comprehensive portfolio? Do you do triage
and take some apps and not others? How do you manage what to do with them and when?
Slew of applications
Dale: It's pretty much every application that HP's business is run upon. It doesn’t matter if it's
enterprise warehousing or data warehousing or if it's internal things like payroll or
web-facing front-ends like hp.com. It's the whole slew of applications that we
have to manage.
Gardner: Tell me what the majority of these applications consist of.
Dale: Some of the larger data warehouses we have are built upon SAP and Oracle. You've got
SQL databases and Microsoft Exchange. There are all kinds of web front-ends, whether it’s with
Microsoft, IIS, or any type of Apache. There are things like SharePoint Portal Services, of
course, that have database back-ends that we back up as well. Those are just a few that come to
mind.
Gardner: What are the major storage technologies that you are focusing on that you are
directing at this fairly massive and distributed problem?
Dale: The storage technologies are managed across two different teams. We have a storage-
focused team that manages the storage technologies. They're currently using HP Surestore XP
Disk Array and EVA as well. We have our Fibre Channel networks in front of those. In the team
that I work on, we're responsible for the backup and recovery of the data on that storage
infrastructure.
We're using the Virtual Library Systems that HP manufactures as well as the Enterprise System
Libraries (ESL). Those are two predominant storage technologies for getting data to the data
protection pool.
Gardner: One of the other trends, I suppose, nowadays is that backup and recovery cycles are
happening more frequently. Do you have a policy or a certain frequency that you are focused on,
and is that changing?

3. Dale: That's an interesting question, because often times, you'll see some induced behavior. For
example, we back up archive logs for databases, and often, we'll see a large increase in those. As
the volume and transactional growth goes up, you’ll see the transactional log volume and the
archive log volume backups increase, because there's only so much disk space that they can
house those logs in.
You can say the same thing about any transactional type of application, whether it's messaging,
which is Exchange with the database, with transactional logs, SQL, or Oracle.
So, we see an increase in backup frequency around logs to not only mitigate disk space
constraints but to also mitigate our RTO, or RPO I should say, and how much data they can
afford to lose if something should occur like logical corruption or something akin to that.
Gardner: Let's take a step back and focus on the historical lead-up to this current situation. It's
clear that HP has had a lot of mergers and acquisitions over the past 10 years or so. That must
have involved a lot of different systems and a lot of distribution of redundancy. How did you
start working through that to get to a more comprehensive approach that you are now using?
Dale: Well, if I understand your question, you're talking about the effect of us taking on
additional IT in consolidating, or are you talking about from product standpoint as well?
Gardner: No, mostly on your internal efforts. I know there's been a lot of product activities as
well, but let's focus on how you manage your own systems first.
Simplify and reduce
Dale: One of the things that we have to do at the scope or the size that we get to manage is that
we have to simplify and reduce the amount of infrastructure. It’s really the amount of choices
and configurations that are going on in our environment. Obviously, you won't find the complete
set or suite of HP products in the portfolio that we are managing internally. We have to minimize
how many different products we have.
One of the first things we had to do was simplify, so that we could scale to the size and scope that
we have to manage. You have to find and simplify configuration and architecture as much as
possible, so that you can continue to grow out scale.
Gardner: Lowell, what were some of the major challenges that you faced with those older
backup systems? Tell me a bit more about this consolidation journey?
Dale: That's a good question as well. Some of the new technologies that we're evolving, such as
virtual tape libraries, was one of the things that we had to figure out. What was the use case
scenario for virtual tape? It's not easy to switch from old technology to something new and go
100 percent at it. So we had to take a step-wise approach on how we adopted virtual tape library
and what we used it for.

4. We first started with a minimal amount of use cases and little by little, we started learning what
that was really good for. We’ve evolved the use case even more, so that in our next generation
design that will move forward. That’s just one example.
Gardner: And that virtual tape is to replace physical tape. Is that right?
Dale: Yes, really to supplement physical tape. We're still using physical tape for certain scenarios
where we need the data mobility to move applications or enable the migration of applications
and/or data between disparate geographies. We'll facilitate that in some cases.
Gardner: You mentioned a little earlier on the whole issue of virtualization. You're servicing
quite a bit more of that across the board, not just with applications, but storage and networks
even.
Tell me a bit more about the issues of virtualization and how that provided a challenge to you, as
you moved to these more consolidated and comprehensive storage and backup approaches?
Dale: One of the things with virtualization is that we saw something that we did with storage and
utility storage. We made it such that it was much cheaper than before and easy to bring up. It had
the "If you build it, they will come" effect. So, one of the things that we may end up seeing is an
increase in the number of operating systems (OSs) or virtual machines (VMs) that we see out
there. That's the opposite of the consolidation effect, where you have, say, 10 one-terabyte
databases consolidated into one to reduce the overhead.
Scheduling overhead
With VMs increasing and the use case for virtualization increasing, one of the challenges is
trying to work with scheduling overhead tasks. It could be anywhere from a backup to indexing
to virus scanning and whatnot, and trying to find out what the limitations and the bottlenecks are
across the entire ecosystem to find out when to run certain overhead and not impact production.
That’s one of the things that’s evolving. We are not there yet, but obviously we have to figure out
how to get the data to the data protection pool. With virtualization, it just makes it a little bit
more interesting.
Gardner: Lowell, given that your target is moving -- as you say, you're a fast growing company
and the data is exploding -- how do you roll out something that is comprehensive and
consolidating, but at the same time your target is moving object in terms of scale and growth?
Dale: I talked previously about how we have to standardize and simplify the architecture and the
configuration, so that when it comes time to build that out, we can do it in mass.
For example, quite a few years ago, it used to take us quite a while to bring up a backup
infrastructure that would facilitate that service need. Nowadays, we can bring up a fairly large

5. scope environment, like an entire data center, within a matter of months if not weeks. This is how
long it would take us. The process from there moves towards how we facilitate setting up backup
policies and schedules, and even that’s evolving.
Right now, we're looking at ideas and ways to automate that, so that' when a server plugs in,
basically it’ll configure itself. We're not there yet, but we are looking at that. Some of the things
that we’ve improved upon are how we build out quickly and then turn around and set up the
configurations, as that business demand is then turned around and converted into backup
demand, storage demand, and network demand. We’ve improved quite a bit on that front.
Gardner: And what version of Data Protector are you using now, and what are some of the more
interesting or impactful features that are part of this latest release?
Dale: Data Protector 6.11 is the current release that we are running and deploying in our next
generation. Some of the features with that release that are very helpful to us have to do with
checkpoint recoveries.
For example, if the backup or resource should fail, we have the ability with automation to go out
and have it pick up where it left off. This has helped us in multifold ways. If you have a bunch of
data that you need to get backed up, you don’t want to start over, because it’s going to impact the
next minute or the next hour of demand.
Not only that, but it’s also helped us be able to keep our backup success rates up and our tickets
down. Instead of bringing a ticket to light for somebody to go look at it, it will attempt a few
times for a checkpoint recovery. After so many attempts, then we’ll bring light to the issue so
that someone would have to look at.
Gardner: With this emphasis on automation over the manual, tell us about the impact that’s had
on your labor issues, and if you’ve been able to take people off of these manual processes and
move them into some, perhaps more productive efforts.
Raising service level
Dale: What it’s enabled us to do is really bring our service level up. Not only that, but we're
able to focus on other things that we weren’t able to focus on before. So one of the things is
there’s a successful backup.
Being able to bring that backup success rate up is key. Some of the things that we’ve done with
architecture and the product -- just the different ways for doing process -- has helped with that
backup success rate.
The other thing that it's helped us do is that we’ve got a team now, which we didn’t have before,
that’s just focused on analytics, looking at events before they become incidents.

6. I’ll use an analogy of a car that’s about to break-down, and the check-engine light comes on.
We're able to go and look at that prior to the car's breaking down. So, we're getting a little bit
further ahead. We're going further upstream to detect issues, before they actually impact our
backup success rate or SLAs. Those are just a couple of examples there.
Gardner: How many people does it take to run these petabytes of recovery and backup through
your next-generation data center. Just give us a sense of the manpower.
Dale: On backup and recovery in the media management side, we’ve got about 25 people total
spread between engineering and operational activities. Basically, their focus is on the backup and
recovery of the media management side.
Gardner: Let’s look at some examples. Can you describe a time when you’ve needed to do very
quick or even precise recovery, and how did this overall architectural approach and consolidation
efforts help you on that?
Dale: We’ve had several cases where we had to recover data and go back to the data protection
pool. That happens monthly in fact. We have a certain amount of rate of resource that we do per
month. Some of those are to mitigate data loss from logical corruption or accidental deletion.
But, we also find the service being used to do database refreshes. So, we’ll have these large
databases that they need to make a copy of from production. They end up getting copied over to
development or test.
This current technology we are using, the current configuration, with the virtual tape libraries and
the archive blogs has really enabled us to get the data backed up quickly and restored quickly.
That’s been exemplified several times with either database copying or database recoveries, when
those few type of events do occur.
Gardner: I should think these are some very big deals, when you can deliver the recovered data
back to your constituents, to your users. That probably makes their day.
Dale: Oh yes, it does save the bacon at the end of the day.
Gardner: Perhaps you could outline, in your thinking, the top handful of important challenges
that Data Protector addresses for you at HP IT. What are the really important paybacks that
you're getting?
Object copy
Dale: I’ve mentioned checkpoint recovery. There are also some the things that we’ve been able
to use with object copy that’s allowed us to balance capacity between our virtual tape libraries
and our physical tape libraries. In our first generation design, we had enough capacity on the
virtual libraries inside the whole, a subset of the total data.

7. Data Protector has a very powerful feature called object copy. That allowed us to maintain our
retention of data across two different products or technologies. So, object copy was another one
that was very powerful.
There are also a couple of things around the ability to do the integration backups. In the past, we
were using some technology that was very expensive in terms of using of disk space on our XPs,
and using split-mirror backups. Now, we're using the online integrations for Oracle or SQL and
we're also getting ready to add SharePoint and Microsoft Exchange.
Now, we're able to do online backups of these databases. Some of them are upwards of 23
terabytes. We're able to do that without any additional disk space and we're able to back that up
without taking down the environment or having any downtime. That’s another thing that’s been
very helpful with Data Protector.
Gardner: Lowell, before we wrap up, let's take a look into the future. Where do you see the
trends pushing this now? I think we could safely say that there's going to still be more data
coming down the pike. Are there any trends around cloud computing, mobile business
intelligence, warehousing efforts, or real-time analysis that will have an impact on some of these
products and processes?
Dale: With some of the evolving technologies and some of the things around cloud computing, at
the end of the day, we'll still need to mitigate downtime, data loss, logical corruption, or anything
that would jeopardize that business asset.
With cloud computing, if we're using the current technology today with peak base backup, we
have to get the data copied over to a data protection pool. There still would be the same approach
of trying to get that data. If there is anything to keep up with these emerging technologies, for
example, maybe we approach data protection a little bit differently and spread the load out, so
that it’s somewhat transparent.
Some of the things we need to see and we may start seeing in the industry are load management
and how loads from different types of technologies talk to each other. I mentioned virtualization
earlier. Some of the tools with content-awareness and indexing has overhead associated with it.
I think you're going to start seeing these portfolio products talking to each other. They can
schedule when to run their overhead function, so that they stay out of the way of production. It’s
just a couple of challenges for us.
We're looking at new configurations and designs that consolidate our environment. So we're
looking at reducing our environment from 50-75 percent just by redesigning our architecture and
making available more resources that were tied up before. That's one goal that we're working on
right now. We're deploying that design today.
And then, there's configuration and capacity management. This stuff is still evolving, so that we
can manage the service level that we have today, keep that service level up, bring the capital
down, and keep the people required to manage it down as well.

8. Gardner: Great. I'm afraid we're out of time. We've been focusing on the challenges and
progress of conducting massive and comprehensive backups of enterprise-wide data and
applications and systems. We've been joined by Lowell Dale, a technical architect in HP's IT
organization. Thanks so much, Lowell.
Dale: Thank you, Dana.
Gardner: And, thanks to our audience for joining us for this special BriefingsDirect podcast
coming to you from the HP Software Universe 2010 Conference in Washington DC. Look for
other podcasts from this HP event on the hp.com website under HP Software Universe Live
podcast, as well as through the BriefingsDirect Network.
I'm Dana Gardner, Principal Analyst at Interarbor Solutions, your host for this series of HP-
sponsored Software Universe live discussions. Thanks again for listening and come back next
time.
Listen to the podcast. Find it on iTunes/iPod and Podcast.com. Download the transcript. Sponsor:
Hewlett-Packard.
Transcript of a BriefingsDirect podcast from the HP Software Universe Conference in
Washington DC on the backing up a growing volume of enterprise data using HP Data Protector.
Copyright Interarbor Solutions, LLC, 2005-2010. All rights reserved.
You may also be interested in:
• Case Study Shows How HP Data Protector Notebook Extension Provides Constant
Backup for Expanding Mobile Workforce
• IT's New Recipe for Success: Modernize Applications and Infrastructure While Taking
Advantage of Alternative Sourcing
• Converged Infrastructure Approach Paves Way for Improved Data Center Productivity