Virtual Tape Libraries

1
Virtual Tape Libraries

• The problem of the Pipe, the Engine, and the
  Bucket

2
A Simple Problem

• Backup 20 Terabytes each week
• Keep the data online for 5 weeks
• Longer retention items move offsite after 35 days
• You have 10 hours to complete all backups
• Find a repository that will handle this data for
  the next five years

3
Complication 1 - Growth
4
Complication 2 The Window
5
Other Complications

• Budget
• Changing RPO/RTO expectations
• New Projects
• Process Changes
• Communication

6
The Solution

• Must Be
• Flexible
• Fast
• Easy to expand
• Cost effective

7
THE VIRTUAL TAPE LIBRARY
8
VTL Benefits
(Maybe)

• Faster
• More Reliable
• More Flexible
• Easier to Manage
• Higher Compression Possibilities (De-duplication)
• Automated Replication
• Etc.

9
VTL Choice Criteria

• Must be compatible with my environment
• Must handle my data
• Must scale to my future
• Must be at least as simple as tape
• Must be as flexible as possible
• Must be reliable
• Must be easy to deploy

10
What should I be looking for?

• A true appliance
• Ease of Use
• Ease of Deployment
• One Finger to Point
• Scalability
• Repository must Scale
• Throughput must Scale

11
What should I be looking for?

• Emulations
• Compatibility
• Specific Library and Drive types may not matter!!

12
What should I be looking for?

• Are there any Performance guarantees?
• Content Awareness
• Replication
• De-duplication (Is it enterprise ready?)
• Whats Next on the Roadmap?
• NO FORKLIFT UPGRADES!!!!!

13
(No Transcript)