1. Copyright © 2004 VERITAS Software Corporation. All rights reserved
Copyright © 2004 VERITAS Software Corporation. All rights reserved. VERITAS, the VERITAS logo, and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation. VERITAS and the VERITAS Logo Reg. U.S. Pat. & Tm Off. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies.

2. Enterprise Vault 6: NetBackup Integration

3. Vision

4. Customer Challenges Data growth continues unabated
TCO of data management skyrocketing
Disk archiving addressed initial pain
Near-line, cheaper storage
Not all data needs near-line access speeds
Long-term reference data
Compliance data at end of retention period
Customers want ILM but struggle to implement

5. Enterprise Vault 6 Sources Clients Apps. Enterprise Vault Exchange
Mailboxes
Journals
Public Folders
PSTs
Outlook
Offline
Vault
Outlook
Web Access
SharePoint
2003
SDK
Apps.
Search
Archive Explorer
Secondary
Store
Archive
Enterprise Vault
Store/Retain/Expire
Index/Search/Future-Proof
View/Restore
Compress/Migrate
Audit/Administer
Categorization/Filtering
File System
SharePoint
2003
Supervision
Domino Journaling
E-Discovery
Summary of the main sources of information to be stored in Vault along with the main clients – note that file system archiving was a mid-2003 deliverable
Adding:
SDK / VE Partner program points to extend the partner ecosystem in all areas
IBM DR 550 Storage Platform integration (EMC Centera competitor)
VERITAS NetBackup Tape migration integration (Further utilization of online & nearline tape resources)
Gotchas:
Don’t propose Offline tapes (i.e. traditional VERITAS concept of tape “Vaults”) this is unlikely to prove workable, but is too early to propose
SMTP
Capture
SDK
SDK
SDK

6. EV 6: Making ILM Vision A Reality
Primary Storage
Enterprise Vault 6 NetBackup Migrator
Disk Archive
NetBackup Media Server 5.1+
Tape Library
Initially for 6 SP1 we will “see” the NBU media server as a storage device just as we do with Windows servers, EMC Centera, NetApp SnapLock, and IBM DR550.
This allows customers to have the opportunity of a tape integration as a secondary storage target for added data security.
There is a NBU + EV Best Practices guide that PS is using to work with deployments.
EV 6 manages data across tiered storage – from hot (live) to warm (recent) to cool (old).

7. Leverage Two Market Leaders
The Magic Quadrant is copyrighted January, 2002 by Gartner Group, Inc. and is reused with permission. Gartner’s permission to print its Magic Quadrant should not be deemed to be an endorsement of any company or product depicted in the quadrant. The Magic Quadrant is Gartner’s opinion and is an analytical representation of a marketplace at and for a specific time period. It measures vendors against Gartner-defined criteria for a marketplace. The positioning of vendors within a Magic Quadrant is based on the complex interplay of many factors. Well-informed vendor selection decisions should rely on more than a Magic Quadrant. Gartner Research is intended to be one of many information sources and the reader should not rely solely on the Magic Quadrant for decision-making. Gartner expressly disclaims all warranties, express or implied of fitness of this research for a particular purpose.
Source: Gartner Research Note: “SAN Management Software Magic Quadrant -- Preliminary Assessment,”
Carolyn DiCenzo and Robert Passmore, January 2002
Source: Gartner, Magic Quadrant for Enterprise Backup/Restore Vendors 2004, C. DiCenzo and R. Paquet,

8. EV 6 and NetBackup Details

9. NetBackup Overview Clients Media Server(s) Master Server
NetBackup Enterprise Server is built upon a 3 tier architecture. *Note* Master & Media servers can be UNIX, Linux, Windows, or any combination. The first tier is the Master Server. The Master Server acts as the “brains” of NetBackup, controlling functions such as job scheduling, backup classes and maintaining the meta data such as tape media and detailed client backup data. The Master Server may be configured to back up and recover data. [RETURN] The second tier is the Media Server, which performs backup and recovery operations. The Media Server was designed to place the backup and recovery close to where the data is. For example, Media Servers can be deployed throughout the enterprise to backup other servers (UNIX, Windows, NetWare) and workstations (e.g. MAC, OS/2, Win98). Another popular use of Media Servers is where there is an application server running a large database application. This application server can become a NetBackup Media server so that local (direct SCSI attach or SAN attach to a tape device/library) backup and recovery can occur. This type of backup is the fastest method possible for larger amounts of data (e.g. several 100 gigabytes). [RETRUN] The third tier consists of the clients themselves that are backed up by the Media (and in some installations, Master) Servers. A “client” can be a UNIX, Linux, Windows or Novell NetWare server or one of many workstation O/S such as MAC OS, Win98 or OS/2. In addition, NetBackup supports OpenVMS clients and Linux clients running on IBM zSeries (OS/390) systems. The combination of a Master Server and one or more Media Server is called a storage domain. Unique Features to mention:
1) Automatic Media Server failover (ensures clients are protected in case the primary Media Server fails). 2) Server independent restore (ensures tapes can be restored via alternate media server).

10. NetBackup Overview: GUI
NetBackup has a robust java or native windows GUI (depending on the platform the server is installed on), plus offers very rich command line functionality. The picture above is the launch window from the NetBackup Administration Console on Windows. On the right side, you can see the wizard that will walk the user through the product step by step.

11. High Level: Archiving and Migration
Enterprise Vault 6 NetBackup Migrator
.DVS files collected to .CAB file
NetBackup Media Server 5.1+
.CAB file backed up to backup image
Initially for 6 SP1 we will “see” the NBU media server as a storage device just as we do with Windows servers, EMC Centera, NetApp SnapLock, and IBM DR550.
This allows customers to have the opportunity of a tape integration as a secondary storage target for added data security.
There is a NBU + EV Best Practices guide that PS is using to work with deployments.
Message
The integration leverages the Collector / Migrator and the NBU VxBSA interface.

12. High Level: Restore and Recall
Enterprise Vault 6 NetBackup Migrator
NetBackup Media Server 5.1+
EV initiates restore
Request for archived item
EV realizes item is with NBU
Item recalled to user
.DVS extracted from .CAB
.CAB restored to disk
Message if timeout exceeded
Initially for 6 SP1 we will “see” the NBU media server as a storage device just as we do with Windows servers, EMC Centera, NetApp SnapLock, and IBM DR550.
This allows customers to have the opportunity of a tape integration as a secondary storage target for added data security.
There is a NBU + EV Best Practices guide that PS is using to work with deployments.

13. High Level: Expiration
Enterprise Vault 6 NetBackup Migrator
NetBackup Media Server 5.1+
EV realizes item is expiring
Most of CAB expired => restore
Marked for deletion in SQL
.CAB restored to disk
Old image marked expired
New .CAB created and backed up
Related index data deleted
Initially for 6 SP1 we will “see” the NBU media server as a storage device just as we do with Windows servers, EMC Centera, NetApp SnapLock, and IBM DR550.
This allows customers to have the opportunity of a tape integration as a secondary storage target for added data security.
There is a NBU + EV Best Practices guide that PS is using to work with deployments.

14. Enterprise Vault 6 NetBackup Migrator NetBackup Media Server 5.1+
High Level: Policies
Enterprise Vault 6 NetBackup Migrator
NetBackup Media Server 5.1+
Archiving policies
User, folder, age, size, quota, etc.
Migration policies
Age of .CAB for migration
Collection policies
Daily collection window
Maximum size for .CAB
Age (last modified) for collection
Whether to migrate
Expiration policies
Length of data retention
User timeout
Time before user gets message to try later
System timeout
Time before system stops trying
Initially for 6 SP1 we will “see” the NBU media server as a storage device just as we do with Windows servers, EMC Centera, NetApp SnapLock, and IBM DR550.
This allows customers to have the opportunity of a tape integration as a secondary storage target for added data security.
There is a NBU + EV Best Practices guide that PS is using to work with deployments.
Removal policies
Time after migration to remove

15. Configuration: NBU Create NBU policy and schedule
Use policy type = DataStore
Storage unit and volume pool let you define target media

16. Configuration: NBU
Use User Backup (no fixed schedule) since EV will control the backup
Set retention to infinity since EV will control the expiration
No specific policy directive needed since EV will pass files to NBU

17. Configuration: EV
Create new Vault Store and Vault Store Partition or use existing
Define collection time
Define maximum collection size
Indicate whether to migrate

18. Configuration: EV Select NBU Migrator Define policy for migration time
Select policy for deletion of collection files after migration

19. Configuration: EV
Select user timeout (time before user gets message asking to check back)
Select system timeout (time after which file is dropped from queue)

20. Monitoring Progress
Monitor progress of backups (migrations) and restores using NBU Activity Monitor

21. End-User Messages
Integrated search
Outlook
File System Archiving

22. End-User Messages
Web search
Universal shortcuts

23. What Files Are Where? File Type Purpose Location .DVS file Saveset
Hour directory
.DVF file
Large saveset (>50 MB)
.CAB file
Collection
Day directory
.ARCHCAB
Temporary collection on disk (migrated)
.ARCHDVS
Temporary saveset on disk (recalled)

24. FAQ Versions required Migrate to two tapes at once?
EV 6+ and NBU 5.1+
Migrate to two tapes at once?
Yes via NBU Inline Copy
Migrate straight to tape?
No – disk must be intermediary
Can migrate data right away (within 1 day)
Support BE?
Not today – planned for the future
Support TSM?
IBM DR 550 support gives us good start

25. 2005-2006 Key Release Summary 1H05 2H05 1H06 2H06
EV 6 BETA (April)
PST “Sniffer”
SharePoint 2003 archiving
Categorization / filtering
Manageability enhancements
MOM 2000/2005 pack
Hosting functionality
Plasmon UDO (Pegasus) support
EV 6 SP1 (TBC: Sep)
Domino journaling
CA 6 (4Q05)
Web Farm support
Escalations
Reviewer notifications/reminders
Post-review research
Improved sampling accuracy
EV 7 (TBC: 2H06)
In planning
MRD in 4Q05
1H05 2H05 1H06 2H06
EV 6 GA (July)
Migration via NetBackup
SMTP capture
EV SDK
IBM DR550 support
E-learning training
CA 5.1 SP3 (July)
Performance enhancements
EV 6.1 (TBC: 4Q05/1Q06)
In planning
MRD in July
DA 6.1 (TBC)
All future release dates are tentative and subject to change.

26. Where We Are Going

27. DMG: Data Orchestration
Primary
System
Primary Store
Backup
Archive
Enterprise
Vault
Secondary Store
Migrate
Information Exploitation
Discovery
Item Level Restore
Long Term
Information Protection
Recovery System Level Restore Short Term
Tertiary Store

28. DMG: Backup + Archiving
Integrated User Restore/Recall Interface
Integrated Backup/Archive Policy Mgmt & Copy Mgmt.
Build Archive Directly From Existing Backup Tapes
Backup Process
Archiving Process
Optimize Backup Through Archiving Of Static Data
Vault
Primary Data
Tape
Library Archive
Migrate Archive To Tape Using Netbackup (6.0 – Mid-’05)
Disk Stage
Disk Archive
Phase I: Migrate data from disk archive to tape using NBU
Phase II: Retroactively archive data from tape
Phase III: Integrated console for managing data protection and archiving policies, integrated restore/recall/search
Mirror

29. Copyright © 2004 VERITAS Software Corporation. All rights reserved
Copyright © 2004 VERITAS Software Corporation. All rights reserved. VERITAS, the VERITAS logo, and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation. VERITAS and the VERITAS Logo Reg. U.S. Pat. & Tm Off. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies.