student guideHP OpenView Storage Data Protector I: Fundamentals u1610s b.00 training © 2003 Hewlett-Packard Development Company, L.P. Netscape, Netscape Commerce Server, Netscape Communications, Netscape Communications Server, "N" logo, Netscape Navigator, Netscape Navigator Included logo, and Netscape Proxy Server are U.S. trademarks of Netscape Communications Corporation Oracle® is a registered U.S. trademark of Oracle Corporation, Redwood City, California. Oracle Reports™, Oracle7™, and Oracle7 Server™ are trademarks of Oracle Corporation, Redwood City, California. UNIX® is a registered trademark of the Open Group. Microsoft®, Windows NT ®, Windows®, and MS Windows® are U.S. registered trademarks of Microsoft Corp. All other product names mentioned herein may be trademarks of their respective companies. Hewlett-Packard Company shall not be liable for technical or editorial errors or omissions contained herein. The information is provided “as is” without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. HP OpenView Storage Data Protector I: Fundamentals Student Guide October 2003 Contents Module 1 — Introduction 1-1. SLIDE: Welcome...................................................................................................................... 1-2 1-2. SLIDE: Agenda (1).................................................................................................................. 1-3 1-3. SLIDE: Agenda (2).................................................................................................................. 1-4 1-4. SLIDE: Additional Resources................................................................................................ 1-5 Module 2 — Data Protector Overview and Architecture 2-1. SLIDE: HP OpenView Storage Data Protector.................................................................... 2-2 2-2. SLIDE: Managed Environment ............................................................................................. 2-3 2-3. SLIDE: Backup Models .......................................................................................................... 2-4 2-4. SLIDE: Split-Mirror Backup Concept................................................................................... 2-5 2-5. SLIDE: Snapshot Backup Concept....................................................................................... 2-7 2-6. SLIDE: HP OpenView Building Block Architecture ........................................................... 2-8 2-7. SLIDE: Data Protector Architecture Components ........................................................... 2-12 2-8. SLIDE: The Cell Concept..................................................................................................... 2-16 2-9. SLIDE: Client/Server Modules ............................................................................................ 2-18 2-10. SLIDE: Platform Support................................................................................................... 2-19 2-11. SLIDE: Cell Manager .......................................................................................................... 2-20 2-12. SLIDE: Internal Database Size Limits .............................................................................. 2-22 2-13. SLIDE: Capacity Planning Spreadsheet ........................................................................... 2-24 2-14. SLIDE: Cell Console (User Interface) .............................................................................. 2-25 2-15. SLIDE: Disk Agent.............................................................................................................. 2-27 2-16. SLIDE: Media Agent ........................................................................................................... 2-28 2-17. SLIDE: Integration Agent .................................................................................................. 2-29 2-18. SLIDE: Installation Server ................................................................................................. 2-31 2-19. SLIDE: Typical Backup/Restore Session ......................................................................... 2-32 2-20. SLIDE: Inter-process Communication ............................................................................. 2-33 2-21. SLIDE: Cell Manager Directory Structure (UX) ............................................................. 2-35 2-22. SLIDE: Cell Manager Directory Structure (Windows)................................................... 2-37 2-23. SLIDE: Client Directory Structure (UX) .......................................................................... 2-39 2-24. SLIDE: Client Directory Structure (Windows) ............................................................... 2-40 2-25. SLIDE: Global Options....................................................................................................... 2-41 2-26. SLIDE: Localized Options.................................................................................................. 2-43 2-27. Review: Data Protector Architecture.............................................................................. 2-45 Module 3 — Data Protector Installation 3-1. SLIDE: Installation Sequence................................................................................................ 3-2 3-2. SLIDE: Installation Methods ................................................................................................. 3-4 3-3. SLIDE: Supported Upgrades ............................................................................................... 3-10 3-4. SLIDE: Data Protector Components .................................................................................. 3-13 3-5. SLIDE: Installation Requirements (UX) ............................................................................ 3-16 3-6. SLIDE: Installation Requirements (Windows).................................................................. 3-18 3-7. SLIDE: Installation of Cell Manager on HP-UX ................................................................ 3-20 3-8. SLIDE: Installation of Cell Manager on Windows ............................................................ 3-23 3-9. SLIDE: Installation of Cell Manager on Solaris ................................................................ 3-25 3-10. SLIDE: Installation Servers ............................................................................................... 3-27 3-11. SLIDE: HP-UX CD-ROM Contents.................................................................................... 3-29 3-12. SLIDE: Windows CD-ROM Contents................................................................................ 3-30 3-13. SLIDE: Solaris CD-ROM Contents.................................................................................... 3-31 3-14. SLIDE: Starting the UNIX GUI.......................................................................................... 3-32 http://education.hp.com U1610S B.00 iii 2003 Hewlett-Packard Development Company, L.P. Contents 3-15. 3-16. 3-17. 3-18. 3-19. 3-20. 3-21. 3-22. SLIDE: Starting the Windows GUI ....................................................................................3-34 SLIDE: Register Installation Servers ................................................................................3-35 SLIDE: Adding New Clients to the Cell ............................................................................3-37 SLIDE: Adding Components to Clients ............................................................................3-40 SLIDE: Importing Clients ...................................................................................................3-41 SLIDE: Deleting (Exporting) Clients ................................................................................3-43 SLIDE: Data Protector Licensing ......................................................................................3-44 SLIDE: Licenses and Part Numbers..................................................................................3-45 Module 4 — Data Protector Basics 4-1. SLIDE: Getting Started ............................................................................................................4-2 4-2. SLIDE: Data Protector GUI.....................................................................................................4-4 4-3. SLIDE: Authorizing Remote Console Access (1) .................................................................4-7 4-4. SLIDE: Authorizing Remote Console Access (2) .................................................................4-8 4-5. SLIDE: General Backup Concept.........................................................................................4-10 4-6. SLIDE: Backup Specification ...............................................................................................4-12 4-7. SLIDE: Backup Checklist......................................................................................................4-14 4-8. SLIDE: Verify Agents .............................................................................................................4-15 4-9. SLIDE: Check Default Media Pools .....................................................................................4-16 4-10. SLIDE: Configure a Device .................................................................................................4-17 4-11. SLIDE: Device Specification...............................................................................................4-18 4-12. SLIDE: Add Media to Media Pool.......................................................................................4-20 4-13. SLIDE: Format Medium ......................................................................................................4-22 4-14. SLIDE: Configure a Backup (1)..........................................................................................4-23 4-15. SLIDE: Configure a Backup (2)..........................................................................................4-24 4-16. SLIDE: Configure a Backup (3)..........................................................................................4-25 4-17. SLIDE: Configure a Backup (4)..........................................................................................4-26 4-18. SLIDE: Start the Saved Backup Specification ..................................................................4-27 4-19. SLIDE: The Scheduler .........................................................................................................4-29 4-20. SLIDE: Scheduled Backup (1) ............................................................................................4-30 4-21. SLIDE: Scheduled Backup (2) ............................................................................................4-32 4-22. SLIDE: Backup Types..........................................................................................................4-34 4-23. SLIDE: Backup Types Examples .......................................................................................4-36 4-24. SLIDE: Verify the Backup Session .....................................................................................4-38 4-25. SLIDE: Perform a Restore...................................................................................................4-39 4-26. SLIDE: Mount Request (1) ..................................................................................................4-41 4-27. SLIDE: Mount Request (2) ..................................................................................................4-42 4-28. SLIDE: Mount Request (3) ..................................................................................................4-43 4-29. SLIDE: Introduction to Reporting......................................................................................4-44 4-30. SLIDE: Reporting .................................................................................................................4-45 Module 5 — Tape Library Configuration and Implementation 5-1. SLIDE: Objectives ...................................................................................................................5-2 5-2. SLIDE: Library Terminology..................................................................................................5-3 5-3. SLIDE: Library Introductions (hp MSL)...............................................................................5-5 5-4. SLIDE: Magazines — Mail Slots ............................................................................................5-8 5-5. SLIDE: Rear Panel — 10U Model........................................................................................5-10 5-6. SLIDE: Tape Drives for HP MSL Libraries.........................................................................5-12 5-7. SLIDE: SCSI Interface ..........................................................................................................5-13 5-8. SLIDE: Library Performance ...............................................................................................5-16 5-9. SLIDE: Fibre Channel — SCSI Router ...............................................................................5-18 5-10. SLIDE: Library Operations/Configuration .......................................................................5-21 U1610S B.00 iv 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Contents 5-11. 5-12. 5-13. 5-14. 5-15. 5-16. 5-17. 5-18. 5-19. 5-20. 5-21. 5-22. 5-23. 5-24. 5-25. 5-26. 5-27. 5-28. 5-29. 5-30. SLIDE: Menu Screen .......................................................................................................... 5-23 SLIDE: Configure Network Access .................................................................................. 5-25 SLIDE: Setting SCSI IDs .................................................................................................... 5-26 SLIDE: Remote Management Interface ........................................................................... 5-28 SLIDE: Web-based Remote Library Management .......................................................... 5-29 SLIDE: Configuring the NSR ............................................................................................. 5-30 SLIDE: Fibre Channel Mapping (per host client) ........................................................... 5-33 SLIDE: HBA Connectivity (topology) .............................................................................. 5-34 SLIDE: Server Considerations .......................................................................................... 5-36 SLIDE: Logical Device Files .............................................................................................. 5-37 SLIDE: RMS Enabled for Windows 2000 ......................................................................... 5-39 SLIDE: Disable RSM for Library on Windows 2000 ....................................................... 5-40 SLIDE: RSM Disabled for Tape Library ........................................................................... 5-41 SLIDE: Windows SCSI Device Paths................................................................................ 5-42 SLIDE: HP 9000 Hardware Addressing ............................................................................ 5-44 SLIDE: Verify Library Robotic Control Using L&TT ...................................................... 5-49 SLIDE: L&TT Connectivity Verification .......................................................................... 5-51 SLIDE: Device Analysis Test............................................................................................. 5-54 SLIDE: Library Exercise Test............................................................................................ 5-55 LAB: MSL Library ............................................................................................................... 5-56 Module 6 — Media Management 6-1. SLIDE: Media Management ................................................................................................... 6-2 6-2. SLIDE: The Media Pool.......................................................................................................... 6-5 6-3. SLIDE: Creating Media Pools................................................................................................ 6-7 6-4. SLIDE: Media Pool Properties .............................................................................................. 6-9 6-5. SLIDE: Media Pool Characteristics .................................................................................... 6-10 6-6. SLIDE: Loose or Strict Allocation?..................................................................................... 6-15 6-7. TEXT PAGE: Media Allocation and Usage........................................................................ 6-17 6-8. SLIDE: Free Pool Concept .................................................................................................. 6-22 6-9. SLIDE: Media Life................................................................................................................. 6-24 6-10. SLIDE: Media Operations .................................................................................................. 6-25 6-11. SLIDE: Formatting Media.................................................................................................. 6-27 6-12. SLIDE: Media Duplication ................................................................................................. 6-30 6-13. SLIDE: Automated Media Operations.............................................................................. 6-32 6-14. SLIDE: Configuring a Post-Backup AMO ........................................................................ 6-34 6-15. SLIDE: Configuring Scheduled Media Copy (AMO)....................................................... 6-36 6-16. SLIDE: Scheduled Media Copy Example......................................................................... 6-40 6-17. TEXT PAGE: The omniamo Command and Configuration Files ................................. 6-41 6-18. SLIDE: Media Vaulting Operations................................................................................... 6-44 6-19. SLIDE: Vaulting Locations ................................................................................................ 6-45 6-20. SLIDE: Vaulting with Media Pools ................................................................................... 6-46 6-21. TEXT PAGE: Automated Media Vaulting ........................................................................ 6-48 6-22. Review Questions............................................................................................................... 6-50 http://education.hp.com U1610S B.00 v 2003 Hewlett-Packard Development Company, L.P. Contents Module 7 — Logical Devices 7-1. SLIDE: The Logical Device ....................................................................................................7-2 7-2. SLIDE: Logical Device Types ................................................................................................7-3 7-3. SLIDE: Device Configurations...............................................................................................7-8 7-4. SLIDE: Configuration Methods ...........................................................................................7-11 7-5. SLIDE: Adding a Device (manual method)........................................................................7-12 7-6. SLIDE: Physical Device Selection.......................................................................................7-15 7-7. SLIDE: Library Repository Configuration..........................................................................7-17 7-8. SLIDE: Library Drive Configuration ...................................................................................7-18 7-9. SLIDE: Media Type and Default Pool .................................................................................7-20 7-10. SLIDE: Advanced Options .................................................................................................7-21 7-11. SLIDE: Device Concurrency ..............................................................................................7-24 7-12. SLIDE: Data Protector Tape Format ................................................................................7-26 7-13. SLIDE: Mount Notification ................................................................................................7-29 7-14. SLIDE: Library Sharing.......................................................................................................7-32 7-15. SLIDE: Autoconfigure a Device (1) ..................................................................................7-34 7-16. SLIDE: Autoconfigure a Device (2) ..................................................................................7-35 7-17. SLIDE: Autoconfigure a Device (3) ..................................................................................7-36 7-18. SLIDE: Library Scanning....................................................................................................7-38 7-19. SLIDE: Library Slot Operations.........................................................................................7-40 7-20. SLIDE: External Control ....................................................................................................7-42 7-21. SLIDE: GRAU and StorageTek Libraries..........................................................................7-45 7-22. Review Questions ...............................................................................................................7-47 Module 8 — Backup 8-1. SLIDE: Performing Backups...................................................................................................8-2 8-2. SLIDE: Backup Specification Types ......................................................................................8-5 8-3. SLIDE: The Backup Specification (datalist).........................................................................8-7 8-4. SLIDE: Backup Specification Contents.................................................................................8-9 8-5. SLIDE: Backup Specification Sequence..............................................................................8-11 8-6. SLIDE: Creating Backup Specifications..............................................................................8-12 8-7. SLIDE: Load Balancing..........................................................................................................8-14 8-8. SLIDE: Static Device Allocation...........................................................................................8-16 8-9. SLIDE: Load Balancing — Object Allocation .....................................................................8-17 8-10. SLIDE: Interactive Backup Specifications........................................................................8-19 8-11. SLIDE: Source ......................................................................................................................8-20 8-12. SLIDE: Destination ..............................................................................................................8-22 8-13. SLIDE: Backup Specification Options..............................................................................8-24 8-14. SLIDE: Pre- and Post-Execution .......................................................................................8-27 8-15. SLIDE: Pre- and Post-Exec Script Failures......................................................................8-29 8-16. SLIDE: Reconnect Broken Sessions .................................................................................8-33 8-17. SLIDE: File System Options ..............................................................................................8-35 8-18. SLIDE: Object Summary ....................................................................................................8-41 8-19. SLIDE: Object Properties...................................................................................................8-42 8-20. SLIDE: Parallel Data Streams from Object ......................................................................8-44 8-21. SLIDE: Configure Parallel Data Streams..........................................................................8-45 8-22. SLIDE: The Backup Process Flow ....................................................................................8-46 8-23. SLIDE: Templates and Groups ..........................................................................................8-48 8-24. SLIDE: Preview ...................................................................................................................8-50 8-25. Review Questions ...............................................................................................................8-61 U1610S B.00 vi 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Contents Module 9 — Restore 9-1. SLIDE: Performing Restores .................................................................................................. 9-2 9-2. SLIDE: Restore Objects .......................................................................................................... 9-4 9-3. SLIDE: Restore from a Session.............................................................................................. 9-6 9-4. SLIDE: Parallel Restore .......................................................................................................... 9-7 9-5. SLIDE: Restore Sequence....................................................................................................... 9-9 9-6. SLIDE: Restore Source ......................................................................................................... 9-10 9-7. SLIDE: Restore Object Properties....................................................................................... 9-13 9-8. SLIDE: Destination................................................................................................................ 9-15 9-9. SLIDE: Restore Options........................................................................................................ 9-17 9-10. SLIDE: Restore Devices...................................................................................................... 9-19 9-11. SLIDE: Restore Media......................................................................................................... 9-20 9-12. SLIDE: Restore Summary................................................................................................... 9-21 9-13. SLIDE: Parallel or Single Restore...................................................................................... 9-22 9-14. SLIDE: Point in Time Restore ............................................................................................ 9-23 9-15. Review Questions ................................................................................................................ 9-25 Module 10 — Internal Database 10-1. SLIDE: Internal Database (IDB) ....................................................................................... 10-2 10-2. SLIDE: Configuring the Database..................................................................................... 10-5 10-3. SLIDE: IDB Information Storage ...................................................................................... 10-6 10-4. SLIDE: IDB Tablespaces.................................................................................................... 10-8 10-5. SLIDE: External Binary Files .......................................................................................... 10-10 10-6. SLIDE: Directory Structure ............................................................................................. 10-13 10-7. TEXT PAGE: Transaction Logs ...................................................................................... 10-15 10-8. SLIDE: Database Size Limits (Review) .......................................................................... 10-17 10-9. SLIDE: Recommended Distribution............................................................................... 10-19 10-10. SLIDE: Managing Database Growth............................................................................. 10-21 10-11. SLIDE: Internal Database GUI ...................................................................................... 10-24 10-12. SLIDE: IDB Size Report ................................................................................................. 10-25 10-13. SLIDE: Database Maintenance ..................................................................................... 10-26 10-14. Text Page: Data Protector Commands ........................................................................ 10-27 10-15. SLIDE: Database Cleanup ............................................................................................. 10-28 10-16. SLIDE: Adding Filename Extensions ........................................................................... 10-29 10-17. SLIDE: Adding DCBF Locations................................................................................... 10-30 10-18. SLIDE: Preparing for Database Recovery ................................................................... 10-31 10-19. SLIDE: Back Up the Database ...................................................................................... 10-32 10-20. SLIDE: Manual Restore of the Database ..................................................................... 10-34 10-21. SLIDE: Manual Restore Using the GUI ........................................................................ 10-37 10-22. SLIDE: Automated Restore of the Database ............................................................... 10-38 10-23. SLIDE: Recovery from Corruption............................................................................... 10-40 10-24. TEXT PAGE: omnidb ..................................................................................................... 10-44 10-25. TEXT PAGE: omnidbutil ............................................................................................... 10-47 10-26. TEXT PAGE: IDB Maintenance Commands ............................................................... 10-54 10-27. Review Questions ........................................................................................................... 10-56 Module 11 — Monitoring and Reporting 11-1. SLIDE: Monitoring and Reporting .................................................................................... 11-2 11-2. SLIDE: Monitoring Current Sessions ............................................................................... 11-4 11-3. SLIDE: Viewing Previous Session Details ....................................................................... 11-6 11-4. SLIDE: Reporting Possibilities.......................................................................................... 11-8 11-5. SLIDE: Report Categories ................................................................................................. 11-9 http://education.hp.com U1610S B.00 vii 2003 Hewlett-Packard Development Company, L.P. Contents 11-6. SLIDE: Reporting Overview.............................................................................................11-11 11-7. SLIDE: Reporting GUI ......................................................................................................11-13 11-8. SLIDE: Web Reporting Interface.....................................................................................11-15 11-9. SLIDE: Reporting Command ...........................................................................................11-17 11-10. SLIDE: Report Groups....................................................................................................11-19 11-11. SLIDE: Report Group Schedule ....................................................................................11-20 11-12. SLIDE: Adding a Report to a Report Group.................................................................11-22 11-13. SLIDE: Service Management Integrations Overview..................................................11-24 11-14. SLIDE: Service Level Management ...............................................................................11-27 11-15. Monitor Review Questions ............................................................................................11-32 11-16. Reporting Lab Review Questions..................................................................................11-33 Module 12 — Event Notifications 12-1. SLIDE: Monitoring, Reporting and Notifications ............................................................12-2 12-2. SLIDE: Notification Concept .............................................................................................12-3 12-3. SLIDE: Data Protector Event Logging..............................................................................12-8 12-4. SLIDE: Default Notifications ...........................................................................................12-10 12-5. SLIDE: Web Notifications GUI ........................................................................................12-11 12-6. SLIDE: Notification Format.............................................................................................12-12 12-7. SLIDE: Report or Event Notification..............................................................................12-15 12-8. Notifications Lab Review Questions ..............................................................................12-16 Module 13 — Access Control and Security 13-1. SLIDE: Access Control and Security .................................................................................13-2 13-2. SLIDE: Access Control ........................................................................................................13-3 13-3. SLIDE: User Groups ............................................................................................................13-4 13-4. SLIDE: The Admin Group ...................................................................................................13-5 13-5. SLIDE: The Operator Group ...............................................................................................13-6 13-6. SLIDE: The User Group.......................................................................................................13-8 13-7. SLIDE: Custom Groups .......................................................................................................13-9 13-8. SLIDE: Group Permissions ...............................................................................................13-11 13-9. SLIDE: Adding Users and Groups....................................................................................13-13 13-10. SLIDE: Changing the Web Password.............................................................................13-15 13-11. SLIDE: Client Security.....................................................................................................13-16 13-12. SLIDE: Network Access — inet (HP-UX) .....................................................................13-18 13-13. SLIDE: Firewall Support .................................................................................................13-20 13-14. Review Questions ...........................................................................................................13-23 Module 14 — Disaster Recovery 14-1. SLIDE: Disaster Recovery..................................................................................................14-2 14-2. SLIDE: Disaster Recovery — Data Protector ..................................................................14-4 14-3. SLIDE: DR Terminology.....................................................................................................14-5 14-4. SLIDE: Data Protector 4-Phase Approach to DR ............................................................14-7 14-5. SLIDE: Supported Recovery Options (5.0) ....................................................................14-10 14-6. SLIDE: Supported Recovery Options (5.1) ....................................................................14-11 14-7. SLIDE: Manual DR Preparation Source .........................................................................14-12 14-8. SLIDE: Cell Manager Configuration Files (DR) ............................................................14-13 14-9. SLIDE: Cell Manager Manual DR Preparation (1) ........................................................14-14 14-10. SLIDE: Cell Manager Manual DR Preparation (2) ......................................................14-15 14-11. SLIDE: Manual Update to Client SRD ..........................................................................14-16 14-12. SLIDE: Manual DR Diskette Content (SRD added) ....................................................14-17 14-13. SLIDE: Assisted Manual DR Procedure .......................................................................14-18 U1610S B.00 viii 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Contents 14-14. 14-15. 14-16. 14-17. 14-18. 14-19. 14-20. 14-21. 14-22. 14-23. 14-24. 14-25. 14-26. 14-27. 14-28. 14-29. 14-30. 14-31. 14-32. 14-33. 14-34. 14-35. 14-36. 14-37. 14-38. 14-39. 14-40. 14-41. SLIDE: One Button Disaster Recovery ........................................................................ 14-20 SLIDE: OBDR Preparation ............................................................................................ 14-22 SLIDE: OBDR Wizard (1)............................................................................................... 14-23 SLIDE: OBDR Wizard (2)............................................................................................... 14-24 SLIDE: OBDR Session.................................................................................................... 14-25 SLIDE: Enhanced Automated Disaster Recovery ...................................................... 14-26 SLIDE: Copy DR Image to the Cell Manager............................................................... 14-29 SLIDE: Choose the Image Source (1) .......................................................................... 14-30 SLIDE: Select the Image Set (2).................................................................................... 14-31 SLIDE: Volume Selections (3)....................................................................................... 14-32 SLIDE: Create the ISO Image (4).................................................................................. 14-33 SLIDE: Image Ready to Burn to CD (5) ....................................................................... 14-34 SLIDE: Booting the DR Image....................................................................................... 14-35 SLIDE: Automated System Recovery Overview ......................................................... 14-39 SLIDE: ASR Procedure Overview with DP.................................................................. 14-41 SLIDE: Recovery Procedure Phase 0 ........................................................................... 14-43 SLIDE: Create the ASR Set............................................................................................ 14-45 SLIDE: ASR Set — Volume Selection .......................................................................... 14-47 SLIDE: ASR Copy Location ........................................................................................... 14-48 SLIDE: Recovery Procedure Phase 1 (1) ..................................................................... 14-49 SLIDE: Recovery Procedure Phase 1 (2) ..................................................................... 14-51 SLIDE: Recovery Procedure Phase 2 ........................................................................... 14-52 SLIDE: Recovery Procedure Phase 3 ........................................................................... 14-54 TEXT PAGE: Requirements/Limitations ..................................................................... 14-55 SLIDE: drstart.exe (interaction)................................................................................... 14-56 SLIDE: Recovering Clients with Disk Delivery........................................................... 14-59 SLIDE: HP-UX Clients.................................................................................................... 14-66 SLIDE: HP-UX Cell Server............................................................................................. 14-68 Module 15 — Manager of Managers 15-1. SLIDE: Manager of Managers............................................................................................. 15-2 15-2. SLIDE: Features................................................................................................................... 15-4 15-3. SLIDE: Concepts.................................................................................................................. 15-6 15-4. SLIDE: Configuration Steps ............................................................................................... 15-8 15-5. SLIDE: MoM GUI ............................................................................................................... 15-11 15-6. SLIDE: Communication .................................................................................................... 15-14 15-7. SLIDE: Distributed MMDB and CDB .............................................................................. 15-16 15-8. SLIDE: Central MMDB ...................................................................................................... 15-18 15-9. SLIDE: Central Licensing ................................................................................................. 15-22 15-10. TEXT PAGE: Added Functionality (MoM GUI)........................................................... 15-25 15-11. Review Questions............................................................................................................ 15-27 Module 16 — Troubleshooting 16-1. SLIDE: Log Files .................................................................................................................. 16-2 16-2. SLIDE: Execution Tracing.................................................................................................. 16-4 16-3. SLIDE: Message Details .................................................................................................... 16-12 16-4. SLIDE: Network Connectivity ......................................................................................... 16-14 16-5. SLIDE: Services ................................................................................................................. 16-18 16-6. TEXT PAGE: User Interface Startup Problems ............................................................ 16-23 16-7. SLIDE: Backup Devices .................................................................................................... 16-26 16-8. SLIDE: Backup and Restore............................................................................................. 16-33 16-9. SLIDE: omnihealthcheck.................................................................................................. 16-39 http://education.hp.com U1610S B.00 ix 2003 Hewlett-Packard Development Company, L.P. Contents 16-10. SLIDE: HealthCheck Config File....................................................................................16-40 16-11. SLIDE: omnihealthcheck.log ..........................................................................................16-42 16-12. SLIDE: omnitrig -run_checks .........................................................................................16-43 16-13. TEXT PAGE: Debugging UNIX Pre- and Post- exec Scripts.......................................16-43 Module 17 — Customizing 17-1. SLIDE: Customizing............................................................................................................17-2 17-2. TEXT PAGE: Contents of the globals File .......................................................................17-4 17-3. TEXT PAGE: Contents of the omnirc.TMPL File..........................................................17-21 Appendix A — Lab Exercises Appendix B — HP-UX Library Configuration Solutions to Review Questions U1610S B.00 x 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Overview Course Description This course is designed for system administrators and consultants who will be implementing, planning or administering the HP OpenView Storage Data Protector product on HP-UX, Windows NT/2000 and Solaris systems. OmniBack versus OmniBack II versus Data Protector HP’s first foray into the market of network backup solutions resulted in the original OmniBack product. This product contained such commands as nbsbackup/nbsrestore and bears absolutely no resemblance to the product HP OpenView OmniBack II. In 2002 the Omniback-II product was replaced by the next generation product, HP OpenView Storage Data Protector 5.0. Throughout this course, we will refer to HP OpenView Storage Data Protector simply as Data Protector for simplicity. Course Goals • This course is targeted at system administrators who are responsible for managing the system backup and recovery in a heterogeneous networked environment with HP OpenView Storage Data Protector software. • This course teaches system administrators and network administrators how to install, configure, and customize the HP OpenView Storage Data Protector product. Student Performance Objectives • • • • Install HP OpenView Data Protector product. Distribute the HP OpenView Storage Data Protector software on the network. Configure the HP OpenView Storage Data Protector product. Use the HP OpenView Storage Data Protector product to backup, restore, and monitor from the GUI and command line. • Manage the HP Openview Storage Data Protector Internal Database • Create custom reports and notification procedures http://education.hp.com U1610S B.00 1 2003 Hewlett-Packard Development Company, L.P. Overview Student Profile and Prerequisites This course is designed for students at the system administrator level. • For HP-UX, this course requires HP-UX System and Network Administration I (H3064S) or equivalent experience. Other recommended HP Education courses: HP-UX System and Network Administration II (H3065S)(for students who will be working in the UNIX environment) POSIX Shell Programming (H4322S) is strongly recommended, but is not a prerequisite • For Windows NT/2000, this level equates to Microsoft Windows Server administration or equivalent experience. • For Solaris, system and network administration training or equivalent experience. • Networking knowledge and backup device knowledge is also recommended. Conventions For convenience, we will refer to specific product directory names by their logical names rather than the fully qualified paths. Unix Logical Name $OMNIHOME or <OMNIHOME> $OMNICONFIG or <OMNICONFIG> $OMNIVAR or <OMNIVAR> /opt/omni /etc/opt/omni /var/opt/omni Directory Path Usage Binaries, man pages, etc. Configuration directory Database and log files Windows NT/2000 Logical Name $OMNIHOME or <OMNIHOME> $OMNICONFIG or <OMNICONFIG> $OMNIVAR or <OMNIVAR> Default Directory Path C:\program files\Omniback C:\program files\Omniback\config C:\program files\Omniback Usage The product root directory Configuration directory The product root directory U1610S B.00 2 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Overview Agenda Day 1 Module 1 — Introduction Module 2 — Data Protector Overview and Architecture Module 3 — Data Protector Installation Module 4 — Data Protector Basics Day 2 Module 5 — Tape Library Configuration and Implementation Module 6 — Media Management Module 7 — Logical Devices Module 8 — Backup Day 3 Module 9 — Restore Module 10 — Internal Database Module 11 — Monitoring and Reporting Module 12 — Event Notification Module 13 — Access Control and Security Day 4 Module 14 — Disaster Recovery Module 15 — Manager of Managers Module 16 — Troubleshooting Module 17 — Customizing http://education.hp.com U1610S B.00 3 2003 Hewlett-Packard Development Company, L.P. Overview U1610S B.00 4 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 1 — Introduction Objectives Upon completion of this module, you will be able to do the following: • • Describe the content and flow of this course. Get additional information about Data Protector. http://education.hp.com U1610S B.00 1-1 2003 Hewlett-Packard Development Company, L.P. Module 1 Introduction 1–1. SLIDE: Welcome Welcome HP OpenView Storage Data Protector 1: Fundamentals • Introductions • Logistics Student Notes Welcome to HP Education, and the HP OpenView Storage Data Protector 1: Fundamentals course (U1610S). This course is designed for system administrators who will be responsible for the installation, configuration, and management of the Data Protector storage management software. This course covers the HP OpenView Storage Data Protector product functionality for version 5.1, released June 2003. Throughout this course, the product name “HP OpenView Storage Data Protector” will be shortened to just Data Protector or DP for simplicity. U1610S B.00 1-2 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 1 Introduction 1–2. SLIDE: Agenda (1) Agenda (1) • • • • • • Architecture Installation DP Basics Library Implementation Media Management Logical Devices • Backup • Restore Student Notes The main topics in this course are listed on the slide. http://education.hp.com U1610S B.00 1-3 2003 Hewlett-Packard Development Company, L.P. P.com .hp.Module 1 Introduction 1–3. L.00 1-4 2003 Hewlett-Packard Development Company. SLIDE: Agenda (2) Agenda (2) • Internal Database • Monitoring and Reporting • Event Notification • • • • Cell Security Disaster Recovery Manager of Managers Troubleshooting Student Notes U1610S B. http://education. hp.Module 1 Introduction 1–4.com • Support services − HP Response Center − Account Support Organization • Consulting services − HP Consulting & Integration http://education.hp. These include: • Product documentation − Soft copy (Acrobat format) is included with the software distribution as well on the on the web.P.00 1-5 2003 Hewlett-Packard Development Company.com − http://openview.com − http://itresourcecenter. L.hp.hp. SLIDE: Additional Resources Additional Resources • Product documentation • Web sites • Support services • Consulting services • Users’ group Student Notes Hewlett Packard provides several additional resources designed to make you successful with our products.com U1610S B. − Suggested reading: − HP OpenView Storage Data Protector Administrator’s Guide − HP OpenView Storage Data Protector Concepts Guide − HP OpenView Storage Data Protector Installation and Licensing Guide • Web Sites − http://education. . com . L.org.hp. there is an HP sponsored user group called OpenView Forum. Their information is available via the web at: http://ovforum.00 1-6 2003 Hewlett-Packard Development Company.P. http://education. They typically have yearly conferences and have several other benefits available to members. U1610S B.Module 1 Introduction In addition to the support and services available from HP. L.hp. Identify the components of the Data Protector cell. you will be able to do the following: • • • • Identify the environment in which Data Protector operates. http://education. Describe the operational concepts of the Data Protector client/server architecture.Module 2 — Data Protector Overview and Architecture Objectives Upon completion of this module.com U1610S B. .P. Plan the layout for an installation.00 2-1 2003 Hewlett-Packard Development Company. This in particular addresses the SLM requirements of service providers. By managing data protection as a set of services rather than a set of data objects and IT resources. and establishes a new focus on recovery and service-centric management. SLIDE: HP OpenView Storage Data Protector HP OpenView Storage Data Protector What is it? • Software that provides automated data protection for businesses with 24x7 availability needs. data can be easily recovered and made accessible. Student Notes HP OpenView Storage Data Protector is a new generation of HP OpenView software that manages data protection as an integral component of an overall IT service. for tape management. HP OpenView Omniback II. heterogeneous SAN & NAS environments with thousands of servers. and disaster recovery. Data Protector helps you meet your service level objectives (SLO) with increased staff efficiency. Most important features: • Automated backups that scale from small workgroups to multisite. backup.Module 2 Data Protector Overview and Architecture 2–1.00 2-2 2003 Hewlett-Packard Development Company.com . U1610S B. L. Data Protector builds upon the capabilities of its predecessor. so that in case of a disaster. • Media management: easily manages the library catalogues to keep track of all media and copies of data for fast recovery. http://education.P.hp. • Fully-integrated Zero-Downtime backup with Instant-Recovery. What does it do? • Data Protection: copies data onto a storage device. 00 2-3 2003 Hewlett-Packard Development Company. The picture above is representative of the IT environment today. Many storage devices are either directly connected to a host or connected via a Storage Area Network (SAN) to meet data storage accessibility needs. Many systems from the desktop to the data center.com U1610S B. . SLIDE: Managed Environment Managed Environment Student Notes The typical IT environment today consists of many systems distributed across the enterprise. Behind these systems are increasingly large and complex data storage systems. such as the HP StorageWorks disk arrays for on-line storage and automated tape systems for near-line storage.P.Module 2 Data Protector Overview and Architecture 2–2. Managing the complexities of the IT infrastructure today requires an even more capable solution to meet the ever changing IT Service Management environment. companies are turning to large storage systems. http://education. As the need to access data from multiple systems and the quantity of data increases. L. The traditional data center has experienced tremendous change and become a server and storage farm.hp. connected via high-speed local area networks (LANs). The systems that operate today’s’ corporations are very numerous and contain huge quantities of data. VA. SLIDE: Backup Models Backup Models direct-attached backup management application server disk host media host snapshot backup Application Server tape Backup Server network backup management media host disk host split-mirror backup Application Server P S S S tape Backup Server Student Notes To protect data from all risks of loss. Data Protector offers several models for data security and backup including: • Direct attached storage • Zero Downtime Backup with Split-Mirror (StoragWorks XP) • Zero Downtime Backup with Snapshot (StorageWorks EVA. Data Protector offers a variety of ways to back it up and recover it including Zero Downtime Backup (ZDB) and Instant Recovery (IR). U1610S B. L. http://education.Module 2 Data Protector Overview and Architecture 2–3. by incorporating near zero-impact.com . using Network Data Management Protocol (NDMP) • Direct backup using X-Copy (extended copy) Data Protector’s Instant Recovery (IR) is capable of recovering terabytes of data in minutes rather than hours.hp. zero-downtime backup or Direct Backup (server-less backup from disk to tape). Data Protector enables a variety of techniques to create recovery images using disk resources as well as tape. Unlike traditional tools that focus exclusively on backup to tape. These techniques can maximize information availability and minimize application impact. depending on your business needs and available hardware.00 2-4 2003 Hewlett-Packard Development Company. MSA) • Heterogeneous network backup • Storage Area Network (SAN) attached online and nearline storage • Network Attached Storage (NAS.P. Usually. . To create the backup image. Before a backup of a mirror can be started.Module 2 Data Protector Overview and Architecture 2–4. L.00 2-5 2003 Hewlett-Packard Development Company. filesystem cache) on the host is flushed to the disk before the mirror is split off.com U1610S B. it is very important that all cached information (database cache. The mirror is not created at backup time but needs to be established ahead of time. SLIDE: Split-Mirror Backup Concept Split-Mirror Backup Concept • True online backup for integrated applications XP • Split mirrors may used for instant recovery or resynced • No performance impact on applications during backup • Mirror synchronization before or after backup • Automatic mirror rotation Application host P M 0 P – primary LDEV M M 1 2 • API based integration Backup host M – mirror copy (MU0-2) Student Notes The general idea behind split mirror backups is to stream the backup from the mirror instead of the production disk. hardware mirror technologies such as Business Copy XP or Continuous Access XP are used to create the mirror. The disk image needs to be consistent so that it can be fully restored. a valid point in time disk image needs to be created.hp. The mirror is typically connected to a separate host (called the backup host) with a tape device attached. One of the following options achieves this (depending upon the type of data to backup): • • • Databases could be put into backup mode Databases could be taken offline A filesystem could be unmounted http://education. As the application host and backup host are different.P. the mirror will simply be split off the production disk at backup time. The backup and the resynchronization of the mirrors do not affect the production database’s I/O performance as they happen inside of the XP Disk Array. The backup duration (from the perspective of the application) is only the time required to perform the split. The HP Education course. http://education.hp. In case a database is running on a filesystem. Mirror Rotation Mirror rotation relies on Business Copy’s capability to maintain up to three independent secondary volumes (S-Vols) of one primary volume (P-Vol). However. Data Protector will automatically use them in a cyclic fashion. The archive log files from the application host are also needed.Module 2 Data Protector Overview and Architecture The above must occur prior to the split of the mirror to guarantee that the backup image will be consistent. a successful restore of all files and directories cannot be guaranteed since cached data won’t be written to disk prior to the split. The different S-Vols are labeled as Mirror Units (MU#0. U1610S B. another S-Vol will be used. At the end of the backup. For the online database backup. The archive log backup can be started when the database is taken out of backup mode. the S-Vol used will be left split off the P-Vol thus keeping the backup versions on the S-Vol available for Instant Recovery. The split-mirror backup will complete successfully also with the filesystem mounted. It’s therefore recommended to unmount a filesystem before performing a spit-mirror backup. covers the concept of Zero Downtime Backup and Instant Recovery within a hands-on SAN environment. it won’t be required to unmount the filesystem first. In case of a plain filesystem backup. For the next backup. This provides a high level of data protection. Data Protector can perform split mirror backups from each of the split mirrors. This will happen right after the mirrors were successfully split off their productive disks. MU#1 and MU#2). If two or more mirrors are available. the backup image alone cannot be restored. there will be no need to unmount the filesystem as the database controls the write to the disk and ensures that data is really written to the disk and not to the filesystem cache. Administrators can either supply one dedicated S-Vol or multiple S-Vols for backup. L.com . during which the consistent backup copy is created.00 2-6 2003 Hewlett-Packard Development Company. U1611S.P. covers the snapshot integration in detail along with Instant Recovery within both a file system and RDBMS environment. The snapshot backup currently is supported with the HP StorageWorks Virtual Arrays. MSA • API based integration Student Notes The snapshot backup concepts are similar to those of the split-mirror backup. L.00 2-7 2003 Hewlett-Packard Development Company. Snapshots may be created on the fly within the array. It is expected that the EVA and MSA will be supported via a patch release due later in 2003). http://education. the HP StorageWorks Enterprise Virtual Array. EVA. SLIDE: Snapshot Backup Concept Snapshot Backup Concept • Similar to split-mirror backups Application host P VA EVA MSA S S Backup host P – primary LUN S – snapshot / child P • Snapshots get created on the fly or are reused • Backup host processes the data • Snapshot information is stored in Instant Recovery database for VA. (At the time of this printing. Snapshots may be designated for use with the Instant Recovery capabilities of Data Protector.com U1610S B.hp. Instant Recovery is only supported for the HP VA products. U1611S. EVA3000 and EVA5000 as well as the HP StorageWorks Modular Storage Array.P. MSA 1000 (MSA available later).Module 2 Data Protector Overview and Architecture 2–5. The HP Education course. . or they may be designated for re-use for backup utilizing a rotation strategy. VA71xx and VA74xx. SLIDE: HP OpenView Building Block Architecture Hp Openview Building Block Architecture • OpenView Enterprise Console • OpenView Operations: Event and Problem Management Network. Data Protector is operationally efficient. enterprise-wide. The Service Desk and Service Information Portal products form the service management umbrella and add a service management process layer and functionality on top of the integrated OpenView solution to complete the service management product offering. http://education. The flexible OVO and Service Navigator consoles also function as one of the OpenView Enterprise Consoles. There are over 400 OpenView products.P. Network Node Manager (NNM) and OpenView Operations (OVO) are the most common integration points for HP and third-party management products. HP OpenView Storage Data Protector offers comprehensive backup and restore functionality specifically tailored for global. Application and Database Management Service Level Management ~200 Openview Partner Solutions Management Repository systems management • Operations • Data Protector • data backup • data recovery • Storage Area Manager • Media Operations network management • Network Node Manager • Customer Views • PolicyXpert • Internet Services • • • • performance management GlancePlus Performance Reporter Web Transaction Observer • Internet Services application management • SMART Plug-Ins: • Apps. What sets OpenView apart from other solutions is the flexible architecture that allows you to build an IT management environment according to needs and requirements.hp. Unparalleled in the industry. Systems.00 2-8 2003 Hewlett-Packard Development Company.Module 2 Data Protector Overview and Architecture 2–6. Our different product offerings can be used as standalone products or in an integrated fashion.com . and distributed environments. DBs • Web/App Servers • Mgmt Server • Managed Nodes service management • Internet Services • Service Desk • Internet Usage Manager • Service Reporter • WebQoS • Service Info. L. This course obviously will not cover all of the products. as of this printing HP U1610S B. but it will focus on the Data Protector storage management product. Portal Network Desktop Network Access Servers Databases Applications Managing Distributed UNIX and Windows Environments. End-to-End Student Notes Illustrated above is the current OpenView building block architecture. to viruses or other unauthorized data access and modification. In short. and reporting tools to document backup and recovery operations. Enterprise IT departments are increasingly using service management tools. Business critical data loss can cost the enterprise thousands. By identifying the relative value of data placed within its care. global data center. Deep integration from Data Protector along with the OpenView Operations centric environment provides unmatched service level management capabilities. Data Protector and IT Service Management Data Protector provides unique capabilities that support IT service management in the areas of data backup and restore.0 (OV DP) there are four new Service Management Integrations introduced which aggregate data and reduces complexity in a large scale.com U1610S B. Data Protector integration with other OpenView service management products consolidates service views. not all data justify equal recoverability. Threats ranging from user error. or to the occasional failure of the storage device itself put data at risk twenty four hours a day. integrated backup solution for heterogeneous environments. and offers turnkey control to create one complete. and to justify future service expansion. Data Protector out of the box has monitoring. measure service delivery against those expectations. like a business.6TB/hour. service performance data and other capabilities into one console. IT department must protect the business critical data to a higher level of protection than the less valuable data. http://education. techniques. Service providers use Service Level Agreements (SLAs) to document the provider-customer contractual expectations. IT managers are equipped with the key data to enable proactive monitoring and planning of backup and data recovery operations. the IT department now is run like a business. With HP OpenView Data Protector 5. Demonstrating SLA compliance requires constant monitoring and periodic reporting to show whether SLA expectations have been met. It supports business and IT alignment.hp. Integration with other HP OpenView service management solutions through the Application Response Measurement (ARM) API and utilization of Data Source Integration (DSI) allows data to be leveraged into service availability and recovery planning activities that are critical to maintaining service level agreements in a heterogeneous environment. IT department can set service expectations on backup and recovery consistent with the protected data’s business value. and methods to set service level expectations. and do so cost effectively.00 2-9 2003 Hewlett-Packard Development Company. a provider can offer multiple service levels each at its own cost structure. Part of IT’s business is managing the risk of data loss. SLAs typically establish availability and performance objectives. giving a service provider better information and insight into the overall IT service delivery. While all data is at risk. Using this model.Module 2 Data Protector Overview and Architecture Storage Data Protector holds the backup performance record of 3. Backup and recovery now is managed like the enterprise itself: that is. .P. even millions of dollars per hour of downtime. notification. L. The information is presented and formatted through various portal components and is made available through a web page. http://education.0 with HP OVO.hp. OVR (OpenView Reporter) is a reporting service that further analyzes. node groups. and prevent problems occurring in networks. modules. L. systems.0 with HP OVO is extended by adding HP OpenView Reporter (OVR 3. Installation of the Data Protector cell manager onto the OVO management server is required for the enterprise console functionality and scalability that this integration provides. applications. networks. DP – OVR integration integrates DP 5. OVO DP SPI (OpenView Operations Data Protector SMART Plug In) is a package containing components of Data Protector that are fully integrated into OVO. personalizes that information for each customer and shows status and business information specific to customer’s outsourced environment. OV SIP (OpenView Service Information Portal) aggregates information collected from various services. reports. Portal components.0 Operational Error Status” report aggregates the “problem” data and can be used by an IT service provider for operational planning.P. OVSN.00 2-10 2003 Hewlett-Packard Development Company. message groups. The Data • • • • • • U1610S B. For example. OV SIP gives an IT service provider customer visibility into the services that they are outsourcing. and applications in any enterprise. Collects and analyzes data. For example. OV SIP contains a portal foundation and a range of management information modules. service definitions and command executables. and services. “DP Transaction Performance” Report consists of the service performance metrics (one of the IT SLA parameters). In addition to SLA compliance reports. as well as message forwarding to other services. “DP5.0 environment. such as data protection services. It standardizes and manages issue management and makes it possible to maintain consistent service levels. OVO SN (OpenView Service Navigator) is a system that maps messages to services to ease the control of complicated systems. Service Graph. OV SIP instead of giving the customer a generalized view of the service provider’s infrastructure. inspects. include Service Browser. and so forth. It is a central management point for various remote OpenView applications.0 with HP OpenView Service Information Portal (OV SIP). OVP Agent and OV Reporter The integration of DP 5. an IT Service Provider can generate monthly operational reports for DP5. The integration includes users. and Service Cards.com . With OVR service providers can generate reports from data obtained from the OVO management server.Module 2 Data Protector Overview and Architecture Data Protector provides the following service management integrations: • HP OVO is a software solution designed to help service providers and their system administrators detect. applications. automates critical response. solve. An IT Service Provider can use these reports to demonstrate to a customer its SLA compliance.0 English version). OVSD (OpenView Service Desk) is a central management point for products. • DP – OVSIP integration integrates DP 5. and collects data gathered by OVO and formats them into a human readable and usable webbased presentation. and generates reports demonstrating SLA compliance.0. It stores SLAs and monitors support service compliance to them.Module 2 Data Protector Overview and Architecture Protector module on OV SIP extracts status information from DP 5. help desk. an IT service provider can give its customers a view into the status of their outsourced data protection operations. L.hp. measures service quality levels. incident resolution. OV SD is a help desk solution. OV SD manages service help desk workflow. and change management processes into a single workflow. When integrated with DP5.0. DP 5. increasing DP’s monitoring and measuring capabilities.P. • DP – OVSD integration integrates DP5.0’s integration with OV SD gives support personnel access to DP5.00 2-11 2003 Hewlett-Packard Development Company.0 data for a timely response and resolution of operational problems before they affect vital data protection service. OV SD (without a human involvement) monitors the time taken to resolve backup-related problems. problem resolution. http://education.com U1610S B. such as adding media or restarting a failed backup. It enables the IT support organization to implement configuration. OV SD automates and regulates IT troubleshooting processes. .0 with HP OpenView Service Desk (OV SD). With this module. and the Cell Client layers.P. right up to the most complex multi-system. With centralized administration capabilities (managed locally or remotely) and a client/server-based architecture. multi-site enterprise-wide solution. SLIDE: Data Protector Architecture Components Data Protector Architecture Components manager of managers distributed GUI OpenView operations console cell cell manager manager cell cell clients clients Student Notes The basic HP Data Protector implementation utilizes only two architecture layers. U1610S B.00 2-12 2003 Hewlett-Packard Development Company. Scalable Client/Server Architecture The Data Protector architecture consists of specialized modules that can be implemented in wide and varied configurations.hp. Data Protector is available as a Single Server Edition. designed for smaller environments.Module 2 Data Protector Overview and Architecture 2–7.com . L. http://education. Data Protector provides the ability to globally support automated backup and restore for thousands of enterprise-wide network systems. The architecture is highly scalable and lends itself to the simplest single system configuration. the Cell Manager. Data Protector can be managed in larger environments by implementing the Manager of Managers (MOM) or OpenView Operations (OVO) layers. com U1610S B. High Performance Backup Data Protector allows backup to many devices simultaneously and supports a large range of today’s’ fast backup devices.Module 2 Data Protector Overview and Architecture The Data Protector client/server architecture provides multiple manager layers. L. which comes with the Data Protector Manager of Manager.P.hp. It is possible to administer multiple Data Protector environments from a single GUI.o. . A centralized media management database (CMMDB).) which allows remote administration and monitoring of many cells from a single consolidated GUI. cross-cell device sharing as well as central license management may also be configured with MoM. Online Application Backup With Data Protector. Enterprise Console The Data Protector integration with HP OpenView Operations provides the concept of the Enterprise Console.00 2-13 2003 Hewlett-Packard Development Company. Key product features: Central Administration Data Protector allows you to administer your complete backup environment from one single system via a GUI. which offers tremendous flexibility and adjusts easily to organizational needs and changes. HP OpenView Operations allows remote administration and monitoring of one or more Data Protector cells from a single Enterprise Console.M. Data Protector also supports integration with key storage products to allow for zero-downtime backup. Manager of Managers—MoM An existing Data Protector Cell Manager can be configured as the Manager of Managers (M. The clients are controlled from the Cell Manager system. Cell Manager and Clients The Cell Manager is the heart of the Data Protector backup environment. including the most popular libraries and auto-changers. We will cover these later in this module. you can perform on-line back up for • SAP R/3 • Informix • Sybase • Oracle (Backup and Restore GUI) • IBM DB2 • MS Exchange (Single mailbox backup and restore) • MS SQL • MS VSS (Volume Shadow Copy Service. Windows Server 2003 only) • Lotus Domino http://education. This GUI can be installed on various systems to allow multiple administrators or operators to access Data Protector via a locally installed console. SAN Support Data Protector is used today in several different SAN implementations. L. called ONTAP. As this technology is evolving. Tape-Library-Support Data Protector supports multiple tape libraries. One Button Disaster Recovery (OBDR) Data Protector allows easy disaster recovery of a complete Windows system. Through its architecture. NetApp Filers have their own operating system. it is highly scalable and suitable for nearly any kind of environment.com . Scalability Data Protector is used in environments from one system (which could be a data server) to environments with thousands of systems.Module 2 Data Protector Overview and Architecture Firewall Support Data Protector has support for backups to be managed through a firewall. Flexible U1610S B.P. Open File Backup Support The Data Protector Open File Manager (OFM 8. Disaster Recovery Data Protector allows easy disaster recovery of a complete Windows system. Easy-to-Use Data Protector comes with an easy-to-use cross-platform consistent Windows style GUI and allows easy administration of a complex environment. It allows for the successful capturing of open files even if they are changing during the backup.1) is a utility that enhances the Data Protector backup ability to manage open files on MS Windows and Novell Netware systems. consult the OpenView web site for the latest information about the supported environments. Open File Manager is an add-on product for use with Data Protector and requires an additional license. which allow for fast unattended backup times. http://education. and contains a NDMP server implementation. which is used by Data Protector to perform a backup and restore on such a system.00 2-14 2003 Hewlett-Packard Development Company. OBDR allows for automated boot and recovery from supported tape drives and servers. NDMP Support Data Protector allows the backup of data stored on an NDMP server such as NetApp filers.hp. This gives administrators more control for remote managed environments. Data Protector Media Management allows tracking and vaulting of media. Sophisticated Media Management Data Protector comes with an integrated database that stores information about each Data Protector medium and the data on it. . It fits all kinds of end-users and administrator requirements.Module 2 Data Protector Overview and Architecture Because of multiple backup and restore options. making Data Protector truly a backup solution for multivendor environments. OpenView Media Operations. Media Agent.P. Data Protector also integrates into the Microsoft Management Console for more convenient access.00 2-15 2003 Hewlett-Packard Development Company. http://education. MS Clusters.hp. Integrations In addition to the online backup integrations. and Online Application Integration Agents) are supported on various platforms. Data Protector offers integrations with OpenView Operations.com U1610S B. Data Protector is very flexible. L. MC/ServiceGuard. Multi-Vendor Support The various Data Protector agents (Disk Agent. and OmniStorage. with each department having its own administrators. cannot be in the same cell. or all systems within one room or building. thousands of miles apart. SLIDE: The Cell Concept Cell Concept • • • • • Backup domain Logical organization of systems Can match your organization Heterogeneous system support Independent but can be centrally managed Student Notes The Data Protector architecture breaks down the size and complexity of the enterprise network by defining Data Protector Cells. However. L.00 2-16 2003 Hewlett-Packard Development Company. Note: A system may belong to only one cell. The Data Protector Cell configuration can reflect the organization within a company.hp. A Data Protector Cell consists of a Cell Manager system and all of the systems that are to have backup managed by it.com . It is also possible to have a cell that contains only one system (called a single-system cell). A cell can be all the systems within a department. U1610S B.Module 2 Data Protector Overview and Architecture 2–8.P. http://education. there is no reason that two machines. Later in this module you will see how to estimate more accurately the size of your Data Protector internal database. They are administered and operate independently of each other.Module 2 Data Protector Overview and Architecture There is no enforced limit to the number of systems per Data Protector Cell. A good rule of thumb is that you should allocate enough disk space to allow the internal database be approximately 2% of the quantity of data that is backed up.hp. all backups are configured according to the Cell Manager’s clock. some of the Data Protector messages can be confusing.00 2-17 2003 Hewlett-Packard Development Company.25%. Data Protector has the capability to monitor and administer all the cells from a central administration point utilizing the Cell Console or Enterprise Console or the Manager of Managers console. although 100 is recommended • The size of the Data Protector internal database • The quantity of backups that can be effectively managed The Data Protector internal database can grow to be many GB. Backing up many small files means more records in the database.) Which Factors Should Be Considered when Defining Cells? • • • • • • Systems that have a common backup policy Systems that are on the same LAN Systems administered by the same people Systems within the same time zone Systems should use time synchronization Systems in the same Windows Domain (for simpler administration) Cells are generally independent parts of the enterprise network. L.P. but the cell size may be limited by a number of factors: • The maximum supported number of systems is 1000. (The module on Database Management will give more specifics about how to plan for and manage database growth. http://education.com U1610S B. You may find that if you are backing up many large files (50 MB–100 MB each). NOTE: If systems in the same cell are in different time zones. this is especially true when backing up large database files. . In addition. then the percentage size of the database compared to data can be as little as 0. which means more space is required for the database. Module 2 Data Protector Overview and Architecture 2–9.com . SLIDE: Client/Server Modules Client-Server Modules cell console (CC) cell manager (CM) media agent (MA) disk agent (DA) Student Notes Data Protector is composed of separate modules. L. each of which performs a specialized task. The major component is the Cell Manager.00 2-18 2003 Hewlett-Packard Development Company. Client/Server Architecture The basis of the client/server model is that the Data Protector software consists of client modules and a server module.P. U1610S B. http://education. These modules can all be installed on a single node (a single node cell) or be distributed across many nodes.hp. Communication between modules is accomplished via TCP/IP sockets. it is responsible for the control of the entire Data Protector Cell and the invocation of the specialized agent processes. http://education.hp. 2003 • Sun Solaris 7.8. the Cell Manager. Backup Agent (with the Disk Agent) and various Application Agents. versions. Platform_Integrtn_SptMtx.com U1610S B.Module 2 Data Protector Overview and Architecture 2–10. .9 • SunOS • IBM AIX • Linux Redhat/SuSE/Caldera • Novell NetWare • SGI IRIX • Windows NT-Alpha • SCO OpenServer • SCO Unixware • SNI SINIX • NCR MP-RAS • Sequent DYNIX • Additional platforms via NFS / shared disk (CIFS) Catalog/Media Database: • files. L.1.pdf This document (found in the Docs/doc directory) contains details about platforms supported for Data Protector 5.P.00 2-19 2003 Hewlett-Packard Development Company. including all integrations with third party software products. hosts • media. drives. Informix • Lotus Domino • MS SQL Server • MS Exchange Server • MS VSS • MS Cluster Server • HP MC ServiceGuard • HP OpenView Operations • HP OpenView OmniStorage Media Agent: • Windows • HP-UX • Sun Solaris • IBM AIX • Linux Redhat/SuSE • Novell NetWare • HP MPE/iX • SCO OpenServer • SNI Sinix Disk Agent: • HP-UX 11. Included in the product documentation you will find several release specific documents describing the supported platforms and integrations. libraries Student Notes The Data Protector product consists of several product components: the Manager of Manager.X • HP OpenVMS • HP Tru64 UNIX • HP MPE/iX • Win NT. SLIDE: Platform Support Platform Support Cell Manager: • HP-UX • Windows • Solaris Application (Integration) Agents • Oracle • Informix • IBM DB2 UDB • Sybase • SAP R/3 • Baan IV on Oracle. Backup Device Manager (with the Media Agent). XP • Win 2000. 00 2-20 2003 Hewlett-Packard Development Company. The UNIX Cell Manager system always has three daemon processes running to provide Data Protector services: crs Cell Request Server mmd Media Management Daemon rds Raima Database Server The Windows Cell Manager system always has three service processes running to provide Data Protector services: Data Protector CRS Cell Request Server Data Protector Inet Remote Connection Server Data Protector RDS Raima Database Server In the Windows environment. and media management sessions.start. U1610S B.exe) not as a service. (mmd. L.status options Internal database Session managers Scheduler Cell Console and agents Installation server (optional) Cell Manager Daemons (Services) CRS RDS MMD Cell Console IDB Session Managers Disk. SLIDE: Cell Manager Cell Manager HP-UX.Module 2 Data Protector Overview and Architecture 2–11. Solaris Manually installed Provides: Background daemons/services manage with omnisv stop. Media and Integration Agents Student Notes The Cell Manager is the key component of a Data Protector Cell.com . and is responsible for the starting of backup. Windows. the MMD runs as an application process. It contains the Data Protector database.P. http://education. restore.hp. If a new session is started. once they are installed with the Cell Manager.00 2-21 2003 Hewlett-Packard Development Company. and check on the status of these services. an additional Session Manager is generated.hp. start. L. A dedicated Session Manager controls the clients for each operation. -start. http://education. -status. =============================== Status: All Data Protector relevant processes/services up and running.com U1610S B. they are: -stop. A program has been provided to stop. . the program name is omnisv.P. There are three options available for the omnisv program. Session Managers The Cell Manager listens for session requests and starts the appropriate Session Manager.sh program used in previous versions Sample output from omnisv: C:\Program Files\OmniBack\bin>omnisv -status ProcName Status [PID] =============================== rds : Active [3348] crs : Active [3040] mmd : Active [1400] omniinet: Active [3312] Sending of traps disabled. bsm rsm dbsm msm asm Backup Session Manager Restore Session Manager Database Session Manager Media Session Manager Administration Session Manager These session manager programs will reside in the /opt/omni/lbin directory on UNIX and C:\Program Files\Omniback\bin (default) on Windows. and the C:\Program Files\Omniback\bin directory on Windows. which in turn starts the required clients.Module 2 Data Protector Overview and Architecture Daemon/Service Control The manager programs will reside in /opt/omni/lbin directory on Unix. The three services/daemons will normally be started when the system boots up. Default program locations: (UNIX) /opt/omni/sbin/omnisv (Windows) C:\Program Files\Omniback\bin\omnisv Note: omnisv replaces the omnisv. 000 per day) • 100 parallel backup sessions (UX. L. To reach the 50 directory limit changes to the global options file (covered later) must be made. The file names database file is initialized with a 2GB (2047MB) maximum size by default.000. supported limits.000 Media MMDB • 1. but may be extended in up to 4 GB increments to a default maximum of 10 directories. they are: DCBF CDB MMDB The detail catalog binary files The catalog database The media management database The IDB has several defined.com .00 2-22 2003 Hewlett-Packard Development Company.hp. http://education.000 Sessions (max 2. Each extension directory may contain up to 10.) DCBF CDB • 450 Million File Names on Windows (est. The three main structures are shown above. SLIDE: Internal Database Size Limits Internal Database Size Limits • File Versions (10x # of file names) • 50 directories (containing binary files) • 4 GB per directory • 10. The file versions stored in the DCBF is initially configured as one directory capable of storing up to 4 GB.P. but may be extended in up to 2 GB (2047MB) increments to a maximum of 32 GB. These limits should not be exceeded under any circumstances.000 files.000 files per directory • 700 Million File Names Unix (est.Module 2 Data Protector Overview and Architecture 2–12. the limit for file U1610S B. The limits illustrated on the slide are also available from the product Release Notes document that ships with the product. The minimum size per extension is 1MB.) (32 GB HP-UX & Windows.000 Media per pool • 500. 30 GB Solaris) • 40. 60 Win) Student Notes The Data Protector Internal Database (IDB) is comprised of several structures that store data. Module 2 Data Protector Overview and Architecture versions is set to allow approximately 10 times the number of filenames. This represents approximately 80% of all the data stored by Data Protector. The size of the MMDB will only be approximately 20-30 MB. L.hp.P. http://education.com U1610S B. .00 2-23 2003 Hewlett-Packard Development Company. Note! The spreadsheet must be copied to an appropriate system to view and use the tool.com .00 2-24 2003 Hewlett-Packard Development Company. http://education. L. The Data Protector Concepts Guide documents the formula for each part of the database.xls.Module 2 Data Protector Overview and Architecture 2–13. SLIDE: Capacity Planning Spreadsheet Capacity Planning Spreadsheet Student Notes The capacity planning worksheet (spreadsheet) shown above is included in the Data Protector product distribution. Simply plug-in the appropriate data and the macros will calculate the amount of disk space that is needed. U1610S B. The spreadsheet is installed in the UX: doc or Windows: Docs directory on the cell manager and is called IDB_capacity_planning. which will help in planning future database growth potential. The spreadsheet contains macros. An alternate approach to using the spreadsheet is to use the documented formulas for estimating the disk space needed. The spreadsheet is the preferred method.P.hp. A system administrator or a backup operator will use the cell console to control the cell.com U1610S B. but it may also be installed on any number of clients within the cell.Module 2 Data Protector Overview and Architecture 2–14. you can access the Cell Manager remotely from the local machine. You do not have to use the Cell Manager as the central graphical user interface system. Solaris Present on all cell managers Provides: Graphical user interface Command-line interface Web reporting java interface May be further distributed from: Cell manager Media No additional license required Student Notes Data Protector provides user interfaces for the UNIX and Windows platforms.P.00 2-25 2003 Hewlett-Packard Development Company. it should run on the platform that will simplify the configuration and administration of Data Protector. Windows. The Data Protector graphical user interface for Windows can be installed on any Windows NT/2000/XP/2003 system. and the Data Protector graphical user interface for UNIX http://education. Once you have installed the user interface on a system in the cell. The user interface is commonly referred to as the Cell Console. Both UNIX and Windows platforms include the following components: • Graphical user interface • Command line interface • Java based reporting interface The user interface is installed as a Data Protector software component onto the Cell Manager system. although the user interface is installed there by default. L.hp. It is common practice to install the Cell Console user interface on both UNIX and Windows clients within the same cell. . SLIDE: Cell Console (User Interface) Cell Console (User Interface) HP-UX. Therefore. 00 2-26 2003 Hewlett-Packard Development Company.Module 2 Data Protector Overview and Architecture (Motif) can be installed on any HP-UX or Solaris system in the cell.hp.com .P. NOTE: The distributed Cell Console must be authorized from the User Manager interface running on the Cell Manager. L. Some additional platforms support a subset of the cell console in order to control some of the local integrations with Data Protector. You can have an HP-UX Cell Manager. Most of the Data Protector commands will reside in the bin directory. for example. http://education. when dialing in to a system for remote support. or when writing shell scripts or batch files. with the user interface installed on a Windows system. In many cases the support is for parts of the command line interface only. The commands can be used in situations where a GUI is not available. Data Protector provides a rich and powerful command line interface. Details are covered in the User Configuration module U1610S B. These programs are installed in the /opt/omni/lbin directory on HP-UX and C:\Program Files\Omniback\bin on Windows. SLIDE: Disk Agent Disk Agent May be installed from: Cell manager Media Invoked by session manager Provides disk access (read/write) Multi-vendor support Exchanges data with media agents HP.P.00 2-27 2003 Hewlett-Packard Development Company. L. Therefore.UX Tru64 OpenVMS NT/2000/XP/2003 Novell Sun Solaris Sun SunOS IBM AIX Linux Sequent DYNIX Digital UNIX SCO Openserver Silicon Graphics NCR others… Student Notes The Disk Agent module is responsible for all read and write actions to disk storage performed by the Data Protector backup and restore managers.hp.Module 2 Data Protector Overview and Architecture 2–15.pdf for a list of currently supported platforms. vbda vrda rbda rrda fsbrda dbbda NOTE: Volume Backup Disk Agent Volume Restore Disk Agent Raw Backup Disk Agent Raw Restore Disk Agent File system Browser Disk Agent Database Backup Disk Agent (for internal database) Refer to the Platform_Integration_SptMtx. The Disk Agent module consists of specialized processes that are started on demand by the respective Backup or Restore Manager process. http://education.com U1610S B. . you must have a Disk Agent module installed on the client system. in order to back up or restore a client node. Module 2 Data Protector Overview and Architecture 2–16.00 2-28 2003 Hewlett-Packard Development Company. U1610S B. a Media Agent module must be installed on the client system to which the backup device is physically attached. Restore or Media Manager process. The Media Agent module consists of specialized processes that are started on demand by the respective Backup. These programs are installed in the <omnihome>/lbin directory on Unix and <omnihome>\bin on Windows: bma rma mma cma uma NOTE: Backup Media Agent Restore Media Agent Media Management Agent Copy Media Agent Utility Media Agent Refer to the Platform_Integration_SptMtx.P. .com . Therefore.hp. in order to utilize such devices for backup or restore. SLIDE: Media Agent Media Agent May be installed from: Cell manager Media Invoked by session manager Provides media access Multi-vendor support.pdf for a list of the currently supported platforms. L. restore and media managers. Exchanges data with disk agents HP.UX NT/2000/XP Novell Linux Sun Solaris IBM AIX Siemens SINIX Student Notes The Media Agent module is responsible for all read and write actions performed to tape by the Data Protector backup. http://education. com U1610S B. EVA. . Data Protector also provides integrations with many other applications that assist in areas such as high availability. EVA.Module 2 Data Protector Overview and Architecture 2–17. VA. SLIDE: Integration Agent Integration Agent Distributed by cell server Database and application integrations Integrates with vendors API/ backup and restore tools Invoked by session manager Executed during backup and restore of databases Works with disk and media agents Multi-vendor support SAP SAP R/3 R/3 Oracle Oracle Informix Informix DB2 DB2 Sybase Sybase MS MS SQL SQL MS MS Exchange Exchange Lotus Lotus Domino Domino IT/Operations IT/Operations Manage/X Manage/X OmniStorage OmniStorage MC/ServiceGuard MC/ServiceGuard MSCluster MSCluster StorageWorks StorageWorks XP. MSA MSA EMC EMC Student Notes Data Protector provides a set of integration modules that enable data to be exchanged between the most popular databases and Data Protector.hp. Data Protector hooks into the vendors API in order to perform online backups and restores. VA.00 2-29 2003 Hewlett-Packard Development Company. The ability to perform online backups is a highly desirable feature in mission-critical. high-availability environments. system control. and monitoring. XP. Database Integrations • • • • • • • • SAP R/3 Oracle Informix IBM DB2 UDB Sybase MS SQL MS Exchange Lotus Notes/Lotus Domino http://education.P. L. NOTE: Refer to thePlatform_Integration_SptMtx. Data Protector clients may be cluster members with HP MC/ServiceGuard. No additional license is needed for the integrations. and applications.hp. and /opt/omni/doc/C/support_matrices on UNIX.com .pdf for a list of the currently supported versions of databases.pdf U1610S B. These integrations require special licenses in order to operate.Module 2 Data Protector Overview and Architecture Application/Device Integrations • • • • • • • • • • HP OpenView Operations HP OpenView Manage/X HP OpenView OmniStorage HP MC/ServiceGuard HP StorageWorks Disk Array (Zero Downtime backup) MS Cluster MS Volume Shadow Copy Service (VSS. platforms. Both products are cluster solutions that allow the Data Protector Cell Manager to be a virtual server. Windows 2003 only) EMC Symmetrix (Fastrax) GRAU DAS StorageTek ACSLS Data Protector and High Availability The Data Protector Cell Manager system integrates with the HP MC/ServiceGuard and MS Cluster Server products to provide high levels of application availability. http://education. L. and Veritas clusters. HP StorageWorks and EMC Symmetrix integrations provide special capabilities to allow data on their disks to be backed up without downtime.P. This Document is located in the C:\Program Files\OmniBack\Docs\support_matrices directory on Windows. Additionally.00 2-30 2003 Hewlett-Packard Development Company. MS Cluster Server. Platform_Integrtn_SptMtx. the particular Installation Server from which the software is to be obtained is specified. 11. Unix and Windows Cell Managers must maintain two separate Installation Servers.hp. 11. The following platforms may be used for the Installation Server: • Windows NT 4.06. The Installation Server must be registered as such with a Cell Manager. Windows 2003 (32-bit) • HP-UX 11. L. 8 & 9 http://education. Windows 2000.11.00 2-31 2003 Hewlett-Packard Development Company. When the Cell Manager system pushes agent software to a client system. The Installation Server does not need to be a client/agent of the Data Protector cell for which it provides installation services. Data Protector software patches must be applied to the Installation Servers(s) and then distributed to clients during an update/push from the Cell Manager. and may provide installation services for more than one cell.0. and Solaris platforms Used separately by UNIX and Windows clients Distributes the installation load May be used by multiple cells HP-UX Solaris Windows Student Notes The Installation Server acts as a repository for the agent software modules. SLIDE: Installation Server Installation Server Manually installed Repository for agent software Must be registered with cell manager HP-UX. . Windows XP PRO.P.Module 2 Data Protector Overview and Architecture 2–18.com U1610S B. Windows.20 • Solaris 7. one for each platform. Module 2 Data Protector Overview and Architecture 2–19. L. The slide above illustrates the location of the processes that execute on the various systems.com .00 2-32 2003 Hewlett-Packard Development Company.hp. as well as their roles. http://education. SLIDE: Typical Backup/Restore Session Typical Backup/Restore Session cell server request crs start rds session catalog read/write cell console connect IDB bsm control/report media agent control/report disk agent ma write data da read Student Notes There are several processes that execute while backup or restore jobs are executing. and does not flow through the manager. NOTE: Acronyms: CRS RDS BSM IDB DA MA Cell (Request) Server (Raima) Database Server Backup Session Manager Data Protector Internal Database Disk Agent Media Agent Data from the backup flows directly between the agents. U1610S B.P. L. all IPC channels are carefully designed to avoid communication bottlenecks.P.hp.com U1610S B. SLIDE: Inter-process Communication Inter-process Communication (IPC) cell console network backup/restore disk agent local backup/restore tcp/ip cell manager tcp/ip disk agent tcp/ip scheduler shared memory session manager media agent session manager tcp/ip tcp/ip media agent Student Notes Data Protector is a distributed application and relies heavily on multiple cooperating local and remote processes. Its IPC mechanisms are designed and implemented with great care to maximize system response time and data throughput. This significantly increases the overall data throughput rate for a backup session. Data Protector uses the following fast and reliable IPC mechanisms. http://education. Data Protector concentrates on simple bi-directional messaging for both data and message transfer. available on all major platforms today: Shared Memory (shmem) + Pipe/Socket (Local) When data is transferred between Disk and Media Agent processes that reside on the same system. . For this reason. shared memory is used for transferring data. Notification and control is implemented via a pipe mechanism.00 2-33 2003 Hewlett-Packard Development Company. a local backup is always preferable to a network backup. As both network capacity and backup device speed are expected to increase significantly during the lifetime of the Data Protector product.Module 2 Data Protector Overview and Architecture 2–20. hp. http://education. depending on the request it has received. Starting Remote Processes Data Protector uses the standard inet (inetd) facility to start up remote processes. This mechanism requires that a fixed port number be allocated for Data Protector.conf. This number must be identified in the global (in addition to the Windows Registry) file before installing the clients. and uses the following mechanism to achieve this: 1.00 2-34 2003 Hewlett-Packard Development Company. but it may vary from cell to cell. The Data Protector session manager invokes specific agent processes. The session manager connects to the system on which it wants to start a media or disk agent process via the predefined port number. Stream sockets are also used for Disk and Media Agent data transfer if the agents do not reside on the same host. Within a Data Protector Cell. 5555. On Windows systems.P. etc. Full network transparency is accomplished with the networking software. all systems must have the same port number configured. 3. there will be a Data Protector Inet service running to handle network requests on the defined listening port.Module 2 Data Protector Overview and Architecture Standard TCP/IP Socket Interface (Remote) The Data Protector session manager processes use the inetd daemon (on Unix) to start up remote agents. 5555. the inetd daemon process is listening on port 5555 and starts the HP Data Protector inet process.com . (This assumes the system security). The Data Protector inet process then starts the desired agents. 2. If this port is already in use. On the Windows platforms. L. At the Unix Agent host. The default port number used is 5555. The session manager sends a control block that informs the remote system exactly what agents to start and what ports are to use for communication. Windows registry path for the global port (5555): HKEY_LOCAL_MACHINE -SOFTWARE -Hewlett-Packard -OpenView -OmniBackII -Common -Parameters InetPort 5555 U1610S B. Data Protector can use another port number. 4. as defined in the /etc/inetd. The stream socket connections are a natural message-passing medium for them. the Data Protector inet service is already running on port 5555 to handle incoming requests. Directory Path /opt/omni /opt/omni /opt/omni/bin /opt/omni/sbin /opt/omni/lbin /opt/omni/databases /opt/omni/lib /opt/omni/lib/man /opt/omni/doc Contents <OMNIHOME> (documentation convention) Data Protector home directory Commands and GUIs Admin only tools Local binaries (agents. L. . etc.com U1610S B. SLIDE: Cell Manager Directory Structure (UX) Cell Manager Directory Structure (UX) /etc/opt/omni options devices datalists schedules dlgroups dltemplates rptgroups rptschedules barlists barschedules sap snmp mom acs cell rid dr users integ dr amo amoschedules /var/opt/omni db40 tmp log install utilns gui /opt/omni doc java sbin lbin bin lib databases newconfig vendor arm build man sam nls cc oracle win oracle8 da ma das opc stk sybase informix Note: these directories contain the installation server components Student Notes The following table outlines the directories used by Data Protector on the Unix Cell Manager system.00 2-35 2003 Hewlett-Packard Development Company.P.hp.) Software depots Shared libraries Man pages Product documentation http://education.Module 2 Data Protector Overview and Architecture 2–21. com .P.TMPL /etc/opt/omni /etc/opt/omni/amo /etc/opt/omni/amoschedules /etc/opt/omni/users /etc/opt/omni/cell /etc/opt/omni/devices /etc/opt/omni/dr /etc/opt/omni/datalists /etc/opt/omni/schedules /etc/opt/omni/snmp /etc/opt/omni/options /etc/opt/omni/sg /etc/opt/omni/rptgroups /etc/opt/omni/rptschedules Web Reporting (Java) components Extra copies of Data Protector configuration files.Module 2 Data Protector Overview and Architecture /opt/omni/java /opt/omni/newconfig /opt/omni/gui /opt/omni/. http://education. L. including an Data Protector database Data Protector GUI components Local startup options template for agents <OMNICONFIG>(documentation convention) Automatic media operations definitions Automatic media operations schedules User configuration directory Cell configuration directory Device templates directory Disaster Recovery data for Windows clients Backup specifications directory Backup specification schedules SNMP configuration directory Global options directory ServiceGuard configuration Report groups directory Report schedules directory /etc/opt/omni/HealthCheckCon File for periodic configuration checking fig (customizable) /etc/opt/omni/Notifications /etc/opt/omni/barlists/ /etc/opt/omni/barschedules /var/opt/omni /var/opt/omni/log /var/opt/omni/tmp /var/opt/omni/db40 Event Notifications Backup and Restore lists for integrations Schedules for barlists <OMNIVAR>(documentation convention) Log files Temporary file area Data Protector database U1610S B.00 2-36 2003 Hewlett-Packard Development Company.omnirc.hp. may be relocated during installation process) Commands and GUIs Installation scripts Data Protector Database Configuration directory Cell configuration directory Driver for disaster recovery http://education. SLIDE: Cell Manager Directory Structure (Windows) Cell Manager Directory Structure (Windows) <product_home> bin log Config NewConfig java obdr db40 help Docs lib tmp Depot amo amoschedules Barlists Barschedules CDROM Integ tmp cell options Sessions Datalists Schedules dr mom devices xcopy rid SNMP dlgroups rptgroups rptschedules i386 dltemplates Install Users utilns setupdir acs sap oracle cc ost win da ma das opc stk sybase Note: these directories contain the installation server components. Student Notes No files are outside the <OMNIHOME> tree.hp.00 2-37 2003 Hewlett-Packard Development Company.com U1610S B. L. The database and all log files are kept under the <OMNIHOME> tree. . Directory Path <OMNIHOME> (default install dir) (C:\Program Files\Omniback <OMNIHOME>\bin <OMNIHOME>\bin\install <OMNIHOME>\db40 <OMNIHOME>\config\ <OMNIHOME>\config\cell <OMNIHOME>\config\CDROM Contents Data Protector home directory (default.Module 2 Data Protector Overview and Architecture 2–22.P. hp.com .00 2-38 2003 Hewlett-Packard Development Company.Module 2 Data Protector Overview and Architecture <OMNIHOME>\config\users <OMNIHOME>\config\amo <OMNIHOME>\config\amoschedules <OMNIHOME>\config\dr <OMNIHOME>\config\devices <OMNIHOME>\config\Datalists <OMNIHOME>\config\Schedules <OMNIHOME>\config\Barlists <OMNIHOME>\config\Barschedules <OMNIHOME>\config\mom <OMNIHOME>\config\Integ <OMNIHOME>\config\rid <OMNIHOME>\config\schedules <OMNIHOME>\config\snmp <OMNIHOME>\config\options <OMNIHOME>\config\Oracle <OMNIHOME>\config\SNMP <OMNIHOME>\java <OMNIHOME>\Docs <OMNIHOME>\depot <OMNIHOME>\man <OMNIHOME>\help <OMNIHOME>\NewConfig <OMNIHOME>\OBDR <OMNIHOME>\tmp <OMNIHOME>\log User configuration Automatice Media Operations definitions Automatic Media Operations schedules Disaster Recovery data for cell clients Device templates Backup specifications Backup specification schedules Backup and restore lists for integrated 3rd party products Barlist schedules Manager of Managers configuration Configurations for 3rd party products Recovery information data used for disaster recovery (Omniback 4. http://education. L.P.x) Backup schedules SNMP trap destination and OVO configuration directory Data Protector global options Oracle configuration SNMP trap delivery configurations Integrated Web Reporting java client Product manuals in PDF format Software depot files for Installation Server Data Protector help pages (word-pad files) Online help files Unmodified copies of the configuration files and Data Protector database One-Button disaster recovery files Temporary files Data Protector log files U1610S B. .00 2-39 2003 Hewlett-Packard Development Company. http://education. SLIDE: Client Directory Structure (UX) Client Directory Structure (UX) /etc/opt/omni cell install customize /var/opt/omni log tmp newconfig bin lib /opt/omni lbin lib databases sbin vendor nls sap acs oracle cc win oracle8 da ma das opc stk sybase informix Note: these directories contain the installation server components.Module 2 Data Protector Overview and Architecture 2–23.P.hp.com U1610S B. L. Student Notes The directories used on the Unix clients are a subset of the directories used by Data Protector on the Unix Cell Manager system. http://education. U1610S B.P.00 2-40 2003 Hewlett-Packard Development Company.hp.com .Module 2 Data Protector Overview and Architecture 2–24. SLIDE: Client Directory Structure (Windows) Client Directory Structure (Windows) <product_home> bin log config Depot obdr db40 help Docs man tmp java bin NewConfig dltemplates Install cell tmp i386 utilns setupdir acs sap oracle cc ost win da ma das opc stk sybase Note: these directories are part of the installation server. Student Notes The directories used on the Windows clients are a subset of the directories used by the Data Protector on the Windows Cell Manager system. L. 00 2-41 2003 Hewlett-Packard Development Company.P.hp. L.com U1610S B. the Data Protector default configuration and options are adequate for everyone. typically time-outs. which allows you to customize Data Protector. is found in the following locations: On Unix Systems <OMNICONFIG>/options/global On Windows NT Systems <OMNICONFIG>\options\global How Global Options Work http://education. However. Global Options File Global options cover various aspects of Data Protector. The global options file. SLIDE: Global Options Global Options • Centrally managed • Product defaults (documented) • Customizable <config_dir> options global Student Notes In most situations. . All global options are explained in the global options file.Module 2 Data Protector Overview and Architecture 2–25. and limits and affect the entire Data Protector cell. many options can be changed to affect the behavior of the product for large and more complex environments. uncomment the line that has the option name and set appropriate value. or pound sign (#). Average users should be able to operate the product without changing them. The options file contains many of the Data Protector defaults. The amount of time spent waiting for a device. (default 0) Increases the default limit of 32 concurrent devices per backup session (maximum is 64). simply remove the ”#” mark. Change the fields and their order in the Devices & Media context.P. but is only used if the items are uncommented. To uncomment a line. Commonly Used Variables The following list includes the most often used global variables. this is the backup queuing time. How To Use Global Options To use a global option. This means that it does not affect Data Protector. 12:00) Scheduled daily cell checking (default. (default is 60 minutes) Determines if pre/post execs are executed during the preview mode. http://education. (default is 15 minutes) U1610S B. off) The amount of time that the SM will wait for a pre/post exec script to complete. L. This file may be modified whenever the need to affect the options in the file is necessary.00 2-42 2003 Hewlett-Packard Development Company. Prevents Data Protector from automatically initializing blank or unknown tapes when using a loose media policy.hp. Motif. which comments out the option.com . (default is 0. DailyMaintenanceTime DailyCheckTime Port MediaView: MaxBSessions: InitOnLoosePolicy: MaxMAperSM: SmWaitForDevice: ExecScriptOnPreview: ScriptOutputTimeout: Scheduled daily maintenance time (default. Each option currently in the file has a hash mark. and the command line interface) and all Cell Manager programs. Increase the default limit of five concurrent backups. These options are not directly distributed to disk or media agents. See the Global file for a complete description. 12:30) Default listening port for the inet process.Module 2 Data Protector Overview and Architecture Option settings from this file are available to all user interface programs (Windows. Even advanced users should not use them unless specifically required by documentation or an HP support representative. The Disk and Media Agents use the values of these options ad environment variables. These variables are found in the following locations: /opt/omni/.hp. L.omnirc on /usr/omni/. affecting the behavior of the Data Protector client only.Module 2 Data Protector Overview and Architecture 2–26.00 2-43 2003 Hewlett-Packard Development Company. SLIDE: Localized Options Localized Options • Locally managed • Agent parameters • Customizable <product_home> omnirc/.tmpl copy/modify Student Notes Using omnirc Options The omnirc variables are most useful for troubleshooting or overriding other settings.omnirc on <omnihome>\omnirc on sys:\usr\omni\omnirc HP-UX and Solaris other UNIX clients Windows NT clients on NetWare clients http://education.com U1610S B.P. .omnirc omnirc. Allows a user to disable any remote session pre.omnirc.TMPL.Module 2 Data Protector Overview and Architecture How to Use omnirc Options Installation provides a template for omnirc file (. http://education.P. if the agent does not get an acknowledgement in OB2RECONNECT_ACK seconds. then it will assume that the socket connection is no longer valid.omnirc) and edit it. depending on the platform). as well as improving performance. copy the template file to omnirc (or .TMPL or omnirc. In other words. Allows a user to restrict or disable any object pre. Changes the sleep time between each retry while loading a device. restarting is not required when adding or changing entries. the WAN line between the Backup Session Manager and agents cannot be down more than OB2RECONNECT_RETRY seconds. To create an active omnirc file.com .hp.and post-exec scripts defined in backup specifications for a specific client. OB2VXDIRECT: OB2ENCODE: OB2OEXECOFF: OB2REXECOFF: OB2DEVSLEEP: OB2RECONNECT_RETRY: Defines how long Data Protector should wait before trying to reconnect after a socket connection has been broken (the default is 1200 seconds). verify its permissions.00 2-44 2003 Hewlett-Packard Development Company. Allows a user to always turn on data encoding regardless how the backup options are set in the backup specification. This file is not active. This is mandatory for the crs daemon on UNIX and recommended for Data Protector CRS and Data Protector Inet services on NT. Specifically on NT. On UNIX. When creating the omnirc file (either by copying or by using an editor). OB2RECONNECT_ACK: Defines how long Data Protector should wait for the message of acknowledgement (default 600 seconds). uncomment the line (remove the # character) and edit the value if necessary. Enables direct (without cache) reading for Advanced VxFS file systems. permissions will be set according to your umask settings and may be such that some processes may be unable to read the file. When changing omnirc file. U1610S B. only when removing entries (or renaming the file). Most Often Used Variables Some commonly used omnirc variables include: OB2BLKPADDING Allows specification of blocks to be pre-pended to all tapes of a certain type to overcome length mismatches while copying.and post-exec scripts for a specific client. the Data Protector services/daemons on the affected system must be restarted. To use a specific option. Set the permissions to 644 manually. L. In other words. How many Data Protector cells may an individual system be configured into? 6.Module 2 Data Protector Overview and Architecture 2–27.com U1610S B.P. What. L. Review: Data Protector Architecture 1.00 2-45 2003 Hewlett-Packard Development Company. Which network port must be available for Data Protector? http://education. . if any. What are the names of the five main components of the Data Protector architecture? __________________________________________ __________________________________________ __________________________________________ __________________________________________ 2. is the limit to how many systems may be in the Data Protector cell? 5. Describe the function of each of the components listed above: 3. What is the Data Protector cell comprised of? 4.hp. http://education.00 2-46 2003 Hewlett-Packard Development Company.hp. L.P.com . What are the main directories for the Data Protector programs: Unix: Windows: U1610S B. Which process or service starts the Data Protector agents? 8.Module 2 Data Protector Overview and Architecture 7. . Distribute Data Protector agents to client systems. Install and configure installation servers. you will be able to do the following: • • • • Install the Data Protector Cell Manager. Understand the basic upgrade concepts http://education.P.Module 3 — Data Protector Installation Objectives Upon completion of this module.hp. L.com U1610S B.00 3-1 2003 Hewlett-Packard Development Company. Hardware and Software Requirements Installation Servers and Cell Managers have certain hardware and software requirements. The Cell Manager is typically used as an installation server. this is an option available during the Cell Manager installation. SLIDE: Installation Sequence Installation Sequence Plan the layout of the Cell Check hardware and software requirements Install Cell Manager and Installation Server from CD Install Clients from Installation Servers using the Cell Manager GUI. http://education. If you are running Data Protector in a mixed environment. Install Cell Manager and Installation Servers Cell Manager and Installation Servers are installed directly from CD.hp. you need at least two installation servers. L.P. one for Windows and one for UNIX. One of the systems within your Data Protector Cell must be the Cell Manager. or locally from CDROM Request and Install the Permanent License Student Notes Planning Before you start to install the Data Protector software. which you should check and verify before you start installing the software.00 3-2 2003 Hewlett-Packard Development Company.com . it is helpful to understand how your Data Protector Cell should be assembled. U1610S B.Module 3 Data Protector Installation 3–1. you may install the agents on the client systems using the Data Protector GUI. or manually from the local CD-ROM. <OMNIHOME> represents: Unix: /opt/omni Windows: C:\program files\Omniback <OMNICONFIG> represents: Unix: /etc/opt/omni Windows: C:\program files\Omniback\config <OMNIVAR> represents: Unix: /var/opt/omni Windows: C:\program files\Omniback http://education. NOTE: Three symbolic names may be used throughout the rest of this manual for paths to various files and directories.P.00 3-3 2003 Hewlett-Packard Development Company. Licensing An Instant-On license is automatically created when the product is first installed. L.com U1610S B. . during which time you must apply for and install a permanent license. This gives you usage for 60 days.hp.Module 3 Data Protector Installation Install Clients After you have installed the Cell Manager and Installation Servers. pkgrm omnisetup Microsoft Installer (setup. 9 platforms.1 client Student Notes Planning Installation of the Data Protector A.exe) ftp.1.05. No installation server is capable of supporting Novell or MPE/iX clients in any way.1 Windows Installation Servers should be in the same Windows domain with the clients that are to be installed. unpack Install script (nwinstall) Installation Server Unix Windows √ √ √1 √ 1) Installation server does not support Dynix. L.exe) PCSI installation file (dpvmskit) Setup program (setup.P. swremove pkgadd.10 version uses native installation tools on major platforms: HP-UX. U1610S B.hp.x or Solaris 7. and Windows (MSI 2.00 3-4 2003 Hewlett-Packard Development Company. Solaris. These clients must be installed and maintained locally. http://education. Unix Installation server can be hosted on HP-UX 11. SCO Unixware 7.com . SLIDE: Installation Methods Installation Methods Target platform HP-UX Solaris Other Unix Windows OpenVMS Alpha MPE/iX Novell Installation tools swinstall. 8. The above table summarizes installation methods and Install Server availability.1.0).Module 3 Data Protector Installation 3–2. They all are capable of supporting every supported Unix client with the following exceptions: • • Dynix client SCO Unixware 7. If not specified.P. component-list is a comma-separated list of component codes. current directory is taken. Located on CD for HP-UX or Solaris. in sub-directory: LOCAL-DP-AGENT-INSTALL Only ksh shell is supported Detects and upgrades previously installed components including the Cell Manager and Internal Database Checks and validates specified components Client host can be imported automatically The new installation script omnisetup.sh: • • • • • New installation of Data Protector 5.0 Upgrade of Omniback-II 4.hp.x Upgrade of Omniback-II 3.5x New local installation (upgrade) of Unix clients Usage: omnisetup. name is an optional name of the cell server host.Module 3 Data Protector Installation Omnisetup. L.sh for local installation of Unix clients performs all required steps.sh (install clients manually or upgrade cell manager) The following types of local manual installations are supported with omnisetup. No spaces are allowed.com U1610S B. http://education. and core and core-integ components need not to be specified.1 Upgrade of Data Protector 5.sh [-source directory] [-server name] [-install component-list] − − − • • • • • directory is the location where installation CD is mounted.00 3-5 2003 Hewlett-Packard Development Company. . sh script walks through the list of available components (listed above). generic ma. Reinstall (da) Disk Agent (YES. (da) Disk Agent is already installed.com .1: If DP 5. no. http://education. it checks the presence of the component name in the -install parameter.1 exists on the system and a specified component is already installed. quit)? If -install option is specified. no. If the -install parameter is not specified. the omnisetup script provides a prompt. then the behavior is as it would be a new installation. L. and cc components.P. or if a component is not found on the system. and none of the remaining ones In case of an upgrade to DP 5.Module 3 Data Protector Installation Omnisetup will attempt to install the subset of the following components. The exact list of the components is subject to availability on the particular platform. U1610S B.hp. the user is prompted similar to the following: Install (da) Disk Agent (YES.00 3-6 2003 Hewlett-Packard Development Company. quit)? Default answer is YES for da.g. cc da das acs ma informix lotus oracle8 oracle sap Cell Console Disk Agent DAS Media Agent ACS Media Agent Media Agent Informix Integration Lotus Notes Integration Oracle8 Integration (also used for Oracle 9) Oracle7 Integration SAP R/3 Integration In case of a new installation: The omnisetup. For each component that can be installed on the host. e. YES No Quit Install this component Do not install this component Do not install this component. and NO for any other component – all subject to availability of the component on the host. 05. After the component is installed. For automatic removal. the script saves the omnirc file. the only way that the script does not install CORE component is that user selects no component for installation or reinstallation (always answers NO).Module 3 Data Protector Installation In case of an upgrade of Omniback II components: If an Omniback II version has been detected a prompt will be displayed: An older version of the product already exists on the system. if -install parameter was not specified. then it compiles a list of already installed components (in -install parameter format). the script ends with brief instructions on how to remove previous product and where to obtain additional information. a list compiled before product removal is used (and no further prompt is issued). it removes /usr/omni (or /opt/omni) directory. subsequent media agents are not prompted for.com U1610S B. . You can remove existing product manually. execute rm –fr /usr/omni Please refer to Installation Guide for additional information Automatic If automatic removal is selected.10 is installed. omnisetup continues as it were a new installation. If user confirms. It must be removed before data protector A. a message appears: (da) Disk Agent installed. it aborts with the message: Removal of previous installation FAILED. The first time any component is selected for installation or reinstallation.hp. CORE-INTEG component is automatically installed (reinstalled if already there). the component is unpacked and installed. Subsequent components do not trigger installation of CORE component. http://education. This is most likely because some process is running and is blocking deletion of files. L.P. If not successful.00 3-7 2003 Hewlett-Packard Development Company. make sure no related processes are running 2. How would you like to remove existing product (MANUAL. Please remove the product manually. the first time any integration component is selected for installation or reinstallation. make sure that no related process runs. To remove a previous version of data protector: 1. If an automated removal of previous version is successful. However. Once a media agent is selected. CORE component is automatically installed (reinstalled if already there). In other words. Finally. Similarly. devtab file…) created after installation of the product by the user 3.automatic)? Manual If manual removal is selected. save any user settings (such as omnirc file. or proceed with the installation script that will do it for you. 0” INSTALLTYPE=type INSTALL=components OMNI_PATH=home-directory USERNAME=crs-account PASSWORD=crs-password HOSTNAME=cell-server log-file It is possible to install hp OpenView Storage DataProtector A.hp./omnisetup. If the host specified cannot be contacted.com .if all are specified. http://education. but cell_server file is available.cc. or if no host was specified and cell_server file is not available. installed client is automatically imported into the cell.00 3-8 2003 Hewlett-Packard Development Company. user will be able to list components that are to be installed as a parameter.sh –server testbox –install da. but client was not imported into a cell. Client or 3.10 1. Automating Windows Installation • • Scriptable installation on windows system using ‘msiexec’ Capable to install DP 5. user is reminded to import client into cell: Installation completed. Alternatively. In exactly the same manner Oracle8 Integration overrides Oracle Integration. Misspelled components and components that do not apply to the system are skipped with no message. .ma. For each component that is installed a message will appear (as stated above). Client was imported into a cell.05. Installation Server U1610S B.0 CM. Please import a client manually.informix Parameters are NOT checked. Installation completed. Cell Manager or 2. “das agent” is selected). only the first is installed (in the order stated in the above table . L. If host name was not specified.P.Module 3 Data Protector Installation If the cell server host name was specified. host name will be taken from there. IS or clients with specific components msiexec /i “hp OpenView Storage DataProtector 5. If several media agents are specified. . .05.10 –gui A.P..msi” INSTALLTYPE=CLIENT INSTALL=”-da A.00” OMNI_PATH=”c:\Program files\OmniBack” /qn /L!* <logfile> msiexec /i “hp OpenView Storage DataProtector 5.1" INTALLTYLE=type INSTALL=components OMNI_PATH=home-directory USERNAME=crs-account PASSWORD=crs-password HOSTNAME=cell-server /qn /L!* log-file Applies to Value Description Cell Manager Client Install.10 –ma A.10” OMNI_PATH=”c:\Program files\OmniBack” /qn /L!* <log-file> Only basic error checking is performed.. msiexec is part of Microsoft Installer.10” OMNI_PATH=”c:\Program files\OmniBack” USERNAME=<CRS account name> PASSWORD=<CRS account Password> /qn /L!* <log-file> msiexec /i “hp OpenView Storage DataProtector 5.00 is to be installed. <log-file> contains further information on this.Local installation of Cell Manager CLIENT….05. http://education.. However. a password for CRS account must be specified in clear text..10 –ma A. .. Name of the account under which CRS service runs. when installing a Cell Manager. Password for the account under which CRS runs.Local installation of Installation server List of components.05.05.05.1.hp. Each component is preceded by a hyphen (dash) and followed by a component version.10 –ma A.Local installation of client IS……..1.. Name of the log file √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ Examples for CM..05...05.05. the installation is aborted.05.. Name of the host that acts as a cell server.Module 3 Data Protector Installation From the command line (or batch file) using the following sytax: msiexec /I "hp OpenView Storage DataProtector 5.00 3-9 2003 Hewlett-Packard Development Company. client and IS installation msiexec /i “hp OpenView Storage DataProtector 5. Server Type Components homedirectory crs-name crs-password cell-server log-file CM.msi” INSTALLTYPE=IS INSTALL=”-is A.com U1610S B. Folder where Data Protector A. L.10 –gui A.msi” INSTALLTYPE=CM INSTALL=”-da A.10 – is A. Enclose list in double quotes.05.1. In case of an error. hp.sh script on the CD-ROM as described earlier.51 HP-UX version 4.1.Module 3 Data Protector Installation 3–3.0.1 HP-UX version 4.1 is supported as an upgrade from previous versions of OmniBack as well as Data Protector as shown above.5 are not supported for upgrade directly to 5. Similar to the UX Cell Manager.0 HP-UX version 4. When automatic is chosen. SLIDE: Supported Upgrades Supported Upgrades HP-UX version 3. first the core part of the database is converted to the new structure. Windows Cell Managers will automatically detect and upgrade Omniback or Data Protector while running the setup. stop the OmniBack or Data Protector daemons (/opt/omni/sbin/omnisv –stop) then use the omnisetup.1 Solaris version 5.1.5 to 5. 4.1. 5.exe from the CD-ROM.1 product will be installed. 5.1 Student Notes Data Protector 5.1 upgrade the database is converted in two steps. the older product will be removed and the 5.1.0. 5.1 all platforms version 5.1 Windows version 5.P.1 HP-UX version 5.1 Note: 5. 5. the operating system software management utilities will be used to remove (swremove/pkgrm) and then install (swinstall/pgkadd) the Data Protector components.50 Windows version 3. 5. 5.0 HP-UX version 4. To upgrade UX Cell Mangers. Versions of OmniBack prior to 3.50 Solaris version 3.0.00 3-10 2003 Hewlett-Packard Development Company. U1610S B.1. 5. When the Cell Manager is upgraded the software is replaced by the new version and the Internal Database is also migrated. 4. This will prompt for the automatic or manual update procedures.com .0.0 Windows version 4. http://education.0.1 Windows version 4.1a is a patch release for version 5.1 (same platform) version 5.0.1 Windows version 4.1 Windows version 4. L. 5.0. In the case of the 3. 5. The installation server is automatically updated as well. On Unix there are two files.1 will transfer all vital data from the old to the new database. filenames and file versions are not transferred during the core upgrade.0. The Global Options File http://education. Catalogs for unprotected objects are skipped.Module 3 Data Protector Installation then the administrator may upgrade the detail part by using Data Protector utilities described in the following sections. all Data Protector functionality is available except browsing single files and directories as well as session message reporting. The number of objects skipped is reported in the <OMNIVAR>log/upgrade.exe omnidbupgrade -udp These utilities shown above process all of the details from the CDB and import the data in the 5.log file.00 3-11 2003 Hewlett-Packard Development Company. The sessions having media that was overwritten or exported from the MMDB are removed.log is generated by the binary files and the Upgrade.5 to 5. upgrade. while the new database is initialized in the <OMNIVAR>/db40 directory. Session messages. The name db40 is used to represent the Internal Database architecture which was developed for OmniBack 4.5 database will remain in the <OMNIVAR>/db directory. Before the changes are made to the <OMNIVAR>/db/catalog it is copied to <OMNIVAR>/db/catalog. L. The session messages are also imported. The upgrade.1 IDB. Core Database Upgrade The core part of the database upgrade from 3. Note: The old 3. Detail Database Upgrade Data Protector offers the administrator both a GUI as well as command line interface for the upgrade of the detail parts of the IDB (these should be executed after the core part has completed): UX GUI Windows GUI CLI xomnidbupg idbupgwiz. this is started unconditionally as part of the upgrade.5 directory <OMNIVAR>/db/catalog has to be changed since the IDB (Velocis) has been upgraded to its version 3. . After the database core upgrade is completed.5 database may be removed at any time after the core and detail parts of the database are upgraded.hp.log.1 Much of the 3.old.5. Upgrading from version 3. and is not compatible with the old catalog contents.log is produced by the scripts used for the upgrade. The 3.com U1610S B.5 to 5.P. The entire MMDB as well as the session information is transferred.log and Upgrade. ” Obsolete parameters are merged.com . The previous setting was …. the old file is renamed to global. 4.1.0 to version 5. • U1610S B.P.00 3-12 2003 Hewlett-Packard Development Company.” Parameters that contain values in a range no longer supported are converted to comments and annotated with the string “This variable cannot be transferred automatically.1 global file as listed below. http://education.Module 3 Data Protector Installation When the Cell Manager is upgraded from 3.#.5. but converted to comments and annotated with the string “This variable is no longer in use. where # is the next available integer starting with one: • • • Uncommented parameters in the old file (active) are copied into the new file and annotated with the string “This value was automatically copied from previous version.x. or 5. L.” Comments from the old global file are not transferred to the new file.hp. the contents of the existing global file is merged into the new 5. hp. . etc).9) system.8. Disk Mirroring. Depending upon the platform. L. the Cell Manager systems are installed from local media. In the previous slide. The Cell Manager and Internal Database must be available for backup operations to be performed.UX/Solaris Cell Manager Installation Server CM IS CC push Solaris Agents Application Agents Windows Agents Application Agents Student Notes Planning the Cell • • • Which system will be the Cell Manager? Which systems will be the Installation Servers? Which systems will be Clients? The Cell Manager must be one of the following: HP-UX 11.00 3-13 2003 Hewlett-Packard Development Company.P. http://education.com U1610S B. Windows NT/2000/XP Pro/2003 or a Solaris (7.Module 3 Data Protector Installation 3–4. SLIDE: Data Protector Components Data Protector Components Windows Cell Manager Installation Server CM IS push Manual Installation/ Update Novell Agents Windows 98 Disk Agent CC MPE/iX Agents HP-UX Agents Unix Agents HP. The Cell Manager system should be reliable and ideally configured with high availability characteristics (RAID.x. this may be accomplished by way of a network depot or shared drive accessible to the native installation utilities for the respective operating systems. most of the agents can be installed on the systems via the Data Protector GUI.hp.sh from the HP-UX CD-ROM. as it is not confined to a single cell usage. Installing Linux Clients For remote installation of Linux clients.Module 3 Data Protector Installation Any supported system can be the Installation Server.P. o Log into the SYSTEM account of the OpenVMS system.COM. In a mixed environment. allocate one system to be the Installation Server for UNIX platforms and one for Windows platforms. L. Additionally the manual installation of the agents may be accomplished by using the omnisetup. Prerequisites Before you install Data Protector on the OpenVMS platform. You can install the Data Protector Disk Agent. but the files and directories placed on the disk are named OMNI*.com . This is because they do not support receiving software from an installation server. http://education.00 3-14 2003 Hewlett-Packard Development Company. MPE/IX. and CLI Interface on systems running OpenVMS/Alpha 7. After the Cell Manager and Installation Servers have been installed manually. Novell. see the release notes document (DPVMSKIT) on the Windows CDROM in the OpenVMS folder. the agents are pushed from the Installation Server under the direction of the User Interface. Creating more than one installation server for a large environment can help distribute the installation load during updates or patches to the Data Protector software.3-1 or above. and Windows 98 agents must all be installed manually from the product media. The product is called Data Protector (DP). For additional details. Installation of the OpenVMS Client The installation procedure of the OpenVMS client has to be performed on the OpenVMS system. the root user must have rights to access the system by using the exec or shell services. o Make sure that you have access to the OpenVMS client installation kit. See the HP OpenView Storage Data Protector Installation and Licensing Guide for more details. The OpenVMS. In most cases. Media Agent. This is historical due to the name change from OmniBack to Data Protector. These may enabled temporarily for the duration of the installation and then removed if desired. U1610S B. o Set the TIMEZONE features of your system by executing SYS$MANAGER:UTC$TIME_SETUP. check the following: o Make sure that TCPIP is configured and is running. • Type MA to install only the Data Protector Media Agent for Novell NeWare.00 3-15 2003 Hewlett-Packard Development Company. proceed as follows: 1. • Type DA to install only the Data Protector Disk Agent for Novell NeWare. Run the installation script: NWInstall <target server name> <NetWare version> <ALL|DA|MA> <port_number> The second parameter is Novell NetWare target server version. see the HP OpenView Storage Data Protector Installation and Licensing Guide for more details and configuration steps to backup the NDS database. http://education.Module 3 Data Protector Installation Installing Netware Clients The installation procedure of the Novell NetWare clients has to be performed from a supported Windows system that is connected to the Novell network. • The port number is optional. 2. and will default to 5555 if not specified. Run a command prompt on your Windows system and change the current path to the CD-ROM root directory.P.hp. Note that the Novell NetWare installation is not a part of the Installation Server functionality.com U1610S B. To install Data Protector on the Novell NetWare server. The installation procedure can be performed from the Data Protector Windows CD-ROM. then to the NetWare sub-directory. The Data Protector Disk Agent and the Media Agent may be installed on the systems running Novell NetWare 4. L. . There are many pre-requisites that must be satisfied before starting the installation.x or later. The third parameter defines which part of the Data Protector Novell Client will be installed: • Type ALL to install the whole Data Protector Novell NetWare client functionality. 11. Cell Manager considerations: The DP 5. 8.11. recommended 128 64. SLIDE: Installation Requirements (UX) Installation Requirements (UX) UNIX platforms: HP-UX 11. or 9 must meet the following minimum requirements: • • Free TCP/IP port: 5555 (default) 256 MB RAM (512 MB recommended) For each parallel backup session you require 40 MB of RAM and 5 -8 MB of data segment size. Hostname resolution mechanism is implemented (consistent across all systems). FTP service is enabled. U1610S B. recommended 128 64. 11. 9 Cell Component Cell Manager Installation Server User Interface Disk Agent Media Agent Integration Modules RAM (MB) Disk Space (MB) 256. 11. 11.com . Kernel parameter: maxdsiz set to a minimum of 128MB. Port 5555 is available for the Data Protector services.00 3-16 2003 Hewlett-Packard Development Company. recommended 128 340 HP-UX 380 Solaris 150 10 20 15 •The required memory (RAM) depends on the number of parallel sessions (backup requires 40MB RAM per session) Student Notes General Requirements • • • • • Networking software (TCP/IP) is installed and running.0.hp. 11. 8.0. L. Example: if you want to run 60 parallel backup sessions you require 3 GB of RAM and 512 MB of data segment size.Module 3 Data Protector Installation 3–5.P. http://education. recommended 512* 240 HP-UX + IDB 220 Solaris + IDB 64 64 64.20 Solaris 7.1 Cell Manager on HP-UX 11.20 or SUN Solaris 7. Module 3 Data Protector Installation • 220 MB on HP-UX or 240 MB on Solaris of available disk space +approximately 2% of planned data to be backed up for use by the IDB.hp.com U1610S B. Installation Server considerations: The DP 5. L.P.00 3-17 2003 Hewlett-Packard Development Company. .1 Installation Server must meet the following minimum requirements: • • 64 MB RAM (minimum) 340 MB of disk space on HP-UX and 380 MB of disk space on Solaris http://education. recommended 128 Disk Space (MB) 190 + IDB 250 100 10 20 15 •The required memory (RAM) depends on the number of parallel sessions (backup requires 40MB RAM per session) Student Notes General Requirements • • • Networking software (TCP/IP) is installed and running. 2000. U1610S B. recommended 512* 64 64 64. For each parallel backup session you require 40 MB of RAM. Example: if you want to run 60 parallel backup sessions you require 3 GB of RAM.com . L.Module 3 Data Protector Installation 3–6.0. recommended 128 64. XP or 2003 must meet the following minimum requirements: • • Free TCP/IP port: 5555 (default) 256 MB RAM (512 MB recommended). 2000. http://education. SLIDE: Installation Requirements (Windows) Installation Requirements (Windows) Windows platforms: Cell Component Cell Manager Installation Server** User Interface Disk Agent Media Agent Integration Modules NT4.P.0. recommended 128 64.hp. XP Pro and Server 2003 RAM (MB) 256.00 3-18 2003 Hewlett-Packard Development Company. Hostname resolution mechanism is implemented (consistent across all systems). Cell Manager considerations: The DP 5. Port 5555 is available for the Data Protector services.0 Cell Manager on Windows NT4. L.com U1610S B.x or later Installation Server considerations: The DP 5.00 3-19 2003 Hewlett-Packard Development Company.0 with Service Pack 6 or higher Microsoft Windows 2000 Service Pack 2 Microsoft Windows XP Professional Microsoft Internet Explorer 5.hp.0. Service Pack 6 or later. .Module 3 Data Protector Installation • • • • • 190 MB of disk space + approximately 2% of planned data to be backed up (for use by the IDB) 100 MB of free space for the User Interface components Windows NT 4.x or later Free TCP/IP port: 5555 (default) http://education.P. TCP/IP protocol from Microsoft 16 MB of disk space needed on system drive Microsoft Internet Explorer 5.1 Installation Server on Windows must meet the following minimum requirements: • • • • • • • 64 MB RAM 250 MB of disk space Microsoft Windows NT 4. You need to install only the components required in your environment. U1610S B. The software is installed from CD with swinstall. L.hp.com .config.P.Module 3 Data Protector Installation 3–7. You can skip the components for the integrations that you do not need. Check system startup file /etc/rc. allow approximately 750 MB of disk space in /opt/omni.d/omni Check if daemons are running (crs.conf file. sub-products or filesets. • Port 5555 with service omni is added to the /etc/services file (omni 5555/tcp). If the Installation Server will also be installed on this system (the default option).rds) Student Notes All Data Protector configuration files and directories.mmd. • System startup and shutdown scripts for Data Protector are added. /etc/opt/omni and /var/opt/omni • The omni service is added to the /etc/inetd. There are sub-products for all integrations. During installation a number of files are generated or changed: • The Data Protector software is installed in the following directories: • /opt/omni. http://education.conf for omni entry.00 3-20 2003 Hewlett-Packard Development Company. Within the swinstall utility you can select the Data Protector bundle or manually select the required products. as well as the Data Protector internal databases reside on this Cell Manager system. SLIDE: Installation of Cell Manager on HP-UX Installation of Cell Manager on HP-UX Configure/Check hostname resolution (DNS) Install software using swinstall Verify /etc/services for "omni 5555/tcp" and /etc/inetd. The startup control file.sd_depot. The following files are automatically configured: /sbin/init. Symbolic link to /sbin/init.d/S838omni /etc/rc.Module 3 Data Protector Installation The Data Protector installation procedure configures an automatic start and shutdown of all Data Protector processes whenever a system is rebooted. 4. http://education. Check the swinstall log file /var/adm/sw/swagent.log for errors. then click Actions -> Mark for Install. Set the OMNI variable to 1 to automatically start the Data Protector processes at boot time.Software Selection window. Post Installation Checks 1. Select Actions -> Install (analysis) to start the install process.com U1610S B. Then start the Data Protector GUI.d/omni script for Data Protector daemon shutdown.d/omni Data Protector daemon start-up script. Symbolic link to /sbin/init. Run the utility /usr/sbin/swinstall as user root. Click OK to open the Install .d/omni Installation Steps 1. /sbin/rc1. Default is 1. This script is uses the /opt/omni/sbin/omnisv command to stop and start the Data Protector daemons.d/K162omni /sbin/rc2.hp. 2.config.00 3-21 2003 Hewlett-Packard Development Company. 3. you can check that the Data Protector daemon processes are running: /opt/omni/sbin/omnisv –status 2. L.P. Insert the CD-ROM in the drive and mount it as a file system. . Specify the source as Local Directory and enter the mount point of the CD-ROM drive followed by DP_DEPOT/DP_A0510_UX11x. (This will install the cell manager. After you’ve installed the software. Select the B6960MA bundle.d/omni script for startup of Data Protector daemons. installation server and all of the on-line documentation) 5. • U1610S B.hp. This file exists on all systems within the cell. The /etc/opt/omni/cell/cell_info file exists only on the cell manager system.Module 3 Data Protector Installation Some Key Files • • The /etc/opt/omni/cell/cell_server file consists of only one line with the cell manager name.00 3-22 2003 Hewlett-Packard Development Company. It has a list of all systems belonging to that cell and what software components are installed onto each system.com . This file exists on all systems within the cell. The /etc/opt/omni/cell/omni_info file has information about which agents and Data Protector version are installed on the local system. http://education. L.P. rds and inet are services running. Check if node name resolving is enabled(DNS) Install product from CD Check for automated startup of services Check if crs.exe. On the CD-ROM.hp. you can either install the software from CD or you can use the Data Protector GUI and define from which Windows installation server you want to install Data Protector client systems. located in the i386 folder or the IA64 folder as appropriate) and you will get three options for the installation: • • • Cell Manager (includes agents and option for installation server) Installation server (only) Data Protector client (plus optional installation server) Select one of these options to continue. To install Data Protector Windows client systems. . L.com U1610S B. SLIDE: Installation of Cell Manager on Windows Installation of Cell Manager on Windows Make sure.Module 3 Data Protector Installation 3–8. During the installation procedure. http://education. execute (run) the Windows Installer Package (setup. Oracle/SAP Integration) you want to install. Disk Agent. that Microsoft TCP/IP is installed and running. if not.P. determine under which user (in the administrator group) the Data Protector services are started. start them manually Student Notes If you want to install a Windows system as Data Protector Cell Manager or installation server.00 3-23 2003 Hewlett-Packard Development Company. Media Agent. you must install the software from CD-ROM. and select which Data Protector components (for example. L. Use the Data Protector user interface to distribute the agent software to the client systems. If you deselect the default option to install the Installation Server on the Cell Manager. etc. Oracle.exe process to ensure that it is running. After a successful installation. NOTE: You can check the status of these services with the Control Panel. Check the task manager for the mmd. They should be set to start automatically. http://education. then you must install the Installation Server to another system before you are able to push agent software to client systems. A special Data Protector service user must be created to back up shared Windows disks or integrations with databases and applications. such as MS SQL.00 3-24 2003 Hewlett-Packard Development Company.com . a number of Data Protector registry entries are added to the Windows registry.hp. During the installation. Run the Windows Installer Package and install the Cell Manager. You may also use the <OMNIHOME>/bin/omnisv –status command to verify their status On Windows systems. Data Protector runs all the services under a default system account or the one specified during the installation. You must also install the Installation Server on an HP-UX or Solaris system if you have a mixed (Unix/Windows) environment. NOTE: See the Installation and Licensing Guide for more details. and three Data Protector services are configured and started: − − − Data Protector CRS Data Protector RDS Data Protector inet The Media Management daemon runs as an application process on windows.P. MS Exchange. start the Data Protector GUI with the start button: Start->Programs->HP OpenView Storage Data Protector ->Data Protector Manager U1610S B. 2.Module 3 Data Protector Installation Installation Steps The installation procedure consists of the following steps: 1. not as a service. The following sub-product packages related to Cell Manager installation are included in the product: OB2-CORE Data Protector Core software. Insert the Solaris installation CD-ROM. OB2-MA Media Agent. OB2-CC Cell Console software. L. mmd.e. . OB2-C-IS Installation Server Core software. i. 2. Check system startup file /etc/rc. OB2-DOCS Data Protector online manuals.hp. http://education. This is required if you want to attach a backup device to the Cell Manager. This is required. OB2-CS Cell Manager software.conf for omni entry. rds) Student Notes Follow the procedure below to install the Cell Manager on a Solaris system: 1. SLIDE: Installation of Cell Manager on Solaris Installation of Cell Manager on Solaris Configure/Check hostname resolution (DNS) Install software using pkgadd Verify /etc/services for "omni 5555/tcp" and /etc/inetd. This contains the graphical userinterface and the command-line interface. otherwise it is not possible to back up the IDB.d/omni Check if daemons are running (crs.00 3-25 2003 Hewlett-Packard Development Company.Module 3 Data Protector Installation 3–9. OB2-DA Disk Agent software.com U1610S B.config.P. Change to the main <package_source> directory. the directory that contains the installation depot file (in this case <Mount_point>/DP-DEPOT). http://education.hp.com .d/omni script that starts up Data Protector.d/omni A script with startup and shutdown procedures.d/K09omni A link to the /sbin/init.pkg <package_name> If you want to install an Installation Server for UNIX on your Cell Manager. The Installed Directory Structure When the installation completes. Some of this configuration is operating system dependent. using the following command in each case: pkgadd -d DP_A0510_SUN78. IMPORTANT If you want to install Data Protector to linked directories. L. /etc/rc2. Configuring Automatic Startup and Shutdown The Data Protector installation procedure configures an automatic startup and shutdown of all Data Protector processes whenever a system is restarted.00 3-26 2003 Hewlett-Packard Development Company. you can do it at this point.Module 3 Data Protector Installation Use the pkgadd facility to install the above packages in the order in which they are listed. U1610S B.d/omni script that shuts down Data Protector.d/S97omni A link to the /sbin/init. for instance: /opt/omni/ -> /<prefix>/opt/omni/ /var/opt/omni/ -> /<prefix>/var/opt/omni/ /etc/opt/omni/ -> /<prefix>/etc/opt/omni/ you must create the links before the installation and ensure that the destination directories exist. Solaris The following files are automatically configured: /etc/init. Refer to “Installing an Installation Server for UNIX” later in this module for the additional steps required. /etc/rc1.P. the core Data Protector software is located in the /opt/omni/bin directory and the Installation Server for UNIX in the /opt/omni/databases/vendor directory. . Because the Cell Manager is not responsible for the installation. then you will need the HP-UX installation server.com U1610S B.Module 3 Data Protector Installation 3–10.hp. an installation server of each type should be installed to avoid manual client installations. http://education. or set up a network share. you will have to install all of the clients from the distribution media. If you are using UX clients. this may also be the Cell Manager system. you will need at least one Windows installation server.00 3-27 2003 Hewlett-Packard Development Company. these require manual client installations. otherwise. L. remote installations can complete faster in complex network environments. this does not apply to Novell and MPE/IX. If you are installing Windows clients. the Cell Manager is free for tasks that are more important. In mixed UNIX and NT environments. The choice for which platforms to use for the installation server depends largely upon the cell clients. SLIDE: Installation Servers Installation Servers Installation Server on Windows • May be installed with Cell Manager software (default) • May be installed with a client • Client (agents) may not be remotely installed after installation server • Required if UNIX Cell Manager needs to push software to Windows clients Installation Server on UNIX • May be installed with UX Cell Manager software (default) • May be installed after a client • Client (agents) may not be manually installed after installation server • Required if Windows Cell Manager needs to push software to UNIX clients Student Notes Installation Servers allow for distributed client software installations. Installation Server Choices You may use both HP-UX and Windows installation servers within the same cell.P. However. Thus. atl.hp.edunet.edunet.dow.P.edunet.edunet.hp.hp.hp.hp.00 3-28 2003 Hewlett-Packard Development Company.edunet.dow.edunet.dow.hp.com r848c76.dow.hp.com checking connection between r848c76.com r848c61.edunet.com r848c77.hp.com checking connection between dlthost.com all checks completed successfully.dow.dow.hp. http://education.com r848c61.hp.atl.com checking connection between r848c77. it may no longer possible to remotely install only the Data Protector Agent software onto the same system.com checking connection between r848c77.Module 3 Data Protector Installation After the Data Protector Installation Server is installed.com r848c61.com checking connection between r848c76.atl.hp.com all checks completed successfully.com checking connection between r848c77.com checking connection between r848c61.hp.com checking connection between r848c61.com checking connection between r848c61.edunet. and and and and and and dlthost.edunet.edunet. The following command may be used to check for DNS mismatches: omnicheck –dns –host <client> -verbose Example-1 checking an individual client: root@r848c61 [/opt/omni] # omnicheck -dns -host r848c61 -verbose DNS DNS DNS DNS DNS DNS DNS check: check: check: check: check: check: check: checking connection between r848c61.hp.dow.hp.edunet.dow.edunet.com checking connection between r848c76.hp.atl.1 version introduces a new tool to help troubleshoot DNS problems associated with clients within the cell.edunet.hp.edunet.hp.edunet.dow.edunet.com U1610S B.hp.hp.edunet.dow.edunet.com r848c61.atl.dow.edunet.hp.edunet.com r848c76.atl.hp.edunet.dow.com r848c77.dow.dow.hp.com dlthost.hp.com checking connection between r848c76.dow.edunet.com .dow.com checking connection between r848c61.hp.hp.edunet.dow.hp.hp.com checking connection between dlthost.edunet.dow.edunet. and and and and and and and and and and and and dlthost. (this is a older Windows limitation that does not affect other newer versions of Windows).com r848c77.edunet.com dlthost.edunet.dow.hp.com checking connection between dlthost.atl.edunet.dow.edunet.atl. install the Data Protector client software before installing the Data Protector Installation Server depot.edunet.com r848c61.com checking connection between dlthost. Troubleshooting DNS The Data Protector 5.com checking connection between r848c77.dow.edunet.hp.edunet.hp.dow.dow.hp.com r848c76.edunet.com r848c77.edunet. L.dow.hp.hp.com Example-2 checking all cell clients: root@r848c61 [/opt/omni] # omnicheck -dns -full -verbose DNS DNS DNS DNS DNS DNS DNS DNS DNS DNS DNS DNS DNS check: check: check: check: check: check: check: check: check: check: check: check: check: checking connection between r848c61.hp. In all cases.hp.hp.com r848c61.dow.edunet.com r848c76.dow.hp.edunet.dow.dow. Included are: ADOBE contains instructions for obtaining the Acrobat Reader for HP-UX DOCS contains the complete set of Data Protector Manuals DP_DEPOT contains the software depot used for swinstall LOCAL_DP_AGENT_INSTALL contains the omnisetup.UX contains an overview of the CD-ROM http://education.hp. L.00 3-29 2003 Hewlett-Packard Development Company.sh script for local agent install and cell manager upgrade MISC some unsupported tools OV_INTEGRATIONS contains the software for the OV Integrations ReadMe. They are: • HP-UX • Windows • Solaris This graphic above illustrates the HP-UX CD-ROM contents.com U1610S B. . SLIDE:HP-UX CD-ROM Contents HP-UX CD-ROM Contents Student Notes The Data Protector software products are shipped on three separate CD-ROMs for the supported Cell Manager platforms.P.Module 3 Data Protector Installation 3–11. exe and all of the binaries for the Windows-Intel 64-bit platform License Checker contains tools to help with licensing MPE contains the components to install the agents on the MPE/IX platform NetWare contains the components to install the agents on the Netware platform OFM_8.com .1 OPENVMS contains the components to install the agents on the HP OpenVMS platform OV_Integrations Contains the software to install the Openview integrations Product_Information autorun the executable invoked when the CD-ROM is inserted into a Windows system U1610S B. L. SLIDE: Windows CD-ROM Contents Windows CD-ROM Contents Student Notes Shown above are the contents of the Data Protector for Windows CD-ROM.1 contains the installation tools to load the Open File Manager version 8.Module 3 Data Protector Installation 3–12.00 3-30 2003 Hewlett-Packard Development Company. Included are: Adobe contains an installable version of the Acrobat reader Alpha contains the agent installation components for the Alpha platform Docs contains the complete Data Protector manual set as PDF files DP_Demo contains product demonstration material i386 contains the setup. http://education.hp.exe and all of the binaries for the Windws-Intel 32-bit platform ia64 contains the setup.P. P.Solaris contains an overview of the CD-ROM http://education. L. Included are: ADOBE contains instructions for obtaining the Acrobat Reader for HP-UX DOCS contains the complete set of Data Protector Manuals DP_DEPOT contains the software depot used for swinstall LOCAL_DP_AGENT_INSTALL contains the omnisetup. .sh script for local agent install and cell manager upgrade MISC some unsupported tools OV_INTEGRATIONS contains the software for the OV Integrations ReadMe.hp.com U1610S B. SLIDE: Solaris CD-ROM Contents Solaris CD-ROM Contents Student Notes This graphic above illustrates the HP-UX CD-ROM contents.Module 3 Data Protector Installation 3–13.00 3-31 2003 Hewlett-Packard Development Company. http://education. The Data Protector GUI may be started with the /opt/omni/bin/xomni command. including: • Clients (install) • Users • Devices and Media • Backup • Monitor • Restore • Instant Recovery • Reporting • Internal Database U1610S B. and it is located in the /opt/omni/bin (<OMNIHOME>/bin) directory.hp. L.com . The Data Protector GUI has several administration contexts.P.Module 3 Data Protector Installation 3–14. SLIDE: Starting the UNIX GUI Starting the UNIX GUI # /opt/omni/bin/xomni & Student Notes The Cell Console (user interface) on HP-UX and Solaris is called xomni.00 3-32 2003 Hewlett-Packard Development Company. the /etc/MANPATH file is updated to allow for easy access to the man-pages. The Data Protector administrator may want to add the <OMNIHOME>/sbin directory to the PATH on the cell manager system. and is not recommended as a long term solution.Module 3 Data Protector Installation While the GUI is the recommended tool for configuring Data Protector. This entry should be removed once a remote cell console is able to connect to the cell manager. This file will need to be modified to allow all distributed GUI’s to access the cell manager. .P.00 3-33 2003 Hewlett-Packard Development Company. This will allow all of the Data Protector commands in <OMNIHOME>/bin to be available after a new login session is started.hp. When Data Protector is installed. then this file should be edited before any remote GUI will be able to connect to the Cell Manager. add a new entry (on a single line) containing four asterisk characters separated by spaces. The users that have access to the Cell Manager are registered in the <OMNICONFIG>/uses/UserList file. followed by the string admin. To get started. it is possible to make configuration changes by using the command line interface or by editing the configuration files in the /etc/opt/omni/cell and /etc/opt/omni/users directories. Example: * * * * admin This will allow any GUI client to connect to the Cell Manager. L. This will allow simpler access to the binaries for some cell management tasks. In addition.com U1610S B. the /etc/PATH file is updated to contain the <OMNIHOME>/bin directory. If there is no local GUI running on the Cell Manager. http://education. 00 3-34 2003 Hewlett-Packard Development Company. Additional commands exist in this directory for command-line execution. simply make the <OMNIHOME>/bin your working directory. L.pdf. U1610S B.com .hp. and execute the programs by name if the directory is not added to the Path.P. All of the programs that make up the command line interface are documented in the <OMNIHOME>/Docs/MAN directory in a single file named CLIReference. http://education.exe. The Administrator may want to add the “bin” directory to the system Path for simpler access to the Data Protector executables. The <OMNIHOME>/bin directory is not added to the system PATH by default. SLIDE: Starting the Windows GUI Starting the Windows GUI Start -> Programs -> HP OpenView Storage Data Protector -> Data Protector Manager Student Notes The user interface on Windows systems is accessed via the Start button.Module 3 Data Protector Installation 3–15. The actual program running is the <OMNIHOME>/bin/manager. This default Installation Server does not need to be registered with the cell manager in order to be used. Additional Installation Servers needed by the Cell Manager must each be registered after they are installed. L. .hp. This is true for Windows Installation Servers and HP-UX Installation Servers in the cell.exe located within the i386 (IA64) folder. Adding a Windows Installation Server As with the Cell Manager installation on Windows. SLIDE: Register Installation Servers Register Installation Servers Client context Student Notes Adding an Installation Server When the Cell Manager is installed. Data Protector will automatically create a Windows shared directory that may be accessed from the network.00 3-35 2003 Hewlett-Packard Development Company. http://education.Module 3 Data Protector Installation 3–16. it must be registered with the Cell Manager. the Installation Server software is also installed.com U1610S B. To utilize the Installation Server.P. Select the Installation Server as the system type. load the CD-ROM and run setup. Add the name of the Windows server in the Name Field or select it by Browsing the Microsoft Windows Network. and click Finish. 2. select the Client context. install the client components first and check the feature to include the installation server. 2. Within the Data Protector GUI.com . U1610S B.00 3-36 2003 Hewlett-Packard Development Company. and complete the installation. This time. select only the sub-product of Data Protector. Select: Edit -> Add -> Import Installation Server from the Menu Bar. Select: Edit -> Add -> Import Installation Server 4. and select Finish . Within the Data Protector GUI. 3. As with the cell manager installation for HP-UX. Adding an HP-UX Installation 1. To use the same system as both an installation server and a client.hp. run swinstall.P. NOTE: You cannot remotely install a Data Protector client on the Windows installation server system. 3. Add the FQDN (Fully Qualified Domain Name) of the HP-UX server in the Name Field. http://education. L. switch to the client context.Module 3 Data Protector Installation Proceed as follows to register the Installation Server: 1. called OB2-IS. The GUI shows which agents and versions are installed on the client systems. which can be used if the GUI is not available. http://education.00 3-37 2003 Hewlett-Packard Development Company. . then select which components to install on which system. Software is distributed to clients using the Data Protector user interface (GUI) In the Data Protector Client context. media agent. and Add Clients from the pop-up menu.hp. the cell console (GUI and command line interface). SLIDE: Adding New Clients to the Cell Adding New Clients to the Cell Clients context Cell Actions Student Notes The Data Protector user interface supports cross platform client installation.Module 3 Data Protector Installation 3–17. Select an installation server to use. as well as the various integration components.com U1610S B. L. The next set of slides illustrates the various installation and deinstallation options that are available for these clients through the supported GUIs.P. This information is also stored in the <OMNICONFIG>/cell/cell_info file. select Clients. Possible components are the disk agent. a normal rcp command is used. omnirexec) and the appropriate install utility is executed. An archive containing utility scripts is copied to the remote system via rcp/ftp. If the system is remote. to access the menu above. and shortcuts are used to speed the installation process. Next. Reads the list of client components you want to install.1 or greater). Choosing Edit -> Add -> Clients allows you to select UNIX or Windows clients. Client Installation — HP-UX For every system. If so. 4. 5. 7. then pushed to the client systems. and ftp is executed to copy the files. Copies the package containing the software onto the client system. using nslookup/ping. To initiate the distribution process. For a Windows client. rlogin is attempted as the root user. http://education. the new software must be installed manually on the cell and installation servers. 8. L. 3. 2. Checks on the client system that it can resolve the hostname and IP address back to the Cell Manager. as well as which installation server to use. the installation procedure found in the utils package is used to install the software on the remote system (omni_rinst. use the Update instead of the Add Client menu selection.sh). 6. U1610S B. Checks to see if the client already has the agent software installed. Pings the system to check connectivity. Determines whether you are installing locally or on a remote host. If local. If this is a first time installation of Data Protector. a password is requested. An ftp script is generated if the client system is not in the .hp. 2. Installs software. 3. 4. Determines if available disk space on the client system meets the needs requested in the require. then the loopback address is used for the IP address.com . what version it is.rhosts file.Module 3 Data Protector Installation Updating to New Versions of Data Protector To update to a new version of Data Protector or single Data Protector components that have been submitted as a patch.P. the cell manager performs these steps: 1. it does not require a password. Checks the version of the OS on the client system and that it is compatible with the agent software being installed.00 3-38 2003 Hewlett-Packard Development Company. Uses IP address resolution to find the IP address of the system via its hostname. (swinstall on HP-UX) Typically the following checks are performed: 1.rhosts list. If client system is in the . The archive is then unpacked (by a special Data Protector tool. Switch to the Client context. If Data Protector has previously been installed (version 3. Adding UNIX Clients The Data Protector GUI can be used to install UNIX or Windows hosts. Checks that the time difference is no more than 10 seconds.dat file. a Windows NT installation server must already be configured in the cell. If not. Using the remote service manager. 5. Gives a summary after installation. it asks in which directory the software should be installed. 6. The script performs some cleanups and deletes all temporary scripts. Starts setup with the option -components component1 component2 -client host1 host2 host3 . Setup checks for access permission to the remote registry. Data Protector can determine which version of the software is currently running on the client system and from which cell manager it was installed. 3.. Asks which components to install. Updates information about currently installed software packets and configuration on the client system. it starts the inet service on the remote host.00 3-39 2003 Hewlett-Packard Development Company.. right clicking on the Clients icon accesses the new client window. 8. and files created on the client system. . When started.com U1610S B. L. 4. http://education. 2. If the destination directory is not available as the default shared disk (\\hostname\C$ for C: and \\hostname\D$ for D:). Setup copies all the files to the destination directory. it proceeds with the next host. From this information.P.) 9. Gets information on which systems should be installed. a manual import may still be necessary to complete the registration process. If it fails. Alternately. Adding Windows Clients The following prerequisites must be met for installation of Windows NT/2000/XP/2003: • Administrator rights on the remote machine (for accessing the remote registry) • A shared disk that corresponds to the destination directory (for copying files) From within the Windows GUI. inet contacts the Cell Manager and instructs it to import the host into the cell. Files: <OMNICONFIG>/cell/cell_server <OMNICONFIG>/cell/omni_info 6. 7. 7. (In some cases. the user is prompted to give the correct shared disk. Prints a summary for every packet requested to be installed on the client system.Module 3 Data Protector Installation 5.hp. the Add New Client icon can be selected from the Tool Bar in the top right-hand corner of the same screen. Setup checks if Data Protector has already been installed (update). Client Installation — Windows NT/2000/XP/2003 Performs the following steps for every system: 1. utilities. P.Module 3 Data Protector Installation 3–18. http://education.00 3-40 2003 Hewlett-Packard Development Company. An example might be if an HP-UX server has been installed with disk and media agents (i.com . U1610S B.. SLIDE: Adding Components to Clients Adding Components to Clients Select client Pop-up menu using mouse right-button Student Notes The Add Components option is used when a client already exists within the cell. If it has an Oracle database added to it. L. then a further integration is required for online backups to occur.e. it has data to be backed up and contains a backup media of some sort).hp. This is achieved via the Add Components screen. but more agents or integrations are required. L. SLIDE: Importing Clients Importing Clients Select clients.hp. use pop-up menu omnicc –import_host <hostname> Student Notes Importing an HP-UX Client To move a system from one cell to another cell (or to remove a system from your local network).P. they simply amend the configuration on the cell manager and client machines. . The relevant files for export and import are: <OMNICONFIG>/cell/cell_server <OMNICONFIG>/cell/cell_info On the client system On the cell manager The <OMNIHOME>/bin/omnicc command may be used to import or export clients.com U1610S B. use the export/import actions.00 3-41 2003 Hewlett-Packard Development Company. The options -import_host and -export_host support client management. These actions do not install or delete the Data Protector client software. An option is available to remove the Data Protector software if this is necessary. http://education.Module 3 Data Protector Installation 3–19. Module 3 Data Protector Installation Importing a Cluster Data Protector supports the HP MC/ServiceGuard clusters running on HP-UX. The Data Protector clustered systems must be installed locally from the CD-ROM on every system within the cluster, and then manually imported to the Data Protector cell using the graphical user interface and specifying the virtual names for floating IP addresses. Use the Import Cluster feature in the GUI for this function. Importing Windows Clients/Clusters As with HP-UX client imports, Windows also has the same functionality. The import updates the files: <OMNICONFIG>\cell\cell_server <OMNICONFIG>\cell\cell_info On the client system On the Cell Manager On Windows the cell_server information is also kept in the registry, if entered incorrectly during the installation process, this entry may be altered manually using regedit: HKEY_LOCAL_MACHINE\ SOFTWARE\ Hewlett-Packard\ OpenView\ Omniback II\ Site\ Note: [fully qualified name of the cell manager] During the Windows client installation, specifying the name of the Cell Manager is optional, simply leave the field empty and continue the install process. In this way the import must be used to register the client with the Cell Manager. Importing a Cluster Data Protector supports the Microsoft Cluster Server (MSCS) for Windows. The Data Protector cluster-aware clients must be installed locally from the CD-ROM on every system within the cluster, and then manually imported to the Data Protector cell using the graphical user interface; select “MS Clusters” in client context, and use the Import Cluster tool or popup menu in the GUI. U1610S B.00 3-42 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 3 Data Protector Installation 3–20. SLIDE: Deleting (Exporting) Clients Deleting (Exporting) Clients Option to delete software omnicc –export_host <hostname> Student Notes Exporting (Deleting) Clients Exporting a client system from the Data Protector cell removes the client references from the Data Protector database and configuration files on the Cell Manager and client system without uninstalling the software on the client computer (unless selected). This can be done using the GUI or the omnicc -export_host command. A client export may be required in the following situations: • • The client needs to be moved to another cell. The administrator wants to remove any systems from the Data Protector cell configuration that are no longer part of the network. The software components may be deleted when a client is exported from the cell when using the Data Protector GUI. If the client is to be imported into another cell, do not remove the software. http://education.hp.com U1610S B.00 3-43 2003 Hewlett-Packard Development Company, L.P. Module 3 Data Protector Installation 3–21. SLIDE: Data Protector Licensing Licensing Evaluation 120 Days Permanent Instant-On 60 Days Emergency 14 Days Default installed with product Installed using : • GUI • Command Line Interface • Editing lic.dat Student Notes When you install Data Protector for the first time, it runs with an instant-on license, which is valid for 60 days. Furthermore, in special cases you may be provided with a temporary license which is valid for three months. This means that you can use Data Protector for up to three months without any permanent license. During this time, you should set up and configure your Data Protector environment, and request your permanent license string. In the event of a loss of the Cell Manager and subsequent recovery using a new system, an emergency license valid for 14 days may be obtained from HP Customer Support. After you receive the permanent license string, you can install it with the Data Protector Installation GUI, or using the command-line interface. You can also use an editor to type the string into the license file, <OMNICONFIG>/cell/lic.dat. You must then issue the omnicc command to activate and verify the changes. Use the command omnicc -query to display the current license information, and the omnicc -password_info for a more extensive report. U1610S B.00 3-44 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 3 Data Protector Installation 3–22. SLIDE: Licenses and Part Numbers Licenses and Part Numbers Student Notes Shown above are the licenses available for Data Protector 5.1. The Starter Packs are for the Cell Manager including a single drive license with unlimited clients. NOTE: All Omniback 3.5, 4.0, 4.1 and Data Protector 5.0 licenses will work with Data Protector 5.1. To take advantage of new product features, additional licenses must be purchased. The Cell Manager installation includes a license.txt file which may be printed and then faxed to the HP Password Delivery Center to obtain a permanent license keys. Visit the HP website: http://webware.hp.com for more information. NOTE: For further information on licensing refer to the HP OpenView Storage Data Protector Installation and Licensing Guide. B6960-90079 http://education.hp.com U1610S B.00 3-45 2003 Hewlett-Packard Development Company, L.P. Module 3 Data Protector Installation U1610S B.00 3-46 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 4 — Data Protector Basics Objectives Upon completion of this module, you will be able to do the following: • • • • • • • Describe the general concepts behind Data Protector backup. Configure a device for Data Protector usage. Initialize a tape for Data Protector. Perform an interactive backup. Schedule a backup. Perform a simple restore. Execute basic reports http://education.hp.com U1610S B.00 4-1 2003 Hewlett-Packard Development Company, L.P. Module 4 Data Protector Basics 4–1. SLIDE: Getting Started Data Protector Basics Purpose Gain familiarity with the GUI Authorize remote administration Understand the backup concept Add a simple tape device into the cell Format media for backup Perform a simple backup Schedule a backup Perform a restore Respond to a mount request Execute a report Student Notes The purpose of this module is to gain familiarity with the Data Protector product and its associated GUI. This module will serve as a tutorial to the basic concepts behind Data Protector backup. At this point you have installed the product and created a cell, this module will guide you to a point at which a simple backup can be initiated. Several steps are required; some are simple checks; others are configuration tasks. The end-to-end process will introduce many of the initial features within the main Data Protector GUI. Each of the features and functions will be discussed in much greater detail in later topics in this training. The purpose of this module is to have you explore the functionality of Data Protector by configuring the cell to perform a simple backup and restore. The steps include: • • • Checking that the appropriate agents exist on the client Checking that the appropriate media pool exists Creating a logical device (i.e., adding a tape drive to the cell) U1610S B.00 4-2 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 4 Data Protector Basics • • • • Using the new logical device to initialize a tape into a media pool Creating a backup specification (a list of objects to backup to the tape) Starting the backup or scheduling the backup Monitoring the backup http://education.hp.com U1610S B.00 4-3 2003 Hewlett-Packard Development Company, L.P. Module 4 Data Protector Basics 4–2. SLIDE: Data Protector GUI Data Protector GUI Menu bar Tool bar Context list Results area Scoping pane Navigation tab Results tabs Status bar Student Notes HP OpenView Data Protector Main GUI The slide above depicts the main Data Protector GUI provided when an administrator executes the xomni(UNIX) or manager(windows) command. The GUI contains several contexts, each designed to allow for control of a specific functional area. To use the graphical user interface of Data Protector, enter: UNIX: Windows: or /opt/omni/bin/xomni Start -> Programs -> HP OpenView Storage Data Protector -> Data Protector Manager c:\program files\Ominback\bin\manager The Context List: Controls access to a given functional area. The Scoping Pane: Provides a tree-like structure of items that may be selected to allow for configuration or properties for the selected item. The Results Area: Provides properties for selected items as well as configuration procedures for the selected items in the Scoping Pane. U1610S B.00 4-4 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 4 Data Protector Basics The Navigation Tabs: Objects and Tasks that appear at the bottom of the Scoping Pane. They are used to switch between the Object list, and configuration Tasks. The Results Tabs: Allows several tasks to be executing in parallel from the single GUI. Each tab shows the results of a particular task. The UNIX interface provides several command line options: • • • • • • xomni -server <Host> to start the user interface for the complete Data Protector functionality and connect to a specific Host which is a cell manager xomnibackup to start the interface for the backup context (xomni –backup) xomnirestore to start the interface for the restore context (xomni –restore) xomnimonitor to start the interface for monitoring a single cell (xomni –monitor) xomnimm to start the interface for devices and media (xomni –admin) xomniadmin to start the interface for users, clients, database and reporting (xomni –users –clients –db –report) The Windows interface provides several command line options: • • • • • • • • • • manager -server <Host> to start the user interface for the complete Data Protector functionality and connect to a specific host, which is a cell manager manager -backup to start the user interface for backup manager -restore to start the user interface for restore manager -monitor to start the user interface for monitoring a single cell manager -admin to start the user interface for devices and media manager -db to start the user interface for the Data Protector Database manager -users to start the user interface for users manager -clients to start the user interface for clients manager -report to start the reporting interface manager -? to see a list of options Data Protector also provides a “snap-in” for the Microsoft Management Console (MMC). If you have the MMC loaded, you may add the OB2_Snap as a standalone Snap-in. NOTE: To use the command line interface of Data Protector, enter: • omnib to start a backup • omnir to start a restore • omnistat to monitor the state of the current backup or restore jobs • omnimm to manage media • omnicellinfo to report on cell configurations Most of these components of the GUI and the command interface will be discussed in further detail throughout the rest of this training course. You may want to view the man-page or WordPad files for omniintro and omnigui for an overview of all the commands available to Data Protector. http://education.hp.com U1610S B.00 4-5 2003 Hewlett-Packard Development Company, L.P. Module 4 Data Protector Basics Proceed as follows to view the man pages on UNIX: export MANPATH=$MANPATH:/opt/omni/lib/man (done by default after installation) man omniintro man omnigui Proceed as follows to view the WordPad documents on Windows: Open the c:\Program Files\Data Protector\Docs\MAN folder (directory) Open any of the *.wri files with the WordPad application. U1610S B.00 4-6 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 4 Data Protector Basics 4–3. SLIDE: Authorizing Remote Console Access (1) Authorizing Remote Console Access (1) <OMNIHOME>/config/users/UserList (Windows) <OMNICONFIG>users/UserList (UNIX) # format "description" "User_Name" "Domain/Group" "FQDN" "DP_Group" “” * * * "admin“ Allows any cell console to connect as admin! “” “root" “sys” r848c40.dow.edunet.hp.com “admin“ “” “ADMINISTRATOR” “PC1” “pc1.dow.edunet.hp.com” “admin” “WebReporting” “java” “applet” webreporting “admin” Student Notes In many Data Protector installations, more than one Cell Console is distributed during the installation process. In order to be able to access the Cell Manager remotely via the distributed Cell Console it must be authorized. By default, only the Cell Console installed on the Cell Manager system can access the cell server process. Any attempts to use a remote cell console will be blocked; a permissiondenied message will appear on the system where the console is running. To authorize another Cell Console, you must add a remote user to the User configuration. If the user is to be a remote administrator, add them to the Data Protector “admin” user group. The screen above illustrates the necessary steps: Select the Users context, select the admin group, then use the right-mouse button to access the context-sensitive pop-up menu, select “Add Users.” http://education.hp.com U1610S B.00 4-7 2003 Hewlett-Packard Development Company, L.P. Module 4 Data Protector Basics 4–4. SLIDE: Authorizing Remote Console Access (2) Authorizing Remote Console Access (2) 5 2 Fields in the UserList file 3 1 4 Student Notes You will need the following information to add an additional user of the Cell Console: • • • • • The Platform type (where the console is installed UNIX or Windows) The User Name (operating system user ID of the person authorized to use the cell console) The User Group/Domain (operating system group if UNIX, or Domain if Windows) The System Name (where the cell console will connect from) All of the above entries may contain <Any> instead of a specific name. This is essentially a wildcard. Use with caution! The Cell Console system does not need to be a client of the cell; this allows an authorized cell console to connect to many different cell managers. NOTE: U1610S B.00 4-8 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 4 Data Protector Basics Manually adding a remote user If you need to have remote cell console access prior to starting your configuration, add the following line to the <OMNICONFIG>users/UserList file on the cell manager: “Any” * * * admin The above entry allows any user from any cell console (user interface) to access the cell manager; this is not a secure long term solution, but does allow for quick remote access to the cell manager. Once access is gained remotely, modify the user configuration as necessary to tighten up the security. http://education.hp.com U1610S B.00 4-9 2003 Hewlett-Packard Development Company, L.P. Module 4 Data Protector Basics 4–5. SLIDE: General Backup Concept General Backup Concept Backup Objects Logical Device Media from Pool System-A Backup Specification Objects SystemA - Disk1 SystemB - Disk2 Logical Device SystemC - Tape1 Disk2 System-B Disk1 DA MA System-C Logical Device DLT 8000 DA Media Pool Student Notes • The Data Protector product performs either local or network backups using the Disk Agents and Media Agents that are installed onto the various systems in the Data Protector Cell. The Backup Specification is essentially a configuration file that contains a list of the objects to be backed up along with the devices to use for the backup. Disk Agents are used to access the object data, and Media Agents are used to write to the backup devices. The physical devices attached to a system are configured into Data Protector as a Logical Device, allowing additional features to be used for backup and restore. One of the features of the Logical Device is a Media Pool. The Media Pool groups tapes together into a logical set, and has policies for how the tapes in the set may be used and accessed. Media Pools may be assigned to a Logical Device when the device is configured, and become the default set of tapes to be used during backup when a logical device is used. • • • U1610S B.00 4-10 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 4 Data Protector Basics • Data Protector backups are configured such that tape selection is done automatically during the running of the backup job. You assign an Object to a Device, which is already assigned to a Media Pool. Data Protector then chooses an appropriate tape for the backup. If no tapes are available, Data Protector will issue a Mount Request for the desired medium. We will explore all of these topics in much detail in the modules following this introduction. NOTE: http://education.hp.com U1610S B.00 4-11 2003 Hewlett-Packard Development Company, L.P. Module 4 Data Protector Basics 4–6. SLIDE: Backup Specification Backup Specification The fundamental components of all Data Protector backups are: • A list of what is to be backed up (objects) • A list of devices to be used (logical devices) • What media is to be used (media pools) • Options (backup spec, object, device) These components are grouped together as a backup specification for repeated use. Student Notes Before going through the individual steps of configuring a backup, it is helpful to know how a backup is defined and processed with Data Protector. Data Protector requires the following fundamental components for all backups: • A list of what is to be backed up. Data Protector refers to the data source as an Object. Data Protector supports specific object types, which will be discussed later in this module. A list of what devices Logical Devices to be used. (Details covered in Module 6) A set of media for the backup to be written to. This is in the form of a media pool. (Details covered in Module 5) The options that are to be used for the backup. Data Protector provides many flexible options that can be used to completely define all characteristics of the backup and the information relating to it. These options will be discussed in throughout this module. • • • U1610S B.00 4-12 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com com U1610S B. http://education. either manually invoked or scheduled. Backup specifications are used to run repeated backups of the same source data.hp. L. .P.Module 4 Data Protector Basics These components can be grouped together and saved as a backup specification.00 4-13 2003 Hewlett-Packard Development Company. Backup Wizard Data Protector provides a “wizard” to guide you through the main steps in configuring a new backup specification. The wizard is not covered here. The remainder of the module will guide you through these steps.hp. To use the Next Step Wizard.com . select it from the View menu in the Menu Bar: View -> Next Step Wizard U1610S B.00 4-14 2003 Hewlett-Packard Development Company.P. SLIDE: Backup Checklist Backup Checklist • Install Disk and Media Agents • Configure Media Pool(s) • Configure Logical Device • Initialize Medium • Create Backup Specification • Save Backup Specification • Schedule/Run Backup Job Student Notes The slide illustrates some of the main tasks that are necessary to complete an Data Protector backup. http://education. L.Module 4 Data Protector Basics 4–7. but rather the steps used within the wizard. with a lab at the end for you to work through them on your own. L. also called the Cell Console.hp. . • Disk Agent — Allows data to be backed up from the cell manager • Media Agent — Allows a backup device to be configured on the cell manager The Clients context on the Data Protector GUI provides the list of the client hosts. along with the software that has been successfully configured on each. be sure that each system in the Cell has the correct software components (agents) installed.P. http://education. TIP! You may see a report from the command line as follows: omnicellinfo –cell brief Before configuring devices or backups.00 4-15 2003 Hewlett-Packard Development Company.Module 4 Data Protector Basics 4–8. SLIDE: Verify Agents Verify Agents Client context Select clients Property list shows installed agents • Install Disk and Media Agents • Configure Media Pool(s) • Configure Logical Device • Initialize Medium Student Notes The initial installation of the cell manager installed three key components: • User Interface — Allows the GUI to be started.com U1610S B. com . It is also used to configure logical devices for backup and restore (discussed in the next slide). In this module. click the Devices & Media context in the GUI. The Default DDS pool should be listed in the Results Area. SLIDE: Check Default Media Pools Check Default Media Pools Device/media context Select media Property list shows configured pools • Install Disk and Media Agents • Configure Media Pool(s) • Configure Logical Device • Initialize Medium Student Notes The Devices & Media context in the GUI is used to configure media into the relevant pool (a media pool is a logical collection of media). To check that this pool is available. you may use or remove these pools as needed.hp. select Media in the Scoping Pane. U1610S B. http://education.00 4-16 2003 Hewlett-Packard Development Company. It should have a 0 in the column #Media indicating that there are no tapes in this pool yet.Module 4 Data Protector Basics 4–9. a default media pool was created for each type of supported medium. During the initial configuration of Data Protector. you will perform a backup to a tape that will be part of the standard media pool called Default DDS.P. L. SLIDE: Configure a Device Configure a Device Select devices Pop-up menu with mouse right-click Properties list shows existing devices • Install Disk and Media Agents • Configure Media Pool(s) • Configure Logical Device • Initialize Medium Student Notes As mentioned in the previous slide.00 4-17 2003 Hewlett-Packard Development Company. They are used to initialize tapes as well as perform backups and restores.Module 4 Data Protector Basics 4–10. http://education. You must create a logical device on the cell manager that can be used to perform the backup at the end of this module. The logical devices are the entities that represent physical devices on a client system. the Devices & Media context can be used to configure logical devices.P. . L.hp.com U1610S B. 9. and enter any textual description for the device.Module 4 Data Protector Basics 4–11.P. 4. Select Devices in the Scoping Pane. Select Data Protector for the Data Format. select Add Device … from the pop-up menu 3. From the pull down list. http://education. Select the Add button. 6. L. SLIDE: Device Specification Device Specification Logical device name and description Student Notes Cookbook to Create a Logical Device From the Device and Media context. select the appropriate SCSI device file/name. Select Standalone for the Device Type. Right–click on the selected Devices in the Scoping Pane. Select your Classroom system from the pull down list for the Client field. Select the Device Name field. enter DDS-Practice as the device name.00 4-18 2003 Hewlett-Packard Development Company. Select the Description field.hp. 2. 7. 8.com . 10. 5. use the following instructions to configure a Logical Device on the Cell Manager: 1. Select the Next button (at the bottom of the Results Area). U1610S B. select the Finish button.Module 4 Data Protector Basics 11. .com U1610S B. Verify that the Media Type is DDS.hp. and Default Media Pool is Default DDS. The Results Area should display your configured device.00 4-19 2003 Hewlett-Packard Development Company. L. Select the Next button (at the bottom of the Results Area) 12.P. http://education. http://education. U1610S B. TIP! Data Protector can use blank media. See previous slide for specifying the pool name for a device.Module 4 Data Protector Basics 4–12. SLIDE: Add Media to Media Pool Add Media to Media Pool Highlight desired pool Select media Pop-up . the blank media is simply added to the pool name specified by the logical device into which the media was inserted. so you do not have to initialize it. some media should be added to the pool.P. At backup time. In this case. Procedure to Initialize a Tape The previous slides introduced the Device & Media context.com . The following instructions should be used from that same context. L. we will use the new logical device to initialize a tape and add it to the default DDS pool.context sensitive menu mouse right-click • Install Disk and Media Agents • Configure Media Pool(s) • Configure Logical Device • Initialize Medium Student Notes Before a backup can take place to the logical device that has been created.hp.00 4-20 2003 Hewlett-Packard Development Company. 6. this opens the Media Pool list. 10. 8.P. L. Select the Automatically generate option (selected by default) Select the Location field. 11. 1. and the tape should be initialized within a short period of time. Insert a tape into the tape drive (be sure it’s not write protected). http://education. 4.00 4-21 2003 Hewlett-Packard Development Company.com U1610S B. and enter “Device Repository” Select the Next button Select the Force Operation button (we assume to have a previously used tape) Select the “Default” for Medium Size. Select the Next button.Module 4 Data Protector Basics Double-click Media in the Scoping Pane. Select Default DDS. 2. 3. 5. 7. .hp. Wait for the device to be ready. select Format from the pop-up menu (use the right-mouse button) Select the DDS-Practice device from the pull-down list next to the Device field. this may take several minutes depending upon previous usage of the medium. Messages should appear in the Results Area window. 9. Select the Finish button. This consists of simply writing a header to the tape and registering it in the media database. Data Protector will not initialize (without the force option) a used tape. Data Protector adds a unique MediumID to each tape initialized. Note the following: • • • • • Data Protector reads the tape before writing to it.00 4-22 2003 Hewlett-Packard Development Company. SLIDE: Format Medium Format Medium Media checked before format proceeds Unique medium-id assigned Session summary Session summary pop-up window Student Notes The graphic above illustrates the messages displayed during a media initialization session.P.hp. The default label for a tape (when auto-label is used) is the pool name and a sequence number within the pool. U1610S B. http://education.com .Module 4 Data Protector Basics 4–13. All tapes must be labeled (formatted) before use. L. and stores this in its internal media management database. P. A definition must now be created to tell Data Protector which objects to place on the tape. we will address only the ones required for a simple backup. There are many options for creating the datalist file. Datalist is synonymous with Backup Specification and is more commonly used to refer to the file containing the backup specification. . and use the menu as shown on the graphic above to add a new Backup Specification. The directory that contains the backup specification file is called datalists. select it. The Filesystem folder under Backup Specification in the Scoping Pane is the place to start.hp.com U1610S B. we are ready for backup. http://education. L.00 4-23 2003 Hewlett-Packard Development Company. The Backup context in the GUI opens the Backup tools.Module 4 Data Protector Basics 4–14. This definition is called a Backup Specification or Datalist. and is in the <OMNICONFIG> directory. SLIDE: Configure a Backup (1) Configure a Backup (1) File system selected Pop-up menu • Initialize Medium • Create Backup Specification • Save Backup Specification • Schedule/Run Backup Job Student Notes Now that we have a logical device and media in a media pool. In this module. hp. U1610S B. then select the OK button. http://education.P.com .Module 4 Data Protector Basics 4–15. SLIDE: Configure a Backup (2) Configure a Backup (2) Blank template Direct attached or remote Student Notes With the Create New Backup window open. L. select the Blank Filesystem Backup.00 4-24 2003 Hewlett-Packard Development Company. (Double-click to open the list as well.com U1610S B. a relatively small object is desirable. 1. a small blue check mark will appear in the box. Select (check) your logical device (it may be selected by default).hp. Select the “plus” in front of your system to open the object list. SLIDE: Configure a Backup (3) Configure a Backup (3) Select objects Select Next> for more options Student Notes For this first backup. Leave most of the options as their default values. 6. select the Next button.Module 4 Data Protector Basics 4–16. select Next. Select Next. Select Next. except as indicated below. .) 8. 3. 4. Select the small check box in front of the desired object or directory. Change the file system options: Protection to 4 days. (You will see Save.00 4-25 2003 Hewlett-Packard Development Company. repeat if necessary to see the directory to backup. and Preview buttons. Start. go to the next page) http://education.) 7. (You will see the scheduler. L. Select Next.) 2. locate a directory or filesystem that is suitable.P. (You will see the job summary. this indicates that it is selected for backup. 5. After you have selected (checked) the items for backup. in order to keep the specification. L.00 4-26 2003 Hewlett-Packard Development Company. exercise-1). Enter a name for the file (for example. 3. 1. Click OK. default. 2. leave the group name. U1610S B.hp. http://education. Select Save as.Module 4 Data Protector Basics 4–17.P. you must perform a save. From the Backup Results area.com . The new backup (datalist) will appear in the Scoping Pane. SLIDE: Configure a Backup (4) Configure a Backup (4) Save backup specification to a file Select finish to complete the definition • Initialize Medium • Create Backup Specification • Save Backup Specification • Schedule/Run Backup Job Student Notes Data Protector backup specifications are stored as files in the <OMNICONFIG>/datalists directory. com U1610S B. and which device(s) to use. 5. perform the following: 1. 3. and will show a session running. The file system object will switch from Pending to Running to Completed http://education. which to ignore.P. To start the backup.hp. it does so using a datalist file. The datalist definition ensures that Data Protector knows which objects to backup. Select OK to start the backup. You will be prompted for the Backup Type (Full) and Network Load (High). 4. select a backup specification then: Start Backup … from the popup menu 2. . In the backup context. SLIDE: Start the Saved Backup Specification Start the Saved Backup Specification Schedule tab for recurring backup Select the saved backup specification Start an interactive backup • Initialize Medium • Create Backup Specification • Save Backup Specification • Schedule/Run Backup Job Student Notes When Data Protector invokes a backup. The Backup Results Area window will become a Backup Monitor window.00 4-27 2003 Hewlett-Packard Development Company. L.Module 4 Data Protector Basics 4–18. The logical device part of the window switches from Inactive/Waiting to Running. 7. The messages part of the window updates the progress as various file system objects are backed up.00 4-28 2003 Hewlett-Packard Development Company.com . L. and shows that amount of KB of data backed up.P. http://education.Module 4 Data Protector Basics 6. U1610S B.hp. http://education.00 4-29 2003 Hewlett-Packard Development Company. therefore. Holidays can also be predefined so that no backups will take place on these days. A schedule is created on a per-backup specification basis. Backups can also be repeatedly scheduled at regular/irregular intervals.com U1610S B. even if scheduled.Module 4 Data Protector Basics 4–19. . care needs to be taken when scheduling multiple backups that no contention arises (for devices or objects). L. Student Notes Once a backup specification has been created. SLIDE: The Scheduler The Scheduler The Scheduler can be used to start a backup at a predefined date and time. defined by the administrator. The scheduler can also run the backup on a regular basis. the scheduler can be used to execute the backup at a predefined date or time. Schedules are created per Backup Specification.P.hp. L.hp. incr #. U1610S B. or simply double-click on a particular day to schedule a backup. You may override the protection for individual backups. SLIDE: Schedule Backup (1) Scheduled Backup (1) Select Add… for recurring backup Student Notes The Data Protector Scheduler offers many possibilities for producing re-occurring backups. but be executed at many different times. Notice on the picture above. Select Add… to create a new schedule. that you may not schedule backups in the past! Data Protector’s scheduler only allows for forward scheduling.Module 4 Data Protector Basics 4–20. each time with a different scope (full.com . incr). Each backup specification may have a single schedule file. http://education.00 4-30 2003 Hewlett-Packard Development Company.P. Holidays are seen in the schedule window and are color-coded black.com U1610S B. http://education. (blackout days) Data Protector can use the standard hp-ux style calendar holiday file as input. and starts them. which is automatically scheduled via the system scheduler. the schedule is always relative to the time on the cell manager.The Holidays file resides in <OMNICONFIG>/Holidays.Module 4 Data Protector Basics • Holidays The scheduler can be configured to skip backups on days that are defined as holidays. omnitrig checks if there are any backups that have been scheduled for the previous hour but did not run. The daylight savings time problem (an hour more or one hour less) is solved. Considering that omnitrig gets started on the cell manager.00 4-31 2003 Hewlett-Packard Development Company. . The scheduling information is checked every 15 minutes by the Data Protector omnitrig process. The name of the schedule file will be the same name used for the backup specification file. L. The scheduling information is kept in text files under the <OMNICONFIG>/schedules directory.hp.P. P. they may execute daily. http://education. Tuesday.Module 4 Data Protector Basics 4–21. L.00 4-32 2003 Hewlett-Packard Development Company. Saturday. U1610S B. or monthly. Sunday.com . in 15-minute intervals. SLIDE: Schedule Backup (2) Schedule Backup (2) Selection determines options Student Notes Backups may be scheduled to be recurring. Every. Monday. Thursday. Day. Wednesday. Backup specifications may also be setup to start executing at some future date. Every 2nd ……10th. Time in 24-hour format. Friday. Month.hp. The following date forms can be used when scheduling a backup: • • • • Specific Date and Time. weekly. Each schedule (file) may contain multiple time parameters. Every 1st. com U1610S B.Data Protector will reduce its use of the network when medium and low are selected. Medium.Module 4 Data Protector Basics • Backup Type The scheduler can also specify what type of backup is to be performed: • Full • Incr • Incr 1 – Incr 9 For each scheduled backup. The default is High.00 4-33 2003 Hewlett-Packard Development Company. High) The level to which Data Protector will monopolize the network where a backup is taking place over a LAN/WAN link.P.hp. • Network Load (Low. the following options can be specified: • Protection Protection set by the scheduler overrides any protection defined within the backup specification. The duration of the backup will increase as the network load is reduced. L. http://education. . U1610S B. For example. Data Protector provides a method of performing full.hp.9 Data Protector tries to find the latest protected backup session with a lower backup level on which the incremental backup will be based. the directory tree is recorded.com .00 4-34 2003 Hewlett-Packard Development Company. Incremental 1 . Data Protector will search through the database to find the latest protected version of the object with a lower level (full or incr 1-4) backup level.Module 4 Data Protector Basics 4–22.P. and various levels of incremental backups: • • Full Everything is backed up. L. and use it as the reference point version on which incremental will be based. SLIDE: Backup Types Backup Types Incremental Incremental plus level Student Notes As is common with many other backup mechanisms. A full backup is equivalent to level 0. With any incremental backup the entire directory tree is backed up. if the user starts backup with backup type incr5. http://education. so even if no files changed. mount point and description identifies an object) on which the incremental backup is to be based. incr 1-9 or incr) will be used as reference point version. Files that have been moved from one directory to another. . NOTE Use the UNIX command touch -m with options to change the modification time on a file. so if the user starts a backup with backup type incremental. the latest version (any level: full.P. Incremental backups can only be based on valid objects. Valid and Invalid Versions of an Object Data Protector differentiates between two types of object versions . Which files are NOT backed up in an incremental backup? Files that have only changed attributes (chmod.Module 4 Data Protector Basics • Incremental without level All other backup types are considered to be at a lower level than incremental without level. Invalid Backup Object Versions • • • The object is not completed (aborted and failed versions of object) during the backup session. Full restore chain for object version is broken (full restore chain is broken if the chain from full to this object version has some missing versions or if one or more object versions from the chain are invalid) Which files are actually backed up in incremental backup? All files that have a modification time newer than the related object versions start time and WinFS files with the archive attribute set.00 4-35 2003 Hewlett-Packard Development Company. Object versions without all media (one or more of the media on which the object was stored has been overwritten/exported or is not protected any more). This can then be seen in the monitor screen (backup type will be Full instead of incremental). (time when prior backup was started). on). chown and chgrp do not change/modify time of file). http://education. This backup promotion option may be disabled by changing the UpgradeIncrToFull global option (default is 1. NOTE If Data Protector cannot find a valid reference point version of the object (hostname. All directories are backed up (irrespective of time). L.valid and invalid. it will start a full backup. Invalid object versions are always ignored when Data Protector is searching for a backup object version to use as a reference point (related object version).com U1610S B.hp. Module 4 Data Protector Basics 4–23. L. SLIDE: Backup Types Examples Backup Types Examples Last Full Incr Incr Incr Incr Incr n Incr n Incr n Incr n Incr Incr Incr Incr Incr Incr n Incr 22:00 12:00 22:00 Incr (n+1) Incr (n+2) Incr 12:00 Incr (n+3) Incr 22:00 12:00 Incr 22:00 12:00 Incr 22:00 12:00 Day 1 Day 2 Day 3 Day 4 Day 5 Student Notes There are three different backup models illustrated above.com .00 4-36 2003 Hewlett-Packard Development Company.hp. Full + Daily Incremental Full backup at the beginning of the week Non-leveled incremental at the end of each day Each day’s incremental is assumed to be nearly equivalent in size and duration and include the changes since the previous nights backup Recovery may require multiple tape sets and take longer to perform (full plus all incrementals) Full + Mid-day Incremental + Daily Leveled Incremental Full backup at the beginning of the week Mid-day Incremental executed daily Leveled incremental using the same level number is executed at the end of each day Each mid-day incremental is assumed to be nearly equivalent in size and duration and include the changes since the previous nights backup U1610S B. each has certain characteristics that may be desirable for certain environments.P. http://education. .00 4-37 2003 Hewlett-Packard Development Company.hp.P.Module 4 Data Protector Basics Nightly leveled incremental increases in size and duration and includes changes since the previous nightly leveled incremental backup Full + Mid-day Incremental + Daily increasing Level Incremental Full backup at the beginning of the week Mid-day incremental executed daily Leveled incremental using an increasing level number is executed at the end of each day Each mid-day incremental is assumed to be nearly equivalent in size and duration and includes the changes since the previous nights backup Nightly leveled incremental is assumed to be nearly equivalent in size and duration and includes the changes from the previous nights leveled incremental Recovery may require multiple tape sets and may take longer to perform http://education. L.com U1610S B. Module 4 Data Protector Basics 4–24. Open the Session folder of the Object folder to view the data. U1610S B.P. http://education. SLIDE: Verify the Backup Session Verify the Backup Session Context Tabs to change data view Highlight session Object properties Student Notes After your backup finishes.com .00 4-38 2003 Hewlett-Packard Development Company. you can review the operation from the database context within the GUI. L.hp. insert that one instead (it makes the mount request appear sooner). L.P. a restore will be started to retrieve a file from the tape following its removal from the Cell Manager.00 4-39 2003 Hewlett-Packard Development Company. 2.com U1610S B. Select the Restore context in the GUI. http://education. .Module 4 Data Protector Basics 4–25. Start a Restore As the root/Administrator user on the system where the backup was performed remove a file or sub-directory (folder) that was included in the previous backup job. 1. Select your object (file system) as shown on the graphic above. Remove the backup tape from the drive. 4. Select the Options tab in the Results Area. 3. SLIDE: Perform a Restore Perform a Restore Context Tabs to change restore options Highlight object Pop-up dialog allows for media preview Select items to restore Start the restore Student Notes In the final part of this module. NOTE: This restore should be performed without the tape in the tape drive to force Data Protector to generate a Mount Request for the tape. If you have another tape.hp. 7.com . Proceed to the next page to see how to handle mount requests. Start the restore by selecting the Restore <object_name> button on the bottom of the Results area. http://education.hp.Module 4 Data Protector Basics 5. 6. Select the “List restored files” and “Display Statistical Information” options. L. If you ejected your tape from the device.P. U1610S B. Data Protector will prompt you (after a short delay.00 4-40 2003 Hewlett-Packard Development Company. 8. Select Finish within the “Start Restore Session” pop-up window to proceed with the restore operation. which could be several minutes) with a mount request for the specific tape to complete the restore operation. 00 4-41 2003 Hewlett-Packard Development Company. The Mount Event is used for both backup as well as restore. . we must satisfy that request in order for the files to be restored and for the restore session to complete.hp. Mount requests will remain pending until they are either confirmed or cancelled. L. Having started a restore and created a situation whereby there is a mount request outstanding.com U1610S B. SLIDE: Mount Request (1) Mount Request (1) Device needs a specific tape to continue Student Notes Data Protector uses a Mount Event to notify you that it needs a particular tape loaded into a logical device.P.Module 4 Data Protector Basics 4–26. http://education. If you close this pop-up window. You may use it to confirm the mount request once you have placed the appropriate tape within the device.00 4-42 2003 Hewlett-Packard Development Company. you may still respond to the mount request. http://education. U1610S B.Module 4 Data Protector Basics 4–27.P.com . see the next page.hp. such as backup and restore. SLIDE: Mount Request (2) Mount Request (2) Student Notes Data Protector will present the above window in the form of a pop-up when you are performing interactive operations. L. 00 4-43 2003 Hewlett-Packard Development Company. L. . or you will be back to the same mount request state. http://education. Select the session that is in the Mount Request state. then select the device waiting for the tape. You may also use the pop-up menu while selecting the mount request with the right mouse button. and confirm the request from the Actions menu.com U1610S B.P.Module 4 Data Protector Basics 4–28. SLIDE: Mount Request (3) Mount Request (3) Monitor context Highlight device Student Notes Mount requests may be handled within the monitor context. NOTE: Be sure to place the tape in the required drive before confirming the request.hp. 00 4-44 2003 Hewlett-Packard Development Company. L. There are several ways to have reports generated. SLIDE: Introduction to Reporting Introduction to Reporting Reporting context Wizard to configure report parameters Tasks scope Report to execute Student Notes Data Protector includes very extensive reporting and notification capabilities. Use the report tasks wizard to execute reports interactively. U1610S B.Module 4 Data Protector Basics 4–29. You may want to experiment with the reporting tasks after you have run backup to see the kind of information that is available from the internal database.com . http://education.P.hp. These will be discussed in much more detail later. com U1610S B.P. SLIDE: Reporting Reporting Select report parameters Finish to view report Student Notes Data Protector comes with several categories of reports that may be executed against the internal database. The example above demonstrates the selection of a session for a single session report. Data Protector provides pull down lists within the reporting wizard to make report parameter selections very simple.00 4-45 2003 Hewlett-Packard Development Company. L. http://education.hp. You may Cancel or Finish to abort or complete the report execution. . Each report selected within the reporting wizard will require different sets of optional parameters in order to execute.Module 4 Data Protector Basics 4–30. P.hp.00 4-46 2003 Hewlett-Packard Development Company.com . L. http://education.Module 4 Data Protector Basics U1610S B. you will be able to do the following: • • • • Identify the components of a tape library Implement tape libraries on Unix and Windows Understand common library operations Troubleshoot device operations http://education.hp.P.com U1610S B. L. .00 5-1 2003 Hewlett-Packard Development Company.Module 5 — Tape Library Configuration and Implementation Objectives Upon completion of this module. This section will provide general tape library implementation techniques. Students pursuing HP Certification in the HPCP program for tape libraries are encouraged to pursue further studies. U1610S B.com . Student without this particular tape library brand will benefit from the implementation and troubleshooting concepts presented here.P.Module 5 Tape Library Configuration and Implementation 5–1. including the HP course for library installation as well as the MSL Library WBT available on the HP ITRC training site (also available on the classroom systems).00 5-2 2003 Hewlett-Packard Development Company. yet focus on the HP StorageWorks MSL product line of midrange tape libraries. L. http://education. Today HP manufactures and sells a variety of tape devices ranging from single drive DDS units to multi-drive ESL libraries.hp. SLIDE: Objectives Objectives • Overview of Library Components • Library (interface) Connectivity – – SCSI Fibre Channel HP StorageWorks MSL Unix Windows • Implementation of Tape Libraries – – – • Library Operations (via GUI) • Troubleshooting Device Operations – – HP StorageWorks Library and Tape Tools (L&TT) Data Protector Utility Agent (UMA) Student Notes This module focuses on the basic knowledge and skills necessary to successfully implement tape libraries for use with Data Protector. hp. Most tape library systems contain the following components: • • • • • • tape drive(s) repository slots media transport mail slot(s) barcode scanner management interface http://education.00 5-3 2003 Hewlett-Packard Development Company. .com U1610S B. Data is typically written onto high capacity tape cartridges by utilizing multiple tape drives simultaneously. scsi3) NSR (fibre channel/SCSI bridge) • Management interface card – – Student Notes The tape library is a complex system used for near-line or off-line storage of data. The tape library system differs from a standalone tape drive in many ways. L.Module 5 Tape Library Configuration and Implementation 5–2.P. not the least of which is the automated handling (load/unload) of media to/from the embedded tape drives. SLIDE: Library Terminology Library Terminology • Tape drive(s) – Data transfer element Cartridge/magazine slots Storage element Transport element Robotics • Repository slots – – • Media exchanger – – • Barcode scanner • Mail-slot(s) – – Import/export slot Eject element SCSI (scsi2. 1. U1610S B. “Medium Transport Element” o the MSL 5000/6000 Series Libraries have a single SCSI transport slot o repository of tape cartridges. FC and SCSI ports in a single cPCI card that is installed into the card cage at the rear of the MSL library. “Import/Export Element” o other tape libraries (non-MSL) may have external access ports or other numbers of mail-slots (typically 0. L. “Data Transfer Element” ports o commonly referred to as import/export slot or mail slot o MSL libraries may have one (5U models) or two mail slots (10U models) o in SCSI terms. HP MSL libraries may be equipped with either Ultra-2 SCSI (MSL 5000) or Ultra-3 SCSI (MSL 6000) controllers in addition to a Fibre Channel interface called the Network Storage Router (NSR E-1200). stored in magazines in the MSL o in SCSI terms. commonly referred to as elements that are presented: • transport o the robotic that moves tape cartridges between slots and drives o in SCSI terms. http://education.Module 5 Tape Library Configuration and Implementation The SCSI interface within the library presents the various components to all attached host systems as objects. SDLT. LAN.hp. There are usually four objects.com .P. or 5) • • • The management interface card varies depending upon the library.00 5-4 2003 Hewlett-Packard Development Company. The NSR provides Serial. “Storage Element” drive o tape drives such as DLT. LTO o in SCSI terms. and easy serviceability. Combines high-end tape drive technology with advanced robotics. announced in April 2003. SLIDE: Library Introduction (hp MSL) Library Introduction (hp MSL) • Background – – – Designed for backup operations with high-end networks.com .Module 5 Tape Library Configuration and Implementation 5–3.00 5-5 2003 Hewlett-Packard Development Company.P. Combines Digital Linear Tape (DLT). The MSL6000 series library models. L. • http://education. MSL#xyz – medium storage library GUI MSL5000 series library MSL6000 series library (xyz indicates slot count) • HP Midrange Libraries – – – – touch-screen Student Notes Background Designed for backup operations with high-end networks and high-performance servers. Features high availability. Some still sold under this brand. Features high availability and maximum storage density. maximum storage density. • The HP brand was introduced with LTO Ultrium 230 (Gen 1) tape drives and supports high-end SDLT tape drives as well. Super DLT (SDLT) or Linear Tape-Open (LTO) drive technology with advanced robotics. History • • • • The StorageWorks MSL5000 series library models are the first generation. are the next generation of MSL libraries that include features such as: • Auto-power-on • Ultra3 SCSI interface • LTO Ultrium 460 (Gen 2) drives U1610S B.hp. • Introduced under Compaq brand. • Features a GUI-Touch Screen for configuration and management of the library. and features. • Use DLT. • Additional cPCI slots for future expandability. • Multimodule system capability with redundant robotics through the passthrough mechanism (PTM).hp. All models ship with: • A single media cartridge. announced in September 2003. and other supported electronics). SDLT.00 5-6 2003 Hewlett-Packard Development Company. or LTO drives. • A card cage with cPCI backplane. Basic components • • Each model starts with the basic components and then varies depending on the brand name. http://education. • Hot-Pluggable drives. • The 10U models have vertical axis assemblies that enable the shuttle (robot) to access tapes in the upper as well as the lower level of the library. • Two or four magazines (left magazines have mail slots). The DLT8000 drive will be removed from CPL in July 2004. drive type. • Contain up to four removable tape cartridge magazines with either 13 cartridge slots (with DLT or SDLT drives) or 15 cartridge slots (with LTO Ultrium drives). motor drives. up to 4 drives in a 10U model.P. 10U models have dual (redundant) hotpluggable power supplies. • Low Voltage Deferential (LVD) connectivity. • Robotics (cartridge shuttle. Note: The MSL5026DLX will go EOL in October 2003. a library can: • Support up to 2 drives in a 5U model. • An electronics controller card. All models contain: • Fully functional Graphical User Interface (GUI) touch screen. L. • A single cleaning cartridge. may be purchased to upgrade an MSL5000 series library with the auto-power-on feature. • Power supply (5U models have single. motor hardware. • Bar code reader. • U1610S B.Module 5 Tape Library Configuration and Implementation An MSL5000 series library enhancement. Basic description • Depending on the model.com . • The 10U models is similar to having two stacked 5U models. . L.P.com U1610S B.Module 5 Tape Library Configuration and Implementation Drive Compatibility Table Native capacity for available MSL drives based upon drive type: http://education.hp.00 5-7 2003 Hewlett-Packard Development Company. the contents of the mail-slot may be managed by Data Protector via the library manager functions of enter and eject.smb. There are various names for this Import/Export Element and different ways for libraries to provide it. or as 0. or 5 slots Student Notes One of the most common ways of entering and ejecting individual tapes from a tape library is via the mail slot.com . SLIDE: Magazines – Mail Slots Magazines – Mail Slots External Access enter/eject tapes Mail Slot(s) 3D views available at http://www. or 5 reserved slots within the tape magazines. See the Logical Devices module for more details. the lower left magazine slots are numbered 29 to 42. L. If so equipped. On the MSL libraries the first slot in the left magazine tray on each of the upper and lower drawers is the 10U models are the mail slots.00 5-8 2003 Hewlett-Packard Development Company. Other slots within the library are numbered beginning with slot 0 (default is zero. http://education.com Configured in Repository 0. (one in the 5U models). may be changed to start with slot 1 as the first position) which is adjacent to the mail slot.Module 5 Tape Library Configuration and Implementation 5–4. and 43 to 57 in the right. Slots 14-28 are in the right (upper) magazine. Other legacy libraries have implemented this as an external access port. 1. Once implemented. The remaining slots in this drawer are number 1-13. 1.hp. U1610S B.P. For the 10U models this slot is in the upper left magazine.compaq. .P. one of which is used for the mail slot. http://education.00 5-9 2003 Hewlett-Packard Development Company. L.com U1610S B.hp. The MSL 6030 has 30 slots.Module 5 Tape Library Configuration and Implementation In the MSL6060 there are 58 fixed cartridge slots and two mail slots for a total of 60 slots. each U is approximately 1. U is the rack-unit measurement.Module 5 Tape Library Configuration and Implementation 5–5.00 5-10 2003 Hewlett-Packard Development Company. used when multiple modules are configured Some models (MSL 6030.hp.75 inches. This is the required configuration. U1610S B. http://education. L. SLIDE: Rear Panel – 10U Model Rear Panel – 10U Model SCSI ports (2) LAN port Serial (RJ11) port [NSR E1200] Student Notes The graphic above illustrates the rear panel components of the MSL libraries. 6060) ship with the optional embedded Fibre Channel (NSR) board in the slot next to the library controller.com .P. the 5U model is half the size of the 10U) The rear panel provides access to the: Power supply Hot-shoe tape drives Card cage PCI add-in card slots Library controller board (Must be in the far right slot or damage to the library will occur) Cable connections Pass-Through Mechanism (PTM) mounting location. (10U shown. .com U1610S B.hp.P.Module 5 Tape Library Configuration and Implementation Library Controller The library controller board contains a single microprocessor and associated logic devices to control robotic operations and manage overall library functions. L.00 5-11 2003 Hewlett-Packard Development Company. The microprocessor also manages the SCSI interface between the library and the host system. Port Descriptions on the Library Controller VHDCI Library SCSI connections (68 pin) 10-Base-T Ethernet connector RS-232 trace connector http://education. U1610S B. Tape drives are mounted at the rear of the library in a hot-pluggable shoe that permits a tape drive to be removed and replaced while other tape drives and the library robotics remain active. media partitioning is supported only on the HP MSL 5026 and MSL 5052 models with DLT 40/80. http://education. Note: The LTO-2 media cannot be used in the Ultrium 230 tape drive. The Ultrium 230 and the Ultrium 460 may be differentiated by the Ultrium logo at the rear of the drive. SDLT 110/220 and SDLT 160/320. SLIDE: Tape Drives for HP MSL Libraries Tape Drives for HP MSL Libraries • Tape drives available – – – – – DLT 40/80 (DLT8000) SDLT 110/220 SDLT 160/320 LTO Ultrium 230 LTO Ultrium 460 • Mounted in a hot-pluggable shoe • Load handle on DLT tape drive extends from the rear • LTO-2 media cannot be used in the LTO Ultrium 230 drive LTO Ultrium Student Notes The graphic above shows an LTO Ultrium tape drive and shoe mechanism removed from the library.hp.Module 5 Tape Library Configuration and Implementation 5–6. The Ultrium tape drive shoe assembly has a slightly smaller base than the DLT/SDLT tape drives.com . As of April 2003.00 5-12 2003 Hewlett-Packard Development Company. The hot-pluggable capability of the tape drives result in uninterrupted SCSI bus activities during removal or installation. The Ultrium 460 will accept both LTO-2 as well as LTO-1 media. L.P. The DLT tape drive load handle extends from the rear of the drive shoe. Student Notes With the recommended standard Ultra/Wide LVD/SE SCSI HBA interface. HP recommends the following (for maximum performance): maximum of two drives per bus for the MSL 5000 series libraries maximum of one drive per bus for the MSL 6000 series libraries Each of the tape drives and the library controller constitute an independent SCSI target. HBA’s are typically assigned SCSI ID 7 by default. . Each drive in the MSL 5000/6000 series library has a maximum sustained rate of twice the data transfer rate with 2:1 compression on the data.Module 5 Tape Library Configuration and Implementation 5–7. http://education. L.com U1610S B. number of drives. The library robotics imposes minimal loading on the bus. the sustained native transfer rates per drive are: – – – – – 6MB/s for DLT 40/80 drives 11MB/s for SDLT 110/220 drives 16MB/s for SDLT 160/320 drives 15MB/s for LTO Ultrium 230 drives 30MB/s for LTO Ultrium 460 drives • Twice these rates in a two-drive module. SLIDE: SCSI Interface SCSI Interface • With the recommended SCSI interface.hp. and the number of drives connected to the SCSI bus. the data transfer rate of the module (shown above) is achievable.P.00 5-13 2003 Hewlett-Packard Development Company. each must be assigned a unique SCSI ID. When any two or more devices are connected to the same SCSI bus. Actual rates depend upon the type of drive. The standard configuration is a SCSI LVD/SE using two VHDCI-series (ultra high desity) 68-pin. It is possible to use special converter hardware to transform a single-ended bus into a differential one (and vice versa). SCSI-2 SCSI-2 (referred to as plain SCSI) is the second-generation SCSI standard. The bus itself won’t function with both types of devices connected. This signaling scheme has made the two signaling mediums incompatible on the same bus. To connect the library to the host system. Two alternative signaling systems are available when implementing SCSI-2: Single-ended interface — This is “regular” SCSI and uses the type of conventional signaling that is used on other buses. Singleended implementations are the most common. U1610S B. Micro-D SCSI connectors. L. The controller must support LVD/SE. http://education. otherwise the bus will default to single-ended if any SE devices are connected (including the use of a SE terminator instead of the normal LVD terminator. SCSI Evolution SCSI-1 The maximum data transfer speed for this implementation of SCSI is 2 to 4MB/s (actual average is around 2. all devices use different commands. Under SCSI-1.Module 5 Tape Library Configuration and Implementation The library is equipped with a Low Voltage Differential and Single-Ended (LVD/SE) SCSI interface.com .P. Differential interface — The differential SCSI bus minimized the potentialbottleneck created by bus length limitations experienced with single-ended SCSI.hp. Differential interfaces are used externally. resulting in two main groups of SCSI devices and controllers that cannot be mixed on the same bus. The LVD bus must operate with only LVD devices connected. They are suitable for internal cabling. The MSL 5000 series is equipped with an Ultra2 SCSI interface The MSL 6000 series is equipped with an Ultra3 SCSI interface SCSI LVD differs from SCSI-SE in that it overcomes the distance limits imposed upon the single-ended standard through an enhanced signaling scheme.5MB/s). using a limited instruction set. the host must have at least one Wide SCSI controller and the appropriate driver software.00 5-14 2003 Hewlett-Packard Development Company. These two alternatives are incompatible. Note: LVD and HVD (High Voltage Differential) will not operate together on the same bus. It consists of the basic SCSI-1 standard with many additions and some deletions. the tape drive performance may be halved (primarily for linear tape and not for HP LTO due to its Adaptive Tape Speed) http://education. Wide —16-bit data pathway incorporating a 68-pin connector and cable. Two bus speeds are defined in SCSI-2 protocols: Regular Fast SCSI-3 SCSI-3 defines new physical-level transports. SCSI-3 defines a new low-voltage differential (LVD) SCSI specification.00 5-15 2003 Hewlett-Packard Development Company. as a means of transporting SCSI data packets.hp. Backup and Restore Basics Backup Speeds and Feeds The feed speed is the rate at which data is transferred to a tape drive. a 3:1 feed speed to write speed ratio is necessary for tape drives. which are discussed later in this module. LVD SCSI is a technology that combines the advantages of both its predecessors.com U1610S B. IEEE 1394 and Fibre Channel. If the feed speed to write speed ratio is less than 2:1. The HP engineering team in Houston quantified the performance of the entire backup solution and its components. so Wide normally means 16-bit. Feed speed is dependent on many factors. L. Wide can indicate 16-bit or 32-bit buses.Module 5 Tape Library Configuration and Implementation Two SCSI bus widths are defined by the SCSI-2 standard: Narrow — 8-bit data pathway incorporating a 50-pin connector and cable. LVD uses differential signaling techniques instead of single-ended. Ultra2 — Transfer rate of 40MHz (also called Fast-40 or F40). Bus speeds are defined in the SCSI-3 protocols: Ultra — Transfer rate of 20MHz (also called Fast-20 or F20). The write speed is the rate at which a tape drive transfers data to a tape. Basic speeds and feeds of the solution were tested. making the bus more stable.P. . Ultra SCSI buses have a maximum transfer rate of 20MB/s for Narrow SCSI or 40MB/s for Wide SCSI. It will support up to 15 devices on one cable and enables the use of external SCSI cabling up to 12m long. Ultra320 — Ultra320 SCSI is the generation of high-performance SCSI technology that offers data transfer speeds of up to 320MB/s. In order to achieve optimal backup performance. Ultra2 SCSI buses use LVD and has a maximum transfer rate of 40MB/s for Narrow SCSI or 80MB/s for Wide SCSI. The 32-bit variant is rarely used. Ultra3 — Ultra160 SCSI is the generation of high-performance SCSI technology that offers data transfer speeds of up to 160MB/s. ATS reduces performance degradation due to slower data rates as well as minimizes drive wear due to frequent repositioning (DLT) as a result of lack of streaming.hp.com .Module 5 Tape Library Configuration and Implementation 5–8. SLIDE: Library Performance Library Performance Native performance based on drive type Student Notes Native performance of the MSL5000/6000 series library indicated above is based upon: the native sustained transfer rate the number of drives Note: the HP Ultrium drives support Adaptive Tape Speed (ATS).P. L.00 5-16 2003 Hewlett-Packard Development Company. the native capacity would be up to 48 TB and native backup performance would be up to 1. also referred to as Matching Data Rate (MDR).728 GB/hour. if the maximum of four MSL 6060 Library modules (each with four LTO Ultrium 460 drives) are placed in a multi-module configuration. http://education. This multi-module configuration provides: more capacity by adding additional cartridges (52-240 including mail slots) more throughput by adding more drives (2-16) For example. U1610S B. Multi-module Configuration The MSL series libraries support a range of two to eight rack-mounted modules configured into a multi-module mode. http://education. a combination of these connections is found in the backup environment. Typically. 1Gbs(gigabit) or 2Gbs (approximately 100MB/s or 200MB/s both support full duplex operation).com/go/connect.hp.Module 5 Tape Library Configuration and Implementation Storage hardware/software Support for specific hardware and software depends upon the library model and environment. select the link for “automated backup” then the “compatibility and tools” link to locate: the EBS compatibility matrix the HP StorageWorks backup sizing tool Types of Connection The type of connection between the servers and clients to be backed up and the secondary storage system affects the backup performance.hp.P. . Fibre Channel connection between backup server and tape device: Data transmitted over a Fibre Channel connection to the tape device is very fast. L.com U1610S B.00 5-17 2003 Hewlett-Packard Development Company. For the most up-to-date information on: Operating systems Servers SCSI HBAs Fibre HBAs Firmware and drivers Go to the HP Enterprise Backup Solution (EBS) compatibility matrix at: http://www. Network connection between client and backup server: The LAN bandwidth affects the speed at which data can be transmitted between the client devices and the backup server. This connection is typically one of the following: Directly connected SCSI tape device: Devices connected directly to the server through a SCSI connection are very fast at backing up that server. com .P. or processor problems are present Serial RJ-11 connector Ethernet RJ-45 connector Fibre Channel activity LED – indicating port activity Fibre Channel link LED – a valid link exists FC-LC connector SCSI VHDCI connector (2) – green LED indicates port activity U1610S B. L.5m VHDCI-VHDCI) Documentation The components of the NSR: Reset switch (push by using paper clip or other sturdy tool) Power LED Green – power has been applied Yellow – POST is in process. SLIDE: Fibre Channel – SCSI Router Fibre Channel – SCSI Router NSR N1200/E1200-160.E2400.Module 5 Tape Library Configuration and Implementation 5–9.00 5-18 2003 Hewlett-Packard Development Company.hp. NSR 2402 N1200 NSR 2402 E1200-160 Student Notes The MSL 5000/6000 Fibre Channel option kit includes: Network Storage Router (NSR N1200 or NSR E1200-160) Serial Cable Two SCSI cables (. http://education. A true device driver is not required for the proper operation of the NSR. The system requirements are: Windows 2000 Server/Advanced Server with SP2 Minimum KGPSA-CD driver v4-4. See the MSL user guide for more details.Module 5 Tape Library Configuration and Implementation The NSR E1200/E1200-160 is installed in the PCI slot adjacent to (the left of) the library controller board. Windows 2000 Device Driver The NSR E1200-160 uses a null device driver (hp_cpq_router. The router OS supports HTTP (management). The N1200/E1200 support Ultra2 LVD SCSI interfaces. When installing the NSR into the Opal colored (Compaq brand) MSL 5026. look for “Installing the Thermal Upgrade Kit” topic. while the E1200 is an embedded cPCI card.P.inf installs a null device driver and creates a device entry under System Devices in the Device Manager.com U1610S B. Insertion of an option card into the library controller board slot damages the PCI backplane and renders the library inoperable. Caution! The library controller board must always be housed in the correct option slot (right most position when facing the rear of the library). set the router to user Port 0 or Port 1 map The NSR supports indexed maps containing a Fibre Channel controller LUN not default not necessary for Windows OS as long as there are less than 8 devices attached use the Port 0 or Port 1 mapping When controller LUNs are enabled (SCSI array controller device at FC LUN0) the Windows 2000 Device Manager will discover the controller device and prompt for the installation of a device driver. L. The M2402 is a modular solution delivering end-to-end throughput in excess of 300MB/s. FTP. The N1200 is an external storage router.53a7 Minimum FCA-2101 driver version 4-4.54a7 and 5-4. The hp_cp_router. there is a requirement to install a cooling kit.54a7 HP recommends using the latest available drivers The NSR supports SCC Fibre Channel device maps not recommended recommendation. http://education. .inf) on Windows 2000. The NSR E2400 solution is designed for embedded use in the HP StorageWorks ESL tape libraries.hp. TELNET and SNMP over the network interface in addition to the serial port access. There is a section in the WBT as well.53a7 and 5-4. The HP StorageWorks NSR m2402 The M2402 network storage router is an external 1U rack-mount Fibre Channel-to-SCSI router with two Fibre Channel ports and four Ultra-3 160 SCSI ports expandable to eight ports.00 5-19 2003 Hewlett-Packard Development Company. the M2402 has a maximum bandwidth of 300MB/s. under the Unknown Device category. http://education. (diskette. Optimizing Performance on the Network Storage Router In order to optimize performance.inf file. network storage routers will support up to two drives per port for most tape drives except Ultrium 460. Supported and optimal configurations U1610S B. Select the driver page. a maximum of one tape drive per SCSI port is always the best configuration. Windows 2000 hardware discovery wizard When the wizard discover the controller device and prompts for installation of driver.inf). and browse to the hp_cpq_router.com . The file may be found on the HP StorageWorks network storage router documentation CD in the \pdfs\cpqnsr directory.00 5-20 2003 Hewlett-Packard Development Company. but the e2400. L. Windows 2000 device manager From the device manager. browse to the location of the hp_cpq_router. These options will populate the system registry with the necessary device information. e1200. and N1200 support Ultra2 SCSI. the Hardware Discovery Wizard will scan the INF directory for installation instructions and automatically install the device driver.inf file to the C:\WINNT\INF directory and restart the system During the startup process. However. right-click the NSR and select properties. In addition.inf (formerly cpqnsr_e1200. The M2402 supports Ultra3 SCSI .P.Module 5 Tape Library Configuration and Implementation Installation of the null device driver There are three options that may be used to install the null device driver for the NSR onto Windows 2000. CD. click Update Driver. or temporary directory) Copy the inf file to the C drive Copy the hp_cpq_router.hp. Limitations of the network storage routers include the type of SCSI interface on the router as well as the router’s bandwidth. com . http://education. or both magazines by opening the doors for tape cartridge removal or replacement o may be password protected Move media o allows movement of media within the library from one element to another o may be used to move cleaning cartridge from a reserved slot to a drive U1610S B. SLIDE: Library Operations/Configuration Library Operations/Configuration Status (main) screen options • Technical Support Information • Mail Slot Access • Magazine Access • • • • • • Move Media LCD Contrast Controls Menu Online Status Power Student Notes Navigating the GUI touch screen The library status screen is the gateway to the operations of the MSL library. Selecting options from this screen allow for operational control and access to information about the library.Module 5 Tape Library Configuration and Implementation 5–10.P. L.hp. Options for the MSL 5000/6000s: Technical Support Information (HP in the menu) Mail Slot Access (not present if disabled) o may be password protected or disabled allows access to a mail slot to remove or insert tape cartridges Magazine Access o allows access to left or right magazines.00 5-21 2003 Hewlett-Packard Development Company. com .Module 5 Tape Library Configuration and Implementation Menu o allow for viewing. You can also use a higher level password to gain access to a lower level operation. the fourth security level is Factory and is reserved for HP. To restore passwords if forgotten. and Service). As a result. use Set User Defaults using the MSL5000 Utility and diagnostic (serial) cable. Online o allows the library to be placed online or offline o default setting is online after power-up initialization Status o view tape drive types o physical tape drive status including cleaning status o cleaning cartridge information Security Levels The MSL5000/MSL6000 Series Library features GUI touch screen security to prevent unauthorized access to the library operation. Password Each password is represented by four decimal digits that are stored in NVRAM in a range of 0001 to 9999.P. The GUI touch screen offers four levels of security. Only the first three are supported in the field. Enabling a password at a lower level re-enables disabled higher levels to that value. Note: 0000 is used to disable password verification for that level. For example. prior to accessing any higher level operation. use the Service password to access the Move Media option. configuring and operating the library.hp. http://education. Using the Service password to access the Menu option also gives full access (without validating) to the Service operations.00 5-22 2003 Hewlett-Packard Development Company. L. you are prompted first to enter the new higher level password. level2. (level1. see appendix for more details. U1610S B. Note: Any configuration that was previously set will be lost. and secure the library. and “Edit Options.com U1610S B.00 5-23 2003 Hewlett-Packard Development Company. and operate the library. diagnose. The options available are: Library Options SCSI Options Network Options Library Info Cartridge Map Utilities . • GUI Simulator (NeoSimHp_414.hp. • Screen has three areas: – – – View System Data Utilities Edit Options • Each option button in these areas brings you to other options that further define the desired task.lets you maintain.lets you view the library data. • See the WBT or user guide for detailed information.exe installed on classroom systems) Student Notes Navigating the GUI touch screen Selecting the Menu option from the library Status screen allows you to view. and operate the library. L. . http://education.Module 5 Tape Library Configuration and Implementation 5–11.P. “Utilities”. configure. The three distinct menu areas are “View System Data”. SLIDE: Menu Screen Menu Screen • Use this screen to view. configure.” View System Data . P. SCSI. U1610S B. Choose Lightening for 2-drive 5U models. The options available are: Library SCSI Network Passwords Use the GUI simulator.00 5-24 2003 Hewlett-Packard Development Company.com . http://education. L. installed on the student systems to practice navigating the menu option. and network options.Module 5 Tape Library Configuration and Implementation The options available are: Maintenance Diagnostics Factory Security Level Edit Options . Thunder for four-drive 10U models.lets you set library.hp. and Level 2 for administration. There are two screens to configure.P. both shown above. SLIDE: Configure Network Access Configure Network Access • Specify Network Address • IP Address • IP Mask (subnet mask) • IP Gateway (router) • DNS Server IP • Enable Remote Management • • • • • Level 1 web login (alpha-numeric) Level 2 web login (alpha-numeric) Enable Web Secure Login Allow Web Level 2 Access Library Name Student Notes The MSL supports remote management via the network interface once it is configured from the GUI touch screen. Note: the GUI touch screen defaults to a level 1 password of “1” and level 2 password of “2”.com U1610S B. First configure the network identity. The service password defaults to “5566”.Module 5 Tape Library Configuration and Implementation 5–12. The default network configuration should be changed to allow for this remote access. L. and then enable the Level 1 and Level 2 web logins. .00 5-25 2003 Hewlett-Packard Development Company. Level 1 is primarily for operations. Enable an alphanumeric string for both level-1 and level-2 as desired. http://education. Service level access is not available from the RMI. web enabled). The RMI allows for a different password (login) than the GUI touch screen. Library maintenance is not available from the Remote Management Interface (RMI. Each web login provides access to a portion of the library functionality.hp. 3. each offering multiple settings to support a variety of applications and platforms.P. The exceptions are host and network specific settings. Return to Main menu. 5. 7.00 5-26 2003 Hewlett-Packard Development Company. http://education.com . Touch Save to confirm your change. L. Repeat these step for each SCSI ID. Available options (in order of appearance): Library Options: Reserved slots (used for cleaning cartridges) Configuring the master module Configuring the slave module SCSI Options: Setting SCSI IDs Setting element bases Network Options: Setting IP address (must be altered for site network connectivity) U1610S B. – A numeric keypad displays.Module 5 Tape Library Configuration and Implementation 5–13. Touch the desired SCSI ID number on the keypad. 4. The setting of each option is stored in NVRAM in the module. Touch one of the following buttons: – OK to confirm the new value. Touch the box next to the SCSI ID you wish to change. many of the factory defaults will be sufficient. For most applications. – The number displays in the New section. – Cancel to cancel the change 6.hp. Student Notes The library is designed with many configuration options. Navigate as follows: Status Screen → Menu → SCSI → <the desired SCSI ID>. 2. SLIDE: Setting SCSI IDs Setting SCSI IDs To set SCSI IDs: 1. Repeat the steps for each SCSI ID that is to be modified Return to the main menu http://education. or Cancel. configure each drive with the corresponding SCSI ID (if possible). . L. 6. 7. 3. a numeric keypad appears. 5. SCSI 1. For example set the ID for Drive 0 to be SCSI 0.Module 5 Tape Library Configuration and Implementation Setting SCSI IDs Each tape drive installed within the library requires a unique SCSI ID.P. Touch the Save button to confirm the change Touch one of the following: OK.hp.00 5-27 2003 Hewlett-Packard Development Company. 4.com U1610S B. etc. For easier manual configuration (identification) of the tape library drives within Data Protector. Select the desired ID number using the keypad. the SCSI IDs may be modified. Navigate the GUI touch screen as follows: Status Screen Menu SCSI (in the Edit Options area) <the desired SCSI ID> 2. To set the SCSI ID: 1. After the library is physically installed and powered on. Touch the box next to the SCSI ID that is to be changed. Drive 1. 82. L.00 5-28 2003 Hewlett-Packard Development Company. SLIDE: Remote Management Interface Remote Management Interface Web Level 1 or Level 2 login Student Notes Shown above is the “Login to the Remote Management Interface” for the HP StorageWorks MSL.P. To access the Login screen.Module 5 Tape Library Configuration and Implementation 5–14.hp. The password must be configured via the GUI touch screen. For example: http://156. There are two different access levels (level 1 or level 2) each with a different password.com . http://education.152.114 U1610S B. enter the IP Address of the tape library into a web browser (the IP name will not work!). See the previous page “Configuring Network Access” for web login details. By selecting the library unit.hp. the tape library automation management console appears. L.00 5-29 2003 Hewlett-Packard Development Company. Along the top of the web interface are the function buttons that allow for remote management and monitoring. allowing for selection and access to the tape library.Module 5 Tape Library Configuration and Implementation 5–15. http://education.P. SLIDE: Web-based Remote Library Management Web-based Remote Library Management Student Notes After a successful login. the logical inventory is displayed. .com U1610S B. 00 5-30 2003 Hewlett-Packard Development Company.hp. The factory defaults are: IP address: Subnet mask: Gateway address: User name: Password: http://1.255. Use the FTP method for this backup to a connected host. L.0 0.255. U1610S B.0. http://education. SLIDE: Configuring the NSR Configuring the NSR Default Login: User name: root Password: password Student Notes Default Ethernet settings for the NSR E1200/E1300-160 HP recommends that all of the factory default values for the Ethernet configuration be changed to site specific values.com .1/ 255.0.1.0 root password These settings may be backed up to a configuration file and restored back to the router in case the settings need to be recovered.1.Module 5 Tape Library Configuration and Implementation 5–16.P. • For procedural information on accessing and changing these settings. forcing the router to negotiate a fabric only mode. SCSI bus configuration The router can appear on a SCSI bus as a pair of initiators. . Note: By default. Not supported on most tape drives (July 2003). Controller LUN Commands. Recommendation: Leave as NONE. If set incorrectly and the router is plugged into a Loop or Fabric. Controller LUN commands The router supports a set of SCSI-3 commands that can be received as FCP commands over the Fibre Channel port. • For more information.00 5-31 2003 Hewlett-Packard Development Company. such as for 1 GB/s. Fibre Channel port By default. the Fibre Channel port speed is set to 2 GB/s. L. Visual Manager User Interface. • The primary Initiator ID can be set to any valid SCSI address (0-15) and is used for most traffic. the unit may receive framing errors. The following slides identify configuration settings that are commonly modified and are available in the Visual Manager UI and the Serial/Telnet UI. Serial/Telnet User Interface. • The router can appear as one or more Target ID on a SCSI bus.com U1610S B.Module 5 Tape Library Configuration and Implementation Common NSR configuration settings Configuration settings To provide connectivity between hosts and devices. Changes to the Fibre Channel port speed must be manually set. which can be found in the trace logs. • Chapter 4. see the NSR e11200-160 user guide: – Appendix B.P. the router must establish an address on each connected Fibre Channel network and SCSI bus. see the NSR e1200-160 user guide: • Chapter 3. the router is identified to the switch as a unique device by the factory programmed World Wide Name (WWN). and the fiber link light will be off because of the incorrect Fibre Channel link speed. http://education.hp. they must be sent to the Controller LUN. • The alternate Initiator ID can also be set to any valid SCSI address (0-15) and is for use with high priority traffic. Fibre Channel switched fabric When connected to a Fibre Channel switch. • The Initiator IDs (primary and alternate) should not be set to the same SCSI address and no other devices on the SCSI bus may use either of these SCSI addresses. (Not supported as of July 2003. When using these commands.) • By default. no Target IDs are set up. the configuration of the Fibre Channel ports is set to N_Port. These commands provide support for value added features such as Extended Copy (a value added option). This sequence is appropriate for tasks such as file backup or restore. when cables are attached or a hub is rebooted). depending on the port in question. • HP recommendation: To map devices to the host. use Port 0 and 1. • Auto Discovery can be disabled by setting the router to Manual Discovery. In these instances. Logical unit management Because SAN resources can be shared. the Buffer Tape Writes option must be disabled. http://education. and status is not returned until the device completes the command.00 5-32 2003 Hewlett-Packard Development Company. it is possible for multiple hosts to have access to the same devices on the SAN. the router provides LUN management as a means to restrict device access to certain hosts. If data does not transfer correctly. LUN management goes beyond simple LUN masking. to prevent gaps in the list of LUNs presented to a host. Buffered tape writes This option is designed to enhance system performance by returning status on consecutive write commands prior to the tape device receiving data.P. the router returns a check condition on a subsequent command. U1610S B. Refer to the HBA manual for the mapping table. Commands other than Write are not issued until status is received for any pending Write. To prevent conflicts.com .Module 5 Tape Library Configuration and Implementation Discovery mode This feature makes it easy to discover attached SCSI target devices and automatically map them on the INDEXED MAP for the bus/port in question. • These devices get automatically mapped to the INDEXED map. L. Host device A host system using a Fibre Channel Host Bus Adapter (HBA) will typically map devices into the existing device-mapping scheme used by that operating system. such as for audit trail tapes or log tapes. Note: This is a type of “mapping protection” so only known hosts will have access to the maps.hp. There are two discovery methods available: • Manual discovery • Auto discovery • Auto Discovery can be set to occur after reboot events (when the router reboots) or link-up events (for instance. Some applications require confirmation of individual blocks being written to the medium. L. A map defines the devices accessible through a particular Fibre Channel port (on the NSR). Shown above are the default configurations obtained without specific mappings defined. This default may not be optimum depending upon the desired level of access to the tape library controller and drives. all hosts have access to all devices. Multiple maps may be created for a single Fibre Channel port. The NSR discovers the WWN of the connected FC switch as well as the WWN of the hosts connected via the FC switch. . SLIDE: Fibre Channel Mapping (per host client) Fibre Channel Mapping (per host client) Switch WWN Host WWN’s Host assignment Map Edit Student Notes The Mapping Menu is used to view and modify the host-to-map information for a Fibre Channel port.00 5-33 2003 Hewlett-Packard Development Company.com U1610S B. The Administrator then assigns each host a map for each Fibre Channel port. Fibre-Channel to host mapping provides a form of LUN security. http://education. edited or deleted. In the default configuration. similar to that used by most SAN connected disk arrays.P.hp. Maps and hosts may be added.Module 5 Tape Library Configuration and Implementation 5–17. SDLT. The Ultrium 460 has a native data rate of 30MB/s.hp.com U1610S B. or DLT tape drives. double that if 2:1 compression is achieved. • Use separate HBA for disk subsystem.00 5-34 2003 Hewlett-Packard Development Company. the total PCI bandwidth needs to be more than double the backup rate. or DLT tape drives for the disk and tape devices http://education. Student Notes With high-speed tape devices. .Module 5 Tape Library Configuration and Implementation 5–18. – Example: More than 200MB/s for a single Ultrium 460 tape drive. The HBA burst rate must meet the following: Ultra2 SCSI supports 80MB/s – limits Ultrium 460 Ultra3 SCSI supports 160MB/s – needed for the Ultrium 460 Ultra4 SCSI supports 320MB/s – currently faster than needed Use separate HBAs for each Ultrium 460 tape drive for every two Ultrium 230. for every two Ultrium 230. L.P. • For optimum performance. SDLT. consider the following: The HBA must be able to transfer data at maximum tape speeds. SLIDE: HBA Connectivity (topology) HBA Connectivity (topology) • Use separate HBAs – – for each Ultrium 460 tape drive. com U1610S B. HP recommends: Multiprocessor or single 1+GHz processor with at least 512MB of system memory 64-bit/66MHz PCI and HBAs o o PCI-X (133MHz) is better 32-bit/33MHZ may degrade the performance on the high-speed tape drives Dedicated IRQs for disk and tape HBAs No other applications running during backup. such as: o o o Virus scans Disk defragmenters CPU-intensive screen savers http://education. L.hp. . For a single Ultrium 460 tape drive the bandwidth must be more than 200MB/s to be able to achieve maximum drive backup performance.P.00 5-35 2003 Hewlett-Packard Development Company. For high-speed tape devices connected to “Wintel” systems.Module 5 Tape Library Configuration and Implementation For optimum performance. the total PCI bandwidth needs to be more than double the backup rate. L. such as: o Virus scans. Disk defragmenters.00 5-36 2003 Hewlett-Packard Development Company.com U1610S B. SLIDE: Server Consideration Server Consideration For high-speed tape drives.P. For a single Ultrium 460 tape drive the bandwidth must be more than 200MB/s to be able to achieve maximum drive backup performance. HP recommends: Multiprocessor or single 1+GHz processor with at least 512MB of system memory 64-bit/66MHz PCI and HBAs o o PCI-X (133MHz) is better 32-bit/33MHZ may degrade the performance on the high-speed tape drives Dedicated IRQs for disk and tape HBAs No other applications running during backup.Module 5 Tape Library Configuration and Implementation 5–19. CPU-intensive screen savers http://education. For high-speed tape devices connected to “Wintel” systems. HP recommends: • Multiprocessor or single 1+GHz processor with at least 512MB of system memory • 64-bit/66MHz PCI and HBAs – – PCI-X (133MHz) even better 32-bit/33MHz may degrade high-speed tape drive performance • Dedicated IRQs for disk and tape HBAs • No other applications running during the backup. the total PCI bandwidth needs to be more than double the backup rate. such as: – – – Virus scans Defragmenters CPU-intensive screen savers Student Notes For optimum performance. .hp. The EBS platform support matrix is available at: http://www.com/go/connect under the “Automated Backup” link. a number of preliminary steps must be completed on the host running Windows operating systems (NT and above). Test with HP Library and Tape Tools (Optional. . depends on backup software capabilities) Test with native backup tools (NTbackup. L. Power up sequence: FC switch (usually takes several minutes to complete the boot up (5-6 minutes for B-series switches)) MSL Library (allow boot up to complete.P. NSR and MSL. or reboot and discovery will have to be run) Hosts (may be already powered on depending upon the operating system) http://education.Module 5 Tape Library Configuration and Implementation 5–20. Install and verify the supported Fibre Channel HBAs.hp. Verify that the host sees the library drives and robotics. SLIDE: Logical Device Files Logical Device Files To set up the library to operate under EBS: • • • • • • • Identify the HP platforms supported by EBS. Update firmware. green LED on library front glows steady) NSR (must be powered after MSL.00 5-37 2003 Hewlett-Packard Development Company. tar) Student Notes Prior to use as an Enterprise Backup Solution (EBS) client or server. the power up sequence is very important for host access to the devices connected to the NSR. if necessary. Power Up Sequence After verifying the configuration of the HBA.com U1610S B.hp. Install HBA drivers. In some cases. or manually invoked) lssf – display properties for specific device files lsdev – list the available device drivers in the system ioscan – scan and display all system devices and associated device files HP-UX drivers for tape library controllers: sctl – requires the manual (mknod) process for creating device files schgr – automatically binds to library controller devices at boot time. Updates to the SRM firmware are regularly released. Firmware version 5. consult the support matrix for details. and configured so that it can become part of an overall EBS environment AlphaServers utilize a robust hardware console known as the System Reference Manual (SRM). Once patched. The server must be installed for Fibre Channel operation with Tru64 UNIX. patched. supports insf device file creation U1610S B. operating system capabilities must be disabled to allow the backup application (Data Protector) to access the library system. L.P. Detailed configuration of the logical devices is covered in the next module. HP-UX includes many tools for managing devices files. Logical Device files on HP-UX The HP9000 is supported running 11.hp. the FC devices are automatically detected by the OS and device files are created.Module 5 Tape Library Configuration and Implementation Logical Device files on Windows Configuration at the operating system level is a critical point that is necessary for the application to see the devices. There are a few patches necessary for support of EBS. the most common are: mknod – manually creates device files insf – automatically creates device files (runs at system startup. Logical Device files on HP Tru-64 Prior to its use as an EBS client or server (device server) a number of preliminary steps must be completed on an AlphaServer running Tru64.com .00 5-38 2003 Hewlett-Packard Development Company. http://education.7 or higher is required to function with EBS.x as an EBS client or server. and may hang if the RSM is enabled.com U1610S B.P.Module 5 Tape Library Configuration and Implementation 5–21. SLIDE: RSM Enabled for Windows 2000 RSM Enabled for Windows 2000 Disable Library RSM for Data Protector use! Student Notes When tape libraries are to be used with Data Protector. .00 5-39 2003 Hewlett-Packard Development Company. The device agent will not be able to access the library.hp. The Data Protector device agent (devbra –devices) cannot properly access the library drive(s). http://education. Shown above is the result of having the RSM enabled while trying to use Data Protector to configure the device. the Windows 2000 Removable Storage Manager must be disabled for the tape library or Data Protector will not be able to access the library successfully. L. Module 5 Tape Library Configuration and Implementation 5–22. Once disabled. U1610S B. SLIDE: Disable RSM for Library on Windows 2000 Disable RSM for Library on Windows 2000 Student Notes Shown above is the simple procedure for disabling the Windows 2000 RSM for a selected library.00 5-40 2003 Hewlett-Packard Development Company.P. Data Protector will be able to function correctly when accessing the library.com .hp. See the next slide for details. L. http://education. etc.).hp. initialization. restore.com U1610S B. Proper device detection by the Data Protector device agent is necessary for successful for all Data Protector media accesses (backup.Module 5 Tape Library Configuration and Implementation 5–23. http://education.P.00 5-41 2003 Hewlett-Packard Development Company. SLIDE: RSM Disabled for Tape Library RSM Disabled for Tape Library Student Notes Shown above is the result of having the RSM disabled for the library to be configured with Data Protector (covered in more detail in the next module on logical devices). L. . where C indicates the use of hardware compression. The first step in testing is to determine the device file associated with the tape library.Module 5 Tape Library Configuration and Implementation 5–24. the path to the tape device shown is Tape1:0:6:0C.P. Shown above are the Windows Device Manger screens showing the SCSI paths for the library changer and tape device. http://education.00 5-42 2003 Hewlett-Packard Development Company. Windows uses the device name: Bus: Target: Lun as the path to the devices.hp. where 0:5:0 is the Bus: Target: LUN for the device. The Data Protector Media Agent provides two programs for tape devices (installed in the C:\Program_Files\Omniback\bin directory by default: devbra – (device agent) used for device discovery and configuration uma – (utility media agent) used for tape library management U1610S B. For example. L. The changer is identified as Changer0:0:5:0. This is a recommended step prior to use with Data Protector.com . SLIDE: Windows SCSI Device Paths Windows SCSI Device Paths Changer0:0:5:0 Tape1:0:6:0C (hw compression) Student Notes Once installed onto the host operating system a tape library may be tested to determine if it is operating correctly. stat list available commands SCSI inquiry SCSI element status (Transport. locate the device path for the tape library robotics (media changer) 3. Once known these devices may be tested with the Data Protector Utility Media Agent (UMA) to determine operational status. Slots) d. L. Export.P.00 5-43 2003 Hewlett-Packard Development Company. execute some “UMA” commands to test library operations a.com U1610S B. help b. Drives. .Module 5 Tape Library Configuration and Implementation Shown above are the results of navigating the Windows (2000) Device Manager to determine the device paths for the tape library controller as well as the tape drive(s). etc.) C:\Program Files\Omniback\bin\uma –ioctl <dev> -barcode example path as reported by devbra: C:\Program Files\Omniback\bin\uma –ioctl Changer0:0:5:0 -barcode 4. inq c. Data Protector procedure for device discovery and testing: 1.hp. move <from> <to> move media from element to element (return to original position when testing is completed. status inquiry. invoke the utility media agent to interact with the tape library (load/unload tapes. scan the system for available devices (shows the Windows device paths) C:\Program Files\Omniback\bin\devbra –devices 2. use integer value or element name) http://education. U1610S B.255. it is up to the system administrator to perform this task when it is convenient.8. http://education. The needed device files will automatically be created after this procedure as long as the needed device drivers are already loaded into the kernel.0.hp.11.8.7. L. HP-UX does not continually scan for new devices.P.Module 5 Tape Library Configuration and Implementation 5–25.7 1/2/0/0.0 scsi1 target spt CLAIMED INTERFACE HP 28655A .SE SCSI ID=7 CLAIMED DEVICE CLAIMED DEVICE HP C5177-7000 Student Notes Mastery of devices and associated files on UNIX requires a bit more knowledge than for Windows systems. some additional (manual) steps will be needed to enable missing devices. After the system starts.11 1/2/0/0.com . as well as when new devices are connected to the SAN while the system is running.4.0.255. The HP-UX operating system typically creates device files at system startup for all known hardware devices that are powered on prior to the system startup. SLIDE: HP 9000 Hardware Addressing HP 9000 Hardware Addressing Components of Hardware Path • Bus Adapter Path • SCSI Target • Device Unit (SCSI LU) – Fibre Channel/SCSI ext_bus target autoch 13 17 1 1/2/0/0.7.8.4 56/52. It is common for administrators to execute these steps when LUNs are added to disk arrays.0.0 fcpdev tgt schgr CLAIMED CLAIMED CLAIMED INTERFACE DEVICE DEVICE HP C7200-8000 FCP Device Interface – SCSI ext_bus target spt 2 4 0 56/52 56/52.255. Administrators must be able to build a kernel with the appropriate drivers and in some cases even create (manually) the necessary devices files.00 5-44 2003 Hewlett-Packard Development Company. the library includes a protocol converter interface card (NSR in MSL libraries).hp. or SCSI LUN.Port) SCSI emulation: 0.198. The most common interface is SCSI.P. the SCSI target ID.Target.Module 5 Tape Library Configuration and Implementation Host Connections The tape library systems typically connect to the Host Bus Adapter of the host system or systems. The three main components of the hardware path displayed by ioscan include: the controller (host bus adapter). still displays the ext_bus as the class of the device controller. the actual hardware path for the controller can represent several different parameters including the back-plane slot of the interface card and all of the Fibre Channel values (varies by switch type). http://education.1 (Bus. however. connected via switch or switched fabric.9.23. the controller is simply the system path from the system bus to the SCSI device.3. The key to the configuration of the library controller device is the location and identification of the ext_bus interface that connects to the library device. and the device unit number.198 (Domain. Example FC address components: HW Path: 0/4/0/0.Area. In this case the library is SCSI.00 5-45 2003 Hewlett-Packard Development Company. When this is the case. the library system will connect to the host via Fibre Channel and then to the internal drives and library controller with SCSI. if the device is on a public or private loop. ioscan will still show the hardware path to the library controller and SCSI devices as if they were “local” devices. Once this is known we can easily locate the SCSI target and LU of the controller that needs to be configured. although Fibre Channel connections are becoming increasingly common.1 Host Bus: 0/4/0/0 (HBA path) FC switch topology: 9. Knowledge of the hardware used to connect the library system is critical to the understanding of the device file that is used to control the library operations.3. In some cases. It does not matter from a local perspective. but is connected to the host through the bridge device. and it will be displayed as a class of device called ext_bus by the ioscan command.Lun) In the case of Fibre Channel. HP 9000 Hardware Addressing The hardware addressing for the SCSI library is essentially the same regardless of whether the library is connected directly to the host or by way of some protocol conversion device that is internal or external to the library. Another possibility is the connection of the SCSI library to a SCSI/Fibre bridge device. . L. In the case of the SCSI connected device. The ioscan command. The three components will be used to construct the minor number (once converted to hex) used to create the device file for the library controller.0.23.com U1610S B. 255) of the FC device.255. it is available and supported but not as widely used as the sctl driver.0 schgr CLAIMED DEVICE HP MSL5000 Series /dev/rac/c7t0d0 tape 1 0/2/0/0.255. Lun 1 is the first drive and Lun 2 is the second drive.hp.3.2 stape CLAIMED DEVICE HP Ultrium 1-SCSI /dev/rmt/2m /dev/rmt/c7t0d2BEST /dev/rmt/2mb /dev/rmt/c7t0d2BESTb /dev/rmt/2mn /dev/rmt/c7t0d2BESTn /dev/rmt/2mnb /dev/rmt/c7t0d2BESTnb ctl 5 0/2/0/0.255.P.1. The example above shows the LUN mode for the Network Storage Router.Area. The typical output for lsdev shows the major number 203 for the sctl driver. If the drivers are configured into the system.1.1 stape CLAIMED DEVICE HP Ultrium 1-SCSI /dev/rmt/1m /dev/rmt/c7t0d1BEST /dev/rmt/1mb /dev/rmt/c7t0d1BESTb /dev/rmt/1mn /dev/rmt/c7t0d1BESTn /dev/rmt/1mnb /dev/rmt/c7t0d1BESTnb tape 2 0/2/0/0. may have side effects while applications such as backup are running) insf new (missing devices) should be created (use –e for existing devices for which device files are missing) The Device File (manual creation) The components of the device file include the mode.0.0 tgt CLAIMED DEVICE autoch 0 0/2/0/0.0 fcpdev CLAIMED INTERFACE FCP Device Interface target 15 0/2/0/0.Module 5 Tape Library Configuration and Implementation Sample MSL 5030 connected to a B-series switch and HP 9000 server running HP-UX 11i: Class I H/W Path Driver S/W State H/W Type Description ============================================================================= ext_bus 7 0/2/0/0.Port (1.255. The ext_bus path includes the hardware path of the HBA as well as the Domain.0.3. These may be collected by using the ioscan and lsdev commands.0. the other choice of mode is block mode. The mode used for the library device is character.00 5-46 2003 Hewlett-Packard Development Company. This Lun addressing mode is used when the NSR is enabled for Active Fabric mode to support the use of the Xcopy serverless backup mode. where Lun 0 is the tape contoller.1.1. L.0.0. The minor number is the hardware path converted to hexadecimal.255.0.1. U1610S B.3. In order to create a device file for use in controlling the tape library. HP-UX device discovery ioscan –fn (use with caution. major number and minor number as well as the device name. the target device is 0 (last digit of the HW path for the target class device) and the Lun number is 0 (last digit of the HW path for the autoch class device) producing a device file: /dev/rac/c7t0d0 for the autochanger device (library controller/robotic).0. The HP-UX command kmsystem may be used to check if the drivers are available on the system.255. the lsdev command will display them along with their character major number.11 (11i) do not have the schgr driver configured by default. This command will also display the configured state for the driver.1. The major number is the numeric value associated with the device driver.3 sctl CLAIMED DEVICE COMPAQ SWMODULAR ROUTER /dev/rscsi/c7t0d3 Notice: The device instance for the ext_bus class device is 7 (I column). and this is used for disk type devices.3. Most HP-UX systems prior to HP-UX 11.0. 231 for schgr.3. http://education.3. you will need to gather all three components.0.com .3. http://education.Module 5 Tape Library Configuration and Implementation Converting a hardware path to a (hex) minor number (output from ioscan –f): Fibre Channel/SCSI (private loop or point to point. domain id=8) 1/2/0/0.0 scsi1 target spt CLAIMED CLAIMED CLAIMED INTERFACE HP 28655A DEVICE DEVICE HP c#t#d# (c2t4d0) Example creating a device file using mknod with output from ioscan –fn and the sctl driver: Class I H/W Path Driver S/W State H/W Type Description ======================================================================= ext_bus 1 8/4 c720 CLAIMED INTERFACE GSC add-on Fast/Wide SCSI Interface target 3 8/4. Once the devices are known.hp.P.7 fcpdev CLAIMED ext_bus 13 FCP Device Interface tgt CLAIMED target 17 1/2/0/0.8. L.8.0 tgt CLAIMED DEVICE UNCLAIMED UNKNOWN HP C7200-8000 unknown -1 8/4.0 stape CLAIMED DEVICE QUANTUM DLT8000 /dev/rmt/1m /dev/rmt/c1t1d0BEST /dev/rmt/1mb /dev/rmt/c1t1d0BESTb /dev/rmt/1mn /dev/rmt/c1t1d0BESTn /dev/rmt/1mnb /dev/rmt/c1t1d0BESTnb mknod /dev/lib_cntl c 203 0x010000 8 bit major number 24 bit minor number 8 bit controller.0.7. set to 0 The Data Protector Media Agent provides two utilities that may be used for device testing prior to configuration as a Logical Device.1 tgt CLAIMED DEVICE tape 1 8/4.0 HP C7200-8000 0xnntd00 SCSI ext_bus 2 .4 56/52. 4 bits LU 8 bit device options. . The utilities are located in the /opt/omni/lbin directory as devbra and uma.0.7.SE SCSI ID=7 target 4 spt 0 C5177-7000 0xnntd00 c#t#d# (c13t11d0) INTERFACE DEVICE DEVICE 56/52 56/52.0.11.0.11 schgr CLAIMED autoch 1 1/2/0/0.255.com U1610S B.00 5-47 2003 Hewlett-Packard Development Company.255.4.1.255. 4 bits SCSI Target.8.0 target 4 8/4. they may be tested with the Data Protector Utility Media Agent (UMA) to determine operational status. invoke the utility media agent to interact with the tape library (load/unload tapes. HP-UX additionally offers the “mc” utility which operates similarly to the Data Protector “uma”. locate the device path for the tape library robotics (media changer) 3. etc. stat h. Drive. status inquiry.com . http://education.Module 5 Tape Library Configuration and Implementation Data Protector procedure for device discovery and testing: 1. Import/Export.P. execute some “UMA” commands to test library operations e. Drives. Export. inq list available commands SCSI inquiry SCSI element status (Transport.hp.00 5-48 2003 Hewlett-Packard Development Company. Storage slots) U1610S B. use integer value or element name) 5. L. scan the system for available devices /opt/omni/lbin/devbra –devices 2. Slots) g. Media transport. move <from> <to> move media from element to element (return to original position when testing is completed. Example: /usr/sbin/mc –p /dev/rac/c0t7d0 –q (SCSI inquiry) /usr/sbin/mc –p /dev/rac/c0t7d0 –r DIMS (SCSI report element status.) /opt/omni/lbin/uma –ioctl <dev> -barcode example path as reported by devbra: /opt/omni/lbin/uma –ioctl /dev/rac/c0t7d0 -barcode 4. help f. .com/support/tapetools Student Notes In addition to the utilities provided by Data Protector.Module 5 Tape Library Configuration and Implementation 5–26. L&TT version 3. L. and media problems – Check the library health • Library test tool provides – Device Analysis – Library Exercise – Firmware Management For the latest version and information.hp. tape automation. and archival products. go to www. diagnose.com U1610S B. drive. As of the printing of this manual.P. convenient program. L&TT assembles these tools into a single. and troubleshoot library. Library and Tape Tools is available for no charge from the HP web site shown above.hp. HP StorageWorks Library and Tape Tools HP StorageWorks Library and Tape Tools (L&TT) is a collection of storage hardware management and diagnostic tools for tape.00 5-49 2003 Hewlett-Packard Development Company.3 is available. SLIDE: Verify Library Robotic Control Using L&TT Verify Library Robotic Control Using L&TT L&TT test tool • Provides the ability to verify robotic operation outside of the backup application – Verify that the library is installed and connected correctly – Quickly identify. HP offers the Library and Tape Tools for tape library and drive management. http://education. Firmware Upgrades — L&TT provides a convenient way of updating product firmware. When a support ticket for a device is generated. L&TT can generate a support ticket that includes essential information for troubleshooting the problem. L&TT automatically informs you of the following updates. The installation check feature is essentially HTML documentation that helps with the most common generic installation issues while also describing how to use L&TT to verify the device installation. If updated firmware is available.P. With libraries.hp. the program notifies the user. enabling users with an Internet connection to take advantage of ongoing enhancements. each time the program is started: • • • • • − New versions of L&TT − New firmware files for connected devices − New device-specific functionality (such as new or updated tests) for connected devices U1610S B. Wherever possible. but HP recommends generating a support ticket because the resulting data is presented in a more useful format. along with key information on product configuration and status.com . users can upgrade the library and the embedded drive firmware in the same operation. Tests include device self-tests. exerciser tests for autoloaders and libraries. The software can be configured to check the Web automatically for firmware updates for connected devices.00 5-50 2003 Hewlett-Packard Development Company. The software assists the user in choosing an appropriate HBA and SCSI ID(s). or users can manually check the Web for updates if the automatic update feature is not desired.Module 5 Tape Library Configuration and Implementation Software Features L&TT offers the following features: • Installation Check — L&TT guides you through a basic installation check of your product. you can e-mail the support ticket to a support center for assistance. as well as the results of the Device Analysis test. and the updates can easily be copied to the system. ensuring that the device is detected by the system. As an alternative to phone support. the embedded drives are updated in parallel to reduce time. Device Identification — L&TT clearly identifies the storage products connected to the system. Support Ticket Generation — If you experience a problem with a storage product. The support ticket contains generic information about a device. This information streamlines the support process and enables the support staff to better serve you if a support call is made later. L. The Device Analysis test can be performed by itself. if available. Troubleshooting Tests — L&TT provides various tests to verify product functionality or to isolate product issues. and verifying key device functionality. http://education. read/write tests on drives. and specific device utilities. Automatic Notification of Web Updates—If a connection to the Internet is present and web updates are enabled in the tool preferences. L&TT performs a Device Analysis test on the device. Note. From the Test area of the GUI.Module 5 Tape Library Configuration and Implementation 5–27.P. http://education. The Windows version of L&TT uses a graphical user interface (GUI).hp. . illustrating the devices connected to the host. The host to tape buffer is used to verify physical connectivity and device availability. The level of functionality that L&TT offers for each device varies depending on features of the device. refer to the L&TT Compatibility Matrix found at http://www.com/support/lttcompatibility. SLIDE: L&TT Connectivity Verification L&TT Connectivity Verification Student Notes Supported Products and Operating Systems For a complete listing of compatible products. the device to host access may be tested.00 5-51 2003 Hewlett-Packard Development Company.com U1610S B.hp. no data is written to the tape. and Tru64 versions of the program use a command screen interface (CSI). L. Shown above is the Windows GUI. whereas the NetWare. and the degree of device integration into L&TT. HP-UX. This would be necessary to support Data Protector Disaster Recovery (OBDR) functionality.P. 2.Module 5 Tape Library Configuration and Implementation Note: the L&TT indicates whether the OBDR capable firmware is loaded onto a device.hp. the device list automatically switches to the By Product tab. Taskbar—This section contains buttons that provide quick access to the main functions of L&TT and to the online help system. the scan feature can discover those devices without requiring a reboot of the system. By Product—This option shows a list of all the products connected to the system. If any devices have been hot-swapped or powered on after the OS has booted. and the third field represents the LUN. If a problem is encountered during the scan. . The list is grouped into the following four categories: o Libraries and autoloaders o Drives o Enclosures and processors o Other devices The three number fields listed after the device represent the device address. the second field represents the SCSI ID. This view makes it easy to see which devices are connected to the same bus as the device in question.00 5-52 2003 Hewlett-Packard Development Company. this information may help in determining the cause. http://education. When the scan completes successfully. shown above the DDS drive does not currently have the OBDR firmware loaded. The Scan tab also lets you rescan the bus. in most cases. Each field in the address is separated by a period: the first field represents the HBA channel. By Connection—This option shows all products connected to the system. Application Window Layout The three sections of the L&TT main screen are: 1. L. and may help in understanding system I/O performance issues. grouped by the HBA they are connected to. Device List—This is a multi-function window that offers several options on the following tabs: Scan—This option provides either a summary status or detailed information (depending on whether Show Details or Hide Details is selected) about the bus scanning process.com U1610S B. P. The Device List also changes to display instructions on this page (if the instructions preference is enabled). then clicking the Identity button on the toolbar opens the Device Information screen. 3. http://education. If another tool function is currently active. This view can be disabled in the software preferences.com U1610S B. The content of this window depends on the device and tool function selected. .00 5-53 2003 Hewlett-Packard Development Company.Module 5 Tape Library Configuration and Implementation Instructions—This window contains brief instructions on how to use the selected screen. L. Using the Device Information Screen When you select a product from the Device List. The Device Information screen provides an overview of the selected hardware device and its current configuration and status. the Device Information screen displays information relevant to the device. Device Information screen—All the main functions of the program are displayed in this window.hp. U1610S B.00 5-54 2003 Hewlett-Packard Development Company. SLIDE: Device Analysis Test Device Analysis Test Student Notes Selecting Device Analysis in the Test Group analyzes data in the internal logs on the device and finds problems if they exist.Module 5 Tape Library Configuration and Implementation 5–28.P.hp. Advice is given on how to solve the problems. http://education.com . L. Module 5 Tape Library Configuration and Implementation 5–29. .com U1610S B. This requires a “scratch” medium to load and unload. SLIDE: Library Exercise Test Library Exercise Test When test is in progress. L. Student Notes Selecting Library Exercise in the Test Group will perform robotic exercise as well as drive load and unload exercises.P. http://education.hp. time remaining will display here.00 5-55 2003 Hewlett-Packard Development Company. Library and Tape Tools will prompt for a tape to be loaded into the mail-slot for this exercise. the MSL Web Based Training may be available on the classroom training systems or may be accessed via the HP IT Resource Center (http://itrc. students are not expected to configure the tape library nor the NSR. Later in this course the MSL libraries will be configured as Logical Devices for use with Data Protector. LAB: MSL Library Consult with your instructor about availability of the MSL simulator (GUI touch-screen) and/or remote access to a Network Storage Router and Remote Management Interface for the MSL library. L.00 5-56 2003 Hewlett-Packard Development Company.Module 5 Tape Library Configuration and Implementation 5–30.P.hp.com .com). U1610S B. Due to the nature of this course.hp. http://education. access may be provided to allow for demonstration purposes. Additionally. P. L. you will be able to do the following: • • • • • Describe the concepts of Media Management in Data Protector.Module 6 — Media Management Objectives Upon completion of this module.00 6-1 2003 Hewlett-Packard Development Company. .com U1610S B. Provide protection for backups through media management. Perform automatic and manual media operations Implement vaulting using multiple media pools. Plan tape rotations to facilitate off-site media storage. http://education.hp. Data Protector has powerful features to organize and protect your backups. Online Catalog Data Protector maintains a record of all the data that been backed up and what media was used to perform the backup. U1610S B. Library Features Logical Organization of Media Data Protector organizes your media into Media Pools. This catalog is part of the Data Protector Internal Database.P. the management of the data once it has been backed up is just as important as the act of backing up the data. a Media Pool is simply a logical collection in which media that belong together are kept.com . SLIDE: Media Management Media Management Library Features • Logical organization of media • Online catalog • Location tracking Protection Features • Media labeling • Media duplication • Media condition monitoring Student Notes Today.hp. http://education. modern backup utilities must offer more than just a mechanism for backing up computers data.Module 6 Media Management 6–1. When it is necessary to restore data. L. As the term storage management implies. the on-line catalog can be browsed to locate the file to be restored and to find the candidate backups that could be used.00 6-2 2003 Hewlett-Packard Development Company. more details are in the Database module. .hp. it would be possible to restore from the wrong media or erase a media that we want to keep. the media usually is moved physically from one location to another. Copied media is also tracked in the Media Management Database. L. Data Protector media contains header information that enables the use of the media to be tracked and controlled. Data Protector can keep track of the physical location of the media by use of predefined Vaulting Locations. Additionally. One disadvantage of this is that the data would be unavailable to the users for twice the length of time required for a single backup. the device repository is stored in the database. In this situation. This has the ability to either schedule automated media copy or execute automatic media copy after a backup job is completed. we need to be able to verify that the correct medium has been selected for the desired action.com U1610S B. This method combines the flexibility of the manual copy plus the automation associated with lights out operations. if the data were being changed in some way. the only place that the original data would reside is on the backup media. When a tape is inserted into a Logical Device. and then accessed by Data Protector. http://education. Media Duplication For extra security. This device repository feature is available for tape library as well as standalone devices. it may be necessary to have multiple copies of a particular backup. Protection Features Media Labeling When backups or restores are performed. or removed after the backup has taken place. there is a possibility that some data may change from one backup to another.Module 6 Media Management Location Tracking Once a backup has been performed. Data Protector (5.1) provides automated media operations. This has the advantage of being able to be performed while the data is back online following the original backup.P. Data Protector stores the current physical location of media. thereby not creating exact copies of the original backup. Without this capability. Data Protector provides a mechanism for copying media.00 6-3 2003 Hewlett-Packard Development Company. There are three methods of creating a second copy of a backup media. For example. The backup could be performed twice. for example to offsite storage or a fire-safe. it is desirable to have multiple copies of the backup available in case there is a fault with the original copy or it is somehow lost. This media tracking provides for quick access to known tapes. In addition to tracking external changes to the media locations. Data Protector assists with this by tracking the condition of the media.00 6-4 2003 Hewlett-Packard Development Company.com . based on three criteria: • The number of times the media has been used • The age of media • I/O errors that have occurred while accessing the media U1610S B.hp. L.P. http://education.Module 6 Media Management Media Condition Monitoring The key to performing successful backups is to use good quality media. The general rule is: "create a media pool with a purpose. The only restriction is that all the media in the same media pool must be of the same physical type.Module 6 Media Management 6–2. for example. Media Pools should be used to organize media in a logical fashion. for example. DDS or DLT. kept 6 weeks) • Local Vault (for tapes that are in the fire safe storage location) http://education." Here are some examples of possible media pool organization: • Weekly Full Backups (Uses 4 tapes weekly. L. A Media Pool is simply a logical collection in which media that belong together are organized into a single structure within the internal media management database. SLIDE: The Media Pool The Media Pool Purpose Purpose •• Logical Logical grouping grouping of of media media •• Media Media usage usage policies policies •• Device Deviceproperty property(default) (default) •• Assigned Assigned to todevice device by bybackup backup Database Backups Full Backups Daily Incremental Backups Archive Logs DB Backups Month End Backups Student Notes Logical Organization Data Protector organizes media into Media Pools.hp. kept 4 weeks) • Daily Database Backups (Uses 1 tape daily. they should contain only media that is related in some way and has the same usage policy.P.00 6-5 2003 Hewlett-Packard Development Company.com U1610S B. kept 8 weeks) • Daily Incremental Backups (Uses 1 tape daily. . and the tapes would be exported when a backup has been written to a good tape in the original media pool to replace the bad one. and managing the pool may be difficult. This approach has certain disadvantages. U1610S B. In this case.hp. while you look at the devices as a transfer mechanism between the data and the media pools. each backup. TIP A simplified way to think about media pools: View them as a destination for your backup. Media Pool Examples The use of pools depends entirely on your preferences. and another one for Windows NT systems) • Per system (every system has its own pool) • Organizational structure (all systems in department_A have a pool. or the cycle in which the media will be used. is slightly different. and more. For example. you will not have to bother with each medium individually. • Combinations of the above criteria. pools can be defined using criteria such as: • System platform (one pool for UNIX systems. and all incremental backups use another pool) • Disaster Recovery pool (must be non-appendable for some DR types) • Database pool (used exclusively for backup of the Data Protector Internal Database) • Create a “bad tape pool” for moving tapes into if they become poor in quality. The pool would be read-only. The quantity of media in the pool may be too large.Module 6 Media Management As you can see from these examples. L. All media in a pool are tracked as one set and have the same media allocation and usage policies. or business critical applications) • Backup type (all full backups use one pool. http://education. Grouping media used for a similar kind of backup into a Media Pool allows you to apply common media handling policies on a group level. while similar. either in the number of tapes required to complete the backup. It would be difficult to verify that you have sufficient media in the pool to complete all the backups that utilize it (as each backup has a different requirement).P.00 6-6 2003 Hewlett-Packard Development Company. and systems in department_B have another pool) • Systems categories (running large databases. It is also possible to have all these backups share the same single media pool.com . refer to the online man pages.P.Module 6 Media Management 6–3. . TIP For more information on these commands. the command line offers several possibilities for automation. L.00 6-7 2003 Hewlett-Packard Development Company. Data Protector provides a set of default media pools. SLIDE: Creating Media Pools Creating Media Pools Using the command line omnimm –create_pool <name> <type> <policy> <age> <overwrites> <options> … Student Notes The Data Protector administrator can create a media pool via the GUI or by using the omnimm command. http://education. Configuration via the GUI is the easier method of creating a new pool. however. one for each media type.com U1610S B.hp. L.00 6-8 2003 Hewlett-Packard Development Company.Module 6 Media Management Example: Create a new media pool using the omnimm command and verify its attributes: omnimm -create_pool New_dds DDS App+Loose 36 100 –free_pool –move_free_media Pool New_dds successfully created.P.hp. http://education.com . omnimm -show_pool New_dds -detail Pool name Pool Description Media type Policy Blocks used[MB] Blocks total [MB] Altogether media Poor media Fair media Medium age limit Maximum overwrites Magazine support Free pool support : : : : : : : : : : : : : New_dds DDS App+Loose 0 0 0 0 0 36 months 100 No Uses free pool + Move free media to free pool U1610S B. P. Data Protector simply provides a default value based upon the media type. http://education. SLIDE: Media Pool Properties Media Pool Properties 1 Works only with library devices Loose policy allows more allocation options 2 32-character name 64-character description Automatic allocation automatic de-allocation 3 Age and overwrites Student Notes The Media Pool properties may be set when a media pool is created or modified at a later time.Module 6 Media Management 6–4. spaces are allowed but not suggested (complicates scripting. The name for the pool may contain up to 32 characters. The description field (64 characters maximum) is optional.hp. To change the media type of a pool you must first delete the pool and then re-create it.com U1610S B. L. The life expectancy and number of overwrites should be set according the media manufacturer's recommendations. The media type is selected when the pool is created and is not modifiable. and may be used to convey a purpose or usage characteristics for the pool. . The Allocation Policy as well as the Usage Policies may be altered for new or existing pools. etc).00 6-9 2003 Hewlett-Packard Development Company. Properties Name and Description Media Pool names can consist of up to 32 characters. For example : WEEKLY_FULL ARCHIVE_LOGS TIP While it is acceptable to use spaces in the name. While using the command line for Data Protector. Notice that the default pools use spaces. you will need to use double quotes around any names that contain spaces.P.00 6-10 2003 Hewlett-Packard Development Company. Use a name that represents the usage of the pool. Use the underscore instead.Module 6 Media Management 6–5.hp. L. the recommendation is not to do so. These characteristics depend on the properties and policies that you have set for the Media Pool.com . a Media Pool is configured so that the media within the pool exhibit particular characteristics. SLIDE: Media Pool Characteristics Media Pool Characteristics Properties Properties •• Media Media allocation allocationpolicy policy •• Media usage policy Media usage policy •• Media Mediacondition conditionfactors factors •• Free Free Pool Pooluse use •• Magazine Magazine support support Loose Loose or or Strict Strict Appendable Appendable or or Non-appendable Non-appendable Age Age and and Overwrites Overwrites Student Notes In addition to being a logical container for your media. http://education. U1610S B. hp. Limit the description to 64 characters. but still has spare capacity is used.com U1610S B. If the media pool allocation policy is appendable. . but will not allow for easy tape rotations. Non-Appendable This specifies that Data Protector will write to a media from the beginning. via the Logical Device definition. Data Protector wants to fill up existing media before going on to use empty media. based on certain factors. The currently supported media types are: • DDS • DLT • LTO-Ultrium • SuperDLT • DTF • ExaByte • AIT • QIC • T3480/T4890/T9490 • T9840 • T3590 • T9940 • SD-3 • Tape • Optical • File Media Usage Policy Appendable This enables Data Protector to append multiple backups to the same piece of media. Data Protector will always request a media that has the most data on it but is not full (See Media Allocation Policy). Data Protector will choose the particular media to be used from the pool. the media that is the most full. Media Type This defines what type of media the pool contains.P. Data Protector will continue to request the medium until it is filled. L. When a backup is performed. it is directed to a specific media pool. When using this policy. for example Database Redo Logs. This policy will save generally be less expensive in terms of media cost.00 6-11 2003 Hewlett-Packard Development Company. This can be very useful when backing up small amounts of data throughout the day. Data Protector will request a media that has been used the least amount of times (See Media Allocation Policy).Module 6 Media Management The description field can be used to give a more detailed explanation of the usage of the pool. http://education. Ideally. Remember that a pool can contain only one type of media. The choice of which tape to use is based on the allocation number associated with the medium. Media that are marked as Poor may be the result of a failure to write due to a hardware (drive) failure. The maximum age of the media is expressed in the number of months. When the media reaches this age. rather than the same tape being used each time. Media Condition Factors Valid For # Months When media is first initialized for Data Protector usage. The allocation number is viewable from the Media Management GUI. right click on a media pool. In this way.Module 6 Media Management If the media pool is non-appendable. Tapes reaching 80% of the number of months are marked as Fair. select properties. the length of time that the media is considered “good quality” is set. Again.00 6-12 2003 Hewlett-Packard Development Company. In this case the tape quality may be verified by scanning and/or verifying the tape. Data Protector ensures even wear across all media. L. Appendable Incremental Only This is the same as appendable except that only incremental backups can be appended to existing backups. the number of overwrites can also be configured. Tapes reaching 80% of this threshold are marked as Fair.com . you could perform a full backup to a new media and append only an incremental backup to it but not another full backup. (omnimver) NOTE Maximum # of Overwrites In addition to the number of months that a media is to be considered valid. it is marked in the Media Pool as Poor and will not be used again for further backups. NOTE Both the age and overwrite thresholds may be altered via the MMFairLimit parameter in the <OMNICONFIG>/options/global file. For example. then the allocation tab. when this threshold is reached the media is marked Poor. This may make media more reliable due to less wear as a result of fewer loadings. CAUTION Media that are marked as Poor should not be reinitialized and registered as a new medium unless the poor condition was as a result of a tape drive failure. http://education. and the tape is new.P. Data Protector chooses a tape that has been used the least number of times. select the Device & Media context.hp. Eighty percent is the default for the use of fair quality marking. U1610S B. NOTE For more details on the allocation policies. If the device being used is a library. unformatted medium). see the next slide. In addition. the media pool view can be changed so that magazine’s are shown rather than individual media. . Media can be preformatted or Data Protector can initialize it on demand at backup time. Data Protector treats the magazine as one large piece of media. the order of the tapes in the magazines should not be changed. L. unloading and storage. and has no applicability to standalone devices. Data Protector can use media within small auto-changers with a standard media pool. Magazine Pools are very useful when backups consistently require multiple tapes. it must be formatted. or the media pool can be configured specifically for magazine support. it must be scanned (barcode) prior to using this feature. Allocation order is “strictly enforced.com U1610S B. In effect. When using this view. This feature is designed to work with tape libraries. (Loose is also required when you want the ability to use a new. it still accepts an alternative that is available for use. Magazine Support Certain SCSI II Library devices. When magazine support is enabled for a media pool. the following commands operate on the entire magazine: • format magazine • modify • verify • move • recycle • ungroup media http://education. The handling of these tapes as one unit eases the process of media loading. or Data Protector will not know where the uninitialized media are located.Module 6 Media Management Media Allocation Policy Loose or Strict The loose policy defines that even while Data Protector will request a particular medium. but may be more expensive if the magazine is not filled before getting removed from the device. such as small auto-changers are equipped to manage media loaded in magazines. the whole magazine is replaced. The strict policy determines that the medium Data Protector requests must be used.00 6-13 2003 Hewlett-Packard Development Company. rather. The setting of this flag tells Data Protector to initialize and use blank media that may be loaded in preference to media that is already initialized.P.hp.” The most commonly used setting is loose because it is more forgiving. Individual media is never removed from a magazine. Allocate Unformatted Media First Before Data Protector can write a backup to a tape. Therefore. http://education. into a group that is suitable for a magazine. It assumes the magazine is completely loaded and does not scan the remaining slots. suffixed with a sequential number. Whenever Data Protector scans a magazine.Module 6 Media Management • • import magazine export When a magazine is formatted.P. U1610S B.00 6-14 2003 Hewlett-Packard Development Company. it reads the label of the first tape to identify the magazine. L.com . Data Protector assigns a name to the whole group of media and gives every single media in the magazine the same name.hp. Group and Ungroup Media group media allows you to group together media that has already been formatted as normal non-magazine-use media. The ungroup media is the reverse. in that it breaks down a magazine grouping so that the media can be used separately. you should never change the order of the tapes in the magazine or remove individual media. it is common to want the ability to use any unprotected tape to perform a backup (provided that the tape belongs to the pool assigned to the needed device. SLIDE: Loose or Strict Allocation? Loose or Strict Allocation? Loose •• Even Evenmedia mediausage usage •• Auto-initialization Auto-initialization(optional) (optional) •• Allocation order not Allocation order notenforced enforced •• Works best with small Works best with smalldevices devices – – standalone standalonedrives drives – small autochangers – small autochangers •• Fewer Fewermount mountrequests requests •• Auto-allocation/de-allocation Auto-allocation/de-allocation Strict •• Even Evenmedia mediausage usage •• Manual Manualinitialization initialization •• Allocation Allocationorder orderenforced enforced •• Works best with library Works best with librarydevices devices •• More mount requests with More mount requests with small smalldevices devices •• Override Overrideduring duringbackup backup •• Auto-allocation/de-allocation Auto-allocation/de-allocation Student Notes One of the most important decisions for creating Media Pools is to choose whether you would like to use loose or strict media allocation. Blank Media Data Protector may “format on the fly”. Loose Allocation The loose allocation policy usually works best with standalone devices and small autochangers.com U1610S B. The media policy must be set to http://education. but this will not be enforced. Data Protector will try to use media that exists according to the allocation order. It will give the media a default name and put it in the media pool associated with the Logical Device used for the backup. Data Protector may auto-format the medium when the backup starts. .P. or is new).hp. The following will summarize each policy. or auto-initialize (format) when it finds blank medium in either a standalone or a library device. With these smaller devices.Module 6 Media Management 6–6.00 6-15 2003 Hewlett-Packard Development Company. The operator will be presented with mount requests for any tape "unprotected or new" if Data Protector finds an invalid tape in the drive. L. The default value at version 5.Module 6 Media Management loose to take advantage of this feature. Additionally. The default value of this parameter varies with the product version. InitOnLoosePolicy must have the appropriate value to allow for automatic initialization.1 is 0. To enable. With automatic formatting. See the note below. you will be able to modify the media label (description) in addition to producing reports on the media used for a particular backup session.00 6-16 2003 Hewlett-Packard Development Company. which is disabled. however.com . it is desirable to have an even usage of media within the library. Strict Allocation The strict allocation policy usually works best with library devices.hp. Data Protector will request a specific medium. The order of the initialization (formatting) will determine the initial allocation sequence. this is the current Allocation Order for the tape. The use of strict allocation for standalone devices will require proactive media management. the even usage would be "strictly enforced" by Data Protector. In order for Data Protector to assign an allocation number to each tape. U1610S B. a global option. Note: The auto-initialize feature may be controlled by modifying the global option InitOnLoosePolicy. To verify the media allocation order.P. If a mount request is given to the operator for a tape from a strict allocation media pool. The tape order has the potential to change with each backup as a result of tape usage. open the GUI and select a particular media pool in the “Device and Media” context. http://education. In the case of the strict policy. At that time only the requested medium will be acceptable to complete the backup. After the backup completes. set the parameter to 1. With these larger devices. to be sure that you always have the correct tape in the drive prior to backups starting. they must all be manually formatted prior to the start of a backup session. In the results area you will see “Order” as one of the column headings. you will not have initial control over the labels (called description in the GUI) for the media prior to the backup. The combination of strict and standalone devices (or small autoloaders) is not usually the best combination for a lights out operation. L. Order of use: as specified in the datalist. during backups.Module 6 Media Management 6-7. This media set is only available in exchanger devices. This media set is sorted with 'Blank' media ahead of media with an 'Unknown' header. The pool policy must be Loose to allow auto-initialization and the global file needs InitOnLoosePolicy=1.00 6-17 2003 Hewlett-Packard Development Company. b. . Data Protector Media Allocation Order The sequence of media allocation is in the order of the following Data Protector media sets: • • • • • Pre-allocated Media Appendable Media Uninitialized Media Free Media Overflow Media Each of these media sets has its own definition and rules about the sequence of media. 'Unknown' media is only used when there is no 'Blank' media. This media set is not sorted. The pool policy can be Strict or Loose. Order of use: when one or more media have protected objects. the most recently written media is reused first. provided that this won't break any other rules such as those relating to protection and appendable media. but the media is not full. This media set is sorted according to the time of the last write. http://education. The most recently written medium is listed first. Pre-allocated media in 'Poor' condition will not be used.hp. The pool must be 'appendable'. Data Protector Administrators are confused when receiving when mount requests are issued during backup when plenty of media is apparently available. or if it is confusing as to the order in which Data Protector is using tapes in the tape library or media pools. Uninitialized Media Uninitialized Media is media without a recognizable header. Text Page: Media Allocation and Usage In many cases. These are explained below: Preallocated Media Media named in the datalist device options pre-allocation list. the following information should be helpful. Data Protector assumes that it can be auto-initialized as required. If receiving unexpected mount requests.com U1610S B. Order of use: a. Appendable Media Media in 'Good' condition.P. with some currently protected data objects. L. 'Blank' media is used first. any unprotected medium can be used. If the data is not protected. • Media in 'Poor' condition. If the policy is Loose. Strict policy means that Data Protector will not use any other medium than the one its own rules indicate should be used. Protected and Unprotected Data The order that media are selected for use depends in part on whether or not the data on the media is protected. • Media in 'Fair' condition which is protected. if the data is protected. In general. The least recently written medium is listed first.com . A preallocation list can be used by both the Loose or Strict policy. Other Factors Relating to Media Usage Strict Policy The Strict allocation policy is not directly related to the use of a preallocation list. As a result. The difference is in Data Protector's response when the medium in the device is not the one dictated by the allocation rules. The order of media use is generally the same for Loose and Strict policy. The medium with the least number of overwrites is listed first. it will not be used for appending.P. This media will only be used if no 'Good' condition media are available. Order of use: • least recently medium is used first. This media set is sorted according to the time of the last write. http://education. L.Module 6 Media Management Free Media Free Media is that which is in 'Good' condition with no currently protected objects contained on it. This media set is sorted according to the total number of overwrites.00 6-18 2003 Hewlett-Packard Development Company. a medium will be used for appending more data. U1610S B. • Media which is recognized by Data Protector as having a header for another backup utility such as 'tar' or 'fbackup'. if found in the device. Unclassified Media Media in the following categories are not classified into any of the sets by Data Protector.hp. Order of use: • least recently medium is used first. they are not allocated for use by Data Protector. Overflow Media Overflow Media is that which is in 'Fair' condition with no currently protected objects. and will not be overwritten until no other medium is available. now with NO protection on the data. five newly initialized media are loaded into an autoloader. which is now the least recently used medium. if the first data object is unprotected. The sixth unprotected backup will overwrite the first medium.' Data Protector will now append protected and unprotected data to the tape.' While any backup object on a medium is still protected. Then several more backups are made. The subsequent backups are all unprotected and they will be appended to the second medium. until all five media are used. If several backups are made. Each subsequent unprotected backup will be written to a new medium. Once a medium.P.com U1610S B. The second backup in this sequence is protected and it is written to the second medium. even if the pool configuration is 'Appendable. As the default protection is 'Permanent' this can be what is preventing the medium being used. in an appendable pool. has a protected object on it. five newly initialized media are loaded into an autoloader. the media are not considered appendable. However. The unprotected backups will also be appended to the first medium and they will not overwrite each other. the behavior changes. . Example 2: Again. with protection on the data.' Example 3: Again. If a backup is made with no protection. it will be written to the first medium. A backup is made with no protection. Check the medium in question with this command: omnimm -list_media <medium label> -detail | grep Protection http://education.hp.Module 6 Media Management Example 1: A pool is configured as 'Appendable' and 'Loose'. and will be written to the first medium. Sometimes a medium that is expected to have no active protection is rejected for use by OBII. It may be that one object on the medium is actually still protected. the whole medium is prevented from being reused. A second unprotected backup will be written to the second medium. L. The presence of a protected object on the second medium makes it 'appendable. they will all be appended to the first media. Because the data on each medium is unprotected.00 6-19 2003 Hewlett-Packard Development Company. Five newly initialized media are loaded into an autoloader. A typical scenario is that an ad hoc backup was added to a medium outside the normal schedules. it is considered 'appendable. Once it is at the end. This will be true even if some space remains on the other media in an exchanger. Data Protector will recheck the cleaning bit. So. It refers to the medium that is used as the first in a sequence of media. When medium #1 is unloaded. If you load an 'expired' cleaning tape. with just enough for '25 times 30 seconds' of cleaning. in the current backup session. assuming that there is enough data to fill it. for each 30 seconds of cleaning and it NEVER rewinds! It just moves along until it gets to the end and then it stops. L. when it is the 'least recently used'. the tape is active for less than 20 seconds. If medium #1 is really faulty. The cleaning tape moves forward. It is possible that medium #1 is in bad shape and could be the cause of the cleaning request. When 30 seconds of cleaning has completed successfully. the medium is not immediately unloaded. U1610S B. Then it will be marked 'Poor' and not used again. The status of the cleaning request is checked only when a medium is being loaded or changed. DDS cleaning tapes are a fixed length. Different parts of backup cannot be appended to the ends of several different media. part way through a backup session. over one section of tape. If the first session medium becomes full. this will show up next time it is used. The medium will be used again. only the medium that is used as first in the session can be appended. If the pool policy is appendable. the cleaning tape will be loaded and used. if the drive sets the cleaning bit. it is an 'expired' cleaning tape. If it is still set. Data Protector will terminate the session and will report that the cleaning tape was requested twice for the device. Cleaning Tape Usage The cleaning status is NOT checked while a medium is in the drive and being written to. http://education. the cleaning request will be checked. After that. it does not actually do any cleaning and the cleaning bit is NOT reset.P. Data Protector can initiate a cleaning operation when the drive sets the cleaning bit. when the write operations fail.com . if the backup session requires more than one medium. Subsequent media for that session must begin at the start of a medium so they need to be empty or unprotected.00 6-20 2003 Hewlett-Packard Development Company.hp.Module 6 Media Management First Session Medium The expression 'first session medium' is found in the Data Protector documentation. It will be used until it is full. medium #2 will be loaded to continue the backup. a mount prompt will occur. and there are no empty or unprotected media available. After the cleaning is done. However. Data Protector assumes the medium is still 'Good' and does not mark medium #1 as 'Poor'. the clean bit on the drive is reset. Statistical Information The correct settings for the 'Full' flag and for 'Data Protection' are the only tape details necessary for Data Protector operation. It assumes that the slots it controls are assigned exclusively to Data Protector and performs media allocation based on the media allocation rules. http://education. and then update the Media Management (MM) database. The rules do not relate to the order of media in the slots. Once the tape has been filled with data.hp. The media allocation rules are the same for small exchangers and large tape libraries.P. The Total & Used sizes are statistical information only. the size will be reset in the MM database. L. Data Protector will write to the end of tape. . Data Protector writes to the tape until the device reports early end of tape (EOT) warning. If a tape is formatted to a smaller size than the physical size of the tape. The same thing applies to tapes that are initialized to a very large size.00 6-21 2003 Hewlett-Packard Development Company. The recorded tape size will be reset to the value of the physical tape size.com U1610S B. so Data Protector does not necessarily start with the lowest slot number and progress towards higher slot numbers.Module 6 Media Management Initialized Size The size that a tape media is initialized to will not ultimately affect the amount of data that can be written to it. Tape Library Slots Data Protector does not care about the order of slots inside a random access tape library. LTO. Allocation and De-allocation When additional tapes are needed for backup. etc.hp. This tape movement is called allocation.” If you turn U1610S B. http://education. When the protection of the data on a tape expires. To implement the Free Pool for an individual media type. SLIDE: Free Pool Concept Free Pool Concept DDS Pool-1 Protected Protected Protected Expired Free-DDS Pool Expired Allocate De-allocate Expired Expired DDS Pool-2 Protected Protected Expired Allocate De-allocate Expired Student Notes Data Protector supports the use of a Free Pool of unprotected media.com . This feature is controlled by a second media pool property in the GUI called “Move free media to free pool.00 6-22 2003 Hewlett-Packard Development Company. so one for DDS. Data Protector will automatically de-allocate the tape and move it into the free pool. create a new media pool or modify the properties of an existing pool and select the “Use free pool” feature on the Allocation properties tab of the GUI. Data Protector will move them from the free pool into the media pool associated with the backup. These “free” tapes may be newly formatted or have expired backups on them. Data Protector will automatically create an additional pool called “Free <Media_type>”. See the next page for more details. Each media type supported by Data Protector may have an associated Free Pool. L.” There will be only one free pool for each media type and it may be shared with all of the other pools of the same media type.Module 6 Media Management 6–8.P. such as “Free DDS. DLT. a frequency of 3 causes de-allocation at 00:00. The media pool allocation and usage policies will be established by properties of the regular media pools. and then the day is divided according to the frequency that you specify. You have the option of forcing a manual de-allocation at any time by using the command: omnidbutil –free_pool_update NOTE The omnidbutil command is available only on the Cell Manager as it is not part of the command line part of the Cell Console. The frequency of the deallocation is controlled by the “FreePoolDeallocFreq” parameter in the global file. The parameter “FreePoolDeallocFreq” is set to one by default. . The default frequency is once per day at 00:00 (midnight).Module 6 Media Management off de-allocation (by de-selecting the “Move free media to free pool) you may still move media manually to the free pool as long as the media is not protected. On the Unix Cell Manager the command is in the OMNIHOME/sbin directory. Media Pool Properties The media pool that uses allocation (uses the free pool) will have condition factors that are inherited from the free pool. Tapes that exist in the free pools are not used for backup until allocated and moved to a regular media pool.com U1610S B. but may be set as high as 96 to produce a 15-minute de-allocation frequency.hp.P. De-allocation Times The de-allocation process occurs periodically during the day. 08:00 and 16:00. The first de-allocation occurs at 00:00. L. on the Windows Cell Manager the command is in the OMNIHOME/bin directory. This implies that all pools that share a set of tapes will use the same condition factors of age and overwrites.00 6-23 2003 Hewlett-Packard Development Company. As an example. as free pools do not have such policies available. http://education. SLIDE: Media Life Media Life Media Pool properties establish expected media life Related commands: omnimm -list_media .P.hp.com .. L. or a recycle has been performed to remove the protection. Medium properties track age and usage Student Notes Once the media is formatted.Module 6 Media Management 6–9. it should not be formatted again.. Description Display a list of media pools Display the contents of a pool Display summary info for a medium Display detail info for a medium Display summary id info for a medium Display detail time info for a medium Command Examples for Media Information omnimm omnimm omnimm omnimm omnimm omnimm -show_pools -list_pool "Default File" -list_media "Default File_9" -list_media "Default File_9" -detail -media_info "Default File_9" -media_info "Default File_9" -detail U1610S B.. omnimm -media_info . http://education..00 6-24 2003 Hewlett-Packard Development Company. use the recycle feature. NOTE Media can only be exported if the protection of the sessions has expired... If the session information is not required (and it is still protected). Formatting a medium more than once resets the quality information stored within the media management database. Data Protector keeps usage and quality information regarding the tape in its database. omnimm -catalog . This is useful for removing the Default pools that are not needed.Module 6 Media Management 6–10. and register it in the media management database Read the header and detail catalog information from a tape. The tape may be from a different cell or may have been exported from the current cell. Prepare it for Data Protector use by writing a header to the tape. Delete media in pool first. SLIDE: Media Operations Media Operations Medium Operations Pool Operations Student Notes Data Protector provides the following Media Management operations for pools: Format Import Delete Select Media Initialize a medium. .hp. Useful when a pool contains a large number of media. Removes an empty media pool. Search a Media Pool for specific media.com U1610S B.00 6-25 2003 Hewlett-Packard Development Company.P. http://education. L. P. The detail catalog is automatically purged from the database when it expires. Change the pool that a particular tape(s) is assigned to. Replicate a tape. The contents of the tape are unaffected. The tape does not need to in a device for this operation. Two devices of the same type and a blank tape are required. The data may also be verified if the tape contains crc blocks.com .00 6-26 2003 Hewlett-Packard Development Company. The tape does not need to be in a device for this operation.hp. http://education. Recover the detail catalogs from a tape that is still in the database but has had its detail catalog expire. L. U1610S B. Alter the vaulting location string associated with a tape. Read the tape header and verify that it is written in Data Protector format. This uses the omnimcopy functionality for duplicating a single tape. Remove all of the protection from the data that is backed up on the selected tape.Module 6 Media Management Media Operations Data Protector provides the following Media Management operations for media within pools: Export Change Location Recycle Move Copy Verify Import Catalog Delete an unprotected medium from the media management database. The tape does not need to be in a device for this operation. Media can be formatted from within the GUI in the Devices and Media context. The media format process is performed within the media pool where the formatted medium is to be added. SLIDE: Formatting Media Formatting Media Before Media can be used. it must be formatted. A unique ID is generated when the media is initialized. the header information is read to ensure that the correct medium is being used. . it must undergo an initialization process called Formatting. The Data Protector GUI now presents the format. where initialize was previously used. or from the command line using the omniminit command.Module 6 Media Management 6–11. Parameters: User label/auto label Location Logical device Media capacity/determine Force Note: Blank media may auto-format on backup when loose allocation is used IMPORTANT: Format each tape only one time omniminit [-options] Student Notes Before any media can be used with Data Protector. It is also possible to manually read media header information by using the Scan operation of a Logical Device or with the “omnimlist – device <logical device> -header” command. Data Protector uses this header to identify one media from another. http://education.com U1610S B. This ID is written to the media header and to the Media Management Database (MMDB).. L. Each time a medium is accessed.P.hp.00 6-27 2003 Hewlett-Packard Development Company. option. The Data Protector media management system requires a unique medium ID for each tape. • Location (optional) The physical location of the medium may be manually entered or selected from a list of pre-configured vaulting locations from the <OMNICONFIG>vault_locations file. With the specification of a user-defined. The location can consist of up to 32 characters.” the label can consist of up to 32 characters. therefore. then the first tape to be auto-labeled in this pool will be called Datalogs_1. an ANSI X3. Data Protector generates a description (label) based upon the name of the media pool that the media is being added to plus the current sequence number. the Data Protector default is 100 MB.hp. http://education.P. It reflects the largest amount of data that has ever been written to the tape. U1610S B. The format of an Auto-labeled medium is POOLNAME_INCREMENT#. This may be altered by modifying the global option: FileMediumCapacity.com . if the pool is called Datalogs. Within the GUI. Data Protector does not take into account any compression factors when determining this capacity. Each time Data Protector writes to a newly formatted media. such as “Oracle 0001. friendly label. It is suggested that the administrator preconfigure the possible locations before formatting media to create consistency. Specify allows the user to input a specific capacity in megabytes that the medium is expected to hold. L. When “Automatically Generate” is chosen.Module 6 Media Management Media Formatting Parameters • Medium Description (Label) Choices for Medium Description are Specify or Automatically Generate. the media capacity figure is updated. • Medium Capacity (Determine or Specify) Determine instructs Data Protector to detect the type of media being formatted and select the appropriate medium capacity. the specified size will limit the size of the file medium. NOTE When using media type File.27 label is also written to the tape.00 6-28 2003 Hewlett-Packard Development Company. the “Automatically Generate” option adds an additional description for the barcode labeled media. • Logical Device The logical device used to perform the media initialization. The capacity is used only for statistical purposes and does not set a hard limit on the amount of data that any media can hold. only logical devices that match the media type of the media pool are displayed as available during media formatting. For identification on other systems. For library devices with barcode capabilities. “Specify” the description to create the label for the medium. For example. For standalone devices. this figure will be the default minimum capacity for this type of media. com U1610S B.P. the force option must be specified.Module 6 Media Management • Force During initialization. L.hp. then. by default. even if the force option is selected. If the format is recognized but initialization is still required.00 6-29 2003 Hewlett-Packard Development Company. Data Protector does not initialize the media. In order to re-format a tape it must first be recycled (this is not generally recommended) http://education. . Data Protector recognizes the following media formats: − tar − cpio − fbackup − HP OmniStorage − Data Protector (Omniback) − HP-UX filesystem − ANSI labeled tapes (some third party backup products ) NOTE Data Protector will not format tapes that are under protection within the current cell. If the format is recognized. The reason is that this media may contain valuable data. Data Protector checks the media to see if it already contains data that is in a recognizable format. Copies recorded in MMDB. After the copy. The logical devices may be located anywhere in the Data Protector cell. if the data were being changed in some way or removed after the backup has taken place. media can be copied. If the original media is overwritten or is exported from the MMDB.com . If an individual medium is lost or damaged the ability to recover data will be lost. the first copy becomes an original. all tapes that contain the requested data are listed. it may be necessary to have two copies of a particular backup. L. the only place that the original data resides is on the backup media. The source and destination devices are logical devices.hp.00 6-30 2003 Hewlett-Packard Development Company. U1610S B. If a mount request is issued during a restore session. The manual. • Copies are protected • Copy and original are marked non-appendable • Copy becomes original if original is exported (deleted) • Copy process may be scheduled • Copy process may be automated with backup omnimcopy –options omniamo -options Student Notes For extra security. single copy operation can be initiated through the GUI or the command line interface with the omnimcopy command. but must be of the same media class.Module 6 Media Management 6–12. http://education. SLIDE: Media Duplication Media Duplication For additional data security. both media are tracked in the media management database so that the original media and its copies can be easily identified. In addition. For example.P. this includes both originals and copies. it may be desirable or required to retain media copies both on-site as well as off-site. the target media is initialized before all data from the source media is copied. During the copy. This can pose a significant challenge when attempting to make an exact copy from a tape that is slightly larger than the destination tape. for performance reasons this is not the preferred method. This avoids unnecessary network traffic. even if they vary slightly in capacity.00 6-31 2003 Hewlett-Packard Development Company. Although it is possible to perform the copy operation from system to system. Always use logical devices that are connected to the same system. Tape Variation There are slight variations in the overall capacity of individual tapes. L. There is a local parameter that may be specified per device called OB2BLKPADDING. . Planning for this eventual issue must be done before media is initialized.Module 6 Media Management NOTE: When the copy process is completed.P. This additional padding should allow tapes of the same type to be duplicated.com U1610S B.hp. both the original and the copy are marked as non-appendable. See the <OMNIHOME>omnirc. This parameter is placed in the omnirc file on each system with connected devices and indicates the number of blocks to add after the tape header.tmpl located on the cell manager for more information. The copy may also be permanently protected. A copy of a copy is not permitted. http://education. There are two types of AMO: • • post-backup: enables automatic media copy at the end of a backup session.00 6-32 2003 Hewlett-Packard Development Company.hp. L.1 that facilitates automated copying of media containing backups. Appropriate device and media pairs must be available during scheduled-copying. which can copy media used in that particular session scheduled: schedules an automatic copy of media used for backups at a specified point in time. the copy session aborts if either the device or medium is not available (such as locked in backup mode).P. U1610S B.com . SLIDE: Automated Media Operations Automated Media Operations* (AMO) AMO types: • Post-backup – – Enables automatic media copy at the end of a backup session Copy all media used in that particular session Pre-determined start time Automatic copy of media used in time window • Scheduled-backup – – *Automated Media Operations – Media Copy abbreviated as AMO Student Notes Automated Media Operations (AMO) is a new feature in Data Protector 5. Media used in various backup specifications can be copied in the scope of a single scheduled AMO session. http://education.Module 6 Media Management 6–13. The source media is generated based on the parameters specified in the AMO specification.P. http://education. each medium will be copied N times source drives destination drives eject = none/copy/original/both new location for target media for vaulting purposes target media protection: default = same as original. as opposed to being mere utility tools such as omnimcopy. The source medium defines the destination pool of the target medium. if they are available. Once this device pair is established. Since the devices that are not available at the beginning cannot be utilized for the session. Incase a mount request pops up. The AMO functionality provides for its own load balancing. An AMO specification triggers the generation of a list of media to be copied.Module 6 Media Management Parameters for AMO (post-backup and scheduled): • • • • • • • operation type: Media Copy is the only possible value. the media pair aborts.00 6-33 2003 Hewlett-Packard Development Company. The data protection for the copy defaults to the original’s protection.hp. These sessions will be tracked in the database and therefore can be monitored and reviewed later. . none. An available ‘pair of devices’ of a certain device type is a minimum prerequisite for successful completion of any automated copy session. It optimizes the usage of the available devices by utilizing as many devices as possible and even selecting local devices. All media management operations. to which the data will be copied. while the session continues to reach its logical end. device locking after the beginning of the session is not possible. Device locking takes place at the outset of an AMO session. like a backup or restore session. Automated Media Copy does not handle mount or cleanme requests. Each source medium is mapped to a target medium.com U1610S B. because currently automated Media Copy is the only member of Automated Media Operations suite. in the realm of AMO classify themselves as sessions. number of copies: N = 1 to 10. permanent. Each source medium is mapped to a pair of devices from among the devices that were specified in the AMO specification. where default is 1. This effectively means that the copied media will belong to the same pool as the original media. a copy session will copy the data from the source to the target medium. days & weeks Creation of an Automated Media Operation specification is a precursor to copying media automatically. However. L. called source media. you can alter the protection period either during the creation or modification of the AMC specification. hp. There may be only one AMO configuration per backup specification.com . L. A post-backup Automated Media Copy specification is configured in the following way: 1.Module 6 Media Management 6–14. right-click Automated Operations and click Add Post-Backup Media Operation to start the configuration wizard.00 6-34 2003 Hewlett-Packard Development Company. 3. SLIDE: Configuring a Post-Backup AMO Configuring a Post-Backup AMO • Select the backup specification • Select source and target devices • Select post backup options Student Notes Post-backup AMO is automatically initiated after a backup session finishes. and thereby supplies information about session. AMO initiates the copy process and copies all media used in that particular backup session. select the desired backup specification. The BSM reports the end of a backup session. After a backup finishes.P. In the Scoping pane. and results in the copying of the media used in that particular session. datalist. http://education. Select the Devices & Media context in the GUI 2. sessionID. On a successful match. Session records for AMO post-backup sessions are stored in the IDB and are also able to be monitored. omnitrig matches the backup (backup specification name) to a corresponding post-backup AMO configuration file. success etc to omnitrig utility. U1610S B. In the Backup Specification drop-down list. 5. http://education. acting as both the source and destination for copying is not allowed. 6. whether either of the media will be ejected automatically after copy session the new location for the target media (if eject is selected) the protection of the target media. Select “Original” and a pop-up window displays the following information about the source medium: • • • Media Pool location of the original medium ID and medium label Additionally. there appears a button in the upper right corner in the GUI called “Original.P. Specify: • • • • the number of copies to be made. when displaying the properties of the original medium. Map the source drive(s) to their corresponding destination(s) to produce a so-called ‘copy-pair’. . Select Finish to exit the wizard. a new tab labeled “Copies” is available to show a list of all valid copies of the medium as well as a summary of their properties.00 6-35 2003 Hewlett-Packard Development Company.Module 6 Media Management 4.hp. L. While displaying the properties of the copied media.. Selecting identical drive/s.com U1610S B.”. Media Properties Tracking of the duplicated media is done within the MMDB. U1610S B. Once the sessions are known. The AMO session consists of the following processes: MSM the media session manager CMA the copy media agent (loads/reads from source media) BMA the backup media agent (loads/writes to destination media) The media will be copied simultaneously.hp. L. AMO copies all of the media that belong to the backup sessions using a single AMO session. Otherwise. within a user-defined timeframe. SLIDE: Configuring Scheduled Media Copy (AMO) Configuring Scheduled Media Copy (AMO) Select to change month Select to change year • • • • poor fair good any condition Choose timeframe Specify options Student Notes The scheduled Automated Media Operation (Media Copy) is the process of duplicating media used in one or more backup sessions at a scheduled time. they will be copied sequentially.P. Scheduled Media Copy seeks backup sessions that started and have completed. http://education.com .00 6-36 2003 Hewlett-Packard Development Company. Load balancing in AMO strives to simultaneously use the maximum number of media during the copy process. if enough devices are available.Module 6 Media Management 6–15. http://education. and attempts to copy them. omnitrig will check for scheduled AMO sessions and triggers omniamo and provides to it the parameters from the saved AMO configuration file(s). Started Within establishes the beginning of the timeframe. This option would probably be used for one-time vaulting purposes. L. Under the auspices of AMO. AMO will not be able to copy media that are related to that particular backup specification because they are still locked by the BSM. Now AMO seeks all media associated with backup sessions that started between 2200 the night before and 0600 the next morning. In such situations. The AMO session displays the following error message: Source medium <medium ID> could not be locked and will not be copied in this session. irrespective of when they were performed. This defines a so-called window of opportunity. It is expected that this option would be used rarely. starting some number of hours before the actual AMO start time. they are Relative. Relative The relative time option apportions a timeframe based on the two input values. Schedule Media Copy offers three timeframe choices when defining the schedule. specifying relative time option.P. or to vault media from a certain time to another! No Time Limit This option selected will include all backup sessions. namely Started Within (hours) and Duration (hours). and No Time Limit. an AMO is scheduled at 1200. Absolute You set the scope in terms of absolute days to search for backup sessions. A conflict can be anticipated in case one or more backup sessions that were started within the AMO time frame were still running beyond this time frame.Module 6 Media Management The omnitrig module polls every fifteen minutes to see if there are any scheduled tasks (including backups or reports) to be processed. The different times used in this hypothetical case conform to a typical business enterprises backup and copy time window. while Duration sets the actual duration of the time frame. and simultaneously AMO was attempting to copy the media that this particular backup specification would produce.hp. Absolute. For example.com U1610S B. we may choose Started Within = 14 hours and Duration = 8 hours. .00 6-37 2003 Hewlett-Packard Development Company. The drops down arrows serve to open a calendar. com . and may include or be the same as the name of a backup specification. In the Scoping pane. type a user-defined name. fair. http://education. Select the Devices & Media context in the GUI 2. L. this is due to the selection in the Source list. 5. Select the source drive(s) and map them to their corresponding destination(s) to produce a ‘device pair’. In the Media Operation Type drop-down list. Specify the time frame within which you want to search for completed backup sessions. right-click Automated Operations and select “Add Scheduled Media Operation” to start the configuration wizard. Click Next. 4. This user-defined name acts as a prefix for that particular configuration file name.P. namely Relative. relative. Select the backup specification(s) of the backups you want to copy. or no time limit source media condition = poor. 3. select Media Copy. lib2_drive1 is disallowed from the Destination list. On closer observation of the figure above.Module 6 Media Management Parameters only available in scheduled AMO: • • • • AMO specification as multi-valued parameter time frame = absolute. good.00 6-38 2003 Hewlett-Packard Development Company. Specify the media conditions and protection of the source. 8. U1610S B. 7. & any source media protection = any. In the Media Operation Name field. Click Next. (the only choice in DP51) and click Next to select the devices for the copy process.hp. 6. for scheduling to take place. unprotected & protected Creating a Scheduled Media Copy To define a new Schedule Media Copy (AMO) proceed as follows: 1. Click Next. Absolute. and No time limits. notice that in Library 2. There are three timeframe choices. Module 6 Media Management Media Condition: • • • • Any: media in any condition is accepted Good: only media in good condition is accepted Fair: only media in fair condition is accepted Poor: even poor media are accepted Media Protection: • • • Any: media with any kind of protection is considered Unprotected: only unprotected media will be considered Protected: only protected media will be considered for copying.00 6-39 2003 Hewlett-Packard Development Company. Specify the various options accordingly. . Click Finish to exit the wizard. 9. Click Next. Right click on a date and select Schedule from the pop-up to open the Schedule Media Operation dialog box (shown below).P. specify the time in days. L.com U1610S B. Click Next. Specify the number of copies to be made. eject mode stipulating whether either of the media will be ejected after copying. 10. Select Use Starting to delay the first performance of the copy operation and specify the starting date.hp. http://education. and click OK. location for the target media (if ejected) and protection for target media. as to how long the media that is being considered are to be protected. 3. all media belonging to backup sessions started within the AMO time frame AMO copies Student Notes The sequence on the slide demonstrates the sequence of events for a scheduled media copy. BMA) to create the tape copies.com . L. The session ends. They are as follows: 1.P. AMO copies everyday at 12 noon. U1610S B.(optional) 5. The MSM starts the necessary agents (CMA.Module 6 Media Management 6–16. 4. http://education.00 6-40 2003 Hewlett-Packard Development Company. SLIDE: Scheduled Media Copy Example Scheduled Media Copy Example backup specs monday tuesday AMO time frame started within 14h duration 8h wednesday week day AMO spec. Omnitrig reads the AMO schedule file and starts the session manager (MSM). The MSM selects media from the database that match the selection criteria (timeframe). The MSM ejects the tapes as configured.hp. AMO session 24:00 2200 0600 1200 24:00 24:00 AMO relative time AMO copies all pertinent media Scheduled. 2. omniamo can also be used to re-start a failed AMO session. Configuration Directories AMOs configuration files are stored in two directories namely amo and amoschedules.amcs to the AMO specification name In case of post-backup AMO. The session id may be exported as follows: On Windows: set SESSIONID=SessionID On UNIX: export SESSIONID=SessionID NOTE: If the session ID is unknown. the media of which you want to make a copy of.1 introduces a new CLI utility called omniamo.P.Module 6 Media Management 6–17. In case of scheduled-backup AMC.amc or . it currently accepts media copy parameters.amc and ScheduleTape. L. The directories will contain AMO associated configuration files and schedule files respectively. Furthermore. omniamo can be used to immediately start an automatic media copy operation.00 6-41 2003 Hewlett-Packard Development Company. TEXT Page: The omniamo Command and Configuration Files Student Notes Data Protector 5. leave out the appending suffix . The locations of these directories are as follows: Windows Configuration: Schedules: UNIX Configuration: Schedules: <OMNIHOME>\Config\amo <OMNIHOME>\Config\amoschedules /etc/opt/omni/amo /etc/opt/omni/amoschedules http://education.com U1610S B.hp. . The syntax is as follows: omniamo –help | help omniamo –amc ConfigurationName <-post_backup | -scheduled> For example: omniamo –amc FullBackup omniamo –amc ScheduleTape where FullBackup. omniamo requires the session ID of the backup session. omniamo will initiate Automatic Media Operations (AMO). use the omnidb –session command to list all previous session stored in the internal database.amcs are names of typical post and scheduled-backup media copy configuration files. it allows a user-defined name as prefix for scheduled AMCs. see below the different contents of the same AMO configuration file ScheduleTape. It is expected that Object Copy (in addition to Media Copy) shall enable such functionality in future Data Protector versions. it requires that the post-backup AMO prefix is the same as the backup specification name. amcs. http://education. While. however the suffix defines whether the AMO operation is post or scheduled.. Media Copy marks both source as well as target media as non appendable. namely a prefix and a suffix. amoschedules contains only scheduled AMO configuration files corresponding to scheduled AMO specifications. Regarding the prefix part of the configuration files.hp.amcs. • U1610S B. For example. Post-backup AMC configuration files suffix in .com . L. On the other hand. Data Protector clearly distinguishes the manner in which the configuration files of the two forms of AMC are labeled.P. in amo and amoschedules directories: Configuration File: NAME " ScheduleTape" SRC_DRIVES "drive2" DEST_DRIVES "drive1" EJECT_DEST DEST_LOCATION "" DEST_PROTECTION -1 TIMEFRAME 14 8 SRC_PROTECTION 0 SRC_CONDITION 2 DATALISTS "test1" Schedule File: -start -starting 1 4 2003 -every -day Sat -month Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar -at 15:45 The name of a typical AMO configuration file can be broken down into its two constituent parts. The prefix may not necessarily be suggestive of the backup specification name.00 6-42 2003 Hewlett-Packard Development Company. whereas its corresponding file in amo stores only AMO specification information. Limitations • Only entire media can be copied as opposed to copying selected objects or sessions contained within the media. while scheduled AMO suffix in.amc. A typical CONFIG file in amoschedules stores detailed AMO schedule information.Module 6 Media Management The directory amo contains both the post-backup as well as the scheduled AMO configuration files. (started within and duration options can only be specified in hours) Source media defines destination pools for target media.Module 6 Media Management • • • • During media copy. but DLT4000 cannot use DLT7000 media). DLT7000 can use DLT4000 media. it forbids forward compatibility. • • • • • http://education.) as homogeneous. i. It is not possible to create copies of media concurrently while the backup is in progress. L. If. however. . the device pair is aborted. The AMO session will fail prematurely if the minimum number of devices necessary for the session cannot be secured at the beginning of the session.g. only libraries are! Data Protector treats the various sub-types of the same device type (e.com U1610S B. Device locking in AMO takes place at the outset of a session. but not vice-versa Therefore. indeed a mount request is received either from BMA or CMA.hp.. the media being copied will be unavailable for restore.g.00 6-43 2003 Hewlett-Packard Development Company. DLT or LTO etc. while allowing backward compatibility within one device type (e. AMC is not supported on standalone devices.e.P. The time frame options under scheduled AMO can only be specified in hours. Mount request handling is not implemented. It is imperative for AMO to lock at least the pair of devices (corresponding to source and target media for each media type) to complete the session successfully. for the purpose of copying. it is possible to copy a DLT4000 to a DLT7000 media. while the session continues to its end. NDMP media cannot be copied. you are advised to choose appropriate source and destination devices. L.com .Each with a specific purpose • Media Duplication (scheduled.00 6-44 2003 Hewlett-Packard Development Company.Pre-configured locations U1610S B. http://education. automatic.inherited from Backup Operations • Media Pools with Strict Allocation .Module 6 Media Management 6–18.Individual Media Feature • Media Labeling . Tapes are typically packed up and sent to an off-site safe storage facility.P. or manual) • Vaulting Locations .hp. Tape rotations typically involve moving the tapes off site. Data Protector supports the following features to facilitate tape rotations and vaulting: • Media Protection .Media Pool Feature • Multiple media pools of the same type • Media Location tracking . and then back onsite after some defined period of time. SLIDE: Media Vaulting Operations Media Vaulting Operations Vaulting: • Offsite protection • Stored in safe facility Student Notes The process of “vaulting" media is essentially a form of protection.Individual Media Feature • Multiple Media Pools . 00 6-45 2003 Hewlett-Packard Development Company. as this will be displayed whenever a tape is requested by a running session (backup or restore). You may also change the media label at the same time. The label and location are stored in the Data Protector database along with the Medium-ID that Data Protector generated for the tape when it was initialized. L. The vaulting locations are used as media location strings. NOTE The tape does not have to be in a tape drive to be modified. SLIDE: Vaulting Locations Vaulting Locations Device and media context allocation order List of media vault locations [barcode label] description label if no barcode [Physical location] Library slot Vault location <config>/vault_locations Student Notes The vaulting locations may be pre-configured into Data Protector using the Device and Media Management GUI.hp.com U1610S B. You may edit this file using an editor instead of using the GUI. You may change the media location from within the Media Manager. assigned to individual tapes.P.Module 6 Media Management 6–19. and stored in the Data Protector Media Management Database. . simply select a medium and then Edit -> Modify…. Vaulting locations are stored in the OMNICONFIG directory as an ASCII file named vault_locations. http://education. When media are moving from one physical location to another it is a good idea to update the Data Protector Database with the correct physical location of the media. Module 6 Media Management 6–20. prior to moving to the active pool. May be used as a holding area for expired media. SLIDE: Vaulting with Media Pools Vaulting with Media Pools Label may be modified Medium selected Location may be modified Media pool may change Vaulting locations omnimm -modify_medium omnimm -move_medium Student Notes Data Protector provides another possibility for vaulting operations.00 6-46 2003 Hewlett-Packard Development Company.hp. U1610S B. but not yet offsite Tapes are physically at a remote location. The command line could be used in conjunction with an automation script to make the media management simpler. such as: Active_pool On-site_vault Off-site_vault Free Pool This is the set of media available within a device repository (library) the active pool could also be considered a "scratch" pool Tapes here are out of the device. You may want to create a media pool for each physical location that a tape may be stored. http://education. L. or just removed from a device repository. Multiple media pools may serve as media repositories when media are to be taken offsite.P. Consider the following worked example for providing automated vaulting operations and media management.com . Data Protector provides both the GUI and command line to allow you to move media from one pool to another of the same type. com U1610S B. L.00 6-47 2003 Hewlett-Packard Development Company.P.Module 6 Media Management Command Example The following example demonstrates the command line method of modifying an existing medium that is moving to a different location (you may change the label at the same time): <old label> omnimm -modify_medium "Default File_9" <new label> Vault_File_9 <new location> "Offsite Vault" Medium information modified.hp. . Medium label : Vault_File_9 Location : offsite vault omnimm -move_medium "Default File_9" Offsite_vault <Media Label> <New Media Pool> http://education. http://education. one way would be to create temporary files. passing to it the session information.hp.Module 6 Media Management 6–21.sh processes the session information and collects the media data from the Data Protector database.sh (sample only.log & exit 0 U1610S B. the other way would be to pass variables directly as positional parameters. It simply starts the manage_media.com .sh script # execute the manage_media.sh) (manage_media. Two scripts will be used. not provided with the product.P. Media data collection 2. The manage_media.sh script.sh # execute as a session post-exec (from /opt/omni/lbin) # optionally store the session and key in a file #print $SESSIONKEY >/tmp/KEY #print $SESSIONID > /tmp/ID # pass the session information to the manage_media. and the label and location are updated. TEXT PAGE: Automated Media Vaulting (A Worked Example with Custom Sample POSIX Shell Scripts) Scenario: Tapes are to be taken out of the library each morning and sent offsite for vault storage. then exits. The number of media used by the particular session is counted and stored in a temporary file.sh $SESSIONKEY $SESSIONID > /tmp/manage_media.sh script is used as a session post-exec script. (this could be printed or emailed if desired). 1. There may be two ways to pass data from the running session to the manage_media. The post-exec feature for the backup specification is used to create a list of media used during the backup session and store it in a file for further processing. A record of the changes is also logged into another file for verification.sh) The collection. L. Media manipulation (collection. Collection. The file is read and each medium listed is moved to a different media pool. The sample provided includes both methods.00 6-48 2003 Hewlett-Packard Development Company. with one method commented out.sh as a background job /opt/omni/lbin/manage_media.sh as a background job. create the script in /opt/omni/lbin on the management server) #!/usr/bin/sh # collection. hp. L. not provided with the product.sh # executed from collection.P.sh # Env Vars for session Post_Exec script # DATALIST name of the datalist # MODE full or incr backup # OWNER session owner # PPID parent process of the session # PREVIEW 0 or 1 if in the preview mode # PWD current directory # RESTARTED 0 or 1 if restarted due to prior failure # SESSIONID omni session id of the running session # SESSIONKEY session key of the running session # SHELL type of unix shell in use # SMEXIT status of the backup session ####### # optionally read data from KEY and ID files if created by collection.00 6-49 2003 Hewlett-Packard Development Company.com U1610S B. create the script on /opt/omni/lbin on the Unix Cell Manager system) #!/usr/bin/sh # manage_media.sh #SESSIONKEY="$(cat /tmp/KEY)" #SESSIONID="$(cat /tmp/ID)" ####### SESSIONKEY="$1" SESSIONID="$2" # VAULT=file_vault # destination pool (considered to be the vault) MED_PRE=VAULT # prefix added to each medium moved to the vault LOC="onsite vault" # location for each medium moved to the vault # Collect the media list from the database /opt/omni/bin/omnidb -session $SESSIONID -media -detail|\ awk -F ":" '$1 ~ /Medium Label/ {print $2}' > /tmp/media_$SESSIONKEY sleep 30 #sleep to allow the database record locks to be freed num_media=$(wc -l /tmp/media_$SESSIONKEY) print number of media used = $num_media print print contents of /tmp/media_$SESSIONKEY cat /tmp/media_$SESSIONKEY sleep 5 exec 4< /tmp/media_$SESSIONKEY COUNT=1 # perform the media operations move and change label/location while read -u4 CURRENT_TAPE do print moving media ${COUNT}.Module 6 Media Management Manage_media. . $CURRENT_TAPE to $VAULT /opt/omni/bin/omnimm -move_medium "${CURRENT_TAPE}" ${VAULT} && \ /opt/omni/bin/omnimm -modify_medium "${CURRENT_TAPE}" \ "${MED_PRE}_${CURRENT_TAPE}" "${LOC}" ((COUNT+=1)) done exec 4<&exit 0 http://education.sh (sample only. What is the purpose of a Media Pool? 2. Review Questions 1. When will you want to use Magazine Support? 5. What protection features does Data Protector provide to safeguard the integrity of your backups? • • • 3. What Media Condition Factors does Data Protector implement? U1610S B. Data Protector provides two media allocation policies.P.com . strict and loose. Briefly.hp.00 6-50 2003 Hewlett-Packard Development Company. • strict • loose 4. L. http://education.Module 6 Media Management 6–22. describe the purpose of these policies. TRUE or FALSE? Explain. TRUE or FALSE? 10. What must be done before Data Protector can use media? 11. What does recycle do to media. How can you change the label on an existing tape? What about the location? Does the tape need to be loaded into a tape drive in order to change the label or location? 7. . By default. and do the media have to be loaded? 8. L. you export it.hp. When is force required? 12. TRUE or FALSE? 13.P. TRUE or FALSE? Explain. To remove bad media from a pool. When initializing media. 14. 9. What happens during a media import? Explain why this would be necessary. http://education. Data Protector supports Vaulting.00 6-51 2003 Hewlett-Packard Development Company.Module 6 Media Management 6. the size in megabytes set by specify or determine specifies the hard limit as to how much data it will hold. Data Protector will automatically initialize blank media.com U1610S B. P. L.com . http://education.00 6-52 2003 Hewlett-Packard Development Company.Module 6 Media Management U1610S B.hp. Configure library devices for use with Data Protector. Bulk-enter/eject tapes from a library repository.Module 7 — Logical Devices Objectives Upon completion of this module. L.00 7-1 2003 Hewlett-Packard Development Company. http://education.com U1610S B. Describe the advanced options for logical devices. you will be able to do the following: • • • • • • • Create simple logical devices within Data Protector. Scan device repositories to determine their contents. Troubleshoot and test a library device.hp. .P. Bulk-initialize tapes within the library repository. U1610S B. media verification.P.hp. media duplication and media listing. or drive index). rather.com . SCSI path. for example backup and restore. The Logical Device concept is used because it allows for easy configuration of device options and greater flexibility in changing devices after backups have been configured. media scanning. The Logical Device definition is stored in the Data Protector media management database. SLIDE: The Logical Device The Logical Device Usage: Usage: •• Backup Backup •• Restore Restore •• Format Format •• Copy Copy •• Scan Scan •• Verify Verify Logical Device Definition Device Options Physical Properties Physical Device Media Student Notes Data Protector does not reference physical devices directly. commonly referred to as the MMDB. http://education.00 7-2 2003 Hewlett-Packard Development Company. A Logical Device consists of a physical part (such as a device file name. Logical Devices are used for all Data Protector operations that require access to a physical device. media initialization. L. it uses a logical representation of the device known simply as a Logical Device.Module 7 Logical Devices 7–1. and a logical part (parameters that control Data Protector's usage of the device). . this controls the Media Pools that will be available to the device.Module 7 Logical Devices 7–2. In most cases the device file for the tape drive is already in existence. L.P. and we simply associate Data Protector features and options with that physical device.com U1610S B. • • • • • • • Standalone Stacker SCSI-II Library (used for SCSI and Fiber Channel) Jukebox External Control GRAU DAS Library StorageTek ACS Library Standalone Device Creation The creation of a standalone device is usually quite simple.hp.00 7-3 2003 Hewlett-Packard Development Company. Be sure to match the device type with physical device. http://education. SLIDE: Logical Device Types Logical Device Types Device Types • Standalone (tape and file) • Stacker • SCSI-II Library • Jukebox (file and optical) • External Control • GRAU DAS Library • StorageTek ACS Library Data Formats • Data Protector • EMC Fastrax • NDMP Student Notes Data Protector allows you to configure the following predefined Logical Device types. this may be increased by manually initializing the file. The media from the file (disk) backup may additionally be backed up to tape for further protection from system failure if needed. it is also possible to create a file type device.Module 7 Logical Devices Standalone File Device While it is true that most standalone devices are tape drives. This type of backup is useful for quick backup. they will be initialized with an Data Protector tape header.” In your standalone device configuration.hp.P. L.com . in an existing filesystem. and no operator intervention is desired to manually change tapes during the backup. The configuration of a file device is very similar to that of a tape drive. This may be beneficial if you have a quantity of available space and you would like to perform a quick backup. when a tape may not be required. A cascade is essentially a standalone device with more than one physical device. The default size for the Data Protector file medium is 100 MB.00 7-4 2003 Hewlett-Packard Development Company. DLT8000) Ultrium drive (LTO) Cascades A cascade is a series of standalone type devices (of the same type) connected to one host that the user wants to use in sequence. DDS3. DDS4) External DDS drive External DLT drive (DLT4000. The files would be treated just as any other medium. Cascades are useful for backing up more data than would be able to fit on a single tape. it is possible to define multiple device files. (see the module for Media Management for details) Standalone and Cascades Standalone A single drive device with no repository slots connected to one system. To configure a device cascade within Data Protector you have to select the device policy “standalone. DDS2. http://education. DLT7000. For example: /dev/rmt/c1t0d0BEST /dev/rmt/c1t1d0BEST /dev/rmt/c1t2d0BEST U1610S B. except that the filenames of the Physical Devices are the actual files that the backups will be written to. In this case Data Protector will write to a file on the disk. Examples of common standalone devices: • • • • Internal DDS drive (DDS1. This is the most common type of device used with Data Protector. 00 7-5 2003 Hewlett-Packard Development Company.hp. SCSI-II Library and Jukebox The SCSI-II Library is a device with multiple repository slots and one or more media drives. once the robotics has loaded the appropriate medium.com U1610S B. the system to which the robotic is connected. Only one backup device license is required per cascade during backup operations. and the use of such items as cleaning tapes and barcode readers. Data Protector accesses the library robotics through a special device file or SCSI path.Module 7 Logical Devices Data Protector will use the physical devices in the same order as defined in the standalone device configuration. Using this concept. In most cases the data device files are automatically created by the operating system. a SCSI-II Library is configured in two steps: • Configuring the Library and Control Path When you add a new SCSI-II Library. the changer#:bus:target:lun identify the device path for the library controller. You'll need to have one data path for each drive in the library. The robotics picks up the media from the slot and inserts it into a data drive or unloads it and puts it back into a slot. Larger library devices are also equipped with barcode readers for rapid scanning of the media repository. The Library is controlled using the SCSI commands. (Eg.P. • The Data Path The data path is used to write data to the medium or read data from it. In many cases the barcode scanning will obtain the labels from a cache at the device. L. The access to a library is split into two paths: • The Control Path The control path is responsible for the control of the robotics within an SCSI-II library. http://education. you first define the robotic. /dev/rmt/0m (UX) or Tape0:0:3:0C (Windows)). . sctl. The data path is the device file associated with the tape drive. the number of slots used. On Windows. This includes the definition of the control device file. On HP-UX systems the appropriate SCSI driver (spt. The default directory path for schgr devices is /dev/rac. the device scans the barcodes as the tapes are entered into the device. schgr) must be configured in the kernel and the SCSI-II control device file must be created before you can configure the device within Data Protector. which can perform random accesses to media repository using the robotics. Module 7 Logical Devices • Configuring the Drives and Data Path The configuration of the data drives is similar to the configuration of standalone devices. L. The user cannot define into which drive the platter will be loaded. operates the Jukebox. ssrfc) Data Protector offers two ways to configure a Magneto Optical Jukebox. so as to allow both sides of the MO medium to be accessed. it is split into two steps: 1. In comparison to a SCSII library. 2. as the HP-UX Jukebox device drivers handle the assignment of the drive to the device file.P. Again. Define a library name and the device files for all MO platters. These are managed with StorageTek ACSLS software. which are available only on HP-UX. the drive index number within the library. Jukebox Configuration The Jukebox is very similar to the SCSI-II Library. The configuration of an MO Jukebox is similar to an SCSI-II library configuration. http://education. (schgr. This is implemented with the use of a special magneto optical driver set. NOTE There are separate device files for side A and side B of the Magneto Optical platters. To use all the drives within a magneto optical jukebox simultaneously.hp. The major difference to SCSI-II library is that a pair of special MO drivers. available on HP-UX. and the type of drive and medium pool used by this device. but only works for Magneto Optical devices.00 7-6 2003 Hewlett-Packard Development Company. See the procedure later in this module for configuration of the Jukebox on HP-UX. the system to which the drive is connected. this jukebox should not be used by any other application U1610S B. NOTE If you configure a jukebox within Data Protector and use it for backups and restores. you have to create as many “logical” drives as there are physical drives available. The SCSI-II library policy cannot be used to run GRAU devices or large StorageTek silos. You define the data device file. The driver for the Jukebox understands the concept of media rotation.com . you are not required to specify a device file. • • As an SCSI-II Library (see above) As an MO Jukebox (preferred) The difference with a Jukebox is that the user accesses a side of a platter and the operating system driver automatically mounts the platter into an available drive. Define the drives. L.P.com U1610S B. while libraries can randomly access the media loaded in their repository slots http://education. .Module 7 Logical Devices Stacker Stacker devices have a cartridge with multiple media slots. The difference between a Library Device and a Stacker is that a Stacker has no control over media selection.00 7-7 2003 Hewlett-Packard Development Company.hp. Stackers can only load media sequentially from the cartridge. simply load and unload. com . http://education. and then configure each one a separate Logical Device (most common on Unix systems) Configure multiple single physical devices as a single Logical Device Configure a tape library more than once.P. The two platforms for the Cell Manager. There are numerous ways to configure Data Protector to make use of the backup devices that are available. each with a different name and set of properties Configure a physical device to have multiple device files. from a Logical Device perspective. each with a sub-set of all the available drives and slots (this is necessary when a library contains drives of different types and where the repository contains more than one type of media) U1610S B. Data Protector supports devices connected to many different Media Agent platforms. you must first understand how the operating system makes the physical device available to you before you can configure it as a Logical Device. SLIDE: Device Configurations Device Configurations Logical device Logical device Logical device Logical device Logical device Logical devices Drives Hardware compression Library controller Robotic and barcode reader Repository slots Mail slot (import/export) Cleaning slot Student Notes While most of the configuration within Data Protector for a Logical Device contains parameters added by Data Protector.Module 7 Logical Devices 7–3. Within Data Protector. it is possible to: • • • • Configure a single physical device multiple times.hp. L.00 7-8 2003 Hewlett-Packard Development Company. and each one represents devices in a slightly different manner. Unix and Windows usually detect and add their devices automatically. Module 7 Logical Devices NOTE On Windows 2000 systems it is necessary to disable the RSM (Removable Storage Manager) driver for the device to be used by Data Protector. Device Scanning (devbra) Data Protector provides a tool to scan Media Agent systems and discover attached devices. This prevents Data Protector from trying to access the device from more than one session at the same time. NOTE: There is a global option to control the queuing time (in minutes).hp. 60 is the default value. .P. or on Windows the Device Manager. Use the device manager to facilitate this change. The Data Protector command devbra –devices lists available tape drives and library devices. the ioscan command. Device request will be queued for up to 60 minutes until the desired drive is available. SmWaitForDevice. it is necessary to use the “Lock Name” property for the Logical Device.00 7-9 2003 Hewlett-Packard Development Company. such as on HP-UX. Sample output from devbra –devices: Windows Host: C:\Program Files\Omniback\bin\devbra –devices Tape: HP:C1533A Path: “Tape0:0:3:0C” SN: “N/A” Description: CLAIMED:DAT 4mm Tape Drive DDS-2 Device type: 4mm Flags: 0x0011 Unix Host: # /opt/omni/lbin/devbra –devices Tape: QUANTUM:DLT7000 Path: “/dev/rmt/0mn” SN: “JF73910796” Description: Quantum DLT 7000 series drive Device type: dlt Flags: 0x0081 QUANTUM:DLT7000 Path: “/dev/rmt/0mn” SN: “JF74020114” Description: Quantum DLT 7000 series drive Device type: dlt Flags: 0x0081 Tape: http://education. Device Locking and Queuing When a physical device is configured more than one time within Data Protector. as RSM is not compatible with Data Protector. You may also use operating system tools as available to discover the connected devices.com U1610S B. L. hp.Module 7 Logical Devices Tape: HP:C1533A Path: “/dev/rmt/0mn” SN: “N/A” Description: DAT 4mm Tape Drive DDS-2 Device type: 4mm Flags: 0x0001 HP:C5177-7000 Path: “/dev/rac/c3t4d0” Description: HP DLT Library 7228w Flags: 0x0086 Slots: 28 Drives: 2 Drive(s) SN: “JF74020114” “JF73910796” SN: “fq000512” Exch: U1610S B.com .P. http://education.00 7-10 2003 Hewlett-Packard Development Company. L. but may be altered as needed once the auto-configuration process completes. . L. hosts or devices are selected by the Administrator and the Logical Device configuration process is then started. Individual device options are set to the product defaults. namely Automatic or Manual. Data Protector executes the device agent (devbra) to scan the Media Agent hosts and assemble a device list.com U1610S B. the Administrator specifies all parameters needed to configure the Logical Device.Module 7 Logical Devices 7–4. With Manual device configuration.P. a high degree of control over all of the parameters is available.00 7-11 2003 Hewlett-Packard Development Company. From the list. SLIDE: Configuration Methods Configuration Methods Automatic • Standalone devices • Libraries (SAN or SCSI) • Two step approach • select system/device • select autoconfigure • Automatic Lock Names • Adjust options as needed Manual • All device types • All parameters user selected • Adjust options as needed Student Notes Data Protector offers two methods of configuring devices. Using this method. http://education.hp. but this procedure requires more experience and a thorough understanding of the hardware and the operating system device to be configured. With Automatic device configuration. omniupload Student Notes The Data Protector Administrator can define a Logical Device via the GUI or by editing a template. L.(omniupload/omnidownload) refer to the following pages or use the online man pages. To modify the configuration of an existing device or to just extract the device configuration from the database use the omnidownload command. and therefore the recommended method. this creates a file which then may be edited and uploaded with omniupload command. NOTE For more information on these commands. The templates in <OMNICONFIG>/devices may be uploaded into the Data Protector Media Management Internal Database with the omniupload command. SLIDE: Adding a Device (manual method) Adding a Device (manual method) Using the command line omnidownload.P.00 7-12 2003 Hewlett-Packard Development Company. U1610S B.com . Logical Device configuration via the GUI is easier than the using the command line.Module 7 Logical Devices 7–5.hp. http://education. this also requires the NDMP Media Agent to be installed TIP! Using the omnidownload command to save device configurations in text files may be beneficial when performing disaster recovery. Standalone. Device Type Interface Type NDMP Server SCSI-II Library Choice of SCSI-II. NDMP – NetApp.Celera Server name required when NDMP is the interface type. the library device adds some configuration parameters for the library components. there are many Data Protector options to choose from including: Logical Device Name (max 32 chars) The name within Data Protector that you will use to refer to this Logical Device. The system to which the physical device is connected. SCSI Library. Example “Hewlett Packard DLT 7000”. . http://education. this also requires the NDMP Media Agent to be installed Description (max 64 chars) Client Device Type Data Format NDMP Server Library Options In addition to the general options available to the standalone device. Choice of Data Protector or NDMP– NetApp. NDMP . NDMP – Celera Server name required when NDMP is the interface type.Module 7 Logical Devices Logical Device General Options When adding a Logical Device. etc.P.com U1610S B. Example: Oasis_DLT_1 (avoid using spaces in the name) A user defined description of the device. as device configurations would need to be created before restore operations would take place. L.hp.00 7-13 2003 Hewlett-Packard Development Company. may be used to display configuration information about the Cell omniupload omnicellinfo Examples: The following table provides some samples using the omniupload/download commands Description List the devices in the cell: (use either of the commands) List the details of a device: (use either of the commands) View the device description template file Copy a template file before editing Edit the file before uploading Upload a new device definition into the cell database Download a device definition for modification where <dev> is the logical device Upload a modified device configuration Command Line Examples omnicellinfo -dev omnidownload -dev_info omnicellinfo -dev -detail omnidownload -list_devices -detail more /etc/opt/omni/devices/configuration.hp. L.00 7-14 2003 Hewlett-Packard Development Company.P.com .dev dds.dev omniupload -create_device dds.dev cd /etc/opt/omni/devices cp tpstalone. http://education. may be used to upload a new device configuration into the Data Protector database from a file.dev vi dds.dev omnidownload -device <dev> -file <Filename> omniupload –modify_device <Logical Name> file <Filename> U1610S B.Module 7 Logical Devices omniupload/omnidownload omnidownload may be used to extract device information from Data Protector database into a file. com U1610S B.hp.00 7-15 2003 Hewlett-Packard Development Company. Barcode Reader Support http://education.P. L. Example: /dev/rac/c0t5d1 Example: scsi2:0:5:1 (HP-UX) (Windows) (Windows) Example: changer0:0:5:0 Drive Index This number indicates the position of the drive within the library. . SLIDE: Physical Device Selection Physical Device Selection Standalone device Library robotic device Student Notes Robotic Device File (SCSI-pass-through device file) The system device file that is used by the operating system to communicate with robotic controller. This is used to identify to the robot which drive to load tapes into. Informs Data Protector if the library includes a barcode reader mechanism.Module 7 Logical Devices 7–6. Unfortunately Windows 2000 will report that the tapes are bad for those that have Data Protector format on them.hp. U1610S B. LTO. Repository slots Drive(s) The repository slots available in this logical library (This may be different from the physical settings. Eject. the RSM driver is not compatible with Data Protector. When you have a choice of drivers. Libraries on Windows 2000 On Windows 2000.com . This feature can be used to ensure that there is no contention between systems. each drive within the library may be a different type of device. This tells Data Protector how to react if it unexpectedly finds that a drive already has media in it. Windows 2000 will attempt to operate the device at boot time. Each drive must be defined within Data Protector in a similar way as any other standalone Logical Device. L. http://education. Choices will vary depending upon the capability of the library. The library controller in this case would need to be specified by manually entering its name in the “SCSI address or filename of the library robotic” field when configuring the tape library. Example: Abort.P. On systems that have the RSM enabled by default.Module 7 Logical Devices SCSI-II Reserve. If the sctl device file is manually configured with the mknod command. a SCSI Pass through driver or autochanger driver (sctl or schgr) must be installed and configured properly on your system.00 7-16 2003 Hewlett-Packard Development Company. as Data Protector is able to detect the device name. Release Robotic Control Busy Drive Handling When a library is connected to two or more systems on a shared bus in a SAN.0 of Data Protector. Libraries on HP-UX Before you configure a SCSI-II Library (Tape or Optical).) A library can contain one or more drives. Disable the RSM for the auto-changer/library devices that you want to use with Data Protector. Data Protector is able to use the device but may be unable to detect it when performing the system scan. the schgr driver makes the Logical Device configuration simpler. As of version 4. The Windows 2000 boot process will automatically try to load and scan each tape for its format. Eject to Mail Slot. such as DLT. etc. Reboot your system as necessary after disabling the device driver for your tape library within the device manager. and before the backup process starts. SLIDE: Library Repository Configuration Library Repository Configuration Slot range Used with Detect dirty drive Student Notes The configuration of the Library Repository allows the Administrator to select all or some of the available slots within a particular library. http://education. or as individual slot numbers. LTO). as shown. Data Protector will use this slot with the logical devices that have enabled the “dirty drive detection” option. If a drive reports that it is in the clean-me mode.log on Windows.hp.P. The slots need not be sequential. Uses of the cleaning tapes (loaded automatically by Data Protector) are logged in the cleaning.log on Unix and C:\Program Files\Omniback\log\cleaining.Module 7 Logical Devices 7–7. each time with a different set of physical slots associated with it. Data Protector will load the cleaning tape before the backup of data begins. The Cleaning Slot option specifies which (if any) of the library repository slots contains a cleaning tape(s). It is possible that a tape library is configured more than once as a logical device.log file stored on the cell manager in the /var/opt/omni/log/cleaning. The slots may be specified in a range.00 7-17 2003 Hewlett-Packard Development Company.com U1610S B. although this is most common. L. . This type of configuration is very useful when the tape library contains more than one type of tape drive (DLT. Dirty drive detection is performed only once. U1610S B.00 7-18 2003 Hewlett-Packard Development Company. where t1 represents the SCSI target ID. this is used to match with the drive 1 (index 1) for the physical drive in the library. SLIDE: Library Drive Configuration Library Drive Configuration Student Notes The Data Protector Library configuration controls access to the library only. You must be able to set the SCSI target ID of the device equal to the drive index number for that possibility. you must configure a logical device type "drive" for each tape drive within the library. One way to make this simpler is to use the SCSI ID of the drive. The example shown on the slide is for a HP SureStore Library. Later you will be able to add a new drive to the library configuration by selecting the library from the "Device and Media Management" context and then Edit -> Add -> Drive… . L.hp. select yes to configure the drive now. Library Drive Index Numbers This is likely to be one of the more difficult parts of the SCSI Library configuration. After the completion of the Library configuration you will be prompted to create a drive for the library.com . You will need to know which device file matches to the library drives.P. note the data device path may be something like: c0t1d0BEST.Module 7 Logical Devices 7–8. Be prepared to provide the device file that corresponds with the library drive index number. http://education. This setting will allow you to easily identify the device in the list that Data Protector will present. this would correspond to the first drive and the Data Protector index number of one (1). . and available as a command. For example Drive 2 gets a tape loaded and then the data is sent to Drive 1. http://education.com U1610S B. restore and media management sessions.00 7-19 2003 Hewlett-Packard Development Company. The command executable is in: <OMNIHOME>/lbin on Unix and in the <OMNIHOME>\bin directory on Windows. no interaction with UMA is recommended. Data Protector starts index numbers at one. NOTE When backup. restore and media operations are in progress. L. such as load and unload: UMA Utility Media Agent The UMA is the only agent that is interactive. Data Protector uses the following agents to access the data (tape) devices in the library: BMA Backup Media Agent RMA Restore Media Agent MMA Media Management Agent Data Protector uses the following agent to manage the library activities. The UMA is useful for troubleshooting and testing the tape library operations.Module 7 Logical Devices NOTE On some devices. This will result in a backup failure! NOTE Library Operations Data Protector uses its various agents to access the library devices during backup. Data Protector may load a tape into the wrong drive.P. There is also a man-page for it. the drives may be numbered starting with zero (0).hp. If you get the Exchanger Data Device and the Drive Index numbers matched incorrectly. Which agents are used depends upon the session type. This default assignment is used for tape initialization as well as backup.00 7-20 2003 Hewlett-Packard Development Company. Example: /dev/rmt/c2t2d0BEST (HP-UX) Example: Tape0:0:5:0C (Windows 2000) Device File Default Media Pool Data Protector requires a Media Pool to be assigned to each Logical Device. Backup Specifications may override this pool assignment so that a particular Media Pool Is used instead of the default. Example: Default DDS.com . The system device file that is used by the operating system to communicate with the data device. Example: DLT The default media pool that will be used for automatic media initialization and backup. U1610S B.Module 7 Logical Devices 7–9. SLIDE: Media Type and Default Pool Media Type and Default Pool Standalone and Library Drive Student Notes Data protector offers the following choices for device media type and Default Media Pool: Media Type Pool Name The type of media that the device supports.hp. http://education. L.P. The table below presents these options.Module 7 Logical Devices 7–10. previous range 1-5) Eject Specifies whether the tape should be ejected after the operation that has accessed it completes. Generally.00 7-21 2003 Hewlett-Packard Development Company. Values: 1 to 32 (32 as of Data Protector 5. This is only useful for standalone tape drives. Setting this to an optimum value for a particular device type allows the device to stream.P.hp. Concurrency This defines the maximum number of concurrent data streams (from disk agents) that the device will receive. faster devices such as DLT 7000 should be configured with higher concurrency values than slower devices such as DDS. and do not require changes in order to use a particular device. . This can have various effects on backup performance. L. http://education. SLIDE: Advanced Options Advanced Options Student Notes Library drives as well as standalone devices support additional Advanced options to control how the devices are to be used during backup. The default is not to eject.com U1610S B.0. The advanced options allow for more granular control over performance characteristics of the device. All of the advanced options have default values. Larger block sizes (greater than 56K) on some Windows systems require modifications to the registry. This option can affect performance negatively. This is useful if manual media changes were performed since the last media scan. For Data Protector to use tapes for backup in different devices.P. The cleaning check is only performed once. because the Media Agent can more quickly locate the segment containing the restore data. because each segment has a fast search mark. consult with the vendor for supported block size for your devices. The default is 64 KB on devices connected to UNIX systems and 56 KB on devices connected to some Windows systems. Optimal segment size depends on the media type used in the device and the kind of data backed up. the block size must be set the same for all devices. It senses this via the SCSI status bytes received back from the drive. and may not be supported. Data Protector will either automatically clean the drive itself or issue a mount request for a cleaning tape to be loaded. the segment size is in the range of 100 to 2000 MB. Your device/interface adapter may not allow for large block sizes. The segment size affects the speed of a restore. Block Size Segment Size U1610S B. http://education. For devices that support barcode readers. If this option is enabled. The maximum block size is currently 1024 KB. otherwise the scan requires each tape to be loaded into a drive to scan the header. The CRC check allows you to verify the accuracy of the data written to the media with the verify operation in the GUI or by the omnimver command. Data Protector will access the cartridge memory when scanning a tape as well as when importing the tape. this is a barcodes scan. Use this field to enter the size of the data segments on the media. Rescan This library option instructs Data Protector to rescan the device repository before a backup starts.00 7-22 2003 Hewlett-Packard Development Company. L. By default. A smaller segment size requires additional space on the media. Dirty Drive Detection This tells Data Protector to detect when a drive is in need of cleaning. For devices. See the Administrators Reference Manual for details. and before the backup begins. This rescan synchronizes the Data Protector media database with the media that is currently present within the library repository. Drives that set the SCSI status during a backup execution may cause the backup to fail with IO errors. Disaster recovery requires the default block size to be used on Windows systems.com . such as LTO (Ultrium) that support cartridge memory.Module 7 Logical Devices CRC Check Use this button to write CRC checks to the media used with this logical device. The additional fast search marks result in faster restores. The device hardware processes data it receives using a device type specific block size. depending on the medium type.hp. Data Protector allows the adjustment of the size of blocks it sends to the device. sh (Windows) The time in minutes that must of elapsed since a mount prompt was issued before the Mount Prompt Notification script is executed. Each buffer area consists of 8 Disk Agent buffers (of the same size as the block size configured for the device). results in a 50% reduction in memory consumption. In this case. for instance.00 7-23 2003 Hewlett-Packard Development Company.com U1610S B. then it becomes more important that a Media Agent has enough data ready for writing to keep the device in the streaming mode. There are two basic reasons to change this setting: • Shortage of memory The shared memory required for a Media Agent can be calculated as follows: DAConcurrency*NumberOfBuffers*BlockSize Reducing the number of buffers from 8 to 4.P. segment size and concurrency. Default: 30 Minutes. The lock is name is usually optional. Used when a physical device is defined more than once for Data Protector. The use of the same lock name for each use of the physical device prevents Data Protector from trying to use (and failing) the same physical device more than once concurrently. . The default script simply sends an email notification to the backup owner containing the relevant details. • Streaming If the available network bandwidth varies significantly during backup. In some cases you may want a different combination of block size. with performance implications. L. The script to be executed after a mount prompt request has been outstanding for the number of minutes configured as the Mount Prompt Delay.sh (Unix) C:\Program Files\Omniback\bin\Mounts.hp.Module 7 Logical Devices Disk Agent Buffers Mount Request Script Mount Request Delay Lock Name Data Protector Media Agents and Disk Agents use memory buffers to hold data waiting to be transferred. and just a string of text that you choose. It is common to configure a tape drive as more than one Logical Device when you would like to apply more than one set of option to be used for different operations such as backup. required for SAN configured libraries. This memory is divided into a number of buffer areas (one for each Disk Agent. increase the number of buffers. http://education. Default template: /opt/omni/lbin/Mount. depending on device concurrency). although this is rarely necessary. You can change this value to be anything between 1 and 32. The example at the top of the slide (above) shows parallel backup. Fewer Disk Agents may be started for backup due to the number of objects included in the backup specification. this allows for the simultaneous (concurrent) backup of multiple objects to a single Logical Device at the same time.P. Any number of logical devices with varying concurrency values may be used within the cell according to cell’s license limits. Data Protector supports parallel backup as well as concurrency. however the device defaults are usually much lower. The maximum concurrency per device is 32. http://education. SLIDE: Device Concurrency Device Concurrency Disk Agent Media Agent Concurrency = 1 Disk Agent Media Agent Disk Agent Concurrency = 3 Disk Agent Media Agent Disk Agent Maximum concurrency: 32 Student Notes Data Protector supports a Logical Device feature called concurrency.com .00 7-24 2003 Hewlett-Packard Development Company. both logical devices set to concurrency one. in the range of 2-5. Concurrency is one of the most commonly altered device options. This option controls the DA to MA ratio for the device. Data Protector will attempt to start the required number of Disk Agents sending data to the Media Agent simultaneously to satisfy the concurrency of the logical device during backup operations. The concurrency feature is primarily designed to keep the Media Agent streaming data to the device to achieve the best device performance.Module 7 Logical Devices 7–11. U1610S B.hp. Parallel backup allows for multiple tape drives to be used (in parallel) within both a single backup job execution as well as with multiple backups running within the Data Protector Cell at the same time. L. Higher values for concurrency. You will need to test various solutions in your environment to find the best possible combination of objects and concurrency to achieve the best performance. http://education. Concurrency Implications • Backup Performance The performance of some linear tape devices. however. Some newer linear tape devices such as HP’s Ultrium allow for speed variation (adaptive write). The organization of the objects within the backup specification will have an impact as well. In most cases multiple objects will reside on the same physical disk. and can better accommodate the data flow provided by the Media Agent to stream the drive. They are : MaxMAperSM (32 default. Data Protector will have to read more of the tape to restore a single object that was interleaved onto the tape with other objects during the backup process. don't necessarily mean higher backup performance.Module 7 Logical Devices There are two global variables that have an impact on the concurrency level as well as the level of parallelism. This should be a consideration when configuring the logical device for backup. • Restore Performance The performance of Data Protector restore may be negatively affected when a device configured for concurrency was used for backup and you are not using parallel restore to recover data. . MaxDAperMA (default 32. range 1-32) controls the maximum number of load balanced media agents per session manager. backups are performed much more than restores. range 1-32) controls the maximum concurrency value (DA to MA) for logical devices. such as DLT. Generally speaking.hp. Using concurrency to backup the partitioned disk may lead to disk head contention. The bottom line is that concurrency values are designed to improve backup performance in most situations.com U1610S B.00 7-25 2003 Hewlett-Packard Development Company. may be negatively impacted by a lack of streaming. so concurrency values should be configured to achieve the best backup performance possible. L.P. Consider performing a full backup on a server with a partitioned disk. and the backup may actually take longer and not allow the tape device to stream due to the disk bottleneck. L.P.Module 7 Logical Devices 7–12. SLIDE: Data Protector Tape Format Tape Format Tape Image Header Data Segments minimum 10 MB 150-1000 MB defaults Segment EOD End of Data Data Blocks Block Size: 8K -1024K Catalog Fast Fast Search Information Search Mark Mark Student Notes The Data Protector tape format supports the following features: • • • • • • • Fast Tape Positioning Multiple Block Sizes Data Multiplexing Appendable Media Label Catalog Information Verification of Tape Contents U1610S B.com . http://education.hp.00 7-26 2003 Hewlett-Packard Development Company. the catalog information is kept in memory and then written to the tape at the end of each segment. and can range from 1 to 60 MB.Segment size is no longer a fixed size (as of 4.. The segment size used will now be determined by the segment size parameter. • Segments — Data to be backed up is written to a segment. This ID is unique and used by Data Protector internally. The larger the segment. the more memory is required to keep the backup information.. Larger tape segments can improve the performance of the backup in many cases. When the data is written to tape. (Media Import is covered in the next module). The size of the segment can be configured in the Logical Device configuration window with advanced options. The required block size for most Disaster Recovery backups is 64KB. or a system specific parameter named OMNIMAXCATALOG_<device_name>.0). The catalog information is also stored within the Data Protector database. • • • http://education. The catalog size takes precedence over the specified segment size.Data stored within the segments are written in blocks. Dynamic Segment Size --. Data Protector may adjust the size of the segment if the catalog reaches the defined limit. Catalog information may be read from the tape into the database by performing a media import. a larger block size may improve performance.hp. In prior versions of Data Protector the block size for Windows NT was at 56K. . when backing up a large data set. The parameter above is used to specify the maximum size of the segment on tape. Catalog Information — Catalog information is stored after each segment is written and records what data (file names. The block size for most Data Protector devices is 64 KB by default (file devices and reel tapes use 16 KB. This information is later used during the restore process. If larger segments are used.com U1610S B. In many cases. The default segment size is 12 MB.Module 7 Logical Devices Tape Sections The Data Protector tape is comprised of the following sections: • Tape Header — Data Protector writes a tape header and tape label. The size of the catalog per segment by default is 12 MB.) was backed up in that segment.00 7-27 2003 Hewlett-Packard Development Company. this should be tested within your environment. L. etc. By specifying a catalog size per device on a particular system. more memory is required on the system on which the media agent is running. This memory is used to store catalog information. but can range from 1 to 60 MB. the data within the segment will be from more than one disk agent. you can limit how large the catalog segment will be on the tape.) This default is now used for both Unix as well as Windows NT. the other is the Data Protector medium ID. The parameter to define the catalog limit must be in the omnirc file on the system where the device is connected. D3 uses 256 KB. . See the previous description for Dynamic Segment Size. The tape header uses only one block on the tape. You should set the block size to equal values if you want to exchange tapes between different devices. Data Blocks ---.P. There are two Data Protector labels: one is the user-defined label. If device concurrency is used. Windows devices were previously set to a default of 56 KB. http://education.hp.Module 7 Logical Devices Block Size Although it is possible to change the block size for a device. U1610S B. Consult with your device/interface documentation to verify support for larger block sizes. L.00 7-28 2003 Hewlett-Packard Development Company. Some disaster recovery procedures used by Data Protector will require the native (default 56KB) block size to be used due to the limited system functionality available at recovery time. it is advisable to be mindful of the following when doing so: • • • • • Each Logical Device has a block size option The default block size is set based upon the type of device Data Protector adjusts the block size automatically during the restore Data Protector backup cannot append to a tape originally written with a different block size than the one for the current device Some versions of Omniback do not support the same block size features as the current release. Some Windows devices still support only 56 KB. compared to the current setting of 64 KB.P.com . This was primarily due to hardware constraints within the operating systems hardware. Mount. File Session key to be used by omnimnt <config>/options/global: MountDelay=<DelayInMinutes> MountScript=<Full Pathname> Student Notes Data Protector provides a script template called Mount (Mount. Data Protector is providing an event driven notification mechanism. For example. The event in this case is a Mount Request. 3480. Loose. or they all may share a single Mount script.bat Parameters USER GROUP HOSTNAME STARTPID DEVNAME DEVHOST DEVFILE DEVCLASS DEVCLASSNAME MEDID MEDLABEL MEDLOC POOLNAME POLICY MEDCLASS MEDCLASSNAME SESSIONKEY Description User name User group name Name of host (short) PID of the process that caused the mount prompt Logical Device Name Short name of host where device is connected to File representing the device DAT standalone. DAT exchanger. App+Strict Medium class number DAT/DDS.P.bat on Windows) that may be executed whenever a device needs a tape. or Windows broadcast to owner of the backup at the cell server after 30 minutes of waiting for a tape to be loaded.Module 7 Logical Devices 7–13.sh on Unix. Every device may use a different script. . or to issue a message to a management application such as OpenView Operations by issuing the opcmsg command. For example.. NOTE The mount script may be customized to perform functions other than standard email.com U1610S B. you may want to execute some paging software in response to the event. The Mount Prompt Script executes in response to an event. App+Loose. Exabyte. MO standalone .hp. Currently same as devclass Medium ID Medium user label Location of the medium Name of the pool Strict.sh <product>/bin/mount. the Mount script will send an e-mail. SLIDE: Mount Notification Mount Notification Defaults Delay: Programs: _____________ 30min /opt/omni/lbin/Mount. L. The type of notification or notification method is up to you. Double Sided Optical. By default.. So in essence. Reel Tape. Optical. DAT stacker. http://education. it can interface with paging software to alert the operator.00 7-29 2003 Hewlett-Packard Development Company. com . http://education.P. The Data Protector Operator should satisfy the mount request from the Monitor GUI or with the omnimnt command.hp. The Mount Notification Script does not confirm the mount. when a backup is writing to a standalone device and the tape has been filled. NOTE In a later section of this course we will discuss in more detail some additional notification procedures that may be used for Data Protector events including mount events. When Data Protector executes the mount notification script. Data Protector issues a mount prompt (when interacting with the session) and then waits until the mount request is satisfied. L. the following events can take place: • • • Data Protector puts the session into the Mount Request state. The name of the logical device The hostname where the logical device is located The physical device file The device class number The device class name The medium ID Value DEVNAME=${5} or %5 DEVHOST=${6} or %6 DEVFILE=${7} or %7 DEVCLASS=${8} or %8 DEVCLASSNAME=${9} or %9 MEDID=${10} U1610S B. Data Protector will request a further tape to be loaded to continue the backup. The mount request may also occur when the tape in the drive is from a different media pool than the one assigned for the backup.00 7-30 2003 Hewlett-Packard Development Company. it passes the following positional parameters to it: Parameter THIS=${0} or %0 USER=${1} or %1 GROUP=${2} or %2 HOSTNAME=${3} or %3 STARTPID=${4} or %4 The name of this script The UNIX username The UNIX group name The expanded hostname The UNIX PID of the client process that started backup session. When this occurs. it simply issues the notification according to the script instructions. For example. Data Protector waits for the mount delay time (30 minutes) and then executes only once the notification script.Module 7 Logical Devices A mount notification is issued when a tape that Data Protector requires is not loaded in the drive or available within the repository of the library. P.com U1610S B. L. .hp.Module 7 Logical Devices MEDLABEL=${11} MEDLOC=${12) POOLNAME=${13} POLICY=${14} MEDCLASS=${15} MEDCLASSNAME=${16} SESSIONKEY=${17} The medium label The medium location The name of the pool medium belongs to The policy name for the pool The medium class number The medium class name The session key to be used by omnimnt http://education.00 7-31 2003 Hewlett-Packard Development Company. Data Protector controls the robotic of a library via a separate device than that of the drives.00 7-32 2003 Hewlett-Packard Development Company.com .Module 7 Logical Devices 7–14. The session manager then gets the Universal media agent to carry out the requests on behalf of the requesting system. unload. U1610S B. L. to perform all the library functions (load. The Data Protector Session Manager instructs the UMA (Universal Media Agent) running on the system.hp. This allows other systems that have library drives attached but no direct robotic control to issue library control requests (load. http://education. unload. SLIDE: Library Sharing Library Sharing System A Data Only inet MA MA SCSI or Fiber Channel TCP/IP Control and Data inet Session Manager MA UMA Robotic System B Student Notes Data Protector allows the sharing of library devices between multiple systems. eject.P. which has the library robotic control attached. or will share the same interface as the drives. scan) etc. eject) to the session manager. control and data. This is can be achieved because Data Protector separates the definition of a library into two parts. The robotic control will either have a dedicated SCSI interface that is attached to the controlling system. If the device files are not the same.P. To enable the direct access mode.libtab file on r848c77 for library hosted by r848c76: Note: quotes are used for library name because the name contains spaces. Data Protector allows for all library connected hosts to access the library directly.libtab Note: The libtab file may be copied to each host requiring direct library access or a client specific file may be created. or SAN zone. L. r848c77.libtab (HP-UX and Solaris) Other Unix: /usr/omni/.00 7-33 2003 Hewlett-Packard Development Company.com /dev/rac/c7t0d0 “HP:MSL5000 Series_r848c76” http://education.com U1610S B. The libtab file is a plain text file with the following format: <FQDN of the local client> <Device File or SCSI path> <Library Name> On HP-UX systems. a configuration file must be created on all hosts called the “libtab” file.Module 7 Logical Devices Direct Library Access Library sharing has one disadvantage. . The libtab definition file is store in: Windows: <OMNIHOME>\libtab UNIX: /opt/omni/. With direct library access. The library control host which coordinates access to the library robotics. To work around this possible failure point.hp. Manually Configuring the libtab File The purpose of the libtab file is to map the library robotic access from local host (media agent client). the “direct access” option may be used for the library configuration.hp. the Device File must be the same on all hosts that are to access the library. After the libtab file is created. If this controlling host if unavailable then the host sends controls directly to the library. a symbolic link may be used on the secondary hosts to create a device name that matches the original name on the controlling host.edunet. Sample /opt/omni/. all hosts may send library control commands directly to the library. where many hosts reside within the same SAN. Create the libtab file on each Windows or Unix system requiring direct access in the event of a library control host failure.dow. This is typically used within a SAN environment. the controlling host is a single point of failure. L. all three systems can “see” all four drives and also the robotic of the library.Module 7 Logical Devices 7–15. The goal of the configuration is that one system (smohpu04) gets access to the robotic of the library.e.hp.com .00 7-34 2003 Hewlett-Packard Development Company. smohpu04 smocl3 SAN http://education. i. representing the same physical drive.P. SLIDE: Autoconfigure a Device (1) Autoconfigure a Device (1) three systems and one library (4 drives + robotic control) Tape Library HP:C7200-800 (DLT 8000) smocl4 Student Notes This example assumes a configuration consisting of three systems and one library consisting of 4 drives. the same lock name for all logical drives should be created. After configuration. U1610S B. The library is connected via SAN to three systems. and all systems access all drives. as compared to previous versions.hp. and may take several minutes.Module 7 Logical Devices 7–16. . The DP 5. http://education.P. SLIDE: Autoconfigure a Device (2) Autoconfigure a Device (2) Select Autoconfigure Select hosts for library configuration Student Notes Data Protector 5. Data Protector scans all selected systems for attached devices.1 devbra tool now produces much more user-friendly output. This scan is done by the tool devbra. This new capability makes SAN based library configuration very simple and mostly automatic (with the exception of the previously mention libtab). The wizard asks you to select all the systems for which libraries or standalone devices are to be configured.1 includes the functionality from the “sanconf” tool (from DP 5. Right click Devices and select Autoconfigure Devices to start the auto configuration wizard.00 7-35 2003 Hewlett-Packard Development Company.com U1610S B. Click Next. L.0) now as part of the device GUI. L.hp. Several systems can access the same device (square button). Right-click the drive name to rename it before the configuration starts. With the grouping by devices (left screenshot) the presentation is based on libraries. which illustrates the step two of the auto configuration wizard. For the drives it is different. Two different presentations help to determine the assignments between the systems and the library. Since the name must be unique within DP a number is appended.Module 7 Logical Devices 7–17. The name of the configured drives consist of: <vendor ID>:<Product>_<Drive Index>_<system name>[(n)] where n is only used in case the drive is already setup inside Data Protector with the same name. The right screenshot shows a grouping based on systems. indicated by the radio button (circle). SLIDE: Autoconfigure a Device (3) Autoconfigure a Device (3) Switch between Device or Host grouping Select system to control the robotic Select systems which should get access to the devices Student Notes This slide contains two separate screenshots.com . This shows all assignments from the system point of view. http://education.00 7-36 2003 Hewlett-Packard Development Company. U1610S B. NOTE: Only one system can access the library robotic.P. .P.Module 7 Logical Devices The following lock names were automatically created: drive1: QUANTUM:DLT8000:CKA32P3224 drive2: QUANTUM:DLT8000:JF90908606 drive3: QUANTUM:DLT8000:JF90413627 drive4: QUANTUM:DLT8000:JF90909085 The lock names consist of: Logical Device Name Drive type Model Serial Number http://education.hp. L.com U1610S B.00 7-37 2003 Hewlett-Packard Development Company. L.hp.Module 7 Logical Devices 7–18. U1610S B. The scan is considered to be a "hard scan" of the tape and is usually avoided when using libraries. http://education. The slide above shows how to access Library Management to perform scans of the library. the barcode scan will report the media label without having to load the any tapes into the drive.00 7-38 2003 Hewlett-Packard Development Company. especially if multiple slots are selected due to the amount of time that the operation may take. SLIDE: Library Scanning Library Scanning Student Notes Data Protector provides a Library Management interface that may be useful verifying library operations and checking library status.P. If the library is configured for barcode capability.com . Scan will actually load a tape and read the tape header. X=Im/Export. D=Drive.com U1610S B.00 *** Copyright (C) 1996 Hewlett-Packard Company *** License is restricted for use with licensed *** HP OpenView Data Protector products.00 7-39 2003 Hewlett-Packard Development Company. The uma utility may read from the shell standard output on Unix: Also notice the cleaning tape in slot 15. .hp.Module 7 Logical Devices Example: NOTE The output of the barcode scan is also available with the uma utility.P. /dev/dltrobot> stat Element Status (T=Transport. S=Storage): 0 T1 Empty "" "" 20 X1 1 D1 2 D2 31 S1 32 S2 33 S3 34 S4 35 S5 36 S6 37 S7 38 S8 39 S9 40 S10 41 S11 42 S12 43 S13 44 S14 45 S15 46 S16 47 S17 48 S18 49 S19 50 S20 51 S21 52 S22 53 S23 54 S24 55 S25 56 S26 57 S27 58 S28 /dev/dltrobot> Empty Empty Empty Full Full Full Full Full Full Full Full Full Full Full Full Full Full Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Full <EOD> "" "" "" "" "" "" "BE1130" "BE1121" "BE1122" "BE1123" "BE1124" "BE1125" "BE1126" "BE1127" "BE1128" "BE1129" "BE1120" "BE1131" "BE1132" "BE1133" "CLN903" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "BE1134" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" http://education.03. L. The CLN prefix for barcode labels is recognized by Data Protector to indicate a cleaning cartridge. # print stat | /opt/omni/lbin/uma -tty -barcode -ioctl /dev/dltrobot *** PROGRAM: UMA VERSION: HP OpenView Data Protector A. com . (this is a hard-scan) Load a tape from the Mail-Slot (supported on libraries that have such a feature enabled) Enter U1610S B. L.00 7-40 2003 Hewlett-Packard Development Company. slot or drive) will allow for the following operations: NOTE Some operations are only available for library devices.hp. Operation Scan Description Identify the tape label and format. http://education. Data Protector will recognize several common Unix tape formats.Module 7 Logical Devices 7–19. SLIDE: Library Slot Operations Library Slot Operations Student Notes Data Protector is able to perform many functions related to media management by selecting the Logical Device within the device and media context. Selecting the device (library.P. .hp.com U1610S B. Both enter and eject operations are available relative to the available mail-slot. Update the vaulting location of a specific tape Remove all protection from a tape. Within a single session Data Protector allows for the selection and then initialization of all (if desired) of the tapes within the library repository. Use with caution. as this allows a tape to be overwritten! Format Import Export Change Location Recycle List Cartridge Memory Allows access to the data stored in the LTO (Ultrium) cartridge memory. http://education. The use of the term “bulk” in this context means multiple slots/tapes simultaneously or sequentially from a single select operation.00 7-41 2003 Hewlett-Packard Development Company. Remove an unprotected tape from the media management database. L. Data Protector is also able to eject multiple tapes for library devices that support the mailslot feature. Read the header and catalog information from a tape to register it into the media management database. see the reporting/ notification or media management sections of this course manual. The Media Session Manager will load and unload tapes as needed to perform the requested task.P.Module 7 Logical Devices Eject Eject a tape to the Mail-Slot (supported on libraries that have such a feature). Initialize a tape into a media pool. Can be automated for bulk-eject. Bulk Operations Data Protector allows for “bulk” media processing tasks to be performed in accordance with the general capabilities of the individual tape library. which is called each time the media agent needs to load or unload a medium from a cartridge. slot. The external script converts the commands to the native ones required by the device and executes them.com . parsing it for all necessary information to complete the required action. Both commands are invoked through the same external script. which must be capable of parsing predefined options and parameters.00 7-42 2003 Hewlett-Packard Development Company. the Data Protector media agent will call the external script. or a positive integer in case of an unsuccessful operation. flip. The script should perform the action and return an exit code of zero if the operation was successful. OmniBack sends: drive.Module 7 Logical Devices 7–20. and unload commands to the external script. L. the Data Protector media agent uses only two operations: medium load and medium unload.hp. Student Notes This device type is designed to allow for simple and efficient support of non-standard autochanger devices that do not work with the standard SCSI pass-through driver. The idea is to locate the execution of device-specific commands in an external script or program. At runtime. but also powerful and flexible enough to deal with a large variety of autochanger devices. To keep this mechanism as simple as possible. load. SLIDE: External Control External Control A mechanism for controlling devices that do not support the SCSI pass-through driver. U1610S B.P. http://education. . the external scripts should detect an unloaded magazine and load it transparently to the media agent.. <Drive #> <Slot #> Caution! The external script runs with root permissions.com U1610S B.. . Example of an External Control Script # # # # # # # Usage: script [-load]|[-unload]|.. If the autochanger has been used before and left in an inconsistent state. the load/unload operations will probably fail and abort the media agent. If the specific autochanger supports magazine loading. -load -unload -slot -drive -flip load cartridge unload cartridge number of the slot (0. L.1..) number of the drive (0.. therefore the security of this script is very important.. any messages read from its stdout will be picked up by the media agent and passed to the controlling session manager as error messages at level minor.1.Module 7 Logical Devices During the execution of the script.if device has two sides (for MO devices) let num=0 let flip=0 for arg in $* do TAB[${num}]=${arg} let num=${num}+1 done http://education. The media agent launches the external script.. The media agent assumes that the magazine is loaded and does not attempt to preload it at startup or unload it at shutdown. Some autochangers have removable cartridge magazines that can be loaded and unloaded under software control. therefore.) use b side .. The script should be able to handle the commands: Drive Slot flip load unload The media agent assumes that the autochanger is online and reset to an operational state before it is used. it runs on the system on which the Logical Device is configured.hp. The media agent does not issue a special reset or initialize command for this purpose.00 7-43 2003 Hewlett-Packard Development Company. The external script should catch this situation and reinitialize the autochanger to a default operational state.P. http://education.hp. L.P.Module 7 Logical Devices let i=0 while [ ${i} -lt ${num} ] do if [ ${TAB[${i}]} = "-slot" ] then let slot=TAB[${i}+1]+1 fi if [ ${TAB[${i}]} = "-drive" ] then let drive=TAB[${i}+1] fi if [ ${TAB[${i}]} = "-load" ] then let load=1 fi if [ ${TAB[${i}]} = "-unload" ] then let load=0 fi if [ ${TAB[${i}]} = "-flip" ] then let flip=1 fi let i=${i}+1 done if [ ${load} -eq 1 ] then /usr/omni/bin/HTC4 insert $slot exit $? else /usr/omni/bin/HTC4 eject exit $? fi U1610S B.00 7-44 2003 Hewlett-Packard Development Company.com . P. . In order to use these devices with Data Protector. The special integration modules also must be installed on the client systems that are connected to the library. SLIDE: GRAU and StorageTek Libraries GRAU and StorageTek Libraries • Large silos controlled by DAS/ACSLS software • Requires unlimited slot library license.com U1610S B. Data Protector passes commands to this system to perform media requests. the additional Unlimited Slot Library License must be purchased.00 7-45 2003 Hewlett-Packard Development Company. http://education. the GRAU DAS Integration Module must be installed on the Data Protector client systems that are attached to the GRAU.hp. These libraries are controlled by DAS software running on a separate system. GRAU DAS Library These large silo libraries are made by the GRAU Company and used in mainframe environments. • Integration modules installed on client systems Student Notes These large libraries are typically seen in mainframe environments and are controlled by a dedicated system running either DAS or ACS software. L.Module 7 Logical Devices 7–21. Before this type of library can be configured in Data Protector. the StorageTek ACS Integration module must be installed on the Data Protector client systems that are attached to the StorageTek.com . U1610S B.P. Data Protector passes commands to this system to perform media requests.hp. These libraries are controlled by ACS software running on a separate system.Module 7 Logical Devices StorageTek ACS Library These large silo libraries are made by the StorageTek Company and are used in mainframe environments. L. Before this type of library can be configured in Data Protector.00 7-46 2003 Hewlett-Packard Development Company. http://education. 00 7-47 2003 Hewlett-Packard Development Company. . What command can be used to get a listing of all the logical devices in your cell? http://education. Review Questions 1. What Data Protector device type would you use to configure a single DLT drive? 2.P. L. Describe the purpose of “Scanning” media? 7. What HP-UX driver does Data Protector use to control the robotics of library devices? HP-UX? Windows? 4.Module 7 Logical Devices 7–22. What Data Protector utility can be used to check communication with a library device before you configure it as a Logical Device? 3. What is the purpose of the advanced option “Concurrency”? 5.com U1610S B.hp. What is the purpose of the “Mount Prompt Script”? 6. What is the difference between a “scan” and a “barcode scan”? 8. True/False? 12. The “Drive Index” is related to the SCSI address of the drive.P. when? U1610S B. What command can be used to create and modify logical devices? 10. L. Is it possible to have more than one logical device that maps onto the same physical device? 13.com . why would you create more than one logical device for a single physical device? 14. What is the purpose of the Lock Name advanced option? Is it ever required by Data Protector? If so.Module 7 Logical Devices 9. http://education.00 7-48 2003 Hewlett-Packard Development Company.hp. If you were able to. What command can be used to perform a “scan” of the media in a device? 11. and post execution scripts.hp.Module 8 — Backup Objectives Upon completion of this module. L.00 8-1 2003 Hewlett-Packard Development Company. Create an automated environment with pre.com U1610S B. Understand the backup processing flow http://education. Adjust all of the options that control the execution of a backup job.P. you will be able to do the following: • • • • Create and Generate Backup Specifications using the GUI and command line. . No other information is required. it becomes a backup specification. SLIDE: Performing Backups Performing Backups Data Protector provides four methods of performing backups: • Interactive backup via the GUI • Predefined backup specification via the GUI • Predefined backup specification via the scheduler • Command-line interface via the omnib command Student Notes Data Protector provides several methods of performing backups. The method to use depends on the flexibility required. This definition may have been created specifically via the GUI for future use. http://education.com . as all the information is contained in the backup specification. U1610S B. L. the user simply selects the backup specification required. a prompt is displayed asking if the backup should be saved. the backup definition is lost. The backup is then executed.00 8-2 2003 Hewlett-Packard Development Company. media.hp. otherwise. and the devices. and options to use.P. The location for the saved files is <OMNICONFIG>/datalists. When the user attempts to exit the backup screen. If the backup is saved. or may be a previously saved interactive backup.Module 8 Backup 8–1. the GUI is used to define exactly what to back up. • Predefined Backup Specification via the GUI A backup specification is a complete definition of a backup saved in a file. • Interactive Backups via the GUI Using this method. and executes it via a menu item. To execute this type of backup. .. 1 Failed Disk Agents ..... 0 Aborted Disk Agents ...com U1610S B. • Command Line Interface via the omnib command The omnib command can be used to start a backup from the command line................. 1 ======================================== Mbytes Total ..Module 8 Backup • Predefined Backup Specification via the Data Protector Scheduler Backup specifications can also be scheduled.... [Normal] From: VBDA@na168w2 "practice-2" Time: 04/20/02 14:44:43 COMPLETED Disk Agent for na168w2:/stand "practice-2"... and frequency... 0 ---------------------------------------Disk Agents Total .....hp...... which allows the user to specify that the backup is to run at a predefined date......... 1 Disk Agent Errors Total .......... 10 Mb Used Media Total ..P. 1 Failed Media Agents . 0 ---------------------------------------Media Agents Total ....... 1 ======================================== Completed Media Agents ... Use omnib and pass all required backup options....... 0 Aborted Media Agents .... Example using omnib with an existing backup specification datalist: # omnib -datalist mydatalist [Normal] From: BMA@na168w2 "dds-1" Time: 04/20/02 14:44:35 STARTING Medium Agent "dds-1" [Normal] From: BMA@na168w2 "dds-1" Time: 04/20/02 14:44:35 /dev/rmt/c1t0d0BEST Initializing new medium: "Default File_8" [Normal] From: VBDA@na168w2 "practice-2" Time: 04/20/02 14:44:41 STARTING Disk Agent for na168w2:/stand "practice-2". time.... There are two methods: Use omnib to execute a previously saved backup specification.........00 ---------------------------------------Completed Disk Agents .. L....00 8-3 2003 Hewlett-Packard Development Company.... 0 Time: 04/20/02 14:44:44 http://education. [Normal] From: BMA@na168w2 "dds-1" Time: 04/20/02 14:44:43 COMPLETED Medium Agent "dds-1" [Normal] From: BSM@na168w2 "mydatalist" Backup Statistics: Session Queuing Time (hours) 0....... .. . disconnect to keep the session running without further interaction: # omnib -filesystem na168w2:/tmp "practice-command" -device dlt_drive1 [Normal] From: BMA@na168w2 "dlt_drive1" Time: 04/20/02 14:43:07 STARTING Medium Agent "dlt_drive1" [Normal] From: BMA@na168w2 "dlt_drive1" Time: 04/20/02 14:43:08 Loading medium from slot 1 to device /dev/rmt/c1t4d0BEST ^C Entering command mode. OMNIB Command Mode ==================== Available are the following commands Abort .com .cancels the device and all Disk Agents working with the specified device Mount <device> .disconnects from the Session Manager Continue .00 8-4 2003 Hewlett-Packard Development Company..aborts the session and all related actions Cancel <device> .Module 8 Backup Example: using omnib to backup a filesystem.P..informs the Session Manager that a mount request has been satisfied Disconnect . http://education.cancels command mode and enters monitor mode Command:>disconnect # session stays running to completion U1610S B. notice the interrupt takes you into command mode for the session where interaction is possible.hp. L. SAP database and logs • Oracle 7 . Data Protector provides the following predefined backup specification types: Datalist This is the most commonly used type of backup specification. . SLIDE: Backup Specification Types Backup Specification Types Datalist: • DP .Oracle 7 databases and logs • Oracle 8 .com U1610S B.00 8-5 2003 Hewlett-Packard Development Company.Informix databases and logs • Sybase . and Novell systems • Windows Registry (configuration) • Data Protector Internal Database • Rawdisk sections http://education.Sybase databases and logs • MS SQL . L.Microsoft Exchange server Student Notes Special types of backup specifications must be used to suit the particular type of source data being backed up (objects).P.Microsoft SQL databases and logs • MS Exchange .hp. It is used to backup: • General file systems (drives) of UNIX.General host and file system Barlist: • SAP .Oracle 8 databases and logs • Informix . Windows.Module 8 Backup 8–2. These must be configured via the NT GUI. including log files Informix An Informix database instance. NOTE The MS backup specifications cannot be configured via the HP-UX GUI. including log files MS SQL An MS SQL database instance. online or offline. L.00 8-6 2003 Hewlett-Packard Development Company. U1610S B.P. online or offline. including log files Sybase A Sybase database instance. online or offline. including log files Oracle 8/9 An Oracle database instance.Module 8 Backup Barlist • • • • • • SAP/R3 An SAP database instance.com . online or offline.hp. including log files MS Exchange A Microsoft Exchange mail server. http://education. online or offline. HFS. VFAT. A backup using this object type backs up the source data.0. http://education. SLIDE: The Backup Specification (datalist) The Backup Specification (datalist) A Backup Specification (datalist) may be used to backup the following object types: • • • • Filesystem (UNIX/Windows/Netware) Hosts (expanded into file systems). NOTE See the Data Protector Administrator’s Guide for details about each of the file systems and some specific details or special considerations for each type. Data Protector provides the following object types: • file system This type of object is used for data residing in the operating system file systems. NTFS 5.Module 8 Backup 8–3. When backed up. FAT16. FAT32. NTFS. NFS. . such as a host backup mixed with filesystem backups from different systems.com U1610S B. file by file. the source data is classified according to the specific object type required.00 8-7 2003 Hewlett-Packard Development Company. Examples: /usr (Unix file system) C: (windows file system) Data Protector supports most common file system types including: Vxfs. rawdisk the DP internal database Student Notes The source data specified within a backup specification is referred to as Objects.hp. others.P. L. Backup specifications may contain different object types. UFS. • rawdisk This type of object is used for data backed up from rawdisk sections (image copy).Module 8 Backup • host Also called Disk Discovery. • winfs Data originating from Windows NT/2000. Registry data is also stored using this object type and is called CONFIGURATION. 98 and XP drives. http://education. This backup will be discussed in more detail in the Database chapter of this manual. this type of object is used for data residing in file systems. A backup using this object type backs up the source data. L.00 8-8 2003 Hewlett-Packard Development Company. OmniStorage is HP’s hierarchical storage management solution. file by file. • netware Data originating from Novell NetWare server drives. ME. File systems such as NFS cannot be backed up using this object type. There are many considerations for backing up and restoring the CONFIGURATION. • omnidb Backups of the Data Protector internal database have this special object type.com . This ensures that the database is backed up in a consistent state.hp. For example raw logical volumes on HP-UX systems. they must be included as file system objects. • vbfs Data originating from HP OpenView OmniStorage MFS (Migrating File Systems). It is different from the file system object in that the specific objects to be backed up are determined dynamically at run time.P. /dev/vg01/rlvol1 or /dev/rdsk/c0t6d0. U1610S B. Data Protector uses a special integration to backup OmniStorage data. see the Data Protector Administrator’s Guide for more specific details. Data Protector provides options at essentially four different levels: • Template Level Options associated with a template will set the initial options for the backup. L.com U1610S B.P. • Backup Specification Level Options available at this level are common to the whole backup session. . SLIDE: Backup Specification Contents Backup Specification Contents Backup Specification Defaults Objects Devices Backup Spec Options Template Options Object Options Device Options Student Notes Data Protector provides a rich set of options that can be used to define all the characteristics that the administrator wants the backup job and stored data to have.hp. These “defaults” may be altered for each of the following three additional levels. including the objects and device specifications that are defined within the backup specification.00 8-9 2003 Hewlett-Packard Development Company.Module 8 Backup 8–4. http://education. P. http://education. A backup specification can contain many device definitions. Each object can have different options. U1610S B.hp.Module 8 Backup • Object Level Options at object level are specific to that particular object. L.) • Device Level Options here are specific to the particular logical device. A backup specification can contain one or many separate objects. Typically.00 8-10 2003 Hewlett-Packard Development Company. objects within a backup specification tend to have the same or similar options. Each one can have different options.com . (Defaults are inherited from templates. Module 8 Backup 8–5. http://education. Load balance was previously explained. SLIDE: Backup Specification Sequence Backup Specification Sequence Choose: Choose: •• Load/non-load Load/non-loadbalance balance •• Source Source •• Destination Destination •• Backup Backupspecification specificationadvanced advancedoptions options •• Filesystem advanced options Filesystem advanced options •• Schedule Schedule •• Backup Backupobject object summary summary(properties/options) (properties/options) Student Notes The list shown above illustrates the typical sequence (as guided by the GUI) used when defining a backup specification. L. so next will be the explanation for Source.P.com U1610S B. .hp. The next several pages will first explain and then illustrate each of the choices shown above.00 8-11 2003 Hewlett-Packard Development Company. com . or the Windows Notepad. Command Line Example-1: Create a datalist containing all of the file systems for a single host.00 8-12 2003 Hewlett-Packard Development Company. SLIDE: Creating Backup Specifications Creating Backup Specifications Choose a template for a set of default options Static or dynamic devices Use the command to create a file ••omnicreatedl omnicreatedl… … ••Edit EditASCII ASCIIfile filein inOMNICONFIG/datalists OMNICONFIG/datalists Student Notes Data Protector is able to generate backup specifications within the GUI. backup specification options and devices and their options may all be modified. L. objects and their options. Once the template is chosen. and then which template options to apply to the new specification. first by selecting an appropriate template.P. All generated specifications are stored in <OMNICONFIG>/datalists directory as text files.Module 8 Backup 8–6. for the host na168w2. the file produced will be host168w2. and are able to be edited with editors such as the Unix vi. http://education. and the logical device dlt_drive1: # omnicreatedl -datalist host168w2 -host na168w2 -device dlt_drive1 U1610S B.hp. Module 8 Backup Command Line Example-2: Create a datalist containing all of the file systems from two hosts.com U1610S B.P.hp. # omnicreatedl -datalist gencombo -host dlthost -host na168w2 -device dlt_drive1 \ NOTE See the man page called omnidatalist for details on the structure and syntax used within the file. . http://education. The datalist file produced by the command line compared to the one produced by the GUI may be structured differently when more than one host is included. the file produced will be <OMNICONFIG>/datalists/gencombo. L.00 8-13 2003 Hewlett-Packard Development Company. you will notice the callout indicating the on/off switch for its use.hp. This feature is designed to be used with multidrive tape libraries. If you refer back to the previous slide. Load balancing can also make a backup more robust. the creator of the backup specification does not need to worry about what objects are sent to each device. Using this method. objects are not targeted at a specific device. SLIDE: Load Balancing Load Balancing Enables dynamic allocation of devices to objects. rather at a pool of devices. Load balancing avoids the pitfalls of static device allocation by enabling dynamic device allocation. but will also work with stand-alone devices. as it is possible to define more backup devices in the backup than are actually required. With dynamic device allocation. Data Protector allocates the objects to a device when the device finishes backing up the previous object. http://education. If a device fails to start. L.Module 8 Backup 8–7.00 8-14 2003 Hewlett-Packard Development Company. The creator of the backup specification defines the minimum number of devices that must be available to successfully complete the backup.P. Objects Devices Student Notes One of the first choices you will have to make when creating a backup specification is the use of load balancing. the maximum number of devices is also defined. In addition.com . U1610S B. In some earlier versions of Data Protector. Data Protector will mark the drive as failed and another device will automatically be used in its place. this was known as Auxiliary Devices. however if three or more devices defined in the backup specification are available and needed. MAX=3 defines that one device is required to complete the backup successfully.hp. http://education.00 8-15 2003 Hewlett-Packard Development Company.com U1610S B. L. . then three (maximum) will be used.Module 8 Backup For example: A load balancing setting of MIN=1.P. U1610S B. This is not usually ideal for the best overall backup performance. it could still be in use and have objects pending to it while other devices have finished their objects and are sitting idle. The following factors need to be taken into account to get the best performance: • The number of objects sent to the device • The size of the objects • The speed of the device and its concurrency • How well the object data compresses • The order in which the objects are backed up If one device in the list has more or larger objects directed to it.com . SLIDE: Static Device Allocation Static Device Allocation Objects are pre-assigned to a particular device. This feature allows for the most control during backups.hp. Backup Specification System A Object System A Object System B Object System C Object System A Device System A Device System B Device System D Device Student Notes Static device allocation occurs load balance is disabled. such as the administrator. then each object defined in the backup specification is targeted at a specific logical device. http://education. The creator of the backup specification must make a decision as to which objects are sent to each device. or to different ones. but may improve performance by giving more control to someone that is very familiar with the data source. All objects can be targeted to the same device. L.Module 8 Backup 8–8.P.00 8-16 2003 Hewlett-Packard Development Company. ” Also. Data Protector will only start the number of media agents defined in the MAX parameter.” At run time. media agents are started for each logical device specified in the backup specification. in this case “2. the backup specification contains four objects and three logical devices. The third device. http://education. you will notice that the device field for each object that normally shows the name of the logical device the object is targeted at. System B Device.00 8-17 2003 Hewlett-Packard Development Company. The backup specification defines “2” as the maximum number of devices that can be used. The options for the backup specification include: “Load Balanced.” The media agents that are started depend on the order defined in the backup specification.com U1610S B. L. Min 1. that is to say they have an order within the object list. we can see a backup specification. it is System D and System A Device. In this example. Max 2. note that the backup objects are in a specific order.hp. .Module 8 Backup 8–9.P. When a backup specification is configured as load balanced. is not used. SLIDE: Load Balancing — Object Allocation Load Balancing — Object Allocation Backup specification System A Object System A Object Run time Concurrency 2 Concurrency 1 Options: Load Balanced Min 1 Max 2 System B Object System C Object System A Object System B Object System D Device System A Device System B Device Pending System A Object System C Object System D Device System A Device System B Device Unused (Max=2) Student Notes On the left. However. now shows “Load Balanced. as it is waiting for one of the devices to have a free concurrency slot. for example it is in use by another backup or restore session.00 8-18 2003 Hewlett-Packard Development Company. so no additional objects are started for the device.hp.Module 8 Backup If one of the devices as not available. The number of disk agents started is the combined concurrency values for the running devices. devices are constantly fed objects until the backup is complete. or it failed to start. In this way. The other System-A object has been allocated to System D device. it makes sense to use a common media pool for each device that is to be a part of a load balanced backup. the disk agents are started. In our example. Object to Device Assignment Objects to be backed up are selected in the following manner: • Objects that reside on the device host have a higher priority for the local device • Objects are scheduled so that the number of disk agents running per host is minimized • Objects are grouped together to satisfy the concurrency requirements of the device Data Protector first sends an object to its local tape drive rather than send it over the network to a drive on another system. http://education. as this device has a concurrency of two. The device concurrency is set to one. U1610S B. the first System-A object has been assigned to the System-A device.com . The device that finishes backing up one of the objects first will be the device that receives the System C object. in this case. along with the System B object. L. The System C object is in the pending state. then Data Protector can use the third device instead. The reason these two devices are used is that they are the first two devices in the list.P. Once the media agents have started. NOTE As the user does not know in advance what objects will be written to each device. the total is three. The coloring used for the check marks in front of the objects indicate whether the items were selected directly (blue) or indirectly (black)) because of another selection. or you may expand the host object and select file systems individually.hp. or non-load balanced wizard.Module 8 Backup 8–10. L.P. select “Tasks” form the bottom of the Scoping Pane. Proceed through the rest of the choices by using the Next button at the bottom of the Results Area. you may select the check box in front of a host to include the “host” object. SLIDE: Interactive Backup Specifications Interactive Backup Specificatios Load balanced Non-load balanced Check Mark Color: Blue = primary selection Cyan = partial Black = secondary selection Gray = partial Manually create a datalist Student Notes When defining objects interactively to be added to a backup specification. You will not be able to change the load balance selection later unless you edit the datalist file with a text editor. The lightened colors (green and gray) are used to indicate partial selections. http://education. Select either the load balanced. As you select objects to be backed up. you may use a “task wizard” to create the specification.com U1610S B. . Within the backup context of the GUI. There you will find the wizards.00 8-19 2003 Hewlett-Packard Development Company. This makes restoration of a complete system very simple. and sessionbased. While the flexibility of combining objects together is quite high. The backup is executed as a single session (a single job) comprised of many objects.00 8-20 2003 Hewlett-Packard Development Company. you may want to consider how you will restore data before you define your backups.com . but may U1610S B. SLIDE: Source Source primary Host object secondary secondary Filesystem objects primary Student Notes What to backup? Multiple object types/selections may be combined together within a single specification for backup. L. object-based.hp. With session-based restore. The choice of host object and file system object may also be mixed with different agent platforms.P.Module 8 Backup 8–11. Data Protector is able to restore all at once the objects from a single backup session. http://education. The backup session is stored in the Data Protector database and may be selected for restore. How to restore? Data Protector provides essentially two methods for data restore. applications and users that open files lock these files to prevent multiple simultaneous access to the same data. So a backup of the “root” file system will only contain the files and sub-directories that are part of the “/ “ mounted directory. The user files should be backed up while the users are not logged on to the system. http://education. Unix essentially has one large directory tree that contains mount point directories for all attached/active disk devices. you will only be backing up the data that resides on the logical volume (disk) mounted to the “/” directory. /opt. as empty. you may want to add the Data Protector Open File Backup extension for windows. These disk devices are commonly logical volumes. when the disk is unmounted.com U1610S B. . Warnings during backup Two very common situations will generate numerous warnings during backup. This product is available starting with Data Protector version 3.Module 8 Backup change the way that you will define your specifications for backup.00 8-21 2003 Hewlett-Packard Development Company. and back them up with the CONFIGURATION object. /var. A mount point directory is an empty directory. you may select to restore an entire object version. /tmp. With object restore.P. called “slash”) file system typically holds directories used as mount points for several other file systems. /stand. While users are logged in the files associated with their profile. /home. This is very common for spreadsheets and word processor files. There are likely to be many more in your environment. One is the backup of the root file system in Unix. Unix: root file system warnings The Unix root (/. If it is necessary to backup open files on Windows systems.5. Directories found in “/” that typically serve as mount points are /usr. L. the other is the backup attempt of open files in Windows. The warnings presented during the backup are due to Data Protector’s detection of the mount point directories.hp. that is how Data Protector will backup the directory. down to the file level. such as /dev/vg00/lvol3. These open/locked files are unable to be backed up by Data Protector. On HP-UX systems this is commonly an LVM disk. A warning for each one will be given. In the case of the registry files. as well as files in the system registry are also opened and locked. you will want to exclude them from the file system that contains them. When you attempt to backup the root file system. NOTE See the Data Protector Administrator’s Guide for a list of files to exclude. Windows: file open warnings In the Windows file system. or any subset of it. http://education. The CRC check is an enhanced checksum function that lets you confirm whether or not data has been written correctly to the medium. NOTE CRC data can be rechecked using the Data Protector verify function in the Media Manager. The following options are available: • CRC Check (default is per device definition. SLIDE: Destination Destination Select library to use all drives Use drive default media pool Student Notes The destination for a backup may be a library or individually selected logical devices. and is usually off) Set this option to ON to have Data Protector calculate the Cyclical Redundancy Check (CRC) when a backup is run.com . each device in the backup specification can have different options. L.Module 8 Backup 8–12. You may override the device default properties for each backup without affecting the device defaults saved within the Media Management Database.P. Each device selected may have modifications made to its default properties. Therefore. Device Properties Properties are modified on a per device basis.hp. or with the Data Protector command: omnimver U1610S B.00 8-22 2003 Hewlett-Packard Development Company. This causes additional processing and tape writes to occur for each backup. • Media Pool (default is as per the logical device definition) This option selects the media pool from which the device should source media.P. The sample above indicates “no media pool selected. the order of media in the list may not be what is required for the next backup. or enter and eject media from a library and you want to avoid mount requests during backup. a physical scan will take place. no specific pool requested for this backup. http://education. Pre-allocation lists can be inflexible and confusing.Module 8 Backup • Concurrency (default is as per device definition) Concurrency allows more than one Disk Agent (up to five) to write to one backup device concurrently.hp. NOTE If the library has been defined to support barcode reading. NOTE Pre-allocation should be used only with the strict media allocation policy and on limited basis. Use of this feature will require daily changes to the datalists. L. then a barcode scan takes place. If a backup does not take place. • Pre-Allocation List (default none) The pre-alloc list requests that a subset of the media in the media pool is to be selected for this backup. It is possible to request in-appropriate media (full/protected). This helps Data Protector keep the device streaming when it can accept data faster than a Disk Agent can send it. It also specifies the order in which the media will be used. • Rescan (Library Repository) (default off) If this option is ON.00 8-23 2003 Hewlett-Packard Development Company. Choose Add to open a dialog box in which you can add specific media (from the selected media pool) to the pre-alloc list. Data Protector will updates library repository information before starting your backup. Data Protector only checks this list at run-time. You must select to override the default media pool if you are to choose specific media. otherwise. . This is useful when you manually change media order.” which is interpreted to mean use the device default pool.com U1610S B. http://education.com . This pre-exec may be executed on any system within the Data Protector cell. Such a script can do the necessary application shutdown that must be performed for a backup to be consistent. including the objects and devices contained within it. (only the relative path from OMNIHOME/lbin is necessary for Unix.Module 8 Backup 8–13. but must reside within the agent directory tree. The following options are available for a backup specification: • Description Enter a meaningful description of your backup specification.00 8-24 2003 Hewlett-Packard Development Company. Example: “Full Backup of Stock.hp. L.sh U1610S B. Aitkin and Waterman Systems.” • Pre-exec Here you can specify a script file that will be executed before the backup starts. and OMNIHOME/bin for Windows) Example: shutdown_application. SLIDE: Backup Specification Options Backup Specification Options Non-modifiable unless disk image added manually Student Notes Backup specification options encompass the whole backup session.P. . This post-exec may be executed on any system within the Data Protector cell. the user must have the necessary access rights to the data that the objects describe. Clustering Options The options for the backup specification fall into two categories.hp. • Automatic Session Restart − Don't restart backups at failover: (default) If the Cell Manager is configured within a MC/ServiceGuard package and fails over to an alternate node during a backup.com Ownership is not truly a backup specification option. We will discuss this option in detail later in this module. Completed file system objects are not restarted. so that they are available to the users.P. Data Protector effectively executes the backup as if being run by the backup owner.e.com U1610S B. Features that are designed to work within the MC/ServiceGuard and Microsoft Cluster environments. it affects the backup specification and the objects that it contains. http://education. Ownership also has an impact on who can restore data. L. Data Protector Options and Clustering.Module 8 Backup • Post-exec The partner to pre-exec. here you can specify a script file that will be executed after the backup has completed. Ownership is specified by three parameters. i.hp. i. Otherwise.sh We will discuss exec scripts in more detail later in this module. • Ownership (default is the creator of the backup specification) Ownership defines the particular system user who owns the backup specification and the objects within it. Such a script can do the necessary application startups that must be performed following a backup. However. as follows: User name. • Reconnect Broken Sessions (default is off) This option can be used to increase the robustness of a backup when it is susceptible to communication breakdowns due to unstable networks. i.uksr.e. the backup will fail. oracle Group name / Domain name.e. the backup job will not be automatically restarted.00 8-25 2003 Hewlett-Packard Development Company. but must reside within the same directory tree as the pre-exec scripts. Therefore. − Restart backup of failed objects: Restart only the failed file system objects that are part of a backup job that was running when the Cell Manager was failed with MC/ServiceGuard. kryton. Example: startup_application. dba Host name. U1610S B. L. • Check Elapsed Time − − • Abort if less than Abort if more than n minutes: Prevents newly started backups from being restarted.hp. Completed objects are restarted as well as failed objects. http://education. and becomes the application ID. n minutes: Prevents long running jobs from being restarted. The ID used must be numeric.Module 8 Backup − Restart backup of all objects: Restart the entire backup of all objects that are part of a backup job that was running while a Cell Manager was failed with MC/ServiceGuard.P. Check Against Abort ID Check the session against the assigned Abort ID for verification.00 8-26 2003 Hewlett-Packard Development Company. This logical ID is assigned to the backup job while it is running.com . NOTE See the man page for the omniclus command for more details and examples. hp. Object Level is always executed on the system where the object resides. before a system can be backed up. http://education.and Post. L.and Post-exec facilities can perform the shutdown and startup from within the backup itself. the administrator must secure the system by shutting down the various applications and databases that the system is running. making them available again to the users. such as database shutdown and start up. After the backup is complete. This is used to avoid execution hangs. Pre/post execution scripts must complete (or send output) within 15 minutes or Data Protector will abort the backup. OmniBack provides two levels of pre and post execution: • Backup Specification Level • Object Level Backup Specification Level can be executed on any system in the cell.00 8-27 2003 Hewlett-Packard Development Company. .P. Data Protector provides two levels of pre/post-exec. BSM Backup Spec Pre-exec Object Pre-exec System A Object Object Post-exec Object Pre-exec System B Object Object Post-exec Object Pre-exec DA System C Object Object Post-exec Backup Spec Post-exec Student Notes Typically. the first is at the backup specification level.Module 8 Backup 8–14. SLIDE: Pre.Execution Allows commands or scripts to be run before and after the backup. Data Protector through its Pre. This timeout value is adjustable by modify the ScriptOutputTimeout parameter in the <OMNICONFIG>/options/global file. the administrator restarts the applications and databases. and the other is at the object level.com U1610S B.and Post-Execution Pre. therefore. To achieve this the scripts that contain such daemon startups may use the UNIX at command to detach the script from the pre-exec script: /usr/bin/at -f script_file.com .00 8-28 2003 Hewlett-Packard Development Company.P. the pre/post execs are run before any objects are backed up. and once for each object to which the host is expanded. and the post-exec will run after the object is backed up.and post-exec command and make it visible in your message window (monitor). you cannot predict the order in which objects will complete. Object Level The level is available for every object within the backup specification. U1610S B. L.sh now or with some delay /usr/bin/at -f script_file.and post-exec commands be scripts terminate with exit(0) when executed successfully. CAUTION When using combined concurrency levels greater than one (1).sh now + 3 minutes To check the error output of your pre. To achieve this on a UNIX system. The administrator may designate any client system to execute the pre/post exec scripts for the backup specification only. the pre-exec runs before any of the objects within the backup specification are backed up. always redirect stderr to stdout. which rely on particular object completion orders. NOTE Tasks that never terminate. The pre-exec will run before the actual object is backed up. CAUTION When using Host objects. must be detached from the scripts in order to avoid time-outs. such as startup of applications or daemons. use output redirection: unix_command 2>&1 & Any non-zero return value from the pre-execution command will result in the backup or backup object being aborted. The scripts are executed on the system where the disk agent retrieves the object data from. The post-exec runs after all the objects have been backed up.hp. We suggest that the pre.Module 8 Backup Backup Specification Level At this level. http://education. do not put commands at the object level. If the script fails. . At this stage.Exec Script Failures How Failures Affect the Flow of the Backup Fail Fail Object Backup Fail Fail 1 2 Fail Object Pre-exec 3 4 5 Backup Spec Pre-exec Object Post-exec Backup Spec Post-exec BDACC Set SMEXIT Set Student Notes The pre/post-exec feature of Data Protector is extremely useful. the BDACC environment variable is set to reflect the status of the object. the object is backed up.hp. it is very important that you understand what effect errors and failures of the scripts have on the backup. before it goes to step 4. However. http://education.and Post-Exec Script Failures Pre. the pre-exec script for the first object is run. However. At this stage. it jumps to step 3. If the script completes successfully (exit code 0). The slide shows the effects of failures at different levels: 1. L.P.Module 8 Backup 8–15. If the backup of the object succeeds or fails. it moves on to step 2. 2. and it jumps straight to step 5. 3. it jumps to step 4. then the backup does not take place. The backup specification level.and Post. SLIDE: Pre.com U1610S B.00 8-29 2003 Hewlett-Packard Development Company. pre-exec script is run. if it works successfully. before it goes to step 5. environmental malfunction Program failed. post-exec script is run. following various failures (pre/post with non-zero return values): Pre 0 0 0 1 1 Post 0 0 1 0 1 Backup started started started Not started Not started DA-Status completed failed Session Status completed failed completed completed with errors failed failed The BDACC variable Data Protector sets the shell variable. At this stage. The variable can be used to check the status of the previous single object backup. successful termination Program failed. The table below shows the various values: BDACC Value 0 1 2 3 4 Status Normal. http://education. the SMEXIT environment variable is set to reflect the status of the entire backup session. the object post-exec script is run. U1610S B.P.com . L. the backup specification. reason unknown. 5. if the script succeeds or fails. BDACC.hp. it jumps to step 5. The following table shows the resulting backup session status that is seen in the monitor window.00 8-30 2003 Hewlett-Packard Development Company. user error Program failed. then the backup session completes. internal malfunction Program failed. At this stage. However. for the object post-execution scripts to contain the completion code for the backup agent.Module 8 Backup 4. Session was aborted. . Incr.group. All disk agents failed.com U1610S B.hp. The backup exit code status. your post-exec script may read the SESSIONID variable and use it as a parameter to the omnidb command. The table below shows the various values: SMEXIT Value 0 10 11 12 13 Status Completed. SMEXIT. The list could then be emailed to the operator: omnidb –session $SESSIONID –media | mailx –s medialist
[email protected]) Is backup in Preview mode? (0 or 1) Is backup a restarted backup? (0 or 1) The session-id of the backup. it will have a session-key.P. If the backup fails immediately.com Backup Specification Pre/Post-exec Variables Variable MODE OWNER PREVIEW RESTARTED SESSIONID SESSIONKEY Pre x x x x x x Post x x x x x x Meaning Backup mode (Full. Incr1-0) Backup Specification Owner. More Data Protector Environment Variables Data Protector sets various session variables that can be interrogated in pre or post exec scripts for conditional processing and reporting of session data. (owner.Module 8 Backup The SMEXIT variable Data Protector sets the shell variable. The variable can be used to check the status of the backup session. to find out what media was used by the session. L. Completed with file errors. SMEXIT x http://education. The session-key (session keys are a sort of temporary session ID.00 8-31 2003 Hewlett-Packard Development Company. but not a session ID). One or more disk agents failed. for the backup specification level postexecution script. For example. some daemon processes. In this case.00 8-32 2003 Hewlett-Packard Development Company. http://education.Module 8 Backup TIP A Pre or Post.. a user can use the detach command.hp. etc.). database server process (dbstart). This command is officially unsupported.c file. The source of the detach command is provided in the detach. L.com .] U1610S B. This is the case if the new process runs in the background and does not exit (for example.P..exec script may hang because it did not close all file descriptors before forking the new process. For example: /opt/omni/bin/utilns/detach pre_script [arguments. where one further attempt is made to communicate with the host.Module 8 Backup 8–16. This protocol has a performance overhead. the BSM and agents will both try to re-establish communication. These settings can be changed by placing the variables in an OMNIHOME/. If communication between BSM and an If communication between BSM and anagent agentfails. The agent will try for OB2RECONNECT_RETRY seconds to re-establish the TCP/IP connection and will then wait for another OB2RECONNECT_ACK seconds to get the acknowledgement from the server. a more advanced protocol is used for agent communication and data transfer. The default for the OB2RECONNECT_ACK variable is 10 minutes.hp. It can be used when backups are taking place over networks that are susceptible to interruptions. If either one of these time parameters times-out.P. and therefore. such as WANs. protocol. SLIDE: Reconnect Broken Sessions Reconnect Broken Sessions Instructs InstructsData DataProtector Protectorto touse usea amore morerobust robustprotocol.omnirc file on all systems involved. L. and for the OB2RECONNECT_RETRY the default is 20 minutes. If the BSM is unable to contact the host to start the agents for the first time. http://education. When this option is enabled. Network Backup Disk Agent TCP/IP Cell Manager TCP/IP Scheduler Session Manager Media Agent Session Manager TCP/IP Student Notes The “reconnect broken session” backup specification option can be used to increase the robustness of the backup. the object is rescheduled to the end of the backup specification. . fails. the object will abort.00 8-33 2003 Hewlett-Packard Development Company. should be used only if the link reliability is a problem. BSM and the agent attempt to re-establish communication.the the BSM and the agent attempt to re-establish communication. If the BSM loses communication with the disk or media agents.com U1610S B. L. http://education.com .P.Module 8 Backup NOTE A broken connection between agent processes cannot be reconnected (media agent to disk agent).hp. U1610S B.00 8-34 2003 Hewlett-Packard Development Company. day) Data Protector will protect the session data on tape from overwrite until the protection expires. . The only general option is the session protection.Module 8 Backup 8–17.hp. Data Protector provides a template that can http://education. Each object can have different options. L.P. month. The default is permanent and may be changed to: None Days <number> Weeks <number> Until <yyyy> <mm> <dd> (year. SLIDE: File System Options File System Options Student Notes Each object to be backed up within Data Protector may have a unique set of options to control how the data is backed up and protected within the Data Protector database. Options at the object level are specific to that particular object. A backup specification may contain one or many separate objects.com U1610S B. objects within a backup specification tend to have the same or similar options. Rather than setting these options individually for each object.00 8-35 2003 Hewlett-Packard Development Company. Typically. where you can specify a script file that will be executed after the backup of the object has completed. The following settings are available: − Warning − Minor − Major − Critical Set the level according to the minimum severity of messages that is required. U1610S B. • Post-exec The partner to pre-exec. The default value is the same as for data protection. http://education. • Pre-exec Pre-exec is used to specify a script file that will be executed before the backup of the object starts. This concept will be explored further in the database chapter of this course manual. Newly added objects then inherit the new default settings provided by the template. • Catalog Protection (default same as data) This option enables you to set periods of protection for information about backed up objects in the Data Protector database. Object options are divided into two categories. L.P. • Reporting Level (default is Warning) This option defines the level of message detail that is reported during the backup session. Messages less than the specified severity are suppressed from the session records in the database. They must be located within the OMNIHOME/lbin directory tree if a relative path is used.00 8-36 2003 Hewlett-Packard Development Company. they may be located anywhere if an absolute path is used. Backup session messages are categorized according to the severity of the message. NOTE Object level pre/post-exec scripts will be run on the system that the object resides on. You may want to expire the catalog but keep the tape protected if the tape is stored off-site for extended periods of time.com . Example: Major – suppresses Warning and Minor messages. options and other: Advanced Options • Public (private is the default) This option defines protection level for the session within the database.hp. Data Protector will only allow restore to be performed by the session owner unless public is selected.Module 8 Backup be modified in advance of adding objects to the specification. and you want to keep your Data Protector database smaller. Users that have restore capability may be able to see and restore sessions that are marked as public. CAUTION Software compression seriously affects the performance of the backup. Typically. − Days Information in the Data Protector database is retained for the number of days specified.00 8-37 2003 Hewlett-Packard Development Company. The specific procedure for this is covered in the Data Protector Administrator’s Guide. as it typically consumes large amounts of CPU resources. which is far more efficient than software compression in most cases.P. you can substitute your own internal data encoding algorithms for greater security. − − Weeks Information in the Data Protector database is retained for the number of weeks specified.com U1610S B. month. Data Protector offers a simple built-in XOR algorithm. The data is compressed on the source system before it is sent over the network.hp. It typically consumes large amounts of CPU resources. Same As Data Protection Information about the object is protected from being overwritten as long as the data is protected. this option is not used. TIP • Encode (default is off) Data Protector lets you encode file system and disk image data so that it becomes unreadable. Software compression can be useful when backing up data over a WAN. thus reducing network traffic. . Other Options • Software compression (default is off) Use software compression on the object before the object is sent to the media agent. L.Module 8 Backup The following values are available: − Until Information in the Data Protector database is retained until a specified date. Compile the dataencoding module into a library. implemented in a shared "C" program library. You enter the year. Do this by writing your own data-encoding module. http://education. and substitute it for the default Data Protector library. and day. CAUTION Encoding (encryption) may have a performance impact on the backup. Since Data Protector provides the API used by the Disk Agent to interface with the data-encoding module. Data is encoded before it is transferred over the to the media agent. as most modern tape devices perform hardware compression. Protection for the information will cease at noon of the entered day. Data may be restored regardless of the level chosen.P. If set to ON. each file in the specified fileset is opened.hp. • Lock files during Backup (default is off) This option defines how files are handled during a backup session. Data Protector traverses the directory trees twice for the backup. locked. This will prevent hard links from being recreated during the restore process. size. etc are stored in the database (they are on tape only). Data Protector traverses the file system tree only once during the backup. and allows Data Protector to fast position on the tape when restoring a specific file. U1610S B. When you set this option to ON. • Do not preserve access time attributes (default is off) Whenever a file is opened (read. the access time attributes remain as they were before backup (they are reset to their original values). When this option is set to OFF. every filename that was previously a link is restored as a file. NOTE Use this option when there are no hard links in your file system. the access time values are changed to the moment of backup. once to detect the hard links. This causes Data Protector to back up hard links as regular files. such as megabytes per hour for each object. All detail about backed up files and directories are logged to the database. This allows Data Protector to estimate the size of the backup as well as detect the links. this information may take a lot of space if there are many files. http://education.). thus speeding up the backup process. When you back up hard links as links. Data Protector cannot estimate the size of the backup or display the percentage of the backup finished. However. The logging level also affects the amount of detail available to the restore browser as well as the backup performance. • Backup POSIX hard links as files (default is off) This option will disable the detection of hard links within the file system. and then to backup the data. This represents a savings of about 70% over the log all option. Data Protector will back up the entire file contents for each hard link.Module 8 Backup • Display statistical info (default is off) Display backup statistics. The logging option potentially reduces the amount of data stored in the database. This complete information allows you to search for backed up files. and read. the access time of the file is changed.00 8-38 2003 Hewlett-Packard Development Company.com . A hard link is a directory entry that actually points to a physical file. etc. files are locked during the backup session. − Log File Details on directories and only file name information are stored in the database. During backup. No file version attributes such as modification time. but will take longer to execute. • Logging (default is log all) Data Protector provides four levels of detail on files and directories stored in the Data Protector database. L. locked. owner. If set to ON. These statistics are displayed in the message window and stored as session messages in the database. When this option is set to ON. preventing the files from being modified during the backup. − Log All This is the default option. protection. or within the specified size Range in KB • Backup Files of Size (default all sizes) Use this menu button to specify the size of files to be backed up. You would use this if you expect to restore an entire file system object and not select individual files and directories by name. • Backup Files of Size (default all sizes) Use this menu button to specify the size of files to be backed up. files Bigger than. • Number of retries (default is 0) Data Protector may make consecutive attempts at backing up opened. or No Report will put messages in the session with the selected severity when locked files are encountered during the backup. The data stored with this option represents a savings of about 90% as compared to log all. locked files. A higher level of detail will result in a larger database. NOTE The following considerations need to be taken into account when setting the log level: The level of detail to which you want to be able to browse when performing restores. http://education. Smaller than.P.Module 8 Backup − − Log Directories Details on directories only are stored in the database. files Bigger than. The message level chosen as Warning. You can back up files of All sizes. • Time out (default is 0) Data Protector will pause in between attempts to backup opened. such as news and mail systems. However. You can back up files of All sizes. or within the specified size Range Winfs Options • Report Open locked files as (Warning is the default) Files that are opened and locked by an application are not backed up by Data Protector. The retry attempt is for each file encountered.com U1610S B. locked files.00 8-39 2003 Hewlett-Packard Development Company. Minor. Smaller than. . No Log No details on files or directories are logged in the database. This timeout is used for each consecutive retry. This disables the search feature during restore. to browse directories. The restore will take longer because Data Protector cannot use fast positioning on the tape but will read from the start of the backup. and you will be able only. You will not be able to search and browse files and directories while restoring. Caution should be used as this will increase the duration of the backup.hp. This option is suitable for file systems with many auto-generated files. L. Data Protector still performs fast positioning because a file is located on the tape near the directory where it actually resides. The size of the Data Protector catalog database. The primary information stored here is at the object level. U1610S B. as compared to POSIX links on Unix. Data Protector will expand the sparse file before backup. Files that do not have the archive attribute set. This is more efficient. When this option is enabled. this is regardless of the modification time of these files. The NTFS links are not very common. • Expand sparse files (default is off) By default. but restricts the restore to only Netware systems. http://education.hp. so this feature is off by default. • Do not use archive attribute (default is off) Data Protector will backup all files with the archive attribute set when performing incremental backup. Data Protector does not attempt to detect hard links for NTFS file systems. this approach improves the backup performance. Data Protector will backup the sparse files in their current.Module 8 Backup • Detect NTFS hard links (default is off) Unlike in Unix operations. but have their modification time changed since the last backup will be backed up during incremental backup. This significantly speeds up the backup process at the expense of backing up each hard link as a separate file. compressed form. Data Protector by default will reset the archive attribute after a backup. but prevents the restore of these files to any other platform.00 8-40 2003 Hewlett-Packard Development Company. L. Netware Options • Number of retries (default is 0) Data Protector will make this number of attempts to backup Netware files before issuing an error message.P. Data Protector will backup NetWare compressed files in the compressed form as with the sparse file option. • Uncompress NetWare compressed files (default is off) By default.com . Here you may also change the order of the objects in the list. The order will affect the execution sequence and pairings for concurrency. http://education.hp. L. . This object summary list is the last configuration screen before you save the specification and/or start the backup.Module 8 Backup 8–18.00 8-41 2003 Hewlett-Packard Development Company.com U1610S B.P. SLIDE: Object Summary Object Summary List sorted based upon order Student Notes The final step in creating a backup specification is to review. Notice that you may select the column headings in the summary within the Results Area to change the sorting preference for the list. From this object summary screen you may also modify any object options individually. The object list order along with the algorithm for load balancing will determine the backup sequence. and possibly change the objects and options selected for the backup. The “Only” list is used for include.com . From here. you may select the parts of a files tem object to backup. Whenever a match for the filter is found. Use the Filter … button to specify a wildcard list of names to include or exclude. instead of the entire tree. which is the default. The Trees list is essentially an Include-only list for the backup.Module 8 Backup 8–19. the item is either skipped or included in the backup.00 8-42 2003 Hewlett-Packard Development Company. U1610S B. and the “Skip” list is used for exclude. In both cases.hp. the list represents a filter for the entire file system. When the lists are empty. L. SLIDE: Object Properties Object Properties Only… Skip … Student Notes The slide illustrates where to find some of the object properties where you may fine-tune the scope of the backup. the entire object (file system) will be backed up.P. The exclude list allows you to specify the absolute path of the files or directories to exclude from the backup. http://education. a UNIX file system mount point for the root file system C: . L. Moreover. Multiple versions of objects may be stored in the database with different descriptions. you will end up with multiple objects in the Data Protector Database! The more meaningful your object description.. • Mountpoint Specifies the file system mount point on a UNIX type system. TIP Data Protector uses three key qualifiers to identify file system objects in the database. These are used for restore and reporting.P.Module 8 Backup Object Qualifiers The data that is to be backed up requires qualification that is more detailed for Data Protector.uksr.. have other qualifiers. such as where it resides. The following list details the most commonly used qualifiers used with the backup specifications: • Hostname Specifies the particular system in the cell that the object resides on. However.com U1610S B. we will not be detailing these options. they are Hostname. such as the instance or SID name.com is a fully qualified hostname.a UNIX file system mount point / . and helps to identify this object during the restore process.hp.a Windows drive letter CONFIGURATION . if the description of an object changes. This description is stored in the Database as the object description. etc. Configuring Data Protector to backup a file system is not sufficient information. or the drive letter on a Windows or Novell system Example: /opt . it is very important.00 8-43 2003 Hewlett-Packard Development Company. Specialized backup specifications. Example: vindaloo. MS Exchange.The windows registry and recovery files • Description (optional-strongly recommended) A description to distinguish between this particular backup of the object and another. A complete description of the object. . which parts of it are to be backed up. Informix. but focusing on the backup specification datalist and options instead. must be specified.hp. etc. Mountpoint and Description. such as Oracle. Although this item is optional." http://education. the easier to locate the object for restore! Example: “Full Backup B4 DB reorg. U1610S B. be aware.P. and overlap the data streams. it is possible to be backing up the same data more than once. (and reduce performance). as we will see in the Restore chapter. with is multiple objects being sent to one device. This configuration is manual. as Data Protector will start a disk agent for each data stream that you configure. L. Data Protector. http://education.Module 8 Backup 8–20. does permit a session based restore. Device concurrency is still available.00 8-44 2003 Hewlett-Packard Development Company. The purpose for creating the multiple streams is for improved backup performance. Session restores allow for all data that was backed up in a session to be restored in parallel.hp. This is very much different than device concurrency. SLIDE: Parallel Data Streams from Object Parallel Data Streams from Object 1 Disk Agent 2 Media Agent Filesystem Disk Disk Agent 3 Media Agent Disk Agent 4 Disk Agent Filesystem Disk 5 Media Agent Disk Agent Don’t forget to consider how you will use restore! Student Notes Data Protector allows for multiple data streams from one file system to be used for a backup.com . Great care must be taken in order that you do not overload the disk. One disadvantage to this configuration is the possible complexity in performing a restore. Recall that an object is defined by three parts. use the Manual Add… feature and select the Trees option for an object. One key to success here is that you will add a file system multiple times. http://education. “Hostname. this is only possible if you change the description for each one. you may add another thread (directory) to be backed up for each file system. SLIDE: Configure Parallel Data Streams Configure Parallel Data Streams Student Notes To configure parallel data streams. . Mountpoint and description.00 8-45 2003 Hewlett-Packard Development Company.Module 8 Backup 8–21.com U1610S B.” As long as the object description is different. L. Add the data streams (directory to backup) one at a time.P.hp. The BSM checks that sufficient licenses are available for the logical devices defined in the backup specification. It will then start the media agents. not at parsing time. A backup is started either interactively by the user or by the Data Protector scheduler. U1610S B. The BSM parses the backup specification and checks it for errors. these objects are expanded into a list of the host's currently mounted file systems. L. which in turn starts a Backup Session Manager process (BSM). If load balancing is used. 2. 5.com . For each media agent. The file systems inherit the options defined for the host object.P. http://education. If the backup specification contains host objects.Module 8 Backup 8–22. The backup request is received by the cell manager. any modified options are read. and whether they can be locked. then license checking and locking takes place.00 8-46 2003 Hewlett-Packard Development Company. 3. SLIDE: The Backup Process Flow The Backup Process Flow Start BSM Parse Global File Start Agents Parse Backup Specification DA 1st Tree Walk MA Yes Host Object? No No Preview? Yes Convert to Filesystem Objects Connect to MA 2nd Tree Walk Send Data to MA Connect to DA Write Data to Device Student Notes 1. it starts the number of disk agents that correspond to the device concurrency. 4. The <OMNICONFIG>/options/global file is parsed. just before the devices start.hp. The Disk Agent connects to the Media Agent and another tree-walk is performed. The session is complete. On Windows NT file systems. 8. If the backup is being run in Preview mode (a dummy run). the SM shuts down the Media Agent and terminates. On the first traversal. during which it reads the files and sends the information to the Media Agent. The Session Manager (SM) starts a new Disk Agent (if required) for the same Media Agent.P. L. and terminates. then stop.com U1610S B.00 8-47 2003 Hewlett-Packard Development Company. the Disk Agent disconnects from the Media Agent. The Disk Agent (DA) does a tree-walk (mount point and tree information are checked). If not. http://education. When the second tree walk is finished. only one tree walk is performed unless you choose to use the NTFS hard link option.Module 8 Backup 6. The restore session runs in a very similar way. The DA then connects to the MA. . it computes the file system statistics and builds a catalog of hard links.hp. 7. groups can be created to organize them more effectively.00 8-48 2003 Hewlett-Packard Development Company.hp. for example. The following elements can be specified in templates: • Devices and Options Devices are only applied to a backup specification. via a template. Groups: • In large environments where many backup specifications and templates are required. L. Rather than specifying the same options each time a specification is generated. etc. Templates Many environments can require many separate backup specifications. http://education. SLIDE: Templates and Groups Templates and Groups Templates: • Often used backup specification and schedule characteristics can be saved in a template. • The template can then be used to generate new backup specifications with ease. the same media pool.P. Object Level Default Options U1610S B. Student Notes Data Protector provides the ability to create templates and groups to aid the generation and organization of backup specifications.com . they can be applied en masse. the same schedule.Module 8 Backup 8–23. if the backup specification uses load balancing or does not have any configured devices. each backup specification may have very similar characteristics to previous ones. • • Backup Specification Options Backup options applied to the whole backup specification. Groups Large numbers of backup specifications and templates can be difficult to administer. You cannot undo this action.Module 8 Backup Backup options applied to objects.P. The sheer size of a list can make it confusing and difficult to find what you are looking for. • • Object Qualifiers (Tree Options) Options skip. http://education. etc). exclude and only.00 8-49 2003 Hewlett-Packard Development Company. Data Protector allows the creation of Groups that allow you to place related backup specifications and templates together. .hp.com U1610S B. you can create groups based on system usage (production. Backup options for an object are not applied to the objects in the backup specification unless the Override object options is selected. development. Schedule How the backup is to be scheduled. L. For example. with the exception of actually writing any data to the backup device. total data calculated Object level pre/post-execs run Student Notes The Preview function allows the user to perform a “preliminary run” of a backup specification. The main difference noticed is the speed with which the objects are completed. it is a very good test of backup specification correctness. (ExecScriptOnPreview) U1610S B. http://education. Checks the following: • • • • • • Syntax of backup specification Licenses Agent startup and communication (disk. When you preview a backup. CAUTION The pre/post execute scripts may run during the preview mode. It is highly recommend that a preview be run on all new or modified backup specifications. See the options in the <OMNICONFIG>i/options/global file to turn off pre-exec during preview.com . Should be performed on all new or modified backup specifications. rather than any transfer of data. SLIDE: Preview Preview Performs a “Dummy Run” of the backup.00 8-50 2003 Hewlett-Packard Development Company. No data is actually backed up or media written to.hp. media agents) Sufficient media pool allocation File system trees walked. This is because only a tree walk and space calculation are made. This may cause some interruptions within a production environment.Module 8 Backup 8–24. especially when they are to be scheduled. The preview will run through all of the backup steps. the backup monitor shows exactly the same kind of information you would see if the backup were actually running.P. L. Therefore. hp. put the value back to the original setting.P. When the preview has completed.Module 8 Backup TIP To speed up a preview of a large backup specification. you can temporarily increase the concurrency of each logical device to the maximum. L.00 8-51 2003 Hewlett-Packard Development Company. http://education.com U1610S B. . Module 8 Backup 8–25. What is an object? 5.00 8-52 2003 Hewlett-Packard Development Company. What are the four fundamental components of all Data Protector backups? • • • • 3. L.P. What is a backup specification? 4.hp. What command is used to perform a backup from the Data Protector command line interface? 2. http://education. What is the purpose of setting the Ownership of a backup specification? U1610S B. Name three types of objects 6.com . Review Questions 1. P. When is it beneficial to use software compression? 9.com U1610S B. What is the meaning of Concurrency? 10. describe the advantages of Load Balancing. In brief terms.00 8-53 2003 Hewlett-Packard Development Company. What is the purpose of pre and post execution? 11. 8. . What is the purpose of a Template? 13.Module 8 Backup 7.hp. What is the purpose of a Group? http://education. What are the differences between object level and backup specification level pre and post execution? 12. L. Module 8 Backup U1610S B.hp. http://education. L.P.com .00 8-54 2003 Hewlett-Packard Development Company. com U1610S B.Module 9 — Restore Objectives Upon completion of this module. Use the Data Protector Restore GUI. Perform single or parallel restores. Perform session and object restores. http://education.hp.P. . L.00 9-1 2003 Hewlett-Packard Development Company. you will be able to do the following: • • • • Use the restore capabilities for Data Protector. L. restores are occasional events that are performed only once in the same manner. interactively through the GUI or via the command line interface omnir command.00 9-2 2003 Hewlett-Packard Development Company. SLIDE: Performing Restores Performing Restores Data Protector provides two methods of performing restores: • Interactive restore via the GUI • Command line interface via omnir Student Notes Data Protector offers two methods of restoring data. http://education. there is no need to have the equivalent of a backup specification for restores. Options can be set on the restore session level. rather a design consideration as restoring data is a destructive process and incorrect or out of date predefined restores are a potential disaster.Module 9 Restore 9–1. waiting to happen. This is not a limitation with Data Protector.hp. The Data Protector Administrator may create a script to automate the restore process using the omnir command.com . Data Protector restore definitions are done on backup session or object level. U1610S B. Data Protector does not provide a method for predefining a restore session’s requirements. Within one restore session. All restores are guided interactive sessions. as well as on object level. For each object. files and versions can be selected. one or more backup objects can be selected. as opposed to scheduled datalist backups. each restore session must be defined when required. In general. if desired.P. As such. com U1610S B.00 9-3 2003 Hewlett-Packard Development Company. http://education. restore data is only necessary for auditing and reporting purposes.hp. While backup data in the Data Protector database is necessary for restore.Module 9 Restore When the restore is started. the restore session manager is executed and a restore session ID is assigned to the restore session. L.P. The restore session is stored in the database in a similar manner to backup sessions. . up to the discretion of the administrator. These sessions may be removed. SLIDE: Restore Objects Restore Objects Depending on the types of backups performed.Module 9 Restore 9–2. • rawdisk From a rawdisk object. many different object types may be available for restore. from the winfs object.00 9-4 2003 Hewlett-Packard Development Company. because Data Protector must read the data multiple times. or complete file system. http://education. winfs. Each object has restore options that are specific to the individual object type. This restore process can be very time consuming. netware From these objects. It is also possible to restore a single file from a raw backup. it is possible to restore the entire raw disk image copy. if the raw backup contains an HFS (single file restore is not supported for JFS). L.P. Only the HP-UX HFS file system is supported for this type of restore. The maximum number of passes of the media is five times.com . Object Types • filesystem. U1610S B. vbfs. the following object types will be available for restore: • file system • rawdisk • omnidb • vbfs • session • SAP • Oracle • Oracle8 • Sybase • Informix • • • • winfs mssql msexchange netware Student Notes Depending on the types of backups performed. directory. There are also restore options that are common to all object types. it is possible to restore the windows registry (part of CONFIGURATION). In addition.hp. it is possible to restore a file. com U1610S B. for example rman for Oracle or sapdba for SAP. Integrated third-party databases are restored using the databases own tools.P. including the <OMNICONFIG> directories. • sap. L. msexchange From these database objects it is typically possible to restore an entire database. onbar for Informix. . informix. oracle8.00 9-5 2003 Hewlett-Packard Development Company. the Data Protector internal database can be recovered. a portion of the database (dataset) or point in time via the redo logs.Module 9 Restore • omnidb From the omnidb object.hp. sybase. This topic will be addressed in much more detail later in this course. oracle. http://education. mssql. you will be able to browse the data trees and select down to the file level if a partial rather than a full restore is necessary. http://education. Normally this would be after a disaster recovery. Disaster recovery within Data Protector is discussed in more detail later in this course. Data Protector provides individual object selection. Each object that is recorded in the database may be restored in parallel with any other object. the restore of an entire system is necessary.hp. Usually.Module 9 Restore 9–3.P.00 9-6 2003 Hewlett-Packard Development Company. so you are not limited to an all or nothing restore. SLIDE: Restore from a Session Restore from a Session Data Data Protector Protector Session Session Restore Restore •• Restores Restores an an entire entire client client •• Can Can restore restore all all objects objects from from a a backup backup together together •• Operates Operates like like a a datalist datalist for for restore restore •• Can Can exclude exclude individual individual objects objects •• Provides Provides a a high high degree degree of of control control for for each each object object •• Makes Makes extensive extensive use use of of the the database database Student Notes In some cases. Data backed up within a single session. The Data Protector internal database plays a key role in making the session and object data available for restore. The session restore capability within Data Protector is based upon how you perform your backups. the disaster recovery includes some out of date files or data. usually from a backup specification (datalist). While selecting a session to restore. U1610S B. Within each session. By selecting a backup session for restore purposes you are able to restore all of the data that was a part of the backup. can be restored in parallel. Data Protector in conjunction with your disaster recovery tools allows for easy recovery of your data from the most current backup session. L.com . the same performance benefits can be realized by choosing to restore objects in parallel. .Module 9 Restore 9–4. Conversely. when it comes to restore time. A sequential restore only allows the selection of a single object at a time. A parallel restore requires only one pass of a media in order to extract all the selected objects from it. backing up multiple objects in parallel maximizes performance. SLIDE: Parallel Restore Parallel Restore Client system disk agents DA MA DA Disk 1 Disk 2 Client system media agent Client system disk agent DA Disk 1 Student Notes When a backup is performed to a logical device that has a concurrency value greater than one and/or multiple logical devices. multiple passes of the media are required if more than one object from the backup is selected for the restore. thus.P.com U1610S B.00 9-7 2003 Hewlett-Packard Development Company. Parallel restore can be used to restore all of the objects to a client system from one restore session as well as objects from unrelated sessions.hp. http://education. L. P.Module 9 Restore Parallel Restore or Sequential Restore In some cases. NOTE A parallel restore may execute multiple DA processes for a single MA. just the reverse compared to concurrent backup. In addition. L. • • • Objects that were backed up in parallel to the same medium are capable of being restored in parallel. Objects that exist on the same medium in different tape segments are restored sequentially. U1610S B.00 9-8 2003 Hewlett-Packard Development Company. This depends largely upon how the objects exist on the physical media. objects selected for parallel restore may be restored sequentially. Data Protector may start multiple DA processes for a single object if the data was backed up in that manner using the trees options. Objects that were backed up to separate devices using different media are capable of being restored in parallel. even if configured for parallel restore.com .hp. http://education. The process is conceptually similar to backup.com U1610S B.P.00 9-9 2003 Hewlett-Packard Development Company. L. such as: • • • • • • • Restore the latest object version Restore to the original location Restore to the original client system Don’t overwrite newer files Replace missing files/directories Use the same device used for the backup Others… The following pages will illustrate the typical restore sequence. . once you have changed all of the necessary defaults. but you may start the restore at any point. http://education.hp.Module 9 Restore 9–5. SLIDE: Restore Sequence Restore Sequence Choose: • Object(s) or Session for restore • Source • Destination • Options • Devices • Media • Backup Object Summary (properties/options) Student Notes The general sequence for restoring data from Data Protector tapes is listed above. remember you can start a restore anywhere within the sequence. You do not have to work through all of the option screens if you want to accept all of the restore defaults. and the browse features allowing for file level selection. Mount Point. you will end up with multiple object names in the database. Notice how /tmp appears more than once.00 9-10 2003 Hewlett-Packard Development Company.com . files etc to restore. the user is able to browse the catalog database to select directories. L. http://education. The level to which the user will be able to browse the detail catalog of the database depends on the following criteria. U1610S B. Description if these change over the life of an object.P.hp. The graphics shown above illustrate the selection of an object to be used for restore. NOTE The three parameters that identify an object in the database: Hostname.Module 9 Restore 9–6. SLIDE: Restore Source Restore Source Select objects or a session from the database Choose items to restore and their properties Select tasks to search for files Student Notes When a restore is performed. It could have been set to “Log All”. When the backup is performed. This choice would be made to save database space of approximately 90% over LogAll. • Log All: If "Log All" was specified. then you may browse the tree as in “Log All”. a user may not be able to see certain objects while browsing the restore catalog. while ordinary users can see only their own objects. as they are not stored in the database. but makes the restore more challenging. and the user must know the complete path. navigating the restore GUI may become time consuming if you are not sure where a particular object resides. no browsing at all is possible. browsing will not be possible. and browsing the file/directory tree is unnecessary. The files must reside within the current Data Protector catalog database to be located by the search. located at the bottom of the Scoping Pane may be able to help locate the files in need of restore. The choice would be made to save database space of approximately 70% over Log All. and the setting of the object protection to public or private. This is a tradeoff between flexibility and database space. If this date has passed.hp. Log File: If “Log File” was used. Searching for Files (Tasks Scoping Pane) When going to restore a file or directory. but uses the most database space. Data Protector User Permissions and Public and Private Objects Depending on the permissions of the user.00 9-11 2003 Hewlett-Packard Development Company. Log Directories: If “Log Directories” was used. “Log Directories” or “No Log”. No Log: If “No Log” was used. • • • Catalog Protection Catalog protection refers to how long the online catalog information is retained.Module 9 Restore Catalog Log Level Catalog log level refers to the logging level that was specified when the backup was performed. This option would be used if restores are only performed at the object level. you can set the catalog information to keep it as long as the media is valid. you should be able to browse down to file level and select the file for restore. as it will not be possible to browse it. This uses the least database space. etc. Admin level users can see all objects. http://education. or until a particular date. Minimal disk space is needed to store the object data as compared to Log All. but only on the backup tape. “Log File”. filename. This will allow the easiest selection.com U1610S B. the user will only be able to browse to directory level and must know the name of the file to be restored. but you will not be able to see all of the file attributes. Typically. The Restore by Query task.P. plus any objects that are made public. . L. You will also be able to see all of the file attributes. if any is known. Select from the list and configure the options for the items that you want to have restored. 5. Select the client system for which the file search will be performed. http://education.Module 9 Restore General steps for performing restore by query searches: 1. (Case sensitive checking is optional. Select Finish to start the restore session. Data Protector will present a list of all matches based upon your selection criteria. 2. U1610S B.00 9-12 2003 Hewlett-Packard Development Company. 6. L.hp.com . Select a modification time for the file. 4.P. Fill in as much information as you have about the file name and object that contains the file. and wildcards are available) 3. or a range of dates for which the backup was taken. Choose a time frame for which to search. You can select the version of the object.*. Within the Properties GUI shown above. or place it into a new directory. Restore only allows you to specify wildcard matches to the object contents. its destination.Module 9 Restore 9–7. only parts of the object restored. You may alter the name of the object. such as anything containing the name core.com U1610S B. and desired. SLIDE: Restore Object Properties Restore Object Properties Version and destination also available in pop-up menu Partial restores Default version is the latest Student Notes Data Protector allows each object selected for restore to be “fine tuned” to meet your requirements. For example maybe you would like all of the Adobe Acrobat documents restored. http://education. you would enter *.P. the Destination tab contains options that allow the destination of the object to be changed. such as *core. .hp. L. When the Into option is chosen Data Protector will append the original object path to the selected new location.00 9-13 2003 Hewlett-Packard Development Company.pdf in the “Restore Only” option screen. or core. enter these in the “Skip” option screen. Perhaps you would like to exclude certain files from the restore. • Non-authoritative: The Active Directory database is updated after the restore using standard replication techniques.com . The Active Directory database is not updated after the restore and the restored data overwrites the existing data in the target destination.Module 9 Restore Restore As / Into • As Restore the file or directory as the given path.hp. L. PC Restore Options Netware By default. Directories will be created as needed and are appended onto the original path. Data Protector will backup NetWare sparse files in their compressed sparse format. This option has to be used when all replication partners for a replicated share have been lost. • Primary: The Primary replication mode allows you to keep the NT directory Service online and is used when you restore FileReplicationService along with the Active Directory service. • Authoritative: This is a Windows 2000 specific option dealing with active directory restores.00 9-14 2003 Hewlett-Packard Development Company. http://education. This choice will speed up the backup process. Windows 2000 For Windows 2000 there is restore option for restore of Windows 2000 active directories. • Into Restore the file or directory into a different directory.P. any path specified as non-absolute will be created relative to the root (/) filesystem. The Nonauthoritative replication mode is the default option. U1610S B. Security Concern The default behavior with Data Protector. and to where the data is to be restored. netware) Data Protector provides many options when restoring file systems. L.00 9-15 2003 Hewlett-Packard Development Company. as well as its predecessor Omniback. is to allow any restore disk agent to respond to any session manager to start the restore process.P.com U1610S B. regardless of the cell affiliation. http://education. . This feature is designed to allow for simpler restores in case of a disaster. In this way any cell manager could be used to restore data to any client. SLIDE: Destination Destination Select or enter any host with a disk agent Student Notes Filesystem Restore Options (including vbfs. what data is to be left out. winfs.Module 9 Restore 9–8.hp. Data Protector will create the necessary directory trees to accommodate your requested location. You may restore data onto any client with a Disk Agent installed (even non-cell clients) as well as restore the data into any new location within the system. Default Destination The default destination for any restored object is the objects original location. It is possible to define at restore time exactly what data is to be restored. choose one of the other two file conflict handlers.hp.P. File Conflict Handling Keep Most Recent: will overwrite files or directories on the disk that are older than the files from the tape being restored. and a restore is performed selecting the contents of Directory_1 for restore. Object Exists!” will be presented during the restore session to indicate that there are items missing from a directory that were not restored.com .Module 9 Restore The client and therefore the cell may be secured to limit which cell managers have access to the various clients. U1610S B. if the following file and directory structure exists: Directory_1 File_A Directory_2 File_B If File_A and File_B are deleted. The specific details of the security configuration is covered in the security module. later in this course. File_A will be restored but File_B will not be restored. Data Protector will not restore files from tape even if the version on disk is older.00 9-16 2003 Hewlett-Packard Development Company. and the "no overwrite" option will not overwrite an existing directory to restore its contents. http://education. No Overwrite: determines that files and directories are not overwritten. The Warning: “Cannot restore – name conflict. such as files that were deleted. Restored files are only those that are not currently on the disk. Overwrite: replaces any files or directories already on the disk with those from the restore tapes. Newer files will remain untouched during the restore. For example. To restore the items. because Directory_2 exists. L. L. SLIDE: Restore Options Restore Options Student Notes Omit Deleted Files (default=off) When performing a point in time restore that requires the restoration of a full backup and subsequent incremental backups. http://education.P. the only mode available for the restore is Overwrite mode. "Merge" as well as "No Overwrite" are unavailable. Data Protector restores deleted files but then removes them at the end of the restore session. this option prevents files present on the full backup but that were removed prior to the incremental backup. the newly restored file will be used.hp. The file will remain in use with no impact to the user. from being restored. it will be renamed to the file name prefixed with a “#”. When this option is selected.00 9-17 2003 Hewlett-Packard Development Company. This allows the file to be restored with the correct name. Move Busy Files If the target file is in use.Module 9 Restore 9–9. When the file is eventually closed and reopened. . Some manual cleanup will be required to find and selectively remove all of the previously busy files. than is actually needed for the restored data. This will typically require more disk space during the restore operation.com U1610S B. Data Protector does not examine the contents of the data blocks by default. U1610S B. Lock Files During Restore (default=off) Restore Time Attributes (default=on) Denies access to files during the restore session.P.hp. Display Statistical Information (default=off) Display statistical information reports statistical information about the restore size and performance. The command/script is executed on the target system. Restore Sparse Files (default=off) When a sparse file (logical size is greater than the physical size) is backed up.Module 9 Restore List Restored Files (default=off) Produces a listing in the restore session messages window of the files restored. The logical size of the restored file will be the same but it will not consume as much physical space. http://education. When this option is selected. unless you enable this option. Data Protector will restore only the blocks containing data and null-data is not restored. Restore time attributes sets the time attributes of the file to what they were when the file was backed up. so it will not create blocks of zeros that were previously allocated to the file.com . conversely. you are able to define a command or script that will be executed before and after restoration. Restore Protection Attributes (default=on) Pre/Post-Exec (no default) Sets the protection attributes of the file to what they were when the files were backed up. some files may not be useable by their applications if they are not restored as sparse. the entire logical size of the file is written to a tape. As with backup. NOTE Selecting this can greatly reduce performance because Data Protector must examine the data to determine if it contains null data blocks.00 9-18 2003 Hewlett-Packard Development Company. L. com U1610S B.00 9-19 2003 Hewlett-Packard Development Company. L. and then select Change . a permanent change to an alternate device would be in order. Select the device in the GUI. SLIDE: Restore Devices Restore Devices Device used for backup Restore device may be changed Student Notes When restoring data. Change Logical Device The device used for the object backup may no longer be available. The omnidbutil command will be discussed in more detail within the database module later in this course.Module 9 Restore 9–10. http://education.P. this is desirable. or the device no longer exists it is possible to use a different logical device of the same type for the restore. If waiting for the device to become available is not acceptable. or currently busy. Data Protector will choose the same Logical Device that was used during the backup for the object. If the device no longer exists. especially if the needed tape is still within the repository of the library. . In most cases. Use the omnidbutil command with the -change_bdev option to permanently change a device to another within the Data Protector database.hp. Module 9 Restore 9–11.com .hp.P.00 9-20 2003 Hewlett-Packard Development Company. L. U1610S B. SLIDE: Restore Media Restore Media Student Notes Shows the media that will be required in order to perform the restore. http://education. P. and Skip choices.” You can specify an acceptable time range for an alternate version. if your preferred version is not available. From the pop-up menu. SLIDE: Restore Summary Restore Summary Student Notes Last minute changes to the object list.Module 9 Restore 9–12. L. Here Data Protector allows the addition or removal of objects for the restore session. Restore Only. an additional choice of version selection by time.00 9-21 2003 Hewlett-Packard Development Company.com U1610S B.hp. http://education. Destination. . Your selection may be from a date and time range from seconds to hours. The properties include Version. allows a file version to be chosen from “best available. The properties for each object may be changed by highlighting the object and using the pop-up menu (right-mouse-button) to select its properties. chose the “start restore” icon from the Tool Bar. Single Restore When single restore is chosen. you can choose individual objects for single restore one at a time without losing the configuration specified up to this point.Module 9 Restore 9–13. In many cases your choice of multiple objects was deliberate. http://education. and select another of the configured objects to restore. SLIDE: Parallel or Single Restore Parallel or Single Restore Start restore from the toolbar or Actions menu Student Notes Configure Parallel Restore When you have selected multiple objects for restore. but just in case sequential restore is needed. you will be prompted for the object to restore. Repeat this process until all of your objects are restored. Data Protector will prompt you with a notification screen.hp. After that object completes.P.00 9-22 2003 Hewlett-Packard Development Company. and choice of performing single or parallel restore. L.com . U1610S B. Restore directory from Tuesday’s incremental backup. order. you can see the objects that Data Protector has decided are necessary to restore and the order.com U1610S B. restores are more complex. Data Protector will issue mount requests for media in the correct order as needed for the restore. Data Protector takes care of this by building the restore session automatically including the objects and the order they are to be restored. if the media is not already in the device. order.hp. The slide shows a screen shot from such a restore session.00 9-23 2003 Hewlett-Packard Development Company.all allin in the same restore the same restore session. 3. the last full fullbackup backupof ofthe thedata data must be restored first. then the following restores must be performed: 1. session. This is because to restore to a particular point in time (a date/time of a particular backup) multiple restores must be performed. Restore directory from last full backup. http://education. the last point in time. For example if a weekly full backup is performed followed by daily multi-level incrementals (Mon-Fri). Restore directory from Monday’s incremental backup. Student Notes When using a full backup plus incremental backup scheme. followed followedby bythe the note incremental backups incremental backupsin in the thecorrect correctorder.Module 9 Restore 9–14. 2. L. the user wants to recover a directory to the state it was on the Tuesday. Data DataProtector Protectortakes takes care of care ofmedia mediaselection selection and andrestore restoreorder. SLIDE: Point in Time Restore Point in Time Restore When Whenrestoring restoringto toa a point in time. must be restored first.P. . L. U1610S B. http://education.00 9-24 2003 Hewlett-Packard Development Company.P. it is also possible to omit files that were deleted between backups.hp. See file system restore options for more information.com .Module 9 Restore With this type of restore. hp.com U1610S B. . TRUE/FALSE? 2. When performing a restore. The same functionality is available with Data Protector Restores. The level of detail available in the restore file browser depends on which factors? 4. Review Questions 1. 3. Is it possible to restore a single file from a rawdisk backup? If yes. L. Regularly performed backups can be saved as Backup Specifications and scheduled via the Data Protector scheduler.00 9-25 2003 Hewlett-Packard Development Company.P. What does a point in time restore mean? 5. describe the limitations. how would you suppress Warning messages? http://education.Module 9 Restore 9–15. 00 9-26 2003 Hewlett-Packard Development Company. Is it possible to restore a file backed up on one system to a different system? Must the system be a member of the same Data Protector Cell? 10.com .Module 9 Restore 6.P. L. What is the difference between the Restore As and Restore Into options? 9. http://education.hp. Overwrite and No Overwrite options: • • • 7. Describe the behavior of the Merge. Give an example of a use for the pre/post-exec facility for restores: U1610S B. What is the difference between a normal restore and a parallel restore? 8. TRUE/FALSE? 12.hp.com U1610S B.P. .Module 9 Restore 11. the file system must first be unmounted. In order to perform a valid Rawdisk backup of a file system.00 9-27 2003 Hewlett-Packard Development Company. L. What is the difference between Exclude and Skip? http://education. Module 9 Restore U1610S B. L.hp. http://education.com .P.00 9-28 2003 Hewlett-Packard Development Company. Restore/recover the Data Protector internal database.00 10-1 2003 Hewlett-Packard Development Company. L. Maintain the Data Protector internal database.hp. http://education.com U1610S B. . you will be able to do the following: • • • • Describe the Internal Database architecture.Module 10 — Internal Database Objectives Upon completion of this module.P. Back up the Data Protector internal database. 00 10-2 2003 Hewlett-Packard Development Company. http://education.hp.P.Module 10 Internal Database 10–1. SLIDE: Internal Database (IDB) Internal Database (IDB) Features • • • • • • Scalable Flexible High performance Reliable Low maintenance Automated recovery Topics • • • • • Architecture Command summary Maintenance Backup Recovery Student Notes In this module.com . the following Internal Database topics will be addressed: Architecture Command Summary Maintenance Backup Restore Recovery Composition of the database and general overview Details on using the database related commands Required routine maintenance Backup procedures and recommendations Restore procedures and recommendations Recovery from corruption U1610S B. L. 0 Database.hp. . less disk IO Many more systems / disks backup in parallel while tracking the catalog data for convenient restore browsing Multi-threaded database server for improved scalability on multi-processor systems Low Maintenance Requirements The IDB maintenance effort has been significantly reduced: • • • Very fast and convenient file version purge (no administrator need to be involved) Higher granularity of IDB ensures its higher robustness and reliability Improved reports and notifications help to monitor and maintain IDB Easy IDB Disaster Recovery With the utility omnidbrestore. IDB recovery is easy: • • • With option ‘-autorecover’ it’s a semi-automatic procedure Using the IDB archive transaction logs the IDB can be restored to the point in time of disaster In-place restore of IDB is possible Automated “Online” Migration With the utility omnidbupgrade.Module 10 Internal Database IDB — Highlights (with contrast to earlier versions) Scalability One of the major features is the overall scalability. higher insertion rate.P. the IDB migration/upgrade is very easy: • • The IDB upgrade utility monitors the upgrade process The administrator can decide when to upgrade the IDB detail part http://education. there is: • • • Less CPU load.com U1610S B.00 10-3 2003 Hewlett-Packard Development Company. L. which allows for: • • Single point control for many more systems Storage of catalog data for hundreds of millions of files / many backup session versions for convenient restore browsing for a long time Higher Performance In the Data Protector 5. residing on tapes not yet upgraded. the upgrade is resumed automatically when services are restarted. U1610S B.00 10-4 2003 Hewlett-Packard Development Company. However. The detail upgrade procedure is recoverable.hp.P. thus backups can run (upgrade will be suspended during that time). will not work or will work partially. Filename purge cannot be run.com . http://education. The upgrade will be suspended while backup is running. Tapes with the detail catalogs not yet upgraded will not be allocated for appended backup. there are several limitations: − − − − Browsing of objects. L.Module 10 Internal Database • The detail part upgrade is performed while the IDB is online. If the system fails in any stage or if Data Protector shuts down. P. http://education. .com U1610S B. but larger sites should consider changing the default database due to higher expected quantities of data. SLIDE: Configuring the Database Configuring the Database • • • • • • Growth planning Disk space allocation Transaction logs Recovery data Event configuration Reporting Student Notes The Internal Database is configured by default when the cell manager is installed.Module 10 Internal Database 10–2. Configuring the Internal Database (or changing its configuration) consists of several facets: • Growth planning • Disk space allocation • Transaction log management (archival) • Recovery data management • Event configuration • Reporting Each of these facets will be explored in more detail in this section.hp. L.00 10-5 2003 Hewlett-Packard Development Company. The default configuration may be acceptable for smaller sites. com . including the system. directory and file names of the source data. http://education.Module 10 Internal Database 10–3.P. the various versions of the files that have been backed up (files that have been backed up more than once).hp. L.00 10-6 2003 Hewlett-Packard Development Company. SLIDE: IDB Information Storage IDB Information Storage • • • • Media management data Device configuration data Backup and restore session data File catalog data Database Type: Raima Velocis Internal Database • • • • • • • User configuration Backup specifications Schedules Cell environment Report groups Report schedules Notifications Flat File Storage UX: /etc/opt/omni Windows: /<product>/config Student Notes Data Protector stores its information in two main locations. /var/opt/omni/db40 on Unix. Data Protector IDB utilizes an embedded database technology provided by the Raima Company called Velocis. U1610S B. <OMNIHOME>/db40 on Windows. and the other being flat ASCII files located under the /etc/opt/omni on Unix. the first being the Data Protector internal database. <OMNIHOME>/config in the windows directory tree. and catalog retention information. The following information is stored in this Data Protector IDB: • Backup Catalog Data All information relating to data that has been backed up. etc. L.00 10-7 2003 Hewlett-Packard Development Company. • Device Management Records describing logical device configuration.P. physical device files.Module 10 Internal Database • Media Management Records describing media labels. backup objects. media locations. media pools. • Backup and Restore Session Data The session progress messages and object status as seen through the monitor screen and also when viewing previous sessions. including logical device names. descriptions.com U1610S B. media utilization.hp. current device repository. etc. lock names. . http://education. or the <OMNIHOME>\db40 may be used for a partition containing only the database. It is highly recommended that the database always have its own filesystem(s) or partition(s). and in the <OMNIHOME>\db40 directory on Windows. or on Unix. L. On Windows 2000. The filesystem may be accessed via a mount to the db40 directory.hp. the empty directory. U1610S B. <OMNIHOME> may be used as a drive letter path to a partition prior to the install of the product. The downside to the partition is that it must be suitable for disaster recovery.00 10-8 2003 Hewlett-Packard Development Company. SLIDE: IDB Tablespaces IDB Tablespaces RDS Controlled Embedded DB Media Management Database Catalog Database Filenames (up to 32 GB) Media management DB: • Devices • Libraries • Media pools Catalog DB: • Objects • Object versions • Sessions • Media positions • Directory names Student Notes The Internal Database resides in the /var/opt/omni/db40 on Unix.com . a symbolic link from the directory /var/opt/omni to the mount point.Module 10 Internal Database 10–4. http://education. because it can grow to be very large.P. discussed later in this course. The CDB tends to be much larger than the MMDB.hp. (see the module "Manager of Managers" for more details) http://education. directories. media and media pool information. This is discussed in more detail later in this section. Multiple Data Protector cells can share it. but reach somewhat of a plateau after the catalog retention time expires. the size should be kept to a minimum (the minimum amount of space required to store the information). NOTE The CDB (objects and positions) and MMDB parts represent the core part of the IDB. The largest file in the CDB is: fnames. In a multi-cell environment. The growth of the database depends on the number of backup sessions and the growth and dynamics of the client environment (number of new files). In such a configuration. and so on. Location: − Unix /var/opt/omni/db40/datafiles/cdb − Windows: <OMNIHOME>/db40/datafiles/cdb All changes made to the MMDB and CDB are updated using transaction logs.00 10-9 2003 Hewlett-Packard Development Company. In an ordinary single-cell environment.P. The filenames table will initially grow rapidly.com U1610S B. share devices.Module 10 Internal Database The embedded Data Protector (Velocis) database is composed of two separate tablespaces managed by the RDS server: • The Media Management Database (MMDB) — stores logical device definitions. at that point the growth will slow dramatically and remain fairly constant. but may be extended in up to 2 GB increments to 32 GB. the MMDB is stored on the Manager of Manager (MoM) system.dat is 2 GB.dat used for the filenames tables (up to 32 GB) The initial limit for the fnames. L. By frequently maintaining the database. versions. you may configure a central MMDB database for many cells. such as files. Location: − Unix: /var/opt/omni/db40/datafiles/mmdb − Windows: <OMNIHOME>/db40/datafiles/mmdb • The Catalog Database (CDB) — stores information about data backed up. The size of the database will ultimately be determined by one complete backup cycle of all of the data. . and therefore. with the Manager of Manager licenses. both parts of the database are located on the same cell server. 0) stores a great deal of data associated with backup session in data-files that are external to the Velocis database (IDB). SLIDE: External Binary Files External Binary Files bsm. http://education.com . The names of the files in the DCBF directory are derived from the medium-id that Data Protector assigned to the tape U1610S B. attributes. modification time.Module 10 Internal Database 10–5. This includes such details as the file size.msm controlled File version attributes One binary file per medium Session Managed Binary Files DCBF Session messages One file per session SMBF SIBF Student Notes Data Protector (as of Omniback version 4. These binary files are updated directly by the session managers. but also in the DCBF if requested. The file details are always stored on tape.00 10-10 2003 Hewlett-Packard Development Company. L. etc. The DCBF will contain one file for every backup medium (tape). permissions. transaction logs are not created for them. When the backup option for filesystem data is set to “Log All” Data Protector will store all the file details in this DCBF.P. There are three data-store directories used by default: dcbf smbf sibf Detail Catalog Binary Files Session Messages Binary Files Server-less Integration Binary Files Detail Catalog Binary Files (DCBF) The DCBF directory contains all of the file version attributes for every file that is backed up.hp. Location: • Unix: /var/opt/omni/db40/dcbf • Windows: <OMNIHOME>/db40/dcbf NOTE All changes made to the DCBF are done directly.hp. Location: • Unix: /var/opt/omni/db40/msg • Windows: <OMNIHOME>/db40/msg NOTE All changes made to the SMBF are done directly.com U1610S B. . The files are grouped by year and month of the session. By default. http://education. there is only one DCBF directory enabled. Data Protector has the default message level at Warning. nor recorded in the database. The size of the SMBF depends upon the following: • The number of stored sessions • The number of messages written per session. but it may be increased to Minor. and the DCBF will contain about 80%. without the use of transaction logs.Module 10 Internal Database when it was initialized. Session Message Binary Files (SMBF) The SMBF stores session messages generated during backup and restore sessions. when the backup option of “Log All” is used. One binary file is created per session.00 10-11 2003 Hewlett-Packard Development Company.) The CDB will contain about 20% of backup file data. Data Protector will automatically remove the file associated with a medium that becomes obsolete (exported or overwritten. − Unix messages require approximately 130 bytes each − Windows messages require approximately 200 bytes each The number of message written per session can be controlled by the message level feature of the backup session. L. The messages that don’t meet the specified severity level will not be displayed during the running session. without the use of transaction logs. Data Protector supports up to 10 DCBF directories per cell. Major or Critical to reduce the minimum severity of logged messages.P. The sysdb holds information useful for this purpose. In addition. These files are only used if you have Data Protector integrated with these HP disk products. Split Mirror/Snapshot Integration Files (ZDB) The VADB and XPDB stores data related to the Zero Downtime Backup integrations with the HP disk arrays. Location: • Unix: /var/opt/omni/db40/meta • Windows: <OMNIHOME>/db40/meta NOTE All changes made to the SIBF are done directly. L. without the use of transaction logs. VA and XP.00 10-12 2003 Hewlett-Packard Development Company.Module 10 Internal Database Server-less Integration Binary Files (SIBF) The SIBF stores raw NDMP restore data and/or EMC Fastrax data. These files are only used if you have Data Protector integrated with these HP disk products. Location: • HP-UX: /var/opt/omni/db40/sysdb • Windows: <OMNIHOME>/db40/sysdb U1610S B. These files are only used if you have Data Protector integrated with these other third party products.hp. Instant Recovery Integration Files (IR) The VADB and XPDB stores data related to the Zero Downtime Backup integrations with the HP disk arrays.com . without the use of transaction logs. VA and XP. Location: • HP-UX: /var/opt/omni/db40/vadb • HP-UX: /var/opt/omni/db40/xpdb • Windows: <OMNIHOME>/db40/vadb • Windows: <OMNIHOME>/db40/xpdb NOTE All changes made to the vadb and xpdb are done directly.P. the split mirrors and snapshots may be used for Instant Recovery. http://education. ini obrindex.com U1610S B. Configure the “RecoveryIndexDir” global option Transaction logging. SLIDE: Directory Structure Directory Structure db40 datafiles cdb mmdb catalog dcbf <file versions> logfiles rlog syslog msg <year> <tables> <tables> velocis. L.chk) Preparation to Allow for All Recovery Possibilities • • • • • • Relocate the IDB directories according to the recommended multi-disk layout. rdm.dat: transaction log: The database configuration file The recovery data file Two files used for the db-replay function (ex.hp.ini: obrindex.chg. but limits the scope of recovery) Regular checking of the database consistency Daily backup of the full database (hot-backup performed) Recording of recovery data in case automated full recovery is needed http://education.00 10-13 2003 Hewlett-Packard Development Company. Data Protector allows many parts of this database to be relocated for optimum performance and recoverability. The previous pages discussed several of the objects listed above.P. RAAAAAAI.dat <transaction logs> <month> <session id> *directories for ZDB and IR not shown Student Notes The directory structure for the default Internal Database is shown above.Module 10 Internal Database 10–6. Later in this section we will discuss the optimum disk layouts. . with archiving enabled (optional. some not yet mentioned: velocis. L.00 10-14 2003 Hewlett-Packard Development Company. and cannot be recovered with the transaction log replay. and performed by the IDB backup. This file is needed for the automated off-line recovery. The copies should be on different disk locations. In the case of disaster caused by a disk failure. It is recommended that the transaction logs are located on the system disk where the IDB was installed. separate from the database. The DCBF data can be imported from the last used media if it is needed. and the other parts of the IDB are relocated to other disks.dat created during the IDB backup. http://education. The off line recovery will also replay the transaction logs to bring the database to the state of the last backup.hp.Module 10 Internal Database Data Protector stores the recovery data in a file called obrindex. Transactions that affected the DCBF are not logged. the logfiles and recovery information would be stored online. U1610S B.dat. There can be two copies of the obrindex.P. The second copy is created by altering the “RecoveryIndexDir” parameter in the global options file.com . Module 10 Internal Database 10–7. TEXT PAGE: Transaction Logs The transaction logs created by the IDB may be used to recover the core database (MMDB and CDB in the event of a failure or corruption. By default the transaction log consists of a single file. The log will grow to a maximum of 2 MB and then be deleted and replaced by a new log. The transaction logs are stored in the following directories: Unix: /var/opt/omni/db40/logfiles/syslog Windows: <OMNIHOME>/db40/logfiles/syslog The names of the transaction logs will be similar to the following (from an HP-UX host): /var/opt/omni/db40/logfiles/syslog/rAAAAAAI.chg NOTE On Windows NT, it is not possible to change the locations of the IDB directories. Archive of Transaction Logs By default, Data Protector does not archive the transaction logs, but rather replaces them when they reach the 2 MB threshold. Enabling of the Archiving feature for the embedded database causes the previous logs to remain in place, instead of getting deleted. To enable the Archiving feature proceed as follows: 1. Stop the Data Protector services Omnis -stop 2. Edit the …/db40/datafiles/catalog/velocis.ini file, and set the parameter: …. Archiving=1 … 3. Ensure that there is enough disk space on the …/db40/logfiles/syslog directory (see the section below) 4. Start the Data Protector services Omnis –start Disk Space Consideration Data Protector will save archive logs until a new IDB backup is performed, at which time they are no longer necessary. The disk space needed to hold the archived transaction logs may be substantial, depending upon when the Archiving is enabled. http://education.hp.com U1610S B.00 10-15 2003 Hewlett-Packard Development Company, L.P. Module 10 Internal Database To minimize the disk space needed for the archived transaction logs, wait until at least one cycle of full backups has been completed within the cell before enabling Archiving. If the names of files are already in the CDB, then the transaction logs will be fairly small. If filenames are not in the CDB, then each new filename added will add approximately 200 bytes to the logs. In a large environment, the size of the transaction logs may be substantial. The suggested approach is to enable the Archiving after most of the filenames are already recorded in the CDB. U1610S B.00 10-16 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 10 Internal Database 10–8. SLIDE: Database Size Limits (Review) Database Size Limits (Review) • File Versions (10x # of file names) • 50 directories (containing binary files) • 4 GB per directory • 10,000 files per directory • 700 Million File Names Unix (est.) DCBF CDB • 450 Million File Names on Windows (est.) (32 GB HP-UX & Windows, 30 GB Solaris) • 40,000 Media per pool • 500,000 Media MMDB • 1,000,000 Sessions (max 2,000 per day) • 100 parallel backup sessions (UX) Student Notes The Data Protector Internal Database limits were introduced in the Architecture module. They are mentioned here as a review for planning purposes. The IDB has several defined (supported) limits. These limits should not be exceeded under any circumstances. The limits illustrated on the slide are also available from the product Release Notes document that ships with the product. The file-names (fnames.dat) database file is initially limited to 2 GB, but may be extended in up to 2-GB increments to a maximum of 32 GB. The minimum extension is 1 MB per extension. The file-versions stored in the DCBF is initially limited to one directory of 4 GB, but may be extended in up to 4 GB increments to a default of 10 directories. The maximum number of DCBF directories is 50, but this requires the modification of the global option “MaxDCDirs” from the default value of 10. Each extension directory may contain up to 10,000 files; the limit for the file versions is set to approximately 10 times the number of file-names. The file versions represents approximately 80% of all the data stored by Data Protector within the IDB. http://education.hp.com U1610S B.00 10-17 2003 Hewlett-Packard Development Company, L.P. Module 10 Internal Database The size of the MMDB will only be approximately 20 MB. TIP See the Release Notes for last minute changes and further details. U1610S B.00 10-18 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 10 Internal Database 10–9. SLIDE: Recommended Distribution Recommended Distribution Tablespaces MMDB and CDB Logs Transaction and Recovery Binary File Directories Student Notes For the best performance using Data Protector’s database and for the easier recovery, it is best to separate the most active parts of the database onto separate disk volumes. Separating the tablespaces from the external binary files will increase the performance of Data Protector. It is also wise to move the transaction logs onto a different disk than the tablespaces, and make a copy of the recovery information. Depending upon the operating system of the cell manager, it may be possible to allocation another partition and then simply move the Internal Database onto the new disk space while the Data Protector servers are not running. (on UNIX systems, this could be done with symbolic links as well) It is best to relocation these directories during the installation process, when the database contains very little data. (Volume mounts can be built before the installation of the database.) http://education.hp.com U1610S B.00 10-19 2003 Hewlett-Packard Development Company, L.P. Module 10 Internal Database Relocation Strategy for the Internal Database Components CDB MMDB DCBF SMBF Transaction logs Store with the MMDB by relocating the datafiles path of the database (symbolic link or mount) Store with the CDB Manage the locations with the database maintenance commands (later in this section) Relocation done by editing the global option “SessionMessageDir” Keep in the default location if CDB, MMDB, and DCBF are relocated U1610S B.00 10-20 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 10 Internal Database 10–10. SLIDE: Managing Database Growth Managing Database Growth Choose Log Level for backup: • No logging • Log all, log file, log directory Marking database records as obsolete: • Automatically when a tape is overwritten • Automatically when retention policy is expired • Manually remove sessions (omnidb or GUI) Purging Invalid records from the database: • Automatically by admin daemon (scheduled) • Manually with "omnidbutil -purge" command Shrink the database to its minimum size: • omnidbutil –writedb/-readdb command Student Notes The Internal Database will continue to grow, as more sessions are executed within the cell. Data Protector stores all the details of successful as well as failed sessions for later reporting. The growth and size of the Internal Database are determined by the following factors: • Catalog Detail Level The number of files and directories backed up and the level of detail held in the database to describe them (Log None, Log All, Log File, Log Directory) • Catalog Protection Time How long detail information is to be kept in the database (should be less than the media protection in most cases) • Number of Logged Messages Messages appearing in the session (message level) http://education.hp.com U1610S B.00 10-21 2003 Hewlett-Packard Development Company, L.P. Module 10 Internal Database Catalog Detail Level The most significant influence on the growth of the IDB is the addition of new clients and new files, as well as the amount of detail logged for each. During the initial configuration of the Data Protector cell, the growth and dynamics of the data will be very high. Over time, however the dynamics may average around 3%-5% per client. Clients with higher dynamics (frequently changing file names) will cause the IDB to experience substantial growth. For instance, email servers that have a high file turnover. Clients, and further objects (file systems) that reside on the clients that have very high dynamics can negatively impact the overall performance and growth of the IDB. These high dynamic clients are candidates for reduced catalog data logging during backup. The selection of “Log File” or “Log Directory” will prevent the unnecessary storage of file version information for dynamic files. The files will be recoverable from tape, but their details will not need to be stored in the database, as they are unlikely to be requested individually. Typically restore by object, or restore by directory is used to put back the files onto the system. Recall (from the backup chapter) that the “Log File” option reduce about 70%, and the “Log Directory” option will reduce about 90% of the file information that is stored. Catalog Protection Time Data Protector allows you to set protection for data backed up and backup catalog information independently. This allows the physical data protection of backup objects on media to be different from the related catalog information for the same objects stored in the Internal Database. Setting the catalog retention time to a period lower than the physical protection time can be useful. For example, if media is required to be kept for a long time span, but realistically, will not be required for restore (archives, etc), the catalog can be kept for only one month, while the data on tape is protected for 3 years. If the catalog protection is set equal to that of the media protection, then the IDB will continue to grow rapidly. The protection of the catalog for particular sessions may be altered in the database by using the GUI or the command line. Changing the Number of Logged Messages The number of logged messages can be controlled in various ways depending on the source of the messages. One source of messages is output from pre/post exec scripts. These messages, by default, appear on stdout, and thus will appear in the session log. If a pre/post-exec script is generating large numbers of messages for each backup, it can take up a large amount of space in the database. Such information can be reduced by either reducing the verboseness of messages or by redirecting them to a logfile. Messages generated by Data Protector itself during the backup operation are another source. Setting the message filter level (Normal, Warning, Minor, Major, and Critical) can control the number of such messages. U1610S B.00 10-22 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 10 Internal Database Data Removal from the IDB Removal of data from the Internal Database should be automatic. As detail catalogs are expiring, and as tapes are overwritten (once protection expires) Data Protector will automatically purge the obsolete data from the database by executing an Admin Session Manager (ASM) according to a pre-defined schedule. The global option file contains the parameter “DailyMaintenanceTime” to control when the ASM executes. The default time is 12:00 (noon). A typical purge session will last for several seconds while obsolete DCBF and SMBF files are removed for the expired media. The manual invocation of a purge may still be needed. The omnidbutil command provides several options to control how this type of data purge will execute. Data Protector has two features that will help determine if an additional purge is needed. They include a purge report as well as an automatic notification. The chapter on Reporting and Notifications will cover both in more detail. Additional maintenance includes shrinking or extending the database. Shrinking is only useful if too much disk space has been consumed, and data removal is desirable followed by a database reduction. Extending the database is necessary if either of the parts of the CDB or DCBF is nearing the initial limitations. http://education.hp.com U1610S B.00 10-23 2003 Hewlett-Packard Development Company, L.P. Module 10 Internal Database 10–11. SLIDE: Internal Database GUI Internal Database GUI Disk volume space Student Notes Keeping tabs on the disk space consumed by the IDB is very important. Database corruption could occur if the disk fills up before a transaction is completed. Data Protector provides sufficient tools to allow advanced monitoring of the space consumption for its database. Frequent monitoring is highly recommended. Data Protector has several built in features to aid in the monitoring of the database: • Built-in size graphs • Event logging and notification (database full event) • Scheduled monitoring via reports • Web Based reporting tools Shown above is the size-graph available within the database context of the GUI. Each of the icons within the Scoping Pane within the MMDB and CDB components support the graph tools. U1610S B.00 10-24 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 10 Internal Database 10–12. SLIDE: IDB Size Report IDB Size Report 1 3 2 Student Notes In addition to the graphs, Data Protector provides pre-configured reports to show the physical size and usage of the internal database components. The Reporting context in the Scoping Pane has several reports available under the Tasks menu tab. The report shown above should be frequently executed to monitor the growth of the database. The amount of maintenance needed for the database will largely depend upon the rate of growth and length of time that the data needs to be kept. http://education.hp.com U1610S B.00 10-25 2003 Hewlett-Packard Development Company, L.P. Module 10 Internal Database 10–13. SLIDE: Database Maintenance Database Maintenance Reasons: • Low disk space • File version purge • Filenames purge • DB size management • DB corruption Student Notes There are several maintenance tasks required to keep the IDB running smoothly. They include: • Monitoring for devices with low disk space (where the database is stored) • Ensuring that regular purging of obsolete data is occurring • Periodically purging the file names tablespace (CDB) • Monitoring for high client dynamics, and making adjustments to the backup specifications • Monitoring and managing the regular growth of the IDB • Preventing corruption, or detecting it early before major problems occur The rest of this section will deal with the commands that are provided with the cell manager to manage, monitor and maintain the IDB. These maintenance commands will allow for relocation and allocation of additional space for the DCBF. U1610S B.00 10-26 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 10 Internal Database 10–14. Text Page: Data Protector Commands Database Commands Data Protector provides several commands for access to and control of the database. The commands are: omnidbinit omnidbcheck omnidbrestore omnidbutil omnidb omnicellinfo Initialize the database and erase all data in it Check the physical consistency of the database. Automated recovery of the database Maintain the database. Query and modify the database Query the database There is a section at the end of this module containing an overview of the database related commands and examples for their usage. http://education.hp.com U1610S B.00 10-27 2003 Hewlett-Packard Development Company, L.P. Module 10 Internal Database 10–15. SLIDE: Database Cleanup Database Cleanup omnidb -purge … omnidb -strip … Student Notes The GUI provides many database maintenance features and actions. Removal of session, session messages, and session versions are provided. The functionality here behaves the same as the omnidb command. See the omnidb man-page or the command reference section lager in this module for details of the selected choices and some examples. NOTE The GUI allows for the selection of multiple sessions as targets for the operation. U1610S B.00 10-28 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 10 Internal Database 10–16. SLIDE: Adding Filename Extensions Adding Filename Extensions Up to 2047 MB per extension omnidbutil -extendfnames <path> -maxsize <MB> Student Notes When the size of the fnames.dat table is insufficient for the needs of the cell, the administrator must extend it. This extension is typically done via the GUI as shown above, but may also be performed from the command line. The omnidbutil command introduced in the slide, is covered by a reference section near the end of this module. Each extension to the fnames.dat may range from 1-2047 MB in size. It is generally recommended to keep all of the extensions within the same directory structure, that is, within the <OMNIVAR>/db40/datafiles/cdb directory. http://education.hp.com U1610S B.00 10-29 2003 Hewlett-Packard Development Company, L.P. Module 10 Internal Database 10–17. SLIDE: Adding DCBF Locations Adding DCBF Locations omnidbutil -add_dcbf <path> … Student Notes It is desirable in larger cell environments to have more than a single directory used for the storage of the DCBF. Data Protector allows for a maximum of 50 directories, but has an initial limit set to 10 by a global option (covered earlier). The new DCBF may be created and initialized via the Internal Database GUI, or by using the omnidbutil command. When using the omnidbutil command, there are additional options for relocating the DCBF, as well as removing the DCBF. Refer to the omnidutil reference near the end of this module for examples. U1610S B.00 10-30 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 10 Internal Database 10–18. SLIDE: Preparing for Database Recovery Preparing for Database Recovery Considerations: Considerations: •• Distribution Distribution •• Transaction Transaction logging logging •• Backup Backup Student Notes Internal Database recovery may be necessary if omnidbcheck reports critical or major corruption to some parts of the database. Preparation is necessary if you are to recover the previous non-corrupted database. Data Protector supports several different recovery possibilities including: • • • Removing the parts of the database that report “Minor” corruption Restoring the database from backup tape (servers running) Restoring the database without the server processes running (crs, rds) The choice of which type of recovery is needed depends upon preparation and the report output from the omnidbcheck command. Corruption reported as Major or Critical will require some form of recovery. Corruption that is Minor allows for removal of the corrupted data, and then continued operations; recovery of the data is optional and in some cases unnecessary. http://education.hp.com U1610S B.00 10-31 2003 Hewlett-Packard Development Company, L.P. and therefore.00 10-32 2003 Hewlett-Packard Development Company. Backs up all the database extension files if they exist. and must be used in order to obtain a consistent backup. Backup all Data Protector configuration data that is stored in the database and flat files.P. and schedules. http://education.5 hours for a 10 GB database) Online backup while the database is being used. must be protected! •• A Aspecial specialobject objecttype typeOMNIDB OMNIDBto tobackup backupthe the internal database is provided internal database is provided •• The TheOMNIDB OMNIDBobject objectmay maybe beincluded includedin ina abackup backup specification specification •• The Theconfiguration configurationand anddatabase databaseare areboth bothincluded included in the OMNIDB object in the OMNIDB object •• A A“hot “hotbackup” backup”is isperformed performed •• Consistency Consistencycheck checkperformed performedbefore beforebackup backup (default=on) (default=on) Student Notes The database is an extremely important part of Data Protector.com . A normal file system backup is not sufficient! Only one database backup can run at a time. this takes about 1. and must be backed up regularly. A special object type of OMNIDB is provided. (-quick enabled by default. backup specifications. Therefore.hp. • • • U1610S B. other backup or restore sessions can run while the database is being backed up. Data Protector also performs the following: • Checks the integrity of the database before backup. L. SLIDE: Back Up the Database Backup the Internal Database The internal database is a critical component.Module 10 Internal Database 10–19. thus preventing back up and restoration of a corrupted database. During the Internal Database backup. including data on devices. Make sure you know which media you use for a database backup.00 10-33 2003 Hewlett-Packard Development Company. This simplifies scheduling and restoring in case of a disk crash. You can set the data and catalog protections to only a few days. Keep at least two copies of the database backup tapes. Modifying the object properties can disable the automatic database check that is performed prior to backup of an OMNIDB object. Checking before Backup You should always check your database before backing it up. In this case. on a specific device. Manually checks the database integrity with the omnidbcheck command. a manual check scheduled with the system scheduler may be a better option. Create a separate backup specification for the database. . (use of standalone devices is preferred in case of a disaster. Schedule a database backup every night. The scheduled check should not be performed while there is any other Data Protector activity. 3. L.Module 10 Internal Database We recommend the following procedure to back up the database: 1. Checking the Integrity of the Database The integrity of the Internal Database is extremely important. 2. This greatly simplifies eventual restore. so you can recover it and the backed up data in case of a disaster. http://education. It is important that the database you back up is consistent. Data Protector provides the following functionality: • • Automatically checks database integrity before each backup.com U1610S B. Only one database check at a time can be run on the database. It may be necessary to disable the automatic check if the database is very large and the check takes too much time. they are easier to configure for the restore process) 4.P. To maintain the integrity. Data Protector by default checks the integrity of the database before the database is backed up. since you know precisely on which medium your database is backed up. Make the database backup using a separate media pool on a separate media.hp. This ensures that you always have an up-to-date backup of the database. 00 10-34 2003 Hewlett-Packard Development Company. SLIDE: Manual Restore of the Database Manual Restore of the Database rds.hp. Data Protector is the only product that will read the Data Protector tapes.com . mmd Data base Internal Database CDB te ca o l e- restore -into Temp Directory R MMDB CDB MMDB te loca Re- Student Notes The restore of the Internal Database must be accomplished in a series of steps.Module 10 Internal Database 10–20. in this case additional steps are needed in order to proceed with the restore. because it is not possible to do a "hot-restore" of the data with this method. L.P. It is possible that the restore of the Cell Database may be onto a different system than the original Cell Server (Manager) system. crs. http://education. that is to say. Why would you need to restore the Internal Database? • • • Corruption Recovery due to loss of data Restore of failed Cell Server Database Restore U1610S B. All restore operations in Data Protector require that Data Protector is operational. " Discovering the Medium Containing the IDB Backup The following procedure requires that the most current IDB backup is known and available.log file stored on the Call Manager holds the answer. so what can be done if the medium ID is not known? The <OMNIVAR>/log/media.hp. Import the tape into the existing (new) IDB. "Reconfiguring a Corrupted DB. (This is not needed if the database is still operational and contains the session information from the desired backup session. Each medium access is recorded within this log file and will prove useful in the case of a loss of the IDB. see the next topic. It is a good practice to print this log file regularly so that it will be available in the event of a Cell Manager disaster.Module 10 Internal Database The process below will assume a recovery onto a newly installed Cell Manager System or after a disaster recovery of the Operating System. If the rds is unable to be started due to database corruption. the Database may need to be re-initialized so that it is operational prior to the restore.) This may require the configuration of a new Logical Device if a new database was created. Consult the media log for the medium ID if it is not known. . Procedure 1. Restoring the IDB The following procedure will restore the Database to the Cell Manager system. just don't overwrite the existing active database.com U1610S B. rds. this requires that the Database Server (rds) is running. 2. (you may be able to restore into the partition or directory where you have located the “db40”. This procedure may also be used to restore the database to a previously non-corrupted state. Restore the desired backup session data onto the system in an alternate location using the "into" feature of Restore. since you will likely have available disk space there. The procedure assumes that you have a Logical Device and Media Pool already configured for use.P. L. Requirements • • • • • Running Cell Server (crs. "db40" directory) http://education. mmd) Operational Database (not corrupted. Use the omnidbinit command to initialize the database if necessary. may be empty) Configured Logical Device Configured Media Pool Sufficient Disk Space Overview: Depending upon the condition of the Cell Server and Database. into a Media Pool using a Logical Device. This information is stored within the IDB.00 10-35 2003 Hewlett-Packard Development Company. before the parts may be distributed. Verify that the database and all of the configurations are operational. instead of the entire db40 directory is supported. http://education. The restore process also restored the configuration files into the same location as the database files. L. mmd. It is advisable to have a disk layout that is conducive to this type of restore. omnisv -start 7. just the contents of the database and configuration files and directories.Module 10 Internal Database 3. which relocate the database while it is restoring the data. Move/rename the current database to a temporary name. stop the Data Protector servers. The disk layout that was present at the time of the backup must be manually recreated first. rds not running.com .hp. Do not relocate the database with the servers running! omnisv -stop 4. In other words. Data Protector will not re-create mount points and/or symbolic links.00 10-36 2003 Hewlett-Packard Development Company. Manually relocating the parts of the database. Data Protector does not backup the disk layout. After the "restore .bkup mv <location>/db40 /var/opt/omni/db40 (where <location> is the full path to the restored database directory (eg. U1610S B. mv mv /etc/opt/omni <location>/omni /etc/opt/omni. the database will be moved! On the slide. Be sure to stop all GUI's and sessions before proceeding. You may want to move them into place as well if they need to be recovered (this step may be optional. this is indicated as the crs.P. omnidbcheck … Disk Space Consideration There will need to be a substantial amount of available disk space for this procedure.bkup /etc/opt/omni 6. Start the Data Protector Servers using the newly recovered database.into" has completed. Not considered in the above procedure is the possibility that some parts of the database reside on separate disk volumes. then move the restored database into place. mv /var/opt/omni/db40 /var/opt/omni/db40. HP-UX)) 5. if the files are intact). hp. SLIDE: Manual Restore Using the GUI Manual Restore Using the GUI Student Notes This essentially the same as the previous manual procedure. http://education.00 10-37 2003 Hewlett-Packard Development Company. L. After using this task. . but only takes into account the actual restore process.Module 10 Internal Database 10–21.P. and not the activation of the restored database.com U1610S B. follow the manual steps outlined previously. The omnidbrestore command executes several steps necessary to recover from a damaged IDB. it is still possible to restore the database in place by using the command omnidbrestore. but some key preparation is required. The general steps performed by omnidbrestore are: • Stop the daemons/services • Read recovery information from the existing obrindex.hp. http://education. CAUTION The existing IDB will be overwritten by this recovery process.00 10-38 2003 Hewlett-Packard Development Company.Module 10 Internal Database 10–22. L.dat options • Prompt for the replay the transaction logs (roll forward) • Restart the daemons/services U1610S B.com .P. In the case of the cell server being inoperable. and the cell server processes are operational. SLIDE: Automated Restore of the Database Automated Restore/Recovery Process Overview • Stop daemons/services • Read recovery information • Restore database session • Log replay (roll forward) • Start daemons/services omnidbrestore omnidbrestore–autorecover –autorecover[[ … … options] options] Student Notes The previous recovery sequence was required if the entire database is replaced. This is the preferred choice for database recovery.dat • Restore the database from the latest backup session using the obrindex. Module 10 Internal Database Preparations must be made in advance if this type of restore is to be successful. RMA. especially the configuration of a second copy for the obrindex. Good preparation should help to avoid this more difficult type of restore. . This is only an issue if the transaction log exceeds 2 MB before the next IDB backup.0 software installed Copies of the latest IDB backup tapes The original device used for the IDB backup. Follow the preparations mentioned earlier in this section.dat file is not available.00 10-39 2003 Hewlett-Packard Development Company.hp. Read mode: -read The read mode reads from a file created with the –autorecover –save <file> options.com U1610S B. L. as well as the name for the transaction log from the last IDB backup which is used for the restore. or attached to a different system. Requirements for automated recovery • • • Data Protector 5. The omnidbrestore utility supports three modes: Autorecover mode: -autorecover In this mode the obrindex.dat file. In this case the <file> may be manually updated with the appropriate restore device information. Manual mode: This manual mode is used when the obrindex. and VRDA options needed. See the man page for omnidbrestore for all the details. http://education. This is mostly used when the original device for the backup is not available for the restore. loaded with the tape The omnidbrestore Utility The ability of the omindbrestore utility to replay the transaction logs may depend upon the Archiving parameter being enabled.dat file.dat file is scanned for the media. All of the options needed for a restore must be specified manually. and then used instead of the obrindex.dat file must be available. The obrindex.P. but requires changes. in which case the transaction log would be overwritten or archived according to the state of the Archiving parameter. When the options are retrieved. the database is automatically retrieved from the last backup tape using the same physical device that the backup was executed with. U1610S B. SLIDE: Recovery from Corruption Recovery from Corruption newconfig! Internal Database CDB MMDB The Thedatabase databasemust mustbe beoperational operationalin inorder order to manually restore the database from to manually restore the database fromtape tape Student Notes The corruption of the Internal Database is rare.P. http://education. L. but it is comprised of files and directories.com .00 10-40 2003 Hewlett-Packard Development Company.Module 10 Internal Database 10–23. There may be some circumstances where the Database Server (RDS) is unable to start due to a corrupted database. Recovery from corruption There are three classes of error reported by omnidbcheck that need to be addressed: Critical: Major: Minor: Reported when the core IDB is corrupted Reported when the filenames detail is corrupted Reported when there are problems with the DCBF Each of the three mentioned above is recoverable. with the proper preparations.hp. When this occurs you are likely to need to restore the Internal Database using the procedure previously discussed. and is stored within a filesystem. The database will appear as to have been created with backups using the “No Log” option. The omnidbutil –writedb –no_detail. if the manual restore is used. 4. Import the media that had the corrupted DCBF file (1 file is used per medium) To replace the corrupted files: 1. Execute the omnidbcheck –bf to get the <medium_id> of the missing files 2. L.dat. All new backups may use the “Log All” option to create new DCBF entries.P. Then recreate the DCBF files by importing the media that was deleted. a copy of the database directory structure was placed within the <OMNIHOME> directory called “newconfig. and not recreate the database if it is on the system already. Execute the omnidbutil –fixmpos to establish consistency within the IDB 6. If these files are missing.00 10-41 2003 Hewlett-Packard Development Company. Identify the corrupted files. The file representing the medium will have “_” characters in place of the “:” character as reported by the omnidbcheck output. then restore will report errors when browsing.” The newconfig/db40 http://education.Module 10 Internal Database Critical To recover from critical level corruption. the IDB may be recovered from tape (preferred) or restored by exporting and importing the current database without the details.hp. removal of the files in the DCBF may be performed. To replace the missing files: 1. the contents of the DCBF may be removed. Major To recover from major level corruption. Minor To recover from minor corruption. Import the media that had the corrupted DCBF file (1 file is used per medium) Creating a New Database There is one major issue that needs to be resolved. Execute the omnidbcheck –dc to get the <medium_id> of the corrupted files 2. Execute the omnimm –media_info <medium_id> to obtain the tape label and location information 3. the IDB will need to be recovered from tape using either of the previous procedures for recovery. . Execute the omnimm –media_info <medium_id> to obtain the tape label and location information 3. as they are no longer referenced. Execute the omnidbutil –fixmpos to repair the corruption 4. You may be tempted to re-install Data Protector.com U1610S B. During the installation of Data Protector. This recovery operation will take approximately 5-20 minutes. followed by an omnidbutil –read_db will recreate the database without the file detail catalogs. you will need to have an operational database to restore Data Protector. Remove the corrupted DCBF medium files 5. since Data Protector will assume that you are performing an upgrade. but this will not succeed. Once the omnidbutil –read_db completes. The Database Server also must be running in order to perform the omnidbinit to initialize the database. the names will be <medium_id>_<timestamp>. Verify the fileset status is installed: swlist -a state -l fileset DATA-PROTECTOR 5.com . http://education. Procedure to Remove and Recreate an Internal Database 1. uninitialized Internal Database. Un-configure the Data Protector product filesets: swconfig -u DATA-PROTECTOR 4. This would be necessary in those cases when omnidbinit is unable to communicate with the database server (RDS). you may use the SD-UX commands to force Data Protector to recreate the database. To use it.P. they should be configured: swlist -a state -l fileset DATA-PROTECTOR 3.00 10-42 2003 Hewlett-Packard Development Company. copy it into the correct location. which will create a new database to allow for the execution of the restore procedure. without re-installing from the product media. Stop the Data Protector Servers (be sure to exit all Data Protector GUI's and sessions): /opt/omni/sbin/omnisv -stop 2. Configure the Data Protector filesets to create a "new" database: swconfig DATA-PROTECTOR 7. The swconfig command will allow us to un-configure and then re-configure the Data Protector product. L. HP-UX Specific Feature When your Cell Manager is HP-UX. and use the omnidbinit command to initialize it.Module 10 Internal Database directory is a new. Check the state of the Data Protector product filesets. Remove the corrupted database: rm -r /var/opt/omni/db 6. Then start the manual recovery process as indicated earlier. Verify the configured state of the filesets: swlist -a state -l fileset DATA-PROTECTOR U1610S B.hp. sh -start 9.P. Follow the restore procedure discussed earlier to restore the Internal Database from the latest backup.Module 10 Internal Database 8. NOTE This procedure may be used to create a new.hp. L.com U1610S B. http://education.00 10-43 2003 Hewlett-Packard Development Company. . empty database that may quickly be enabled to allow for a restore of the database from tape. Start the Data Protector servers: /opt/omni/sbin/omnisv. L.sys@na168w2 2000/04/18-2 Backup Completed root.00 10-44 2003 Hewlett-Packard Development Company.sys@na168w2 2000/04/20-2 Backup Failed root.Module 10 Internal Database 10–24.sys@na159w10 2000/04/18-1 Restore Failed root.sys@na168w2 2000/04/20-3 Backup Completed root. http://education.sys@na159w10 2000/04/13-6 Backup Completed root.com . Example 1: Listing sessions from the database omnidb -session SessionID Type Status User.hp.sys@na159w10 2000/04/13-5 Backup Completed root.sys@na168w2 Example 2: Listing a specific session from the database omnidb -session 2000/04/20-3 Object Name Object Type Object Status ======================================================================= na168w2:/tmp 'practice-command' FileSystem Completed Example 3: Listing details of a specific session from the database omnidb -session 2000/04/20-3 -detail Object name : na168w2:/tmp Object type Object status Started Finished Object size Backup mode Protection Catalog retention 'practice-command' : FileSystem : Completed : Thu Apr 20 14:43:55 2000 : Thu Apr 20 14:44:17 2000 : 6528 [KB] : Full : Protected permanently : Protected permanently U1610S B.sys@na159w10 2000/04/13-4 Backup Completed root. which may be performed on individual items within the database. TEXT PAGE: omnidb The omnidb Command (reference) The omnidb command provides several important capabilities for database maintenance. omnidb is a general-purpose query tool used to gather information from the database.sys@na159w10 2000/04/13-2 Backup Completed root. however omnidb is also able to make some modifications to the existing session records. Primarily.P.sys@na168w2 2000/04/20-1 Backup Completed root. This module is primarily about maintenance. This section will provide some brief examples so that the basic format of data stored in the database will be understood.sys@na159w10 2000/04/13-3 Backup Completed root.Group@Host ==================================================================== 2000/04/13-1 Backup Completed root. In the first case. The date form is [YY]YY/MM/DD. In the first case. same_as_data_protection.P. the time interval is the number of days (after today) during which the data cannot be overwritten. the value is the date until which the data is protected. Example: Change the protection of a session from permanent to 30 days omnidb -session 2000/04/20-3 -change_protection days 30 omnidb -session 2000/04/30-3 -change_catprotection days 30 http://education. you must specify the value. it changes protection for all Failed/Aborted objects. When the protection is until a specified date or for a time interval. you must specify the value.hp. When the protection is until a specified date or for a time interval. L. In the second case.com U1610S B. or for a time interval.00 10-45 2003 Hewlett-Packard Development Company. Protection can be none.Module 10 Internal Database Access Number of warnings Number of errors Device name : : : : Private 0 0 dlt_drive1 Example 4: Listing details of a specific object from a session in the database omnidb -session 2000/04/20-3 -filesystem na168w2:/tmp 'practice-command' Started Finished Status Object size Backup mode Protection Catalog retention Access Number of warnings Number of errors : : : : : : : : : : Thu Apr 20 14:43:55 2000 Thu Apr 20 14:44:17 2000 Completed 6528 [KB] Full Protected permanently Protected permanently Private 0 0 Other Options for omnidb -change_protection Protection Changes the current protection of the object versions identified by ObjectName and/or SessionID to the new protection defined as Protection. In the second case. permanent. or for a time interval. -change_catprotection Protection Changes the current protection of the catalog retention time. Protection can be none. . same_as_data_protection means that the catalog will stay until data is overwritten or exported. the value is the date until which the data is protected. until a specific date. The date form is [YY]YY/MM/DD. until a specific date. If it is specified without any other option. the time interval is the number of days (after today) during which the data cannot be overwritten. There are three aspects to record selection. L. It will still be possible to restore from this session until the media used is overwritten.P.com . at that time the session data will become obsolete.00 10-46 2003 Hewlett-Packard Development Company.hp. sessions and session messages. Stripping Catalog Detail You can mark detailed data for removing using the omnidb -strip command. Example: omnidb -session 2000/05/01-1 -purge U1610S B. with various options. All objects within a session will be marked as unprotected.Module 10 Internal Database Database Maintenance Commands The omnidb command may be used to select (mark) data to be removed from the Internal Database. http://education. detail catalogs. there are four possibilities: • • • • strip the detail catalogs of all the objects in a session strip the detail catalogs for a specific object within a session strip the detail catalogs on all unprotected objects strip the detail catalogs for an object older than a specific number of days Examples: using omnidb -strip • all unprotected objects in the database: omnidb –strip • all objects within a session omnidb -session <session-id> -strip • a specific object within a session omnidb -session session-id -filesystem host:/mnt 'description' -strip • a specific object older than 30 days omnidb -filesystem host:/mnt 'description' -strip 30 Purging Sessions The omnidb command may also be used to purge an entire session from the database. http://education. L.00 10-47 2003 Hewlett-Packard Development Company. Purging the CDB does not actually shrink the size of the files. as well as obsolete (overwritten) backup sessions. and sessions without any media. You must execute the omnidbutil command with super-user (root/administrator) privileges from the Cell Manager system only.P.com U1610S B. or as a result of running omnidbutil as described next The following command can purge information relating to restore sessions. . The omnidbutil command offers the following general capabilities: • • • • • • Removal of Obsolete Data from the Database Reporting on Database Usage Operations on Detail Catalog Binaries Files and the CDB Device and Session Control Synchronization of the MMDB and CDB (within the MoM environment) Other Miscellaneous Cell Tasks Removing Obsolete Data from the Database Data Protector automatically removes obsolete information from the CDB at regular time intervals (see the Purge Schedule topic below). The data previously selected (marked) for removal by omnidb will be permanently removed from the database by this purging process. such as failed or aborted sessions.hp. TEXT PAGE: omnidbutil The omnidbutil command (reference) The omnidbutil command has several different uses. all associated with the database.Module 10 Internal Database 10–25. Purging data is essentially a two-step process: First: data must be marked as obsolete This happens as catalogs expire or via the omnidb command Next: data must be removed This happens automatically at maintenance time. it merely makes space for new information. Purging removes unneeded information from the database and frees space for new information. A purge session manager (ASM) will execute based upon a schedule.com . such as the names of each file being backed up during each session. Purge Schedule The default installation of Data Protector includes automatic database purging. You may notice the ASM running if the monitor context is available while it is running.hp. The -info as well as the -extendinfo options for omnidbutil report on table and record usage for the database. http://education. L. The restore of single files is slower when the data about the file is not in the database. The default schedule calls for a standard purge every day at 12:00 (noon).Module 10 Internal Database Examples: starting a purge session manually: omnidbutil -purge Removes: • obsolete file names. in the CDB. The purge (maintenance schedule) is controlled by the global options file parameters. you should also verify that the disk space where the database is located is not full. session messages and objsolet DCBF files Removes: • restore sessions and obsolete backup sessions older than <n> days Removes: • obsolete file versions (DCBF) for all media with expired catalog protection omnidbutil -purge –days <n> omnidbutil -purge -dcbf omnidbutil -purge –filenames (requires exclusive access) Removes: • obsolete file names (files with no DCBF files Data Protector records detailed data.P. You can create space for new data by removing this data from the CDB.00 10-48 2003 Hewlett-Packard Development Company. You can remove detailed data for a backed-up object in one specific backup session. Reporting on Usage Monitoring the size of the Internal Database if very important. restore and backup sessions. In addition to table size. U1610S B. this would be fatal to the database server. this is because Data Protector has to search for the file from the beginning of the media Data Protector normally tracks file positions on tape in its database. close monitoring of the usage for the DCBF is needed to ensure continued smooth backup operations.dat The omnidbutil command can create new extended fnames. extended fnames. their size cannot be reduced.dat files where new data is to be stored. and the maximum size of the data table is 32 GB.datN file in the specified directory. It is important to plan the location of database extension files carefully. when client dynamics are usually the highest.00 10-49 2003 Hewlett-Packard Development Company. For example: omnidbutil -extendfnames /var/opt/omni/db40/datafiles/cdb -maxsize 500 This command creates an additional database file in the same directory as the original database. The database extension files are backed up as part of the database backup and are restored with database recovery. run the following command: omnidbutil -extendfnames pathname -maxsize size Where pathname is the full path to the directory where the new database files will reside. This is especially important in the first year of operations. The maximum size of each new file extension is 2 GB. (typically <OMNIVAR>/db40/datafiles/cdb) and size is the size of the database extension file in MB (range 1-2047 MB per extension). Once you define the extended fnames. To verify the sizes of the tables created. thus giving a full database size of 2.P. each time you run the command.Module 10 Internal Database Extending fnames. Example: Listing the existing DCBF directories: omnidbutil –list_dcdirs http://education.hp. The limits for the DCBF mentioned earlier should not be exceeded.5 GB.com U1610S B.dat files. and extends the size by 500 MB. . Data Protector creates a new. The directory for the extension must already exist. On the cell server. us the following command: omnidbutil –extendinfo Managing the DCBF There are several possibilities for managing the DCBF: • Listing existing DCBF directories • Adding additional DCBF directories • Relocating the DCBF directories • Removing invalid references to the DCBF (after a recovery) Adding Additional DCBF directories Using the reporing mechanisms in the GUI. L. P.Module 10 Internal Database Example: Adding (creating) an additional DCBF directory omnidbutil –add_dcdir <path_name> omnidbutil –modify_dcdir <path_name> Additional options: -maxsize -maxfiles The maximu size of the DCBF directory (limit 4096) The limit of files in the DCBF directory (limit 10000) The minimum amount of disk space needed to use the DCBF directory (default 100) Assign the usage sequence to the DCBF directory <MB> <n> -spacelow <MB> -seq <n> DCBF Directory Selection Data Protector provides three different algorithms for use of the DCBF directories. L.00 10-50 2003 Hewlett-Packard Development Company. The choice of algorithms is made by changing the “DCDirAllocation” parameter in the global options file. http://education.. rename on Windows) omnisv -start omnidbutil –remap_dcdir U1610S B. Note you must have exclusive access to the database for the following (no sessions or GUI’s running): 1) 2) 3) 4) 5) omnidbutil –add_dcdir . and then simply inform Data Protector of such a move. Use the following procedure for relocation of DCBF entries. omnisv –stop <move the files> (use mv on UNIX.. Data Protector chooses an appropriate directory to use. Moving DCBF contents It is possible to manually relocate (first) the DCBF entries. The values used for the parameter are: 0 1 2 (default) use the sequence number or order of the DCBF directories balance the use of the DCBF directories based upon size balance the number of entries within the DCBF directories Data Protector first determines which DCBF directories are still useable (those not already exceeding any limits).hp.com . The DCBF directory is considered full when any of the following is true: Maximum_size – Current_Size < Space_Low Disk_Space < Space_Low Current_Files >= Maximum_Files Based upon the algorithm selected. and then read it back. restores. . it merely removes obsolete or detail data. Use the following command to copy the database to a set of ASCII files.hp. To ensure the integrity of the database. the only possible way is to copy the database to an ASCII file. be sure that backups. or both. Data Protector does not really shrink the size of the database.com U1610S B. You will be prompted to archive (copy) the DCBF and SMBF before omnidbutil removes exclusive access to the IDB. MMDB.Module 10 Internal Database Removing DCBF Directories To remove a DCBF directory. omnidbutil -writedb [-mmdb <directory>] [-cdb <directory>] [-no_details] Example: write the database into the mmdb and cdb directories under /tmp: mkdir /tmp/mmdb mkdir /tmp/cdb omnidbutil -writedb -mmdb /tmp/mmdb -cdb /tmp/cdb NOTE Writing the database out in ASCII format requires approximately 20% more disk space than the current database size. Copying the Database to ASCII Before you copy the database to an ASCII file.P. You must specify which part of the database you want to copy. use the following procedure: 1) 2) 3) 4) 5) omnisv –stop <move the files to another DCBF directory> omnisv -start omnidbutil –remap_dcdir omnidbutil –remove_dcdir <dir_name> (will fail if not empty) Shrinking the Size of the Database By using the purge procedures discussed earlier. Is it Feasible to Shrink the Database? You can use the omnidbutil -info command to see how many records are actually used and how many are occupied by data. If the size of the tablespaces must be reduced. it is feasible to shrink the database. and create more space for new data. If a high number of records are unused. or GUIs are not running. we recommend purging the database to remove obsolete data prior to the export. before copying the database. http://education. L. CDB.00 10-51 2003 Hewlett-Packard Development Company. -changebdev from_devname to_devname This option is used to change the default restore device that will be used to restore each backup object. If something happens in Data Protector that causes some processes to hang. This is useful if the device used for backup is no longer available. a running session backing up the database may be cleared (failed) and then removed. and frees up every database resource the process is using. Other Options to omnidbutil: -purge_stop Stop a running purge process.com .hp. If needed. the device is set to the device that was used for the backup.P. While most restore operations allow the device to be changed. This command should be used after moving databases from one cell server to another and after -readdb of files that were created on another cell server. Therefore.00 10-52 2003 Hewlett-Packard Development Company. The old_host option must be specified after -readdb of files that were created on another cell server. L. this process may block the Internal Database. In this case. http://education. (see the section on database restore) U1610S B. If the old_host option is not specified. this command must be used.Module 10 Internal Database Reading the Database from ASCII Reading the database from the ASCII file. Use the following command to read the database from an ASCII file. -change_cell_name [old_host] This option changes the owner of the catalog database to the current cell server. omnidbutil -readdb [-mmdb <dir>] [-cdb <dir>] [-no_details] Example: read from the mmdb/cdb directories under tmp omnidbutil -readdb -mmdb /tmp/mmdb -cdb /tmp/cdb NOTE If you encounter problems with the “omnidbutil –readdb” command. -show_cell_name Reports the owner of the catalog database. By default. the clear option is used. This is also useful after a restore of the database from tape. This option kills any running Data Protector process. database restores such as Oracle/SAP provide no such mechanism. omnidbutil tries to get the previous owner of the catalog database (old host) from the database itself. -clear This option is used to bring the Internal Database back to a consistent state. you may have to first initialize the database with the omnidbinit command. loses any data written to the database after it was copied to the ASCII file. use the instructions in the next section to enlarge the size of the database. It also changes all references in the (central) media management database from old_host to current cell server. like the backup session manager (BSM). Make sure that the database is large enough for data in the ASCII file. This is the manual version of the automatic de-allocation feature of media management.Module 10 Internal Database -free_pool_update Transfer unprotected media from the backup pools to the free pool.00 10-53 2003 Hewlett-Packard Development Company.hp. This is normally executed during the day automatically. and is controlled by the global option: “FreePoolDeallocFreq”.com U1610S B.P. . L. http://education. see the man page. NOTE For more details on the omnidbutil command. For this. The omnidbcheck command should be run frequently to ensure continued operations of the database. Errors found during the check process may require a repair or rebuild of the database. file names.00 10-54 2003 Hewlett-Packard Development Company. It can be used to reset Data Protector to its default state. Options for omnidbcheck: • • • • • • • • Core (checked as part of the daily maintenance with backup) File names BF (binary files) DC (detail catalog) SMBF (session messages) Sibf (serverless integration) Quick (core. file names. Early detection of problems is very important. SMBF. omnidbcheck The omnidbcheck command checks the consistency of all or parts of the Internal Database. Several different options exist to allow for full or partial checking of certain sections of the database. This command is useful if you want to initialize the database from a script.Module 10 Internal Database 10–26. The force option suppresses this prompt.com . SIBF) Time estimates for omnidbcheck: (Medium sized database at version 4. TEXT PAGE: IDB Maintenance Commands Other Database Maintenance Commands Command Locations: • • Unix: /opt/omni/sbin Windows: <OMNIHOME>/bin The directory structure for the database must exist before execution of omnidbinit.0) • Core (5-10 minutes) • File names (~1 hour) • BF (~10 seconds) • DC (~1 hour) • SMBF (no estimate) • SIBF (no estimate) U1610S B. If errors are detected. an error report is sent to the standard output. omnidbinit is automatically executed during the first Data Protector installation. the command requires exclusive access to the database.P. DC. BF. Be very careful! -force Data Protector normally prompts you to verify that you really want to delete all data in the database. omnidbinit {-force} This command is used to initialize the database and erase all data in it. BF) Extended (core. L. http://education.hp. . consistent version of the database before continuing with backups and restores.5 hours) Extended (add above estimates) Data Protector supports several different recovery possibilities including: • Removing the parts of the database that report “Minor” corruption • Restoring the database from backup tape (servers running) • Restoring the database without the server processes running (crs. Each log file will contain details of the check along with a timestamp of when the check was performed. The file names created will be the database section name with a “.00 10-55 2003 Hewlett-Packard Development Company. as more corruption may result.Module 10 Internal Database • • Quick (~1.com U1610S B.txt” suffix. If omnidbcheck detects database inconsistency. L. rds) The choice of which type of recovery is needed depends upon preparation and the report output from the omnidbcheck command. Even if the database is corrupt. it is wise to fix this inconsistency or restore an older. Some options for the omnidbcheck command are: (see the man page for more options and details) -quick Check the core. and then continued operations. Corruption that is Minor allows for removal of the corrupted data. CDB filenames. but it is not wise to do so. or as a whole. The “core”of the IDB is defined to include the following: • • • MMDB and CDB objects Object versions Media positions The database may be verified in parts. this may take several hours on a large database) http://education. The command can be also used to display the contents of the DCBF and SMBF sections of the database. and the presence and size of DCBF -extended Full check of database excluding the SMBF (full check of the database consistency including detail file information. it may still be possible to use it.hp. The log files will be written to <OMNIVAR>/log on the cell manager system. The omnidbcheck creates a log file for each part of the database that is checked.P. recovery of the data is optional and in some cases unnecessary. Corruption reported as Major or Critical will require some form of recovery. The Data Protector internal database is comprised of two tablespaces.com .Module 10 Internal Database 10–27.hp. What does the term purging mean in relationship to the database? 7. What are their names? • • 3. L. Review Questions 1. Under what directory is the Internal Database located? 2. What does the term invalid mean when describing records in the database? 6. • • • 4.00 10-56 2003 Hewlett-Packard Development Company. List three types of data that are stored in the Data Protector internal database. What would you need to add to your database to increase its capacity beyond the 2-GB limit? U1610S B. http://education.P. Name 5 parts of the Internal Database that are external to the tablespaces: • • • • • 5. Which database files are likely to be the biggest in the database. What command would you use to perform a thorough consistency check of the database? • 14. The database can be backed up as a normal file system.com U1610S B.00 10-57 2003 Hewlett-Packard Development Company.P. Which option can be set in a backup to reduce the amount of detail information stored in the database? • 13. TRUE/FALSE? http://education. L. an automatic database purge takes place every day at midday. Which file do you edit to change the purge schedule? • 11. and what information do they hold? • • 9. What command can be used to display information about database size and utilization? • 16. . TRUE/FALSE? 10.hp. By default.Module 10 Internal Database 8. What combinations of commands are required to shrink the database? • • • 15. What variables in the /etc/opt/omni/options/global file relate to the purge process? • • 12. Module 10 Internal Database 17. prior to a backup of the database? 18. Where are the Data Protector configurations stored for: • • • • Backup Specifications: Backup Schedules: Logical Devices: Media Pools: U1610S B. L. What action is performed automatically.00 10-58 2003 Hewlett-Packard Development Company. Where are the transaction logs kept? 20. http://education. What happens to the archive logs when the database is backed up? 23.hp. When should archiving be enabled? 22.P.com . What files are needed in order to recover a database? 19. How can archiving be enabled for the database? 21. you will be able to do the following: • • • • Use the report GUI.P.00 11-1 2003 Hewlett-Packard Development Company. http://education. . Create and understand the uses of report groups. L.com U1610S B.hp. Use the Data Protector reporting command line.Module 11 — Monitoring and Reporting Objectives Upon completion of this module. Use the Web Interface for reporting . Windows NT. U1610S B. SLIDE: Monitoring and Reporting Monitoring and Reporting Monitor Monitor GUI GUI •• Monitor Monitorcontext context •• Database Databasecontext context •• OpenView OpenView Reporting ReportingCommands Commands Java Java Reporting ReportingGUI GUI ARM/DSI ARM/DSIIntegration Integration Cell Database Report Report Schedules Schedules Events Events Student Notes Data Protector provides a rich set of tools and features to enable the administrator to manage the backup function effectively.00 11-2 2003 Hewlett-Packard Development Company. http://education. L.hp.Module 11 Monitoring and Reporting 11–1. Monitoring and Reporting capabilities are available from the following Data Protector tools: • • • • • • Data Protector GUI (UNIX. and to check outstanding mount requests. OpenView) Reporting commands (omnirpt) Java Web Reporting Scheduled Report Groups Event Driven Notifications (covered in the next module) ARM and DSI Integrations Various monitor functions are provided to allow the administrator to view the current and previous cell activity. This can be used to check the status of currently running backups and restores.P.com . for example. Service level reporting can be achieved by taking various metrics from Data Protector DSI (Data Source Integration) and feeding this into MeasureWare. These reports may be scheduled as report groups.hp. Notifications are sent in various forms. etc. Data Protector response times can be measured using Application Response Measurement (ARM). media available for use. http://education. Notification capability enables the administrator to be alerted of a predefined event such. such as email and SNMP. like Mount Request or Device Error. L. media used for the previous night’s backups.P.com U1610S B. .Module 11 Monitoring and Reporting Reporting capability allows generation of formatted reports against all aspects of cell operation.00 11-3 2003 Hewlett-Packard Development Company. In addition. raw. oracle…) Name (Hostname-mount point) Device (logical device) Size (in KB) Done (%) Errors number of Description text Student Notes Monitoring the status of current sessions is accomplished by using the Data Protector Monitor context. perhaps in a mount_request state. http://education.hp. L.P. From the Monitor window you can: • • Check on progress/details of current sessions (backup.com . To check the backups of last night.) Object Type (filesystem.. restore. failed. start the monitor to see if any sessions are still active. aborted. U1610S B. restore) Upon invocation.Module 11 Monitoring and Reporting 11–2. the monitor will display current active sessions. To start the Monitor only context use xomni –monitor (HP-UX) or manager –monitor (Windows).00 11-4 2003 Hewlett-Packard Development Company. SLIDE: Monitoring Current Sessions Monitoring Current Sessions Connect to another cell Detailed Information (Drill Down Session) Object Status (complete. purge) Respond to mount requests for media for an active session (backup. L. Data Protector will prompt for the cell to connect to.P.00 11-5 2003 Hewlett-Packard Development Company.com U1610S B.hp. 2000 "Attach" to a running session and monitor it interactively omnidb -session <ID> -report omnidb -session -type backup -latest omnidb -rpt -wo 2000/05/12 3600 omnidb -rpt -wo 3600 3600 omnidb -session <ID> -media omnistat omnistat -previous -last 1 omnistat -previous -until 2000/05/12 omnistat –session <ID> -monitor Question: What does the following Unix command produce? omnidb -session $(omnidb -rpt -latest |awk 'NR==1 {print }' ) –media Monitoring Multiple Cells The Data Protector cell monitor allows you to monitor multiple cells from one single location. Multi-Cell monitor capability is also provided with the OpenView Operations integration and Manager of Manager. Optionally you may start the xomni -monitor or Manager. Select the icon to change connection to a different cell manager.Module 11 Monitoring and Reporting Command Line Interface (interactive monitoring) omnidb –session omnidb -filesystem omnidb -session <ID> -detail Obtain a full listing of previous sessions Obtain a full listing of filesystem backup sessions Obtain object level detail from a particular session See the session report progress messages Show the latest completed backup session Show a summary of all of the session that ran in the last 1 hour on May 12 Show a summary of all of the sessions that ran in the last hour (3600 seconds) List media used by a session <ID> Show currently running sessions Show the sessions that ran in the last 1 day Show all previous sessions through May 12. You may use the User Manager to allow for more remote control if desired. NOTE By default. You must be already an authorized user to connect to another manager. all cell consoles will have read-only permission to other cells through a remote cell monitor. .exe -monitor with the -server <cell_manager> option to monitor a remote cell. http://education. Session Details By double clicking on one particular session. SLIDE: Viewing Previous Session Details Viewing Previous Session Details Student Notes To view the previous sessions. and you can check how long the backup took. http://education. L. You can search for messages or delete them from the Data Protector internal database to save space. Session detail information should be deleted only when it is no longer required. then select sessions to view all of the previous sessions. check the details on it. switch to the internal database context.P.hp. U1610S B. you get into the session details monitor. and perhaps restart the failed backup objects.Module 11 Monitoring and Reporting 11–3.00 11-6 2003 Hewlett-Packard Development Company. In the case of a failed session. All messages that occurred during a session are shown here as well. You can check the used media. find out what the problem was.com . you may select the failed backup session. Here you can see an overview of all backed up objects and their size. description. . the full object description is provided.P. the size of each object is displayed along with the number of errors or warnings that occurred during its backup. The object backup status can be Completed.Module 11 Monitoring and Reporting For each backup object.hp.00 11-7 2003 Hewlett-Packard Development Company. such as client system.com U1610S B. plus the completion status of the pre/post exec command. and its backup status. Furthermore. The session status is a summary of the status of all objects. http://education. Failed or Running. L. mount prompt. You may want to configure some additional triggers for reporting. U1610S B. L. This grouping is necessary for scheduling and event based execution. The event driven reporting functions are covered in the next module.P. Some of these capabilities require some configuration before they may be used. SLIDE: Reporting Possibilities Reporting Possibilities Interactive reports (GUI) Report groups Web reports (Java GUI) Event triggered Student Notes Shown above are some of the possibilities that Data Protector provides for collecting data from the embedded database. The interactive reporting command line and GUI are available for use right out of the box. Data Protector also comes pre-configured with several events that trigger logging.hp.com . The configuration of a Report Group would allow for collections of reports to be executed in a single action. http://education.Module 11 Monitoring and Reporting 11–4.00 11-8 2003 Hewlett-Packard Development Company. hp.com U1610S B. SLIDE: Report Categories Report Categories Data Protector provides detailed reports in the following categories: • • • • • • Backup specifications Configuration Internal database Pools and media Sessions in timeframe Single session Student Notes Data Protector provides a rich set of predefined detailed reports to provide all the typical information that the Cell Administrator may need to assist with the day to day Data Protector tasks: (These are all available via the Web Interface and Reporting context of the GUI) Backup Specifications • • • • • • • Trees in backup specifications Objects without backup Objects latest backup Objects average sizes Not configured file systems Backup specification information Backup specification schedule http://education.P.Module 11 Monitoring and Reporting 11–5. . L.00 11-9 2003 Hewlett-Packard Development Company. com .Module 11 Monitoring and Reporting Configuration • • • • • • • Cell information Configured clients not used Configured devices not used Lookup schedule Clients not configured Licensing report Client backup report Data Protector Database • • Data Protector database size report Data Protector database purge report Pools and Media • • List of media Media statistics Sessions in Timeframe • • • • • • • List of backup specifications Session flow report Device flow report Report on used media Client statistics Backup statistics Backup errors Single Session • • • • • Single session report Session objects report Session per client report Session devices report Session media report In an MOM environment. http://education. NOTE U1610S B. reports can include information from multiple cells.P. L.00 11-10 2003 Hewlett-Packard Development Company.hp. such as ASCII. omnicellinfo. L. omnistat. SLIDE: Reporting Overview Reporting Overview Choose Reporting Tool Interactive Report or Add Report Group and Add Report to Group Choose Report Content Choose Report Format Define Report Group Schedule Choose Delivery Method Student Notes Data Protector provides a large number of predefined reports. omnidbutil) http://education. Reporting Tools Data Protector provides the following mechanisms for defining and running reports: • Data Protector GUI (reporting context) • omnirpt command • Web Interface • Data Protector commands (omnidb. and can be scheduled to provide regular information. etc. etc.com U1610S B.hp.Module 11 Monitoring and Reporting 11–6.. such as email. in a selected format.P.00 11-11 2003 Hewlett-Packard Development Company. broadcast. omnimm. Reports can be generated interactively via GUI or command line. Reports can also be used within notifications. HTML. . Delivery Methods Reports may be delivered using the following methods: Broadcast Email External Log SNMP Allows for pop-up window within the Microsoft Windows environment. but in a summary form. A report must also reside in a report group if it is to be scheduled. It provides the requested information.00 11-12 2003 Hewlett-Packard Development Company.hp. showing the most important information. a database session manager (DBSM) is started. This format is useful to import the reports into some other applications for further analysis. such as a spreadsheet program. which is useful when using a Web browser. This is a suggested format for broadcast messages. http://education.) • Tab A report is generated with fields separated by tabs. • HTML A report is generated in HTML format. Report Formats To generate a report. not the individual reports. L. Data Protector allows schedules for the group of reports. Sends the report data to an SNMP manager. users could check to see if their systems were backed up by following a link on the Intranet site. and their data saved as HTML files (documents) as content for a web server. requires a mail sending capability to be available on the Cell Manager.P. Executes a program external to the Data Protector product. The report can be created in four different formats: • • ASCII A report is generated in plain text format.com . Short A report is generated in plain text format. Sends the report as Email. The report data is sent to this executable as command line parameters. For example. such as OpenView NNM or OVO. (reports would have to be scheduled.Module 11 Monitoring and Reporting Report Groups Reports can be run interactively or can be placed in Report Groups to allow multiple reports to be collated together to provide more useful information. Logs the report data to a file on the Cell Manager. U1610S B. P. (see the next page) http://education. The Data Protector GUI can be used to define. and schedule reports on both Windows and HP-UX cell servers. SLIDE: Reporting GUI Reporting GUI Student Notes The Data Protector GUI provides an easy to use method of generating and viewing reports online. generate.com U1610S B. Data Protector reports can be viewed individually. Documentation for all of the supported reports may be found on the man-page for omnirpt. Some reports can be used only in a report group and are not available as interactive reports. a mount request. L.hp. . or grouped into report groups. The GUI provides mini-Wizards to guide you through report generation and scheduling. for example.00 11-13 2003 Hewlett-Packard Development Company.Module 11 Monitoring and Reporting 11–7. P. 5. Select Finish to execute the interactive report. switch to the Reporting context. U1610S B. Provide the necessary information for the report.com . L. Click the Tasks tab at the bottom of the Scoping pane to switch to the tasks wizards. 3. 4. In the Data Protector GUI. http://education.hp.00 11-14 2003 Hewlett-Packard Development Company. 2. Browse the provided reports and select the one you want to view.Module 11 Monitoring and Reporting To view each report individually and interactively: 1. which means that it is available on any client system that supports the cell console user interface. run. you can also configure your reporting structure through it. Not only can you use the Java reporting facility to get online access to your reports. SLIDE: Web Reporting Interface Web Reporting Interface (java applet) Student Notes Data Protector provides a Java applet Web-based online reporting capability that lets you configure. During reporting operations.P. L. Microsoft Internet Explorer 4. with JDK 1.x.hp. The Java reporting interface is installed as a component of the cell console. such as adding new reports to a report group and changing a report's parameters.00 11-15 2003 Hewlett-Packard Development Company. and print all the Data Protector built-in reports of the omnirpt command interactively.Module 11 Monitoring and Reporting 11–8. Data Protector's Java applet directly accesses the Cell Manager to retrieve current data. .1 or later support). The Java applet requires a web browser (Netscape Navigator 4. http://education.com U1610S B.x. When you save the report. By default. you must access the Data Protector Web reporting interface. one can be set later through the User Manager. select Edit -> Change Web Password…. From the User Manager. you must add this report to an existing or a new report group. The Web reporting interface does allow for the creation of report groups.html located in /opt/omni/java/bin on Unix. Once you are logged onto the Cell Manager via the web-reporting tool. When the report is saved. or <OMNIHOME>\java\bin on Windows. L.html Address: C:\Program Files\Data Protector\java\bin\webreporting.com . Restricting Access to Web Reporting When you install the Data Protector Cell Manager. the Web reporting user (Called java) is automatically created. no password is needed to use the Data Protector Web reporting. you can print it or save it.hp. however. (the reports are the same.html To generate reports using the Data Protector Web reporting interface. the presentation is HTML) To view a report.P. http://education. not the report data. The report groups are saved on the cell manager in the <OMNICONFIG> directory. click the report and provide the needed information. a new group is created when saving a report to a new group. When the report is displayed.Module 11 Monitoring and Reporting The Java interface is started from a web browser by opening the Java GUI file webreporting. the definition to collect the data is stored.00 11-16 2003 Hewlett-Packard Development Company. you can generate various types of reports in a fashion similar to the Data Protector GUI. URL: file:/opt/omni/java/bin/webreporting. U1610S B. .. L..P. see the omnirpt man page. start report groups.hp. ... ReportOptions Session Option: -session SessionID PoolOption: Label Option: -label Label LocationOption: ExpirationOption: -expiration NoOfDays MediaClassOption: PoolOption: -pool Pool MediaStatusOption: DatalistOption: -datalist BackupSpecificationName. | -snmp Hostname. and send methods. The omnirpt command is used to generate reports..00 11-17 2003 Hewlett-Packard Development Company. All of the report names are predefined..Module 11 Monitoring and Reporting 11–9. define report formats.. For a detailed description of the command.com U1610S B.. DatalistGroupOption: LookupScheduleOption:-schedule NoOfDays NetworkOption: TimeframeOption: -timeframe Start Duration | -timeframe Day Hour Day Hour Day: Student Notes The omnirpt Command The omnirpt command allows you to generate individual reports. | -external Hostname:/CommandName.. | -log Hostname:/Filename. The syntax of the omnirpt command is as follows: omnirpt -report ReportName ReportOptions or omnirpt -rptgroup ReportGroup http://education.. list_sessions | session_flow | device_flow | used_media | host_statistics | backup_statistics | backup_errors | dl_trees | obj_nobackup | obj_lastbackup | obj_avesize | fs_not_conf | dl_info | dl_sched | db_size | db_purge | cell_info | hosts_unused | dev_unused | lookup_sch | hosts_not_conf | licensing | host | media_list | media_statistics | pool_list | single_session | session_objects | session_hosts | session_devices | session_media -pool Poolname -location Location -class MediaClass -status MediaStatus -group BackupSpecificationGroup -network Network_IP_Adress.. but have flexible option sets.. SLIDE: Reporting Command Reporting Command omnirpt -report ReportName ReportOptions [FormatOption] [MethodOptions] [-multicell] [-multiple] [-header] omnirpt -rptgroup ReportGroup FormatOptions: MethodOptions: ReportName: -ascii | -html | -tab | -short -email EmailAddress.. | -broadcast Hostname. saved in a file: omnirpt -report used_media –timeframe 24 24 –tab –log data.com .hp.txt NOTE If you have an HP-UX cell manager.P. http://education. you may want to take advantage of the Netscape Fasttrack Server that is available from the applications media.Module 11 Monitoring and Reporting Here are some examples of omnirpt use: Generate a report on system <System_Name> in HTML format. omnirpt -report host -host System_Name –html Generate a report on media used in the last 24 hours in tabulated format. U1610S B.00 11-18 2003 Hewlett-Packard Development Company. L. highlight reports.hp.Module 11 Monitoring and Reporting 11–10. After the report group is created. may be scheduled.You will be prompted for a report group name. Report groups may also be triggered by the event notification system. SLIDE: Report Groups Report Groups Student Notes The report group defines a collection of reports that will be executed together. you may assign (save) report definitions to the group.P. unlike individual reports. The report group.com U1610S B. http://education. and using the pop-up menu (right mouse button) select Add Report Group… . L.00 11-19 2003 Hewlett-Packard Development Company. switch the GUI to the reporting context. . and then schedule the report group. names without spaces and special characters are acceptable. To create a report group. com . http://education. A few examples of schedule files are shown below. the schedule file can be created manually.00 11-20 2003 Hewlett-Packard Development Company.hp. L. Example 1: every Saturday at 8:00 PM. they can be scheduled to generate reports on a regular basis. The easiest way to schedule a report is to use the Data Protector GUI as shown in the slide above. The omnitrig process initiates scheduled reports in the same way as backups. Alternately.P. SLIDE: Report Group Schedule Report Group Schedule Student Notes Once reports have been defined and grouped into report groups.Module 11 Monitoring and Reporting 11–11. 2000: -start -starting 20 5 2000 -every -day Sat -month May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr -at 20:00 U1610S B. beginning May 20. .00 11-21 2003 Hewlett-Packard Development Company.com U1610S B. The report schedule files are named the same as the report groups in the rptgroups directory. excluding January 1-5: -start -starting 1 1 2000 -every -day -month Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec -exclude -day 1 2 3 4 5 -month Jan -at 20:30 The schedule files are located in the directories /etc/opt/omni/rptschedules on HP-UX and C:\program files\Data Protector\config\rptschedules on Windows. http://education.P.Module 11 Monitoring and Reporting Example 2: every day at 8:30 PM. L.hp. report definitions may be added to it to form the collection. Once defined. The report group has the concept of a folder. Report groups are saved as ASCII files in the <OMNICONFIG>\rptgroups directory on the cell manager. Data Protector allows for several reports to be added to a single report group. as well as several report groups to be created.Module 11 Monitoring and Reporting 11–12.00 11-22 2003 Hewlett-Packard Development Company.P.com . the properties of the report group and reports within the group may be modified. Report Groups A report group can contain multiple individual reports that will be executed together via the execution of the report group. After the report group is created.hp. or container for the report definitions. L. U1610S B. http://education. SLIDE: Adding a Report to a Report Group Adding a Report to a Report Group Student Notes The report group is used to create a report collection that may be scheduled and executed together. it will be created. A report group would satisfy the multi-report requirements. http://education. log file { TYPE ASCII file type TO file location "/var/opt/omni/log/media_rpt. . under notification.Module 11 Monitoring and Reporting Normally. See the omnirpt man page for more details on report ID and options for each type of report. Report groups must also be defined if reports are to be launched regularly via the scheduler.00 11-23 2003 Hewlett-Packard Development Company. The whole report group can also be scheduled and delivered by the notification service. After the report group is created it will appear at the bottom of the reports list.P.hp. a user will require information that is not available from any single report type. one of the choices for saving is to a report group. command line. Example Report Group: The following example is stored in the following file: <OMNICONFIG>/rptgroups/Manage_Media NAME "Manage_Media" { comments REPORT "show-all-media" report name { ID "media_list" type of report POOL "Default File" pool name STATUS "Good" media status LOG report method. In some cases the requirements must be satisfied by a combination of reports. from there it may be executed. you must choose to save a report. a report of the previous night's sessions and details of the media used.com U1610S B. If the report group does not yet exist.log" } } } TIP To create a report group from the Web interface. and the Web interface). Report groups can be defined by all three reporting mechanisms (Data Protector GUI. For example. L. notification.0 . With HP OpenView Data Protector 5.OVO .0 .OVSIP (Service Information Portal 3. global data center.0) for service level information presentation U1610S B.hp.OVSN .P. The SLM integrations with other OpenView service management products consolidates service views.OVSIP (Service Information Portal 3.0) for service level information presentation DP 5. service performance data and other capabilities into one console.00 11-24 2003 Hewlett-Packard Development Company. http://education. giving a service provider better information and insight into the overall IT service delivery.OVR (Reporter 3.Module 11 Monitoring and Reporting 11–13. • • • • DP 5.OVO . L.com .0 .OVSD (Service Desk 4.DP-SPI .0 . Data Protector 5. SLIDE: Service Management Integrations Overview Service Management Integrations Overview operational level presentation OV-R 16 16 crystal crystal reports reports Data Protector Omnirpt for skipped files DP-OVO SPI DP-SIP service level presentation Cfg Cfgfiles files SIP scripts scripts Events snmp traps event collection and consolidation Cfg Cfgfiles files OVO OV-SN Service Mapping 11 crystal crystal report report problem management SLA SD Cfg Cfgfiles files scripts scripts Student Notes Data Protector.0 there are four new Service Management Integrations introduced which aggregate data and reduces complexity in a large scale. out of the box has monitoring.0 contains several integration possibilities to enable Service Level Management (SLM).DP-SPI .0) for problem management DP 5.0) for operational level information presentation DP 5. and reporting tools to document backup and recovery operations.DP-SPI . Data Protector extends its service centric approach to SLM through leverage of several OpenView products.OVO . While all data is at risk.00 11-25 2003 Hewlett-Packard Development Company. modules. and do so cost effectively. Threats ranging from user error. and methods to set service level expectations. automates critical response. like a business. Using this model. Demonstrating SLA compliance requires constant monitoring and periodic reporting to show whether SLA expectations have been met. It is a central management point for various remote OpenView applications. OVO DP SPI (OpenView Operations Data Protector SMART Programming Interface) . a provider can offer multiple service levels each at its own cost structure. Backup and recovery now is managed like the enterprise itself: that is. measure service delivery against those expectations. and to justify future service expansion. This component resides on both ends and is integrated into both products. such as data protection services. OV SIP (OpenView Service Information Portal) .a reporting service that further analyzes. By identifying the relative value of data placed within its care.P. OVO SN (OpenView Service Navigator) . even millions of dollars per hour of downtime. and prevent problems occurring in networks. or to the occasional failure of the storage device itself put data at risk twenty four hours a day. Business critical data loss can cost the enterprise thousands.com U1610S B. and Service Cards. the IT department now is run like a business. SLAs typically establish availability and performance objectives. Overview of products used in the service management integrations: • HP OVO – a software solution designed to help service providers and their system administrators detect. as well as message forwarding to other services. IT department can set service expectations on backup and recovery consistent with the protected data’s business value. include Service Browser. not all data justify equal recoverability. systems. IT department must protect the business critical data to a higher level of protection than the less valuable data. and so forth. and applications in any enterprise.Module 11 Monitoring and Reporting Enterprise IT departments are increasingly using service management tools. • • • • http://education. Service Graph.a component that implements the data passing interface between Data Protector and OVO. Part of IT’s business is managing the risk of data loss.SIP aggregates information collected from various services. The information is presented and formatted through various portal components and is made available through a web page. inspects.a system that maps messages to services to ease the control of complicated systems. In short.hp. techniques. Collects and analyzes data. networks. and collects data gathered by OVO and formats them into a human readable and usable webbased presentation. to viruses or other unauthorized data access and modification. Service providers use Service Level Agreements (SLAs) to document the provider-customer contractual expectations. . solve. Portal components. OVR (OpenView Reporter) . L. 0 English version). DP – OVR integration: integration of DP 5. With OVR service providers can generate reports from data obtained from the OVO management server.0.P. OV SIP gives an IT service provider customer visibility into the services that they are outsourcing. For example. It standardizes and manages issue management and makes it possible to maintain consistent service levels. and services.com . increasing DP’s monitoring and measuring capabilities. such as adding media or restarting a failed backup. OV SD automates and regulates IT troubleshooting processes. measures service quality levels. OVSN. OVP Agent and OV Reporter The integration of DP 5. DP 5. http://education. • • DP – OVSIP integration: integration of DP5. When integrated with DP5.0 with HP OVO is extended by adding HP OpenView Reporter (OVR 3.0 with HP OpenView Service Desk (OV SD). OV SD is a help desk solution. An IT Service Provider can generate monthly operational reports for DP5. With this module.0. U1610S B. It enables the IT support organization to implement configuration.Module 11 Monitoring and Reporting • OVSD (OpenView Service Desk) – a central management point for products.hp. help desk. an IT service provider can give its customers a view into the status of their outsourced data protection operations.00 11-26 2003 Hewlett-Packard Development Company. applications. “DP Transaction Performance” Report consists of the service performance metrics (one of the IT SLA parameters).0’s integration with OV SD gives support personnel access to DP5. It stores SLAs and monitors support service compliance to them. The Data Protector module on OV SIP extracts status information from DP 5. and change management processes into a single workflow. OV SD (without a human involvement) monitors the time taken to resolve backup-related problems. “DP5.0 Operational Error Status” report aggregates the “problem” data and can be used by an IT service provider for operational planning.0 data for a timely response and resolution of operational problems before they affect vital data protection service. incident resolution. and generates reports demonstrating SLA compliance. problem resolution.0 environment.0 with HP OVO. L. • DP – OVSD integration: integration of DP5. OV SIP contains a portal foundation and a range of management information modules. personalizes that information for each customer and shows status and business information specific to customer’s outsourced environment. An IT Service Provider can use these reports to demonstrate to a customer its SLA compliance. OV SD manages service help desk workflow. In addition to SLA compliance reports. OV SIP instead of giving the customer a generalized view of the service provider’s infrastructure. For example.0 with HP OpenView Service Information Portal (OV SIP). Service Management Applications PerfView PerfView Planner IT/Operations ManageX Data from OB2 Database Notifications Events/Scheduled Java Reporting Tabular Reporting ASCII Reporting Reports Web Reporting Student Notes Service Level Reporting In addition to Web. Application programs that use the ARM API act as sources of response time information (and also user supplied information that may be relevant to a particular transaction) for ARM compliant system management and monitoring tools. HP MeasureWare will log ARM transaction information in its repository for subsequent analysis and reporting. SLIDE: Service Level Management Service Level Management Summary Data Protector Data ARM / DSI NT Event Log Data MeasureWare Integration SNMP ….P. What Is ARM? The ARM API is an emerging standard for measuring end-to-end response times of transactions in distributed environments. The ARM and DSI integrations require that a MeasureWare Agent be installed on the Data Protector Cell Manager. L. Data Protector can provide source data for Application Response Measurement (ARM) and Data Source Integration (DSI) integrations. like HP MeasureWare. . such as a backup operation.00 11-27 2003 Hewlett-Packard Development Company. and command line reporting. It can also raise real time alerts (or alarms) when the elapsed time of a specific transaction. http://education. exceeds a predefined threshold.com U1610S B.hp. GUI.Module 11 Monitoring and Reporting 11–14. you must additionally replace the library /opt/omni/lib/arm/libarm. Windows NT cell managers require no additional steps for setting up the ARM Integration.sl with the appropriate ARM library. it is simple to integrate Data Protector with an application like HP OpenView Performance Agent. a number of actions are possible.P. formerly called MeasureWare. As Data Protector is already ARM equipped. U1610S B. including but not limited to. the transaction data will immediately show up in MeasureWare and PerfView. Measuring The following information can be measured with the ARM integration: • Overall session duration • Disk agent read times • Disk agent network write times • Media agent network read times • Media agent data write times • Session manager write to database time. or taking automated remedial action to resolve the problem.00 11-28 2003 Hewlett-Packard Development Company. paging a system operator. If Data Protector is installed on a system where MeasureWare is already present or vice versa.Module 11 Monitoring and Reporting When a real time alert is raised. On the Windows platform. It does not matter whether you install it before or after the Data Protector installation.sl with the appropriate ARM library. See the HP OpenView Data Protector Administrator’s Guide for more information. such as HP OpenView IT/Operations. The ARM integration is provided only on Data Protector cell managers. Installing the ARM Integration For the installation. On UNIX systems. • Database purge duration The following table shows the supported ARM transactions: Transaction Name BS-<Backup_specification> RS-<Session_ID> BO-<Object_name> DP DC Additional Information Time Time Time Number of purged records and database size (MB) Database size (MB) Transaction Description Duration of a backup session Duration of a restore session Duration of a backup of a specific object Duration of the Data Protector database purge. On HP-UX. In order to use it. informing a central operations console. which supports the ARM API. Duration of the Data Protector database check. this is completely automatic. If the cell manager is an HP-UX system. all you need is the ARM 2. L. http://education. the only required task is to create a link from a MeasureWare library to an Data Protector directory.com .0-compliant library to the specific system. you need to replace the library /opt/omni/lib/arm/libarm.hp. install the ARM 2.0 compatible RPM agent installed on the cell manager. What Can be Measured? Some examples of what can be measured using the DSI integration is: • Database size • Media usage • Media status • Number of systems • Amount of data per system • Full and incremental backup figures Overview of the Configuration In order to use DSI. This command can be used to gather information about the Data Protector environment. Data Protector provides a sample script and configuration file that shows you how to use the Data Protector reporting command line interface with Data Source Integration to log data about the Data Protector environment and backup and restore sessions. • Compile the class specification file. • Write a script to query data from Data Protector. The scripts are supported on UNIX systems. • Set-up class specifications file.com U1610S B. The script and class specification file can be easily modified for collecting other information from Data Protector. omnirpt. and access metrics from sources of data other than the metrics logged by the MeasureWare Agents scopeux collector. write a script that loops querying the selected data and writes it to standard output. Write a script to collect data: Select what data you want to log. you must: • Identify what data you want to log. http://education. 2. L. by default. See the omnirpt man page for more information on the command. follow these steps: 1. Data Protector provides a reporting command. Configuring the Integration To configure the Data Protector DSI integration. log two metrics: the number of clients in cell and the size of Data Protector internal database size.00 11-29 2003 Hewlett-Packard Development Company. . located in the /opt/omni/bin/ directory.hp.Module 11 Monitoring and Reporting What Is DSI? The Data Source Integration (DSI) allows you to use the HP OpenView Performance Agent (MeasureWare) to log data.P. Second. • Start the logging process. define alarms. Data Protector provides a sample Korn shell (ksh) script and class specification file that. Creating graphs of backup duration of important systems in your environment to detect trends in operation time (PerfView). add the following line to the file. in the /etc/opt/omni/dsi directory.log DATA PROTECTORII Using the Data Here are some examples of what you can do with the data that Data Protector provides: • • • • • Real time alerting of backup or restore sessions that exceed the specified time window (MeasureWare). Backup reports written to a web server to make them available on an on-demand basis (built-in Data Protector reporting with the capability to write HTML). Compile the class specification file: Use the sdlcomp command from the /opt/perf/bin directory to compile the class specification file. L.00 11-30 2003 Hewlett-Packard Development Company. In order to compile the Data Protector sample class specification file.Module 11 Monitoring and Reporting 3. Refer to the DSI manual for the complete syntax of the class specification file.ksh | /opt/perf/bin/dsilog Data Protector.P. and the management (Data Protector built-in reporting with the capability to send emails). Create the class specification file: The class specification file defines what data you want to log. with the following command: /opt/perf/bin/mwa stop Now you can edit the file /var/opt/perf/perflbd.com . and how you want it to be logged. Start the logging process. Start the script that collects your data.rc.spec Data Protector. Before you start modifying the perflbd. use: sdlcomp obdsi.rc. Forecasting of the Data Protector database growth to be able to spot points in time when certain limits will be reached (PerfView Planner). stop the mwa services.log 6. It must be added as a single line: DATASOURCE=DATA PROTECTORII LOGFILE=/etc/opt/omni/dsi/Data Protector. In the case of Data Protector sample metrics. Configure perflbd.log Data Protector 5. http://education. end users. If you are configuring Data Protector sample metrics. Regular email reports to backup operators. U1610S B.hp.spec. obdsi.rc file. 4. and pipe its output using the dsilog command. use the following command (in one line): obdsi. Data Protector provides a sample class specification file. . L.00 11-31 2003 Hewlett-Packard Development Company.Module 11 Monitoring and Reporting • Send major and critical Data Protector events to your network management solution.hp.com U1610S B. such as HP OpenView Network Node Manager (Data Protector built-in notification engine sending SNMP traps).P. http://education. how do you determine if last nights backups succeeded? 3.00 11-32 2003 Hewlett-Packard Development Company. Using the command line interface.Module 11 Monitoring and Reporting 11–15.P. how do you determine if last night's backups succeeded? 2. how do you abort a running session? 5. Using the command line interface. how do you respond to a mount request? U1610S B. Using the command line interface. Using the Data Protector GUI. http://education. how do you abort a session? 6. L. Using the command line interface. Using the GUI. Monitor Review Questions 1.hp. how do you determine if there are sessions currently running? 4.com . In what directory are schedule definitions stored? 5. In what formats can reports be generated? • • • • http://education. . What command can be used to generate reports? 4. Reporting Lab Review Questions 1.Module 11 Monitoring and Reporting 11–16. What is a report group? 3.com U1610S B.P. What report categories are provided? • • • • • • 2.hp. L.00 11-33 2003 Hewlett-Packard Development Company. com .00 11-34 2003 Hewlett-Packard Development Company.Module 11 Monitoring and Reporting U1610S B.hp.P. http://education. L. http://education. Manage the Data Protector event log.com U1610S B.hp.P. .Module 12 — Event Notifications Objectives Upon completion of this module. you will be able to do the following: • • Use the Data Protector event notifications for automation. L.00 12-1 2003 Hewlett-Packard Development Company. P.hp. Reporting. and are logged into file and presented to the administrator within the GUI. the event driven notifications can take automation to another level. Data Protector provides several possibilities for retrieving stored data from the Internal Database. Reporting and Notifications Monitoring. http://education. Events occur frequently within the Data Protector cell.com . L.Module 12 Event Notifications 12–1. Data Protector is able to have automated handling of events that cause reporting or notification to occur. While this capability is very necessary. SLIDE: Monitoring. in addition to logging events to a file. and Notifications Monitor Monitor GUI GUI •• •• Monitor Monitorcontext context Database Databasecontext context •• OpenView OpenView Reporting ReportingCommands Commands Java JavaReporting ReportingGUI GUI Report Report Schedules Schedules Cell Database Events Events Student Notes As discussed in the Monitoring and Reporting module. U1610S B.00 12-2 2003 Hewlett-Packard Development Company. This may prove useful in the testing of notifications that have been customized. . The maintenance checks may also be executed manually by using the “omnitrig –run_checks” command. The global option “DailyMaintenanceTime” is configurable to cause these checks to be done at another time.com U1610S B.P.hp.Module 12 Event Notifications 12–2. SLIDE: Notification Concept Notifications Concept Data Protector provides an event driven notification service: Event: • Device error • End of session • Low database space • Mount request • And more! Notification Method: • Broadcast • Email • External • Logfile • SNMP • Report group triggers Student Notes Data Protector provides an event driven notification system. There are two main types of notifications: • • Event triggered (a result of a run-time event occurrence) Scheduled maintenance triggered (a result of “maintenance time” checks) Maintenance Time Maintenance time is normally schedule for 00:00 (midnight).00 12-3 2003 Hewlett-Packard Development Company. L. http://education. the same report is written to a file on your web server in HTML format. so that others can also access this information. The media report lists all of the tapes used for the evening backups.com . Example 2 In case of a device failure or a mount request. Example 3: Data Protector executes a media report that gets fed to an external script. Additionally.) Notifications that result from scheduled Maintenance: Database Purge Needed Database Space Low Health Check Failed License Will Expire Not Enough Free Media Unexpected Events User Check Failed Notifications that are Event triggered: Alarm Backup Errors Database Corrupted Device Error End of Session Mail Slots Full Mount Request U1610S B.Module 12 Event Notifications Examples of Using Reporting and Notification Example 1 Every morning at 7:00. L. which activates the backup administrator's pager.P.00 12-4 2003 Hewlett-Packard Development Company. a report about all backup sessions in the last 24 hours is created and sent by email in ASCII format to the backup administrator's mailbox. for a worked example of automated media eject from a tape library. The external script send eject commands to the tape library to eject the tapes so they may be taken off-site. (See the Data Protector Administrators Guide Appendix-A.hp. a Windows NT broadcast message is immediately sent to the backup administrator's Windows NT workstation and an external command is triggered. http://education. Evaluates the configured parameters (days since last purge.00 12-5 2003 Hewlett-Packard Development Company. free disk space. Evaluates the configured parameter (number of days) to warn of license expiration. Notification Events Alarm Backup Error Database Corrupted Device Error End of Session Mail Slots Full Description Critical messages as a result of internal Data Protector conditions. and are received as pop-up windows on the system display even if no one is logged in. . and if one backup of the OBDB exists. The termination status of a backup session is completed with errors. The free pool media count has dipped below the configured threshold.com U1610S B. Mount Request Database Purge Needed Database Space Low Health Check Failed License Will Expire Not Enough Free Media Unexpected Events User Check Failed Notification Send Methods • Broadcast Broadcast message notifications allow you to send a broadcast message with desired information to specified systems when a specified event occurs. estimated purge time) to determine if a data purge is needed. the media database is consistent.Module 12 Event Notifications The following events can be trapped and notifications generated which alert interested parties so that remedial action can be taken. Evaluates the configured threshold parameters (maximum size of CDB. maximum size of DCBF) to avert a disk full condition. A failure of Data Protector to be able to write to a device. Occurs when ejecting media from a tape library. number of filenames. or errors. http://education. The result of Data Protector detecting a problem while trying to add or retrieve data. The reports are limited to 1000 characters.P. Execution of a customized (admin defined) script to perform some checking has failed. so the short format is preferred. Check if Data Protector services are running. Broadcast messages are limited in length. The number of events in the event log has exceed the configured threshold.hp. Broadcast messages can be sent to Windows systems only. (This is not supported on UNIX systems) You must specify the system to which the broadcast message should be sent. Occurs when every backup session completes. A backup or restore session is running and requesting a tape in order to continue. L. some libraries have more than one repository position to be used as the mail slot(s). 00 12-6 2003 Hewlett-Packard Development Company. The SNMP trap can be further processed by applications using SNMP traps. SNMP traps are sent to the systems configured in the Windows SNMP traps configuration. which includes the report in variable $6. such as the HP OpenView Operations. On a UNIX cell manager. An OV_APPL_ALLERT SNMP trap is generated. SNMP traps are sent to the systems configured in the notification. do the following: 1. The log file is posted on the cell manager system. open: Control Panel. On UNIX systems.hp. U1610S B. called Data Protector. Services. 2. you must create an Data Protector Exchange profile. and add the systems to which the SNMP traps will be sent (trap destinations). and specify. You must choose. On the cell manager. the full path name of the script that is located on the cell manager system which is to process the report data. Configure the SNMP service. no additional configuration is needed.P. If you are sending email notifications from a Windows system with Microsoft Exchange. On a Windows NT Cell Manager. • Logfile Log to file notifications allow you to post a log file with desired information when a specified event occurs. The script receives the report output as standard input (STDIN). • Report Group Report group notifications allow you to execute all of the reports from a report group when a specified event occurs. • SNMP SNMP trap notifications allow you to send an SNMP trap with desired information when a specified event occurs. Network. on a system that will be sending email (usually the Data Protector Cell Manager).com . L.Module 12 Event Notifications • Email Email notifications allow you to receive email with desired information when a specified event occurs. http://education. You specify the name of the file to which you want to post the report. • External External script notification allows you to process the output of the report in your own script. SNMP traps are sent to the systems configured in the Windows SNMP traps configuration. To configure Windows NT SNMP traps. The recommended format for script processing is the tab format. On a Windows NT cell manager. select Optional Networking Components to start the wizard. Minor. Critical. or configure the minimum message level and allow Data Protector to send only Major or Critical messages. SNMP trap configuration allows for all session messages to be sent to a trap destination. NOTE The OVdests file does not exist by default in all versions of Data Protector. the trap recipient may easily become overwhelmed with the volume of messages received through this mechanism. in addition to the notifications listed above. In the wizard. 4. It is strongly suggested that some filtering be put in place at the receiver to control the volume of messages that Data Protector may potentially send. Configure the SNMP service. Services tool. follow the wizard to install the management and monitoring tools. NOTE Data Protector may be configured to send SNMP traps to a management server for all session messages.hp.com U1610S B. Network and Dial-up Connections.Module 12 Event Notifications To configure Windows 2000 SNMP traps. and add the systems to which the SNMP traps will be sent (trap destinations).P. Administrative Tools. 5. . it may need to be created. L. Warning. such as: trapdest: <hostname> where <hostname> is the trap destination (IP Name) The OVfilter identifies the minimum message levels as Normal. do the following: 1. select Management and Monitoring tools and select Next. In the Advanced menu. 2. http://education. Enter the list of messages levels that would be sent as SNMP traps. Configuring SNMP Event distribution (HP-UX) Configure the files /etc/opt/omni/snmp/OVdests and /etc/opt/omni/snmp/OVfilter.00 12-7 2003 Hewlett-Packard Development Company. On the cell manager. The OVdests will contain the name of the trap recipient. Open the Control Panel. Major. 3. While this may be useful. Configure the SNMP Service community strings and trap destinations. open: Settings. SLIDE: Data Protector Event Logging Data Protector Event Logging Student Notes Data Protector tracks several different cell events and stores them in an event log. The events stored here are the result of the Data Protector event notification system. or by using the Reporting context of the GUI and selecting Event Log. Data Protector provides several events types that may be configured.hp. crs may also be logged separately.Module 12 Event Notifications 12–3.txt. the events that occur for the cell server process. Events that occur as a result of Data Protector monitoring. To remove entries from the GUI. Periodic purging of this event log is suggested. or executing jobs may trigger event processing.” The items in the log will not be removed. In addition to the Data Protector Event Log. The global option that controls this behavior is called U1610S B. L. By default most of the event types simply log to the event log files. select Event Log. simply display the text file “Ob2EventLog.00 12-8 2003 Hewlett-Packard Development Company. http://education.P. The event log is stored in readable form in the <OMNIVAR>log directory as Ob2EventLog. and use the pop-up menu item “Empty Event Log.com .txt. To view the old events. The event log is viewable as a text file. but the GUI will no longer display the “old” entries. as this file will grow without limits. On Windows systems additional logging may be sent to the system event log. If the administrator enables this additional logging. The default value is set to 0 (zero) which means off.log. then manual purging of the log file over time is necessary. L. http://education.hp.Module 12 Event Notifications “LogCrsEvents” and is set to 0 (zero) by default.P. . The log file where these events will be stored is called <OMNIVAR>/log/crsevents. To enable this use the global parameter “EventLogMessages”. which means off.com U1610S B.00 12-9 2003 Hewlett-Packard Development Company. The events that may be logged as a result of this feature are: • • • • • Cell Server (crs) service start and stop Session Manager processes start and stop Device Mount Requests Device Errors Major and Critical messages generated within a session These events are only logged on the Cell Manager system (where the CRS service is running). broadcast. You may create additional notifications that use all of the pre-configured events. Many of the notifications send their alerts based upon pre-configured thresholds. SLIDE: Default Notifications Default Notifications Event names Student Notes Each of the default notification send alerts to the Data Protector Event Log. The thresholds and parameters may be viewed using the GUI shown above. U1610S B. your customized notification may use any of the methods shown previously. The event configurations may be altered by using a text editor as well as via the GUI. such as E-mail.hp.Module 12 Event Notifications 12–4. etc. The format for the configurations is shown on the next page. http://education. Notifications are stored in an easy to edit file. L.com .P.00 12-10 2003 Hewlett-Packard Development Company. this is not performed within the Java GUI.Module 12 Event Notifications 12–5. L. http://education.P.hp. The native GUI must be used to edit notifications.00 12-11 2003 Hewlett-Packard Development Company. SLIDE: Web Notifications GUI Web Notifications GUI Student Notes The Data Protector Java based Web GUI may be used to add.com U1610S B. . delete or view the notifications that are configured into the cell. DbSpaceLow.com . -log. The parameter depends on the action and can be Report Group. Depending on the event. Student Notes Defining Notifications Notifications can be defined using the following methods: • • • Data Protector GUI Java Web Reporting Manually by modifying the Notifications file Notification definitions are stored in the <OMNICONFIG>/Notifications file on Unix. this can be a logical device or backup specification. -external. http://education. EndOfSession. email address. Event can be: DeviceError. The main structure for the Notifications file is outlined on the slide above. or Other… NOTIFICATION “<NotificationName>” { -event “<EventID>” -object “<ObjectName” <Action> “<parameter>” } Action can be -report. -snmp or -broadcast.hp.00 12-12 2003 Hewlett-Packard Development Company.Module 12 Event Notifications 12–6. ObjectName specifies the object that will be checked for the event. MountRequest.P. -email. filename or hostname. L. each identified by NotificationName string. SLIDE: Notification Format Notification Format Notifications file consists of any number of notification items. or <OMNICONFIG>\Notifications on Windows. The following examples may be referenced if you would like to manually add to the Notifications file on the cell manager: U1610S B. NOTIFICATION { -event "DBSpaceLow" -object "*" -report "Database" } "Notify_4" "Notify_3" http://education. NOTIFICATION { -event "DBSpaceLow" -object "*" -email "
[email protected] 12 Event Notifications Example 1: Add an entry to a logfile every time a session completes.edunet.P. .nap.hp. L.com" } Example 4: Notify root@cell_server via email the database space is low by executing a report group that performs that action.log" } Example 2: Execute an external script when a device error occurs.00 12-13 2003 Hewlett-Packard Development Company. NOTIFICATION "Notify_1" { -event "EndOfSession" -object "*" (could be a datalist name instead of *) -log "/var/opt/omni/log/end_of_session.hp. NOTIFICATION { -event "DeviceError" -object "*" (could be a logical device name) -external "/opt/paging/page_admin.sh" } NOTIFICATION "Failed_Device:DLT-1" { -event "DeviceError" -object "DLT-1" (send notice for logical device DLT-1) -email "root@r207w100" } "Notify_2" Example 3: Notify root@cell_server via email the database space is low.com U1610S B. P. http://education.sh" } "Notify_5" NOTE The notification above will execute in addition to any configure Mount Script that is associated with the device.Module 12 Event Notifications Example 5: Start an external media management script when a session finishes: NOTIFICATION "Session_End" { -event "EndOfSession" -object "w100_gen" -external "/opt/omni/lbin/manage_media.com . L.00 12-14 2003 Hewlett-Packard Development Company. Excerpt from the /etc/opt/omni/rptgroups/Database file: NAME "Database" { REPORT "Size_Report" { ID "db_size" MAIL { TYPE ASCII TO "root@na168w2" } } } execute the database size report action for the report is mail format is ascii recipient is root at <host> Example 6: Execute a script when any device is in the mount_request state.sh" } The following is the configuration for the report group called Database that will be executed according to Notify_4 above.hp. U1610S B. NOTIFICATION { -event "MountRequest" -object "*" (could be a logical device name) -external "/opt/omni/lbin/Mount_notify. In this manner you have multiple notification methods for a single mount request event. The report group was created using the Windows NT GUI. such as E-mail.com U1610S B. and deliver it by the defined delivery mechanism. L.P. generate a report of the media used and email it to the operator. This concept could be extended to automate the eject of media from a library (to the mail-slots) based upon a daily report connected to an event. and scheduled.00 12-15 2003 Hewlett-Packard Development Company. the DBSM invokes omnirpt to generate the report. The send method for the notification can be set to Report Group.Module 12 Event Notifications 12–7. when the end of a backup session condition occurs. so he or she can remove the tapes from the library.hp. When the particular event occurs. Notifications can also be used to trigger report generation. http://education. . then defining a notification. For example. This form of report generation can be very useful. This is done by first defining a report group and reports. SLIDE: Report or Event Notification Report or Event Notification Scheduled Event omnitrig • • • • • Broadcast Email External Logfile SNMP dbsm invokes omnirpt to generate report Delivery Method Notification Event Session Manager Student Notes Reports via Notification We have already seen how reports can be generated interactively via the GUI and Web. TRUE/FALSE? U1610S B. What send methods are available for notifications? • • • • 3. L. TRUE/FALSE? 5. http://education.com . Why would you want to send a notification to a report group? 4. Notifications Lab Review Questions 1.P. For what events can notifications be generated? • • • • 2. Which file is used to store notification definitions? 6.Module 12 Event Notifications 12–8. More than one notification can be configured for the same event type. Broadcasts can only be sent to NT/Windows systems.00 12-16 2003 Hewlett-Packard Development Company.hp. hp. Configure user groups in the cell.00 13-1 2003 Hewlett-Packard Development Company. you will be able to do the following: • • • Control user access to the cell.Module 13 — Access Control and Security Objectives Upon completion of this module. . Manage network access to the cell. http://education.com U1610S B.P. L. By default. SLIDE: Access Control and Security Access Control and Security Data Protector Security and Control Levels •• Local Local user useraccess accessto tothe thecell cell console console •• Remote Remotecell cell console console access access to to the the cell cellmanager manager •• Access Access to to the the web web reporting reportinginterface interface •• Remote Remote control control of of non-cell non-cell clients clientsfor for restore restore •• Remote Remoteaccess accessthrough through a afirewall firewall Student Notes Out of the box. the only user that is able to operate the cell console and use the command line interface is the root/Administrator user logged into the cell manager system. http://education.Module 13 Access Control and Security 13–1. including the support for access through a firewall. Data Protector is both secure and un-secure from different perspectives. and a design feature of the product. This section of the course will address all of the topics listed above. the disk agent is configured to respond to “any” session manager requesting to restore data.hp. On the other hand. U1610S B.com . What appears to be a huge security hole is easily closed.00 13-2 2003 Hewlett-Packard Development Company.P. L. although this is not very common. etc.com U1610S B. Administrator. and Restore.00 13-3 2003 Hewlett-Packard Development Company. http://education. Oracle. Student Notes Access to Data Protector’s functional areas. such as root.hp.Module 13 Access Control and Security 13–2. . The Data Protector operations that the users are able to perform depend on the capabilities assigned to the User Group to which they belong. Backup. Device Configuration. L. such as Client Installation. is strictly controlled by the allocation of specific permissions to Data Protector User Groups. SLIDE: Access Control Access Control Access to Data Protector's functional areas is strictly controlled by the allocation of permissions to Data Protector user groups.P. Users may be assigned to more than one group. Specific operating system users. may be configured as members of a Data Protector User Group. groups. http://education. L.hp.com . SLIDE: User Groups User Groups Data Data Protector Protector provides provides three three default defaultuser usergroups. New groups can be added by the administrator.Module 13 Access Control and Security 13–3. Admin Operator User Student Notes A Data Protector user group is a set of access rights that permit execution of certain portions of Data Protector functionality.00 13-4 2003 Hewlett-Packard Development Company. New groups can be added by the administrator. Data Protector provides three default user groups that provide the typical level of delegation and control required by most customers: • • • Admin Operator User U1610S B.P. SLIDE: The Admin Group The Admin Group • Complete control of all Data Protector functions.hp.Module 13 Access Control and Security 13–4. they must be added to the Admin group. When Data Protector is installed. . as it must always have full-control. including installation and configuration. the root/Administrator user of the cell manager is always a member. Student Notes The Admin Group is all-powerful.com U1610S B. the root/Administrator user of the Cell Manager system is automatically added to the Admin group. If you require other users to have full control of the Data Protector Cell. L. • By default. http://education. Accordingly.00 13-5 2003 Hewlett-Packard Development Company. • The administrator group cannot be modified. Members of this group have complete control of all Data Protector operations.P. the Admin group cannot be modified in any way. L.P.com . database database DBA DBAusers. therefore.hp. NOTE Operators have super-user like privileges through Backup and Restore! U1610S B. configured. users.Module 13 Access Control and Security 13–5.configuration and reporting/notification. Oracle. default.00 13-6 2003 Hewlett-Packard Development Company. Student Notes The Operator group has fewer capabilities than the Admin group. installation. it still has many other powerful rights. such such as as Oracle.configuration and reporting/notification. •• By Bydefault. care should be taken when assigning users to this group. are are added added to to this this group group when when the the integration integration is is configured. http://education. functions. The members of the Operator group are prevented from executing the following operations: • • • • Client system installation User Configuration Logical Device configuration Reporting and Notification configuration Although the Operator group does not have these permissions.excluding excluding installation. SLIDE: The Operator Group The Operator Group •• Complete Completecontrol controlof ofall allData Data Protector Protectorfunctions. . as these are functions typically performed by the system administrator.Module 13 Access Control and Security The main purpose of the Operator group is to provide operators the ability to perform the day-to-day operation of the Data Protector Cell. This is why the Operator group does not have any Configuration type permissions.P.hp.00 13-7 2003 Hewlett-Packard Development Company. L. http://education.com U1610S B. Giving users the ability to restore their own data may be desirable in environments like developer workgroups.com . By default. there are no users configured into the Data Protector User Group. Any media requests that accompany the restore session must be satisfied by the members of the Operator or Admin groups. L. if the correct media is loaded in the device specified by the restoring user.P. http://education.00 13-8 2003 Hewlett-Packard Development Company. No intervention on the part of the Admin or Operator group members is required to satisfy mount requests. SLIDE: The User Group The User Group •• Permission Permission to to initiate initiate restores restoresonly only •• Can only access their own data Can only access their own data (private) (private) •• Can Can be beused usedby byresponsible responsible users users who who have haveaccess access to their own tape drives or libraries to their own tape drives or libraries Student Notes The User Group has permission only to initiate a restore of the user's own data. U1610S B. Those responsible for backup must assign ownership of the backup job to allow a member of the user group permission to see the data available for restore within the restore GUI.hp.Module 13 Access Control and Security 13–6. where they have access to their own tape drives or libraries. abort.operator.00 13-9 2003 Hewlett-Packard Development Company. a custom group can be created to satisfy this requirement. monitor. The relevant users are then added to (or modified in) this group. Device configuration. Data Protector allows you to create your own groups. Student Notes In addition to the predefined default groups. User configuration. mount prompt. start backup specifications. L.com U1610S B. and and user usercan canalso also be be modified. and restore. You may choose to create custom groups that match the structure and requirements of your IT department. •• Default Default groups.hp. SLIDE: Custom Groups Custom Groups •• Customer Customerdefined defined groups groups can can be be created created to to suit suit the the local local environment. http://education.P. except client configuration. modified. In this case. . and Reporting and Notification. operator. Example The User Group operator has all access rights. start backups. environment.Module 13 Access Control and Security 13–7. groups. The user group user has only the Start restore access right. The IT organization may require some sort of hybrid where more senior users can format tapes (media configuration). hp.Module 13 Access Control and Security There are two ways to allow for more flexibility: • • Modify one of the existing groups (Operator. User) Create a new group U1610S B.P. L.00 13-10 2003 Hewlett-Packard Development Company.com . http://education. modify. (e. and modify users or user groups. . configure. and are considered very powerful rights. Restore as root) Permissions Explained Clients configuration User configuration Device configuration Allows a user to perform installation and update of client systems Allows a user to add.hp. and rename logical devices.g.Module 13 Access Control and Security 13–8. and how these permissions are assigned to the default user groups.com U1610S B.P. delete. L. This includes the ability to add a mount prompt script to a logical device.00 13-11 2003 Hewlett-Packard Development Company. delete. NOTE Many of the permissions will allow super-user capability indirectly. Allows a user to create. SLIDE: Group Permissions Group Permissions admin X X X X X X X X X X X X X X X X X X operator user Clients Configuration User Configuration Device Configuration Media Configuration Reporting and Notification Start Backup Start Backup Specification Save Backup Specification Backup as root Switch Session Ownership Monitor Abort Mount Prompt Start Restore Restore to Other Clients Restore From Other Users Restore as root See Private Objects X X X X X X X X X X X X X X X Student Notes The above slide displays the complete set of Data Protector permissions. Note that this is a powerful right. http://education. schedule. Allows a user to restore objects belonging to another user. modify. Allows a user to restore an object to a system other than the one where the object was backed up. Note: This user right is appropriate if the Start backup specification user right has been enabled. This user right is required to run any restore on NetWare clients. Allows a user to perform a backup using a backup specification. if an owner has been set for the datalist. L. This user right is required to run any backup on NetWare clients. monitor and abort their own sessions. Allows users to back up their own data.com . Allows users to restore their own data. U1610S B. including ejecting and entering media.P. Users can view information about any active session in the cell.Module 13 Access Control and Security Media configuration Reporting and notifications Start backup Start backup specification Save backup specification Backup as root Switch session ownership Monitor Abort Mount prompt Start restore Restore to other clients Restore from other users Restore as root See private objects Allows a user to manage media pools and the media in the pools and to work with media in libraries. This is a powerful right. Allows a user to view and restore objects that were backed up as private. you also need a Java user under Applet Domain in the Admin user group. Users having only this user right are able to view their own and public objects on the Cell Manager. so the user can back up objects listed in any backup specification and can also modify existing backup specifications. Allows users to create. and save their backup specifications. It can affect the security of your system.00 13-12 2003 Hewlett-Packard Development Company. http://education. Allows a user to start a backup specification without becoming the owner of the backup session. This is a UNIX specific user right. Allows a user to back up any object with the rights of the root login. Users can abort any active session in the cell.hp. to monitor and abort their own restore sessions. To use web reporting. Allows a user to respond to mount prompts for any active session in the cell. Allows a user to restore objects with the rights of the root UNIX user. Allows a user to create Data Protector reports. This is a UNIX-specific user right. com "admin" http://education.hp.P. Alternately.com "admin" "WebReporting" "java" "applet" webreporting "admin" "root" "root" "*" hpwind37. . SLIDE: Adding Users and Groups Adding Users and Groups Select Users to add a new group Select a group to add new users or modify access Manually add a user Edit <OMNICONFIG>/users/UserList file. if no GUI is available. Example: <OMNICONFIG>/users/UserList file: "Daphne Blake" "blake" "users" custed11.Module 13 Access Control and Security 13–9.00 13-13 2003 Hewlett-Packard Development Company. this is a wildcard that may be used in any of the first 4 fields.mayfield. the “*” is displayed in the GUI as <Any>.com U1610S B.uksr. L.hp.hp. and deleted from the Data Protector GUI. Note. modifications can be made directly to the configuration files. modified. Student Notes Users and Groups can be created. A Manager-of-Manager configuration will be generated. U1610S B. The total of all of the numeric values for each of the user rights added to the group is stored along with the group name in the Class Spec file. http://education. Additional Users — Special Situations A Data Protector Administrator will need to add users to the configuration in any of the following circumstances: • • • Someone wishes to use the cell console GUI on a remote system. The appropriate user must be added to the relevant group on the Cell Manager.hp. Each of the user rights is assigned a numeric value. the following steps are required: • • The User Interface Component must be installed on the remote client.com .Module 13 Access Control and Security Fields in the UserList file: • • • • • Field 1 = Real name Field 2 = Operating system user name (user id) Field 3 = Operating system group name. L. the integrations with third party databases. it is best not to modify it manually. The ClassSpec contains the user rights assigned to each Data Protector group. Additionally. or domain name for Windows users Field 4 = System name (hostname) Field 5 = Data Protector user group The <OMNICONFIG>/users/ClassSpec file is somewhat more complex.00 13-14 2003 Hewlett-Packard Development Company. such as Oracle. In these situations.P. This will require that the backup specifications are "owned" by that user as well. Integration with OpenView Operations will be performed. and therefore. typically require that a special user be added to the admin group or operator group to allow the backups to be performed by the database administrator's user id. and may have its contents removed to remove the Web password. The Web password will be encrypted and stored in the file <OMNICONFIG>/users/WebAccess on the cell manager.Module 13 Access Control and Security 13–10. there is a web user (java) inserted into the Admin group. http://education. . There is no password required to access the Web Reporting applet by default. Create a new empty file to remedy this situation. as well as the cell data is available. The protection requirement is largely due to the fact that through the web interface.00 13-15 2003 Hewlett-Packard Development Company. and the following error will occur: 159:10018 Old password is not correct. SLIDE: Changing the Web Password Changing the Web Password No old password by default Password saved in <OMNICONFIG/users/WebAccess Student Notes When Data Protector is installed on the Cell Manager. you may want to password protect the web functionality. or if the password is forgotten. L. Removal of the file will prevent a new password from being created.hp. This file exists as an empty file by default. To provide more security. notifications and report groups may be modified.com U1610S B.P. or at least restrict access to only known.P. This file is created on the cell manager. choose the cell manager or client systems to restrict access to only certain systems. even those that are not members of the same cell. The resulting list of configured hosts is stored in the <OMNICONFIG>/cell/allow_hosts file. Using the Data Protector Install (cell administration) GUI. Otherwise.hp. trusted cell managers. it is also a security risk. and distributed to each cell client automatically when the secure cell choice is made.Module 13 Access Control and Security 13–11. each client may be independently secured.com . U1610S B. SLIDE: Client Security Client Security Secure clients Secure cell <OMNICONFIG>cell/allow_hosts Student Notes Data Protector normally provides a secure environment from a user perspective. L. Cell administrators may want to prevent outside access to systems in the cell. This designed-in feature allows for remote recovery of data from one cell to another. the default installation allows for any cell manager or restore session manager to access any disk and media agent. However. By default the cell manager is always able to access the client. This may be accomplished by configuring the access limit to the cell by using the Secure feature shown above. http://education. Although this may be a very valuable feature for some environments.00 13-16 2003 Hewlett-Packard Development Company. as the cell manager is registered in the <OMNICONFIG>/cell/cell_server file. L. .Module 13 Access Control and Security The limited access restriction must include all systems that are to be remote managers. either modify the allow_hosts file on each system in the cell.00 13-17 2003 Hewlett-Packard Development Company. To remove the access limit. or use the GUI to unsecure the cell or individual clients.hp. such as OpenView Operations management stations.P.com U1610S B. http://education. U1610S B. 2.hp.sec allows administrators to control access to the system “pre-service.port 5555 request Student Notes The Omni-Inet process is the server started on each client to initiate the agents. L. the service daemon (in this case inet) would not be started if the requestor does not pass the initial security check. The inetd is started when the operating system starts. The inetd matches the port number of the requested service to the server by consulting the /etc/services file.P.” That is. When service requests come in the service configured in the /etc/inetd.log DP .log ns ctio e nn 6 co /sbin/init. NOTE The service name is omni.sec /var/adm/inetd. Data Protector sends service request on the well-known port 5555 to the Omni-Inet server on client systems.d/inetd sta rts 1 s lo g /etc/services: omni 5555/tcp $OMNIHOME/bin/inet 5 s ta rts c ly ous u n i on t d cke e h c 4 3 inetd Checked at startup 2 /var/adm/inetd. hence the name omni-inet. On UNIX systems. and the daemon started is inet. SLIDE: Network Access — inet (HP-UX) Network Access — inet (HP-UX) <OMNIVAR>/tmp/inet.conf: omni stream tcp nowait root $OMNIHOME/bin/inet/inet -log $OMNIVAR/tmp/inet.Module 13 Access Control and Security 13–12.00 13-18 2003 Hewlett-Packard Development Company. this service request is intercepted by the inetd (super daemon).conf file that matches the service request port is identified. http://education.com . 1. This level of security further enhances the security checking already performed by Data Protector. The inetd.sec /etc/inetd. here the port identifies the desired service name. conf file for server startup instructions.198. http://education. L.sec file.153.00 13-19 2003 Hewlett-Packard Development Company.sec for more information.hp.153. Inetd starts the inet service daemon to initiate the agents. Example: The /var/adm/inetd. 4. the inetd checks the security limitations for the requested service by consulting the /var/adm/inetd.P.com U1610S B.* # limited access to the 156. .Module 13 Access Control and Security 3. After the service name is known. If the remote system is authorized to start the local server then the inetd consults the /etc/inetd.198 subnet Consult the man-page for inetd.sec file may contain an entry similar to the following entry to limit the Omni-Inet daemon: omni allow 156. In both cases. SLIDE: Firewall Support Firewall Support Internet VPN tunnel Internet Internet VPN tunnel GUI Firewall DMZ DA MA CM Firewall 5555 (outbound) Intranet CM GUI DA 5555 + OB2PORTRANGE(outbound) DA MA MA GUI Student Notes The goal of Data Protector’s support of systems outside a firewall is to provide a solution for the backup of systems in the Demilitarized Zone (DMZ) while keeping either the cell console (GUI) or some other clients within the Intranet.Module 13 Access Control and Security 13–13. and media agent in the DMZ.P. only ports need to be opened for outbound connections: • • The disk agent and media agent in the DMZ (this is the recommended configuration) The cell manager.com . L. Supported Configurations Below are the two supported and recommended configurations. http://education.hp.00 13-20 2003 Hewlett-Packard Development Company. Shown above are the two supported firewall configurations for Data Protector. there are other possibilities but they represent security risks and should be avoided. disk agent. U1610S B. Technically. omnirc file (omnirc on Windows): OB2PORTRANGE=5000-5099 To correctly determine the number of ports needed: Unix: Num_ports = 5 + Num_sessions + Num_media_agents + Num_disk_agents Windows: Num_ports = 5 + Num_sessions + 2 x Num_media_agents + Num_disk_agents The above formula represents the “worst case scenario” of concurrent processes. some additional data must be supplied to Data Protector. For example. In the examples shown on the slide. and the cell manager on the outside. Other Internet connections are not recommended due to the number of ports that would need to be opened on the inbound connection from the GUI to the cell manager. No provisions must be made for port 5555. The OB2PORTRANGE parameter controls the dynamic listening port range used by Data Protector on an individual system.omnirc file. except the configuration for user that will be logging in. the parameter “OB2PORTRANGE” must be set to a range of ports.00 13-21 2003 Hewlett-Packard Development Company.hp. only the cell manager that is in the DMZ would need this configuration. by default set to 5555. The disk agent in the DMZ or Internet (not recommended) Having the disk agent outside the firewall will require many additional ports on the inbound to be opened to the media agent. L. in the <OMNIHOME>/.com U1610S B. http://education. This range will not affect the inet port. Configuring Data Protector for Firewalls To enable Data Protector to operate in one of the two supported configurations. NOTE The following configuration is technically supported but poses a higher security risk. The parameter is specified per system in the <OMNIHOME>/. This parameter is not in the global options file as it is configured per system. The range of ports sufficient for most Data Protector cells is around 100. . and is not recommended. as the connections are not initiated from the disk agent.P. In the case of having the GUI inside the firewall.Module 13 Access Control and Security Notice that the GUI connecting through the Internet using a point-to-point or VPN connection requires no additional configuration on the cell manager. With Data Protector 5. administrators have the ability to target a group of agents that is relevant for the cross-firewall operation.0. functionality related identification of a Data Protector 5.com . except for the DBSM which is specifically identified with its own clause. With this new method. Example: OB2PORTRANGESPEC=CRS:7000-7009. the OB2PORTRANGE variable will be parsed next to maintain compatibility with previous versions. the port ranges should not overlap. It is possible for two or more process groups to share a process range. This will allow for fewer ports to be open in the firewall.hp.P. L. a new implementation allows for specifying a port range for every binary. the last one in the sequence applies. debug trace name as well as in some protocol version checking.00 13-22 2003 Hewlett-Packard Development Company. but then the range should be exactly the same for all of them. The selection is based on the so-called ‘progname’ which is a platform independent. The size of the range for this group will be much smaller than the range as described above. The IPC library will check for a new omnirc variable named OB2PORTRANGESPEC. If a specification is identified more than once. “xSM” would be used for all session managers. The same name appears in version output. The value of this new variable will be parsed and checked against the progname for the process (thread) obtained from the programming libraries.Module 13 Access Control and Security Process connections Process Cell Manager Disk Agent User Interface (GUI/CLI) NOTE Connects to Disk Agent/Media Agent Media Agent Cell Manager Port Numbers Used 5555 OB2PORTRANGE on Media Agent system 5555 + OB2PORTRANGE on the Cell Manager Remote installation of client systems across the firewall is not supported. Program Name samples (progname) CRS MMD BSM RSM DBSM BMA-NET RMA-NET U1610S B. Generally. Client systems need to be manually installed. If no match is found. http://education.xSM:7050-7099.0 executable. as shown above in “xSM”.DBSM:7200-7499 When a specification begins with a lower case x. to prevent one group of processes from exhausting the port range from another group. this means that the range applies to the processes that have the rest of the string in the progname as a substring. In other words. . Any user in the Admin group may run backup and restore? 6.hp.sec must be modified for normal Data Protector operations. Which two files store the Data Protector group and user assignments? 4.00 13-23 2003 Hewlett-Packard Development Company. What is the allow_hosts file used for? http://education. TRUE or FALSE? 7. Review Questions 1. L.com U1610S B. What are the three default user groups? 3.Module 13 Access Control and Security 13–14.P. UNIX and Windows users can be added to the same Data Protector group. What is the purpose of the Data Protector user groups? 2. TRUE or FALSE? 5. The /var/adm/inetd. P.hp. http://education.00 13-24 2003 Hewlett-Packard Development Company. L.Module 13 Access Control and Security U1610S B.com . http://education. therefore.00 14-1 2003 Hewlett-Packard Development Company. as well as specific operating system documentation.Module 14 — Disaster Recovery Objectives Upon completion of this module.P. you will be able to do the following: • • Describe the role of Data Protector in disaster recovery. Prepare to recover your systems.hp. Data Protector is not part of the core operating system of either Unix or Windows. An understanding of these concepts and procedures is essential. L. This module contains selected extracts from the Data Protector Administrators Guide. It is essential that you do not use the contents in this module alone as a basis for your own disaster recovery procedures. In this module. we will introduce you to the different recovery procedures that are available with Data Protector.com U1610S B. special procedures must be followed to successfully recover from a disaster. . Refer to the Data Protector Administrators Guide and Data Protector Concepts guide for more information on this subject. however. Disaster recovery is not usually necessary. This includes re-partitioning and re-formatting the boot partition and recovery of the operating system with all the configuration information that defines the environment.hp. the following factors can exacerbate the situation: • • • The system must be returned to online status as quickly and efficiently as possible. L. The available personnel to perform the recovery may have only fundamental system knowledge.P. and the environment needs to be recovered before the normal restore operation can begin. In these cases.Module 14 Disaster Recovery 14–1. You must understand the recovery procedure! Student Notes A disaster is any situation in which a system does not function properly. Keep consistent and relevant backups.00 14-2 2003 Hewlett-Packard Development Company. whether due to human error. Disaster is always serious. Additional steps are required before recovery can begin. SLIDE: Disaster Recovery Disaster Recovery Disaster can strike at any time! • • • • • Plan carefully. http://education.com . or natural disaster. hardware failure. Remember that Data Protector is not part of the core OS. the root (boot) partition of the system is not available. U1610S B. administrators are not familiar with the required steps. and therefore. This step must be complete in order to recover other user data. regardless of the chosen disaster recovery method. You must have a well-defined.com U1610S B. easy-to-use solution. Preparing for a Disaster Recovery Carefully follow the instructions in this section to help you prepare for disaster recovery. Preparation is necessary. and recover from. It is a complex task that involves extensive planning and preparation before execution. systematic process in place to prepare for. disastrous situations.Module 14 Disaster Recovery Disaster recovery cannot be purchased as a predefined.P.00 14-3 2003 Hewlett-Packard Development Company. L. . http://education.hp. U1610S B. http://education.00 14-4 2003 Hewlett-Packard Development Company. L.com . • The Data Protector Database It may be necessary to recover the Data Protector database if it becomes corrupted and beyond repair with normal database maintenance tools.Module 14 Disaster Recovery 14–2. (The IDB recovery is covered in the Internal Database module of this course) • Cell Manager System The cell manager system recovery is more complicated that a client system. so offline recovery is necessary. as it holds the Data Protector database and software.P. This database is not available during disaster recovery of the Cell Manager. SLIDE: Disaster Recovery — Data Protector Disaster Recovery — Data Protector There are three types of failure that require some form of Data Protector disaster recovery: Corruption/loss of the Data Protector database Failure of the cell manager system Failure of a client system Student Notes There are three components of the Data Protector architecture that may require recovery: • Client System Recovery of a client system may be necessary because of hardware failure.hp. The database must also be recovered as a part of the cell manager recovery procedures if the cell manager fails. or corruption or loss of critical system software or configuration. Used with OBDR. .hp. The file containing the necessary information on how to format and partition all disks installed within a system.com U1610S B. This file is a Unicode file generated during the CONFIGURATION backup of a Windows client. This file is stored on the Cell Manager in the <OMNICONFIG>\dr\srd. The image is created by Data Protector. SLIDE: DR Terminology Disaster Recovery Terminology DR OS P1S SRD OBDR EADR ASR AMDR Student Notes There are several terms used in this discussion that are likely to be new. DR OS This is a bootable CD-ROM containing an ISO image. L.Module 14 Disaster Recovery 14–3. This file is called the Phase 1 Startup (P1S) file.P. but must be burned onto a CD using any ISO capable CDburner product.00 14-5 2003 Hewlett-Packard Development Company. EADR. The directory on the Cell Manager is <OMNICONFIG>\dr\p1s. and need to be introduced for clarity. ASR and AMDR P1S SRD http://education. This is may be stored on the Cell Manager during the full system backup. Used with EADR and OBDR The System Recovery Data file which contains system information required for the configuration and restore of a failed system. U1610S B. The Data Protector integration with Microsoft Automated System Recovery feature for Windows XP and 2003.P.hp. http://education. provides for automated operating system recovery and Data Protector DR processes.com . Data Protector prepares the image needed for the OBDR automated system recovery feature. The Data Protector Assisted Manual Disaster Recovery feature allows for post-operating system installation recovery. This requires significant preparation to be used. L.Module 14 Disaster Recovery OBDR EADR ASR AMDR This One Button Disaster Recovery capability exists as a feature of most HP tape drives. Data Protector provides a “miniserver/agent” installation with automated tools. The Data Protector Enhanced Automated Disaster Recovery feature allows for automated or semi-automated recovery of failed system.00 14-6 2003 Hewlett-Packard Development Company. 00 14-7 2003 Hewlett-Packard Development Company.Module 14 Disaster Recovery 14–4. L. SLIDE: Data Protector 4-Phase Approach to DR The Data Protector 4-Phase Approach to Disaster Recovery Phase Phase0: 0:Preparation Preparation Phase Phase1: 1:Configuration Configuration Phase Phase 2: 2: Re-activation Re-activation Phase Phase3: 3:Restore Restore Student Notes The disaster recovery process consists of 4 phases: Phase 0 Preparation • Perform full client backups • Update the DR OS Image after hardware/software changes Phase 1 Boot the DR OS • Replace any faulty hardware • Boot the system from the DR OS CD-ROM • Select the scope of the recovery Phase 2 OS configured and Data Protector installed • Critical volumes are automatically restored • (including the boot partition. and the partition containing Data Protector) Phase 3 Restore missing data • Restore any data not restored from the Phase 1 and 2 using Data Protector http://education.P. .hp. OS.com U1610S B. and standard priority Windows NT systems. 5.P.00 14-8 2003 Hewlett-Packard Development Company. − Joint recovery of the operating system. Activities for testing the procedures. What are the preparation steps needed on every system? For HP-UX systems. application data only)? This will yield several categories of systems: High priority HP-UX. partitions. 2. it is critical to define all the sources of configuration data and include these in a backup specification as part of the pre-exec stage. where can the necessary information and programs be obtained? When recovering HP-UX systems. On Windows. for example. 3. because. Planning Developing a detailed disaster recovery plan is crucial for successful disaster recovery. within what specified time. 4. striping. a fresh installation of the application. L. What method of recovery will be used for a specific system? − Operating system recovery per OS vendor procedure. mirroring. The plan must be prepared by IT administration and should include consideration of the following: 1.hp. In addition. it is important to know where information about the structure of the storage environment can be found. it is important to define what needs to be done before backup. this will require an extensive OS-configuration task. the most important configuration data is centralized in the registry. point in time to which to recover. corresponding tests are required. most of the data may come from a database online backup. but with more relaxed conditions (like time frame. − Joint recovery of the operating system and parts (or all of) the application. for example. At what time intervals and using which systems (or copies of them) do you perform these tests? U1610S B. together with the application and the application data. and what other systems need to be recovered. and clustering. To confirm the validity of the planned recovery procedures. Here the recovery of the application data is a distinct and separate series of steps. volume groups. high priority Windows NT. Most likely. Step-by-step instructions for recovering each client. What systems must be recovered. there are several steps that need to be addressed before a successful disaster recovery can be executed.com . which can be backed up by backing up the configuration object. − In the event disaster recovery becomes necessary. http://education.Module 14 Disaster Recovery Regardless of the disaster recovery method chosen. for example. to guarantee consistency of the environment during the backup. and loading the application with the application data. How to Create a Consistent and Relevant Backup • Examine the activity on the system during backup. and will refuse to run the service as expected. This might sound simple. To follow the example. the system is expected to operate and function as it did just before the backup was done.Module 14 Disaster Recovery Consistent and Relevant Backup In case of a disaster. and backup. Depending on what is active on the system when the backup runs. . data consistency for an application can be violated and result in restart and execution issues after recovery. for various reasons (HPUX example: License server at run level-2). the target system should be put back into the state it was at the time of the backup. this cannot be accomplished in most cases. however. you can get information on minimal system activity. A backup of the entire system with all connected disks done at sufficient intervals serving your restore to time-X requirement. However. L. certain circumstances can make the situation challenging. will realize that the data read from the file is inconsistent.P. Only operating system-related processes are allowed to run while the backup is performed. The backup must include the configuration object (for Windows systems). no low-level services are running. basic networking. Some have daemons or processes active as soon as the system finishes booting. A backup taken at the standard operating stage (the standard run level-4) cannot be expected to yield a problem-free restart of such an application. By looking at a freshly installed operating system.00 14-9 2003 Hewlett-Packard Development Company. System activity should be minimal: core operating system.hp. Some applications are not completely inactive. even if they have been shut down. It implies that all applications are truly shut down. that is. An exception to this is if services for a database (which are backed up online) are active. the license server. Such an early process may even read the data into memory and write a “ dirty flag” into some file while it runs. • • • http://education. Additionally.com U1610S B. The best concept would be to perform the backup with the relevant partition(s) set offline. This can be done using an appropriate pre-exec script. if started after such a pseudo-recovery. P.hp. http://education. U1610S B.x • Manual DR Solaris 7/8 • Manual DR Student Notes Data Protector 5.0) Cell Manager Client • Assisted Manual DR • Enhanced Automated DR • OBDR • Disk Delivery • Assisted Manual DR • Disk Delivery • Manual DR • Disk Delivery • Disk Delivery Windows NT/2000 • Assisted Manual DR • Enhanced Automated DR • OBDR Windows XP • Assisted Manual DR HP-UX 10. L.0 supports all of the disaster recovery options listed on the slide. SLIDE: Supported Recovery Options (5.x/11. The rest of this module will outline the concepts for each type.00 14-10 2003 Hewlett-Packard Development Company.Module 14 Disaster Recovery 14–5.com .0) Supported Recovery Options (5. The rest of this module will outline the concepts for each type.00 14-11 2003 Hewlett-Packard Development Company.x/11.Module 14 Disaster Recovery 14–6.hp. .com U1610S B.x Solaris 7/8 • Assisted Manual DR • MS Automatic System Recovery • Manual DR • Manual DR Student Notes Data Protector 5.P. SLIDE: Supported Recovery Options (5. http://education.1) Cell Manager Client • Assisted Manual DR • Enhanced Automated DR • OBDR • Disk Delivery • Assisted Manual DR • MS Automatic System Recovery • Disk Delivery • Assisted Manual DR • MS Automatic System Recovery • Manual DR • Disk Delivery • Disk Delivery Windows NT/2000 • Assisted Manual DR • Enhanced Automated DR • OBDR Windows XP • Assisted Manual DR • MS Automatic System Recovery Windows 2003 (32/64bit) HP-UX 10.1) Supported Recovery Options (5.1 supports all of the disaster recovery options listed on the slide. L. SLIDE: Manual DR Preparation Source Manual DR Preparation Source Copy to floppies from Installation depot or CD-ROM Student Notes Assisted Manual Disaster Recovery (AMDR) is available for Windows NT.P. Additionally. a few manual steps are necessary to be able to use the AMDR tools. U1610S B. Any time after a backup for a client or Cell Manager is completed. Diskette 1 of the set contains the drstart. A set of recovery diskettes for the Cell Manager must be prepared in advance of a necessary recovery.exe program. or just in time from the Cell Manager.00 14-12 2003 Hewlett-Packard Development Company. and be updated with the latest SRD for the system. L. 2000. http://education. Creation of AMDR diskettes The Data Protector Cell Manager (Installation Server) as well as the Data Protector Windows installation media contain the components that must be available during the AMDR procedure.Module 14 Disaster Recovery 14–7.hp. a one time preparation (per platform) of the AMDR diskettes is required.com . XP and 2003 operating systems. and is used to begin the AMDR. Files from one of the source locations must be copied to the recovery diskettes and then may be used to initiate the AMDR. Client system recovery diskettes may be prepared ahead of time. In most cases these files are automatically copied via the graphical user interface (DR wizards) or the omnisrdupdate command.P. The contents of these directories are used by most of the methods used by Data Protector for disaster recovery. .com U1610S B.Module 14 Disaster Recovery 14–8.hp.00 14-13 2003 Hewlett-Packard Development Company. http://education. SLIDE: Cell Manager Configuration Files (DR) Cell Manager Configuration Files (DR) Unicode source for omnisrdupdate command Student Notes The graphic above highlights the location of the stored “dr” data used for AMDR as well as other procedures discussed later in this module. L. L. The location for the stored recovery.srd may be copied to the diskette when needed for recovery of the Cell Manager.P. Shown above is the Cell Manger AMDR preparation wizard. http://education.00 14-14 2003 Hewlett-Packard Development Company.com . U1610S B.hp.srd file may be a local floppy drive (A:) or a network share if available. When a share is used.srd file on disk1 of the two disk AMDR disk set. SLIDE: Cell Manager Manual DR Preparation (1) Cell Manager Manual DR Preparation (1) default location: local floppy drive (a:) Student Notes Disaster recovery media for the Cell Manager must be prepared in advance to allow the system to be fully recovered. The omnisrdupdate command is used to update recovery. This is useful for systems that don’t support the other more automated methods. the recovery.Module 14 Disaster Recovery 14–9. exe –location may be used with client backup also Student Notes The graphic above illustrates the use of the backup post-exec to update the recovery. If the recovery.P.com U1610S B. http://education. then additional manual recovery/restore steps will be necessary to recover the current Data Protector Internal Database as well as other data to bring the system to the most recent backup state.srd file in the desired location for the cell manager. .srd is outdated.Module 14 Disaster Recovery 14–10.hp.00 14-15 2003 Hewlett-Packard Development Company. SLIDE: Cell Manager Manual DR Preparation (2) Cell Manager Manual DR Preparation (2) omnisrdupdate. This procedure should be used whenever a new configuration backup for the Cell Manager is performed. L. This is most likely run from the Cell Manager when a client system is unavailable and in need of recovery.hp. http://education.Module 14 Disaster Recovery 14–11. L.00 14-16 2003 Hewlett-Packard Development Company. U1610S B. SLIDE: Manual Update to Client SRD Manual Update to Client SRD Student Notes The Data Protector disaster recovery wizard may be used to update disk1 of the recovery disk set for a client system just when it is needed (or ahead of time if preferred).P. The AMDR disk set may also be created at this time and then updated as shown above.com . The GUI shown above allows for a selection of any disk location and defaults to the local A: drive. hp.P.srd for the specific client that is in need of recovery. . The recovery.exe program which is used after the installation of the operating system (DR OS). SLIDE: Manual DR Diskette Content (SRD added) Manual DR Diskette Content (SRD added) omnisrdupdate Student Notes The contents for the AMDR disk set for a 32-bit system is shown above.00 14-17 2003 Hewlett-Packard Development Company. http://education. The disk1 should contain the latest recovery. L.Module 14 Disaster Recovery 14–12. The AMDR disk1 includes the drstart.srd file is available on the cell manager by utilizing the data in the <OMNICONFIG>\dr\srd directory and omnisrdupdate command.com U1610S B. The 64-bit systems require a third disk due to the size of the zipped executables on disk2. L. • Create/format the boot and system partitions • Create/format additional partitions as originally existed on the system Execute the drstart. U1610S B. Typically the default is \WINNT. After the recovery.0: temporary install of DR OS (\DPwinnt. SLIDE: Assisted Manual DR Procedure Assisted Manual DR Procedure • Install the Windows operating system • NT 4.P.hp. • performs an offline restore (omniofflr) using the recovery.exe from Disk1 • installs the DP recovery tools and agents to a temporary location in the DR OS. this temporary OS may be removed. referred to as the DR OS. • Windows NT 4. • Windows 2000: the DR OS will be the active operating system after recovery.srd and local tape device if possible. • attempts to contact the Cell Manager and perform an on-line recovery (restore) of critical volumes by using omnidr.00 14-18 2003 Hewlett-Packard Development Company. http://education.Module 14 Disaster Recovery 14–13. so a choice such as \DROS or \DPWINNT is suitable.0: requires a temporary install to any directory other than the default location for the OS.com . 150MB) • 2000: active install of DR OS • Create/format boot and system partitions • Create/format additional partitions as original system • Execute drstart.exe from Disk1 • Installs DP recovery agents (15MB) • Online recovery attempted • Offline recovery from local device possible • Recover other partitions (vendor specific) Student Notes The procedure for recovering a failed client is as follows: Install the Windows operating system. .Module 14 Disaster Recovery Recover other partitions using normal DP restore procedures as well as any other vendor specific partitions. L.00 14-19 2003 Hewlett-Packard Development Company.hp.com U1610S B. (see the Administrators guide for more details) http://education.P. The tape drive is used to perform a full Data Protector backup in addition to an ISO image of the Operating System.hp.hp.P.Module 14 Disaster Recovery 14–14. The HP OBDR is supported on a limited number of hardware (PC) platforms with certain HP tape devices. Using a patented process. SLIDE: One Button Disaster Recovery One Button Disaster Recovery (OBDR) Firmware based SCSI CD-ROM emulation Tape drive eject button enables emulation mode Boot drive (CD-ROM) must be selected Restore other data Perform full OBDR backups System Restored DP Platforms: Windows NT Windows 2000 Initiate OBDR Student Notes HP’s one button disaster recovery (OBDR) support within Data Protector was introduced with version Omniback version 3. U1610S B. Consult the documentation on the HP URL: http://www.html for the current platform support.com .5 and is currently supported for Windows NT/2000. the tape drive is able to emulate a SCSI CD-ROM drive so that during a Disaster Recovery the computer system may be booted from this device.00 14-20 2003 Hewlett-Packard Development Company. The creation and maintenance of cumbersome boot disks becomes obsolete and everything you need to perform the recovery can be stored on tape. the tape drive switches back into “normal” operating mode and proceeds to restore the system automatically.com/products1/storage/products/tapebackup/obdr. manuals and the software applications and licenses during a disaster recovery. The entire recovery process is automatic and removes the need to locate drivers. L. Once the boot process has completed. The principle behind OBDR is simple. http://education. com U1610S B. .Module 14 Disaster Recovery If OBDR is supported for your platform. use the Data Protector Windows GUI to create an OBDR backup. the default 64K block size should be used to write to the device if you plan to perform offline restore. L.00 14-21 2003 Hewlett-Packard Development Company. then select the tasks tab. • It is essential to have an OBDR capable computer configuration: the system’s BIOS must support bootable CD extensions as defined in the El-Torito standard and read/write access to hard disk drive using LBA addressing via INT13h function XXh. The OBDR device must be conform to the same standard when emulating the CD-ROM. This is the only default block size available on Windows when performing disaster recovery. • A media pool with a Non-appendable media usage policy and Loose media allocation policy has to be created for the OBDR capable device. OBDR limitations: • Multiboot systems that do not use Microsoft's boot loader are not supported. • All drivers. http://education. • Network must be available when you boot the system in Safe Mode with Networking (Windows 2000) or in Directory Services Restore Mode (Windows 2000 Domain Controller). (e. Certificate Server Database and MS Cluster Service Database are not restored automatically during Phase 2.P. The Data Protector OBDR wizard will guide you through the backup process. When backing up the client. If this disk space is not available. • Replacement disks have to be attached to the same host bus adapter on the same bus. You will need to have the Windows installation CD-ROM during this backup process for Windows NT. • The logical device must have a 64Kb block size as its default. Only the media from such a pool can be used for disaster recovery.g. • An additional 200 MB of free disk space is required on the boot partition. and be assigned the nonappendable/loose media pool. • The hardware configuration of the target system must be the same as that of the original system. They can be restored on the target system using the standard Data Protector restore procedure (except for Microsoft Cluster Service database on Windows NT).hp. the disaster recovery fails. LILO boot loader from Linux) • Internet Information Server (IIS) Database. select the OBDR wizard. (see the next slide) OBDR requirements: • Automatic Disaster Recovery component must be installed. This includes SCSI BIOS settings (sector remapping). required for boot must be installed under the <%SystemRoot%> folder. Go to the Backup context within the GUI. Terminal Services Database. Module 14 Disaster Recovery 14–15. the OBDR wizard only runs on supported platforms. Use HP StorageWorks Library and Tape Tools to verify the OBDR capability. SLIDE: OBDR Preparation OBDR Preparation Requirements: • 64Kb block size (logical device) • Non-appendable media pool • Logical device default media pool non-appendable • Local GUI • Local OBDR capable tape device Student Notes The Data Protector requirements for OBDR are as follows: • 64KB block size set for the logical device • media pool allocation set to non-appendable • logical device must be assigned to the non-appendable pool in advance. L. no device properties may be changed during the OBDR wizard • local GUI may be required depending upon the platform of the Cell Manager. • the local device must have HP’s OBDR capable firmware installed.00 14-22 2003 Hewlett-Packard Development Company.com . or to upgrade the drive firmware. http://education.P. U1610S B.hp. .com U1610S B. L. this must include the Internal Database. and the database is also checked for corruption during the backup.hp.Module 14 Disaster Recovery 14–16. however. http://education. The hot-backup mode for the Internal Database is used as normal. Often the Internal Database is backed up to media separate from the filesystem of the Cell Manager. SLIDE: OBDR Wizard (1) OBDR Wizard (1) Cell Manager database included with system drive Student Notes The Data Protector OBDR Wizard may be used to create the recovery tape for the Cell Manager. in the case of OBDR they must be included in one backup.P.00 14-23 2003 Hewlett-Packard Development Company. SLIDE: OBDR Wizard (2) OBDR Wizard (2) device properties not modifiable via wizard Student Notes While using the OBDR wizard. U1610S B.hp.com .00 14-24 2003 Hewlett-Packard Development Company. http://education.Module 14 Disaster Recovery 14–17. Because of this.P. it may be beneficial to have a separate logical device defined as the OBDR device. L. device properties may not be modified. with all of the specific settings already prepared. iso file.Module 14 Disaster Recovery 14–18. SLIDE: OBDR Session OBDR Session <OMNIHOME\tmp\AUTODR contains process details recovery. power the system (on) while still depressing the eject button (release the eject button when the tape drive led’s begin to flash) 5. select the mode of recovery (details later. interrupt the normal boot.iso” file for Windows 2000 is approximately 80 MB and will be removed from the temporary location after it is moved to the tape.00 14-25 2003 Hewlett-Packard Development Company. A log file called autodr. Additionally the autodr file contains OBDR processing details. L. power the failed system just long enough to insert the tape into the tape drive. This will require additional storage space in the <OMNIHOME>\tmp directory while the backup is executing. and may be used to help troubleshoot failed OBDR sessions.hp.P. Booting from the OBDR tape: 1.exe to create the boot image used to restore the operating system. The “recovery. and select the SCSI CD-ROM from the list of boot devices 6.com U1610S B. turn the system power off 3.log is stored in the same directory as the recovery.iso (~80MB) created in <OMNIHOME>\tmp deleted after tape write Student Notes Data Protector uses the omniiso. depress and hold the eject button on the OBDR tape device 4. after EADR) http://education. 2. . To store the full DR image on the Cell Manager.P. size and all operating system boot. • Records essential system configuration. The CD ISO image can be burned on a CD-R using CD burning tool.Module 14 Disaster Recovery 14–19. automated recovery. SLIDE: Enhanced Automated Disaster Recovery Enhanced Automated Disaster Recovery EADR (Windows NT/2000) • Provides faster. When a disaster occurs. (CD burning software must support standard .iso image burn) U1610S B. During a full client backup the data required for temporary DR OS setup and configuration is packed in a single large DR OS image file.hp. the Enhanced Automated Disaster Recovery Wizard restores the DR OS image from the backup medium (if it has not been saved on the Cell Manager during the full backup) and converts it into a disaster recovery CD ISO image named recovery. L. This information may be stored on the Cell Manager in the <OMNICONFIG>\dr\p1s directory and is also stored on the on the backup tape. a WinFS file-system option must be enabled. The DR OS image file contains all of the necessary information and files to install a minimal operating system which is later used for full restore session. • Prepares recovery image for CD • Uses recovery (SRD) diskettes (optional) Student Notes The EADR Concepts The Data Protector EADR process collects all relevant environment data automatically at the time of backup. necessary driver files. http://education. included information is the data about partition type.com .00 14-26 2003 Hewlett-Packard Development Company. it is off by default.iso. If this disk space is not available.Module 14 Disaster Recovery Use the DR OS CD to boot the failed system. This additional free space is needed during collecting information for EADR (e. software or configuration change. If the DR OS image has not been saved on the Cell Manager during full backup. Boot partition has to be larger than 100 MB or disaster recovery will fail. the default 64K block size must be used to write to the device if you plan to perform offline restore. Network must be available when you boot the system in Safe Mode with Networking (Windows 2000) or in Directory Services Restore Mode (Windows 2000 Domain Controller). Enhanced Automated Disaster Recovery Wizard will restore it from the backup medium. such as change of IP address or DNS server.hp. Boot the target system from the disaster recovery CD and select the scope of recovery. . Use Enhanced Automated Disaster Recovery Wizard to prepare a DR CD ISO image from the DR OS image file of the crashed system and burn it on a CD. This is the only default block size available on Windows NT/2000 when performing disaster recovery. the operating system and the partition containing Data Protector) are automatically restored. EADR requirements • • • • • Automatic Disaster Recovery component must be installed.g. An additional 200 MB of free disk space is required on the boot partition. Phase 1: Replace the faulty hardware. Phase 3: Restore User Data and other Partitions Use Data Protector standard restore procedures to restore user and application data. The hardware configuration of the target system must be the same as of the original system. and finally recovers the original system as it was at the time of backup.00 14-27 2003 Hewlett-Packard Development Company. Phase 2: Restore Critical Volumes Critical volumes (the boot partition. This also applies to any network changes. Data Protector automatically installs and configures the DR OS. the disaster recovery fails. WINNT and system32 directory etc…) All drivers required for boot must be installed under <%SystemRoot%> folder. When backing up the client.P. This is a completely unattended recovery. • • • NOTE http://education. This includes SCSI BIOS settings (sector re-mapping). The general steps using the Enhanced Automated Disaster Recovery method for a Windows NT/2000 client are: Phase 0: Perform full client backup. Replacement disks have to be attached to the same host bus adapter on the same bus. scanning registry. formats and partitions the disks. Caution: You have to perform a new backup and prepare a new DR CD after each hardware. The systems BIOS must support bootable CD extensions as defined in the El-Torito standard and read/write access to hard disk drive using LBA addressing via INT13h function XXh.com U1610S B. L. U1610S B. You must press F12 to proceed with EADR process otherwise system will try to boot from hard disk. security and CD-ROM section in BIOS must be set the way it is possible to boot from CD drive. After that in command window full session restore is started. logon and starting restore session. Inspect AUTODR. http://education. Depends which operating system was installed on crashed host. First when small amount of data is written to disk and partition information is placed on hard disk. Small amount of data is written to disk followed by reboot.00 14-28 2003 Hewlett-Packard Development Company. Verify if backup device and backup server host are available on the network.iso image which will be used to burn bootable CD. In case if there are Errors reported. (Microsoft recommends NTFS type of partition for bootable data) Next step is to start mini operating system and updating information of original system.Module 14 Disaster Recovery EADR steps • • • • • Full host backup with configuration (if this is also Cell manager include backup of Data Protector database) Verify all Warnings in backup session log check if there are any system/application critical files locked during backup. Verify settings in BIOS of crashed system: boot-up sequence. Now you can remove bootable CD from drive. After reboot partition information is checked.P. verify the activity on backup device and in monitor session (amount of restored data). check if reported files are needed during installation. After you have iso image You need to use one of CD burning software to create bootable CD for crashed system. Follow instructions on screen. • • • • • • Optional you can monitor restore session from DP GUI is Cell manager is available. Select recovery scope from menu. Use Restore Tasks start wizard for preparing .hp. CD burning software must support burn CD from iso image. Hint: If you suspect that restore session has stopped. Created bootable CD contains usually about 90 Mb size.log file and search for any Error or Critical warning. L. Check if Inet service is running and if needed media for restore session is available.com . At first time partition is FAT and needs to be converted to NTFS if there were NTFS partition used before crash. Several reboots might be needed during phase one. Switch on / restart crashed system and follow instructions. Module 14 Disaster Recovery 14–20. http://education. it is stored with the name <client name>. L.P.com U1610S B. Object Properties DR image is placed on Cell manager in: <OMNICONFIG>\dr\p1s\hostname.img into: <OMNICONFIG>\DR\P1S (Windows & Unix Cell Managers) This is useful if you are going to prepare a disaster recovery CD ISO image on the Cell Manager.img Image is also copied to tape Student Notes Optional Copy full DR image to disk If the disaster recovery image is saved to the Cell Manager during backup.00 14-29 2003 Hewlett-Packard Development Company. . because it is much faster to obtain DR image from disk than from the backup medium.hp. SLIDE: Copy DR Image to the Cell Manager Copy DR Image to the Cell Manager Filesystem Advanced Options Object Summary. U1610S B.P.00 14-30 2003 Hewlett-Packard Development Company. Use the EADR wizard to create the recovery file that is to be “burned” to CD-R.com . but just in time for the cell clients (or ahead of time if desired). SLIDE: Choose the Image Source (1) Choose the Image Source (1) Student Notes The disaster recovery image must be prepared ahead of time for the Cell Manager. http://education.Module 14 Disaster Recovery 14–21. L.hp. If the full DR image was copied to the Cell Manager during the backup. L. .hp.P. SLIDE: Select the Image Set (2) Select the Image Set (2) Image may be created from disk file or recovered from latest backup tape Student Notes The image to use for the creation of the EADR CD is selectable at the time of the creation. then it should be available in the <OMNICONFIG>\dr\p1s directory. (approximately 30Mb per client) http://education.com U1610S B. otherwise it may be recovered from the last backup tape.00 14-31 2003 Hewlett-Packard Development Company. but requires some additional disk space to store the image for each client.Module 14 Disaster Recovery 14–22. The Cell Manager disk copy will be much faster. Module 14 Disaster Recovery 14–23. SLIDE: Volume Selections (3) Volume Selections (3) Student Notes When multiple backup sets exist for a client, the wizard presents a list of possible objects to use for the recovery set. Only one version for each object may be selected. After the objects are selected, Data Protector will prompt for the location of the recovery image. U1610S B.00 14-32 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 14 Disaster Recovery 14–24. SLIDE: Create the ISO Image (4) Create the ISO Image (4) Student Notes The recovery image (recovery.iso) may be stored in any location prior to recording it to CD. As soon as the destination is selected the ISO image will be created. The ISO image file creation usually takes 5 to 10 minutes. The resulting file may be 80-100MB depending upon the system. The recovery image creates a bootable DR OS CD for system recovery. List of files from EADR bootable Windows 2000 CD: BOOT.BIN BOOTDISK.CFG DRIMLDR.BIN MACHINE.TXT MBR0.IMG MBR1.IMG MINIOS.IDX MINIOS.IMG RECOVERY.INI RSCOPE.CFG RSCOPE.TXT http://education.hp.com U1610S B.00 14-33 2003 Hewlett-Packard Development Company, L.P. Module 14 Disaster Recovery 14–25. SLIDE: Image Ready to Burn to CD (5) Image Ready to Burn to CD(5) Student Notes Once the recovery.iso file is created, Data Protector is essentially done with the EADR backup process. Use an ISO compatible CD-burning software to copy the recovery.iso contents to CD and then use this EADR CD to boot the system. U1610S B.00 14-34 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 14 Disaster Recovery 14–26. SLIDE: Booting the DR Image Booting the DR Image Select “boot menu” key during POST/BIOS initialization Select device; the following message is displayed during startup: DRIM To start recovery of machine press f12 within 10 seconds … WARNING! You are about to start disaster recovery of the machine <SYSTEM_NAME> All data currently residing on disks will be lost. Please consult the documentation for details. Select recovery scope and press ENTER: Reboot (cancel and reboot) Default recovery (recover OS and Data Protector disk) Minimal recovery (recover OS disk) Full recovery (recover all configured disks) Student Notes The boot process for OBDR and EADR is very similar. The main difference is getting to the point where the Disaster Recovery medium is used to start the system. In the case of OBDR, the tape drive must be switched into the CD-emulation mode at power-up and then chosen for the boot device (manually; the boot menu is available by using F8 on some systems). The EADR ISO CD must also be selected as the boot medium, and the F12 key must be depressed to initiate the DR process (as shown on the slide). If F12 is not selected within 10 seconds, the default boot (from the hard drive) is attempted. Starting disaster recovery: Selecting the scope of recovery; there are 4 different scopes of recovery: No recovery: Disaster recovery is not performed and the computer is rebooted. Default Recovery: Critical volumes are recovered. All other disks are partitioned and formatted and remain empty and ready for Phase 3. Minimal Recovery: Only system and boot disks are recovered. Full Recovery: Identical to Default Recovery at the current time. http://education.hp.com U1610S B.00 14-35 2003 Hewlett-Packard Development Company, L.P. Module 14 Disaster Recovery Phase 2 aspects: Offline recovery is performed if the Cell Manager is not accessible (e.g. due to network problems, Cell Manager has experienced a disaster, online recovery has failed, etc.). Only standalone and SCSI-II Library devices can be used for offline recovery. Note that recovery of Cell Manager is always offline. Remote restore is the most common way of restoring data on DP client because of central media repository and managing. Local restore has an advantage in that it may be faster and no need for network access or Cell Manager access is required.(in case if network has down etc…). This allows for clients to be restored in advance of DR on the Cell Manager in case of a site failure. The Data Protector command (installed by the temporary DP installation) begins with a call to drstart.exe, which looks for the latest system recovery data (SRD) and then executes omnidr. omnidr -version | -help omnidr [-srd <file>] [-temp[os]] [-map <OrgMnt1> <TrgMnt1> [-map <OrgMnt2> <TrgMnt2>] ...] [GeneralOptions] -srd <FileName> Path to System Recovery Data file. -temp[os] Temporary OS is used for disaster recovery. <OrgMnt> Mountpoint of storage device on the original system. <TrgMnt> Mountpoint of storage device on the target system. GeneralOptions -target <hostname> Target system hostname. -local Forces restore to a local device. This command is used to restore any type of backup objects in the absence of a working database, which may have been caused by a disaster or lost connection with it. It is used as a standalone CLI utility or --better yet-- the higher level utility omnidr.exe, which assumes default invocation of omniofflr.exe based on the SRD file contents. Offline Restore (omniofflr.exe) Offline restore is based upon the omnidbrestore program code (used to restore the IDB). This command is used when the Cell Manager is unavailable. The omniofflr.exe requires exhaustive details about the restore device and backup media, including the position of backup objects on the medium. Information regarding the media can be obtained from the SRD file or alternatively by querying the DP database using omnidb.exe command in phase 0 i.e., when the system is still intact. The user can also write a script, which queries the database and prepares another script where a bunch of omniofflr.exe commands are executed with appropriate options. U1610S B.00 14-36 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 14 Disaster Recovery NOTE UMA for media management is not working if there is no Cell server up and running. The required tape must be manually loaded using library functionality (manually). Syntax: omniofflr {DeviceOptions} {MediaOptions} {ObjectOptions} {GeneralOptions} Options: Device -name <LogicalDeviceName> -dev {<PhysicalDevice>} -mahost <DeviceHostname> -policy <Logical Device Policy No.> -type <Logical Device Type No.> -description <DeviceDescription> -blksize <BlkSize> -name <LogicalDeviceName> parameter that specifies the logical device name -dev <PhysicalDevice> specifies the physical device (c:\temp\dev1, scsi1:0:0:0, /dev/tape0…) -mahost <DeviceHostname> specifies the name of the host, where the restore device is located Media Agent started -policy <log. device policy> specifies the logical device policy number: 1 = Standalone 3 = Primitive Stacker 5 = 6300 MO jukebox 6 = Exchange through cmd execution 8 = GRAU DAS exchanger library 9 = Silo medium library 10 = SCSI II exchanger 11 = RSM exchanger http://education.hp.com U1610S B.00 14-37 2003 Hewlett-Packard Development Company, L.P. Module 14 Disaster Recovery -type <log. device type> specifies the logical device type number 1 = DAT/DDS 2 = Quarter Inch Cartridge 3 = 8mm – ExaByte 4 = Advanced Information Technology 5 = 3480 Cartridge 6 = Raw Magnetic Disk 7 = Regular Disk File 8 = STK 9840 9 = Generic Magnetic Tape Device 10 = Digital Linear Tape 11 = StorageTek D-3 Redwood 12 = 3590 Cartridge (Magstar) 13 = Ultriuim drive 14 = Quantum Super DLT 15 = Ecrix VXA 16 = 17 = -description <DeviceDescription>] optional parameter that specifies the logical device description. -blksize <BlockSize>] optional parameter that specifies the block size the device is going to use when accessing media U1610S B.00 14-38 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 14 Disaster Recovery 14–27. SLIDE: Automated System Recovery Overview Automated System Recovery Overview • ASR is defined by Microsoft for Windows XP Pro and 2003 • ASR comprises of two parts: • backup and restore • ASR backup (without DP) • Contains a backup of the system state data, system services, and all disks associated with the operating system components • Does not contain user data • Creates floppy disks – Contains information about the backup, disk configuration, and how to accomplish a restore Used when performing a disaster recover together with the installation CD – • Data Protector 5.1 offers full integration with ASR • ASR is supported for Windows XP and 2003 Student Notes Windows XP and .Net Windows 2003 offer a process called automated system recovery (ASR), which can perform a system recovery after a system crash occurred (for example hard disk is defective). ASR has two parts: ASR backup and ASR restore. You can access the backup portion through the Automated System Recovery Preparation Wizard located in the Windows Backup functionality. The Automated System Recovery Preparation Wizard backs up the System State data, system services, and all disks associated with the operating system components. It also creates a floppy disk, which contains information about the backup, the disk configurations (including basic and dynamic volumes), and how to accomplish a restore. The system state includes a collection of system-specific data maintained by the operating system that must be backed up as a unit. It is not a backup of the entire system. The System State data includes the registry, COM+ Class Registration database, system files, boot files, and files under Windows File Protection. For servers, the System State data also includes the Certificate Services database (if the server is a certificate server). If the server is a domain controller, the System State data also includes the Active Directory database and the SYSVOL directory. If the server is a node in a cluster, it includes the Cluster database information. The IIS Metabase is included if Internet Information Services (IIS) is installed. http://education.hp.com U1610S B.00 14-39 2003 Hewlett-Packard Development Company, L.P. Module 14 Disaster Recovery You can access the restore part of ASR by pressing F2 when prompted in the text mode portion of setup. ASR reads the disk configurations from the floppy disk and restores all of the disk signatures, volumes, and partitions on the disks required to start your computer. (It will attempt to restore all of the disk configurations, but under some circumstances, it may not be able to do so). ASR then installs a simple version of Windows and automatically restores data from the backup created by the Automated System Recovery Preparation Wizard. For more information on how to use ASR directly with Windows XP or 2003, see Microsoft documentation. Data Protector 5.1 offers a complete integration with ASR that provides all the benefits of ASR, without the need to deal with Windows XP/2003 backup and restore tool directly. The following slides describe the integration in detail. U1610S B.00 14-40 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 14 Disaster Recovery 14–28. SLIDE: ASR Procedure Overview with DP ASR Procedure Overview with DP Phase 0 preparation • Full client backup (CONFIGURATION + disk) • Floppy set creation ( CM: before disaster, client: creation can be done on any Windows system after the disaster) Disaster occurs Phase 1 Configuration • OS installation CD (bootable) and ASR floppy set are necessary • Temporary OS installation • Original storage structure and contents are automatically re-established Phase 2 re-activation • All critical data (boot, system and “DP” partitions) are restored • All user and application data are restored using the normal restore procedure Phase 3 restore Student Notes This slide gives a brief overview about all necessary steps, required to perform a successful disaster recovery integration of ASR with Data Protector. There are four distinct phases: phase 0: preparation To be able to perform a disaster recovery, a full host backup is necessary. This includes all partitions and the CONFIGURATION section of the system. In order to get the SRD and ASR files created, it is necessary that the Automatic Disaster Recovery module is installed on the client system. Such a backup must be performed before the disaster occurs. The creation of the floppy set for the client systems, alternatively called ASR set, can also be done after the disaster occurs. This requires another Window XP or 2003 system, where the Automatic Disaster Recovery module is installed. For the Cell Manager though, the floppy disks must be generated before the disaster occurs. It is not necessary to update the SRD file manually (with GUI wizard or command omnisrdupdate) because, the update procedure automatically adds information about session and media id to the SRD file, when the disk set is created. Since this step requires access to the Cell Manager, it is imperative for the CM to create the ASR set before the disaster occurs. http://education.hp.com U1610S B.00 14-41 2003 Hewlett-Packard Development Company, L.P. Module 14 Disaster Recovery phase 1: configuration phase 2: re-activation phase 3: restore This is the phase right after the disaster happened, i.e. the system has crashed and can’t be started. In this phase, a temporarily existing OS and some Data Protector binaries are installed, which automatically launch the restore process. In this phase, the original storage structure and its contents are automatically re-established. All data belonging to the root and system partition, as well as the partition where Data Protector previously resided, is restored. Within this phase the user restores user related data, which were not automatically restored during phase 2. Critical partitions (boot / system / data protector) ASR focuses only on three partitions (also called volume or disk): boot, system and data protector. These three partitions are also called the critical partitions. A boot partition (also called disk or volume) contains the files required for the initial step of the boot process, whereas the system partition contains operating system files. The Data Protector partition hosts Data Protector executables, and in case of a Cell Manager also the IDB. U1610S B.00 14-42 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 14 Disaster Recovery 14–29. SLIDE: Recovery Procedure Phase 0 Recovery Procedure Phase 0 Perform a full host backup • must contain – CONFIGURATION – – system/boot partition partition where data protector is installed used for phase 1 and 2 other partitions • SRD file is created (on Cell Manger) – – used for phase 3 – – contains information required for configuration and restore (general DR usage) location on HP-UX: /etc/opt/omni/dr/srd/<system name> location on Windows: <Omniback Home>\config\dr\srd\<system name> • ASR file is created (on Cell Manager) – – – contains ASR specific information Unix: /etc/opt/omni/dr/asr/<system name> Windows: <Omniback Home>\config\dr\asr\<system name> Student Notes Phase 0 comprises all of the necessary steps which have to be done prior to a disaster. The first prerequisite is to perform a full system backup, containing all partitions as well as the CONFIGURATION part. During such a backup, the so-called system recovery data (SRD) information and the data required for ASR is collected. This is warranted only if the Automatic Disaster Recovery module is installed on the client system. To check whether these data are collected properly, the session should contain the following messages: [Normal] From: VBDA@tacul "tacul.bbn.hp.com [/CONFIGURATION]" Time: 02/15/03 02:17:38 Successfully collected system recovery data. [Normal] From: VBDA@tacul "tacul.bbn.hp.com [/CONFIGURATION]" Time: 02/15/03 02:17:57 Successfully collected ASR data. The SRD and the ASR data are stored in separate files. For a CM running on HP-UX, the data are stored under /etc/opt/omni/dr/srd/ and /etc/opt/omni/dr/asr/ respectively. For windows CM, the corresponding files are located under <Omni Home>\config\dr\srd\ and <Omni Home>\config\dr\asr\. http://education.hp.com U1610S B.00 14-43 2003 Hewlett-Packard Development Company, L.P. Module 14 Disaster Recovery Both files inherit the corresponding system name. The ASR file contains data used for the ASR procedure. The SRD file is used for other disaster recovery procedures as well. After a backup, the SRD file doesn’t reflect any information about session and media Ids. However, this information is essential to successfully execute a disaster recovery. During the creation of ASR diskette sets, (see next slide) the SRD file is updated; this effectively means that the information about session and media ID, important for the restore, is extracted from the internal database of Data Protector and added to the SRD file. This update process can also be done manually, via the GUI or the command omnisrdupdate. Since the updating of the SRD file is accomplished as an integral part of the creation of the ARS file set, it is not necessary to do it manually. U1610S B.00 14-44 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 14 Disaster Recovery 14–30. SLIDE: Create the ASR Set Create the ASR Set Student Notes For all Data Protector client systems, the creation of the floppy set or the so-called ASR set can be done after disaster strikes (just in time). This only requires another Window system, where the Data Protector GUI component is installed. For the Cell Manager, however, the floppy disk set must be prepared before the disaster occurs as the Cell Manager is the source of the data for the ASR set. Creation of the ASR set The ASR set can be created after a full client backup was performed. This is done via the Data Protector GUI wizard, under the Restore context, Tasks, and Disaster Recovery. In the wizard, when the version of the object is selected, corresponding information about the media and session ID is extracted, and subsequently added to the SRD file (This is otherwise, also, known as update the SRD file). When the ASR disks are created for the first time it is necessary to select the option Copy DR installation, in order to make sure that all necessary data are written to the diskettes. Once the ASR set is created, only the first diskette (which contains ASR information) has to be updated, i.e. the option Copy DR installation doesn’t have to be selected. Such an update is http://education.hp.com U1610S B.00 14-45 2003 Hewlett-Packard Development Company, L.P. Module 14 Disaster Recovery necessary after each hardware or software configuration change. This is also true for any network changes, such as a change of IP address or DNS server. Having the option Copy DR installation enabled, files which are needed in order to start the restore, like vrda_2l.exe, inet_2k.exe, vrda_nt.exe, inet_nt.exe, omnienu.dll, rma.exe, omnidr.exe, omnir.exe, devbra.exe, omnioflr.exe, etc. are grouped together as a zip file and copied to the floppy disk, disk 2 (and/or disk 3 in the case of the 64-bit systems). Note: When performing the creation with the option Copy DR installation, and using the floppy drive as the destination, the following windows pop up after the creation of the configuration files: This means that the diskette, which is already in the floppy drive should be used for this step too, i.e. the diskette remains in the floppy drive while the dialog box is confirmed. Only, in case the space is not enough to accommodate the DR installation bits, an additional disk has to be utilized. This precautionary measure is taken, because the ASR configuration data files (like SRD) vary in size and if they reach a certain size, the maximum size of the floppy disk is exceeded, and therefore an additional disk has to be used. NOTE: The option Copy full DR image to disk can be selected but has no impact. This option is only valid for Enhanced Automated Disaster Recovery (EARD). Contents of the ASR set DP defined files DR1.cab, DR2.cab, drstart.exe, omnicab.ini, recovery.srd The binary drstart.exe (disaster recovery wizard, GUI) is the first DP executable, which is started during an ASR recovery (phase 2). It unpacks the DP packages, install the binaries from the *.cab files and starts omnidr.exe, which then runs the restore. asr.sif, asrpnp.sif, autoexec.nt, config.nt, setup.log These files represent the contents of the so-called ASR archive file. Micorsoft (ASR) defined files U1610S B.00 14-46 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com Module 14 Disaster Recovery 14–31. SLIDE: ASR Set – Volume Selection ASR Set — Volume Selection Each critical volume is selected from available backups Student Notes To create the ASR set, Data Protector requires the selection of the versions of the critical volume backups that are desired for disaster recovery. The selection of these volumes causes an automatic update of the SRD (recovery.srd) to be created on the destination disk(s). http://education.hp.com U1610S B.00 14-47 2003 Hewlett-Packard Development Company, L.P. Module 14 Disaster Recovery 14–32. SLIDE: ASR Copy Location ASR Copy Location creates disk2 Disk1 folder created as ASR disk Disk2 folder created for DP DR installation Contents must be manually copied to floppies if other than A: is selected for the destination. Student Notes The destination for the ASR set us usually the local floppy drive, but may also be folder on the local system. For successful use of the ASR set, the disk folders contents must be copied to floppy disks and be available during the ASR recovery procedure. The selection of the Copy DR Installation causes the creation of Disk2, and potentially Disk3. These disks will hold the DR installation for Data Protector (agents, etc). U1610S B.00 14-48 2003 Hewlett-Packard Development Company, L.P. http://education.hp.com 4.com U1610S B. ASR re-creates the layout of the boot and system disks. SLIDE: Recovery Procedure Phase 1 (1) Recovery Procedure Phase 1 (1) 1.sif. 2. Boot from the Windows XP/2003 installation medium.hp. • All partitions are formatted and assigned original drive letters 5. This is required to initiate a restore of the complete system (boot. The following steps are required: 1. XP/2003 setup automatically proceeds based on the information found in asr. a temporary OS and some Data Protector (DR) installation binaries are installed.exe installation binary (located on disk1).log files. asrpnp. L. • Installs a temporary data protector recovery module (from disk2/3) • omnidr. System is rebooted. .sif and setup. • During boot process. system and DP partition) afterwards (phase 2 see next slide). After inserting the first diskette ASR re-creates the layout of the boot and system disk(s). Student Notes In the first phase of the ASR procedure. Change the diskette(s) when prompted.P. Insert the first (updated) diskette from the ASR set. 3. 3. NOTE: If third party SCSI or RAID driver are to be installed or configured then this must be done before step 2 (invoked with F6). ASR automatically starts data protector drstart. Press F2 during the start of the OS setup to enter the ASR mode. During the setup the ASR diskettes must be provided.exe is started automatically to perform the restore of the data 7. press F2 key to enable ASR mode 2. http://education. 6.00 14-49 2003 Hewlett-Packard Development Company. ASR copies installation files from the CD-ROM. Boot from Windows installation media (CD-ROM).Module 14 Disaster Recovery 14–33. http://education. The Windows CD and the floppy disk should be withdrawn.exe) is started and prompts for the second floppy disk. After that the system is automatically rebooted. When the system comes up again the Data Protector disaster recovery wizard (drstart.00 14-50 2003 Hewlett-Packard Development Company. After the restore the system is rebooted. U1610S B. L. ASR will reformat the disk layout and copy files from the CD-ROM.hp. NOTE: Only in phase 1 it is necessary to boot from the CD-ROM.com . The hard disk is used for subsequent reboots.Module 14 Disaster Recovery After the first diskette is inserted.P. P. a so-called online restore is performed.). SLIDE: Recovery Procedure Phase 1 (2) Recovery Procedure Phase 1 (2) If CM can be reached (by omnidr) • Prepares the necessary options and omnir.exe which was installed during the DR installation. Note that the recovery of a Cell Manager is always offline.1 GUI If CM can’t be reached (by omnidr) • An offline restore is performed – Restore Session Manager is started on the client system (omniofflr. . online recovery has failed. due to network problems. Offline recovery invokes the omniofflr. Cell Manager has experienced a disaster.hp.1 GUI.Module 14 Disaster Recovery 14–34.00 14-51 2003 Hewlett-Packard Development Company.exe is started – – Restore Session Manager is started on the Cell Manager session can be monitored in the DP 5. http://education. etc. Only standalone and SCSI-II Library devices can be used for offline recovery. Offline recovery is performed if the Cell Manager is not accessible (for example.com U1610S B. In this case a session manager is started on the Cell Manager system and the session can be monitored in the DP 5.exe ) only standalone and SCSI-II libraries are supported ASR on Cell Manage is always an offline restore – – Student Notes If the Cell Manager can be reached then. L. 00 14-52 2003 Hewlett-Packard Development Company. This must be restored before any other files. http://education. This phase is performed automatically and doesn’t require any manual intervention. the following three separate restore sessions will have been executed and are visible inside the GUI: Session 1 In this session the Windows file protection catalog is restored. boot. which is executed at the first login after the recovery..com . Once the system is up again. and “data protector” partition is restored automatically • After the restore. and data protector partitions are restored.Module 14 Disaster Recovery 14–35.P. It performs some cleanups and is then removed automatically. L. U1610S B. otherwise windows file protection service disallows overwriting protected files. all the data on the boot. At the end of phase 2. boot.exe is started with the option –cleanup • removes the temporary Data Protector installation • After phase 2. After phase 2. Data Protector will install a command script into the directory \All Users\Start Menu\Programs\Startup. disk and Data Protector partition are available again. the system is rebooted. SLIDE: Recovery Procedure Phase 2 Recovery Procedure Phase 2 • System. the system is rebooted automatically • omnidr. the following there sessions should have been performed • session 1: restore windows file protection catalog • session 2: file system restore • session 3: CONFIGURATION and IDB (in case of CM) Student Notes In phase 2. the system.hp. com U1610S B.P. In this session the CONFIGURATION and IDB (in the case of CM) is restored.00 14-53 2003 Hewlett-Packard Development Company.Module 14 Disaster Recovery Session 2 Session 3 In this session the file system is restored.hp. http://education. L. . where the services are not running. There are also some limitations of the MS ASR procedure: Special OS services aren’t restored within the disaster recovery scope.Module 14 Disaster Recovery 14–36. which were not restored during phase 2.00 14-54 2003 Hewlett-Packard Development Company.com . must be restored manually. not yet restored.P. have to be restored manually • user data must be restored • Some OS services aren’t restored during phase 2 • examples (see limitations for a complete list): – – – Internet Information Server (IIS) Database Terminal Services Database Certificate Server Database • has to be restored using the standard Data Protector restore procedure • Data stored on vendor specific partitions is not automatically restored • see limitations Student Notes In phase three all partitions. U1610S B. http://education. which is not the case during ASR. because their backup API requires the services be online.hp. SLIDE: Recovery Procedure Phase 3 Recovery Procedure Phase 3 • All partitions. L. Windows XP Home Edition does not support ASR. Only those local backup devices are supported that can be installed by Windows during OS installation (no additional drivers are required). If you replaced a network card or a video card.Module 14 Disaster Recovery 14-37. SCSI disks must be correctly terminated. The disk geometry comprises of the following parameters: # of bytes/sector # of sectors/track # of tracks/cylinder but doesn’t include the number of cylinders. The storage capacity of each replacement disk on the target system must be greater than or equal to the capacity of the corresponding disk on the original system. o In future MS may remove this limitation and allows for example to store the configuration data on a network drive or on a CD. disk geometry of the replacement disk must be identical to the replaced disk. . The partitions will be recreated during the ASR.00 14-55 2003 Hewlett-Packard Development Company. Internet Information Server (IIS) Database. • • • • • • • • • • • • http://education. L.hp. All disks used in ASR must be accessible to the system (hardware RAID must be configured. you will have to manually configure it. In addition. and Certificate Server Database are not restored automatically during Phase 2. but you will have to restore the data manually using the vendor specific procedure for restoring data. video cards and network interface cards. Multiboot systems that do not use Microsoft's boot loader are not supported. except for hard disk drives. Data Protector Automatic Disaster Recovery component must be installed on target systems. Floppy disk drive must be installed: o Microsoft limitation o Floppy and CD drives must be connected to IDE or SCSI controllers. TEXT PAGE: Requirements / Limitations There are many requirements and limitations to consider before using the ASR: • • To enable recovery using ASR. This is the only default block size available on Windows when performing disaster recovery.P. Terminal Services Database. That’s why the geometry can be the same even though the disk doesn’t have the same size. the default 64 Kb block size should be used to write to the device if you plan to perform an offline restore. Replacement disks must be attached to the same host bus adapter on the same bus. External devices such as USB or PCMCIA devices are not supported.) When backing up the client.com U1610S B. etc. All disks on the target system must have 512 bytes-per-sector. Data stored on vendor specific partitions is not automatically restored during ASR. The target system must have the same number of physical disks with critical volumes as the original system. you can restore data on EISA utility partitions using the standard Data Protector restore procedure. The hardware configuration of the target system must be identical to the original system. They can be restored to the target system using the standard Data Protector restore procedure. However. Module 14 Disaster Recovery 14–38. 3.hp. U1610S B.P.exe (interaction) drstart. The option Use Debugs must be selected. it might be necessary to create debugs in order to be able to analyse the error.exe (interaction) enable debug logs Student Notes The first Data Protector component. Click on Cmd button to open a command line window.com . SLIDE: drstart. L. the debugs can be copied from the directory %System32%\ob2dr\tmp either to a floppy disk or to a different partition. which is started by ASR is the Disaster Recovery Wizard (drstart.exe). 4.00 14-56 2003 Hewlett-Packard Development Company. This can be done in the command line window opened in step 2. When the Disaster Recovery Wizard appears. any button can be clicked in order to stop the automated procedure. http://education. Click Finish to continue processing When the error appears. To created and collect debugs the following steps are necessary: 1. In case of troubleshooting. 2. This wizard normally runs automatically without any user interaction. 3.com U1610S B. If they are identical. Enter the command “net stop NtmsSvc”. arising because the original name stored on the Cell Manager is different from the name used on the client (dhcp system name). 3. To disable the Removable Storage Manager during ASR.hp. ASR using this device is possible. the communication between the Restore Session Manager and the Media Agent doesn’t work. You do not have to copy it when you are only updating the ASR set. 4. Before. Updated scsitab file If the released scsitab file was updated with the library used for the disaster recovery process. stop the procedure by pressing any key. To find out whether this copy is necessary. 2. L. follow these steps: 1. When the disaster recovery wizard window pops up. the system name is set to a dhcp name (like. this general requirement is also true for ASR. If the online restore fails. follow the steps below: 1. Online restore will probably fail Since the unattended setup of Windows uses dhcp.com).Module 14 Disaster Recovery Troubleshooting when using a locally attached drive In case the backup.hp. Click Finish to continue. the ASR procedure automatically attempts an offline restore. You have to copy the scsitab file only the first time you are preparing the ASR set. Rename the scsitab file back to its original name. In this case. the above mentioned issue becomes invalid. otherwise copy the scsitab file to the first ASR diskette.P. Rename the scsitab file (located in <Data_Protector_home>) and run devbra -dev from the command prompt again. . it must be copied onto the first ASR disk. which needs to be recovered (local attached). Because of this system name mismatch. Because during an offline restore. Removable Storage allows applications to access and share the same media resources. 2.00 14-57 2003 Hewlett-Packard Development Company. which might require additional considerations.bbn. DP auto configures the library. any robotic libraries are configured on Windows system this service must be disabled. Disable Removable Storage Manager Removable Storage Manager is a Windows service used for managing removable media (such as tapes and disks) and storage devices (libraries). Compare the both outputs of the devbra -dev command. Open a command prompt window by clicking Cmd button. http://education. 4. and consequently the online restore will fail with an appropriate message. Run devbra -dev from the command prompt (from <Data_Protector_home>\bin). required for the disaster recovery. was done to a library connected to the system. dhcp-15-139-46-5. there are certain aspects. hp. they allow only certain Cell Managers to connect to them. http://education.srd file to “machinename” (unsupported feature). that medium.srd file. containing the backup.P. because the unattended installation of ASR sets the hostname to “machinename”. Troubleshooting when using secure clients When the clients within the DP cell are secure. load medium manually into the drive In case. then the offline restore will fail. and tries to connect to the client to which the library is connected. the system which is going to be recovered acts as a Cell Manager. and detects the drives only as standalone then. There are no issues for an online restore.00 14-58 2003 Hewlett-Packard Development Company. of course. In order to skip such an autoconfiguration. change the system name specified with –mahost inside the recovery. which. In this case the secure option for this system has to be switched off. If this client does not allow this. In this case.Module 14 Disaster Recovery Note: The autoconfiguration is performed in case the restore MA host is not responding. does not match the name as described in the recovery. DP can’t fully auto configure the library.com . has to be manually loaded into the drive. L. U1610S B. This causes problems in case of an offline restore. This is the case when a locally attached drive is used. Dis k De live ry 20GB Hosting System Method • The replacement disk is attached to another Data Protector client. Windows 2000. • Replacement Disk is partitioned and formatted. • The replacement disk is installed in the failed client.1 supports: HP-UX. SLIDE: Recovering Clients with Disk Delivery Recovering Clients with Disk Delivery Disk Delivery offers the fastest means of recovery as it bypasses: • Use of recovery diskettes • Installation of OS from CD-ROM • Installation of Data Protector agents Auxiliary Disk Method • Failed client booted from an Auxiliary disk. the administrator must ensure that before the disaster. Tru64. Window NT 4. As with manual disaster recovery. Aix. L.. (Use the Data Protector Client context to add components) http://education. • The replacement disk is partitioned and formatted. Solaris. • Data Protector GUI used to restore to replacement disk. DP 5. It bypasses the initial installation steps that are normally performed as a part of the recovery process. . however. Windows XP Student Notes Recovering Clients with Disk Delivery Disk delivery offers a faster means of recovery.00 14-59 2003 Hewlett-Packard Development Company.hp. enough data to be able to correctly format and partition the disk has been collected.P. • The failed client is booted from the replacement disk. • System booted from replacement disk. Data Protector automatically stores the relevant information as part of the configuration backup if the Automated Disaster Recovery component is installed on the client and Cell Manager systems. For Windows NT/2000.com U1610S B.0. • The Data Protector GUI is used to restore to the replacement disk.Module 14 Disaster Recovery 14–39. enough data has been collected to be able to correctly format and partition the disk. The administrator must ensure that before the disaster. Connect the auxiliary disk to the faulty system. and the Data Protector disk and media agents.e. Restore the data from backup media on the disk. networking. This establishes the network connection to the Data Protector Cell. 2.Module 14 Disaster Recovery Disk delivery can be enacted in two ways: • Using a Hosting System A hosting system is a system of the same platform as the failed system. Remove the auxiliary disk. The first method. 3. specifically to recover failed client systems. U1610S B.hp. and one that is already a configured Data Protector client. HP-UX. 1. Attach the restored disk to the crashed client and recover. NT. using a working Data Protector client system. (i. 3. A separate auxiliary disk is required for each platform type that may be recovered. L. and reboot the system to the minimal installation installed on the auxiliary disk. and reboot from the new disk. replace the faulty disk with a new disk. is described in this section.00 14-60 2003 Hewlett-Packard Development Company. http://education. containing a minimal operating system installation and Data Protector disk agent. 1. For Windows NT/2000. Format and partition the disk. The second way is to have a bootable disk connected to the crashed system. 4. 2. Format and partition the new disk. Data Protector will automatically store the relevant information as part of the configuration backup.P. etc). The first way is to use a working Data Protector client system (hosting client) and create the new disk while connected to this host. The disk must contain a bootable operating system.com . Using an Auxiliary Disk An auxiliary disk is a disk that has been prepared in advance. Disk Delivery Disaster Recovery of a Windows NT/2000 Client There are two ways to perform Disk-Delivery disaster recovery. 4. The recovered partitions are: • • • The boot partition (containing the NTLDR) The OS partition The partition containing Data Protector Any remaining partition can be recovered manually. • Connect the new disk to a Data Protector client (hosting system). Use the Restore function provided by Data Protector to restore the boot disk of the faulty client onto the replacement disk. This is the preferred method for disaster recovery of a Windows NT client. however. From an Data Protector client that has the GUI installed. You then replace your crashed disk on the faulty system with this new hard disk. and effectively. you need a bootable disk. successful full backup of the client that you want to recover. select the hosting client. read and follow the section. Reboot the host client system so that the new disk is recognized. In order to recover from a disaster quickly. you need a client of the same platform type as the crashed client.Module 14 Disaster Recovery It is imperative that you complete a few steps in order to prepare for disaster recovery. Remember that once the disaster occurs. you use a working Data Protector client to restore the latest full backup of your crashed disk onto a new hard disk connected to the hosting client. Connect the new disk to a working Data Protector host client system. when prompted in the disaster recovery Wizard. In addition to completing the steps listed in this section. In case you want to use the hosting Data Protector client method for recovery.P. Windows NT. . it is recommended that you assign partitions in the same order as they were at the time the full backup was performed. efficiently. When partitioning the system. It simplifies drive letter http://education. If you choose the auxiliary method for recovery. 2. L. you will need the following: • • • The most recent. 4.00 14-61 2003 Hewlett-Packard Development Company. 3.e. compatible with the hardware of the crashed system. A new hard disk to replace your crashed disk. “ Preparing for a Disaster Recovery. partition the new disk using the disk administrator and the original partition size information provided by Data Protector.com U1610S B. The disk should contain: Preparation • − − A minimal OS installation including network components An Data Protector Disk Agent Recovery This section provides the procedure for recovering your Windows NT client system using the disk delivery method. The actual disk delivery disaster recovery procedure consists of the following steps: 1. If partitioning has not already been done using one of the commercial partitioning packages. This is an especially important procedure in the case of system partition. Using the disk delivery method on NT. From there. it will be too late to perform disaster recovery successfully.hp.” in the Data Protector Administrators Guide. if you have not prepared in advance. and the hardware I/O path to connect the new disk). (i. run the Manager>Restore>Tasks tab>Disaster Recovery wizard. hp.Module 14 Disaster Recovery reassignment after restore and prevents a possibility of failure at system restart. http://education. L. and is described in this section. Drive letter assignments — available by right clicking on the original drive letter — serve as anchor points for the Restore Into option.x This description does not cover the recovery of a cluster environment. This is the preferred disaster recovery method for an HP-UX client.x and 11.com .ini file. and then connect it to the crashed system. U1610S B. 8. Remove the new disk from the client. This is not the same as a normal restore session. because of an inappropriate path to the system partition in the boot.P. The administrator must ensure that enough data has been collected before the disaster to be able to correctly format and partition the disk. when performing a restore of data. Connecting a bootable disk that contains a minimal OS installation and Data Protector Disk Agent to the crashed system will also work is the second method. This completes the recovery of the client system. 6. 5. Preparation Preparation for this disaster recovery is provided on several levels: • • • • Gathering the information for your backup specification Preparing the disk Preparing your backup specification (pre-exec) Executing the backup.00 14-62 2003 Hewlett-Packard Development Company. 7. additional steps and modification to the environment are necessary. Reboot the faulty system. NOTE Do not close down the GUI when performing a disk delivery restore because the restore will cease. Limitations • HP-UX 10. The first method is to use a working Data Protector client system and create the new disk while connected to this host. All of these preparatory steps are necessary before executing disaster recovery on the client system. Restore the latest full backup of your crashed disk onto the new hard disk using the Restore Into option. Disk Delivery Disaster Recovery of an HP-UX Client There are two possible methods for disk delivery disaster recovery. Depending on the configuration of the MC/Service Guard environment. Perform any necessary drive letter mappings. so that the information can be found when disaster strikes. Ensure that rpcd is configured on the system (configure the variable RPCD=1 within the file /etc/rc. Prepare the Backup Specification Provide a pre-exec script that performs the following: a.com U1610S B.d. Move some kill links from /sbin/rc1. version administration (there is a collection of the “ auxiliary information” per backup) must be considered. This prepares the system so that it can enter the state of minimal activity. which would otherwise be suspended by moving to run level 1.hp. See Appendix B. Only one bootable auxiliary disk is required per site and platform.config. rpcd. Collect all the necessary information about the environment and put it in a place where it is available if disaster recovery is needed. and they are needed for the backup. The state can be characterized as follows: • • Init-1 (FS_mounted. It is suggested that you put it onto a different system that can be accessed easily.Module 14 Disaster Recovery One-Time Preparation This section provides a list of items that need to be executed for each target system at backup time.. disk-mirroring. you must prepare it. The information should cover: • • • • • • • Physical and logical storage structure of the storage Current logical volume structure (vgcfgbackup and vgdisplay -v) ServiceGuard configuration data. L.d to /sbin/rc0. inetd.d/dce). Create the Auxiliary Disk If you want to work with the auxiliary boot disk. you must establish a state of “ minimal activity” (modified “init 1 run level"): The following steps are performed. swagentd.P.00 14-63 2003 Hewlett-Packard Development Company. striping File systems and mount points overview (bdf or copy of /etc/fstab) The output of the swapinfo command I/O-structure overview (ioscan -fun and ioscan -fkn) Client network settings http://education. have networking configured. date_set. “ Move Kill Links for HP-UX 10. once per client: 1. it is important to document the location of these files in the disaster recovery plan. The details given apply to HP-UX 10. If the information is collected as part of a pre-exec command. Also. The kill links include the basic services.” of the Data Protector Administrators Guide. This disk must contain the operating system. in order to perform successful disaster recovery. syncer_running) The following processes should also be running: network. hostname_set. 2.x. 2. In case the system to be backed up has application processes active at low run levels.x. and must be bootable. and complement the changes for the boot-up section. . 1. 2. if done so. f. Set up a backup specification for the client on the Data Protector cell manager. It should include all the disks (with disk discovery) and include the pre-exec and post-exec scripts.com . if applicable. unless the application data gets backed up separately. h. e. the information must then be extracted prior to the actual recovery. for example. However. 5. c. Consider logging out all users from the system. Testing the Procedure Execute this backup procedure. and so on. enter the state of minimal system activity (sbin/init 1.P. using online database backup. http://education. 3. especially any change in LVM structure. check if run_level 1 is reached).sec and use inetd -c). Shut down all applications. Boot from the auxiliary operating system. 4. the root volume group (to be restored) must be created on the repaired disk (using vgimport). If needed. Attach the auxiliary disk (which contains the HP-UX operating system and the Data Protector client) to the system. restarts applications. g. An emergency copy of the data can also be put into the backup itself. wait 60. It will not look like a root volume group during U1610S B. Note that this is a modified “ init 1" state. Replace the faulty disk with a new (comparable-sized) disk. or at least at every major system configuration change. and make it the boot device. so that nobody can log on to the system while the backup is running (overwrite inetd. Recovery This describes how to restore the system to the state when the backup was done. Provide a post-exec script that elevates the system to the standard run-level. Use the saved data for the non-root volume groups (with vgcfgrestore or SAM). Additionally.hp.00 14-64 2003 Hewlett-Packard Development Company. You may want to restrict network access to the system. Perform the following steps: 1. L. An auxiliary disk containing the HP-UX operating system and the Data Protector agents. d. and repeat it on a regular basis. You will need the following to successfully perform a disk delivery disaster recovery: • • • A new hard disk to replace your crashed disk. A successful full backup of the client that you want to recover. 3.Module 14 Disaster Recovery b. Reconstruct the LVM structure. list all the required media for the restore and make sure they are available. like mirror. . Create the file systems and mount them as required by the data from the backup. Import the system with the auxiliary disk into the cell. 10.P. 8. http://education.Module 14 Disaster Recovery the restore process. mountpoint names (like /etc_restore for /etc.00 14-65 2003 Hewlett-Packard Development Company. and so on). 13. but not the original. Select the version from which you want to restore. First. Make the system reboot from the new (or repaired) disk. including the (future) root-volume to the system. 7. ServiceGuard. 12. L.hp. Shut down the system that was just restored. using the option "Restore As <new_mountpoint>". the new disk can also be temporarily connected to a hosting system that requires an Data Protector disk agent. The root-volume from the backup is restored to the root-volume on the "repaired disk. it can be connected to the faulty system and booted. because we are currently running on the OS from the auxiliary disk. Remove any files in the mountpoints to be restored.com U1610S B. and so on. striping. from the data saved on a secondary storage device during backup. Use similar. 11. 9. Start the Data Protector user interface and open a connection to the Data Protector cell manager. Restore all the required mountpoints." Nothing is restored to the currently running auxiliary operating system on the auxiliary disk. Disconnect the auxiliary disk from the system. After being restored. 6. Reconstruct any other storage structure. Make the new disk bootable. NOTE Instead of using an auxiliary disk. 14. They must be clean. SLIDE: HP-UX Clients HP-UX Clients Steps required to recover an HP-UX client: Step 1: Recover the Operating System • Install minimal operating system plus networking.Module 14 Disaster Recovery 14–40. • Configure logical volumes and file systems. • Reboot. Usually. Student Notes The recovery process that must be followed for a HP-UX client is made up of three basic steps: Step 1 — Recover the Operating System • Install Minimal OS With a worst case disaster. • Configure networking. Ignite/UX can be used for steps 1 and 2. Step 3: Restore Data • Perform restore. http://education. a minimal installation is all that is required to get the system up and running. A minimal installation leaves out all the non-core software (which will be recovered from backup later).com . L.hp. Step 2: Install Data Protector Software • Install Data Protector client software from cell manager.00 14-66 2003 Hewlett-Packard Development Company.P. U1610S B. the system disk or all disks have been lost or corrupted. When the faulty or destroyed hardware has been replaced the first step is to install the operating system. all the logical volumes and file systems must be recreated and mounted..P. regardless of the backup software used. This is so that when the restore process is started. the data will be replaced in the appropriate mount points relating to the volumes. See the Ignite/UX documentation for more information. These basic steps must be performed. you can recover the remainder of the system from the most recent Data Protector backup tapes. NOTE The recovery process described in step 1 is not particular to Data Protector. etc). Again. patches. rather than the one created during the minimal install. http://education. Ignite/UX can be used to prepare recovery tapes that make the recovery much simpler and faster. this restore procedure is no different than any other backup mechanism.com U1610S B. Networking must be installed and configured (TCP/IP). • Reboot the System It is usually required that following a complete recovery. and Data Protector software have been recovered. (i. the whole system can be recovered minus certain system files. Use the same procedure as when the client was first added into the cell.00 14-67 2003 Hewlett-Packard Development Company. Oracle Agent. Step 3 — Restore Data • Restore Client System Data Now that the OS.Module 14 Disaster Recovery • Configure Networking Remember that Data Protector is a networked backup solution.e. the Data Protector client software can be pushed to the client from the cell manager system. for it to function properly. Exactly what should or should not be recovered must be decided by the restorer. TIP When performing a full restore. Disk Agent.hp. Typically. such as device files and the /etc/lvmtab file. therefore. Install the same client software modules that the client had previously. L. etc). networking. Data Protector is only the means by which data is stored and recovered. Only then will the system be back to its pre-disaster state (kernel configuration changes. . • Configure Logical Volumes and File Systems Once the operating system has been installed. TIP Step 2 — Install the Data Protector Software • Install Data Protector Client Software Once the basic operating system and networking have been recovered. the client and cell manager must be able to communicate. the system should be rebooted to boot from the newly restored kernel. Media Agent. Data Protector's restore option “move busy files” can be used to restore program files and libraries that may already be in use. http://education.P.hp. We covered this same procedure earlier in the Installation module U1610S B.Module 14 Disaster Recovery 14–41.00 14-68 2003 Hewlett-Packard Development Company. Import media containing backup of the Data Protector DB. Step 2: Install Data Protector Software • • • • Install Data Protector server software.com . • Configure logical volumes and file systems. Step 2 — Install Data Protector Software • Install Data Protector Cell Manager Software The cell manager software must be installed again from the CD media. Student Notes The recovery process that must be followed for an HP-UX cell manager is composed of three basic steps: Step 1 — Recover the Operating System • Install Minimal OS This is identical to the procedure described previously for a client system. L. Recover the Data Protector database. SLIDE: HP-UX Cell Server HP-UX Cell Server Steps required to recover an HP-UX cell server: Step 1: Recover the Operating System • Install minimal operating system plus networking. Step 3: Restore Data • Perform restore. Ignite/UX can be used for steps 1 and part of step2. • Configure networking. Create a local logical device. • Reboot. logical devices. “move busy files.00 14-69 2003 Hewlett-Packard Development Company.hp. because the database is now empty and has no knowledge of this or any other previous backups that have been performed. • Import Media Containing Data Protector Database A tape containing the most recent copy of the Data Protector database must be re-imported into one of the default media pools. recovery of the database will bring back all aspects of the Data Protector configuration. such as media pools. the Data Protector configuration will only contain the default media pools. take special care not to overwrite the active Data Protector database that you have just recovered. A temporary logical device definition is created for the import. In addition. a Logical Device must first be defined. Step 3 – Recover Data • Perform Restore The Cell Manager restore is identical to A a client system restore. TIP http://education. The import procedure can take quite some time. In this way. Data Protector's restore option. it is highly recommended that you always exclude the IDB from all filesystem and host level backups! When performing a full restore. The import procedure reads the tape and populates the database with information regarding the objects present on the tape. so that the import procedure can be used. Before the database can be recovered. media. CAUTION When performing a full recovery of a cell manager system. that you have a manual method of identifying the tapes. You must do this.com U1610S B. with one on the backup tape that may be part of a file system or host backup. also.” can be used to restore program files and libraries that may already be in use.Module 14 Disaster Recovery • Create Logical Device Following installation of the Data Protector software. For this reason. the import procedure can be faster (no other objects on tape) and the tapes can be identified more easily.P. The recovery process requires that the Data Protector database be recovered. etc. depending on the number of objects on the tape. L. TIP It is highly recommended that you have Data Protector database backups write to their own media pool and tapes. Recovery of the database is described later in this module. . • Recover the Data Protector Database The Data Protector database must be recovered before it is possible to access any of the previously performed backups. hp.Module 14 Disaster Recovery U1610S B.com . L.P.00 14-70 2003 Hewlett-Packard Development Company. http://education. com U1610S B. Consolidate the Media Management Database for multiple cells.hp. . Share devices between cells. Centrally manage multiple cells via Manager of Managers.00 15-1 2003 Hewlett-Packard Development Company. you will be able to do the following: • • • • Understand the purpose of Manager of Managers. L.Module 15 — Manager of Managers Objectives Upon completion of this module. http://education.P. ) The Theenterprise enterprisemay mayconsist consistof ofmultiple multiplecells cellsdue dueto: to: •• Geographical Geographicalreasons reasons •• Database limitations Database limitations •• Implementation Implementationof ofseparate separatecell cellmanager managerplatforms platforms(UX. states. or countries.Win) The Thepitfalls pitfallsof ofmaintaining maintainingmultiple multiplecells cellsinclude: include: •• More Moredifficult difficultto toadminister administer(than (thana asingle singlecell) cell) •• Unable Unableto toshare sharebackup backupLogical LogicalDevices Devices(libraries) (libraries)among amongcells cells •• Lack Lackof ofenterprise-wide enterprise-widereporting reportingcapability capability Student Notes Potential Reasons for Use The Enterprise computing environment may consist of multiple Data Protector cells. SLIDE: Manager of Managers Manager of Managers (M.hp. different cities. L.Win) (UX.00 15-2 2003 Hewlett-Packard Development Company.P. for example. U1610S B.Module 15 Manager of Managers 15–1.o. • Communications The communications between the separate locations may be unreliable (WANs).M. Some local control and management of backups is required. http://education. Having multiple Data Protector cells is a perfectly legal configuration and may have been a design consideration for one or more of the following reasons: • Geographical Reasons Separate cells may exist in each geographical location that the company has.com . It is this kind of environment that may have problems with the 8 GB size limit of a single Data Protector database. In essence. it is not possible to share a library between systems in different cells. but some organizations have separate teams administering each platform. this limitation can be a problem. There is no specific reason for doing this. and monitoring. http://education. When multiple cells are implemented. • Implementation of Separate HP-UX and NT Cell Managers You may decide to implement a separate cell manager for HP-UX and Windows clients. − Redirect the display variable to his local system. (unless the cell console is registered) − Then. . Therefore. start the GUI to perform the backup. • Lack of Enterprise-Wide Reporting Capability Reports can be generated only by the cell manager system. They can contain data relating only to the systems that reside in the cell. L. clients are split between multiple cells rather than a single cell. because each cell has its own media management database. schedules. Each cell is autonomous and designed to be managed by the cell manager of the same cell. • Unable to Share Backup Libraries between Cells Typically. templates.Module 15 Manager of Managers • Catalog Database Size Limitations As we explained previously in the database module.P. When backing up many clients that have large numbers of files. the Data Protector internal filenames database has a size limitation of 8 GB. it may be tedious to control all of the backups from a single point. This allows 8 GB x the number of cells. The Pitfalls While the implementation of multiple cells may be justifiable for any of the reasons described above.com U1610S B. the process must be repeated.hp. the only solution is to implement multiple cell managers. large backup device libraries are used in complex environments that may have a requirement to backup very large amounts of data and many files. The same is true with backup specifications. For example. In this case. if a backup of a particular system is to be performed: − The administrator must first log on to the cell manager to which the system belongs. it can cause many headaches: Difficult to Administer • Administration of multiple cells is more complicated. If a backup is to be performed on another system belonging to another cell.00 15-3 2003 Hewlett-Packard Development Company. effectively spreading out the size of the database. and control over the enterprise backup environment of up to 50 Data Protector cells from a single point.00 15-4 2003 Hewlett-Packard Development Company.hp. This means that any device in a cell using the CMMDB is available to all cells using the CMMDB. SLIDE: Features Features M.M. http://education.M. M. • Centralized Media Management Database (CMMDB) Optionally. and reporting of the status of the whole environment. Features Features •• Centralized Centralizedmanagement managementof ofall alltasks tasks •• Enterprise reporting Enterprise reporting •• Centralized Centralizedlicensing licensing •• Distributed Distributedcatalog catalogdatabases databases(CDB) (CDB) •• Centralized media management Centralized media managementdatabase database(CMMDB) (CMMDB) •• Sharing of library backup devices Sharing of library backup devices Student Notes • Centralized Management of All Tasks Centralized management of all tasks allows configuration.O. central database to manage devices and media within the enterprise. management.P.Module 15 Manager of Managers 15–2. Allowing systems in different cells to share expensive devices may better utilize them. This includes backup configuration. U1610S B. • Shared Libraries When using the centralized media management database. media management.O. monitoring. you can share high-end devices among cells in a multi-cell environment. L. all the cells in the environment can share a common.com . This lets you have multiple databases in your enterprise backup environment. L. resulting in up to 50 times the single cell database space.Module 15 Manager of Managers • Centralized Licensing Centralized licensing allows one central location to administer the licenses for all backup environments (cells).P. • Distributed Data Protector Database The database containing all the information on data backed up is split amongst each of the cell managers in the environment. When the MoM environment is configured.com U1610S B. http://education.hp. . connecting to the MoM cell server from the Web interface will give access to multi-cell reporting. • Enterprise Reporting The Data Protector Manager-of -Managers can generate reports on a single cell.00 15-5 2003 Hewlett-Packard Development Company. as well as for the entire enterprise environment. The systems may be located in different geographical areas and time zones.Module 15 Manager of Managers 15–3.com . L. consists of a number of systems from different vendors. with different operating systems.00 15-6 2003 Hewlett-Packard Development Company.P.hp. SLIDE: Concepts Concepts Large Enterprise Backup Environment Student Notes What Is an Enterprise Environment? A typical enterprise network environment. When to Use an Enterprise Environment? This solution can be used when several geographically separated sites require common backup policies. http://education. All the systems are connected with LAN or WAN networks operating at various communication speeds. shown above. It can also be used when all departments at the same site want to share the same set of backup devices. U1610S B. com U1610S B.P. This layer enhances Data Protector’s scalability and allows easy backup. There can be multiple (up to 50) client/remote cells. there are no additional processes installed on this system. With the Data Protector Manager-of-Manager concept. Data Protector Manager of Manager has been designed to simplify this task.Module 15 Manager of Managers Where Does Manager of Manager Fit In? Configuring and managing backups of such a heterogeneous environment is challenging. . and provide a new graphical user interface (xomnimom/mom.00 15-7 2003 Hewlett-Packard Development Company. share its media management database. • • • • Multiple cells can be managed from a single location. http://education. L. The manager cell can be thought of as having a special cell manager running. The Data Protector cell manager acting as the MoM cell manager can handle additional tasks.hp. One Data Protector cell manager acts as the Manager of Managers server. Remote MoM-client cells can be connected via LAN or WAN. The Data Protector Manager of Managers concept adds an additional hierarchical layer to the already known Data Protector architecture.exe) to show the view of multiple cells. and device and media management of large distributed environments. one cell acts as the manager cell and the other cells run as client cells. However. restore. Install the proper licenses on the Manager-of-Managers. L. •• Restart RestartData DataProtector Protectorservices/daemons services/daemonson onall allcells. cells. http://education. as well as on every cell in the MoM environment. Configure MoM server. server.Module 15 Manager of Managers 15–4. •• Configure MoM server. Configure the MoM Manager (see the following page).hp. Import cells to the MoM environment. 2. •• Import cells to the MoM environment.00 15-8 2003 Hewlett-Packard Development Company. 3. Student Notes Configuring the Data Protector Manager-of-Mangers (MoM) consists of the following steps: 1. cells. •• Create Createa acommon commonAdministrator Administratoraccount accounton onall allcells. Restart the Data Protector processes (daemons/services) on all cells. Each of these steps is described in the following pages. •• Install “Manager Install “Managerof ofManager ManagerExtension” Extension”licenses. Create an Data Protector Administrator account that is common for all cells. licenses.P. 4. Choose which cell will act as a MoM Manager.com . SLIDE: Configuration Steps Configuration Steps •• Choose Choosea aMoM MoMserver. U1610S B. Import Data Protector cells into the MoM environment. 6. 5. -rw------. 1. consider using Highly Available Clusters. manually and via the GUI.com U1610S B. Make sure the file has permissions as shown. execute the /opt/omni/sbin/omnisv stop command to stop the Data Protector services. touch /etc/opt/omni/cell/mom_info 3.P. See the HP OpenView Data Protector Installation and Licensing Guide or the Installation module in this course for more information on how to configure the Data Protector cell manager system. The MoM Manager system should be highly reliable. The Data Protector MoM GUIs are part of the standard Data Protector cell console package. Start the manager of managers user interface: xomnimom http://education. 2. the Manager-of-Manager extension license must be installed on each Data Protector cell manager that takes part in the MoM environment Configuring a MoM Manager This section describes how to configure an HP-UX Data Protector cell manager as a MoM Manager. • Install Licenses In order to activate the Data Protector MoM features.00 15-9 2003 Hewlett-Packard Development Company. It will contain the list of managed cell managers. L. The MoM server is included as part of the standard Data Protector cell manager package. • The system must already be an Data Protector cell manager. This file cannot be edited manually. Create an empty file named mom_info in the /etc/opt/omni/cell directory. Login as the root/administrator user on the management server. 4.1 root sys 0 May 18 17:07 mom_info 5. with the software installed.Module 15 Manager of Managers There are additional configuration tasks that you may want to perform to use some specific MoM functionality: • • • Configuring a centralized media management database.hp. The Data Protector Manager of Manger requires installation of no additional executables. . Run the omnisv start command to start the Data Protector services. Distributing the MoM configuration Choosing a MoM Manager This section describes the prerequisites for the MoM Manager system. Configuring centralized licensing. Highlight the Cell Manager system. 3. be sure to exit the GUI first. Verify that the mom_server file has been created in the <OMNICONFIG>/cell directory. and that it contains the FQDN of the MoM cell server.com . 2.Module 15 Manager of Managers Note: Creating the empty mom_info file may be accomplished via the GUI: Select the Clients context for the Scoping Pane. 4. Select the Actions Menu item: “Configure CM as Manager-of-Managers Server” You will be prompted to restart the Data Protector servers. 5.00 15-10 2003 Hewlett-Packard Development Company.hp. /opt/omni/sbin/omnisv –stop (Unix) b.P. <OMNIHOME/bin/omnisv –start (Windows) 6. <OMNIHOME/bin/omnisv –stop (Windows) d. Restart the Data Protector servers: a. 1. /opt/omni/sbin/omnisv –start (Unix) c. http://education. U1610S B. L. you must have a user. tasks. (or another username of your choosing) http://education. Log in to each cell manager in the multicell environment as root/Administrator. This user will be the MoM administrator. 1. .Module 15 Manager of Managers 15–5. This user will be the MoM administrator. Add the MoM Administrator (Mom_Admin) to the Data Protector admin User Class. L.hp. use the following procedure: Add a MoM Administrator to Cells Before you can use the MoM GUI to administer remote cells. the the MoM MoMGUI GUI has hasadditional additionalfeatures: features: •• Import Importand andexport exportcells cells •• Move clients between Move clients betweencells cells •• Distribute Distributecommon commonMoM MoMconfiguration configurationfiles: files: – User class specifications – User class specifications – – Holidays Holidaysfile file – Global – Globaloptions optionsfile file – Vaulting locations – Vaulting locationsfile file Student Notes In order to run the Data Protector MoM GUI. you have a user called Mom_Admin in every Admin group on each cell in the enterprise. belonging to the Admin user group. in every cell in the environment.00 15-11 2003 Hewlett-Packard Development Company. For example.com U1610S B. 2.P. SLIDE: MoM GUI MoM GUI In In addition additionto tothe thestandard standard cell cell manager managertasks. do the following: 1. 3. switch to the Client. you will not have permission to the remote cell. (Optional) You do not need to perform this step if the system is the MoM Server system. Add the root/Administrator of the mom_server to the Admin group on the imported cell to gain full permission to control the cell. and from the pop-up menu Import Cell Manager. you must manually create this file. Import Cells to the MoM Environment To import an Data Protector cell to the MoM multicell environment. You can now continue by importing the Data Protector cells into the multi-cell environment.Module 15 Manager of Managers Configure the MoM GUI 1.1 root sys 18 Jun 18 17:07 mom_server Make sure the file has permissions as shown. The Data Protector Manager of Manager user interface module must be installed on the system where you want to run the user interface. 4. or <OMNIHOME>/bin/mom. although you are registered as the mom_server. NOTE The mom_server file is created automatically on the cell manager system when it is imported into the MoM environment. standard on HP-UX). (This is an optional component of Windows cell manager systems. U1610S B. This would be necessary in those cases when the cell console is distributed amongst the clients in the cell. This opens the Data Protector Manager-of Managers GUI. Start the MoM user interface with the /opt/omni/bin/xomnimom. It is for other systems from which you want to be able to run the GUI: Create the following file in the <OMNICONFIG>/cell directory. In the Data Protector .hp. If you are not the root/Administrator user of the imported cell. select Enterprise Clients from the Scoping Pane. L.00 15-12 2003 Hewlett-Packard Development Company.com . 2. http://education. which provides access to all MoM functionality.exe command. containing the system name of the MoM Manager: -rw-r--r-.P.Manager-of-Managers window. 2. If the client is to connect to the correct MoM server (and not the local cell manager). Stop the Data Protector daemons by entering the following command: /opt/omni/sbin/omnisv stop <OMNIHOME>/bin/omnisv stop (HP-UX) (Windows) 2. Use Export Cell Manager to remove client cells from the Data Protector MoM environment.P. The user must login in as root/Administrator and do the following: 1.00 15-13 2003 Hewlett-Packard Development Company.hp.Module 15 Manager of Managers This results in: • • The <OMNICONFIG>/cell/mom_server file on the client cell manager system is updated with the name of the Data Protector MoM cell manager system name. you will be notified to restart the Data Protector daemons on each imported cell that uses CMMDB on the MoM Server. The <OMNICONFIG>/cell/mom_info file on the Data Protector MoM cell manager system is updated to include the name of the new client cell manager system. Restarting Data Protector Services When you have configured the MoM environment. . L. Start the Data Protector daemons by entering the following command: /opt/omni/sbin/omnisv start <OMNIHOME>/bin/omnisv start (HP-UX) (Windows) http://education.com U1610S B. The hostname will be removed from the <OMNICONFIG>/cell/mom_info file and will empty <OMNICONFIG>/cell/mom_server on the client system. it is possible that the GUI can be run from any of the cell manager systems as long as configuration allows. The MoM GUI is part of the standard. L.P. U1610S B.00 15-14 2003 Hewlett-Packard Development Company. regardless of whether it is a normal cell manager.hp. cell console package. If the Data Protector device and media management databases are being shared. it communicates directly with all the cell managers. the MoM GUI is not restricted to the MoM cell manager system alone. http://education.Module 15 Manager of Managers 15–6. In other words. or MoM and client cell managers for GUI communication. it is possible for a client system to directly communicate with another cell manager system for non-MoM GUI activity. SLIDE: Communication Communication Cell Manager/ Manager of Manager Cell #1 Client System Client System Mom GUI Cell Manager Cell #3 Cell Manager Client System Client System Client System Client System Cell #2 Student Notes The MoM GUI communicates directly with the cell manager systems that are part of the MoM environment.com . therefore. When the Data Protector MoM GUI is running on a client system. Client Systems to Cell Managers Client systems communicate directly with their Data Protector cell manager system. com U1610S B. L. with one exception. . When central licensing is distributed from the Manager of Managers cell manager. http://education.hp.00 15-15 2003 Hewlett-Packard Development Company. This is covered in the client system and cell manager communication above since in this case the MoM cell manager system is also acting as a client system.P. • Client System to Client System Client systems belong to one cell and normally do not communicate with client systems from another cell. it is possible for client systems to communicate directly.Module 15 Manager of Managers Manager-of-Manger Cell Manager to Client Cell Manager There is little communication between the Manager-of-Managers cell manager and client cell managers. If the Data Protector device and media management databases are being shared. with the following exceptions: • If the MoM GUI is running from the MoM cell manager system. com . media. http://education. their configuration. In a typical. Therefore. it is impossible to access and use this data from another Data Protector cell.P. directories. The Catalog database (CDB) stores information about data backed up. and versions. without moving them to the other cell. L. SLIDE: Distributed MMDB and CDB Distributed MMDB and CDB Cell #1 MoM Server CDB IDB MMDB WAN Cell #2 Cell Manager LAN Cell #3 Cell Manager MMDB CDB CDB IDB MMDB MMDB MMDB IDB MMDB Student Notes In a normal configuration.hp. such as files. which stores information about backup devices. and media used for backup. both parts are located on the cell manager system and keep information on devices. cell-oriented environment. The database is actually composed of two embedded parts: • • The Media Management database (MMDB). For security reasons. and backup information for that cell. media and devices used in a cell cannot be accessed and used in some other cell.00 15-16 2003 Hewlett-Packard Development Company. each Data Protector cell manager system maintains its own internal database.Module 15 Manager of Managers 15–7. U1610S B. and catalog information. http://education. devices. Device sharing can be achieved by having one centralized MMDB for all the cells and keeping an individual CDB for each cell.P. in that only the cell manager of that cell maintains information about the backups. When using Manager-of-Manager. media. Each cell is autonomous.com U1610S B. .hp.00 15-17 2003 Hewlett-Packard Development Company.Module 15 Manager of Managers In larger multi-cell environments with high-end backup devices. you may want to share these devices and media among several cells. L. This allows media and device sharing while preserving the security capabilities of the multi-cell structure. this distributed model can be left in place (default). or the media management databases can be merged and centralized. SLIDE: Central MMDB Central MMDB (CMMDB) — Distributed CDB Cell #1 MoM Server IDB CDB WAN Cell #2 Cell Manager LAN CMMDB Cell #3 Cell Manager CDB CDB CMMDB IDB IDB Student Notes The CMMDB on the MoM cell server allows you to share devices and media across several cells in a MoM environment. each cell is no longer autonomous. it is recommended only when using local LAN connections.hp.Module 15 Manager of Managers 15–8.P. this is when multiple cells have been implemented to overcome database capacity issues. It may be highly desirable to centralize the media management databases if multiple cells are being maintained on the same local site (connected via LAN). Once the media management databases have been centralized. This makes devices of one cell (using the CMMDB) accessible to other cells that use the CMMDB. A reliable network connection is essential between the MoM cell and the other Data Protector cells. but not WAN. L. as it must obtain information on devices and media from the central MoM server's centralized media management database.00 15-18 2003 Hewlett-Packard Development Company. U1610S B. Typically. Therefore. http://education. Note that it is optional to centralize the Media Management database.com . as it does not have any protected data on it. If it is implemented. whether it should use the CMMDB or its own local MMDB. any other cell can use it. only by the cell that owns it.hp.P. If a tape is loaded in a library and not yet initialized. NOTE Once you have configured the CMMDB and start using it. NOTE If you are configuring a new cell (and you do not yet have devices and media configured).com U1610S B. NOTE Each cell manager ALWAYS has its own Catalog database (CDB). which is useful when certain client cell managers are connected to the MoM server over unreliable data links. where the bulk of the Data Protector database resides. You can decide for each cell. Immediately after the MMDB is changed from local to remote. located in following directory for all media requests: On HP-UX: On Windows NT: /etc/opt/omni/cell <Data Protector_home>\config\cell Data Protector operation and the user interface see the MMDB in the same way. If a tape has been initialized by one cell. Once this protection has expired.00 15-19 2003 Hewlett-Packard Development Company. there is no need to merge the database. however. The media allocation rules apply in exactly the same way to shared tapes. Each medium that contains protected data has information showing which cell currently owns the data. It may be possible that you recover the old state of an MMDB. NOTE The centralized MMDB has a big effect on licensing. It is recommended that you start from scratch with a new MMDB. and import all the tapes since the merge occurred. You want to merge cells only with the CMMDB that already has devices and media. Data Protector goes to the cell manager specified in the file mmdb_server. any cell can initialize it. . They can be removed from client. http://education. Configuring a Centralized Media Management Database This section describes how to configure a centralized media management database for the whole multi-cell environment. and no other tapes are available. it is not possible to split it back into local MMDBs. L. When CMMDB is used. any cell can reuse the medium.Module 15 Manager of Managers The implementation of the CMMDB is optional. If required this process will also merge the local Media Management Database into the CMMDB. all the licenses associated with libraries and devices are validated from the MoM server. assuming there is a loose policy. except that appendable media can be appended. you can also choose on which systems MMDBs will be centralized. This always happens to the default pools. Repeat steps 3 and 4 for all the client cells you want to add to the CMMDB. The duplicated names have a “ _N” appended to their name.Module 15 Manager of Managers Procedure On the MoM.com . d.00 15-20 2003 Hewlett-Packard Development Company. 6. or media management sessions running on any of the cells to be added to the enterprise (multi-cell) environment. On each MoM server client cell. Log onto the MoM Manager and copy the /var/opt/omni/db40/datafiles/mmdb directory to a safe location. edit the duplicated names of media pools and devices (in the user interface). restore. On the MoM server. to indicate from which cell the pool has come. perform the following: 5. Log on to the cell manager of the client cell as user root. run the following command: omnidbutil –mergemmdb client_cell_server_name NOTE The -mergemmdb option requires exclusive access to both databases (MoM and client cell manager) 4. L. On the MoM manager. /opt/omni/sbin/omnisv –stop cd /var/opt/omni/db40/datafiles cp –rp mmdb mmdb. where N represents a number. you must add one cell at a time to the CMMDB. Before proceeding. you must manually change the backup specifications that use these devices to use the new device names. http://education.P. c. you must have exclusive access to both the MoM database. a. so that it is available if you want to recover the unmerged MMDB later. It is a good idea to add a line to the media pool’s description. Check that there are no backup. Data Protector cell managers in all cells must have the new version of Data Protector installed and running. 1. b. U1610S B.before_mom /opt/omni/sbin/omnisv –start 3. containing the name of the MoM manager.hp. (fully qualified) NOTE The mmdb_server file may be a copied from the mom_server file. In this case. 2. if they exist in both cells. as well as the client cell server’s database. Create the <OMNICONFIG>cell/mmdb_server file. hp.P.00 15-21 2003 Hewlett-Packard Development Company. L. Stop and restart the Data Protector processes: omnisv stop omnisv start 8.com U1610S B. . Update configuration files on the CMMDB host: omnicc -update_mom_server http://education.Module 15 Manager of Managers 7. P. These individual licenses are restricted to the cell on which they are installed. U1610S B.hp. http://education. SLIDE: Central Licensing Central Licensing Licenses must be generated using IP address of MoM server. Student Notes Manager of Managers — Licensing When enterprise management is implemented via MoM. Licenses are allocated to client cell managers.00 15-22 2003 Hewlett-Packard Development Company. L. You may install individual licenses on each cell instead of central licenses. central management of your Data Protector license is available as an additional feature. Client cell managers contact the MoM for license information.Module 15 Manager of Managers 15–9. All licenses are stored on the MoM server. All licensing administration tasks will have to be performed on each cell.com . Module 15 Manager of Managers Why Centralized Licensing is Better Data Protector allows you to configure centralized licensing for the whole MoM environment. and licensing to MoM and centralized licensing. You can then allocate licenses to specific cells to suit your needs. you must complete “License Move” requests and submit them to the licensing center. In the Manager-of –Managers GUI. Select the server that has the licensing information you want to change. See the “Installation and Licensing Guide” for more information. you can change the license at any time. The Mayan cell now needs three more “ Multi-drive Server for UNIX” licenses. The Aztec cell is reorganized.P. The Mayan cell manager is another UNIX system with one multi-drive server in its cell. suppose you have two cell managers in your enterprise environment. configured with centralized licensing. L. removing the licenses from one cell and adding them to another is a relatively simple task that can be achieved via the MoM GUI. and the other is named Mayan.00 15-23 2003 Hewlett-Packard Development Company. switch to the Clients context. Therefore. All licenses are installed and kept on the single MoM server system. Once a license has been allocated to a cell. 2.hp.com U1610S B. However. Aztec has four “ Multi-drive Server for UNIX” licenses. and vice-versa. with most of the clients and three of the multi-drive servers being transferred to the Mayan cell. Increasing the number in this column will correspondingly decrease the number of available licenses. if you are converting an existing environment from separate cells. One is named Aztec. Thus. In this window. The types and numbers of licenses available to your selected cell manager appear in the Results Area: The USED column shows the number of licenses assigned to that particular server. . from the pop-up menu choose Configure Licensing to open licensing configuration in the Results Area. it can only be used in that cell. NOTE This means that the licenses must be generated by the HP password center using the IP address of the MoM server system. select the MoM cell server. for a total of four. For example. Central Licensing Configuration 1. you can see the current licensing configuration for all cell managers in the multi-cell environment. Mayan has one “Multi-drive Server for UNIX” license. The Aztec cell manager is a UNIX system with four multi-drive servers in its cell. http://education. NOTE The instant-on evaluation license does not permit MoM license configuration. Licenses are allocated for a specific cell and are not floating licenses. Because these two cell managers are in an enterprise environment. dat file is used if available. The TOTAL column shows the total number of licenses. The lic_server file will contain the name of the MoM manager acting as the license server. Select Finish to apply the configuration.hp.Module 15 Manager of Managers The AVAILABLE column shows the number of licenses available to the entire enterprise. Select the desired license “Used” column. licensing information from the local <OMNIHOME/cell/ lic. L. License Configuration Files The license configuration selected for a client is stored on the cell manager in the <OMNICONFIG>/cell/licdistrib. MoM managed licenses will receive a configuration file called <OMNICONFIG>/cell/lic_server. If Data Protector does not find this file. increase its corresponding number in the USED column. This is the number of licenses not taken by any cell within the enterprise environment. 4. Systems that are selected to use the remote. the last licensing status is kept for 72 hours. This hostname in the lic_server file must be the fully qualified name for the MoM server (this should occur by default) if DNS is used for host name lookup. When the Data Protector services start and find this lic_server. U1610S B. http://education. both used and available. Giving up Licenses To give up a license type. select to increase or decrease the value.00 15-24 2003 Hewlett-Packard Development Company.dat file is used to hold the license information when local licensing is used.com . 3.P. in the entire enterprise. Getting Licenses To get a license type. The lic. In case of a communication problem. thus increasing the number available. reduce its corresponding number in the USED column. Data Protector will check licenses with the MoM server every hour.dat. follow these steps: 1.” from the pop-up menu select: Distribute Configuration. Importing and Exporting Data Protector Cells Importing a cell into an enterprise environment allows it to be centrally managed with the Manager-of -Managers.P.Module 15 Manager of Managers 15–10. http://education. In the HP Data Protector . Checks if there are any devices configured on the system then leads you through the steps to move devices to another system. select “Enterprise Clients. TEXT Page: Added Functionality (MoM GUI) The Manager of Managers interface allows you to view and manage an environment consisting of multiple Data Protector cells. open one of the cell managers client lists from the Scoping Pane. some additional features are provided. vaulting. Create the desired user class specification.00 15-25 2003 Hewlett-Packard Development Company. and vaulting on all cell managers in a MoM environment. Select the client you want to move to another the cell manager. then leads you through the steps to move the media. holiday file settings. 2. global options file settings.Manager-of -Managers window. . L. To distribute the MoM configuration. Checks if there are media used in the devices on this system. As well as providing remote administration of a cell in the same way as running the Data Protector GUI locally. OmniBack II does the following: • • • It checks to see if the system is configured in any backup specifications.com U1610S B. Moving Systems between Cells Data Protector allows you to move systems between cells. 3. Exporting a cell removes it from the enterprise environment. and global options settings on the MoM manager. 1. During the process. Distributing the MoM Configuration Data Protector allows you to create a common user class specification. Select Move Client System to Another cell from the pop-up menu in the Scoping Pane. then leads you through the steps to reconfigure backup of this system in the new cell. In the Scoping Pane.(select the “+” next to the hostname) 2.hp. holidays file settings. L. U1610S B. http://education.Module 15 Manager of Managers 3.com . In the HP Data Protector . select the type of configuration and the cell managers to which you want to distribute the selected configuration. 4.hp.00 15-26 2003 Hewlett-Packard Development Company. Click Finish to distribute the MoM configuration.Distribute Configuration window.P. the MoM system should be highly available. A special license must be purchased before MoM can be used.hp. L. Name four reasons for implementing Manager of Manager? 2. the catalog databases can also be merged. TRUE/FALSE? http://education.00 15-27 2003 Hewlett-Packard Development Company.com U1610S B. A merged database can easily be unmerged. When using a centralized media management database. TRUE/FALSE? 8. Why? 6. What command is used to merge the media management databases? 7. TRUE/FALSE? 3.P. What configuration information can be distributed from the MoM GUI when using the Distribute Configuration function? 5. When using MoM. Review Questions 1. why must a “license move” request be submitted to the password center? 4.Module 15 Manager of Managers 15–11. . When implementing centralized licensing in an existing environment. hp.com . L. http://education.P.Module 15 Manager of Managers U1610S B.00 15-28 2003 Hewlett-Packard Development Company. Module 16 — Troubleshooting Objectives If you have problems with Data Protector.P. .00 16-1 2003 Hewlett-Packard Development Company. user interface. and starting backup/restore sessions http://education. use the suggestions in this module to get back on track.com U1610S B.hp. devices. L. such as network. including information on: • • • • • Data Protector log files Process tracing Browsing troubleshooting messages What to do when you cannot access the online troubleshooting A description of common problems. log omnisv. http://education.log Valuable troubleshooting information can be obtained by examining the Data Protector log files. The following table shows the directories where the log files can be found: Unix /var/opt/omni/log Windows NT All logs except the RDS. Other UNIX Systems /usr/omni/log U1610S B.P.log file are stored in this directory: <Data_Protectory_home>\log Installation logs will be in the system “tmp” directory.log inet.log file is located in the <OMNIHOME>\db40\catalog directory.log IS_install.log trace.hp. L.00 16-2 2003 Hewlett-Packard Development Company.log sm.log media.log upgrade.log RDS.Module 16 Troubleshooting 16–1.log debug. SLIDE: Log Files Log Files UNIX: /var/opt/omni/log Windows: <OMNIHOME>/log cleaning. such as C:\temp The RDS. Student Notes The directory in which Data Protector log files are kept depends on which operating system you are using.log Upgrade.com . On Windows.log Upgrade. .log informix.log media.Module 16 Troubleshooting Netware SYS:\USR\OMNI\LOG The following list shows the Data Protector log files and describes their contents: cleaning. For this reason. this starts the integrated help. This file contains the trace of the remote installation and is located on the installation server.com U1610S B. select Help Help Topics from the toolbar. This is a very important file.log oracle8. This is the log file of the Data Protector internal database. a new entry is made to this log. Application specific logs contain traces of the integration calls between the application and Data Protector. This log file contains errors that occur in backup and restore sessions. debug.log This file records all Data Protector initiated tape-cleaning events. While some can be meaningful to the user.log sm.log oracle.P. such as errors in parsing the backup specifications. These log files are located on application servers. This file is updated when Logical Devices have the Cleaning Tape option enabled and they are in the clean-me state.hp. Media that contains the Data Protector database backup is also marked.log can be used after disaster recovery to find the tape where that database was backed up and what media were used after the database’s last backup. To start the help system from within the GUI. This file is updated when the Data Protector services are stopped and started.log Online Help Data Protector provides extensive help via an integrated help system. This log is created during the upgrade and contains traces of the upgrade processing.log omnisv. Unexpected conditions are logged into this file. or imported. Each time a medium is used for backup.log RDS.log IS_install.log (UNIX only) sap. It can be useful to check the recent activity of Data Protector on client systems.00 16-3 2003 Hewlett-Packard Development Company. Requests made to Data Protector’s inet program (a program that starts agents) are logged to this file. media. http://education. it is used mainly by the HP support organization. on HP-UX the Netscape browser will start.log sybase. L.log inet. It can be used for integration troubleshooting. initialized. However.hp. It can be used to trace virtually any Data Protector command. daemon. SLIDE: Execution Tracing Execution Tracing Execution tracing provides highly detailed information. Student Notes Data Protector processes may be started in a special mode called the "debug" mode to allow for extensive tracing of their execution. U1610S B. This execution tracing produces voluminous data sets which may consume a significant amount of disk space.P.00 16-4 2003 Hewlett-Packard Development Company. use with caution. When to Enable Debugging You should collect debugs only when the support organization requires them to resolve a technical issue. Consult the support organization about the detail level that should be applied and environmental conditions for running Data Protector in the debug mode. trace output is in ASCII and can provide useful information for administrators. When Data Protector runs in debug mode. Example: xomni -debug 1-99 /mydir SUFFIX Manager –debug 1-99 \temp SUFFIX Reading execution trace output requires special knowledge and is normally performed by HP Support. or service.Module 16 Troubleshooting 16–2. it creates debug information that consumes a large amount of disk space. L.com . http://education. This is useful for the HP Support Center to assist you in troubleshooting situations with your cell. The tracing produces a set of “debugs” that may be needed by HP Support. Module 16 Troubleshooting How to Create Execution Traces There are several methods that may be used to trace various components within Data Protector. in the File menu. Debugging Using the OB2OPTS Variable Debugging parameters for Data Protector integrations can be set using the OB2OPTS environment variable. Debugging Scheduled Sessions To debug scheduled sessions. L.hp. Debugging parameters must be added in the first line of the file. http://education. Debugging Using the Trace Configuration File Edit the trace configuration file (/etc/opt/omni/options/trace on UNIX and <OMNIHOME>\Config\Options\trace on Windows). Below are several common methods: • • • • • Debugging Using the Data Protector GUI Debugging Using the Trace Configuration File Debugging Scheduled Sessions Debugging Using the OB2OPTS Variable Debugging as a Command Line Option Debugging Using the Data Protector GUI To set the options for debugging using the Data Protector GUI. then restart the Data Protector services.P. . The GUI will be restarted in the debug mode. Specify the debug options and restart the GUI.com U1610S B. click Preferences. and then click the Debug tab. For more details about the OB2OPTS variable refer to the HP OpenView Storage Data Protector Integration Guide. edit the schedule file (/etc/opt/omni/schedules or /etc/opt/omni/barschedules on UNIX and <OMNIHOME>\Config\Schedules or <OMNIHOME>\Config\BarSchedules on Windows).00 16-5 2003 Hewlett-Packard Development Company. Trace files are created in: /tmp on UNIX <OMNIHOME\tmp on Windows And named: OB2DBG_<DID>_[<SID>]_<Program_Name>_<Host>_<PID>_<Postfix Where: is the debug ID. 1 is seconds. The entire list must be put in quotes. 1000 is milliseconds.domain". DA) Program Name is the program name of the Data Protector program writing the trace Host is the system name where the trace file is created PID is the process ID. this is the PID of the first process that accepts the debug parameter.Module 16 Troubleshooting Debugging as a Command Line Option Most all Data Protector commands can be started with an additional -debug parameter: <DP command> -debug 1-99. DID U1610S B.C:n.domain host2. L. is the size limit (KB) for the debug file to enable circular logging is the timestamp resolution.T:s POST host Where: 1-99 C:n T:s POST Host is the debug range.log on the Cell Manager whenever tracing is enabled. where 0 is off.hp.P. The list of hostnames limits the hosts where the debug is turned on during execution of the Data Protector command. The range should always be specified as 1-99. This trace log contains information about when and where debug traces where generated within the cell. The debug postfix option is used for creating the trace file name. all debugs are “children” of this process SID is the session id added by backup and restore agents (MA.com . they should be delimited by spaces. If more than one host is on the list. For example: "host1. is the debug postfix added to each file produced by the tracing is the quoted list of hostnames where the debug is turned on. http://education. Trace logging Data Protector creates a log file called trace. unless requested otherwise by HP Support. POST is the postfix as specified in the -debug parameter.00 16-6 2003 Hewlett-Packard Development Company. Restart the Data Protector Inet service with the following startup parameter: -debug 1-99 POSTFIX CRS Trace on Windows NT/2000 In order to generate cell manager execution traces on Windows NT/2000. is the time ID that guarantees that it is unique. use the -debug option with care.log to omni stream tcp nowait root /opt/omni/lbin/inet inet -log /var/opt/omni/log/inet. http://education.conf file and change the following line: omni stream tcp nowait root /opt/omni/lbin/inet inet -log /var/opt/omni/log/inet. with a maximum of three characters. is the postfix. INET Trace on UNIX To generate INET execution traces on UNIX.POST Where: Prog Time POST is the code name of the Data Protector program. all integrations will generate trace log files.hp.00 16-7 2003 Hewlett-Packard Development Company. NOTE Execution traces can become very large.P. then Services. edit the /etc/inetd.Module 16 Troubleshooting On Netware. L.log -debug 1-99 SSF INET Trace on Windows NT/2000 In order to generate INET execution traces on Windows NT/2000. open the Control Panel. open the Control Panel. then Services. Stop the service and then restart the Data Protector CRS service with the following startup parameter: -debug 1-99 POSTFIX cell_manager_hostname NOTE If you enable INET debugs. the trace file name is: SYS:\USR\OMNI\TMP\ProgTime.com U1610S B. For this reason. . it creates a large volume of debug information on the system.ctx files written by Data Protector. cell manager only.. every system) − Collect also the standard debug logs 2. On the cell manager and the client: Look at the following directories: On UNIX On Windows /tmp \<OMNIHOME>\tmp You should see only crs. Delete any files from previous debugs (. such as "1-99") − Debug scope (client only.00 16-8 2003 Hewlett-Packard Development Company.hp. Try to reduce the error environment as much as possible.com . Return your environment to normal operation.pid and the mmd.. Have only ONE failing client involved in the debug run The following is useful only if the error is reproducible: 3. • • • • Prepare the environment for the debug run. L._error_run. Collecting debugs can be grouped into the following tasks: Discuss with the support organization what detail level should be applied and what environmental conditions to use for the debug run. such as: Create a backup specification that contains just one file or a few objects. Discuss with the support organization the technical issue and request the following information: − Debug level (this is a command option needed later. When Data Protector runs in debug mode. Collect the debug information.txt) U1610S B. Perform the debug run. which needs to be managed. The following steps show how to collect debug information for a typical issue. which involves one client and the cell manager (example from the Admin Guide): 1.P. http://education.Module 16 Troubleshooting Execution Trace Example Debug information should only be collected when you have been asked by the support organization to do so in order to follow up on the resolution of a particular technical issue you have experienced. 7.txt xomni -debug 1-99 error_run. Windows 2000 Pro SP2 Topology information (command output of omnicellinfo -cell on cell manager) On the system where the (tape) devices are connected. execute the command: devbra –DEV Put the output in the info file. examples: HP N-4000 Series. .P.. Move Data Protector into the error situation. HP Netserver For Windows NT systems with devices connected: SCSI controller used (onboard_type/Adaptec xxx/.11. Exit all OB2 GUIs (close the OB2 application).txt This brings up the manager GUI and starts the debug mode.(re-execute the problem) 10. output redirection might not work. 9..com U1610S B. (Careful. On the cell manager: On Windows NT <OMNIHOME>\bin\omnisv -stop (modify the necessary services as described previously) <OMNIHOME>\bin\omnisv -st On UNIX /opt/omni/sbin/omnisv –stop (modify the necessary configuration files as described previously) /opt/omni/sbin/omnisv -start 8. examples: HP-UX 11.Module 16 Troubleshooting 4. In case you need to collect CRS debugs as well (per support organization instruction) you need to: Stop the Data Protector services on the cell manager. On the cell manager (after adapting).) 5.hp. You can define the postfix of the trace file names created by substituting the error_run text with your preference.00 16-9 2003 Hewlett-Packard Development Company.. L.) Operating System information. http://education. media agent and disk agent system). This cancels the debug mode for the Data Protector manager. Create an info text file containing the following: Hardware identification of the systems (cell manager. enter a command similar to: On Windows NT On UNIX manager -debug 1-99 error_run. 6. Exit all OB2 GUIs and stop all other backup activities in the cell. (omnisv –stop) Restart the services with debug. WINZIP. Shar/uuencode or otherwise mail the files to the support organization.00 16-10 2003 Hewlett-Packard Development Company. You will see several . you need to: − − Stop the Data Protector services on the cell manager. 15._error_run. Gzip.. http://education. Compress and pack ALL the . If the error includes the usage of a client system. U1610S B. 17.. collect them as well._error_run. Cleanup the /tmp directories by deleting the .. 14.hp. Give information about how you packed or compressed the file in the mail.com .Module 16 Troubleshooting 11._error_run.txt files. In case you need to collect CRS debugs as well (per support organization instruction). 12._error_run. or TAR.P. you also need to collect the .txt files and the info file using compress. 16. 13.txt files from the client and include them in the package. L.txt files.. In case the support organization asked you to collect the standard debug log files. Look at the /tmp directories (on the cell manager and on the clients).... Restart the services without the debug option.. . when Data Protector is idle. during a backup. L.P. restore or media sessions. and Where Processes Run The following table shows which processes run where.hp. and when. When.00 16-11 2003 Hewlett-Packard Development Company. http://education.com U1610S B.Module 16 Troubleshooting Process Overview Which. the message number may be selected to reveal the troubleshooting utility dialog window. http://education.00 16-12 2003 Hewlett-Packard Development Company. Troubleshooting Data Protector Messages An example of the error message ID number format is: [x:y]. Possible action(s) that may be taken to solve or avoid the problem. A check box to view the message description and action. Detailed description of the error message.Module 16 Troubleshooting 16–3. You can get a detailed explanation of messages that occur within a running session by selecting the message ID number. When displayed during a session.P. Data Protector provides additional information with an interactive troubleshooting dialog.com . U1610S B. The dialog window consists of four text fields: Message Text Details Description Actions You will see the message as displayed in the session. L.hp. SLIDE: Message Details Message Details Click for details Student Notes In case of difficulties during the operation. ACTION: Before contacting your post-sales Data Protector Support Representative. Every single message has three fields that are organized in the same way as online troubleshooting: MESSAGE: DESCRIPTION: ACTION: Error message as it appears in Data Protector. Report this error to your post-sales Data Protector Support Representative.hp. .Module 16 Troubleshooting When You Cannot Access Online Troubleshooting If the user interface cannot be started. http://education.g.txt on Windows An example of one error message is shown below: MESSAGE: [12:5] Internal error in (\"p\":num) => process aborted This is an unexpected condition and is likely due to a combination of circumstances involving both this product and the operating system. The troubleshooting file is available only in the directory where the cell manager is installed. you can access the troubleshooting file. This is a plain text file containing all of the error messages that can appear in Data Protector.com U1610S B.txt). host running BMA and host running BSM).txt on Unix <Data Protector _Home>\help\enu\Trouble. * Save session output to a file (e. host running VBDA. DESCRIPTION: An internal error occurred.P. please gather as much information as possible: * Write down product version and build number.log) in DATA PROTECTORHOME/log directories on all hosts involved in the situation when this error occurred (i.00 16-13 2003 Hewlett-Packard Development Company. * Make a note of the circumstances that cause this error. It can be found at the following locations: /opt/omni/gui/help/Trouble. session. * Collect all log files (*. The process was not able to recover and aborted ungracefully immediately after reporting this condition. L. Detailed or extended information about the error.e. Possible actions to take to solve or avoid the problem. com . This means that host A is unable to communicate with host B.hp. SLIDE: Network Connectivity Network Connectivity Data Protector relies heavily on networking.Module 16 Troubleshooting 16–4. Cell Console Network Backup Disk Agent Local Backup TCP/IP TCP/IP Cell Manager TCP/IP Disk Agent TCP/IP Scheduler Session Manager Session Manager Shared Memory Media Agent TCP/IP TCP/IP Media Agent Student Notes A very common problem in a Data Protector environment is host name resolution.P.00 16-14 2003 Hewlett-Packard Development Company. Connectivity and name resolution are potential problem areas. U1610S B. Resolving a host means that host A can interpret the FQDN and determine its IP address. The table below shows Data Protector components and how they should communicate among one another within the Data Protector environment. Communication among hosts means that host A in the table should resolve host B by its fully qualified domain name (FQDN). L. http://education. we have host A (nevizex1.Module 16 Troubleshooting Data Protector Components Name Resolution Host A Host B Disk Agent Client Host Media Agent Client Host Disk Agent Client Host Cell Manager Host Disk Agent Client Host MoM Server Host Media Agent Client Host Disk Agent Client Host Media Agent Client Host Cell Manager Host Media Agent Client Host MoM Server Host Cell Manager Host Media Agent Client Host Cell Manager Host Disk Agent Client Host Cell Manager Host MoM Server Host MoM Server Host Disk Agent Client Host MoM Server Host Media Agent Client Host MoM Server Host Cell Manager Host Example One For example.10: bytes=32 time=10ms TTL=255 Reply from 10. and host B is the cell manager with a media agent.10.domain.00 16-15 2003 Hewlett-Packard Development Company.10.com U1610S B.domain. enter: C:\users>ping nevizex2.com [10.P. .10: bytes=32 time<10ms TTL=255 Reply from 10.com If the response is valid. This response consists of host B’s IP address and confirmation on messages being sent to it.10.10.com) and host B (nevizex2. you will get the following text: Pinging nevizex2. Host A is a client with a disk agent. L.10.domain.10.domain.10] with 32 bytes of data: Reply from 10.domain. On Windows NT.10.10.10.10: bytes=32 time<10ms TTL=255 http://education.hp.com If host A properly communicates with host B.10: bytes=32 time<10ms TTL=255 Reply from 10. To test name resolution in this environment: From host A.10.com). you should get a response from host B. ping host B using the following command: ping nevizex2. and Unknown Host on UNIX systems.10: icmp_seq=0.10. icmp_seq=3. icmp_seq=4. Request timed out.com: 64 byte packets Name Resolution DNS Resolution Problems If you encounter resolution problems when using DNS on Windows NT Windows NT.com Pinging active. but is not available on the network.10.com PING active.10] with 32 bytes of data: Request timed out. if the result of the ping is similar to the example below.hp.10.domain.10: 10.10.10.10.10. time=1.00 16-16 2003 Hewlett-Packard Development Company.com If the response is valid. C:\users>ping active. check for and resolve possible network problems on the remote host. you will get the following text: 64 64 64 64 64 bytes bytes bytes bytes bytes from from from from from 10. Request timed out. the host is resolved correctly. the ping command will say only that the packet has been sent but not received. L. you will get a message saying Bad IP Address on Windows NT. Request timed out. This means that the host is turned off.10: 10.com [10.Module 16 Troubleshooting On UNIX. enter: /usr/sbin/ping nevizex2.com . If the response is not valid.10: 10.10.domain. Example Two on UNIX On UNIX (as in the NT example two). icmp_seq=1. or that the network link between your system and the remote system is down.10. http://education.10.P. time=0. time=0. C:\users> To resolve this problem. as shown below: /usr/sbin/ping active.--> Network-->Protocols--> TCP/IP Protocol--> Properties-->DNS) U1610S B.10: 10. time=0. enter the DNS Server in the Microsoft TCP/IP Properties window (Control Panel. you need to resolve this problem either on your DNS configuration or in your HOSTS file. Depending on how your environment is configured to do name resolution. Example Two on Windows NT On Windows NT. in an unstable state. ms ms ms ms Ms Press Control-C to stop the command.domain.10.10.domain.domain. time=1. icmp_seq=2. Module 16 Troubleshooting UNIX If you encounter resolution problems when using DNS on UNIX.com or nsquery hosts active.hp. On HP-UX. TIP You may also be able to configure the cell manager so that it may operate even in those cases when the DNS server is unavailable.domain> If you are using DNS. verify the lookup service that you are using by viewing the contents of the /etc/nsswitch. FQDN) /etc/opt/omni/users/UserList contains the authorized users/hosts http://education. nis. L. nis+) Test the lookup service using the nslookup or nsquery commands. . The following files will need to be modified to allow the cell to operate when the nameserver is unavailable. you may still be able to use /etc/hosts as a fallback service. then the response would be similar to the one below: *** No address (A) records available for active.conf. /etc/opt/omni/cell/cell_manager contains the cell manager host name (fully qualified domain name.domain.00 16-17 2003 Hewlett-Packard Development Company.com (nsquery is in /usr/contrib/bin) If the target system was not defined on the DNS.domain> or nsquery hosts <client_name.com U1610S B.com In this case. verify the configuration of the configured HOSTS file.conf file. this is configured with the /etc/nsswitch. you can see if the DNS can resolve the target system by entering the following command: nslookup active. (dns. which is located in the %NTHOME%\System32\drivers\etc directory. and the nameserver is not reachable.domain. for example: nslookup <client_name. HOST File Resolution Problems If you encounter resolution problems when using the HOSTS file on Windows NT. files.P. see your network administrator.domain. P. First. http://education. They are used for communication of Data Protector components and unattended systems tasks. L.00 16-18 2003 Hewlett-Packard Development Company. SLIDE: Services Services The Data Protector services must be running: # ps -ef | grep omni root 1519 1 root 1532 1 root 1520 1 0 08:15:36 ? 0 08:15:40 ? 0 08:15:37 ? 0:01 /opt/omni/lbin/mmd 0:00 /opt/omni/lbin/crs 2:02 /opt/omni/lbin/rds -d UNIX Windows Student Notes Services are critical components on Data Protector systems. it can occur that Data Protector services are stopped or are not installed on the Data Protector client you are targeting for backup. see “ Networking and Communication Problems. make sure that name resolution is not a problem. use the following command: telnet <full_hostname> 5555 U1610S B.Module 16 Troubleshooting 16–5.hp.” To test if the Data Protector inet service is running on a remote system. by using the telnet command and the Data Protector inet service port number.com . Data Protector inet Service Due to maintenance and other system tasks. For more details on service problems. by default.hp.Module 16 Troubleshooting If you get a response similar to the one below in the telnet window. and get the status of Data Protector daemons. Stopping Daemons To stop the Data Protector daemons. enter the following command in the /opt/omni/sbin directory: omnisv -stop http://education. If you get a response.00: INET. the Data Protector inet service is installed and running/responding on the remote system: HP OpenView Storage Data Protector A. Unix security blocking access to the service port. To manually stop. connection refused. start. you know there are some problems with the current installation. log on to the cell manager system as superuser.05. internal build 190.00 16-19 2003 Hewlett-Packard Development Company. these daemons are started automatically during the system’s startup.com U1610S B. Data Protector is not installed on the remote system. built on Tue July 16 16:37:32 2002 Connection closed by foreign host. Problems Starting Data Protector Daemons on HP-UX The following daemons run on the Data Protector UNIX Cell Manager system: Data Protector CRS daemon (/opt/omni/lbin/crs) Data Protector Database daemon (/opt/omni/lbin/rds) Data Protector Media Management daemon (/opt/omni/lbin/mmd) The Data Protector Inet program (/opt/omni/lbin/inet) is started by the system inet daemon when an application tries to connect to the Data Protector port. Possible problems include: • • • Data Protector inet service is not running on the remote system.P. L. is port 5555. Normally. see “ Problems Starting Data Protector Services” below. which. . Verify that the <OMNICONFIG>/options/global file exists. Check that you have all Data Protector database files in the <OMNIVAR>/db40 directory. See /var//opt/omni/log//RDS.log for details. L. enter the following command in the /opt/omni/sbin directory on Unix.com . <OMNIHOME>\bin on Windows: omnisv -start Checking the Status of the Daemons To check the running status of Data Protector daemons.Module 16 Troubleshooting Starting Daemons To start the Data Protector daemons. omnisv -start Could not start the Cell Manager daemon. /opt/omni/sbin/omnisv start Could not start Raima Velocis server daemon.hp. http://education.P. See /var/opt/omni/tmp/omni_start. One possible reason for this message is that the volume where the Data Protector internal database resides is not mounted. • The Data Protector cell manager daemon cannot start. Compare the list of files in the <OMNIHOME>/newconfig/var/opt/omni/db40 on Unix and <OMNIHOME/newconfig/db40 on Windows to the list of files in the <OMNIVAR>/db40 directory. You would most probably get this message if the global options file were missing.00 16-20 2003 Hewlett-Packard Development Company.log for details. <OMNIHOME>\bin on Windows: omnisv -status Possible reasons why a Data Protector daemon may fail to start include: • The Raima Velocis server daemon could not be started. U1610S B. enter the following command in the /opt/omni/sbin directory on Unix. This can happen if someone has accidentally removed the directory or some of the database files.com U1610S B. or some of the files are missing.. 2. In this case. you do not have permission to start and stop services. follow the steps in “ Recovering the Complete Database” in the Administrators Guide. For recovery.P.." If you get this error message when starting services.. If the server cannot be started. see: "Raima Velocis server daemon could not be started" above... continue with the next step. stop...the daemon is probably not running: 1. it is likely either that the <OMNIVAR>/db40 directory does not exist. then start/stop or modify the services. If the service still fails to start. Ask your system administrator to grant you the permission to start. Check that the database server is really not running using the following command: omnisv -status The output should then be similar to the following: . Problems Starting Data Protector Services on NT/2000 Data Protector runs services on both client and server systems. . If the database server is running. If the database server is not running. log off and log on again for the changes to take effect..Module 16 Troubleshooting • The Raima Velocis server daemon is apparently not running. You can also log off the system and log on as system administrator.00 16-21 2003 Hewlett-Packard Development Company. try one of the other options in this list. The following services run on Data Protector client systems: • Data Protector Inet The following services run on Data Protector server systems: • • • Data Protector Inet Data Protector CRS Data Protector Database There are many possible reasons why Data Protector services may fail to start: • "You do not have permissions to start the services. start it with the following command: omnisv -start Otherwise.. L. http://education.. and modify services on the system that you are administering.hp.. 3. Raima Velocis server up and running [nnn].. If any of Data Protector commands terminates with following message: [12:1166] Velocis daemon error . U1610S B. either on the client system or on the server system. This means that you cannot predict which ports are used. However. Port Usage In general.Module 16 Troubleshooting • The service user does not have permissions to start the service If you get the following error message “Service Start-up failed due to logon failure. If the service still fails to start. The location of the service is registered in the ImagePath key. The Services User properties have been changed. uninstall the current installation. try one of the other options in this list. uses a dynamic port assignment.P. L. the communication between the graphical user interface and the Cell Manager can be restricted with respect to the ports being used. Modify service parameters in the Service dialog box. If this is a server system. The system can not find the file specified. click Services.exe file invokes a Dr.hp. Watson diagnosis.” it means that the user who is configured to run the services does not have permission to start/stop services. If this does not solve the problem. and double-click the problematic service.ctx file on the \Data Protector\tmp directory to resolve the problems. This will give you a clean installation and all the binaries of the services and other binaries will be in place. If the executable does not exist on this location. stop. copy the Data Protector\db40 and Data Protector\config directories to a safe location before uninstalling Data Protector. Also. then reinstall the software. http://education. some database log files can be corrupted. A specified service has not been found. the communication between Data Protector components. and modify services on the system you are administering. try one of the other options in this list. contact your system administrator to set up the account with appropriate permissions on the system. Delete the mmd. In the Control Panel.00 16-22 2003 Hewlett-Packard Development Company. which are distributed over several systems on a LAN. • • • Database log files are corrupted and the MMD crashes when starting the CRS service. This points to a corruption in the database log files.com . Then restart the services. and the Data Protector CRS service can fail to start. Because of improper database shutdowns.” First. Ask your system administrator to grant this user permission to start. If the service still fails to start. try one of the other options in this list. If the service still fails to start. the following error message is given: “Could not start the <Service Name> on system. the MBD. si "Wolf_win95" Time: 21.98 11:02:30 Cannot get the list of filesystems on host "wolf.com U1610S B. http://education. [Critical] From: BSM@lacoste. L. Use the <Data Protector_home>\bin\omnii95 command. It is. No other system should be using this port if the Data Protector graphical user interface must use it. run the omnisv -stop command to stop the Data Protector services. and specify the port number to use. port 5555. as well as the INET port.Module 16 Troubleshooting The result is that two port numbers will be used as follows: INET port This is the port used to initiate any communication between Data Protector components. which can be modified to a different number. Change the CrsPort entry in the GLOBAL file. or if you see an error message similar to the one below in the Data Protector message log window. use the <Data Protector_home>\bin\omnii95 -kill command. CRS port NOTE 1.hermes. Stop the CRS service with the following procedure: As user root. Problems Connecting to Windows 95/98 Client Systems If you encounter problems connecting to a Data Protector Windows 95/98 client system using the telnet full_hostname 5555 command.00 16-23 2003 Hewlett-Packard Development Company. See the HP OpenView Storage Data Protector Installation and Licensing Guide for information on how to modify this number.hp.09. Use the following procedure: Run the omnisv -start command to start the Data Protector services. make sure that the Data Protector Inet service is running on the Windows 95/98 client system. . To stop Data Protector Inet service on a Windows 95/98 Client system.hermes.” [Warning] From: BSM@lacoste. Follow the procedure below to configure the CRS port. The two ports cannot be mapped to the same number.hermes "Wolf_win95" Time: 21.P. by default. 2. 3.hermes. This port is the only port used by the GUI to communicate to the cell manager.09. Restart the CRS service.” Backup of this host will be retried at end of session.98 11:02:29 [61:12500] Cannot connect to inet for getting filesystem list on host"wolf. or simply your user is not authorized to access the Cell Manager. To ensure that you are able to start the GUI from any system (for testing) add the following entry to the <OMNICONFIG>\users\UserList file on the Call Manager: * * * * Admin The above entry is considered to be a security risk. To make the GUI compatible on both systems. To remedy this problem. Access denied problems are the result of user configuration issues. but you will notice new processes named “windu_registryd43” and “windu_clientd43” running U1610S B. and hostname resolution is falling back to local files. (inet is not responding).com . review the steps in the HP OpenView Storage Data Protector Installation and Licensing Guide.. the developers have simulated a windows registry on HP-UX. The Cell Manager host file is not reachable or is not up and running or has no Data Protector software installed and configured on it. If you are able to connect from the remote GUI. as well as the short name for the hostname. but have no access. If there is a bad installation. • • • • Follow the instructions above to resolve any communication problems between the system with the user interface and the Data Protector cell manager.P.00 16-24 2003 Hewlett-Packard Development Company. check that all services are running properly on the cell manager. you may want to add an additional user to the UserList configuration file. services not being installed. and thus should not be left in place after testing is completed. your DNS server may be down.hp. If you are able to run the GUI. • • Access Denied message when starting the GUI on a local or remote system: This event may be similar to the above DNS problem. or a network communication related problem. This fallback mechanism is a common problem if the local host lookup file does not contain fully qualified domain names. Be sure to have an entry for the cell manager that uses the fully qualified name. Registry Problems on HP-UX The Data Protector GUI available on HP-UX was ported from the 3. This should be considered a short-term fix to be able to access the GUI.Module 16 Troubleshooting 16–6. The following message is the most common when one of these is the source of the problem: Cannot access the Cell Manager system. because some components failed to install or were improperly installed. For the most part this is invisible to the users. http://education. check the installation. If communication between the systems is not the problem.5 GUI that previously ran only on Windows systems. L. TEXT PAGE: User Interface Startup Problems Data Protector user interface startup problems usually are the result of services not running. using the telnet command. then go to the users context and refine the access limits for the cell. If the installation is okay. windu. Settings that are modified in the GUI are saved in the home directory in a file named “. .<hostname>. rds) are stopped while the GUI is running.hp. L. but the messages will look very ominous. http://education. If the server processes (crs.” This file is not modifiable. but may be removed if the GUI is not running to reset to the Data Protector installation defaults. This should not cause any lasting problems. and the GUI may be restarted after all the servers are running again. mmd. The messages may be safely disregarded.com U1610S B.Module 16 Troubleshooting in the background.P.00 16-25 2003 Hewlett-Packard Development Company. and then the GUI is stopped. you will see “Wind/U Error (251). these errors occurring as a result of the loss of communication between the windu_registryd and the crs processes. use the ioscan –fnCtape command to verify connectivity and device files. Periodically new devices are added to this list by HP. the problem may be with Data Protector. L. Download the most recent scsitab from HP to add support for the newest devices.com . On Windows use the Data Protector command: devbra – devices. Can the system see the device? ioscan. SLIDE: Backup Devices Backup Devices Can native backup tools access the device? tar.00 16-26 2003 Hewlett-Packard Development Company. If they do not work. Supported Devices (SCSITAB) Data protector provides support for devices of many types from HP and other vendors. try tar. Do not modify this file manually.Module 16 Troubleshooting 16–7. fbackup.hp. etc. and further investigation is required. the problem is not with Data Protector. U1610S B. On the Cell Manager is a file named “scsitab” which provides a list of all supported models. cpio.P. The best practice is to eliminate Data Protector as the source by accessing the device with another native backup utility. devbra (NT) Is the library device configured correctly? uma Is there a problem with media? omnimver Student Notes General Troubleshooting When you have a device problem. you may jump to the conclusion that it is a Data Protector configuration problem. cpio. if they do. on Windows try NTbackup. Can the system see the device? On HP-UX. fbackup. However. For example on HP-UX. and so on. http://education. UMA is packaged and installed as part of OB2's media agent fileset.Module 16 Troubleshooting Media Problems Is the media bad. uma is located in <OMNIHOME>/bin/uma. but it will probably not be able to locate and use Data Protector's NLS message catalog. . this is specified as –ioctl <device name>. and the Data Protector NLS message catalog is in /opt/omni/lib/nls/C/omni. uma is located in /opt/omni/lbin/uma. verify that it is configured correctly: Select the drive. Testing Library Device Robotics with UMA (Utility Media Agent) The uma program is a standalone utility program provided on both HP-UX and Windows NT. also those that are not supported by Data Protector. Library Devices The most common error message for an improper configuration is. Library Device Drive Index Problems When using libraries with multiple drives. which can be used both interactively and in batch mode. Symptoms of drive index problems are seen when using multiple drives within the library at the same time. and click Scan from the Actions menu. Verify that they match the drive index number assigned to them in Data Protector. Messages do not point exactly to this problem but to some kind of problem with loading and/or unloading the medium from or to the drive." Configure your drives as follows: 1. 3. On Windows systems. 4.cat. The only option that needs to be specified is the pathname of the device file that controls the robotics of the target autochanger. Uma can be started both interactively or in batch mode. omni. If you have received uma as a standalone program. After configuring each drive. http://education. Configure your drives one at a time. On HP-UX systems.com U1610S B. It implements a shell-like user command interface.” This implies a problem with the robotic control device file. Check the drive indexes as they appear on the library’s control panel. a very common problem is mismatched drive indexes in the library drive configuration. For example.P. “Cannot access exchanger control device.cat. or if you run it on a system on which Data Protector has not been installed. uma will be fully functional and behave as documented. does the operation work with other media? Use the Data Protector verify function to verify existing backups.exe. "Cannot load medium.00 16-27 2003 Hewlett-Packard Development Company. 2.hp. Refer to the Appendix for detailed information on how to properly configure a library device. L. It controls the robotics of most SCSI-II compliant autochangers. The drives must be known to uma in order for the offl command to work. L.. which correspond to the autochanger's drives." or the more convenient.. for a multi-drive autochanger. Syntax uma version uma -ioctl deviceFile –[barcode] -tty Commands: help inq res rel init addr offl drive sense pos slot move from to [0|1] stat Options -version -ioctl deviceFile Displays the version of the uma command. "128. uma allows you to specify symbolic instead of physical element addresses (slot IDs). in ascending order.Module 16 Troubleshooting For your convenience. Ideally. symbolic "D1. U1610S B. you can specify the physical address. Display the barcode labels if used. deviceFileN Specifies the device file of one or more autochanger drives. When you need to refer to the 1st drive of the autochanger. Specifies the pathname of the device file that controls the robotics of the target autochanger.P." The output of the addr command reflects the duality of this addressing convention. you specify a list of device files.com . http://education.hp.00 16-28 2003 Hewlett-Packard Development Company. Directs the UMA to read commands from the “stdin” -barcode -tty Examples: echo stat | C:\Program Files\Omniback\bin\uma –ioctl <dev> –tty print stat | /opt/omni/lbin/uma –ioctl <dev> -tty -device deviceFile1 . and stat operations (see below). S=Storage): Transport: Im/Export: 1 . . 303 http://education.Module 16 Troubleshooting Commands help inq Displays the usage synopsis for the uma command The inq command performs an SCSI-II inquiry operation on the UNIX device file specified with the -ioctl option. product ID. Query and print the autochanger's element assignment page. 67 (T1 .. X=Im/Export. The effects will be unpredictable.. 1 64 .P. This command should not be used if another process is accessing the autochanger at the same time. D4) (S1 . S48) Data Drive(s): 128 . It requires no additional arguments. robotic arm. vendor ID.. import/export slot) has a unique integer number (slotID). repository slot. The init command performs an SCSI-II "initialize element status" operation.. and firmware revision number. 131 Repository: 256 ... referring to an ACL 4/52 DLT autochanger: /dev/spt/sctl0> addr Element Addresses: (T=Transport.hp. It requires no additional arguments. which can be used to address this specific item. res rel init addr The following output is obtained by executing the addr command on the UNIX device file. X4) (D1 . This command puts an exclusive write lock on the device file. Each addressable item inside the autochanger mechanism (drive.com U1610S B.. D=Drive.00 16-29 2003 Hewlett-Packard Development Company. which (if applied to an autochanger robotic device) forces the autochanger to reset its internal state and perform an inventory of its repository.. As the element assignment differs between different autochangers. pos. Reserve control device file for exclusive access. which prevents other programs from accessing it until it is released (or the current uma process terminates). T1) (X1 . It returns the device's type. L. Release control device file. the software that controls the movement of media inside the autochanger must find out and use these numbers to perform move. Reverses the effect caused by a res command. data drive. the barcode for each medium is printed. L. http://education. the source and destination slot IDs (address numbers.hp. but can be used by developers and support engineers to diagnose potential device problems. No additional arguments are required. U1610S B.e. If a medium is loaded in the specified drive.. if the tape has not been dismounted and ejected by the drive. This command is generally not required. NOTE stat This command queries the device for information about the state of each of its addressable elements. By default. The output of this command is a table of physical and symbolic element IDs and their states. The actual meaning of this operation may differ among different autochanger models. it will eject the medium.P. The mandatory argument is a symbolic drive ID (i. sense pos move NOTE Flipping is supported only for double-sided optical media. Uma recognizes one specific environment variable.Module 16 Troubleshooting The numbers returned by the addr command are the physical element addresses of different elements within the autochanger ( i. By default (if no flipping argument is specified). if barcode support is available and enabled. which can be used to enable barcode support for autochangers that are equipped with barcode reading hardware. For tapes. offl This command can be used only if at least one drive was specified at uma -dev option. but is provided for testing purposes and convenience. This command has two mandatory arguments. or repository element. Additionally. Both physical and symbolic slot addressing may be used. Read the device's sense data and dump them in hex-dump format. This operation is meaningful only if the specified slot ID refers to an import/export. Most autochangers do not allow you to move a tape from a drive to a repository location. as reported by the addr command described above) and an optional numeric Boolean argument that can be used to instruct the robotics to flip the medium before inserting it into the destination slot. the effect of a flip command is not defined.com . element address "65" corresponds to the location of the 2nd data drive. Use the offl command on the drive device file to put the drive off-line before executing the move command. indicating which elements are free (Empty) and occupied (Full).. Move a medium from a source slot into a destination slot.00 16-30 2003 Hewlett-Packard Development Company. The pos command positions the autochanger transport mechanism in front of the specified slot ID. flipping is disabled. etc. the same as if an mt offl command was specified. This command is not directly useful to the user.e. element address "256" corresponds to the 1st repository slot. uma OB2BARCODE=1 into uma. D3 for the 3rd drive == the 3rd device file specified with the -dev option). 20" " 6210030" /dev/spt/sctl0> exit To let uma execute a batch script of its own commands.Module 16 Troubleshooting The stat command can be used to query the status of a specific slot (i.. If no additional arguments are specified.e.com U1610S B.).hp. stat S will query all repository slots. stat 290 or stat S35) or a related group of slots (i. ..00 16-31 2003 Hewlett-Packard Development Company. /dev/spt/sctl0> inq SCSI Inquiry: Type: Vendor ID: Product ID: F/W Revision: 8 "ATL "ACL4/52 "1.00 *** Copyright (C) 1996 Hewlett-Packard Company *** License is restricted for use with licensed *** HP OpenView Data Protector products.P. separated with new lines: cat >/tmp/cmdFile inq addr stat <ctrl-D> uma -ioctl /dev/spt/sctl0 –tty </tmp/cmdFile >/tmp/outFile http://education. etc.02. The only option that must be specified is the pathname of the device file that controls the robotics of the target autochanger: uma -ioctl /dev/spt/sctl0 *** PROGRAM: UMA VERSION: HP OpenView Data Protector A.e. Examples Uma can be started both interactively or in batch mode. L. stat D will query all drives. the stat command will query and print the status information for all slot IDs it can address. simply redirect its stdin to a file containing a list of uma commands. length of cables.) are dealt with in detail in Appendix A of the HP OpenView Storage Data Protector Licensing and Installation Guide. they are in use by another device driver. run the <OMNIHOME>\bin\devbra -dev command from the Data Protector command line interface on the system on which the devices are located. Typically. L. or when the length of the transferred data (defined by block size) is larger than the length supported by the SCSI adapter. Media used with DDS drives must comply with the media recognition system.P.” check to see if you are using a medium that is not compatible with the media recognition system. and so on. Using Unsupported SCSI Adapters on NT Using unsupported SCSI adapters with Data Protector devices can cause a Blue Screen of Death (BSOD). They are most commonly resolved by checking the SCSI communication between the system and the device (SCSI cables. claimed device. To list all physical devices that are configured on the system. Remove configured tape devices.hp. If any of the SCSI addresses have a CLAIMED status. then Tape Devices to open the Tape Devices dialog box. and so on). U1610S B. Reboot the system.com . the problems occur when the SCSI device is accessed by more than one media agent at the same time. . Other common problems are hardware-related.00 16-32 2003 Hewlett-Packard Development Company. You can change the block size in the Advanced Backup Options. click on Control Panel. Device Open Problems If you receive an error from a DDS device similar to the following: “ Cannot open device (not owner). http://education. It is suggested that you use Adaptec SCSI adapters.Module 16 Troubleshooting On Windows NT/2000 Systems Problems involving device SCSI addresses (SCSI address not found. adapters. To resolve the problem. Full Backups Are Performed Instead of Incrementals There are several reasons why full backups instead of incrementals are performed: • No previous FULL backup exists.00 16-33 2003 Hewlett-Packard Development Company.P. the problem usually involves licensing or permissions. If a protected full backup is not available for this comparison. Data Protector uses a full backup as reference point to determine what files have changed (and thus needs to be included in the incremental backup). Data Protector requires a full backup.Module 16 Troubleshooting 16–8. Before performing an incremental backup of an object. http://education. . a full backup will be performed.com U1610S B. This section also describes situations when backup and restore sessions are not started as they were configured. L. SLIDE: Backup and Restore Backup and Restore Full instead of Incremental Unexpected mount requests Backups not working: Scheduled/Interactive Restore not possible • No previous full backup? • Object description has changed? • Backup owner is different? • • • • • Non appendable media? Media from wrong pool? Strict allocation policy? Preallocation list sequence? Library device not scanned? • Service not in Admin group? • Licenses available? • omnitrig entry in crontab? • Data Protector permissions? • Backup protection? • Data Protector permissions? Student Notes Starting Backup and Restore Sessions When Data Protector fails to start a backup or restore session.hp. . the person starting the backup is the owner of the data. On Standalone Devices If a mount request is issued for a standalone device and media is available in the device. To resolve this issue. the incremental backup will become a full backup. “UpgradeIncrToFull”. because the data for USER_1 is private. This will make this user owner of all backups. In this case. • The media in the device is not formatted. If you would like Data Protector to automatically format unformatted media. although there is still available space on the media.(this may be controlled by a global option. disk. do not physically writeprotect any media. regardless of who actually starts the backup session. The host (system). the exact media specified in the Prealoc list must be available in the device when a backup is started. set the media pool policy to Loose for media available in the device. Data Protector issues a mount request. The backup owner should be a user from the Admin class. Data Protector considers this a new object. If any one of these three change.00 16-34 2003 Hewlett-Packard Development Company.Module 16 Troubleshooting • The description has changed. but is different than the one in the Prealoc List of the Backup Specification. Data Protector performs a full backup instead of an Incremental. you can configure a session owner for the backup in the Advanced Backup Specification options. For example. change the media pool policy to Appendable to append backups until the media is FULL. if USER_1 performs a full backup. and the media pool to be used has a strict policy. If the exact media is not available. U1610S B. and USER_2 tries to start an incremental backup. the media will not be used because of the non-appendable policy of the pool. and the Pool specified has a strict policy. a mount request is issued.P. In this case. default value is 1 which means on) The backup owner is different. • Unexpected Mount Requests In order for the Data Protector media management to work properly. and cannot be used as a base for USER_2’s incremental backup. To append backups to media. http://education. If you are using a Prealoc list of media in combination with the strict media policy. If your pool is defined to use a strict media allocation policy.com . L. the following is possible: • The media in the device is in a media pool that has a non. and description define an object. even if the host and disk are the same.appendable policy.hp. If your backups are configured to run as Private. • The media in the device is formatted. If no formatted media is available. media that is not formatted will not be used for backup. the exact media specified in the Prealloc list must be available in the device when backup is started. the following is possible: • The media in the library is not formatted and the media pool that the device is in has a strict policy. but is different than the one in the Prealloc list of the backup specification. In the event this is modified and permissions for this account are removed. perform the following steps in the Data Protector Backup Manager: From the GUI: 1. they are started by the Data Protector system account. If the exact media is not available. media that is not formatted will not be used for backup. • The Data Protector service account is not in the Data Protector Admin Group. to add a new user. • The media in the library is formatted. See online Help for information on the dialog box. switch to the Users context. add the Data Protector account to the Admin group on the cell manager. select Admin. If your pool is defined to use a strict media allocation policy. In the Scoping Pane. If you are using a Prealloc list of media in combination with the strict media policy. a mount request is issued. To use any available media in the device without the Prealoc list in the Backup Specification. change the media pool allocation policy to Loose. Click Edit. (if it is available in the Library). set the media pool policy to Loose. L.com U1610S B. To resolve this issue. Add. This account is added to the Data Protector Admin group on the cell manager at the time of installation. or if the Service account changes. the scheduled sessions no longer run. . 2. http://education. To do this. In the Data Protector Manager. If no formatted media is available in the library. If you want Data Protector to automatically format unformatted media.hp.P.00 16-35 2003 Hewlett-Packard Development Company. Data Protector will issue a mount request. To use any available media in the device without the Prealloc list in the backup specification.Module 16 Troubleshooting To use another media (if it is available in the device). On Library Devices If a mount request is issued for a library device. This can be modified in the media pool properties. Users. remove the Prealloc list in the Properties of the Backup Specification Data Protector Fails to Start a Scheduled Session When Data Protector runs scheduled sessions. and media is available in the library. and the pool specified has a strict policy. in combination with the Prealoc list. change the media pool allocation policy to Loose. To use another media (if available in the device) in combination with the Prealloc list. 3. remove the Prealoc list in the Properties of the Backup Specification. in the Data Protector Manager. the backup session cannot be started.30.P. Data Protector checks if licenses are available. execute the omnicc –query command. See the HP OpenView Data Protector Licensing and Installation Guide for licensing details.” To get license information.. enter the following command: crontab -l If the following line does not appear.45 * * * * /opt/omni/sbin/omnitrig Data Protector Fails to Start an Interactive Session There are two common reasons for Data Protector to fail starting an interactive backup: • Permissions are insufficient. To resolve this issue. • Data Protector Backup Sessions are not started at all (UNIX-specific!). Data Protector checks if licenses are available.” On Windows. To check and change user rights of a particular user. If this user does not have sufficient permissions. check the status of the failed session for the message: “No licenses available. http://education. Every time a backup session is started. To determine if this is the cause.hp. to get information about available licenses.sh stop and the omnisv.. If they are not.00 16-36 2003 Hewlett-Packard Development Company. • Licenses are not available. Every time a backup session is started. U1610S B.sh start commands in the /opt/omni/sbin directory. click Help-> About.Module 16 Troubleshooting • Licenses are not available. you need to request new licenses and apply them to the Data Protector system. stop and start the Data Protector daemons by entering the omnisv.com . omnitrig entry was automatically added by HP Data Protector 0. permissions are required to start the backup session. You can determine this is the reason by checking the status of the failed session. If they are not.. see “ Configuring Users and User Groups. Check that the omnitrig program is included in the crontab file.15. These permissions are checked for the user who is currently running Data Protector. L. To verify this.. The message will read “No licenses available. Every time a backup is started. the session cannot be started. the backup session cannot be started.” in the Administrators Guide. Set the protection as required. 2. because its DNS is improperly configured. only as system_name. L. Backup Protection Expiration To restore an incremental backup object.Module 16 Troubleshooting To resolve this issue. The solution is to configure the protection for your full backups so that they are protected for longer than your incremental backups.com U1610S B. Restores for an incremental backup based on the corresponding full backup that is expired are not possible. Consequently.00 16-37 2003 Hewlett-Packard Development Company. If you try to restore a database." the problem is as follows: When backing up the database on a system. and it fails with a message like.domain.com.hp. This situation can also be the other way around. but it cannot. you need both the full backup and the incremental backup object versions. See the HP OpenView Data Protector Licensing and Installation Guide for licensing details.domain. It cannot expand the system to the long name. 3. set the protection as follows: 1. you will need to request new licenses and apply them to the Data Protector system. backup schedules are configured in such a way that incremental backups are protected for the same duration as the corresponding full backup. Troubleshooting Application Database Restores A poorly configured DNS environment can cause many problems with database applications. 5. In many cases. . switch to the Backup context. the restore session manager wants to restore to the system_name. Windows/Unix NT Solution In Windows NT. The time difference between the protection for the FULL backup and the incremental backup should be the amount of time between the FULL backup and the last incremental backup before the next full backup. When a restore is performed. This will keep your FULL backup protected and available until your last incremental backup expires. In the Data Protector Manager. For example. the agent that starts on the system logs the system’s name to the database as system. then Options. 4.com. where DNS is configured on the cell manager and not on the application client. your data will actually be protected only until the full backup expires. Click the Schedule tab. you should set the protection of the FULL backup to six days more than the incremental backups. Right-click this Backup Specification.domain. http://education. if you run incremental backups Monday through Friday and FULL backups on Saturday. because it does not know this system as system_name.P. Select the Backup Specification used to back up the data you want protected.com. "Cannot connect to target database" or "Cannot create restore set. then choose Properties. Module 16 Troubleshooting Problems When Installing Data Protector NT Clients When using Data Protector’s remote installation to UPDATE Windows NT clients. no more help topics can be seen. This will reinstall the original version of the hhctrl. err=[1326] Logon failure: unknown user name or bad password. Solution Rename or delete the file %SystemRoot%\system32\hhctrl. The application reports that the Data Protector Help system is not installed. the help window is normally displayed.hp. and will install it. L.ocx and restart Data Protector Manager or Data Protector MoM Manager. The Data Protector Inet service on the remote computer is running under a user account that does not have access to the Data Protector share on the installation server computer. You should change the username for the Data Protector Inet service with access to the Data Protector share.00 16-38 2003 Hewlett-Packard Development Company.P. Neither Help Navigator nor dialog help works. http://education.ocx used by Data Protector is replaced with a different version during installation of another software application. U1610S B. Problem Using Data Protector Windows Online Help When the user selects Help or Help Topics. which is most probably a local user. Reason This problem can occur if the ActiveX control hhctrl.ocx control.com . you get the following error: Error starting setup process. After that. mmd.00 16-39 2003 Hewlett-Packard Development Company.com U1610S B. SLIDE: omnihealthcheck omnihealthcheck UX: /opt/omni/sbin Windows: <Data Protector_home>\bin> • Execute commands listed in HealthCheckConfig file. omnitrig and omniinet) are active (omnisv –status) list of Data Protector media pools (omnimm -list_pools) check Data Protector Cell manager name (omnidbutil -show_cell_name) http://education.P. The omnihealthcheck command checks: • • • whether the Data Protector services (rds. Student Notes The omnihealthcheck command reads a configuration file and automatically and periodically checks the status of Data Protector services. crs. • Check list of Data Protector media pools. omnitrig and omniinet) are active. . • Check if the Data Protector services (rds.hp.Module 16 Troubleshooting 16–9. Each line in the file is treated as a command line and is executed. • Check Data Protector Cell manager name. Commands must be listed with full pathnames except if they are Data Protector commands located in bin (Windows) or sbin (UNIX) directories. mmd. crs. L. 00 16-40 2003 Hewlett-Packard Development Company.P. omnihealthcheck can be used for monitoring reliability and conditions of Data Protector cell. L. Student Notes The omnihealthcheck config file may be modified to include additional checks to the defaults provided. The default schedule value can be changed by changing the DailyMaintenanceTime option in the Data Protector global options file. This is the text file describing which commands must run when omnihealthcheck command is used. commands are executed under account.hp.. with may be different than the administrator. On Windows. U1610S B.Module 16 Troubleshooting 16–10.com . If you want to use other non-Data Protector commands. http://education. Omnihealthcheck is by default scheduled to run daily at midnight as a part of the Data Protector maintenance mechanism. then full path must be used to run a command. which NT Data Protector CRS service run. Commands used in HealthCheckConfig file run under administrator / root account during omnihealthcheck command execution. operating system commands may be used. SLIDE: Health Check Config file HealthCheckConfig File UX: /etc/opt/omni/HealthCheckConfig Windows: <Data Protector_home>/Config/HealthCheckConfig Example of HealthCheckConfig file: OPTIONS: Timeout=200 COMMANDS: # Checks DP Services omnisv -status # Checks Pools and Media omnimm -list_pools # Checks DP Internal Database omnidbutil -show_cell_name For checking other DP functionality. additional commands can be added. . If this time is exceeded then return error code for this command and execute next command. Also. L.com U1610S B. Timeout variable is defined in seconds (by default this is 200 seconds).hp. Timeout variable in healthcheckconfig file determine time for execution of each command in healthcheckconfig file. there is almost no impact on running backup / restore sessions.00 16-41 2003 Hewlett-Packard Development Company. http://education.Module 16 Troubleshooting Running omnihealthcheck with default HealthCheckConfig does not have any impact on the performance of Cell manager.P. Exit code: 0 . L. SLIDE: omnihealthcheck. If all commands are executed without any error then the Healthcheck exit code is 0 (no errors). When the omnihealthcheck command is first started.log is appended during omnihealthcheck command.P. http://education.00 16-42 2003 Hewlett-Packard Development Company.hp.Module 16 Troubleshooting 16–11. ======> Running: omnisv -status ProcName Status [PID] =============================== rds : Active [281] crs : Active [188] mmd : Active [176] omnitrig: Active omniinet: Active [301] =============================== Status: All Data Protector relevant processes/services up and running.log Windows: <Data Protector_Home>/Log/HealthCheck. together with information about each separated command used in omnihealthcheck configuration file.log file is created. EXIT CODES: 0 All commands listed were executed and their exit codes 1 At least one command could not be executed or completed with non zero exit code 2 Config file could not be read 3 Command timed out (depending on Timeout variable) U1610S B. .log omnihealthcheck Log UX: /var/opt/omni/log/HealthCheck. the HealthCheck.log Example: Health check started: 17-May-01 11:56:08. . Student Notes This text file HealthCheck.com . P.Module 16 Troubleshooting 16–12. SLIDE: omnitrig –run_checks omnitrig -run_checks UX: /opt/omni/sbin Windows: <Data Protector_home>\bin> Event Configured ================================ UserCheckFailed DbSpaceLow NotEnoughFreeMedia UnexpectedEvents HealthCheckFailed DbPurgeNeeded LicenseWillExpire Yes/1 Yes/1 Yes/1 Yes/1 Yes/1 Yes/1 Student Notes The omnitrig -run_checks command may be used to start checks for the following Data Protector notifications: • • • • • • • Database Space Low Not Enough Free Media Health Check Failed User Check Failed Unexpected Events License Will Expire Database Purge Needed Any triggered notification is shown in the Data Protector Event log. By default omnitrig runs once per day at midnight (can be changed in global options file. L.hp.com U1610S B. variable: DailyMaintenanceTime) http://education. .00 16-43 2003 Hewlett-Packard Development Company. use at(1) to start commands which normally keep the pipe open. It is up to the designer of the script to allow for capturing of data sent to stdout. An issue with the pipe monitoring is. The best way to prevent this is before the fork. See the global file for the ScriptOutputTimeout variable for session exec scripts and SmDaIdleTimeout. the process does a set process group and so becomes a process leader (detaches). 2.and Post. Data Protector monitors the output of a pipe attached to the stdout of the script. close their file descriptor. After the script is started. stdout of ALL processes started by the script are also attached to this pipe unless otherwise explicitly closed by the process or script. Redirect the output and stdout to a file when starting a command. See below for a sample program. which normally keeps the pipe open. which can affect object exec scripts.Exec Commands “ for more details on these variables. Data Protector sets the SESSIONKEY. This is important because Data Protector monitors the data coming from the pipe.and Post.hp.P. You will notice the script completes but Data Protector will not complete until the sleep is finished. See the man page for more details on these system and function calls. See the Administrator's Guide under the heading “Backing up Data .com .exec Scripts First a little understanding of how Data Protector starts an exec script and the limitations.00 16-44 2003 Hewlett-Packard Development Company. TEXT PAGE: Debugging UNIX Pre. which shows how Data Protector starts exec scripts. The reason is that there are still file descriptors attached to the pipe.” When a session exec script is started it will show up in the ps output as "sh script_name". stdout is not captured or reported. SMEXIT and OWNER environment variables for a session exec script and sets PREVIEW and BDACC for an object exec script. This is the case of processes launched in the background.Module 16 Troubleshooting 16–13. U1610S B. The owner specified in the backup specification will own the process for the script. feof() will not return non-zero until these processes complete or close the file descriptor. You can then cat this file in the end of the script to report anything that has been output to the file. To demonstrate this launch a "sleep 300 &" in an exec script. Other ways to work around this are: 1. If the script forks new processes that have stdout attached to the pipe and they are still running when the script is completed. In the script.Pre. it will show up in the ps output as "sh -c script_name. The exec scripts are stated using popen() for object exec scripts and fork() and execvp() for session exec scripts. The function feof() monitors the pipe looking for non-zero. SESSIONID. If no data is passed through the pipe over a global file defined timeout. feof() will not return non-zero until ALL processes that have stdout attached to the pipe Data Protector is reading. L. Data Protector will report this timeout and consider this an error. When an object exec script is started. PREVIEW. http://education. Data Protector only captures the output of stdout. . The script can be modified as a test to explicitly set the Data Protector environment variables required by the script. If the script returns a non-zero value upon completion. the main tool available is to add the following lines after the first line in the script: set -x exec 2>&1 These lines put the shell into debug mode.” when working with exec scripts. Read and understand the section for “Advanced Tasks and Concepts” in the “Administrator's Guide. This is documented in the Administrator's Guide in the section for "Advanced Tasks and Concepts. the environment is very similar.P.00 16-45 2003 Hewlett-Packard Development Company. Confirm nothing is hung on an attempted read from stdin. We can help if Data Protector is not detecting the return correctly. Other ideas are to execute the ID command to confirm the ownership is correct. If the script does not work from cron. you will be able to see the commands as they are executed. If the script does run from cron. Execute the env command to ensure your environment is correct.Module 16 Troubleshooting Data Protector checks the return of waitpid() for session exec scripts and pclose() for object exec scripts that monitor the return of the script. su may alter the environment Data Protector sets up to run the script. Anything the commands send to stdout unless your script redirects it somewhere else will also be captured in the session output. Except for Data Protector setting up the environment for some Data Protector specific variables. to handle error conditions within the script and exit with the desired exit code. Another idea is to confirm the script works when run from cron as the owner of the backup specification or barlist. If the following test scripts echo the correct information. set the proper environment variables and capture the return. Since Data Protector is capturing stdout. HP will not debug a customer exec script." Data Protector's function is to start the script with the correct owner. Also. We can help in assuring the script is started and with the correct ownership and Data Protector environment variables set. you have confirmed that Data Protector is not the problem. The exec line redirects stdout to the same place as stdout.hp. If the script is started with the correct ownership and Data Protector environment variables but does not function as expected this is NOT a Data Protector supported issue. How the script functions is totally the responsibility of the designer of the script. this does NOT mean it this is a Data Protector problem. it is unlikely to work from Data Protector. L. Data Protector does not support the use of “su” from an exec script. It is completely the responsibility of the script designer to set any environment necessary for the script Data Protector does not set. http://education.com U1610S B. If problems arise with the script. The commands are echoed to stdout. this will be considered an error. Anything else is consulting and beyond the scope of what HP is able to provide. You can also change the exit values to confirm Data Protector is checking the return code properly. L.00 16-46 2003 Hewlett-Packard Development Company. http://education.P.00 only echo "exiting $0" echo "---------------------------------------------------------" exit 0 Session Post-exec Script (for POSIX shell) #!/usr/bin/sh echo "---------------------------------------------------------" echo "entering $0" echo "Output from id is " `id` echo "PREVIEW is ${PREVIEW}" # 1 if preview is running echo "SESSIONID is${SESSIONID}" # session post-exec only echo "SMEXIT is ${SMEXIT}" # session post-exec only echo "OWNER is ${OWNER}" echo "DATALIST is ${DATALIST}" # echo "RESTARTED is ${RESTARTED}" # echo "SESSIONKEY is ${SESSIONKEY}" # echo "MODE is ${MODE}" # echo "exiting $0" echo "---------------------------------------------------------" exit 0 Object Pre-exec Script (for POSIX shell) #!/usr/bin/sh echo "---------------------------------------------------------" echo "entering $0" echo "Output from id is " `id` echo "PREVIEW is ${PREVIEW}" # 1 if preview is running echo "exiting $0" echo "---------------------------------------------------------" exit 0 Object Post-exec Script (for POSIX shell) #!/usr/bin/sh echo "---------------------------------------------------------" echo "entering $0" echo "Output from id is " `id` echo "PREVIEW is ${PREVIEW}" # 1 if preview is echo "BDACC is ${BDACC}" echo "exiting $0" echo "---------------------------------------------------------" exit 0 U1610S B.hp.com .Module 16 Troubleshooting Session Pre-exec Script (for POSIX shell) #!/usr/bin/sh echo "---------------------------------------------------------" echo "entering $0" echo "Output from id is " `id` echo "SESSIONKEY is ${SESSIONKEY}" # session pre-exec only echo "PREVIEW is ${PREVIEW}" # 1 if preview is running echo "OWNER is ${OWNER}" echo "DATALIST is ${DATALIST}" # echo "RESTARTED is ${RESTARTED}" # echo "SESSIONKEY is ${SESSIONKEY}" # echo "MODE is ${MODE}" # 3. 00 17-1 2003 Hewlett-Packard Development Company.com U1610S B. L. http://education.hp.P. . you will be able to do the following: • • Modify the Data Protector global options. Modify the Data Protector local options.Module 17 — Customizing Objectives Upon completion of this module. typically time-outs. Student Notes In most situations. http://education. The global options file. L.Module 17 Customizing 17–1. the Data Protector default configuration and options are adequate for everyone. SLIDE: Customizing Customizing The behaviour and appearance of Data Protector may be customized using the global and . and limits and affect the entire Data Protector cell. many options can be changed that affect the appearance and behavior of the product.P.00 17-2 2003 Hewlett-Packard Development Company. All global options are explained in the global options file. Global Options File Global options cover various aspects of Data Protector.com .omnirc files. is found in the following location: Location on HP-UX Systems /etc/opt/omni/options/global U1610S B.hp. which allows you to customize Data Protector. However. hp. this is the backup queuing time. How To Use Global Options To use a global option. but is only used if the items are uncommented. To uncomment a line. Commonly Used Variables The following list includes the most often used global variables. The options file contains many of the Data Protector defaults. See the Global Options file for a complete description. Each option currently in the file has a hash mark. (default is 15 minutes) http://education.com U1610S B. Motif. or pound sign (#). (default is 0.P. L. (default is 60 minutes) ExecScriptOnPreview: Determines if pre/post execs are executed during the preview mode.00 17-3 2003 Hewlett-Packard Development Company. These options are not directly distributed to disk or media agents. simply remove the ‘#’ mark. MaxBSessions: Increase the default limit of five concurrent backups InitOnLoosePolicy: Prevents Data Protector from automatically initializing blank or unknown tapes on under a loose media policy. uncomment the line that has the option name and set appropriate value. off) ScriptOutputTimeout: The amount of time that the SM will wait for a pre/post exec script to complete. • • • • • • • MediaView: Change the fields and their order in the Media Management context. which comments out the option. This file may be modified whenever the need to affect the options in the file is necessary. This means that it does not affect Data Protector. SmWaitForDevice: The amount of time spent waiting for a device. MaxMAperSM: Increases the default limit of five concurrent devices per backup session. . Average users should be able to operate the product without changing them.Module 17 Customizing Location on Windows NT Systems <Data Protector_home>\config\options\global How Global Options Work Option settings from this file are available to all user interface programs (Windows. and the command line interface) and all Cell Manager programs. Whenever CRS needs to be bound to a specific port use this option to specify the port.dat file before installing the cell server. # hostname and user information. the following Data Protector events are logged to a Windows NT EventLog: -start/stop Cell Request Server -start/stop Session Manager -device mount request -device error -all MAJOR/CRITICAL session messages Note that this is Data Protector NT specific option and it logs events only on cell manager computer. # LogCrsEvents=0 or 1 # default: 0 # If set to 1.com . L. CRS creates <Data_Protector_home>/log/crsevents. # Port=InetPortNumber # # # # # # # default: 5555 Data Protector inet process listen port.00 17-4 2003 Hewlett-Packard Development Company. If the Data Protector default port is already used by some other product you should change this. TEXT PAGE: Contents of the globals File (Global Options version 5. time. Enter the new port number in the /tmp/omni_tmp/socket. http://education.log file # where it logs all CRS events along with the date. # EventLogMessages=0 or 1 # # # # # # # # # # default: 0 If set to 1. U1610S B. NOTE: it is up to the Data Protector # administrator to delete the file if it grows too large and # occupies too much disk space.hp. # CrsPort=CrsPortNumber # # # # # default: no default value By default (if this option is not set) Data Protector CRS process dynamically sets the listening port at runtime.P.Module 17 Customizing 17–2.1) # AbortIfMINgtDevices=0 or 1 # # # # default: 0 If set to 1 and MIN value of load balancing is greater than number of devices used in backup session the session aborts. Cell server installation scripts will also update your global file. if a database backup is started. a purge session will be suspended whenever a backup/restore session is running. # DBPurgeSuspension=0 or 1 # # # # # # # # # # # # default: 1 If this option is set to 1 (default). the purge session creates a number of transactions stored in the online backup transactions file. . If free disk space is lower than this number. L. This affects the size of the file and a time needed to restore the transactions from the online backup transactions file to the database when the backup is finished. Additionally. Data Protector will stop searching for files when more than <NumberOfFiles> files matches the specified search pattern. # DBMaxFilesInDir=NumberOfFilesInDirectory # # # # # # default: 2000000 This limit is used by the Data Protector database. otherwise Data Protector reports the database is corrupted.00 17-5 2003 Hewlett-Packard Development Company.P.Module 17 Customizing # DBMaxFilesFound=NumberOfFiles # # # # # default: 500 This limit is used by the Data Protector file pattern search function. purge session manager ("PSM") will suspend its execution while database check is in progress. This is a standard notification event and can be used to trigger predefined report or action.hp. special event will be triggered (DbSpaceLow). If this option is set to 0.com U1610S B. This influences backup performance as if there was another backup/restore session running. http://education. # DBPurgeSuspensionDuringDBCheck=0 or 1 # # # # default: 1 If this option is set (=1). a purge session will continue in parallel with backup/restore sessions. Increase the number if a directory with more than <NumberOfFilesInDirectory> files exists. It prevents endless loops if the database is corrupted. # DBFreeDiskSpace=MinSpaceInMBytes # # # # # # default: 50 This option is used for checking free disk space on disks where Data Protector internal database is located. if set. http://education. 2 # # # # # # default: 0 This global option controls which algorithm will be used to select the directory for the creation of the new DCBF file. 1.Balance size 2 .Module 17 Customizing # DBFreeExtFileSpace=MinSpaceInMBytes # # # # # default: 250 This option is used for checking free extension file space.dat (base and extension files) have less then specified number free space. # BrowseHistoryStart=NumberOfDays # # # # # # # # default: 0 (disabled) If "Search interval" in GUI is set to "None". 0 . backup sessions without any valid media. U1610S B. If fvers.00 17-6 2003 Hewlett-Packard Development Company. Option is meant to prevent CU with large history from selecting "None" by accident and thus slowing down browsing.Balance number # MaxDCDirs=NumberOfDirectories # # # # # default: 10 minimum: 1 maximum: 50 This option Directories. then global option BrowseHistoryStart. overrides it to whatever value specified in BrowseHistoryStart.P. Specifying 0 disables cache all together.Fill in sequence 1 . and media management sessions) are kept in the database. Data Protector will trigger special event (DbSpaceLow). Even if this global option is set. CU can still browse history before BrowseHistoryStart by specifying in GUI search interval larger than BrowseHistoryStart.com . L. # DCDirAllocation=0.dat and fnames. # BrowseMPosCache=NumberOfMegabytes # # # # default: 40 This option specifies upper limit of memory used by DBSM when browsing Detail Catalog. specifies maximum number of configured DCBF # KeepObsoleteSessions=NumberOfDays # # # # # default: 30 This global option controls how many days obsolete sessions (restore sessions.hp. hp. using the twenty-four hour clock notation. # DailyMaintenanceTime=HH:MM # # # # default: 12:00 This option is used for starting daily maintenance tasks at first omnitrig run after the specified time each day. http://education.Module 17 Customizing # KeepMessages=NumberOfDays # # # # # default: 0 This global option controls how many days the session messages are kept in the database (if the session is not obsoleted and removed sooner). # RecoveryIndexDir=FullPathToTheBackupDir # # # # # default: none This option sets backup directory for the obrindex.P. the recovery index will be created/appended into this directory in addition to the default recovery index file. Specifying 'None' disables starting daily checks. Valid values are hour:minute. # DailyCheckTime=HH:MM # # # # # default: 12:30 This option is used for starting daily checks at first omnitrig run after the specified time each day. # KeepDiskonlySessions=NumberOfDays # default: 365 # This global option controls how many days # backup sessions are kept in the database. # SessionMessagesDir=FullPathToTheMessageDir # # # # # default: /var/opt/omni/db40/msg (HP-UX) default: Data Protector_Home\db40\msg (Windows) This global option determines the location of the session messages. L. using the twenty-four hour clock notation. If this is changed.dat file. Valid values are hour:minute.00 17-7 2003 Hewlett-Packard Development Company. . If this directory pathname is writable. If the value is 0 then the session message are not removed before session.com U1610S B. the diskonly # RepositionWithinRestoredObject=0 or 1 # # # # default: 1 This option specifies if restore should use repositioning and multiple disk agents to restore trees and files within one object. then it is users responsibility to move the existing files. This option specifies maximum idle time for devices. Backup Session Manager (BSM) sets catalog retention to object protection if catalog retention is larger than object protection. session pre-exec is started after device lock.com .00 17-8 2003 Hewlett-Packard Development Company. you should change this to specify the maximum size of a "file" medium. Backup Session Manager (BSM) executes session pre-exec before successfully locking needed devices. Backup Disk Agent (BDA) for every volume of host object will execute pre/post-exec specified. If this option is not set (=0). Note that for the duration of pre/post-exec scripts.Module 17 Customizing # BackupPreexecBeforeDevLock=0 or 1 # # # # # default: 0 If this option is set (=1). If the global option is changed. BSM will not be respondable. When Data Protector writes specified size of data in one file. # FileMediumCapacity=MaxSizeInMBytes # # # # # # # default: 100 If you are using "file" devices. if set to 1. # PrePostExecOnEveryVolumeForHostBackup=0 or 1 # # # # # # # # default: 0 If this option is set (=1). If set to -1. # BackupDeviceIdle=seconds or -1 # # # # # default: 600 During "BAR" backups. and if set to 2 executing of external scripts is not allowed. If set to 0. Backup Session Manager (BSM) will execute pre-exec just prior to starting first volume BDA and post-exec after last volume BDA finished. the logical medium must be exported and the file U1610S B. L. devices can be running without assigned objects. http://education. # BackupCatalogProtectionEqualToObject=0 or 1 # # # # default: 0 If this option is set (=1). you will get a mount prompt. no checking is performed.hp. the next "file medium" will be loaded.P. Or if you are using "file" exchanger. Otherwise. BSM doesn't close and unlock device until session has finished. script can be executed only in bin directory. # ExternalScriptMode=0 or 1 or 2 # # # # # # default: 0 This option is used to check if omnirpt is allowed to execute script on CM as external method. You can override this setting for each configured device with advanced options of the device. # MountDelay=DelayInMinutes # # # # # # default: 30 This is the default mount prompt delay (session manager will wait for specified time for someone to confirm/cancel a mount request. # ScriptUser=username # # # # # # # # default: "omniback" The backup session manager tries to execute scripts with permission from the user who started the session or from the owner of the session if the owner of the session has switched. # MountScript=FullPathname # default: "/opt/omni/lbin/Mount. # MMFairLimit=PercentageOfPoor # # # # # # # default: 80 This limit is used for detecting "Fair" (almost "Poor") media.hp. it tries to execute the script as the ScriptUser. If Data Protector cannot find the user in the /etc/passwd file.00 17-9 2003 Hewlett-Packard Development Company. Data Protector will check barcodes (during barcode rescan) and if the barcode starts with specified Prefix. http://education. You can override this setting for # each configured device with advanced options of the device. the script is not executed. a mount script will be executed).com U1610S B. .P. initialization. If there is no answer on mount prompt.sh" # Default mount script. but it cannot detect a cleaning tape. This is useful if you have devices with barcode support. the medium will be treated as a cleaning tape. Otherwise the original size # ClnTapeBCPrefix=Prefix # # # # # # default: CLN If this option is set to a non-empty value. Data Protector Media Management uses such ("Fair") media only if there is no "Good" media available. L. When a medium exceeds a specified percentage of limit specified for "Poor" media (this limit can be set for each pool). it is marked as "Fair".Module 17 Customizing # removed before # will be used. If even the ScriptUser is not found in the /etc/passwd file. # FreePoolDeallocFreq=TimesPerDay # # # # # # # # # default: 1 limit: 1 <= FreePoolDeallocFreq <= 96 This period is used to run free pool deallocation process on Data Protector Cell Manager (Media Mgmt 2). Set this variable only after consulting the Hewlett-Packard support.. The GUI will show in list of users to configure only users with higher UID than MinimumUID. deallocation is performed once per day (00:00). the Monitor GUI will show only new messages (messages which were generated after connect). # InitOnLoosePolicy=0 or 1 # # # # default: 0 This option is used by backup session manager. unless prior agreement from Hewlett-Packard support is obtained.12:00). 06:00. uucp. # EnableSCSIReserveRelease=0 or 1 # # # # # # default: 0 If set to 1. 08:00. # MinUID=MinimumUID # # # # # default: 100 This limit is used by the User Configuration GUI. set to 4 four times per day (00:00. L. set to 2 two times per day (00:00. this option enables access to the SCSI reserve/release functionality used with library robotics. when the media # is ejected from the slot. the Monitor GUI will show all messages generated by a session when the user connects to a running session. U1610S B.00 17-10 2003 Hewlett-Packard Development Company. free pool deallocation will be started every 15 minutes.hp. this option is checked if the session manager should automatically initialize new media. 18:00).Module 17 Customizing # NonResidentLocation=NonResidentLocationString # default: "" # This is the string displayed in location field. daemon. If maximum (96) is specified. When using loose policy media checking.P. If set to 1. If this is not set.com . 12:00. This is useful for excluding non-human users like root. http://education. General use of this variable is not supported. 16:00). bin.. # ShowAllMsgs=0 or 1 # # # # # default: 1 If this option is set. set to 3 three times per day (00:00. com U1610S B. BindTimeout is expected # maximum response time of each Cell Server to MOM GUI. In some cases. Topic Help and "Data Protector on the Web". L. # OnlyValidObj=0 or 1 # # # # # # default: 1 This option changes the list mode for versions of the object (in GUI and CLI). If this option is set to "1" (default). Restore or Monitor operation will continue. # BindTimeout=TimeoutInSeconds # default: 15 # BindTimeout is used by the MOM GUI. there can be a lot of messages to put in the message part of the window.00 17-11 2003 Hewlett-Packard Development Company. This may cause the GUI to abort because it runs out of memory. http://education. . Several values can be divided by ":". # AcroRead=AcrobatReaderCommand # default: "/opt/Acrobat4/bin/acroread" # The command to start the Acrobat reader for displaying # documentation files. Restore and Monitor GUI message windows. only valid (at least one medium of object exists) object versions are listed and if set to "0". The Backup. unusable for restore).hp.Module 17 Customizing # MaxGUIMsg=SizeOfMsgWindowInBytes # # # # # # # # # default: 1 MB This limit is used to limit the output to Backup. So if the total sum of all messages (length) is greater than the specified limit. # HideMethodsPerClient=0 or 1 # default: 1 # This option is used to hide the End User Notification capability by # default. # TM_LABEL_xx=MenuLabel # See the variable TM_ACTION_xx for details. # WebBrowser=WebBrowserPath # default: "/opt/NSCPcom:/usr/dt/bin" # The search path for finding the Netscape browser used in # displaying Online Help. all object versions are listed (even invalid object versions.P. the GUIs will stop writing messages to the message window (The user will get a warning message). VBDA performs aligned backup. aligned backup in VBDA is disabled (default). # Otherwise.Module 17 Customizing # AlignedDefault=0 or 1 # default: 0 # If this option is set. U1610S B. # HidePrivateObj=0 or 1 # # # # # # default: 1 If this option is set (=1). In such case. protection of a related chain is not checked at all. http://education. Admin users have full access (no checking). # StrictPrivacyCheck=0 or 1 # # # # # # default: 1 If this option is set (=1).com . If an option is not set (=0).P. Data Protector will never show objects that are private to other users (except admin users). Admin users have full access (no checking). incremental backup is automatically upgraded to a full backup if there is no valid related chain to be used for incremental backup. # UpgradeIncrToFull=0 or 1 # # # # # default: 1 If this option is set (default). # IncrOnProtected=0 or 1 # # # # # default: 1 If this option is set (default). If this option is not set (=0). the backup session manager will abort incremental backup. Otherwise. Username. only the username is checked. Data Protector will force full backup for every object that failed or was aborted in last full backup. Otherwise.00 17-12 2003 Hewlett-Packard Development Company.hp. L. but restore is still denied. groupname and hostname must match for an object to be accessible by a user. Data Protector will make new Full backup of the object instead. Data Protector strictly checks private objects (backups). This allows very strict handling of backup generations and does not allow incremental backup to be made on full/incremental backup from previous generation. objects are shown in list of objects of session / on medium. incremental backup is done only on a protected chain (all backups from full to last incremental must be protected). # ForceFull=0 or 1 # # # # # # # # default: 0 If this option is set (=1). # UseMaxConc=0 or 1 # # # # default: 0 If this option is set (=1).com U1610S B. L. sessions (session # MaxBSessions=MaxNumberOfBackupSess # # # # # default: 5 limit: 1 <= MaxNumberOfBackupSess <= MaxSessions The maximum number of concurrently running backup sessions (backup session managers).). http://education. If the number provided is out of specified range. . It is used for load balancing and does not limit the number of media agents with statically assigned objects. If operation can not be completed within timeout value.00 17-13 2003 Hewlett-Packard Development Company. Check the global option 'MaxDAperMA' for to find out the maximum concurrency.P. This is actually the maximum concurrency of any device in the cell.Module 17 Customizing # MaxSessions=MaxNumberOfSessions # # # # default: 200 limit: 25 <= MaxNumberOfSessions <= 200 Maximum number of concurrently running managers). RSM. # MaxMAperSM=MaxMediaAgentsPerSM # # # # # # default: 32 limit: 1 <= MaxMediaAgentsPerSM <= 32 The maximum number of concurrently running media agents per session manager. default (5) will be used. BSM will always start the MA with maximum concurrency. error is issued and connection closed. # SmSendReceiveTimeout=timeout in seconds # # # # # default: 1800 This timeout is used when sending or receiving data from Session Manager (BSM. # MaxDAperMA=MaxDiskAgentsPerMA # # # # # default: 32 limit: 1 <= MaxDiskAgentsPerMA <= 32 Maximum number of concurrently running disk agents per media agent.hp. etc. However. http://education. Used when starting an agent. a warning message is displayed indicating that any additional messages from this session will not be stored into to the database. When this value is exceeded.Module 17 Customizing # SegmentsPerDA=SegmentsPerDA # # # # # # default: 30 limit: 0 <= SegmentsPerDA <= 2147483647 This number is used by the Restore SM to determine how often to start disk agents for the restore of OmniStorage (VBFS) volume. L.com . # MinDelayForConnectionRetry=TimeInSeconds # # # # # default: 30 limit: 0 <= MinDelayForConnectionRetry <= 120 Specifies the minimum time in seconds between connection retries. If 0 is specified.00 17-14 2003 Hewlett-Packard Development Company. If connection fails next one will not be attempted until this time has elapsed. # SmMaxAgentStartupRetries=NumberOfRetriesAtAgentStartup # # # # default: 1 limit: 1 <= SmMaxAgentStartupRetries <= 50 This option specifies the maximum number of retries that a session manager will use to start an agent before it fails. # SmMaxAgentMessages=NumberOfAgentMessages # # # # # # # # default: 3000 This option specifies the maximum number of messages received from a single Media/Disk agent that Backup/Restore Session Manager will store into the database. messages are still visible in the session monitor while session is alive. only one disk agent will be started and therefore all media will be read (slow).hp. a warning message is displayed indicating that any additional messages from this particular agent will not be stored into to the database. # SmMaxMessagesPerSession=NumberOfMessagesMessagesPerSession # # # # # # # # default: 30000 This option specifies the maximum number of messages per one session that Backup/Restore Session Manager will store into the database. When this value is exceeded. # SmWaitForNewClient=WaitForInMinutes # U1610S B. However.P. messages are still visible in the session monitor while session is alive. # SmWaitForFirstClient=WaitForInMinutes # # SmWaitForFirstClientSec=WaitForInSeconds # # # # # default: 10 minutes This timeout is used by the backup session manager. BSM: After the last BAR client disconnects. BSM will complete the session and go down. BSM will wait for specified timeout. If there are no connections in the specified timeout. If it can not open the database within the timeout it will go down and report it in the global debug http://education.com U1610S B.hp. In general. . license etc. If a lock can not be obtained for the desired devices. RSM: After receiving request for restore for specified device. # SmWaitForDB=WaitForInMinutes # # # # # # default: 60 minutes This timeout is used by the backup session manager. After the backup script on the BAR system starts.log file to log the start and end time. # SmLogStartStop=0 or 1 # # # # default: 0 If this option is set (=1). BSM tries to open the database at startup. session managers will put an entry into the /var/opt/omni/log/sm. If dynamic is used then the Backup Session Manager tries to get a lock for the minimum number of devices used for backup. the BSM will wait for the specified time-out. SmWaitForDevice is used as a time-out for different kinds of queuing (queuing for lock. # SmWaitForDevice=WaitForInMinutes # # # # # # # # # # # default: 60 minutes This timeout is used by the Backup Session Manager. If there are no new connections in the specified timeout. the BSM will wait for specified timeout for the first client connections. Changing this timeout may influence restore performance. If the database cannot be opened (omnidbcheck or omnidbutil are running). the backup session will fail. If it can not get a lock for the devices.P. BSM will go down.Module 17 Customizing # SmWaitForNewClientSec=WaitForInSeconds # # # # # # # # # default: 30 seconds This timeout is used by backup and restore session managers (BSM and RSM). L. The Backup Session Manager first tries to get a lock for all devices that will be used for backup. RSM will wait for specified timeout before actually starting RMA.00 17-15 2003 Hewlett-Packard Development Company. BSM will wait for specified timeout for new client connections.). 00 17-16 2003 Hewlett-Packard Development Company. it will wait for specified timeout for an initial identification from the session manager. You do not get this in GUI selections! AgeLimit is age of a medium (in months) after which medium condition is set to Poor. If the session manager does not identify itself.log ) # failed. CRS will kill the session manager. http://education. # ScriptOutputTimeout=TimeoutInMinutes # # # # # default: 15 minutes This timeout is used by the Backup SM.com . L.. # MC_x=Visible # # # # # # # # # # # # # # # Default values for different media classes. x is a media class number (see defaults table . Can be set in pool configuration. but can still be used. If set to 0. The alternative is to check for environment variable PREVIEW (1 or 0). DefSize is the default size of media (in KBytes) of that class. When CRS starts the session manager. DefConc is the media class default concurrency (must be U1610S B. OverwriteLimit is number of overwrites after which a medium condition is set to Poor.).. which is exported to the environment of the pre/post-exec script.P. This is used to set to medium size if size cannot be detected by the device itself. remote session and object pre/post-exec. The session pre-exec or post-exec script should send some output at least every ScriptOutputTimeout minutes.for DDS. or the session gets aborted by the session manager. The Visible field is either 0 or 1. # MaxWaitForSm=WaitForInSeconds # # # # # # default: 25 seconds This timeout is used by the Cell Request Server (CRS). the media class is visible in the Pool Configuration GUI. If set to 1. that the session has # SmDisableScript=0 or 1 # default: 0 # This value is used to disable any execution of pre/post-exec # scripts: session. you would specify MC_1=xxxx. # ExecScriptOnPreview=0 or 1 # # # # # # default: 0 This option is used by the Backup SM to check if it should execute the session pre-exec script or post-exec script when backup preview is running.Module 17 Customizing # file ( /var/opt/omni/log/debug. Can be set in pool configuration.hp. it is not visible. it will close the database.00 17-17 2003 Hewlett-Packard Development Company. policy number (see defaults table).com U1610S B.hp. --------------------------------------------| DevicePolicy | x | Visible | --------------------------------------------| Standalone | 1 | 1 | | Stacker | 3 | 1 | | SCSI-II Library | 10 | 1 | | Jukebox | 5 | 1 | | External control (script) | 6 | 1 | | Grau DAS exchanger library| 8 | 1 | | STK Silo medium library | 9 | 1 | --------------------------------------------x is device # DBIdleTimeout=TimeoutInMinutes # # # # # # default: 30 minutes This timeout is only used by the Database Session Manager (DBSM).Module 17 Customizing # # # # # # # # # # # # # # # # # # # # # # # # between 1 and 5) . Defaults: ---------------------------------------------------------------------------| MediaClass | x | Visible | AgeLimit | OWrLimit | DefSize | DefConc | ---------------------------------------------------------------------------| DDS (4mm) | 1 | 1 | 36 | 100 | 2 GB | 2 | | Exabyte (8mm) | 3 | 1 | 36 | 250 | 5 GB | 2 | | DLT | 10 | 1 | 36 | 250 | 20 GB | 4 | |T3480/T4890/T9490| 5 | 1 | 36 | 250 | 256 MB | 3 | | 3590 | 12 | 1 | 36 | 250 | 10 GB | 4 | | D-3 | 11 | 1 | 36 | 250 | 25 GB | 4 | | Reel Tape | 9 | 1 | 36 | 250 | 500 MB | 3 | | Optical/RawDisk | 6 | 1 | 36 | 250 | 325 MB | 2 | | File | 7 | 1 | 36 | 250 | 100 MB | 3 | | QIC | 2 | 1 | 36 | 250 | 4 GB | 2 | | AIT | 4 | 1 | 36 | 250 | 25 GB | 4 | | STK9840 | 8 | 1 | 36 | 250 | 40 GB | 3 | | T3590 | 12 | 1 | 36 | 250 | 10 GB | 4 | | LTO-Ultrium | 13 | 1 | 36 | 250 | 100 GB | 4 | | SuperDLT | 14 | 1 | 36 | 250 | 100 GB | 4 | | DTF | 16 | 1 | 36 | 250 | 42 GB | 4 | | 9940 | 17 | 1 | 36 | 250 | 60 GB | 3 | ---------------------------------------------------------------------------- # DP_x=Visible # # # # # # # # # # # # # # Default values for different device policies.you can override this for each configured device.P. When the GUI/command request a data again. . http://education. When the DBSM is inactive (GUI/command does not request any data from it) for a specified time. Visible . L.same as for MC_x. the DBSM will try to open the database again and reply to request. The front-end (GUI or command) which started the session manager. U1610S B. It will be used when the device becomes available.) the connected client should identify (send its name and version) itself to the session manager in the specified time. # DBLockTimeout=TimeoutInSeconds # # # # # default: 1800 limit: 120 <= TimeoutInSeconds <= 7200 This timeout is used by Velocis. the Session Manager does not reconnect to "MMD".P. If after a specified timeout. The running BMA will NOT be aborted. Otherwise the SM will go down. the Session Manager's device. A Velocis call will wait for a specified timeout for a table lock. SM closes connection to the client. If the new connection was established to the session manager (for example: the started Disk Agent/Media Agent has connected to SM.00 17-18 2003 Hewlett-Packard Development Company. the BSM will start a new media agent (if any). new monitor (xomnimonitor/omnistat) has connected to SM. media and slot locks are cleared. # SmPeerID=WaitForInMinutes # # # # # # # # # # default: 5 minutes This timeout is used by all session managers (BSM/RSM/MSM/DBSM). should connect to the SM in the specified time. # SmWaitToOpenDevice=WaitForInSeconds # # # # # # default: 30 seconds If the BMA cannot open the device for SmWaitToOpenDevice time period (for example: in the case when OB2SLEEP and OB2RETRY are big).Module 17 Customizing # MMDLockTimeout=TimeoutInMinutes # # # # # default: 60 minutes This timeout is used in case of communication problems between "MMD" and Session Managers.. L.hp.com . See also: DBLockTries. # DBLockTries=NumberOfTries # # # # default: 10 limit: 1 <= NumberOfTries <= 100 This value specifies how many times the "DB" will retry on a failed lock request. before the lock request will fail.. # SmFirstConn=WaitForInSeconds # # # # # default: 30 seconds This timeout is used by all session managers. If the client does not identify itself in the specified time. http://education. Note: Agents are sending status messages to the SM in constant intervals. After the disk agent disconnects from the session manager. .00 17-19 2003 Hewlett-Packard Development Company. The MA timeout should always be higher than the DA timeout.Module 17 Customizing # SmMaIdleTimeout=TimeoutInMinutes # # # # # # # # # # # # default: 140 minutes This timeout is used only by the Backup and Restore SM. # UsePanScripts=0 or 1 # # # # # default: 0 If this variable is set (=1). check also the variable SmDaIdleTimeout. post-exec scripts and mount request scripts from the /opt/omni/lbin/scripts directory. so normally this inactivity should not happen (this prevents SM from hanging a complete session in case a disk agent hanged). so normally this inactivity should not happen (this prevents the SM from hanging a complete session in case a media agent hanged). L. No scripts in other directories can be started for security reasons. This delay solves timing problems in TCP/IP on some platforms. Note: Agents are sending status messages to the SM in constant intervals. the SM closes the connection to the agent. # DaStartDelay=DelayInSeconds # # # # # # # default: 5 seconds limit: 0 <= TimeoutInSeconds <= 30 This delay is used by backup & restore session managers. If a connected disk agent is inactive (no message was sent to SM) for the specified time. SM will wait for a specified delay period before it starts a new disk agent. If this variable is changed. # SmDaIdleTimeout=TimeoutInMinutes # # # # # # # # # # # default: 120 minutes This timeout is used only by Backup & Restore SM.P. If this variable is changed. If the connected media agent is inactive (no message was sent to the SM) for the specified time.com U1610S B. check also the variable SmMaIdleTimeout. The MA timeout should always be higher than the DA timeout. SM closes the connection to the agent.hp. http://education. Data Protector will always try to start the session pre-. Module 17 Customizing # MultiHomed=0 or 1 # default: 1 # If set. # SessSuccessfulWhenNoObjectsBackedUp=0 or 1 # # # # # default: 0 This option this option behavior in were backed is used by Data Protector. this option allows tape statistics logging into # media. additional alias hostnames for # Ob2TapeStatistics=0 or 1 # default: 0 # If enabled. L. host backup exclude options apply only to a single volume.P.hp. this option allows checking of medium header # before medium is removed (ejected). By setting to 1 user can change the Data Protector order to report session as successful when no objects up. # Ob2HeaderCheck=0 or 1 # default: 1 # If enabled. # HostBackupExcludesApplyToSingleVolume=0 or 1 # default: 0 # If enabled.log file.00 17-20 2003 Hewlett-Packard Development Company. U1610S B. the user can add # ServiceGuard installations. http://education.com . uncomment the line containing the variable.Module 17 Customizing 17–3. which may not be the case for the # target tape during the copy operation. # # NOTE: Changing these variables can cause misbehavior of Data Protector # software components. If the variable is set to 1. # # To make a variable active. relevant only if the Library Control System # and not Data Protector controls the library robotics. If the variable is set to 0.com U1610S B. . When this variable # is set to 1. but only when removing entries (or renaming the file). The effect is that http://education. It is also possible that the # source and the target tape are of a slightly different length. # # OB2NOLOCKDRIVE=0|1 # Default: 0 # A StorageTek related variable. the drive is not locked during the Data Protector activity # on a drive. This can be due to a perfect streaming of # the source tape during the backup. # # To make it active. L. TEXT PAGE: Contents of the omnirc.00 17-21 2003 Hewlett-Packard Development Company. # When changing the omnirc file. # In order to avoid this. # # OB2BLKPADDING_<DeviceType>=<number_of_empty_blocks> # Default: 0 # During copying tapes it may happen that the data on the source tape does # not fit on the target tape.P. # remove all leading spaces and set the desired value for the variable # as follows: # <VariableName>=<VariableValue> # # An omnirc variable must be set on the Data Protector client that performs # the process affected by the variable. you have to restart the Data Protector # services/daemons on the Data Protector client where you modified the # omnirc file.hp. the below set of variables can be used to # specify the number of empty blocks written after the tape header at # the initialization time for various device types. copy it into file <Data_Protector_home>\omnirc. If the variable is set to 0. the drive is locked during the # Data Protector activity on a drive.TMPL File # #--------------------------------------------------------------------------# # Filename: <Data_Protector_home>\omnirc. Please contact Data Protector customer support # before changing any variables! # #=========================================================================== # Variables for a Media Agent client #=========================================================================== # OB2READ0_FSM=0|1 # Default: 0 # Some backup devices do not report the FILEMARK when 0 bytes is # read.TMPL # # $Revision: /main/dp51/42 $ # # This file is a template for Data Protector agent environment variables. # Specifically on Windows. This is mandatory for the crs daemon on UNIX and recommended # for Data Protector CRS and Data Protector Inet services on Windows. # The omnirc variables' default values are set by Data Protector binaries # and can not be set in this file. Data Protector treats such a situation # as a filemark. restarting is not required when adding or # changing entries. Data Protector does not treat # such a situation as a filemark. if you have configured a logical device with the name DLT_STD. the empty blocks should take up approximately 1 percent of the length of the entire tape.ExaByte AIT .hp. the empty blocks are not copied. and tape copy should run without problems. You must specify a specific value for each configured logical device separately. OB2DEVRETRY=n Default: 30 U1610S B. OB2XS2RETRY=n Default: 15 Number of retries for the open call for the external SCSI II robotics control.P. the MA will finish the current data segment on the tape and start a new one. OB2XS2SLEEP=s Default: 10 Timeout (in seconds) between the open calls the external SCSI II robotics control. The optimum value of the variable differs from one medium to another. If this is still not enough for successful copying. OMNIMAXCATALOG_<LogicalDevice>=1-60 Default: 12 Sets the maximum size (in MB) of the Data Protector catalog that is sent by the MA to the BSM at the end of each segment. specifying the number of empty blocks to be written after the medium header (device default block size is used): OB2BLKPADDING_1 OB2BLKPADDING_2 OB2BLKPADDING_3 OB2BLKPADDING_4 OB2BLKPADDING_5 OB2BLKPADDING_6 OB2BLKPADDING_7 OB2BLKPADDING_8 OB2BLKPADDING_9 OB2BLKPADDING_10 OB2BLKPADDING_11 OB2BLKPADDING_12 OB2BLKPADDING_13 OB2BLKPADDING_14 DAT/DDS QIC Quarter Inch Cartridge 8mm . The number of blocks should be calculated according to the set block size.00 17-22 2003 Hewlett-Packard Development Company. L. increase the value by 0. When the medium is copied.Advanced Information Technology 3480 Cartridge Raw Magnetic Disk Regular Disk File STK 9840 Generic Magnetic Tape Device DLT .Digital Linear Tape StorageTek SD-3 . http://education. you need to set the OMNIMAXCATALOG_DLT_STD variable. Note that when the specified size is reached. For each device type.Module 17 Customizing # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # the size of data on the medium is smaller. You can get the logical device names in the Data Protector GUI or by using the omnidownload -list_devices command (the names are listed under the "Device name" column in the output of the command).Exabyte media written. For example.5 percent until you find the most suitable value. there is a special variable used. by changing the <LogicalDevice> with a specific logical device name. Normally.Redwood 3590 Cartridge (Magstar) LTO Ultrium Quantum SuperDLT For example: OB2BLKPADDING_3=5 This will put 5 empty blocks on the beginning of every 8mm .com . Sets the number of # retries for the open call for stacker devices. relevant only if the Library Control System # and not Data Protector controls the library robotics. relevant only if the Library Control System # and not Data Protector controls the library robotics. # # OB2SCTLMOVETIMEOUT=s # Default: 240000 # Data Protector timeout period (in milliseconds) after the SCSI II # MoveMedium command has been issued. Sets the timeout # (in seconds) between the open the calls for stacker devices. # Data Protector will try to check if cleaning tape is in the slot. which is the default # setting. # # OB2CHECKCLNSLOT=0|1 # Default: 1 # If a cleaning slot is specified on non-barcode device. . # # OB2DEVSLEEP=s # Default: 30 # Timeout (in seconds) between the open calls for the drives. and this variable is set to 1. # # OB2CLNRETRY=n # Default: 60 # Number of retries when accessing a slot that has the cleaning medium loaded. If the move is not completed after # this timeout. Data Protector issues tape-alert command to devices and reports # the retrieved tape-alert information. If the OB2TAPEALERT is set to 0 # the tape-alert reporting is disabled. the ioctl call will fail.00 17-23 2003 Hewlett-Packard Development Company.com U1610S B. It specifies the amount of time (in seconds) in # which Data Protector will re-trying to open a device special file of a drive.Module 17 Customizing # Number of retries for the open call for the drives. # # OB2CLNSLEEP=s # Default: 5 # Timeout (in seconds) between retries when accessing a slot that has the # cleaning medium loaded. if time limit for open retries (OB2DEVTIMEOUT) is exceeded. # # OB2STKRETRY=n # Default: 40 # A StorageTek related variable. it is assumed that cleaning tape is in slot and no check will # be performed. When a ADIC/GRAU DAS library is configured a # list of all DAS clients (GRAU_client_names) is defined in file # \DAS\ETC\CONFIG on the DAS server computer. # # OB2TAPEALERT=0|1 # Default: 1 # By issuing tape-alert command to devices Data Protector can retrieve and # report statistical information maintained by the device about the device # or its logical units. # # OB2DEVTIMEOUT=s # Default: 6600 # This is a Tru64 specific variable. is a ADIC/GRAU DAS # Library backup device related. # # DAS_CLIENT=<GRAU_client_name> # Default: If DAS_CLIENT variable is not set the client name OMNIBACK is used. On Tru64 system the retries # may end earlier. together with a DAS_SERVER variable. If # variable is set to 0. # # OB2STKSLEEP=s # Default: 5 # A StorageTek related variable. L. # This variable. When OB2TAPEALERT variable is set to 1.P.hp. Each Data Protector client with http://education. # By setting this variable to 1. Therefore DP retries this operation for # OB2_DAS_ENTER_RETRY times using timeout of OB2_DAS_ENTER_SLEEP seconds. In this way different Data Protector # clients can access ADIC/GRAU DAS library. # with a special SCSI II address for the eject Mailslot.P. Data Protector uses the direct access U1610S B. # # DAS_SERVER=<GRAU_server_name> # Default: if DAS_SERVER variable is not set the autochanger ioctl host is # used (parameter: -ioctl <server_name>). # # OB2_DAS_ENTER_RETRY=<number of retries> # Default: 10 # OB2_DAS_ENTER_SLEEP=<sleep for n seconds> # Default: 6 # These variables are ADIC/GRAU DAS Library backup device related. you can use up to 250 DAS drives in a # GRAU library. # DP tries to insert media but it takes some time for user to insert the media # and close the library door. # If this variable is set to Y. # If it is switched on. # If this variable is set to Y. # # OB2LIB_STACKIMP=<scsii_address> # OB2LIB_STACKEXP=<scsii_address> # Default: -1 (no default value) # If a library supports stack mode for entering and ejecting the media. each one with its unique # GRAU_clinet_name. # Example: # OB2LIB_STACKEXP=289 # OB2LIB_STACKIMP=288 # # OB2DASDRIVESTATUS2=0|1 # Default: 0 # By default only up to 15 DAS drives can be used in a GRAU library. # This variable defines the use of the direct restore functionality. # This variable. together with a DAS_CLIENT variable.com . the above two # variables are used to tell the Data Protector MA which # addresses to use for entering (OB2LIB_STACKIMP) and ejecting the media # (OB2LIB_STACKEXP). # # OB2NDMPDIRECT=Y|N # Default: Y # NDMP MA specific environment variable. L. the NDMP server will not create the file # history information. http://education. Data Protector can restore single files. When a ADIC/GRAU DAS library is configured a # list of all DAS clients (GRAU client names) is defined in file # \DAS\ETC\CONFIG on the DAS server computer. the NDMP server will create the file # history information. # # OB2NDMPFH=Y|N # Default: Y # NDMP MA specific environment variable. is a ADIC/GRAU DAS # Library backup device related. Each Data Protector client with # DAS agent installed that wants to access ADIC/GRAU DAS library robotics # individually should have the DAS_SERVER variable set to the host name of # the DAS server computer.Module 17 Customizing # DAS agent installed that wants to access ADIC/GRAU DAS library robotics # individually should have the DAS_CLIENT variable set to unique # GRAU_client_name defined on DAS server computer. It # is used only if the variable OB2NDMPFH is switched on at backup time. # If this variable is set to N. which is the recommended setting. When you wish # to insert new catridge into library this is done through I/O unit(mail slot). and one for the # enter Mailslot (although physically the same slot).hp.00 17-24 2003 Hewlett-Packard Development Company. If DAS_CLIENT is not specially declared the DAS_CLIENT # client name OMNIBACK is used. http://education. the OB2SCSITIMEOUT variable is used. If set to 1. # # OB2ALIGN=n # Default: 0 # Used to define the alignment factor for backup read calls.com U1610S B. # #=========================================================================== # Variables for a Disk Agent client #=========================================================================== # # OB2ENCODE=0|1 # Default: 0 (encoding is off) # Setting the variable overrides the backup option -encode for the # backup disk agent. Use this variable to control which files should # be backed up when an incremental backup is performed. If used. before running the sanconf command. it must be set on all clients affected by the # sanconf command. # # OB2SANCONFSCSITIMEOUT=s # Default: if not set. It is used for performance # improvement on HP-UX VxFS only. the direct access restore functionality # is disabled. L.Same as 0. # 1 . the Disk Agent uses the "last modified" # and "last accessed" time attributes to detect the files changed # since the last backup. This variable takes # effect only when specified together with the "OB2CHECKCHANGETIME" variable.P. The recommended # value is 15 seconds. # # OB2CHECKCHANGETIME=0|1|2 # Default: 1 # During the incremental backup. . OB2ALIGN variable sets the alignment to # (media_blocksize * align factor). Backs up modified # files. # 2 .00 17-25 2003 Hewlett-Packard Development Company. # # OB2SKIPDIRECTORY=0|1 # Default: 0 # Setting the variable allows the backup option -skip for directory not # only files. # There are three valid values: # 0 . This improves backup performance. # # OB2INCRDIFFTIME=s # Default: 0 # Specifies an "incremental latency" period (in minutes) that is enforced # when checking the inode "last accessed" time with incremental backups.Only the "last accessed" time attribute is checked. # Install the latest VxFS patch on your system before setting this variable. If greater # than zero. and all subsequent file backup reads # are performed according to this size.Always checks both time attributes. Backs up modified and moved files. # If this variable is set to N. except when the option "do not preserve access time attributes" # is selected and file locking is disabled. The # referential time received from the Session Manager (time of the previous # backup) is the first incremented by the specified period and then compared # to the inode "last accessed" to qualify for backup.hp. # meaning that direct data transfer between the disk and the user-supplied # buffer for reads and writes is used. # This variable sets the timeout value for the sanconf command triggered # operations. # A sanconf command specific variable.Module 17 Customizing # restore functionality. # # OB2VXDIRECT=0|1 # Default: 0 # A VxFS related option. then VxFS VX_DIRECT advisory is set. In this case it acts the same # as when the variable is set to 2. but does not back up moved files. no warnings will be displayed when trying to back up filesystem # containing mount point to local or NFS mounted filesystem.Volume Manager Disk Group # # OB2NOREMOTEWARNINGS=0 | 1 # Default: 0 # If enabled. the HP StorageWorks # XP Agent checks the status of mirrored disks within a check interval # specified by the SSEA_SYNC_SLEEP_TIME variable for so many times as # specified by the SSEA_SYNC_RETRY variable. specify: # OB2CLUSTERDISKTYPES=NETRaid4M Diskset. if you are using NetRAID4M disk. snapshot and direct backup (HP StorageWorks # XP Agent (SSEA) client. L. HP StorageWorks EVA Agent(EVAA) client # and HP StorageWorks SA Agent (SAA) client) #=========================================================================== # # SMB_DISK_RESCAN=s # Default: 30 # The SMB_DISK_RESCAN variable sets the time interval (in seconds) needed # for successful disk rescan. For example. # #=========================================================================== # Common variables for split mirror. that is every 10 seconds. the HP StorageWorks U1610S B. # # SSEA_SYNC_REPORT_RATE=n # Default: 2 # During the resynchronization of mirrored disks. # # SSEA_SYNC_RETRY=n # Default: 10 # During the resynchronization of mirrored disks. # For example. http://education. The default value is 30 seconds. the status # will be displayed to monitor every 2nd check. the HP StorageWorks # XP Agent checks the status of mirrored disks for so many times as specified # by the SSEA_SYNC_RETRY variable.Module 17 Customizing # # OB2LOGENABLED=0|1 # Default: 0 (logging is off) # Setting the variable will enable logging of names of all objects backed # up during a backup session. # It is used only on Unix-like systems. The SSEA_SYNC_REPORT_RATE # variable specifies the rate of displaying the status of the mirrored disks # to the Data Protector Monitor. The SSEA_SYNC_SLEEP_TIME variable sets # the time interval (in seconds) between these status checks. The default # value is 5. # #=========================================================================== # Variables for an HP StorageWorks XP Agent (SSEA) client #=========================================================================== # # SSEA_SYNC_SLEEP_TIME=s # Default: 5 # During the resynchronization of mirrored disks. define the disk resource name as the value of the # OB2CLUSTERDISKTYPES options. # EMC Symmetrix Agent (SYMA) client. specify: # OB2CLUSTERDISKTYPES=NETRaid4M Diskset # If you are also using Veritas Volume Manager. The # default value is 2. HP StorageWorks VA Agent (SNAPA) client. # # OB2CLUSTERDISKTYPES=<resource_type_name> # Default: none # This option enables the Data Protector Inet service to # differentiate between local and cluster disk resources which use their # own resource driver and not the Microsoft resource driver. if the SSEA_SYNC_SLEEP_TIME option # is set to 5 seconds and the SSEA_SPLIT_REPORT_RATE is set to 2.P.com .00 17-26 2003 Hewlett-Packard Development Company.hp. To specify a # disk resource. # # SSEA_SPLIT_SLEEP_TIME=s # Default: 2 # During the split of mirrored disks.P.hp. . the HP StorageWorks XP Agent # checks the status of mirrored disks for so many times as specified by the # SSEA_SPLIT_RETRY variable. if the SSEA_SPLIT_SLEEP_TIME variable is # set to 2 seconds and the SSEA_SPLIT_REPORT_RATE is set to 5. The SSEA_SPLIT_SLEEP_TIME variable sets the # time interval (in seconds) between these status checks. the SSEA_MULTI_MOUNT and the SSEA_MOUNT_PATH variables are ignored # if this variable is set to 1: # Windows NT # disk images # Oracle8/9 # SAP R/3 # MS SQL Server 2000 # MS Exchange 5. # if the SSEA_MULTI_MOUNT is set to 1. The default # value is 2. # if the SSEA_MULTI_MOUNT is set to 0. # # SSEA_SPLIT_RETRY=n # Default: 120 # During the split of mirrored disks. The default value is 120. the split is aborted. # # In the cases stated below.x # # If this variable is set to 0: # # <BU_MOUNT_PATH>/<application_system_name>/<mountpoint_name_on_application_system>_<MU#> . that is every 10 seconds. this variable is set to 1 and its override is # ignored. If there is no # progress after the specified number of status checks. # # SSEA_SPLIT_REPORT_RATE=n # Default: 5 # During the split of mirrored disks. or in the # # <BU_MOUNT_PATH>/<application_system_name>/<mountpoint_name_on_application_system>. the status # will be displayed to monitor every 5th check. # directory on the backup system. the HP StorageWorks XP Agent # checks the status of mirrored disks within a check interval specified by # the SSEA_SPLIT_SLEEP_TIME variable for so many times as specified by the # SSEA_SPLIT_RETRY variable.com U1610S B. the HP StorageWorks XP Agent # checks the status of mirrored disks within a check interval specified by the # SSEA_SPLIT_SLEEP_TIME variable.Module 17 Customizing # XP Agent checks the status of mirrored disks within a check interval # specified by the SSEA_SYNC_SLEEP_TIME variable. The SSEA_SPLIT_REPORT_RATE variable specifies # the rate of displaying the status of the mirrored disks to the # Data Protector Monitor. This variable controls how the mountpoints on the # backup system are created. The default value # is 10. If there is no progress after the specified number of status # checks. where <BU_MOUNT_PATH> is: http://education. # The default value is 5. # # Note that the creation of mount points is also influenced by the # SSEA_MULTI_MOUNT and the SSEA_MOUNT_PATH variables. # # SSEA_PRESERVE_MOUNTPOINTS=0|1 # Default: 0 # Data Protector creates unique mount points and mounts them automatically # on the backup system.00 17-27 2003 Hewlett-Packard Development Company. The SSEA_SPLIT_RETRY variable sets the number # of retries for these checks. L. the resynchronization is aborted. For example. The SSEA_SYNC_RETRY # variable sets the number of retries for these checks. the application system # LDEV MU# is appended at the end of mount point path on the backup system. the variable has to be set as follows: SSEA_IR_VGCHANGE_A=vgchange a e # shared. L. # # SSEA_MULTI_MOUNT=0|1 # Default: 0 # This variable specifies. if the SSEA_MOUNT_PATH is not specified or # <SSEA_MOUNT_PATH>. U1610S B. # # In the case of a Windows 2000 Data Protector HP StorageWorks Disk Array XP client: # <Data_Protector_home>\tmp. # # By setting this variable. the integration always mounts the selected # first level mirror to the same mountpoint on the backup system.P.Module 17 Customizing # # In the case of an HP-UX or Solaris Data Protector HP StorageWorks Disk Array XP client: # /var/opt/omni/tmp. # This variable is ignored if the SSEA_PRESERVE_MOUNTPOINTS is set to 1. By default. # # SSEA_MOUNT_PATH=<first_part_of_the_mountpoint_path> # Default: none # This variable specifies. the variable has to be set as follows: SSEA_IR_VGCHANGE_A=vgchange -a s # normal (vgchange -q n -a y). if the SSEA_MOUNT_PATH is set to <SSEA_MOUNT_PATH>. the variable is not set (default) # # Use the exclusive mode to enable the instant recovery if an application/filesystem # is running in the MC/ServiceGuard cluster on the application system. how the mountpoints are created on the # backup system. # # If this variable is set to 1: # # The mountpoint for the backed up filesystem is created in the: # /<mountpoint_name_on_application_system> (HP-UX or Solaris Data Protector HP StorageWorks Disk Array XP client) # \<mountpoint_name_on_application_system> (Windows 2000 Data Protector HP StorageWorks Disk Array XP client) # <Drive_letter_on_the_app_system>: (Windows NT Data Protector HP StorageWorks Disk Array XP client) # directory or drive letter on the backup system. If this variable is set to 1. the mirrored volume groups can be activated in # the following modes: # exclusive. # Specify the first part of the mountpoint path to set this variable. this variable is not set. It controls in which mode # the mirrored volume groups on the application system are activated after # the SVOLs are synchronized to PVOLs during the instant recovery process.com . the first part of the mountpoint path is set as: # /var/opt/omni/tmp (HP-UX or Solaris Data Protector HP StorageWorks Disk Array XP client) or # <Data_Protector_home>\tmp (Windows 2000 Data Protector HP StorageWorks Disk Array XP client). # This variable is ignored if the SSEA_PRESERVE_MOUNTPOINTS is set to 1. # thus enabling every first level mirror to be mounted to its own mountpoint.hp.00 17-28 2003 Hewlett-Packard Development Company. If this variable is not # set. if the SSEA_MOUNT_PATH is set to <SSEA_MOUNT_PATH>. # If this variable is set to 0. together with the SSEA_PRESERVE_MOUNTPOINTS and # with the SSEA_MOUNT_PATH variables. if the SSEA_MOUNT_PATH is not specified or # <SSEA_MOUNT_PATH>. http://education. together with the SSEA_PRESERVE_MOUNTPOINTS and # with the SSEA_MOUNT_PATH variables. # # The variable is must be set on the application system only. how the mountpoints are created on # the backup system. # # SSEA_IR_VGCHANGE_A=vgchange -a e|vgchange -a s|vgchange -q n -a y # Default: vgchange -q n -a y # This an HP-UX instant recovery related variable. .Round Robin policy (Default). Data Protector will fail the session. this variable is set to 1 and its override is ignored.com U1610S B. # # During a Data Protector session. if the SNAPA_MOUNT_PATH is not specified or # <SNAPA_MOUNT_PATH>. where <BU_MOUNT_PATH> is: # # In the case of an HP-UX Data Protector HP StorageWorks Disk Array VA client: # /var/opt/omni/tmp. # 3 [SST] . the command/script set by the Restart application # option is always executed if set. and if the failover to # an alternate path occurs.Shortest Queue Length policy.No Load Balance policy. When several alternate # paths are available.Shortest Service Time policy. # 1 [RR] . when the HP StorageWorks AutoPath # Shortest Queue Length load balance policy is set. Refer to # "Variables for any ZDB Agent client". # Oracle8 # # If this variable is set to 0: # # <BU_MOUNT_PATH>/<application_system_name>/<mountpoint_name_on_application_system>_<Sess ionID>. # #=========================================================================== # Variables for an HP StorageWorks VA Agent (SNAPA) client #=========================================================================== # # The varaibles described in this section. with the exception of the # SNAPA_IR_VGCHANGE_A variable are used for the purpose of backward compatibility.P. HP Auto Path will dinamically balance data load between the # alternate paths to achieve optimum performance.hp. the command/script set by the Restart application # option is not executed if the command/script set by the Stop/quiesce application # option fails. # directory on the backup system. The load balance policies supported are: # # 0 [none] . # # SNAPA_PRESERVE_MOUNTPOINTS=0|1 # Default: 0 # Data Protector creates unique mount points and mounts them automatically # on the backup system. This variable controls how the mountpoints on the # backup system are created. L. # It is recommended to use the common snapshot agents variables.00 17-29 2003 Hewlett-Packard Development Company. # 2 [SQL] . # # In the case of a Windows 2000 Data Protector HP StorageWorks Disk Array VA client: http://education.Module 17 Customizing # # SSEA_ALWAYS_POST_SCRIPT: 0|1 # Default: 0 # By default. if the SNAPA_MOUNT_PATH is set to <SNAPA_MOUNT_PATH>. # # In the case stated below. # If this variable is set to 1. # #================================================================================= # Variable for an HP StorageWorks XP Agent (SSEA) and VA Agent (SNAPA) client #================================================================================= # # OB2AUTOPATH_BALANCING_POLICY=0|1|2 # Default: 1 # HP Auto Path for HP-UX provides enhanced data availability for host systems configured # with multiple host adapters and connections to a disk array. # This variable is ignored if the SNAPA_PRESERVE_MOUNTPOINTS is set to 1. the variable has to be set as follows: SNAPA_IR_VGCHANGE_A=vgchange -a s # normal (vgchange -q n -a y). # # The variable must be set on the application system only.hp.com . the variable is not set (default) # # Use the exclusive mode to enable the instant recovery if an application/filesystem # is running in the MC/ServiceGuard cluster on the application system. # #=========================================================================== # Variables for any ZDB Agent client #=========================================================================== # # ZDB_PRESERVE_MOUNTPOINTS=0|1 # Default: 0 # Creates unique mount points and mounts them automatically # on the backup system. It controls in which mode the # snapshotted volume groups on the application system are activated after the # child LUNs are synchronized to parent LUNs during the instant recovery process. http://education. the command/script set by the Restart application # option is always executed if set. # # SNAPA_IR_VGCHANGE_A=vgchange -a e|vgchange -a s|vgchange -q n -a y # Default: vgchange -q n -a y # This an HP-UX instant recovery related variable. the first part of the mountpoint path is # set as: # /var/opt/omni/tmp (HP-UX Data Protector HP StorageWorks Disk Array VA client) or # <Data_Protector_home>\tmp (Windows 2000 Data Protector HP StorageWorks Disk Array VA client). # # SNAPA_ALWAYS_POST_SCRIPT: 0|1 # Default: 0 # By default. By default.P. if the SNAPA_MOUNT_PATH is not specified or # <SNAPA_MOUNT_PATH>. # how the mountpoints are created on the backup system. # # If this variable is set to 1: # # The mountpoint for the backed up filesystem is created in the: # /<mountpoint_name_on_application_system> (HP-UX Data Protector HP StorageWorks Disk Array VA client) # \<mountpoint_name_on_application_system> (Windows 2000 Data Protector HP StorageWorks Disk Array VA client) # directory or drive letter on the backup system. # # By setting this variable. the variable has to be set as follows: SNAPA_IR_VGCHANGE_A=vgchange -a e # shared. If this variable is not set. # Specify the first part of the mountpoint path to set this variable. this variable # is not set. # If this variable is set to 1. the command/script set by the Restart application option is not # executed if the command/script set by the Stop/quiesce application option fails. # U1610S B. the snapshotted volume groups can be activated in # the following modes: # exclusive.Module 17 Customizing # <Data_Protector_home>\tmp. This variable controls how the mountpoints on the # backup system are created. L.00 17-30 2003 Hewlett-Packard Development Company. together with the SNAPA_PRESERVE_MOUNTPOINTS variable. # # Note that the creation of mount points is also influenced by the # ZDB_MULTI_MOUNT and the ZDB_MOUNT_PATH variables. if the SNAPA_MOUNT_PATH is set to <SNAPA_MOUNT_PATH>. # # SNAPA_MOUNT_PATH=<first_part_of_the_mountpoint_path> # Default: none # This variable specifies. # # ZDB_MOUNT_PATH=<first_part_of_the_mountpoint_path> # Default: none # This variable specifies. # # directory on the backup system. # if the ZDB_MULTI_MOUNT is set to 0. If this variable is set to 1. or in the # # <BU_MOUNT_PATH>/<application_system_name>/<mountpoint_name_on_application_system>. # # If this variable is set to 1: # # The mountpoint for the backed up filesystem is created in the: # /<mountpoint_name_on_application_system> (UNIX client) # \<mountpoint_name_on_application_system> (Windows 2000 client) # directory or drive letter on the backup system. where <BU_MOUNT_PATH> is: # # In the case of a UNIX client: # /var/opt/omni/tmp. # This variable is ignored if the ZDB_PRESERVE_MOUNTPOINTS is set to 1. # how the mountpoints are created on the backup system. the SessionID # is appended at the end of the mount point path on the backup system. If this variable is not set. this variable # is not set. if the ZDB_MOUNT_PATH is set to <ZDB_MOUNT_PATH>.x # # If this variable is set to 0: # # <BU_MOUNT_PATH>/<application_system_name>/<mountpoint_name_on_application_system>_<Sess ionID>. # # ZDB_MULTI_MOUNT=0|1 # Default: 0 # This variable specifies. # # In the case of a Windows 2000 client: # <Data_Protector_home>\tmp.com U1610S B. # If this variable is set to 0. # thus enabling every group of mount points for one replica storage version in # the storage pool to be mounted to their own mount points. . # Specify the first part of the mountpoint path to set this variable.00 17-31 2003 Hewlett-Packard Development Company. L. # # ZDB_ALWAYS_POST_SCRIPT=0|1 http://education. how the mountpoints are created on # the backup system.P. # This variable is ignored if the ZDB_PRESERVE_MOUNTPOINTS is set to 1. # This variable is ignored and set to 1 on HP StorageWorks Virtual Array. if the ZDB_MOUNT_PATH is not specified or # <ZDB_MOUNT_PATH>. if the ZDB_MOUNT_PATH is not specified or # <ZDB_MOUNT_PATH>. together with the ZDB_PRESERVE_MOUNTPOINTS variable. # if the ZDB_MULTI_MOUNT is set to 1. the integration always mounts the selected # group of mount points for one replica storage version in the storage pool to the # same mountpoint on the backup system.Module 17 Customizing # In the cases stated below. this variable is set to 1 and its override is # ignored. the ZDB_MULTI_MOUNT and the ZDB_MOUNT_PATH variables are ignored # if this variable is set to 1: # Windows NT # disk images # Oracle8/9 # SAP R/3 # MS SQL Server 2000 # MS Exchange 5. By default. together with the ZDB_PRESERVE_MOUNTPOINTS and # with the ZDB_MOUNT_PATH variables. if the ZDB_MOUNT_PATH is set to <ZDB_MOUNT_PATH>.hp. the first part of the mountpoint path is # set as: # /var/opt/omni/tmp (UNIX client) or # <Data_Protector_home>\tmp (Windows 2000 client). <host_object_name 2>. # Since each HSV Element Manager command increases the load on your HP StorageWorks EVA # system.. you can do it using this variable./Hosts/Backup hosts/MyHost_Port2 # # You can force the the HP StorageWorks EVA client to find # these two host objects by setting: # EVA_HOSTNAMEALIASES=MyHost_Port1.com . the command/script set by the Restart application option is not # executed if the command/script set by the Stop/quiesce application option fails. presentations. #=========================================================================== # Variables for an HP StorageWorks EVA Agent (EVAA) client #=========================================================================== # # EVA_HOSTNAMEALIASES=<host_object_name_1>. You might need to increase the default value when # your HP StorageWorks EVA system is under extreamly heavy load. the command/script set by the Restart application # option is always executed if set. # # EVA_GETOBJID_MAX_RETRY=n # Default: 10 # When creating new HSV Element Manager objects (virtual disks. # # EVA_EMAPI_RETRY_DELAY=20 # Default: 10 # Some HSV Element Manager commands that the HP StorageWorks EVA client # executes tend to fail when the target HP StorageWorks EVA system is under # heavy load. http://education. # Example: # Supposing your backup host is represented within the Element Manager by the following # two host objects: # . # See also the variable EVA_EMAPI_MAX_RETRY which sets the maximum number of retires.hp. the HP StorageWorks EVA client # searches the HSV Element Manager for host objects that match the backup host. By default the HP StorageWorks EVA # client will only search by two names: # .MyHost_Port2 # # EVA_EMAPI_MAX_RETRY=30 # Default: 10 # Some HSV Element Manager commands that the HP StorageWorks EVA client # executes tend to fail when the target HP StorageWorks EVA system is under # heavy load. When the target HP StorageWorks EVA U1610S B. With this # variable. In this case Data Protector will wait for the period set # by the EVA_EMAPI_RETRY_DELAY variable (in seconds) and try to execute the command again. # If this variable is set to 1. it is usually better to increase the delay than the number of retries.Module 17 Customizing # Default: 0 # By default.short backup host hostname (as seen on the IP network) # # If you whish to add more hostnames to the search. you can define how many times Data Protector should retry before # concluding that a command has failed. L. The # search is done by the host object name.full backup host hostname (as seen on the IP network) # .P./Hosts/Backup hosts/MyHost_Port1 # . # Default: no host object names specified # As a part of ZDB backup. etc) the # HP StorageWorks EVA client sends the creation requests to # HSV Element Manager and then collects data about the created objects. In this case Data Protector will wait for the period set # by the EVA_EMAPI_RETRY_DELAY variable and try to execute the command again.00 17-32 2003 Hewlett-Packard Development Company... With this variable you can define how long (in seconds) should Data Protector # wait between the retires.P. L.Module 17 Customizing # system is under heavy load.00 17-33 2003 Hewlett-Packard Development Company. together with the SYMA_PRESERVE_MOUNTPOINTS # variable. # # SYMA_MOUNT_R2_READWRITE=0|1 # Default: 0 # This is an HP-UX related variable. # # By default. it is ususally better to increase the delay than the number of retries. syma agent retries to lock the database for as many # times as defined by this variable. If this # variable is set to 1. Should the mirror be used for DSS or other # tasks after the backup. # See also the variable EVA_GETOBJID_RETRY_DELAY which sets the delay between the retries. this variable is not set. See also the variable EVA_GETOBJID_MAX_RETRY which sets maximum # number of retries. For backup. the volume groups and filesystems on the # Backup (R2) System are activated and mounted in read-only mode. etc) the # HP StorageWorks EVA client sends the creation requests to HSV Element Manager and then # collects data about the created objects. # Since each HSV Element Manager command increases the load on your HP StorageWorks EVA # system.hp. If it is already locked by # another process. it may happen that object creation takes some time. the first part of the mountpoint path is set as: # /var/opt/omni/tmp (HP-UX Data Protector EMC Symmetrix client). presentations. this might not be sufficient.com U1610S B. # #=========================================================================== # Variables for an EMC Symmetrix Integration client #=========================================================================== # # SYMA_LOCK_RETRY=n # Default: 15 # When syma agent interacts with Symmetrix disk array. # # EVA_GETOBJID_RETRY_DELAY=n # Default: 10 # When creating new HSV Element Manager objects (virtual disks. . # # This variable is ignored if the SYMA_PRESERVE_MOUNTPOINTS is set to 1. # If this variable is set to 0. therefore # Data Protector has to retry to collect the created object until all of them are # found. it may happen that object creation takes some time. it # is sufficient to activate the Backup (R2) System volume groups and # filesystem in read-only mode. therefore # Data Protector has to retry to collect the created object until all of them # are found. http://education. it has to # exclusively lock the SYMAPI database. how the mountpoints are created on the Backup (R2) System. the volume groups and filesystem on the # Backup (R2) System will be activated in read/write mode. # # Specify the first part of the mountpoint path to set this variable. You might need to increase the default # value when your HP StorageWorks EVA system is under extreamly heavy load. # # If this variable is not set. With this variable you can define how many times Data Protector should retry # before concluding that a command has failed. When the target HP StorageWorks EVA # system is under heavy load. # # SYMA_MOUNT_PATH=<first_part_of_the_mountpoint_path> # Default: none # This variable specifies. It is not to be used on Windows systems. devices not fully synchronized. existing write pending tracks. if the SYMA_MOUNT_PATH is set to <SYMA_MOUNT_PATH>. the SYMA_MOUNT_PATH variable is ignored if this variable is set to 1: # Windows NT # disk image # Oracle8 # SAP R/3 # # If this variable is set to 0. # # In the cases stated below. # # If this variable is set to 1.rec (Windows client) # All critical operations. # Syma agent is sequentially checking for the invalid link statuses # (before split or restore operation) until they are in the valid # condition but not for more then SYMA_SYNC_RETRY times. # # The creation of mount points is also influenced by the SYMA_MOUNT_PATH variable. # # SYMA_SLEEP_FOR_LOCK=s # Default: 30 seconds # Timeout (in seconds) between two subsequent syma agent attempts to lock # the SYMAPI database. this variable is set to 1 and its override is # ignored..Module 17 Customizing # # SYMA_PRESERVE_MOUNTPOINTS=0|1 # Default: 0 # Data Protector # creates unique mount points and mounts them automatically on the Backup (R2) System. where <BU_MOUNT_PATH> is: # # In the case of an HP-UX Data Protector EMC Symmetrix client: # /var/opt/omni/tmp.P. L. If the size of this file exceeds the maximum size. # syma agent at next successful backup.rec (UNIX client) # <Data_Protector_home>\Config\Emc\symmR1.. # # SYMA_SYNC_RETRY=n # Default: 15 # A successful split and restore operation of the links # (SRDF.rec or <Data_Protector_home>\Config\Emc\symmR2. the mountpoint for the backed up filesystem is # created in the: # <BU_MOUNT_PATH>/<application_system_name>/<mountpoint_name_on_application_system> # directory on the Backup (R2) System. starts cleaning process.com . the mountpoint for the backed up filesystem is created in the: # /<mountpoint_name_on_application_system> (HP-UX Data Protector EMC Symmetrix client) # <Drive_letter_on_the_app_system>: (Windows NT Data Protector EMC Symmetrix client) # directory or drive letter on the Backup (R2) System.00 17-34 2003 Hewlett-Packard Development Company.). # # SYMA_REC_FILE_LIMIT=n # Default: 102400 # Maximum size (in bytes) of syma recovery file: # /var/opt/omni/emc/symmR1. # This variable controls how the mountpoints on the Backup (R2) System are created. # which deletes all obsolete records in these files.. if the SYMA_MOUNT_PATH is not specified or # <SYMA_MOUNT_PATH>. # # SYMA_SLEEP_FOR_SYNC=s # Default: 30 # Timeout (in seconds) between the last unsuccessful link status check U1610S B. are logged in these file (e.g.hp.g. de-activating volume groups) # for recovery purposes. http://education.rec or /var/opt/omni/emc/symmR2.TimeFinder) requires a valid status of the links # (e. which are done on the R1 and R2 systems during the # backup (EMC). therefore there is no need to mount it # after the split. only the files residing on primary storage (disks) are # backed up. which may cause NVBDA to hang. the files are backed up regardless of their # primary or secondary storage position. # A filesystem does not have a stop I/O functionality to flush the data from # the filesystem cache to the disk and stop the I/O for the time of the split.com U1610S B. the filesystem on the Application (R1) System # is dismounted before the split and mounted after the split.hp. In such a case it is # not required to dismount the filesystem before the split. # # OB2MIGRATION=0|1 # Default: 0 # If set to 1 then the restored files are migrated to secondary storage # immediately after restoring them.Module 17 Customizing # (see SYMA_SYNC_RETRY) and next link status check. If set to 0. the components that cannot be restored will be skipped. Restore may fail. L. # # OB2OSTONLYMAG=0|1 # Default: 0 # If set to 1. # #=========================================================================== # Variables for OmniStorage integration client #=========================================================================== # # OB2OSTTIMEOUT=s # Default: 180 # Timeout (in seconds) when waiting for the OmniStorage Library Manager # volume and drive availability. Currently. # By default. the command/script set by the Restart application option is # not executed if the command/script set by the Stop/quiesce application # option fails. this variable enables backing up VxFS extent attributes # on OmniStorage VBFS.00 17-35 2003 Hewlett-Packard Development Company. it controls the I/O to the disk. # The only way to back up a filesystem in split mirror mode is to dismount the # mount point on the Application (R1) System. the filesystem on the Application (R1) System # is not dismounted before the split. . # #=========================================================================== # Variables for MS VSS integration client #=========================================================================== # # OB2VSS_DUMPTO=<pathname> # Default: none # The value specifies the behavior of the VSS integration agent in case it # is not possible to perform a regular restore. Specify # a full pathname on your system where you want these components to be dumped http://education. this feature is disabled because of bug # in BRAPI. Sometimes. # if the restore location specified in Writer Metadata Document is unavailable. for example. # If this variable is set to 1. # this is the only way to ensure that the data on the filesystem is consistent. # # SYMA_UMOUNT_BEFORE_SPLIT=0|1 # Default: 0 # If this variable is set to 1. # # If this variable is set to 0. the command/script set by the Restart # application option is always executed if set. If an application (Oracle or SAP) # runs on the filesystem.P. # # OB2OST_BACKUPEXTATTR=0|1 # Default: 0 # If set to 1. # # SYMA_ALWAYS_POST_SCRIPT: 0|1 # Default: 0 # By default. Module 17 Customizing # in case the restore fails. No scripts will be run. # # OB2OEXECOFF=0|1|2 # Default: 0 # This variable controls the execution of the object pre/post-exec scripts. http://education. # # OB2PORTRANGE=<range> # Default: no range specified (i. In the backup specification. # If set to 1. # # 1 # Pre/post-exec scripts disabled. # Note that the firewall needs to be configured separately and that the # specified range does not affect the Inet listen port. "/usr/local/scripts/my_script PAR"). use any available port) # This option limits the range of port numbers that Data Protector # processes use when assigning listen ports dynamically. the scripts should be specified # with complete path and parameters included # (e. the # pathname is set as /tmp (UNIX) or <Data_Protector_home>\tmp (Windows).e. # # 2 # Pre/post-exec scripts location will be restricted to /opt/omni/lbin # (HP-UX or Solaris systems). # # OB2PORTRANGESPEC=<range specifications> # Default: no ranges specified (i.00 17-36 2003 Hewlett-Packard Development Company. # This option is typically set on the Cell Manager system and/or the # Media Agent system when components of the cell are located on both sides # of a firewall.g. # Script location is always restricted to # /opt/omni/lbin (HP-UX or Solaris systems). # By default. # # OB2REXECOFF=0|1 # Default: 0 # This variable controls the execution of a remote pre/post-exec (for # the entire backup specification) on a particular client. L.g. If this variable is not set. # In the backup specification there should be no path specified for # the script (e. /usr/omni/bin (other UNIX systems) or # <Data_Protector_home>\bin (Windows systems) directory only. You have to specify a fully qualified path of an existing # directory. this variable is not set. This variable has precedence over the paths specified by the # postfix parameter.com . # It can be set to the following values: # # 0 # Pre/post-exec scripts can be located in any directory on the object's # system. use any available port) # This variable limits the range of port numbers that specific U1610S B.hp. # A new variable named OB2PORTRANGESPEC provides more control over the # ranges and helps keep their sizes smaller. the client refuses to execute the remote pre/post-exec script. # #=========================================================================== # Variables which can be used for any agent client #=========================================================================== # # OB2DBGDIR=<pathname> # Default: none # This variable is used to change the location of debug files on a per # system basis.P. /usr/omni/bin (other UNIX systems) # or <Data_Protector_home>\bin (Windows systems) directory on the remote client. and the backup # will continue. "my_script PAR1 PAR2").e. # Refer to "Firewall Support" in HP OpenView Storage Data Protector Administrator's # Guide or in online help for additional information. L. # # OB2RECONNECT_ACK=s # Default: 1200 # Timeout (in seconds) before an agent gives up waiting to acknowledge a # message from the session manager. .P.X clients that have both.hp.com U1610S B. # Note that the firewall needs to be configured separately. in case the following error # occurs during the backup: # Cannot allocate/attach shared memory (IPC Cannot Allocate Shared Memory Segment) # System error: [13] Permission denied) => aborting # #=========================================================================== # # http://education. # # OB2SHMEM_IPCGLOBAL=0|1 # Default: 0 # This option should be set to 1 on HP-UX 11.Module 17 Customizing # Data Protector processes use when assigning listen ports dynamically. the # Disk Agent and the Media Agent installed. # # OB2RECONNECT_RETRY=s # Default: 600 # Timeout (in seconds) before an agent should give up trying to reconnect # to the session manager.00 17-37 2003 Hewlett-Packard Development Company. # Refer to "Firewall Support" in HP OpenView Storage Data Protector Administrator's # Guide or in online help for additional information. # This option is typically set on the Cell Manager system and/or the # Media Agent system when components of the cell are located on both sides # of a firewall. P.00 17-38 2003 Hewlett-Packard Development Company.hp.com . http://education. L.Module 17 Customizing U1610S B. Lab Exercises – Appendix A http://education.hp.com A-1 U1610S B.00 2003 Hewlett-Packard Development Company, L.P. Appendix A Hands-on Labs Lab 3: Installation Objective: The objective of this lab is to install and configure the cell manager and clients. http://education.hp.com A-2 U1610S B.00 2003 Hewlett-Packard Development Company, L.P. Appendix A Hands-on Labs 3–1. LAB: Installation Planning Directions Objective: To become familiar with installing a Data Protector cell and configuring clients. Small teams allow you to configure a multi-system cell. Teaming is optional, but if chosen, teams are best with two members. The ideal cell for classroom use would be to have one Windows 2000 system per student and an HP-UX system to be shared. The objective of this lab is to create a Data Protector Cell, with one system being the Cell Manager and Installation Server and the others being client systems and, optionally, installation servers. If you have been provided with a Windows-based system in addition to or instead of an HP-UX system, you can perform the labs on either platform or both. Pre-installation Activities Plan your cell. a. b. c. d. Decide which system will be the Cell Manager. Decide which systems will be disk/media agent clients. Decide which systems will be installation servers. List the systems to be included in the cell, and check the agents to be installed there. Document the systems that will become part of your cell (ask your instructor): Cell Manager: Unix Installation Server: Windows Installation Server: Unix Client(s): Windows Client(s): Check to see that all of your systems meet the prerequisites for disk space, operating system version, RAM, etc. It is extremely unlikely that your systems do not meet them, but it is good practice to check anyway. 1. For the HP-UX and Windows 2000 Cell Managers it is highly recommended that before starting the installation, you create a separate file system for <OMNIVAR>/db40. For the classroom environment, 500 MB should be sufficient. On HP-UX, create a filesystem and mount it to /var/opt/omni/db40. http://education.hp.com A-3 U1610S B.00 2003 Hewlett-Packard Development Company, L.P. Appendix A Hands-on Labs On Windows, create a partition and use a driver letter path, c:\program files\omniback\db40. (Create this directory before creating the partition.) Why do you think this is recommended? 2. Verify that port number 5555 is available on all systems. Try the telnet client with the port option as follows: telnet <hostname> 5555 (This command should return nothing.) For Windows, the registry may be modified after the installation if port 5555 is already in use. For Unix, check the /etc/services file . 3. Verify that all systems to be included in the cell use the same IP name lookup service. For UNIX, verify that DNS is the preferred lookup service; examine the contents of the /etc/nsswitch.conf file (on all systems). Verify that DNS precedes FILES, as below: hosts: dns [NOTFOUND=continue] files nis 4. Verify that the name server configuration uses the HP Education name server. (Ask your instructor for the specific IP address and search entries to use for this domain) cat /etc/resolv.conf 5. For Windows, verify that the same DNS configuration as the Unix systems is in use. (Use the Education site name server) 6. Proceed to the Cell Manager Installation labs which follow; choose either HP-UX or Windows or both depending upon systems availability. http://education.hp.com A-4 U1610S B.00 2003 Hewlett-Packard Development Company, L.P. Appendix A Hands-on Labs 3–2. LAB: Installation — HP-UX Cell Manager Objective: To install Data Protector software on the system you have chosen to be the Cell Manager You will install from the following software depot (provided by your instructor): Source Host Name: ________________________________________ Source Depot Path: _______________________________________ Perform the following as the root user: 1. Create a “snapshot” of the current disk space to determine how much space is consumed by the installation. bdf > /tmp/before_dp.txt 2. As the root user, run swinstall to install Data Protector. Change the source host and depot to the one supplied by the instructor. Data Protector is in a product bundle by default. For example: B6960AA HP OpenView Data Protector You are required to install the full product. However, now is a good opportunity for you to drill down into the product to see all the available Data Protector file sets. a. Start the installation by selecting: Actions: Mark for Install b. Select: Actions: Install (analysis) (Analysis Phase begins.) c. When you see Ready, click OK. d. Click Yes to begin installation. e. After installation, click Done when ready. f. Exit the swinstall program: File: Exit Post Installation — Cell Manager 1. Check for successful installation of software: Use swlist to verify that Data Protector file sets have been installed: swlist -l fileset DATA-PROTECTOR http://education.hp.com A-5 U1610S B.00 2003 Hewlett-Packard Development Company, L.P. Appendix A Hands-on Labs 2. Verify the amount of disk space consumed by the installation. (notice the changes to /, /opt, /var) cat /tmp/before_dp.txt bdf / change: /var change: /opt change: 3. The processes, mmd, rds, and crs, should currently be running: crs is the cell manager daemon. mmd is the media manager daemon. rds is the Raima Velocis (database) server. 3. Check to see if all the Data Protector processes are running: ps -ef | grep omni or /opt/omni/sbin/omnisv -status 4. Check /etc/services for the service, omni, port 5555: grep 5555 /etc/services (You should now see an entry for this port number.) 5. /etc/inetd.conf should have an entry for the service, omni: grep omni /etc/inetd.conf (You should see an entry for the service, omni.) 6. Data Protector directories: /opt/omni, /etc/opt/omni, /var/opt/omni should have been created: ls -ld /opt/omni /etc/opt/omni /var/opt/omni 7. The installation placed a configuration file in /etc/rc.config.d and a script in /sbin/init.d called omni. Look at these files. What commands can be used to start and stop the Data Protector daemons? Start commands: __________________________________________________ Stop commands: __________________________________________________ http://education.hp.com A-6 U1610S B.00 2003 Hewlett-Packard Development Company, L.P. Appendix A Hands-on Labs 8. Log off and then log on again as root. This will refresh your profile, which has been modified by the Data Protector installation. (PATH and MANPATH variables are usually set during login using the /etc/PATH and /etc/MANPATH, both are modified by Data Protector). 9. Start the Data Protector GUI: /opt/omni/bin/xomni & What information do you see here? 10. Exit the GUI: File -> Exit http://education.hp.com A-7 U1610S B.00 2003 Hewlett-Packard Development Company, L.P. Appendix A Hands-on Labs 3–3. LAB: Installation — Windows Cell Manager Directions Hardware permitting, you can complete this lab which will demonstrate the installation process of a Cell Server and Client on the Windows platform. If you do not have a Windows system available, the instructor can demonstrate this to the entire class instead. Software source system: Software source path: 1. Obtain from the instructor the location of the Data Protector software. This may be a network share or it may be copied to a partition on the local system. 2. Ensure you are logged on as Administrator or have Administrator permissions. 3. Change to the product directory or share name. 4. Execute the Autorun from the product depot or CD-ROM. 5. Select Install Data Protector. (this may require an update to the Microsoft Installer, which will require a reboot to be able to continue) 6. Follow the installation wizard to install Data Protector. Be sure to select the Cell manager as the choice to install. Other options will be the client, or installation server. Verify the default location for the installation, C:\program files\Omniback (notice that Omniback is still used by Data Protector for support of previous versions) Installation Prompt screens: License Agreement: Customer Information: Installation Type: User Account: Custom Setup: Ready to Install Accept the licensing agreement Fill in a user for the registration (any user will do for now) Select the Cell Manager to install Enter the Administrator login name and password Select to add the Manager of Managers User Interface http://education.hp.com A-8 U1610S B.00 2003 Hewlett-Packard Development Company, L.P. Appendix A Hands-on Labs 7. When complete, you will be asked if you want to start using Data Protector. Click “NO.” 8. Exit the Autorun executable. 9. Look at the following: The directory structure (default C:\Program files\Omniback). Be sure to locate the config and db40 directories, as well as the bin, command directory. 10. Verify that the Data Protector services have been added: Use the Windows 2000 Computer Management,right click on My Computer, then select manage, Open the Services and Applications tab, select services. Look for the three Data Protector services; ensure they are started and configured for automatic startup using the system account. 11. Using regedit (Start -> Run “regedit”), look at the following registry hives (do not make any changes): HKEY_LOCAL_MACHINE\SOFTWARE\HewlettPackard\OpenView\OmnibackII\Site HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\omniback_ crs HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OmniInet HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Velocis 12. Run the Data Protector GUI: Start->Programs->HP OpenView Storage Data Protector->Data Protector Manager Take some time to look around the GUI. See if you can find some of the controls that you used in the Motif GUI earlier. When finished, exit the GUI. If the system is not to be the primary cell manager, then uninstall Data Protector and reinstall just the client. While installing the Cell manager and client, you may optionally add or remove the installation server at the same time. The selection to add/remove the installation server will be available in the Custom Setup screen during the installation process. 13. Uninstall Data Protector from your windows system. (Start -> Settings -> Control Panel (Add/Remove Programs) Select Data Protector, and remove it. http://education.hp.com A-9 U1610S B.00 2003 Hewlett-Packard Development Company, L.P. Appendix A Hands-on Labs 14. Run setup.exe (or Autorun)again, but this time, install the system as a client and add the Installation Server. 15. When prompted for the Cell Server name, you have two choices: a. Leave the field empty, this will allow the client to be imported from the cell manager (preferred). b. Enter the fully qualified name of the cell server (requires the use of DNS as the lookup service). This should instruct the Cell Server to “import” your system as a client. (Note, if you enter the cell manager name incorrectly, you will may have to modify the registry to change it, or uninstall Data Protector and start over. 16. From the Cell Manager, start the GUI and go into the Clients list to verify that the Windows system has been imported. If not, import it manually. http://education.hp.com A-10 U1610S B.00 2003 Hewlett-Packard Development Company, L.P. Appendix A Hands-on Labs 3–4. LAB: Installation — HP-UX Installation Server (Optional) As the root user run swinstall. 1. Change the source host and depot to the one supplied by the instructor, and change the software view to products. 2. Drill down (double-click) into the Data Protector Product. DATA-PROTECTOR A.05.10 HP OpenView Storage Data Protector 3. This will explode to a listing of the file sets contained within the full product. In the list of file sets, select the Installation Server file set. OB2-IS A.05.10 HP OpenView Storage Data Protector Installation Server 4. Now start the installation. Actions: Install (analysis) (Analysis Phase begins). 5. When you see Ready, click OK. 6. Click Yes to begin installation. 7. After installation, click Done when ready. 8. Exit the swinstall program: File: Exit Post Installation — HP-UX Installation Server Check for successful installation of software. 1. Use swlist to verify that Data Protector file sets were installed. swlist -l fileset DATA-PROTECTOR 2. Check /etc/services for the service, omni, port 5555. grep 5555 /etc/services (You should now see an entry for this port number.) /etc/inetd.conf should have an entry for the service, omni: grep omni /etc/inetd.conf (You should see an entry for the service, omni.) Data Protector directories: /opt/omni, /etc/opt/omni, /var/opt/omni should have been created: ls -ld /opt/omni /etc/opt/omni /var/opt/omni http://education.hp.com A-11 U1610S B.00 2003 Hewlett-Packard Development Company, L.P. Appendix A Hands-on Labs 3–5. LAB: Configuring the Installation Server Before completing this lab, you must have already installed the cell manager and an installation server to a second system. At this stage the Cell Manager system does not know that the Installation Server(s) exist. In order for the Cell Manager to see the Installation server, you must register it on the Cell Manager. 1. Before you configure the Installation Server, look at the contents of the following file on the Cell Manager: <OMNICONFIG>/cell/installation_servers What does it contain? 2. Now you can continue with the configuration procedure: The following steps must be performed on the Cell Manager system to configure the Installation Server into the Cell. Start the Data Protector GUI. Add the Installation Server. At the top of the GUI, select Clients from the pull down list to switch to the clients context. Highlight “Installation Server” (single click with the right mouse button) to display the pop-up menu. Choose Add Installation Server. Enter the hostname of the system containing the installation server software. (It may be another cell manager containing an installation server.) The Cell Manager will now connect to the system to verify that it is indeed an Installation Server, and if it’s okay will configure it. Import all of the Installation Servers that you configured (Windows and Unix) Exit the GUI. 3. Now, look at the config file that you checked previously: installation_servers What does it contain now? http://education.hp.com A-12 U1610S B.00 2003 Hewlett-Packard Development Company, L.P. Appendix A Hands-on Labs If you have both systems listed, congratulations! You have just configured your Installation Server. Installing Clients (Optional) You must have more than one system in your cell that is not the cell manager or installation server to proceed. 1. Decide which systems have disks to be backed up (Disk Agent clients). Review your list from the beginning of this exercise. 2. Decide which systems have backup devices to be used by Data Protector (Media Agent clients). Review your list from the beginning of this exercise. 3. Install the appropriate agent software on systems in your cell: Cell Console Disk Agent Media Agent a. Start the Data Protector GUI. b. Add the host and choose the components: c. Select Clients from the pull down list to switch to the client context. d. e. f. g. Right click on Clients in the list below Data Protector Cell From the pop-up menu, select Add Clients. Select the platform of the target machine: (UNIX, or Windows NT) Select an appropriate installation server (This changes by default.) Select Next> h. Enter hostnames in the Name field; select Add to add the names to the client systems list (when adding Windows clients using the Windows GUI, the Microsoft Windows Network may be browsed to select clients to add to the cell) i. Repeat this for each hostname. j. Click Next> , when finished entering hostnames. k. Select the components that you want installed from the Components tab; select an appropriate user name from the Options tab (For Windows, this should be the domain admin, for UNIX, the root user.) The Options tab also allows for an alternate to the default installation directory. The Customize for each client separately button is self explanatory. l. Select Finish when ready to install the agents. http://education.hp.com A-13 U1610S B.00 2003 Hewlett-Packard Development Company, L.P. Appendix A Hands-on Labs 4. Verify that the appropriate agents are installed. Using the client’s context of the Data Protector interface can perform this. Select a host from the list of configured hosts. The properties will automatically be shown. What other information can you get about each host (client)? 5. On the Cell Manager (Installation Server) check the contents of the install log text files; check for errors. (Depending upon the system, not every log will exist.) HP-UX logs: <OMNIVAR>/log/IS_install.log Windows Logs: <OMNIVAR>\log\IS_install http://education.hp.com A-14 U1610S B.00 2003 Hewlett-Packard Development Company, L.P. Appendix A Hands-on Labs 3–6. LAB: Patching the Installation Server/Cell Manager Before completing this lab; verify with your instructor that access to the HP Openview Support Web is available from the classroom. The following procedure is demonstrated for a Windows Cell Manager/Installation Server. Objectives: • practice the update of the Cell Manager and or Installation Server within the cell • practice using the patch check functions of Data Protector Procedure: 1. Create a new temporary directory to hold the downloaded patch files (some may consume a large quantity of disk space): Windows: C:\temp\DP51_Patches UNIX: //tmp/DP51_Patches 2. Open the web browser and access the HP OpenView Support Web site: http://support.openview.hp.com Select the “patch downloads” as shown below. http://education.hp.com A-15 U1610S B.00 2003 Hewlett-Packard Development Company, L.P. Appendix A Hands-on Labs 3. Select the Data Protector product from the list of available OpenView products: (see below) 4. Select the Operating System that is to be patched (HP-UX, Windows) http://education.hp.com A-16 U1610S B.00 2003 Hewlett-Packard Development Company, L.P. Appendix A Hands-on Labs 5. Browse the available patch selections for the necessary/desired patches; review the “view path full text” to determine applicability to your environment as well as patch dependencies; then download the patch(s). 6. Select the download patch now link; then save the patch to the local disk. 7. Specify the save location as the directory created in step 1 of this procedure. http://education.hp.com A-17 U1610S B.00 2003 Hewlett-Packard Development Company, L.P. com A-18 U1610S B. . look for the section entitled “Special Installation Instructions”. then execute them one at a time to install them. Executing the patch file.exe. Scroll through the dialogue to note any special requirements prior to completing the patch installation. 9. Continue downloading all of the necessary patches.Appendix A Hands-on Labs 8. shown below: http://education.P.hp.00 2003 Hewlett-Packard Development Company. in this case DPWIN_00038. presents the following dialogue: 10. L. .Appendix A Hands-on Labs 11.00 2003 Hewlett-Packard Development Company. Selecting Next (from the screen above) starts the Install Shield Wizard.P.com A-19 U1610S B.hp. select Next to being the installation process (shown below): http://education. L. http://education. as shown below.00 2003 Hewlett-Packard Development Company.exe as well as the original files that were replaced by the patch (see below). This directory will contain the executable named PatchUninstall.hp. L. Be sure to stop all sessions before continuing: 13. You will be prompted to save the original files. The installation process verifies that no sessions are currently running.P. to allow the patch to be un-installed later. The default directory for the saved files is: C:\Program Files\Omniback\Patched_files.Appendix A Hands-on Labs 12.com A-20 U1610S B. . at least one GUI session was connected to the Cell Manager (dbsm is running). (shown below are the properties for the Cell Manager. the properties for the Installation Server is essentially the same screen) http://education. After the patching process completes.00 2003 Hewlett-Packard Development Company.P.hp. .Appendix A Hands-on Labs 14. start the DP GUI and verify that the patches were installed on the Cell Manager as well as Installation Server. L.com A-21 U1610S B. . execute the “omnicheck –patches” to see the listing. after verifying that the Installation Server and Cell Manager are successfully patched. upgrade the clients to distribute the patches to other systems in the cell. Finally. (see below) 16.Appendix A Hands-on Labs 15. L.hp.com A-22 U1610S B. http://education.P.00 2003 Hewlett-Packard Development Company. Data Protector also provides a command line interface to verify the installation of patches. How could you use this command to perform the import/export functions you have just performed via the GUI ? http://education. you will find programs starting with omni.Appendix A Hands-on Labs 3–7.P. L. .00 2003 Hewlett-Packard Development Company.hp. you will find several programs starting with xomni and omni. 2. you may want to add the <OMNIHOME> directory to the environment variables. On HP-UX. Look in <OMNIHOME>/bin for the Data Protector programs. Try the following commands from the command line (DOS prompt): omnicellinfo –cell omnicc –query NOTE: On windows.com A-23 U1610S B. Read the command reference (man page) for the omnicc command. so they are more convenient to use 3. On Windows. LAB: More on the Data Protector GUI and Commands 1. The programs that begin with omni… make up the Command Line Interface to Data Protector. .P. L.com A-24 U1610S B.00 2003 Hewlett-Packard Development Company. http://education.Appendix A Hands-on Labs Lab 4: Data Protector Basics Objective: To introduce the main features and functions of Data Protector.hp. LAB: Data Protector Basics Objective: To create a standalone logical device. Prepare to perform a restore: If you want to restore a file. 5. Remove the following files prior to the restore: http://education. Execute the backup in “Full” mode. Perform the required steps for backup (including all the checks listed in the slides). back up a small file system: /tmp /home / (but only the /etc sub-directory) On Windows. 2. Remove your tape from the tape drive after the backup job has completed. You should: • Configure a standalone logical device. L.Appendix A Hands-on Labs 4–1. 1. (Suggestion: at this time is to keep the backup simple. initialize a tape and perform a backup of some objects on the Cell Manager. include all of the following into a single backup specification. • Create a backup specification and save it as “backup 1” 3. you will have to delete something (be sure not to delete any critical files yet). .00 2003 Hewlett-Packard Development Company. Use the procedures presented in this module to perform a backup of some data on your systems within your cell.hp. • Initialize at least one tape into the “Default DDS” media pool. 4. If you have both Windows and UNIX clients in the cell. then restore a single file. back up the following: c:\winnt\system32\drivers\etc c:\temp c:\winnt\temp c:\Inetpub c:\Perl.P. On HP-UX.com A-25 U1610S B. c. select each session for details. Schedule the same Backup Specification (from steps1-2) to execute tonight at 11:00 PM as a full backup.com A-26 U1610S B. From the “Reporting” context. HP-UX: rm –r /home/user1 rm –r /tmp/* b.hp. select each tape listed. From the “Device & Media” context open the Default DDS pool. . examine the contents. b. execute the same report as in the previous step.” 8. Windows (use Windows Explorer): delete c:\Perl delete c:\Inetpub 6. Then examine the Backup results area columns named “Scheduled” and “Backup Type. d. L. be sure to verify that your backup session completed successfully. and verify the Objects (use the Objects tab). From the “Internal Database” context.Appendix A Hands-on Labs a. open the sessions folder. From the “Reporting” context. http://education. Perform the required steps for the restore of a file from your previous backup making sure to create and respond to the mount request (as a result of the tape removal) 7. accept all of the default parameters. Verify that the backup is correctly scheduled by selecting the Filesystem tab under Backup Specifications in the Backup context. When you come in tomorrow. Proceed as follows: a. Schedule this backup to run at least two hours after your previous backup.P. 9. execute the “List of Backup Sessions” report from the “Sessions in Timeframe” folder. e. select “Web Reporting” from the Actions menu. Create another backup specification for any part of your cell.00 2003 Hewlett-Packard Development Company. “Tasks” tab. From the “Restore” context open the Sessions and Objects folders. 00 2003 Hewlett-Packard Development Company. http://education. . L.P.Appendix A Hands-on Labs Lab 5.com A-27 U1610S B.hp.6 & 7: Device & Media Management Objective: The objective of this lab is to learn how to use the device and media management features of Data Protector. When Data Protector is first installed. pools. You will be prompted. DDS. add a few locations.P. 9. a.Appendix A Hands-on Labs Lab 6-1: Media Management Objective: The objective of this lab is to learn how to use the media management features of Data Protector. We want to keep only the default pools for the media types that we will be using within our cell. “Do you want to delete media pool xyz?” Click Yes. . you will keep only default DLT . and switch to the Devices and Media context. c. (for example.00 2003 Hewlett-Packard Development Company. select: Edit -> Add -> Media Pool http://education. a. proceed as follows: 7. 10. “Fire Safe”). Using the Location field. including: • • • • • Creating a media pool Defining media pool properties Adding media to a pool using initialization Media pool operations Command line interface It is assumed that you have configured a standalone device for your use from the “Getting Started” module. Start the Data Protector GUI. There is one default pool for each media type. it provides you with a set of default media pools. From the menu bar. Right-click on the pool you want to remove. 9. you cannot delete pools en masse. In the Device & Media Management context window: Edit-> Locations b. one at a time. Typically. so you will need to repeat this process for each of the unwanted pools. 8. Unfortunately. This standalone device will be used during this lab. 1.hp. Select Delete from the pop-up menu. Examine the contents of the <OMNICONFIG>/vault_locations file. Otherwise. “Device Repository”. the list will be too cluttered. Create your own media pool for test purposes. L.com A-28 U1610S B. Create some predefined Vaulting Locations. and File. Start by deleting all the pools that you will not be using. Open the list of media pools in the Scoping Pane. Is this file modifiable? 4. “Offsite Storage” . 2. b. c. http://education. You will now be presented with the Media list in the Results area. L. one for full backups and the other for incremental backups. Using the GUI.com A-29 U1610S B. yourname_inc. Select the Folder labeled “Media” b. Use the Data Protector command line interface to get information about your new media pools: • • • omnicellinfo -mm omnimm -list_pool or omnimm -show_pools -detail omnimm –list_pool <poolname> 7. Create two further media pools. (Or. use the pop-up menu by right clicking on the media pool name and select Format. 5. a. You are now presented with the Media Pool Editor window..hp. Open the test media pool by double clicking on it. Initialize some media (use the Standalone device created in Module 4) and add them to your media pools as follows: a. and set the media allocation policy to use Append Incrementals Only.Appendix A Hands-on Labs b. use <yourname_full> for the pool name and set the media allocation policy to Non-appendable. For the incremental pool use <yourname_inc> for the pool namd.. "A loose and appendable test pool" The media type for this pool.00 2003 Hewlett-Packard Development Company. Your pool will now be added to the list of configured media pools. 6. For the full backup pool. because you have no media in the pool.. The list will be empty.. Leave these fields with the defaults. Use Yourname_test.) Appendable (the default). (The default is DDS.P. . Loose (default). Call these media pools yourname_full. d. From the menu bar choose: Actions -> Format. Load a tape into your standalone device. Complete the options as follows: Pool Name Description Media type Media Usage Policy Media Allocation Policy Media Condition Factors The name you want to call your Media Pool. you will see a dialog box telling you “1 out of 1 media was successfully initialized. Set this to Default Medium Size Select Finish. Repeat this process to initialize the remainder of your media. 12. you will see the media agent start to perform the initialization of the media. this procedure will fail. select: Move to Pool A list of media pools of the same media type will be selectable in a pull down list. Complete the format options as follows: Device Medium Description Location Eject after Operation Force Operation Choose an appropriate logical device Select Automatically generate Select a vaulting location or leave the field empty Select eject if you want your media to eject from the drive after it is initialized. look at what information is available for the media and media pool. Try moving media from one pool to another: Select a single media by right clicking on it. etc. If the media that you are trying to initialize has been used before. 10.hp. then move it back. Select the destination media pool by clicking on it. Leave it disabled to start.Appendix A Hands-on Labs 9. select: Properties What can be modified? b. Your newly initialized media will now appear in the Media List. .00 2003 Hewlett-Packard Development Company.e.P. tar. fbackup. See what can be changed after the media is initialized: a. In the message section in the Results Area. but try to initialize at least one of your media using the command line interface omniminit command. Change the location. If the media is a recognized format. then press Finish. then click Apply.com A-30 U1610S B. Select a single media by right clicking on it. and Data Protector recognizes the format.. http://education. When you have initialized all your media. (media properties) 11. (i. Upon completion of the initialization. enable it only if the initialization fails.) force will be required. and you will need to repeat the process to specify the Force option. The list of all media pools will be displayed in the Results Area. from the list.” Click OK. Then. L. Then. Check that the media has been moved to the pool as you requested. from the pop-up menu select: Export You will be asked to verify that you want to export the media. Import the media back into your pool: Select your media pool from the Scoping pane. .) In the Results Area screen you will see the scan take place.hp.com A-31 U1610S B. Try the export and import operations: Select a single media by clicking on it. http://education. from the pop-up menu select: Import Select the device where your media is loaded. What does Export actually do? (Read the Online Help). Then scan the media using a logical device to check its status: Open the Devices list in the Scoping pane Select the logical device you want to use. (leave all of the other options to their default settings) Select Finish. Make sure that the media you just exported is loaded in one of your devices.00 2003 Hewlett-Packard Development Company. click OK. and click Next. What does Foreign mean? 15. from the pop-up menu select: Scan (Do not eject after scan.P. L.Appendix A Hands-on Labs 13. Then. leave the other options unchanged. The media type will show Data Protector Foreign. 14. bat to <OMNIHOME>/bin/DDS_mount. Unless you want to re-initialize all of your existing tapes. Copy the mount notification template to DDS_Mount. LAB: Logical Device Configuration—Standalone Objective: The objective of this lab is to learn how to configure a standalone tape device.Appendix A Hands-on Labs 6–2. Standalone 1. http://education.P. 5.sh to /opt/omni/lbin/DDS_mount. What are the default block and segment sizes? What is the default concurrency? 4. LTO) may be substituted.bat) 6. L.00 2003 Hewlett-Packard Development Company.hp. DLT. Configure a standalone DDS drive. copy /opt/omni/lbin/Mount. What Data Protector device type would you use to configure a single DDS/DAT drive? 2. Modify the device options so it will use the new DDS script after 15 minutes of waiting for a tape to be loaded.com A-32 U1610S B. 3.sh) On Windows copy <OMNIHOME>/bin/mount. (On Unix. do not change the block size for the devices after the media is initialized. . any standalone type (File. If a DDS is not available. Instructions for Jukebox 1 1. at least 1GB is recommended. or Device Manager on Windows) create a new partition and put a filesystem on it. for performing more sophisticated backups and automated media copy functions. Name them library_1 and library_2 3. LAB: Logical Device Configuration—File Jukebox (Recommended) File Jukebox Objective: create two multi-drive file jukeboxes.hp. but the file0n will be created by Data Protector File_Jukebox demonstration device <your_host> Jukebox <path>/library_1/file01-0n * create as many files as you have disk space. Note: this device type is a bit unusual. assume each will be 110 MB (create http://education. In order to perform this exercise you will need a substantial amount of free disk space. Configure the logical device: (substitute <path> with the mount point for your partition). L. 2. This space could be on either a Unix or Windows system with the Data Protector media agent installed. Create a directory under /jukebox (c:\jukebox) for each jukebox. but you will be able to exercise Data Protector functionality that you may otherwise not be able to test with standalone devices. if using a driver letter path. The first jukebox may contain more slots than the second and will be used primarily for load balanced backup. Ask your instructor about available disk space. Create a “file” media pool using any unused name. as it is not common to be used in a production environment. If the /jukebox filesystem does not exist complete the following. accept all of the default options. if so. The second jukebox will only be used to demonstrate AMO functions. or skip to step 1 if the /jukebox already exists: Using the Operating system tools (SAM on HP-UX. Device name : Description: Host Name: Device type: Set of Files/Disks: (note: the <path> directory must exist.00 2003 Hewlett-Packard Development Company. Note: In some cases the /jukebox filesystem may already exist. such as load balancing. verify its capacity and use it in place of <path> below. or just a drive letter. For Windows 2000 this may be a drive-letter-path. first create a new empty directory such as c:\jukebox.Appendix A Hands-on Labs 6–3.com A-33 U1610S B. use the volume manager and create a new mount point called /jukebox. .P. On Unix. Select all of the slots.P. (more if you would like) Drive-1 Drive Name: file_drive1 Description: virtual drive ClientName: <your_host> Pool Name: <your choice> Concurrency: 2 Drive-2 Drive Name: file_drive2 Description: virtual drive Host Name: <your_host> Pool Name: <your choice> Concurrency: 2 5. the Actions -> Format… Logical Device for Initialization: Library Drive: file_drive1 Media Pool: <your_choice> Media Initialization Data: Automatically generate (instead of description) Location: Device Repository (or a vaulting location) Medium Size: http://education.hp. then Actions -> Scan… 7. Select all of the slots.Appendix A Hands-on Labs Media type: 20 or more slots if you have space) File 4. Expand contents of the newly created file_jukebox device in the Scroping Pane.00 2003 Hewlett-Packard Development Company. 6. the properties will be displayed in the Results Area. Create at least two “virtual” drives for the Library/Jukebox. Select all of the slots in the Results Area (use Shift+Mouse. What Format does Data Protector recognize for the media that is in the file slots? 8. or Control+Mouse). . Scan all of the media slots in the jukebox.com A-34 U1610S B. Initialize all of the file media into the an appropriate “file” pool. L. Select the "Slots" component. will be done by AMO if necessary) d. only 3-4 media slots are needed to demonstrate AMO.P.Appendix A Hands-on Labs Specify (instead of Default): Note: <MB> (valid range:10-4096) be sure to allow for space in the partition for the second set of files to be used by jukebox-2. b. use the Edit menu and select: Edit -> Add -> Scheduled Media Operation… b. Apply the change to the specification. change the destination to use one of the drives in Jukebox_1. Create a second file jukebox. LAB: Preparation for Automated Media Copy Objective: create additional devices to be used for AMO to be configured with backup. 1. Media Operation type: AMO_lab1 Media Copy (no other choice) http://education. Using the backup specification created for module 4 that was named “backup_1”. . Media Operation name: c. with the following exceptions (unless you have sufficient disk space for more): a. Assign the drives in the new jukebox to the same pool as the original jukebox. 1.00 2003 Hewlett-Packard Development Company. multiple drives within the same jukebox will suffice) 1. Follow the procedure used previously for configuration of the file jukebox. Requirements: two library devices of the same media type and media capacity. 6–5.com A-35 U1610S B. 6–5. Requirements: two library devices of the same type (we will assume file jukeboxes and use drives from each jukebox.hp. L. LAB: Automated Media Copy Objective: create a scheduled Automatic Media Operation using Media Copy. Execute the backup interactively. Create only a single drive jukebox c. 6–4. Use <path>/library_2/file01-nn as the path/names for the slots. Create a scheduled Media Copy specification: a. LAB: Preparation for Automated Media Copy Objective: perform a simple backup using Jukebox_1 as the destination. Format the media to the same size as the original file jukebox media (optional. 2. From the Device & Media context. use two file jukeboxes (or multiple drives in the same jukebox). Select the “All backup specifications” option (default) i. Media Condition: Good j. o. Hint: Open the “Sessions” container to see the session ID’s. Select Ok to the pop-up. Finish 2. Select (within the media pool) the destination medium used for the replication.hp.com A-36 U1610S B. L. Open the Monitor context of the DP GUI. end of lab. select the AMO_lab1 specification. Media Protection: Any k.Appendix A Hands-on Labs d. Started within 1 hour g. 5. open the Automated Operations container.P. open the media pool containing the copied media. watch for the AMO session to start. Examine all of the tabs in the results area to view the possible values for the media operation. 3.amcs” and is an ASCII file. Select Relative Time frame (media used within the last 1 hour) f. use notepad or another text editor to view the file from the <OMNICONFIG>\amo directory. After the AMO completes. Protection for target media: “Same as original” n. Examine the schedule for the scheduled media copy. Select the Copies tab to determine the name of the copy. 9. Continue monitoring the progress to completion. . http://education. The file should be named “AMO_lab1. Eject media: “Do Not Eject Media” m. 7. there is a new button labeled “Original”. use notepad or another text editor to view the file from the <OMNICONFIG>\amoschedules directory. Switch the context to Devices & Media. Select the source and target drives (choose only one drive from each of the file jukeboxes) e. 8. Duration 1 hour h. Examine the configuration file for the scheduled media copy. The file should be named “AMO_lab1. 4. 6.amcs” and is an ASCII file. Number of copies: 1 l. Select the original (source) medium used for the replication process and view the properties. Do not make any changes to this file. Notice in the “General” tab of the properties results. In the Device & Media context of the GUI. Do not make any changes to this file. Select it to view the name of the original medium. Add a schedule so the Media Copy executes in the next 15-minutes. Do not make any changes to this scheduled operation.00 2003 Hewlett-Packard Development Company. switch to the Internal Database context and review the session that was created. SCSI-II Library SCSI II Type in the name of the control device file eg: HP-UX /dev/rac/c#t#d# Windows: scsi2:0:5:1 Busy Drive Handling Barcode Slots Abort (leave as default for now) Leave unchecked. 4.P. NOTE Use the "cookbooks" presented in the appendix to accomplish the robotics device configuration first if necessary.00 2003 Hewlett-Packard Development Company. note the paths to the respective devices.com A-37 U1610S B. you can complete this next part of the lab to configure it. we are assuming that you are using a HP 9000 with a HP six-tape DDS library (auto-changer). and then click OK. Description of your device. . Edit -> Add -> Device Device Name Description Client Name Device Type Interface Type Library’s robotic SCSI Address Whatever you want your library known as (avoid spaces). or ask your instructor for assistance. Execute the Device Agent to determine if the SCSI devices are properly configured (drivers and device paths are needed). Select the host where the device is attached. Start the Data Protector GUI. L.Appendix A Hands-on Labs 6–4. Create a Logical Device of type SCSI-II Library and set the attributes shown in the table.hp. 1. In the lab. LAB: Configure a SCSI II Library Logical Device If you have a DDS or DLT Library attached to your system. ask the instructor if there are any changes to be made to the following instructions. Verify that the Media Agents are installed on the library host system. unless your device supports a barcode reader Specify 1-6 for the 6 slot auto-changer http://education. If you have another type of library. /opt/omni/lbin/devbra –devices Changer: Tape Drive(s): 3. 2. Select the Devices & Media Context. . select slot 6 from the list.00 2003 Hewlett-Packard Development Company. Verify that OmniBack can communicate with the library. 6. Have it check the status of at least one of the tape slots by scanning it: NOTE Before performing the next step. you can use this feature. make sure that no tape is currently loaded in the drive. you can choose any slot. Load the cleaning tape in slot 6 of the magazine. All tapes must be stored in the repository or magazine. The media type for this kind of device (Default is DDS). L.P.hp. or use the Default <Type> for now. Media type 5. enter 1. otherwise change the index as necessary. Set the following attributes: Device name Description Client Data Format Data Drive Drive Index Default Media Pool Whatever you want your drive to be known as (avoid spaces). 7. Choose an appropriate media pool. the scan will abort. and then create a new media pool and change this field later Accept all of the defaults Advanced Repeat the above step if you have a multi-drive library. http://education. cleaning tapes are loaded in the last slot. You may want to interact with the device using the Utility Media Agent (UMA) first to verify that it is operational. When prompted “Do you want to create a Drive for library?” click Yes.com A-38 U1610S B. Select the system connected to the tape library Select Data Protector select the SCSI address or Device File for the exchanger data (tape) device If this is the first and only drive in the library. A description of your device. otherwise. Verify that the library and drive logical devices have been added to the list of configured devices.Appendix A Hands-on Labs Cleaning Slot If the instructor has supplied you with a cleaning tape. However. but the default is abort.. The Logical Device option “Busy Drive handling” can be set to change this behavior. Normally. Without it. Select the library entry in the list of configured devices in the Scoping Pane. then click OK. When loaded. L. it will read the header of the tape. indicating how many slots were scanned.P. When the scan operation has completed. blank.hp. tar. Therefore a scan should be performed after every manual movement of media to/from the library. 11. Using the command line interface.Appendix A Hands-on Labs 9. then unload it back to its slot. list the devices configured on the system and the detailed information on each device using the following commands: omnicellinfo –dev (-detail is also available) omnidownload –list_devices NOTE Refer to the online man pages or the appendix at the back for syntax. Using the command line interface.Select one of the slots in the Results area and then: Actions -> Scan (barcode scan if available) You will be asked to select the drive to be used for performing the scan operation. In the messages window you will see the media agent start and attempt to load the first tape into the drive. “empty.com A-39 U1610S B. open the contents. . perform a scan of a standalone drive and a library (if you have a library available) using the following command: Standalone: omnimm -repository_update <device_name> Library slot: omnimm -repository_update <drive_name> -slot 1 http://education. for example. and select the slots component. It will repeat this process for each slot that you have selected. 10. you will see a dialog box. Data Protector has no knowledge of what tapes are in which slots. Select the drive you have configured in this library. NOTE The scan operation is very important. etc. The messages window should contain a summary of the status of the slots. fbackup. This should also be shown in the media status list.00 2003 Hewlett-Packard Development Company. hp. modify the description field of one of your devices.00 2003 Hewlett-Packard Development Company. Using the command line interface.com A-40 U1610S B.P. Use the following commands: omnidownload omniupload http://education. . L.Appendix A Hands-on Labs 12. use FQDN (media agent hosts): 1. . This lab will verify SAN connectivity and then proceed to library configuration.hp.00 2003 Hewlett-Packard Development Company. The Fibre Channel switch that connects the NSR to the UNIX hosts is configured with an IP address and already connected to an Ethernet LAN.P. 3. http://<IP_address_of_NSR> http://education. 2. Pre-configuration Data Collection: Library type: Library Interface (circle one): SCSI Fibre Channel/SCSI Systems that have library access. 4. 3. 4.com A-41 U1610S B. The MSL Library is connected to a Fibre Channel SAN via a Network Storage Router. Library IP address: Fibre Channel Switch IP Address: Login: Network Storage Router IP Address: Login: Password: Password: Login: Login: Login: Login: Password: Password: Password: Password: Password: 1. Verify with your instructor what systems/devices are available for this MSL configuration before proceeding. The following assumptions are made: 1.Appendix A Hands-on Labs 6–5. Start a web browser on a local PC and access the Visual Manager Interface for the NSR. The NSR is connected to an Ethernet LAN and is configured with an IP address. In many cases these systems and devices are in remote locations and are shared with other training sites. L. The MSL Library is connected to an Ethernet LAN and configured with an IP address. 2. LAB: Configure the MSL Tape Library (optional) Notes: Many HP Education sites have access to additional hardware either locally or remotely. com A-42 U1610S B.P.hp. Login when prompted. L. http://education. Note the host maps in the “Mapping Information” section. 3. Scroll down the report to locate the “Discovery Information” and “Mapping Information” sections. 5. If this is not the case. ask your instructor how to proceed. Select the “Report” link in the Main Menu. . there should be “Auto Assigned” maps for each WWN of the HBA for the SAN connected hosts as well as an Indexed map for the WWN of the FC switch. you may have to manually build the maps.00 2003 Hewlett-Packard Development Company. using the login name and password collected earlier. This indicates that all hosts in the SAN should have access to the devices. Verify that the CHGR and TAPE devices are listed in the “Discovery Information” section of the report. 4.Appendix A Hands-on Labs 2. L. Using the same web browser that was used for the connection to the Visual Manager for the NSR.00 2003 Hewlett-Packard Development Company.Appendix A Hands-on Labs 6.hp. connect to the IP address of the MSL tape library (you may have to turn off use of the proxy server for the web browser) http://<IP_Address_of_the_ MSL_Library> 7.P.com A-43 U1610S B. http://education. . Login to the Remote Management Interface using the Password collected earlier. (see below) Select Here 9. Select the Library to access the status screen. L. .Appendix A Hands-on Labs 8.00 2003 Hewlett-Packard Development Company.hp. Note the number of drives. number of slots. the status of the mail slot and number and locations of tapes.P. Check the status and configuration of the MSL Library.com A-44 U1610S B. http://education. L. Select Here for Admin View 11. http://education. Select the “Report” tab. 12. connect to the Fabric Manager (B-series switches only) for the FC switch used in the SAN that connects the library to the servers. login using the information collected earlier.hp.Appendix A Hands-on Labs 10.P. Select the “Admin View” folder.00 2003 Hewlett-Packard Development Company. Using the same web browser.com A-45 U1610S B. . then select the “View Report” button. L. provide password collected earlier) http://education.00 2003 Hewlett-Packard Development Company. .P. verify that the NSR is visible (may have different names depending upon the model used) 14. Ask your instructor how to proceed if this has not been done already. telnet <unix_client> (login using root id.hp. You may be able to add/import the clients into your existing cell. The hosts connected to the SAN must have Data Protector Media Agents installed in order to be successful. Scroll down the report until you see the “Name Server” section.Appendix A Hands-on Labs 13.com A-46 U1610S B. Client Verification Steps 15. (UNIX Clients only) Telnet to each client system that is connected to the library to verify that the Data Protector Agents are installed. (Again.Appendix A Hands-on Labs 16. Otherwise import or add the client as appropriate to the Data Protector cell.00 2003 Hewlett-Packard Development Company. http://education. Verify that the client system contains device files for the MSL Changer as well as the tape devices. verify that the Data Protector Agents are installed. consult with your instructor before proceeding if you are unsure) 22. While connected to the prospective client system. ioscan –fn (note the device name for the schgr device) Look for entries similar to the following: 17. 19. swlist –l fileset DATA-PROTECTOR (look for DATA-PROTECTOR. Decide which of the connected clients will be the controller for the robotics and then use the “Auto-configure” method to create the logical device configuration within Data Protector: (proceed as follows) a. verify that the client doesn’t already belong to an existing cell.OMNI-MA) 18. cat /etc/opt/omni/cell/cell_server (should be empty or non-existent) Notify your instructor if the client is already in use in another cell. Repeat the “Client Verification Steps” for each system connected to the tape library.hp. L.OMNI-MA is installed. If the DATA-PROTECTOR. 21. Add the client systems into the Data Protector cell by importing them (preferred) or by adding media agents to them. .com A-47 U1610S B. Select the Device & Media context in the Data Protector GUI. Execute the Data Protector Device Agent to test access to the MSL Changer and Tape devices: /opt/omni/lbin/devbra –devices 20.P. .com A-48 U1610S B. Select all of the clients (hosts) that are connected to the SAN containing the tape library. 23.00 2003 Hewlett-Packard Development Company. Create the libtab file (/opt/omni/.libtab) Libtab contents: (according to the example above and data collected from ioscan) http://education. From the Actions menu. proceed as follows: a. b. d. Open the Folder representing the tape library and choose the library controller host (Robotics Path).hp. Select each drive and rename as desired (see below) then Finish.Appendix A Hands-on Labs b. Verify that the robotics device file has the same name on each client. Select “Next ->” e. If the names are different. For the client that was not chosen for the Robotics Path create a configuration that allows for direct library access in the event that the controlling host is unavailable. create a symbolic link or rename the device file so the names match exactly.P. select “Autoconfigure Devices …” c. Execute the following to verify that the device file and library are available: print stat |/opt/omni/lbin/uma –ioctl <dev_file> -barcode -tty c. L. hp.Appendix A Hands-on Labs r848c77. Select the MSL Logical Library and perform a “Barcode Scan”. . 25. Select “Advanced” (near the bottom of the screen) f. Open the Library Folder b.00 2003 Hewlett-Packard Development Company. The “Advanced Options – Settings” should open by default g. In the Device & Media context of the DP GUI. Enable direct access for each drive as shown below.hp. Verify the Lock name for each drive within the library. Select “Settings” tab e.com A-49 U1610S B. Enable the “Use direct library access” option.com /dev/rac/c7t0d0 “HP:MSL5000 Series” 24.P. (Troubleshooting tip: errors in the Libtab file will prevent the enabling of direct access) a. Select the Drives Folder within the library c. 26. L.edunet. modify the library drives that are associated with the system containing the Libtab file that was created in the previous step.dow. http://education. Verify that the tapes shown in the Remote Management Interface match those shown by Data Protector. Select (double-click) a drive in the library configuration associated with the Libtab host d. com A-50 U1610S B. Create a new Media Pool named MSL_Library 28. 29. http://education.P. L. Lab completed.Appendix A Hands-on Labs 27.hp. Initialize all of the tapes in the MSL into the MSL_Library media pool.00 2003 Hewlett-Packard Development Company. use the autolabel feature and accept the defaults for the media capacity. . conf and /etc/nsswitch. 2. In many cases these systems and devices are in remote locations and are shared with other training sites. Verify DNS configuration for the system before adding it to the cell by connecting to the system and displaying the /etc/resolv. L. make the necessary adjustments to enable name resolution using DNS. Some sites have the DNS configuration documented in the beginning of the /etc/hosts file.Appendix A Hands-on Labs 6–6. Open a terminal window. Your instructor may choose to demonstrate this if hardware access is limited.P.conf.00 2003 Hewlett-Packard Development Company.conf search nameserver nameserver Login: Login: Login: Password: Password: Password: http://education.hp. LAB: Configure a Multi-Drive SCSI Tape Library (optional) Notes: Many HP Education sites have access to additional hardware either locally or remotely. Verify with your instructor what systems/devices are available for this additional library configuration before proceeding. use FQDN (media agent hosts): 1.com A-51 U1610S B. look there for the needed parameters for the next step: 2. cat /etc/resolv. . Library IP address: Device Files for the library: Changer: Drive 1: Drive 2: Drive 3: Drive 4: 1.conf files. Pre-configuration Data Collection: Library type: Library Interface: SCSI Systems that have direct attached library access. and telnet to the client system. Display the /etc/resolv. Import the client system connected to the tape library into the cell. These usually indicate an incomplete name resolution issue on one or more of the client systems.conf contents are correct on all clients and then run the check again omnicheck -dns 6. If the agents are older upgrade them from the Clients context of the DP GUI. . Verify that the Media and Disk Agents are installed on the client and are the same version as the cell manager.Appendix A Hands-on Labs cat /etc/nsswitch. Verify that the imported client is registered with the FQDN of the client.com A-52 U1610S B. L. Verify DNS connectivity with other systems within the cell: omnicheck -dns 5. Look for “cannot resolve” messages in the output of the omnicheck command.P. 7. Open a terminal window for the client system where the SCSI library is connected and execute the Data Protector Device Agent to discover the available devices (see sample): Windows: c:\program files\omniback\bin\devbra –devices UNIX: /opt/omni/lbin/devbra –devices http://education. 4.hp. Verify the /etc/resolv. This does not verify successful DNS configuration.00 2003 Hewlett-Packard Development Company.conf hosts: dns (verify the hosts entry shown below) [NOTFOUND=continue] files nis 3. Appendix A Hands-on Labs 8. Start the Data Protector GUI. 12. 11.P. Select Next ->.com A-53 U1610S B. http://education. .00 2003 Hewlett-Packard Development Company. 15. 14. switch to the Devices and Media Context. Select the Devices Folder.hp. Lab Completed. 13. L. Select the client system with the Library connected. 16. Select the Library that is to be configured. 9. and from the Actions menu choose “Autoconfigure Devices…” 10. select Finish. Use the Barcode Scan to determine the number of available media. Create a new media pool that matches the drive types in the library. Format 2-3 tapes from the available library repository into the new pool created in the previous step. Modify the drive properties for each drive in the library so that they use the Media Pool created in step 11 as the default pool. Create a new filesystem/partition to be used for a file jukebox.hp. LAB: Preparation for Automated Media Copy Objective: create additional devices to be used for AMO to be configured with backup. Requirements: two library devices of the same type (we will assume file jukebox is the only classroom solution) 1. . • Format the media to the same size as the original file jukebox media. 2.com A-54 U1610S B. L.Appendix A Hands-on Labs 6–7. Follow the procedure used previously for configuration of the file jukebox.00 2003 Hewlett-Packard Development Company. • Assign the drives in the new jukebox to the same pool as the original jukebox. http://education. with the following exceptions (unless you have sufficient disk space for more): • Create only a single drive jukebox • Allocate a minimum number of file (slots) such as three to four. This should be sufficiently large to accommodate 3-4 media from your original file jukebox to allow for practice with Automated Media Copy.P. or file jukebox. MSL tape library. use any available library or standalone devices that you configured into the cell. http://education. For the backup tasks. It is unlikely that all of the labs will be completed.Appendix A Hands-on Labs Lab 8: Backup Objective: During the following labs. This may be a DDS-Autochanger.P. you may pick and choose ones that look interesting.00 2003 Hewlett-Packard Development Company. you will try out several methods of backup and the options available. or any other available device. DLT tape library.com A-55 U1610S B. L. .hp. e.Appendix A Hands-on Labs 8–1. set the following option: Display Statistical Info Check this box. Click the Backup context. f. Next> Choose one of the devices that you created from the previous module. . From the bottom of the Scoping Pane. Launch the Data Protector GUI: b.com A-56 U1610S B. 4 Click the Advanced… button. From the Scoping Pane select the Interactive Backup Wizard (no load balance) c. Let's start by revisiting a simple interactive backup via the GUI: a. Click OK when done. Select a filesystem from one of the clients. Protection Select Days. (choose the next available 15 minute interval. L.00 2003 Hewlett-Packard Development Company.P. Select the Next > button at the bottom to make the device selection. you may want to make it 30 if you don’t think you will finish this section before the next quarter hour passes. d. Select the Tasks tab. Leave the remaining fields with the default settings. Select the desired protection (minimum of 4 days). Select to schedule the backup to run at some time in the next few minutes. Select the tab named “Other”.) http://education.hp. Click Next > once more. LAB: Backup Objective: Simple backup 1. http://education.00 2003 Hewlett-Packard Development Company. a Preview be performed. h. Acknowledge the message by clicking OK. just select Next>. Whenever a new backup specification is created or modified.hp. i. If the preview has worked. you will see the media and disk agents start. The object will go into the running state. you have a good indication that the backup will work also. L. . At the summaries screen. and hence. Save the backup as a new specification. k. it is highly recommended that before it is run. Preview the backup.com A-57 U1610S B. Notice the device name in the Device column. runs very quickly. It simply does a tree walk of the file systems. and the percentage complete indicator will go from 0 to 100 %.P. From the Results Area (backup wizard): Click Preview Backup In the Results Area. but will not actually write any data to tape. Choose to save it to a group with your initials as the group name. choose any unused name for the file. j. A window will appear informing you when the preview is complete. Preview will perform a dummy run of the backup. Select your object in the Summaries and then select the “Change device” button to assign your object to a device. or review the properties for the backup.Appendix A Hands-on Labs g. You should see the session report. which is based on the data and a run number.00 2003 Hewlett-Packard Development Company. 1. Identify one of your backup sessions. then get detailed information on it with the command: omnidb –session sessionid –detail f. Let's start with the ASCII source of the backup specification you just created. You can also get object level detail from the session: omnidb –session sessionid –report http://education. more BackupSpecificationName notepad BackupSpecificationName (hp-ux) (Windows) d. Get a list of the previous Data Protector sessions: omnidb –session The current sessions: omnistat e. Examine the schedule for the backup by going to the <OMNICONFIG>/schedules directory.Appendix A Hands-on Labs 8–2.com A-58 U1610S B. don’t make any changes) more BackupSpecificationName notepad BackupSpecificationName (hp-ux) (Windows) c.hp. L. Bring up a terminal/command window and use the following commands on the Cell Manager system: cd <OMNICONFIG>/datalists Display the contents of the directory ll or dir Your backup specification should be listed. b. LAB: Backup — Command Line Practice Objective: Using the command line interface for backup. . Each session listed has a session-id. Now take a look at its source with the command: (note. it will be the same information you saw in the Messages window when you performed the backup. Now we will show you how to get information regarding the backup you just performed using the Command Line Interface: a.P. It is the same list generated by the omnidb –session command.P.00 2003 Hewlett-Packard Development Company. . e. Double click one of the objects to see its messages and other properties. Now we will show you how you can get information regarding the backup you have just performed. Discover the names of the objects that were backed up as part of the session: Unix: omnidb –filesystem <object_name> –session <sessionid> –catalog Windows: (note the description part of the object name must be endclosed in double-quotes) omnidb –winfs <object_name> -session <session id> -catalog 2. Find out what media was used for this session. via the GUI: a. Select the Devices and Media context. http://education.hp. b. You will see the objects backed up in that session. Drill down into the media pool by double clicking on it. You will now be shown a list of the previous sessions.Appendix A Hands-on Labs g. Start the Data Protector GUI.com A-59 U1610S B. b. L. Switch to the Internal Database context to see all previous sessions. Find out what media was used by the session: omnidb –session sessionid –media h. 3. select: the Media tab. a. look at the media in the media pool. Identify a backup session and view the properties for it by double clicking on it. Switch to the Monitor Context. The monitor screen will show if there are any sessions in progress c. open the sessions tree to see the data. Now that you have identified the media that was used for the session. d. From the tabs at the top of the Results Area. as restore is covered in the next module. Now. Select one of the objects to see the filesystem browser appear in the Results Area of the GUI. The objective here is to show you what new data appears after each backup you perform.hp. Open the Restore Sessions folder by double-clicking on it. Perform another backup. Verify that the backup has completed successfully by using either the GUI or the command line interface. (Choose a short backup so as to not occupy the command line for too long) Use the omnib command to launch the same backup specification: omnib –datalist <any_backup_spec_name> 6.P. click Cancel if necessary then (optionally) 5. Open one of the previous sessions by double-clicking on it. take a quick look at what is available under the Restore window. Drill down into the media by double clicking on it. b. . Select the Restore context. c.Appendix A Hands-on Labs You will be presented with a list of the media that is in the pool. Look at the information found on each one of the tabs. Explore/Expand parts of the filesystem directory tree by clicking on the plus “+” sign. http://education. locate the specific media that was used. We will not go into much detail here. e. When finished viewing the files. f. 4. but this time use the command line interface to initiate the session. L.00 2003 Hewlett-Packard Development Company.com A-60 U1610S B. d. Repeat this process to expand the subdirectories also. c. a. Open one of the systems to see the object backups for it by double-clicking on it. Select the View menu.sh Click Apply to make the changes to the backup specification file. Set the following: Pre-exec Post-exec /tmp/yourname_pre_exec. Preview the backup: Actions -> Preview Backup http://education. In the Options tab. Start the Data Protector GUI (if not already started) 5. Make these scripts executable: chmod 755 /tmp/yourname*. Open the Backup Specifications list to see existing specifications.sh.00 2003 Hewlett-Packard Development Company. This script should contain the following two lines: #!/usr/bin/sh print "Data Protector Post-Environment" >>/tmp/yourname_omni_post. Create a script called /tmp/yourname_pre_exec. Select the Options tab from the top of the Results Area. LAB: Pre and Post Execute Scripts (Unix) 1. This script creates an output file that shows the environment variables set during script execution: #!/usr/bin/sh print "Data Protector Pre-Environment" >>/tmp/yourname_omni_pre. .sh /tmp/yourname_post_exec. L.sh 4. Create another script called /tmp/yourname_post_exec.log exit 0 2. Select the Backup context to modify a backup specification: 6.log exit 0 3. fill in the full path to the pre/post exec scripts that you created.hp. Select one of your backup specifications that will execute very quickly. 8. a.log print $(env) >> /tmp/yourname_omni_pos.log print $(env) >>/tmp/yourname_omni_pre. 9. 7.P.sh.Appendix A Hands-on Labs 8–3. choose By Group. Select the Advanced option in the Filesystems Options section.com A-61 U1610S B. SMEXIT. (read/execute)" NOTE By default. i.com A-62 U1610S B. if you choose an incremental for a new object).e.Appendix A Hands-on Labs Select High Network Load. Verify that there are no abnormal messages in the Messages box. Click Preview Backup. L. This incremental backup will be based on the full backup of the object performed earlier. When the preview is complete. "Backup Completed!" Verify that there are no abnormal messages in the Messages box. http://education. Click OK to close the Message box. such as " exitcode Pre-exec failed with 127 => backup aborted!" or "Post-exec failed with exitcode 127 => backup aborted!” make sure that the script contains the correct PATH to all the commands that are contained in the script. you will see the message: "Preview Completed!" Click OK to close the Message box. (This step is irrelevant if you are not backing up over a network). Set the ExecScriptOnPreview option in the global file to change this. you will see the message. 10. Click Ok. SESSIONID. You should be able to see the environment variables and their values discussed in this module. (You will need to do a full backup first.P.00 2003 Hewlett-Packard Development Company. etc. Check the permissions of the script. Error Code 126 is also very common. . TIP If you get critical errors. When the backup is complete. Check the output files that your pre and post-exec scripts generated. It must have at least "rx. Pre and Post-exec scripts at backup specification level are not executed during previews. b.hp. Now perform an incremental backup of any object that you choose. Start the backup: Actions -> Start Backup Select Full Backup Type and Select High Network Load. Incremental Backup 11. . L. decide what media pool to use and the pool properties (perhaps try append incrementals only). http://education. Start by making some modifications to the contents of the directory that you intend to backup by copying or renaming some files within the directory.P.Appendix A Hands-on Labs Again. as this will not usually corrupt the operating system in any way) Verify that there are no abnormal messages in the Messages box.com A-63 U1610S B. decide which logical device to use (perhaps use a library if you have not done so yet).hp.00 2003 Hewlett-Packard Development Company. (choice of a temp directory is wise. txt set >> c:\temp\backup_post.P. create a batch file (script) called: c:\program files\omniback\bin\pre_exec. LAB: Pre and Post Execute Scripts (Windows) 1. Open the Backup Specifications list to see existing specifications. 8. Select one of your windows backup specifications that will execute very quickly (such as the one used in the Data Protector Basics module.txt echo “end of pre exec environment” >> c:\temp\backup_pre.txt 3. 6. fill in the full path to the pre/post exec scripts that you created. create a batch file (script) called: c:\program files\omniback\bin\post_exec.txt 2. c.00 2003 Hewlett-Packard Development Company.Appendix A Hands-on Labs 8–3. .bat Contents: echo “Post exec environment” > c:\temp\backup_post.txt echo “end of post exec environment” >> c:\temp\backup_post. Set the following: Pre-exec Post-exec pre_exec.bat Click Apply to make the changes to the backup specification file. Select the View menu. L.txt set >> c:\temp\backup_pre. Preview the backup: Actions -> Preview Backup http://education. choose By Group. Using Notepad.bat Contents: echo “Pre exec environment” > c:\temp\backup_pre. 5. 7.com A-64 U1610S B. Select the Options tab from the top of the Results Area.hp. In the Options tab. Start the Data Protector GUI (if not already started) 4. Select the Advanced option in the Filesystems Options section. Select the Backup context to modify a backup specification that runs on the Windows system.bat post_exec. Using Notepad. 9. Set the ExecScriptOnPreview option in the global file to change this. Check the output files that your pre and post-exec scripts generated. if you choose an incremental for a new object). When the preview is complete.e. You should be able to see the environment variables and their values discussed in this module. Incremental Backup 10. decide what media pool to use and the pool properties (perhaps try append incrementals only). etc. "Backup Completed!" Verify that there are no abnormal messages in the Messages box. Click Ok. Pre and Post-exec scripts at backup specification level are not executed during previews. decide which logical device to use (perhaps use a library if you have not done so yet). . you will see the message: "Preview Completed!" Click OK to close the Message box. as this will not usually corrupt the operating system in any way) http://education. d. you will see the message. (This step is irrelevant if you are not backing up over a network).hp. L. Start the backup: Actions -> Start Backup Select Full Backup Type and Select High Network Load. Start by making some modifications to the contents of the directory that you intend to backup by copying or renaming some files within the directory.com A-65 U1610S B. This incremental backup will be based on the full backup of the object performed earlier. Verify that there are no abnormal messages in the Messages box. (choice of a temp directory is wise. (You will need to do a full backup first.P.00 2003 Hewlett-Packard Development Company. Click Preview Backup. When the backup is complete. i. Again. Now perform an incremental backup of any object that you choose. NOTE: By default.Appendix A Hands-on Labs Select High Network Load. Click OK to close the Message box. SMEXIT. SESSIONID. L.com A-66 U1610S B.00 2003 Hewlett-Packard Development Company.hp.P. .Appendix A Hands-on Labs Verify that there are no abnormal messages in the Messages box. http://education. or create a new one. Use any incremental level that you would like. The backup should run each night starting tonight. or c:\winnt\system32\drivers\etc\hosts. To finish this section we will take a quick look at Templates and Groups. 2. You may want to use the file jukebox that we created earlier in the course. and file system incremental. file system full. Exclude the Data Protector database from the file system tree where it resides. but this lab is designed to allow you to experiment on your own. add an additional comment to the top of the file. The tapes are write-enabled. http://education. You will require at least two logical devices. Modify the hosts file. L. Your instructor will guide you if necessary. 5. All these backups have used one logical device and this device has been statically allocated. You may re-use the backup specification from the previous step. The backup should execute at least 3-4 hours after the full backup from step 2.Appendix A Hands-on Labs 8–4. The remaining lab is designed to allow you to experiment with many of the features not yet covered by the previous labs. Before you finish for the day. When you arrive the next day. the individual steps are left out. Schedule a Full backup of the cell manager to be executed at midnight. check the following: • • The devices your backup will use are powered on. Create and preview a backup specification that does a full backup of all the hosts in your cell using load balancing. you may want to add only a few file systems. 3. not the entire host to the backup specification. Schedule an incremental backup to run for the cell manager. . either /etc/hosts.P. LAB: More Backups You have now performed three different types of backups. 4. If you have very limited disk space. 1.hp. Since by now you should have a little experience with the GUI. check the status of your backups.com A-67 U1610S B. Tapes belonging to the media pools you have specified are loaded in the correct devices. interactive. Modify a file before the backup starts.00 2003 Hewlett-Packard Development Company. by opening up the Templates collection in the Scoping Pane (this is in the Backup Context).hp. Organize your backup specifications using the grouping feature so that you can easily identify your backup specifications. . The options that you select are just a sub-set of those used for the Backup Specification. Create your own template. L.00 2003 Hewlett-Packard Development Company. try changing the views and note the results in the Scoping Pane (open all the component trees within the Scoping Pane) Choose from: By Name. Create two to three groups to exercise the capabilities.Appendix A Hands-on Labs 6. By Type.P. Experiment with the View menu in the Menu Bar. By Group 7.com A-68 U1610S B. http://education. 00 2003 Hewlett-Packard Development Company. Which directory did you look in to view your new data list? c. L.hp. What command did you use? b. a) What command did you use? b) Use the GUI to view the /tmp file system object that now resides on the tape? c) Looking at the Start Time and End Time. .com A-69 U1610S B. a. What must be done with the data list produced by omnicreatedl before it may be used for backup? 2. how long did the backup take to run? http://education. LAB: omnicreatedl (Optional) 1. Use the omnicreatedl command to create a data list that contains the file systems on your cell server.P.Appendix A Hands-on Labs 8–5. Use the omnib command to backup a temp directory(/tmp or C:\temp) on your cell server. Give the data list an appropriate name. Have the backup protected for 4 days. 00 2003 Hewlett-Packard Development Company. What are the causes of all of the warnings? Is this full backup useful for a system recovery? 3. 2. If you have an HP-UX server. If you have a Windows 2000 system with an internal tape drive create a full system backup using the local tape drive. perform a full system backup to the autochanger. Could this full backup be useful for disaster recovery. 1. Explain what to do with the “Minor” error messages that are produced.com A-70 U1610S B. . If you have an HP-UX server.P. 5. This backup should use a pre-exec script to umount the filesystem and a post-exec to mount again the filesystem after the backup completes. perform a rawdisk backup of any logical volume. Experiment with deleting and restoring some files that were previously part of a full backup from either Windows or Unix. even with these error messages? 4.) http://education. if you have to schedule the backups from steps 2 and 3 to run during the evening.Appendix A Hands-on Labs Lab 8-6: Backup (advanced-optional) Objective: The objective of this lab is to practice with some additional Data Protector backup features. (This may take some time to complete. What is in the CONFIGURATION object that is part of a full Windows backup? Try using the Restore context to browse its contents after the previous full backup completes. L.hp. hp.00 2003 Hewlett-Packard Development Company.com A-71 U1610S B.Appendix A Hands-on Labs Lab 9: Restore Objective: The objective of this lab is to learn how to Data Protector restore features.P. . L. http://education. Each one was performed by selecting a single file-system component. HP-UX has multiple mount points by default. Restore1: Restore the file into a new directory. First. After you examine the file. use the option to list restored files. in most cases. 2. or notepad) if you have not done the previous lab that included this step. use the default options. choose an appropriate new name. (non-critical files on HP-UX may be found within the /home filesystem. or explain why they were not. you should be aware of the Restore GUI. Note! You may have performed various different backups to get to this point of the course. Add a line to the top of the file by using one of the system editors (vi. such as host_copy. make a copy of it in the same directory. You may want to delete some non-critical files before the restore starts. Restore the file from the full backup that included the hosts file. This lab will intentionally be very unstructured to allow you time to experiment. You have performed three restores.P. On your local host file. Verify that the files were restored in each case. then verify that they were restored. Now you should try a parallel restore that will restore files from three separate objects in the same restore session. look at the contents of the hosts file. L. 1. Restore is usually quite simple. This lab assumes that you have taken at least one full backup of your cell manager.00 2003 Hewlett-Packard Development Company. . Restore2: Restore the file to the original location. Restore3: Overwrite the file on the disk during the restore.hp. http://education. By now. it is a matter of deciding what to restore.Appendix A Hands-on Labs 9–1. to where and from which backup. Restore the file /etc/hosts or C:\winnt\system32\drivers\etc\hosts.com A-72 U1610S B. including filesystem restore. Let’s start with a simple single-file restore. This will not be possible on Windows unless you have multiple partitions. and its general options from the previous discussion. LAB: Restore Objective: During this lab you will perform the Data Protector restore function and use some of available options. The examples below will give some guidance on how to construct the command line for the restore. so use the following as a reference only. omnir command. L.P.txt to the latest version on HP-UX and trace to Windows. (make the window as wide as possible) enter: omnidb –filesystem This will produce a listing of all the file system objects that are available for restore. Use the Data Protector Restore GUI to restore: rgb.Appendix A Hands-on Labs 3.hp. Insert your hostname:mount point and description into the command and review your output. skip to step 6 for Windows a. as if it is corrupted. 5. 4. Perform these steps for UNIX. Restore the file to the original location and overwrite the one on the system. All the restores you have performed up to now have used the GUI. but you will not be given the specific location. Your data will be different.com A-73 U1610S B. to perform the same point in time restore that you have just performed. Hint: use the Restore by Query from the Restore Context of the GUI. Your output should resemble the following example: # omnidb -filesystem Object Name Object type =================================================================== scorpio:/ 'Nigels /etc backup' FileSystem scorpio:/ ' [/]' FileSystem scorpio:/home ' [/home]' FileSystem scorpio:/Data Protector ' [/Data Protector]' FileSystem scorpio:/opt ' [/opt]' FileSystem scorpio:/stand ' [/stand]' FileSystem scorpio:/tmp ' [/tmp]' FileSystem scorpio:/usr ' [/usr]' FileSystem scorpio:/var ' [/var]' FileSystem hostname : mount ' description' # omnidb –filesystem scorpio:/ 'Nigels /etc backup' # Description: The preceding command will produce a listing of all the backup sessions that contain this object. . You will restore a single file. From the terminal window. You will see something like this: # omnidb -filesystem scorpio:/ 'Nigels /etc backup' http://education.00 2003 Hewlett-Packard Development Company. Now you will learn how to use the command line interface. com' WinFS pc99.dow.com:/D 'D:' WinFS # Description: hostname : mount “ description” use double quotes! # omnidb –winfs pc99.com:/ [d:0] /etc [f:0] /etc/hosts.dow.uksr.dow.com:/CONFIGURATION 'CONFIGURATION:' WinFS pc99.dow.edunet.uksr.P.edunet.com:/C “C:” http://education.dow.uksr. In this example.hp. You want to restore to the point in time of the incremental.edunet.edunet. . The larger one (in KB size) is the full.edunet. it is 1999/12/12-2.uksr.Appendix A Hands-on Labs SessionID Started Duration Object Status Size [KB] NumberOfErr ======================================================================= 1999/12/12-2 15:01:05 00:00:30 Completed 71 0 1999/12/12-1 14:53:51 00:01:08 Completed 10048 0 From this listing.com:/ [Normal] From: RMA@scorpio. so make a note of the SessionID.dow. L.com' WinFS pc99.uksr. you can see the two previous backup sessions.dow.hp.hp.hp.uksr.hp. From the terminal window.hp.com:/C 'C:' WinFS pc99.edunet. Now with the above information you can initiate a command line restore: # omnir -filesystem scorpio:/ 'Nigels /etc backup' -session 1999/12/12-2 -tree /etc –catalog You should see messages similar to this: [Normal] From: RMA@scorpio. (make the window as wide as possible) enter: omnidb –winfs This will produce a listing of all the file system objects that are available for restore.edunet.hp.hp.com "" Time: 12/14/99 17:06:08 STARTING Disk Agent for scorpio.com "" Time: 12/14/99 17:06:13 COMPLETED Disk Agent for scorpio.hp.hp.00 2003 Hewlett-Packard Development Company.hp.hp. Your output should resemble the following example: Object Name Object type ============================================================================ == pc99.hp.edunet.bkup [Normal] From:
[email protected] "Scorpio_DDS" 17:06:30 COMPLETED Medium Agent "Scorpio_DDS" Time: 12/14/99 6.com:/CONFIGURATION 'pc99.hp.com A-74 U1610S B.dow. b. Perform these steps for Windows clients: a.hp.com "Scorpio_DDS" 17:05:52 STARTING Medium Agent "Scorpio_DDS" Time: 12/14/99 [Normal] From: VRDA@scorpio. and the smaller is the incremental.com:/C 'pc99. You want to restore to the point in time of the incremental. and the smaller is the incremental. In this example. Now.dow.com A-75 U1610S B.00 2003 Hewlett-Packard Development Company. it is 2003/09/17-2. Try the following: • • • Restore a file to a different system (the client system does not need to be in your cell) Try restoring a busy file Restore an entire system. You will see something like this: # omnidb -filesystem scorpio:/ 'Nigels /etc backup' # omnidb -winfs pc99. Free format lab.edunet. explore for yourself some of the other Data Protector restore functionality available.P. Insert your hostname:mount point and description into the command and review your output. Use the online help to find out about the options available in the different screens. L. c.edunet. Now with the above information you can initiate a command line restore: # omnir –winfs pc99. The larger one (in KB size) is the full.Appendix A Hands-on Labs The preceding command will produce a listing of all the backup sessions that contain this object.com:/C “C:” –session 2003/09/17-2 –tree /temp –catalog 7. so make a note of the SessionID.hp. all objects in parallel http://education.com:/C "C:" SessionID Started Duration Object Status Size [KB] NumberOfErr ============================================================================ 2003/09/16-3 12:27:25 00:52:18 Completed 2052530 0 2003/09/17-2 13:43:54 00:52:18 Completed 1265 0 From this listing. . Perform some restores of your own.hp.dow.hp. you can see the two previous backup sessions. 00 2003 Hewlett-Packard Development Company.hp.com A-76 U1610S B.Appendix A Hands-on Labs Lab 10: IDB Management Objective: The following lab demonstrates the management tasks for the Internal Database. .P. http://education. L. or change the device properties of another device to use the media pool from step 1.com A-77 U1610S B. It should be protected by being backed up. http://education. Procedure: 1. LAB: Internal Database Backup Objective: The following lab demonstrates backup for the Internal Database. (optional) Create a new Logical Device that is assigned to use the pool created in step 1. before any manipulation of the database. Create a backup specification to perform a full backup of your Internal Database.hp. It is essential that a backup of the database is performed on a regular basis. after all of the other backups have completed. Backup using a standalone device (this may be a remote device. such as one connected to Windows system. L. (c) Choose Add Backup. Internal Database Backup Recommendations (for Easier Recovery) Use a separate backup specification for the Internal Database. Create a new Media Pool to be used exclusively for the Internal Database backups. As discussed earlier. Be sure to use this device for the backup. . Add at least one tape to the pool. the Internal Database is critical to the operation of the product. a local Windows device for the remote Cell Manager is Ok).P.Appendix A Hands-on Labs 10–1. (This must be a device that you will have physical access to for this lab. Use a separate media pool for the Internal Database media. From the View menu: View -> By Group In the Scoping Pane: (a) Open the Backup Specifications container (b) Select “Default” with the right-mouse button. (e) Select the Internal Database object (f) Select the device added from Step 2. 2. Protect the backup for one month. as long as it is a device you will have physical access to) Backup the database daily. (d) Select the Blank Filesystem Backup template. 3.00 2003 Hewlett-Packard Development Company. such as write_db/read_db or adding database extension files. i. Perform an interactive backup of the database using your newly defined backup specification. Now that you have a backup of the database. Open a terminal window on the Cell Manager and execute the following command to display the list of directories that are to be included in the Internal Database backup: omnidbutil –list 5.). (Object Properties/Database ) Click ellipsis (. In the Protection field. and enter 4.Appendix A Hands-on Labs Set the following options for the Database Backup: Description Check before Backup Backup Device Database Backup Options Enter a description. Leave this enabled. you can continue with the remainder of the lab.00 2003 Hewlett-Packard Development Company. OmniDB Backup This button defines whether a consistency check is to be performed prior to backup. “IDB Backup” 4. L. you can recover from this backup! http://education. . Remove the tape from the tape drive and physically label the tape as Data Protector IDB Backup. select Weeks.hp.. select the Logical Device to be used.P..e. Monitor the backup to verify that it completes successfully. secure in the knowledge that if anything goes wrong. Select: Start Backup 6.com A-78 U1610S B. Save the datalist as. omnidbutil -extendfnames <OMNIVAR>/db40/datafiles/cdb -maxsize 500 or omnidbutil -extendfnames <OMNIVAR>\db40\datafiles\cdb -maxsize 500 http://education. The file that occupies the most database tablespace is: fnames. in up to 2047MB increments. L.hp. record the disk space used for Filenames: Space used File names Disk space usage _______________ 2.P. (replace OMNIVAR with the correct path to the CDB on your Cell Manager. Check to see if your database has additional extents: omnidbutil -extendinfo How many extensions are being used? What is the maximum size with extensions? fnames.com A-79 U1610S B. The default limit of the file is 2 GB. but the command line is used here. (Note omnidbutil is not in your PATH by default) HP-UX: /opt/omni/sbin/omnidbutil Windows: C:\program files\Omniback\bin\omnidbutil omnidbutil -info Save a copy of the command's output.Appendix A Hands-on Labs 10–2. this file occupies about 20% of the Internal Database. Use omnidbutil to display database information. . Extension files allow the database to be extended beyond its default capacity. LAB: Internal Database Maintenance Adding Extension Files to CDB This lab may be performed by using the GUI if desired. maximum size is 32 GB. Add a 500 MB extension to the base file fnames.dat This file contains information on the names of the files backed up. From the command's output.00 2003 Hewlett-Packard Development Company.dat . Typically. You may need this later. 1.dat 3. hp.P.Appendix A Hands-on Labs 4.00 2003 Hewlett-Packard Development Company. L.com A-80 U1610S B. omnidbutil -extendinfo What file was created for the extension? How many extensions are being used? What is the new total capacity? http://education. Display the extension information again. . Enter the low space value of 50 MB. f. Specify the maximum number of files to be 1000. DCDirAllocation=2. Check the contents of the newly created DCBF directories. Verify that the DCBF_2 directory was created. What are your observations? 4. Add one directory using the GUI. and select Detail Catalog Binary Files. L. Use the command line similar to the following: omnidbutil –add_dcdir /var/tmp/DCBF_3 –maxsize 100 –maxfiles 1000 –spacelow 50 –seq 2 2. What is the meaning of this change? 3. d. Using the omnidbutil command on the Cell Manager. Using the Internal Database context. Select Finish. Enter the Path to the directory where you will place the DCBF extension. Inform Data Protector of the change. Is there any way to notify Data Protector that this has been done? Check the man-page (word pad document) for the options to omnidbutil. Specify the maximum size to be 100 MB. Enter Allocation Sequence: 1 c. e. Perform a few (at least 3) quick backups. and sequence number 2. create an addition DCBF directory named DCBF_3 in a location where you have at least 100MB available. Move a file from DCBF_3 to DCBF_2. Open the Usage folder. (this should be in a filesystem that has at least 100 MB available) Choose the name for the directory to be DCBF_2. right click to get the pop-up menu and select Add Detail Catalog Directory b. and add another using the command line.com A-81 U1610S B. . h.Appendix A Hands-on Labs 10–3.P. Change the allocation algorithm in the global file. add one additional DCBF directory as follows: a. and then use the correct command to remove the DCBF_3 directory from Data Protector. LAB: Adding Directories to the DCBF Objective: Add two additional DCBF directories to the cell. perhaps to your file jukebox.hp. Allow for up to 1000 files. Adding Extension Files to the Internal Database (via the command line) 1. http://education.00 2003 Hewlett-Packard Development Company. g. minimum space 50 MB. After removing some data. 2. use the automated restore to recover it. . look for sessions marked as followed: Aborted session (called the “no” symbol) Failed session (called “X” symbol) Select some or all sessions of status Aborted/Failed. You should see that while the disk space usage is the same.hp.Appendix A Hands-on Labs 10–4. 1. check the database utilization again. purge any failed or aborted backup sessions: Open the Sessions container. What information has changed? Execute the command: omnidbutil –purge –daily (would normally be executed at noon) Execute the omnidbutil –info command again.com A-82 U1610S B. Try the following commands. L.00 2003 Hewlett-Packard Development Company. again using omnidbutil –info to check utilization before and after each purge and strip command: Get a listing of previous sessions: http://education. the record usage has gone down. (Use the [Ctrl] key to select multiple sessions. LAB: Internal Database Maintenance Purging data from the Internal Database Try some of the different methods provided to mark backup records as invalid and remove them from the database. Using the “Data Protector Database” context of the Scoping Pane. "Are you sure you want to remove these <num> sessions?" When the purge has finished. Session information can also be purged from the database using the command line interface. using the omnidbutil –info command. This lab will use both the GUI as well as the command line.P. Compare the output to the previous time you ran the command.) From the pop-up menu: Remove Session Click Yes to the prompt. as well as their default values: KeepObsoleteSessions: KeepMessages: DailyMaintenanceTime: DailyCheckTime: 4. Note the use of the following parameters. Using the command line.Appendix A Hands-on Labs omnidb –session Remove session log information for selected session: omnidb -purge -session <session_id> Remove the detail catalog for a selected session: omnidb -strip -session <session_id> 3. purge restore sessions (including detail catalog information) older than 1 days: omnidbutil -purge –sessions –days 1 Changing the Purge Schedule (optional) Data Protector automatically performs a standard database purge daily.00 2003 Hewlett-Packard Development Company. remove only the session messages for a selected session. Use the following procedure to examine the schedule and behaviour: 1.P. Use any text editor to open the file <OMNICONFIG>/options/global 3. Using the GUI. Use the operating system copy command. Close the file and exit the editor.com A-83 U1610S B. L. . http://education. Use the Data Protector Database context as in step 1 4. Make a backup copy of the original file before proceeding. (just in case…) 2.hp. Appendix A Hands-on Labs http://education. L.P.com A-84 U1610S B.00 2003 Hewlett-Packard Development Company. .hp. For Unix this may be /root. Once you have a recent backup of the database. 10. 4. Confirm the media prompt by typing OK. 3. Execute the command: omnidbrestore -autorecover 6. then create a new database backup. http://education. use the procedure outlined within the student notes of this module. Once the database has been successfully restored.hp. Examine the properties (date/time) of the <OMNIVAR>/db40/logfiles/rlog/obrindex. 2. 7.com A-85 U1610S B. 11. enter cancel at the prompt.dat. Stop and then restart the Data Protector services. LAB: Internal Database Recovery Objective: This recovery will focus on the automated recovery capabilities. and for Windows 2000 it may be C:\Documents and Settings\Administrator. Start the GUI and verify that the Devices. L. if this is desirable.dat) is available. Close the Data Protector GUI. Perform another backup of the IDB. 9. unless the medium indicated does not match the tape you have. 1. 5. start this process again. the date/time should match the time of the previous IDB backup.Appendix A Hands-on Labs 10–5.00 2003 Hewlett-Packard Development Company. Verify that the recovery log (<OMNIVAR>/db40/rlog/obrindex. See note below.P. Media and Database content is as it was at the time of your backup. Be sure to have your most recent database backup tape at hand. NOTE If the media you have available is different than the one that you’ve been prompted to confirm. You can also use the manual recovery. . 8. check the status of the Data Protector services. Open the “global” file and alter the value of the RecoveryIndexDir parameter to contain the path to the login directory of the system administrator user. http://education. Rename the obrindex.00 2003 Hewlett-Packard Development Company.Appendix A Hands-on Labs 12. 14. investigate some of the other possibilities for omnidbrestore.hp.dat file.dat file in the “db40/logfiles/rlog” directory to obrindex_orig.dat file was created.P. compare the date/time of the new file to the obrindex.com A-86 U1610S B. and what to do if you don’t have the obrindex. Are the files the same or different? 13.dat file that exists in the <OMNIVAR>/db40/logfiles/rlog directory. Verify that the new obrindex. See the man-page for omnidbrestore.dat file is used for the session? 15. such as how to manually replay the transaction logs. . L. Which obrindex. Perform another restore using the omnidbrestore –autorecover command. If time allows.dat. This may be useful to execute at periodic intervals to maintain peak performance after long periods of record add/record delete cycles. Reinitialize the Internal Database: omnidbinit http://education. LAB: Export/Import the Database (optional) Objective: This lab (while no longer necessary) offers some possibilities to export and then re-import data within the Internal Database.com A-87 U1610S B. omnidbutil -writedb -cdb <temp_dir>/omnidb -mmdb <temp_dir>/omnidb Make copies of the indicated dcbf directories as prompted. These cycles are completely normal. The recovery log directory is the <OMNIVAR>/db40/logs/syslog directory. 5. Using the GUI. Make copies of the recovery log directory in case recovery is needed. this includes exiting from all GUI’s since these use a DBSM to connect to the database. Shrink the Physical Size of the Database Files You should have found that while using the various purge methods can reduce the record utilization. . Reduce the disk space that the database is utilizing by the following procedure: (note. Try selecting the various subentities. You should see similar information to that seen with the omnidbutil command. Create a temporary directory (this can be any directory that has sufficient space to contain the Data Protector DB): mkdir /tmp/omnidb (HP-UX) mkdir C:\temp\omnidb (Windows) 2. only valid data). (Purged data will not be written to the ASCII format. 3. Write the Internal Database information into ASCII format into the temporary directory.Appendix A Hands-on Labs 10–6. the actual space used is not. this is not very commonly done) 1.hp.00 2003 Hewlett-Packard Development Company. Make note of how much space the database is currently utilizing: omnidbutil -info 4. L. Expand the Usage tree.P. Make sure that no Data Protector activity is taking place. review database size and record utilization: Bring up the GUI and go to the Internal Database context. but may fragment the database over time. 6. plus information in graphic pie chart form in the Disk Usage tab. Verify that your database is now occupying less disk space: Compare the disk space usage in this output with the previous output. Using the GUI. . omnidbutil -info 11. Stop the Data Protector services. Read the ASCII formatted data back into the empty Internal Database: omnidbutil -readascii -cdb /tmp/omnidb -mmdb /tmp/omnidb Type y to the prompt. and will contain only the default media pool definitions. and copy the msg and dcbf contents back into their original locations. You should see similar information to that seen with the omnidbutil command. 7. expand the Usage tree. review database size and record utilization: Start the GUI and go to the Internal Database Scoping pane.hp. L. All database data will be lost! Are you sure (y/n)?” When the database has been reinitialized. Check the size again using omnidbutil. All data will be lost! Are you sure (y/n)?" 8. "Database import will overwrite old database. 10.P.00 2003 Hewlett-Packard Development Company.Appendix A Hands-on Labs Type y to the prompt “This will initialize Internal Database. From the Objects tab. 9. http://education. View the information in graphics pie chart form in the Disk Usage tab.com A-88 U1610S B. it will be empty. Restart the Data Protector service daemons. Try selecting the various subentities. Mount the logical volume to this new directory mount /dev/vg00/dpidb /var/opt/omni/db40 6.P. L.Appendix A Hands-on Labs Lab 10-7: Move the Internal Database to a New Location (optional) Objective: To relocate the Internal Database to overcome disk space limitations that are encountered over time. . Restart the Data Protector Services /opt/omni/sbin/omnisv –start 9. (A similar procedure may be executed on Windows 2000) 1. Reclaim the disk space consumed by the old database directory.00 2003 Hewlett-Packard Development Company. rm –r /var/opt/omni/db40_save /var/opt/omni/db40 http://education. 10. Create a new db40 directory mkdir /var/opt/omni/db40 5.hp. Create a new logical volume (partition) that is at least 100 MB (for this lab). This lab will be performed on HP-UX where the LVM capability exists. Stop the Data Protector services /opt/omni/sbin/omnisv –stop 3. Verify (using the GUI) that all of the session and media data are present and accessible. lvcreate –L 100 –n dpidb /dev/vg00 newfs –F vxfs /dev/vg00/rdpidb 2. Copy the contents of the “old” database to the new mount point cp –rp /var/opt/omni/db40_temp/* 8. Add the new mount point to the /etc/fstab file mount –p | grep dpidb >> /etc/fstab 7. Rename the “db40” directory mv /var/opt/omni/db40 /var/opt/omni/db40_temp 4.com A-89 U1610S B. Appendix A Hands-on Labs Lab 11: Monitoring and Reporting Objective: The objective of this lab is to learn how to use the command line and GUI to monitor and interact with activities within the cell.00 2003 Hewlett-Packard Development Company. http://education.P.hp. L. .com A-90 U1610S B. just restart it. From the menu bar.P. 4. Select Actions.) The restore session should be left waiting on the mount request. You should see the status of all the backup objects and devices. Start a full interactive backup on your cell manager and a test of a single file restore. What information is provided within the Monitor while sessions are running? • • • • • • 3. 6.hp. At the detail level. Bring up a terminal window or command prompt and issue the following command: omnistat What information is provided? • • • • http://education.Appendix A Hands-on Labs 11–1. L. When the sessions are running. Now. so that you have two sessions running together (this test works best if both sessions request the same logical device. you are monitoring the individual session. What actions are available for this session? 5.00 2003 Hewlett-Packard Development Company. switch to the Monitor context. Double-click on your backup session to explode it to detail level. use the command line interface to get the same information you have just obtained through the GUI. LAB: Monitors 1. close all GUI windows and follow the steps below to use the monitors.com A-91 U1610S B. Start the Data Protector monitor GUI. 2. as well as progress messages. . If the backup should finish before you have finished the lab. What mode are you in now? What commands are available in this mode? Disconnect from the monitor with the appropriate command. View all of the previous sessions in the cell by opening the sessions folder. Only new session messages are displayed. Monitoring the session through to completion using the command line is also possible.com A-92 U1610S B. 8. You will see a list of the previous sessions that have been run in your cell.00 2003 Hewlett-Packard Development Company. Open the Internal Database Context of the GUI . where sessionid is the one reported from the omnistat command (your running test backup). omnidb –session <sessionid> -report You should see very familiar output to the GUI from this command. The command returns to the prompt and gives you a snapshot of the running session and its state at that point in time. it shows the progress of the session as long as the monitor GUI window is open.hp. Try interacting with the session (HP-UX only): Press the Control and C keys together (or whatever the Interrupt keys are). look at the detail level of a particular session. Issue the following command: omnistat –session <sessionid> -monitor You will notice that the command does not return immediately to the prompt as it is waiting for output from the session. This is not the same as the GUI monitor. 9.Appendix A Hands-on Labs 7. Again. Display the session information on the running backup session with the following command.P. not the entire session log. L. Now let's use the GUI to look up information on previous sessions. 10. http://education. . You may have to wait a while before you see a session message. Produce a list of all of the file systems that have backups in the cell: omnidb –filesystem <or> omnidb -winfs http://education.Appendix A Hands-on Labs 11. Find out what media was used by this session: omnidb –session <sessionid> –media 18.P. Open a terminal window on your workstation. .hp. and execute the following command: omnidb -session This gives a listing of previous Data Protector sessions. Double-click on one of the old sessions to see the details of the session. Close the windows for this session. 15. Find out what tapes were used in this session. 12. 16. Display the same information on previous sessions using the command line. Produce a report showing the latest backup session: omnidb -session -type backup –latest 20. 14. as sessions are removed during the database maintenance process.com A-93 U1610S B. L. Try a selective (partial) view of the sessions: Right-click on the Sessions container Select Properties Choose from the “Created” list Choose from the “From type” list Choose from the “Backup Specification” list By what categories are you able to list the sessions? 13. Obtain a listing of the backup sessions run in the last day: omnidb –session –type backup –last 1 19. The listing will contain only “valid” sessions. List all backup sessions for the last week.00 2003 Hewlett-Packard Development Company. Display detail level information on a particular old session: omnidb –session <sessionid> –report 17. Appendix A Hands-on Labs 21.) omnidb -filesystem <object_name> -session <session_id> -catalog omnidb –winfs <object_name> -session <session_id> -catalog Note: the description part of the object name for Windows objects must be enclosed in double-quotes.00 2003 Hewlett-Packard Development Company.com A-94 U1610S B. Produce a detailed report describing what was backed up in the latest session. L. The object name for a file system object is in the form: <hostname>:<mount point> “<description>” omnidb -session -type backup -latest -detail Session ID: ___________________________________________ Object Name: _________________________________________ 22.P. (You will need the session ID and the object name you have recorded.hp. even though the session report shows single quotes! http://education. . Produce a report showing what files were backed up by this session. Record the session ID and one of the object names from the report. 00 2003 Hewlett-Packard Development Company. http://education.Appendix A Hands-on Labs Lab 12: Reporting and Event Notifications Objective: The objective of this lab is to learn how to use the Reporting and Notification features of Data Protector.com A-95 U1610S B. .P. L.hp. .com A-96 U1610S B. Create a report group named “Event_Lab1" a. 2.txt Format: ASCII 3.00 2003 Hewlett-Packard Development Company.hp. Select “show selection criteria in report. Select (right mouse button) the newly created. Choose a name for the report category.” Media: Type: <Any> Description: “my custom media report” Media Condition: <Any> Protection: Any Libraries: Choose any library or jukebox device that you have (dds or file) Media Pools: All media pools Locations: All locations Time Frame: Started within 12 hours Duration: 12hours Send Method: Log Log to File: <system_temp_directory>/custom_media_report1. Switch the Data Protector GUI to the Reporting context. select Add a Report Group… c.Appendix A Hands-on Labs 12–1. select “Preview” to execute the report. a. L. Select Reports using the right-mouse-button. Fill in the name for the report group. b. b. Select the “Reports on media and media pools” report category. Add a second media report to the Event_Lab1 group as follows: Report type: Media Statistics Report Name: “Custom_Media_Statistics” http://education. 5. Select Finish to save the report into the report group. 4.P. Add a report to the Event_Lab1 report group. “custom_media_list. 1. do not schedule the report group yet.” c. LAB: Reporting and Event Notification In this lab you will configure event notifications as well as report groups. P. Choose the Add… button near the bottom of the Results Area. and fill in a time that is within the next 15 minutes f. You may want to schedule it to run at the next closest 15 or 30 minute mark.00 2003 Hewlett-Packard Development Company. and schedule it to run soon). b. Select the report group with the right mouse button. Select Daily. Select “Properties” c. a.Appendix A Hands-on Labs Media: Type: <Any> Description: “Media Summary Report” Media condition: <Any> Protection: Libraries: <Any> “Don’t Care” Media Pools: “All media pools” Locations: “All locations” Time Frame: “No time limit” Send Method: “Log” Log to file: “<system_temp_directory>/custom_media_report2.txt Format: ASCII 6. Execute the report group. g. Using a terminal window view the two text reports that were created 8. L. 7. Select “Ok” at the bottom of the GUI. check the current time. Select the schedule tab in the Results Area. Select Finish to save the report to the report group in the <OMNICONFIG/rptgroups/Event_Lab1 file. Schedule the report group to be run daily. d.com A-97 U1610S B. Select “Start” c.hp. e. . (In other words. Select “Apply” to update the report configuration file in the <OMNICONFIG>/rptschedules/Event_Lab1 file. Select (right mouse button) the Event_Lab1 report group b. a. http://education. Select Add Notification… Name: Notification_Lab1 Event: End of Session Send Method: Use Report Group Report Group: Event_Lab1 Level: Normal Session Status: <Any> c. Notification definitions are stored in the file <OMNICONFIG>/Notifications. Set the thresholds sufficiently low so that the event is triggered. as well as the parameters that control their execution. a. L. Start a backup of some very small object (so it completes quickly).00 2003 Hewlett-Packard Development Company. 13. Examine all of the Notifications that already exist. Create (Add) a new Notification for the database. Re-execute the omnitrig command. http://education. a. Select the Next> button. 12. Name: Custom_Database_Notification Event: Low Database Space Send Method: HP-UX: Email to root @ <cell_manager> Windows: Broadcast to the <cell_manager> system Level: Major Filenames Tablespace Size Limit: 200 Disk Free Threshold: 100 DCBF Size Limit Threshold: 100 b. (/tmp or C:\temp) 11. 14. If no event is sent. notice the default limits and thresholds. The notification should send an E-mail (hp-ux) or broadcast (Windows) to notify root/administrator that the database is nearly out of space. Modify the default event for the Database Space Low that goes into the Data Protector Event Log. check your current disk space utilization and reduce the threshold below that which is currently used to force the execution of the notification. . 15.hp. b. After the backup completes examine the directory to see that the reports were generated by the notification event. 10. Suggestion: backup the temp directory.com A-98 U1610S B. In the Scoping Pane.P. Add the report group as a notification event that will be executed with every backup job. Execute the omnitrig command to trigger the event. Execute the omnitrig –run_checks command to test if the notification sends an alert (email/broadcast). Look at the default notification for the Data Protector Database Space. Look at this file to see how your current (default) notifications are configured. Datalists: <Any> Select Finish.Appendix A Hands-on Labs 9. select Notifications with the right mouse button. Can the entries still be read? Which file contains a record of the past events? Open the file to examine its contents. .com A-99 U1610S B. http://education. What has caused the events to be written to the log? 17.P. L. Clear the events out of the Data Protector Event Log by selecting the Event Log within the Scoping Pane using the right mouse button.00 2003 Hewlett-Packard Development Company.Appendix A Hands-on Labs 16. select Empty Event Log. Examine the Data Protector Event Log for the events that have occurred.hp. L. . 6. Select New -> Virtual Directory 5. Stop the Apache Web Server (if it is running. Save the file and exit the editor.Appendix A Hands-on Labs 12–2. Windows: Create an additional directory alias on the Windows Peer IIS web server: 1.d/hpapache2 2. select Ok. Enter “DP_Report” as the Alias. Select “Default Web Site” 4. Browse and Select the C:\Program Files\Omniback\java\bin directory.d/hpapache2 stop 5. Select Next on the Virtual Directory Creation Wizard. Edit (vi) the /opt/hpapache2/conf/httpd.hp.com A-100 U1610S B. HP-UX: Create an additional alias for the default Apache web server running on port 80. 9. Edit the system file that controls the automatic startup of the Apache Web Server: vi /etc/rc. 8. then Finish.P. Modify the Apache_Start parameter so the value is “one”: APACHE2_START=1 3. Open the Container representing your system. This could be done on any system with the User Interface installed. 3. Select Next. As Administrator select: Start -> Programs -> Administrative Tools -> Internet Services Manager 2.conf and add the following in the Alias definition section of the configuration file (be careful where these lines are added). this may not be necessary if the Apache_Start parameter was 0) /sbin/init. then Next. (or another of your choosing) 7. From the Action Menu. 1. Enable Execute permission in addition to the already selected Read and Run scripts permissions. LAB: Web Server Configuration (basics) Objective: This lab focuses on configuring the Web Reporting capability into a web server so that reports may be viewed from a remote web browser without installing the Data Protector User Interface. Look for the section in the file that starts with: # Aliases: Add here http://education.config. ( you will have to use :wq! to save the file since it is readonly) 4.00 2003 Hewlett-Packard Development Company. Save the file and quit the editor. be certain not to mix this new entry in the middle of an existing definition.com A-101 U1610S B.Appendix A Hands-on Labs There are some existing Alias definitions. Alias /DP_Report "/opt/omni/java/bin/" <Directory "/opt/omni/java/bin/"> allow from all deny from none order allow. Start the Apache Web Server: /sbin/init. L.hp.d/hpapache2 start Accessing the Web Reporting tools: Start Internet Explorer (access either the Windows web server or UNIX web server) Address: http://<FQDN>/DP_Report/WebReporting.deny </Directory> 6. .00 2003 Hewlett-Packard Development Company. 7.P.html http://education. Note that broadcasts can be sent only to NT systems! 2. Test your notification by performing a simple interactive backup of a single file. and click Show. Set the report format to ASCII. use email to an HP-UX system): a. such as mediareport. c. . and press Add. and then enter a Report Name. then click Define and Save Report. Using the Web interface. then Save Report. click Save Notification. expand the Single Session report category and select the Session Media Report. and enter a name for your new report group. Using the Web interface. provided in the Web interface and Data Protector GUI. When you have finished. in the form of a broadcast or email message: a. b. d. L. enter either the hostname for a Broadcast or the email recipient.00 2003 Hewlett-Packard Development Company. then Add Notification. Click Save Report. The outcome is that when any session finishes.Appendix A Hands-on Labs 12–3.hp. Select Notifications. so accept the one that is displayed by default.P. you cannot select a blank session. Select Broadcast or Email. click the Save to New Report Group button. You need to make a modification to the report definition file so that it is not reporting on a specific session (this way it will report on the session it is run for). The report is displayed. In the Send Report To field.com A-102 U1610S B. You will then be asked to select the specific session for which you want to generate the report. notification of this fact is broadcast or emailed to the system specified. such as mediareportgroup. http://education. Fill in the boxes as follows: Name Event type Object Action Parameter Enter a name for your notification End of Sessions <ALL> Broadcast | Email The hostname of the NT system or email address of the HP-UX system. Unfortunately. 1. LAB: (Optional) Additional Notifications This lab focuses on the Notification functions in Data Protector. Log in to the cell using the Web interface. Configure a notification to send a report of the media used when the session completes. configure a notification that sends a Broadcast message to a Windows system (If no NT system is available. com A-103 U1610S B. as it is possible to leave the session name blank. Upon completion of the backup. edit the report group file you just created.Appendix A Hands-on Labs e. .hp. f. http://education. check that you receive either a broadcast or email containing a list of the media that was used. 3.P. Locate the line that contains the session specification. this modification is not required. Notification definitions are stored in the file <OMNICONFIG>/Notifications. Remember that report groups can be used to send a combination of reports upon a notification event. The file should look something like this when edited: NAME "mediareportgroup" { REPORT "mediareport" { ID "session_media" BROADCAST { TYPE ASCII TO "saturn" } } } When using the Data Protector GUI to define the same report. Using an editor. and delete it. L.e. (i. 4. Save the file. Try some notifications of your own using different formats and delivery methods. Look at this file to see what your notification looks like. SESSION “1999/12/09-6”). The file will be named as you specified and located in the <OMNICONFIG>/rptgroups directory.00 2003 Hewlett-Packard Development Company. Now test your notification by running a simple interactive backup of a single file. L.hp.Appendix A Hands-on Labs Lab 14: Security Objective: The objective of this lab is learning how to assign specific privileges to users by using the Data Protector Groups and Users features. .P.com A-104 U1610S B.00 2003 Hewlett-Packard Development Company. http://education. Select the Admin group. Add your new users to groups: Add your first user yourname1 to the Admin group. . L.hp. try executing the Data Protector GUI. Switch to the Users context. 2.” Your new group should now appear in the list of User Groups. 4. Add a new user to the operating system. LAB: Access Control User Configuration Consult your instructor about the possibility of using an existing operating system login in order to bypass step 1. exit Data Protector and then logoff. Fill the boxes as follows: Group Name Description Access Rights Enter the name of your group Student. From the menu bar select: Edit->Add->User Group The Add Group dialog box will appear. then from the menu bar select: Edit->Add->Users http://education. Enter “yourname’s custom group. By default. 3. As the new user. click “Finish. preferably not an administrator. Create a group called Student.00 2003 Hewlett-Packard Development Company.) Be sure to test the login capability of the user before proceeding to the next step. create four new users called <yourname>1 – <yourname>4.” Click on the following radio buttons: Media Configuration Start Backup Specification Mount Request When complete. then start the Data Protector GUI. but an end user or operator level. Add a custom group: Make sure you are logged on as root. you should not have any permission. 1.P.Appendix A Hands-on Labs 14–1. Operator and User.com A-105 U1610S B. and back on as the system administrator. In the Users Scoping Pane you will see the three pre-configured groups Admin. (Using the HP-UX System Administration Manager (SAM) utility. Appendix A Hands-on Labs You will then be presented with the user add screen. (i. that is.e. Click (…) and select the Data Protector group to which you want to add the user. users). Test your Admin group assignment. Does the xomni GUI appear as it did when you ran it from the root user? Do you have access to all the functional areas via the GUI as before? http://education. Enter the hp-ux group or Windows domain that the user belongs to. Login as yourname1 Start the Data Protector GUI as this user: (the PATH to the command may need to be entered) eg: /opt/omni/bin/xomni Does the Data Protector GUI appear as it did when you ran it from the root user? Do you have access to all the functional areas via the GUI as before? Why is this? 6. You can find out the group name by logging on as the user and typing id. Now test your Operator group assignment.com A-106 U1610S B. click “>>”. Click (…) and select the system on which the user resides. Click on UNIX User. Now repeat this process for users yourname2-4. 7. When all boxes are filled. Fill the boxes as follows: User Name Group / Domain Name Real Name Host Name User Group Unix or Windows User Click (…) and select the user you want to add from the list. Admin.P. the list is simply from the /etc/passwd file. Select Finish 5. Exit the GUI and logoff from this user account. assigning the users to the following: User <yourname>2 <yourname>3 <yourname>4 Group Operator User Student When you have added all your users. The list shows all systems in the cell. Test user <yourname>X. L. . Login as <yourname>2.hp.00 2003 Hewlett-Packard Development Company. login as <yourname>3. Does the xomni GUI appear as it did when you ran it from the root user? Do you have access to all the functional areas via the GUI as before? Why is this? Exit the GUI and logoff from this user account. L. Login as <yourname>4.00 2003 Hewlett-Packard Development Company.hp.com A-107 U1610S B. http://education. Now test your Student group assignment. . Now test your User group assignment.Appendix A Hands-on Labs Why is this? Exit the GUI and logoff from this user account.P. Does the xomni GUI appear as it did when you ran it from the root user? Do you have access to all the functional areas via the GUI as before? Why is this? Exit the GUI and logoff from this user account. 9. 8. Complete the following review questions. 00 2003 Hewlett-Packard Development Company. Is there another way to secure your cell from remote restores if the system is HP-UX? http://education. Were you successful? Why? 3. limit access to prevent restores between cells. What if you forget to add yourself? 5. .com A-108 U1610S B.P. Are you successful? Why? 4. Try to restore some of your files into a temporary directory to a cell client that belongs to the other cell team that you’re working with.Appendix A Hands-on Labs Lab 14-2: Access Control and Security Objective: Work with another team using a different Data Protector cell.hp. Were you successful? Why? 2. Secure each cell to prevent outside access to your clients. Be sure to specify your cell manager as a trusted server. 1. Try to perform a backup of any filesystem from the system you restored to. Try importing that other client into your cell. L. Appendix A Hands-on Labs Lab 15: Manager of Managers Objective: To introduce the Multi-manager (M. .00 2003 Hewlett-Packard Development Company.) configuration capabilities of Data Protector.hp.M.P. L.o.com A-109 U1610S B. http://education. working with a partner. Create an empty file in the /etc/opt/omni/cell directory: cd /etc/opt/omni/cell touch mom_info chmod 600 mom_info ll mom_info -rw------.com A-110 U1610S B. Decide whose system will be the MoM cell server. Add the root user of the MoM cell to the admin group so that root can use the xomnimom GUI to manage the remote cell.1 root sys 18 Aug 18 17:07 mom_info Make sure the file has permissions as shown.Appendix A Hands-on Labs 15–1. you will centralize the media management databases so that the MoM client gets its entire media and device information from the MoM server. This file cannot be manually edited. The other system will be the cell server for the client cell: Name of MoM cell server:_________________________________ Name of client cell server:_________________________________ Configure the MoM Manager (HP-UX) Perform these steps on the system that you have selected to be the MoM server: 1. . L. perform the following steps. 7. Stop and restart Data Protector services on the server: /opt/omni/sbin/omnisv stop /opt/omni/sbin/omnisv start 4. Next. you will configure centralized licensing. 5. http://education.00 2003 Hewlett-Packard Development Company.hp. Finally. you will configure one of your systems as the MoM server and the other as a MoM client. This will enable you to share devices and media between cells. LAB: Manager of Managers Objective: In this lab. It will eventually contain the list of managed cell mangers. 2. Add the root user of the MoM cell server to this cell.P. Log on to the cell manager you want to configure as the MoM manager as user root. Add a MoM root User to Client Cells. 3. 6. On the client cell server. highlight Enterprise clients. This results in: The <OMNICONFIG>/cell/mom_server file on the client cell manager system is updated with the name of the Data Protector MoM cell manager system name. Switch to the Clients context.Appendix A Hands-on Labs Select the Admin group. import your client cell manager into the MoM environment: 8.P. Import the client cell manager.. Verify that the imported client cell has been added to the list. 9. and from the pop-up menu select: Import Cell Manager 11. Start the MoM user interface: /opt/omni/bin/xomnimom –cde & This opens the Data Protector-Manager-of-Managers window that provides access to all MoM functionality. http://education.. Enter the fully qualified hostname of the client cell server and click OK. Edit -> Add -> Users.00 2003 Hewlett-Packard Development Company. Set the following: User Name Group Real Name Host Name User Group UNIX / Windows User root sys MoM root user The hostname of the MoM server Leave as Admin UNIX User Click >> when done.hp. L. In the Scoping Pane. 10. The <OMNICONFIG>/cell/mom_info file on the Data Protector MoM cell manager system is updated to include the name of the new client cell manager system. Select Finish when done. The imported cell manager should appear in the list of cell servers on the left of the screen. . Import Cells to the MoM Environment Now.com A-111 U1610S B. and edit the duplicated names of media pools and devices (in the user interface). When complete.com A-112 U1610S B. Example: # /opt/omni/sbin/omnidbutil -mergemmdb blake7 About to start media management database merge from host blake7. Use the GUI to View Information Familiarize yourself with information available through the GUI by selecting the various contexts from the scoping pane. . you must manually change the backup specifications that use these devices to use the new device names... Centralize the Media Management Databases Before sharing can occur. where N represents a number. It is a good idea to add a line to the media pool’s description to indicate from which cell the pool has come... merge the client MMDB with the MoM’s MMDB: /opt/omni/sbin/omnidbutil -mergemmdb client_cell_name This will extract information from the client's MMDB and merge it with the existing MMDB on the MoM server.. "Default Tape" and belonging devices and media .. run the GUI on the MoM server...Appendix A Hands-on Labs 12. you must merge the media management databases of the client cells with the MOM server: As root on the MoM server. 13.00 2003 Hewlett-Packard Development Company. "Default T3480" and belonging devices and media . On the client cell.. "Default SD-3" and belonging devices and media .. Use the system editor to create the /etc/opt/omni/cell/mmdb_server file containing the name of the MoM Manager.P. http://education.hp. "Default T3590" and belonging devices and media . (fully qualified) or simple copy the file mom_server to mmdb_server to create it. "NT Systems" and belonging devices and media . In this case. perform the following: Log on to the cell manager of the client cell as user root or administrator. L. The duplicated names have a “ _N” appended to their name. This always happens to the default pools if they exist in both cells... Are you sure (y/n)?y Merging Merging Merging Merging Merging Merging DONE! pool pool pool pool pool pool "Laptops" and belonging devices and media . select the client cell manager to which to distribute. In the list of cell managers. select the Clients context. . use File -> Update (to obtain the latest configuration change). Try performing a backup of some files from the client system to a device that is located on the manager system (device sharing). L. such as “Fire Safe” and Offsite Storage. perform the following: If xomnimom is already running on the MoM Server.com A-113 U1610S B. try running the Data Protector GUI on the client system and look at the devices and media section (this information is now being supplied from the MoM. highlight “Enterprise Clients” and select Distribute Configuration from the pop-up menu. The configuration file is sent to the client cell manager. select the button for Vaulting.hp. save it by moving to another location: On the MoM server system. From the MoM GUI menu bar. Take a look at the devices and media views for both systems. add some new locations to the <OMNICONFIG>/vault_locations file on the mom server. In the window. however. the MMDB on the client is no longer required. Also. 14. Now that the database has been merged. http://education.00 2003 Hewlett-Packard Development Company. Click Distribute. Use the MoM GUI to Distribute Configuration Data Using vi or another editor.Appendix A Hands-on Labs Stop and restart the Data Protector processes by running: omnisv stop omnisv start Update configuration files on the CMMDB host: omnicc -update_mom_server This pushes the cell_info file to MoM and CMMDB server to <OMNICONFIG>/mom/cell_info directory under CellServer name.P. You should see that they are now the same. Notice how the client cell is now "indented" under the MoM server. you will not be able to distribute the licenses as described below. select the MOM server system and from the pop-up menu. (It should currently be local.com A-114 U1610S B. . L.com Category Number of Licenses Data Protector Cell Manager for HP-UX 1 Data Protector Cell Manager for Windows NT 1 Single drive for UNIX 500 Single drive for Windows NT / NetWare 0 Multi-drive server for UNIX 0 Multi-drive server for Windows NT / NetWare 0 On-line Extension for UNIX 1 On-line Extension for Windows NT 0 Manager-of-Managers Extension for UNIX 1 Manager-of-Managers Extension for Windows NT 0 61-250 Slot Libraries Extension for UNIX 0 61-250 Slot Libraries Extension for Windows NT 0 Unlimited Slot Libraries Extension for UNIX 1 Unlimited Slot Libraries Extension for Windows NT 0 EMC TimeFinder and EMC SRDF 1 Using the MoM GUI.uksr.Appendix A Hands-on Labs Check the contents of the client system's vault_locations file. http://education.hp. Select the Remote mode button. using the following command on the client system: omnicc -query Note that the Licensing Mode is set to Local.) Click OK to the action verification dialog. select the client system by clicking on it. If you have a “real” license proceed as follows: Note that some steps must be performed at the client cell server. Example: # omnicc -query Licensing mode License server : Local : scorpio.hp. configure the client to use Remote (centralized) licensing: From the Scoping Pane.P. If you are using the instant-on license that ships with the product. select: Configure Licensing From the servers list.00 2003 Hewlett-Packard Development Company. 15. Check on the licenses configured for the MOM server. while others are performed on the MoM server. Configure the client cell manager to use centralized licensing by performing the following steps: Check the current status of licensing on the client. stop here. use the appropriate licenses.Appendix A Hands-on Labs At this stage. http://education. and that the license mode is Remote. Also. (i. In the MoM GUI. Click on the About tab to verify that the number of licenses is correct. . click Redistribute. 250) by either typing this in (recommended!). and how may have been allocated to the client system.) When ready. You should now see that zero licenses are available. on the client system. Next.P. set the number of Single Drive for UNIX licenses to be half of that available. Again. and that the license mode is Server. Again. or using the up/down arrows. select an Online Extension license. verify that the number of licenses is correct.hp. Use the MoM GUI to Display License Information Select the MoM cell server from Manager of Managers GUI. You should now see that the licenses have been configured. which indicate how many licenses are available. and that the license mode is now Remote.com A-115 U1610S B. the Type of Licensing screen changes views and shows two columns for each license.e.00 2003 Hewlett-Packard Development Company. you could run the omnicc –query command again on the client system. In the Allocated column. L. 16. select the client cell server. try the omnicc –query command. (If you are using NT. 00 2003 Hewlett-Packard Development Company. .P.com A-116 U1610S B.hp. L.Appendix A Hands-on Labs http://education. 00 B-1 2003 Hewlett-Packard Development Company. .hp.com U1610S B. Configure library devices for use with Data Protector/Omniback. http://education. L.Appendix B HP-UX Library Configuration Objectives Upon completion of this module. you will be able to do the following: • • Create library device configurations in HP-UX.P. Shutdown the system. Sctl is used along with the SCSI interfaces and is in the HP-UX kernel by default. Configuring the DAT Autoloader or DLT Library using the SCTL driver The following procedure can be used to install the connection to a tape library on an HP-UX 11. This procedure will make modifications to your kernel. A. Make sure you have the required driver(s). 1. These are provided as examples. Determine the hardware path for the device Overview: You will need a single scsi id for your device.com . Check if your kernel definition already has the sctl driver installed: # lsdev -d sctl (use the lsdev to list existing kernel drivers) } outp ut if drive r is in Character Block Driver Class the kernel 203 -1 sctl ctl Note: the sctl driver should be in the kernel by default. 6. Create device file(s) for the autochanger/library unit.V) systems or Workstations using HP-HSC. Procedural Outline 1.T. Knowledge of system administration is required.K.N.x system.P. and are somewhat specific to certain systems. 3. Determine the hardware path for the device. 2. HPGSC or PCI interface bus slots for the autochanger/library robotics SCSI connection. 5. http://education. Connect the new device. 1.L.00 B-2 2003 Hewlett-Packard Development Company.D. 2. Check the current bus configurations to find a suitable SCSI adapter: U1610S B.hp. Make sure that you have the required driver: Overview: You should not need to build a new kernel if you have any other device on your system that requires the SCSI PASS-THRU driver sctl. There is also man-page that may help (man 7 scsi_ctl) Installation for a server (A. L.Appendix B HP-UX Library Configuration Following are three procedures that may be used as aids to configure the library robotics along with HP-UX. Test the operation of the device. 4.R. Select one of your SCSI busses. if the device is a DDS Autoloader. We will need this for the device file later.P. A.2.00 B-3 2003 Hewlett-Packard Development Company. . and 2 are used. B.0 stape CLAIMED DEVICE HP HP1533A target 3 8/16/5. and execution of the new kernel.Appendix B HP-UX Library Configuration # ioscan -f -k -C ext_bus Class I H/W Path Driver S/W State H/W Type Description =============================================================== ext_bus 0 8/0 c720 CLAIMED INTERFACE GSC add-on Fast/Wide SCSI Interface ext_bus 1 8/4 c720 CLAIMED INTERFACE GSC add-on Fast/Wide SCSI Interface ext_bus 2 8/8 c720 CLAIMED INTERFACE GSC add-on Fast/Wide SCSI Interface ext_bus 4 8/16/0 CentIf CLAIMED INTERFACE Built-in Parallel Interface ext_bus 3 8/16/5 c720 CLAIMED INTERFACE Built-in SCSI Note: the "I" column (instance number) of the 8/16/5 interface. this will be the SCSI target for the tape drive as well as the autoloader since SCSI lu’s are used for the internal devices within the unit. scan the bus for available addresses: The H/W Path for this example is: 8/16/5 (from a D-class system) # ioscan -f -k -H 8/16/5 Class I H/W Path Driver S/W State H/W Type Description =============================================================== ext_bus 3 8/16/5 c720 CLAIMED INTERFACE Built-in SCSI target 2 8/16/5. # cd / # shutdown -h (power off the system when instructed to do so) http://education. Shut down the system. Note. we will use 4 for the autochanger.7 ctl tgt CLAIMED DEVICE CLAIMED DEVICE Initiator 3 8/16/5.0 sctl C.0. Shutdown the system to allow connection of the new device.0 sdisk CLAIMED DEVICE TOSHIBA CD-ROM XM-5701A target 13 8/16/5.7. On the 8/16/5 bus.com U1610S B. L.2 tgt CLAIMED DEVICE disk 0 8/16/5. The hardware address including the SCSI target of the autoloader will be: 8/16/5.4.hp.0 tgt CLAIMED DEVICE tape 0 8/16/5. For our system the instance number of this interface is a 3. 3. addresses 0. Connect the new device to the halted system Note: If you are using a DDS Autochanger. 203) U1610S B.4. make sure to set the scsi id on the autochanger correctly. C.00 B-4 2003 Hewlett-Packard Development Company.0 tgt sctl CLAIMED DEVICE CLAIMED DEVICE Initiator Note the instance (I) number for the Built-in SCSI: 3 Note the target id of the device: 4 Note the lu of the the Unknown device: 1 the hardware path: 8/16/5. Verify that the sctl driver is in the kernel: # lsdev -d sctl Character Block 203 -1 Driver sctl Class ctl note the “Character (major) number for the sctl driver.2 tgt CLAIMED DEVICE disk 0 8/16/5.1 UNCLAIMED UNKNOWN HP C1557A target ctl 13 8/16/5. and L is the Lun (4 bits). When the system reboots. and the last 8 bits are 00. or 0x034100 in hex where 0xIITL00 is the format and II is the card instance (8 bits) T is the SCSI target (4 bits). 6 hex digits left justified. then power all peripherals on and power up the system last.com . lu 1.0 sdisk CLAIMED DEVICE TOSHIBA CD-ROM XM-5701A target 1 8/16/5.0 stape CLAIMED DEVICE HP C1557A unknown -1 8/16/5.7 3 8/16/5. scan for the new device in the ioconfig: # ioscan -f Class I H/W Path Driver S/W State H/W Type Description =============================================================== ext_bus 3 8/16/5 c720 CLAIMED INTERFACE Built-in SCSI target 2 8/16/5.0 stape CLAIMED DEVICE HP HP1533A target 3 8/16/5.P.4. 4 Scsi Address Autoloader Options 7 Back of HP DDS autochanger device (not on DLT Libraries) A. in our case a 4 should appear in the scsi address window on the back of the device.2. Connect the new device to the system.7.4 tgt CLAIMED DEVICE tape 1 8/16/5.Appendix B HP-UX Library Configuration 4. device 4.4. http://education. The second window for the autoloader options should be set to 7 for HP-UX. 24 bits total. B. L.0 tgt CLAIMED DEVICE tape 0 8/16/5.hp.0.1 becomes card instance 3. 4.1 Class I H/W Path Driver S/W State H/W Type Description =============================================================== ctl 0 8/16/5.00 B-5 2003 Hewlett-Packard Development Company. Manually bind the sctl driver to the device using the ioscan command (this is optional. The utility is used for interacting with scsi changers. configure the Logical Device. We will only need to build a device file for the autochanger unit using the scsi pass-thru device driver. Once the test is verified. target id 4.4.P. Verify the binding from the previous command: # ioscan -f -H 8/16/5.03. a utility that will get installed with the media agent module. zero fill) # mknod /dev/scsi_library c 203 0x034100 B. 1.4. Start the uma utility using the -ioctl option for the new device file: # /opt/omni/lbin/uma -ioctl /dev/scsi_library *** PROGRAM: UMA VERSION: HP OpenView OmniBack II A.1 C. We will use the mknod command for this purpose.50 *** Copyright (C) 1996 Hewlett-Packard Company *** License is restricted for use with licensed http://education. lu 1. Test the operation of the device Overview: HP OmniBack II provides uma (universal media agent). but makes the ioscan output look nicer): # ioscan -M sctl -H 8/16/5. L.hp.1 sctl UNCLAIMED UNKNOWN HP C1557A 6. Gather the information needed to create the device file for for the robotics: Device Name: /dev/scsi_library (any name will work) Device Type: c (for character type devices) Driver Major#: 203 (output from the “lsdev -d spt” command) Device Minor#: 0x034100 (03 from the scsi card.com U1610S B. A. Create the device file(s) for the autochanger/library unit Overview: The tape drive in the autoloader will autoconfigure at reboot time.Appendix B HP-UX Library Configuration 5. We can test the new device file we built in the previous section to be sure that it allows us to pass commands to the autochanger. . P.00 B-6 2003 Hewlett-Packard Development Company. X=Im/Export.com .hp. /dev/scsi_library> inq SCSI Inquiry: Type: 8 Vendor ID: "HP " Product ID: "C1557A " F/W Revision: "U709" /dev/scsi_library> stat Element Status (T=transport.Appendix B HP-UX Library Configuration *** HP OpenView OmniBack II products. S=Storage): 1 D1 Empty "" 2 S1 Full "" 3 S2 Full "" 4 S3 Full "" 5 S4 Full "" 6 S5 Full "" 7 S6 Full "" /dev/scsi_library> exit U1610S B. http://education. L. D=Drive. This procedure will make modifications to your kernel. Create device file(s) for the autochanger/library unit.hp.P.Appendix B HP-UX Library Configuration Configuring the DAT Autoloader or DLT Library using the SPT driver The following procedure can be used to install the connection to a tape library on an HP-UX 11.I. Check if your kernel definition already has the spt driver installed: # lsdev -d spt (use the lsdev to list existing kernel drivers) Character Block Driver Class } output if driver is in 172 -1 spt spt the kernel no output if driver is not in the kernel 2. A. 5.x system.00 B-7 2003 Hewlett-Packard Development Company. Test the operation of the device. 2. Make sure you have the required driver(s). Procedural Outline 1. Make sure that you have the required driver: Overview: You will most likely need to build a new kernel if you have no other device on your system that requires the SCSI PASS-THRU driver or SCSI There is also man-page that may help (man 7 scsi_pt) Installation for a server (E.d/spt. Build a new kernel (if necessary).H. Knowledge of system administration is required. Check if your system has the following file: /usr/conf/master. L.1 bin bin 4270 Nov 6 1997 /usr/conf/master. Connect the new device. .G.com U1610S B. 1. 3. Determine the hardware path for the device Overview: You will need a single scsi id for your device.d/spt -r--r--r-. A. (this indicates the presence of the pass-thru driver on the system) # ls -l /usr/conf/master. Check the current configuration: http://education. Shutdown the system. 6.d/spt B. 7. Determine the hardware path for the device. 4.T.some K’s) systems using HP-PB bus slot for the autochanger/library robotics SCSI connection. 0.5 target CLAIMED DEVICE disk 1 56/52. The hardware address including the SCSI target of the autoloader will be: 56/52.0 target CLAIMED DEVICE tape 2 56/52.Parallel Interface Note: the "I" column (instance number) of the 56/52 interface. if the device is a DDS Autoloader. B.2.0 disc3 CLAIMED DEVICE HP C2490AM C. and 6 are used. skip to section 4.prev U1610S B.P. L. Note.0 disc3 CLAIMED DEVICE TOSHIBA CD-ROM XM-4101TA target 5 56/52.0 tape2 CLAIMED DEVICE HP HP35480A target 3 56/52. Make a backup copy of the sytem configuration file: # cp -i /stand/system /stand/system.Wide SCSI ID=7 ext_bus 1 56/48 scsi3 CLAIMED INTERFACE HP 28696A .Wide SCSI ID=7 ext_bus 2 56/52 scsi1 CLAIMED INTERFACE HP 28655A . Note: this procedure will modify the kernel and system files.6 target CLAIMED DEVICE disk 2 56/52.0 disc3 CLAIMED DEVICE HP C2490AM target 6 56/52.com .6. On the 56/52 bus. If you have determined from step 1 that your kernel does not contain the scsi pass-thru driver. 5. we will use 4 for the autochanger. this will be the SCSI target for the tape drive as well as the autoloader since SCSI lu’s are used for the internal devices within the unit. For our system the instance number of this interface is a 2.5. Select one of your SCSI busses.hp. We will need this for the device file later. proceed as follows.SE SCSI ID=7 ext_bus 3 56/53 lpr2 CLAIMED INTERFACE HP 28655A . Build a new kernel (if necessary) Overview: If your kernel does have the driver in already.00 B-8 2003 Hewlett-Packard Development Company. 2. addresses 0.2 target CLAIMED DEVICE disk 0 56/52. A. http://education. 3. spt.SE SCSI ID=7 target 2 56/52.Appendix B HP-UX Library Configuration # ioscan -f -k -C ext_bus Class I H/W Path Driver S/W State H/W Type Description =============================================================== ext_bus 0 56/40 scsi3 CLAIMED INTERFACE HP 28696A . scan the bus for available addresses: The H/W Path for this example is: 56/52 (from a E-class system) # ioscan -f -k -H 56/52 Class I H/W Path Driver S/W State H/W Type Description =============================================================== ext_bus 2 56/52 scsi1 CLAIMED INTERFACE HP 28655A .4. A. Shutdown the system. # kmupdate 4.0 stape CLAIMED DEVICE HP C1557A unknown -1 56/52.Appendix B HP-UX Library Configuration B. Connect the new device to the system.SE SCSI ID=7 CLAIMED DEVICE target 6 56/52. When the system reboots. then power all peripherals on and power up the system last. Create a new kernel. and execution of the new kernel.P.00 B-9 2003 Hewlett-Packard Development Company. 4 Scsi Address Autoloader Options 7 Back of HP DDS autochanger device (not needed on DLT Library) A. Connect the new device to the halted system note: Make sure to set the scsi id on the autochanger correctly.1 UNCLAIMED UNKNOWN HP C1557A … http://education. B.4 tgt tape 1 56/52. The second window for the autoloader options should be set to 7 for HP-UX. L. in our case a 4 should appear in the scsi address window on the back of the device.hp. # cd / # shutdown -h (power off the system when instructed to do so) 5. . # mk_kernel D.4. # kmsystem -c y spt C.4. Shutdown the system to allow connection of the new device.com U1610S B. Edit the system file to include (configure) the spt driver into the kernel. Schedule the kernel to be moved into place during the next shutdown cycle. scan for the new device in the ioconfig: # ioscan -f Class I H/W Path Driver S/W State H/W Type Description =============================================================== … ext_bus 2 56/52 scsi1 CLAIMED INTERFACE HP 28655A . P. target 4. Verify the binding from the previous command: # ioscan -f -H 56/52. in this case 4.4. target id 4. Manually bind the spt driver to the device using the ioscan command: # ioscan -M spt -H 56/52.hp. lu 1) # mknod /dev/scsi_library c 172 0x024100 B.4. Create the device file(s) for the autochanger/library unit Overview: The tape drive in the autoloader will autoconfigure at reboot time. A. L. device lu 1 C. from the unknown device at 56/52. We will only need to build a device file for the autochanger unit using the scsi pass-thru device driver. and the lu of the robotic 1.1. 172 6.00 B-10 2003 Hewlett-Packard Development Company. http://education. We will use the mknod command for this purpose. in this case “2” note the Target id for the unit.4.1 C.Appendix B HP-UX Library Configuration note the I (instance number) for the ext_bus (SCSI card) for the device. which means SCSI instance 2.1 Class I H/W Path Driver S/W State H/W Type Description =============================================================== spt 0 56/52. Gather the information needed to create the device file for for the robotics: Device Name: /dev/scsi_library (any name will work) Device Type: c (for character type devices) Driver Major#: 172 (output from the “lsdev -d spt” command) Device Minor#: 0x024100 (02 from the scsi card.0 spt CLAIMED DEVICE HP C1557A U1610S B.com . Verify that the spt driver was added to the kernel: # lsdev -d spt Character Block 172 -1 Driver Class spt spt Note: the “Character (major) number for the spt.4. Test the operation of the device Overview: HP OmniBack II provides uma (universal media agent). S=Storage): 1 D1 Empty "" 2 S1 Full "" 3 S2 Full "" 4 S3 Full "" 5 S4 Full "" 6 S5 Full "" 7 S6 Full "" /dev/scsi_library> exit http://education. . X=Im/Export.hp. Start the uma utility using the -ioctl option for the new device file: # /opt/omni/lbin/uma -ioctl /dev/scsi_library *** PROGRAM: UMA VERSION: HP OpenView OmniBack II A. D=Drive.com U1610S B. Once the test is verified. We can test the new device file we built in the previous section to be sure that it allows us to pass commands to the autochanger.00 *** Copyright (C) 1996 Hewlett-Packard Company *** License is restricted for use with licensed *** HP OpenView OmniBack II products. L.Appendix B HP-UX Library Configuration 7.P. /dev/scsi_library> inq SCSI Inquiry: Type: 8 Vendor ID: "HP " Product ID: "C1557A " F/W Revision: "U709" /dev/scsi_library> stat Element Status (T=transport. configure the Logical Device. 1. a utility that will get installed with the media agent module. The utility is used for interacting with scsi changers.00 B-11 2003 Hewlett-Packard Development Company.03. x system.Parallel Interface U1610S B. Shutdown the system. 5.Wide SCSI ID=7 ext_bus 2 56/52 scsi1 CLAIMED INTERFACE HP 28655A . 1. 4. HP-GSC or PCI bus slot for the autochanger/library robotics SCSI connection. http://education. A.com .P. 7. Build a new kernel (if necessary). 3. 6. Knowledge of system administration is required.11 by default) Procedural Outline 1.Appendix B HP-UX Library Configuration Configuring the DAT Autoloader or DLT Library using the SCHGR driver. L. A. This procedure will make modifications to your kernel.00 B-12 2003 Hewlett-Packard Development Company. There is also man-page that may help (man 7 autochanger) Installation for a server systems using HP-HSC. Make sure that you have the required driver: schgr Overview: You will most likely need to build a new kernel if you have no other device on your system that requires the SCSI Autochanger driver schgr. Check the current ioconfiguration: # ioscan -f -k -C ext_bus Class I H/W Path Driver S/W State H/W Type Description =============================================================== ext_bus 0 56/40 scsi3 CLAIMED INTERFACE HP 28696A .hp. Determine the hardware path for the device. (schgr is in 11. The following procedure can be used to install the connection to a tape library on a HP-UX 11. Connect the new device.Wide SCSI ID=7 ext_bus 1 56/48 scsi3 CLAIMED INTERFACE HP 28696A .SE SCSI ID=7 ext_bus 3 56/53 lpr2 CLAIMED INTERFACE HP 28655A . Test the operation of the device. Verify the device file creation. Make sure you have the required driver(s). 2. Determine the hardware path for the device Overview: You will need a single scsi id for your device. Check if your kernel definition already has the schgr driver installed: # lsdev -d schgr Character Block (use the lsdev to list existing kernel drivers) Driver Class no output if driver is not in the kernel 2. com U1610S B. On the 56/52 bus.6 target CLAIMED DEVICE disk 2 56/52.2 target CLAIMED DEVICE disk 0 56/52. this will be the SCSI target for the tape drive as well as the autoloader since SCSI lu’s are used for the internal devices within the unit. # kmsystem -c y schgr C.prev B.P. Build a new kernel (if necessary) Overview: If your kernel does have the driver in already. For our system the instance number of this interface is a 2. B. 2.0.0 target CLAIMED DEVICE tape 2 56/52. and 6 are used. Note: this procedure will modify the kernel and system files.hp.5. Create a new kernel. A. 3. The hardware address including the SCSI target of the autoloader will be: 56/52. if the device is a DDS Autoloader.2.0 tape2 CLAIMED DEVICE HP HP35480A target 3 56/52. 5.0 disc3 CLAIMED DEVICE TOSHIBA CD-ROM XM-4101TA target 5 56/52. Edit the system file to include (configure) the spt driver into the kernel.6.0 disc3 CLAIMED DEVICE HP C2490AM target 6 56/52. we will use 4 for the autochanger. . We will need this for the device file later. proceed as follows. Select one of your SCSI busses. addresses 0. spt.5 target CLAIMED DEVICE disk 1 56/52. skip to section 4.00 B-13 2003 Hewlett-Packard Development Company. Note. scan the bus for available addresses: The H/W Path for this example is: 56/52 (from a E-class system) # ioscan -f -k -H 56/52 Class I H/W Path Driver S/W State H/W Type Description =============================================================== ext_bus 2 56/52 scsi1 CLAIMED INTERFACE HP 28655A .0 disc3 CLAIMED DEVICE HP C2490AM C. L.Appendix B HP-UX Library Configuration Note: the "I" column (instance number) of the 56/52 interface. If you have determined from step 1 that your kernel does not contain the scsi pass-thru driver. Make a backup copy of the sytem configuration file: # cp -i /stand/system /stand/system. # mk_kernel http://education.4.SE SCSI ID=7 target 2 56/52. When the system reboots. Shutdown the system.SE SCSI ID=7 target 6 56/52. Connect the new device to the system. in our case a 4 should appear in the scsi address window on the back of the device. # kmupdate 4. Connect the new device to the halted system note: Make sure to set the scsi id on the autochanger correctly.P. Shutdown the system to allow connection of the new device. L. The second window for the autoloader options should be set to 7 for HP-UX.hp.4. # cd / # shutdown -h (power off the system when instructed to do so) 5.1 schgr CLAIMED DEVICE HP C1557A … C. B. Schedule the kernel to be moved into place during the next shutdown cycle. A.00 B-14 2003 Hewlett-Packard Development Company. then power all peripherals on and power up the system last. http://education.4 tgt CLAIMED DEVICE tape 1 56/52.0 stape CLAIMED DEVICE HP C1557A autoch 1 56/52. 4 Scsi Address Autoloader Options 7 Back of HP DDS autochanger device (not needed on DLT Library) A. 231) U1610S B.4. scan for the new device in the ioconfig: # ioscan -f Class I H/W Path Driver S/W State H/W Type Description =============================================================== … ext_bus 2 56/52 scsi1 CLAIMED INTERFACE HP 28655A . Verify that the schgr driver was added to the kernel: # lsdev -d schgr Character Block 231 29 Driver schgr Class autoch note the “Character (major) number for the schgr.com . and execution of the new kernel.Appendix B HP-UX Library Configuration D. A. D=Drive. Verify the device file creation: # ls -l /dev/rac total 0 crw------. The utility is used for interacting with scsi changers.50 *** Copyright (C) 1996 Hewlett-Packard Company *** License is restricted for use with licensed *** HP OpenView OmniBack II products. . configure the Logical Device.1 bin sys 231 0x024100 Aug 10 13:17 c2t4d1 7. a utility that will get installed with the media agent module.00 B-15 2003 Hewlett-Packard Development Company.com U1610S B. Once the test is verified. Check the device file(s) for the autochanger/library unit Overview: The tape drive in the autoloader will autoconfigure at reboot time along with the autochanger robotics if the schgr driver is loaded in the kernel. Test the operation of the device Overview: HP OmniBack II provides uma (universal media agent). We can test the new device file we built in the previous section to be sure that it allows us to pass commands to the autochanger.03. 1.P.Appendix B HP-UX Library Configuration 6. X=Im/Export. /dev/rac/c2t4d1> inq SCSI Inquiry: Type: 8 Vendor ID: "HP " Product ID: "C1557A " F/W Revision: "U709" /dev/scsi_library> stat Element Status (T=transport.hp. L. S=Storage): 1 D1 Empty "" 2 S1 Full "" 3 S2 Full "" 4 S3 Full "" 5 S4 Full "" 6 S5 Full "" 7 S6 Full "" /dev/rac/c2t4d1> exit http://education. Start the uma utility using the -ioctl option for the new device file: # /opt/omni/lbin/uma -ioctl /dev/rac/c2t4d1 *** PROGRAM: UMA VERSION: HP OpenView OmniBack II A. 4. Test the operation of the device. Installation for a server systems using HP-HSC. 2. Knowledge of system administration is required. Verify the device file creation. Connect the new device. 3.P.00 B-16 2003 Hewlett-Packard Development Company. HP-GSC or PCI bus slot for the autochanger/library robotics SCSI connection. 1. L.0 kernel by default. Make sure that you have the required drivers: schgr and ssrfc Overview: You will most likely need to build a new kernel if you have no other device on your system that requires the SCSI Autochanger Hardware driver schgr and the MO Autochanger surface driver ssrfc. Neither of the previous drivers are in the HP-UX 11. This procedure will make modifications to your kernel. 6. Check if your kernel definition already has the schgr driver installed: # lsdev -d schgr Character Block (use the lsdev to list existing kernel drivers) Driver Class no output if driver is not in the kernel OR # kmsystem -q ssrfc (use kmsystem to list existing kernel drivers) Module Configured Loadable ========================================== ssrfc N # kmsystem -q schgr (use kmsystem to list existing kernel drivers) Module Configured Loadable ========================================== schgr N - U1610S B.com . Make sure you have the required driver(s).Appendix B HP-UX Library Configuration Configuring the MO Jukebox with OmniBack The following procedure can be used to install the connection to a HP MO Jukebox on an HP-UX 11. A. Determine the hardware path for the device.x system. 5. Shutdown the system. 7. Build a new kernel (if necessary).hp. http://education. Procedural Outline 1. 2 tgt CLAIMED DEVICE disk 2 8/16/5. On the 8/16/5 bus. A.0. 3.0 tgt CLAIMED DEVICE tape 0 8/16/5.7 tgt CLAIMED DEVICE ctl 3 8/16/5. spt. scan the bus for available addresses: The H/W Path for this example is: 8/16/5 (from a D-class server) # ioscan -f -k -H 8/16/5 Class I H/W Path Driver S/W State H/W Type Description ===================================================================== ext_bus 3 8/16/5 c720 CLAIMED INTERFACE Built-in SCSI target 5 8/16/5. Make a backup copy of the sytem configuration file: http://education. B.com U1610S B. Determine the hardware path for the device Overview: You will need a single scsi id for your device.2. Check the current ioconfiguration: # ioscan -f -k -C ext_bus Class I H/W Path Driver S/W State H/W Type Description =================================================================== ext_bus 0 8/0 c720 CLAIMED INTERFACE GSC add-on Fast/Wide SCSI Interface ext_bus 1 8/4 c720 CLAIMED INTERFACE GSC add-on Fast/Wide SCSI Interface ext_bus 2 8/8 c720 CLAIMED INTERFACE GSC add-on Fast/Wide SCSI Interface ext_bus 4 8/16/0 CentIf CLAIMED INTERFACE Built-in Parallel Interface ext_bus 3 8/16/5 c720 CLAIMED INTERFACE Built-in SCSI Note: the "I" column (instance number) of the 8/16/5 interface. addresses 0 and 2 are used. For our system the instance number of this interface is a 3. we will use 3 for the autochanger. L. The hardware address including the SCSI target of the autoloader will be: 8/16/5.P. skip to section 4. Build a new kernel (if necessary) Overview: If your kernel does have the driver in already. We will need this for the device file later.0 sdisk CLAIMED DEVICE TOSHIBA CD-ROM XM-5701TA target 9 8/16/5.7. Note: this procedure will modify the kernel and system files.0.0 sctl CLAIMED DEVICE Initiator C. A.3. Select one of your SCSI busses. proceed as follows. .00 B-17 2003 Hewlett-Packard Development Company.hp. If you have determined from step 1 that your kernel does not contain the scsi pass-thru driver.0 stape CLAIMED DEVICE HP C1533A target 7 8/16/5.Appendix B HP-UX Library Configuration 2. # mk_kernel D. A.7 tgt CLAIMED DEVICE ctl 3 8/16/5. Shutdown the system.2.0 tgt CLAIMED DEVICE tape 0 8/16/5. B.0 sdisk CLAIMED DEVICE HP C1113J target 7 8/16/5.2 tgt CLAIMED DEVICE disk 2 8/16/5.00 B-18 2003 Hewlett-Packard Development Company.7.1. Shutdown the system to allow connection of the new device.0 stape CLAIMED DEVICE HP C1533A target 6 8/16/5.0 sdisk CLAIMED DEVICE TOSHIBA CD-ROM XM-5701TA target 8 8/16/5. Connect the new device to the halted system note: Make sure to set the scsi id on the MO Jukebox correctly.0. When the system reboots. and execution of the new kernel.0 schgr CLAIMED DEVICE HP C1100J target 9 8/16/5. Create a new kernel. Verify that the schgr driver was added to the kernel: U1610S B. A. Schedule the kernel to be moved into place during the next shutdown cycle.com .Appendix B HP-UX Library Configuration # cp -i /stand/system /stand/system. # kmupdate 4.3 tgt CLAIMED DEVICE autoch 0 8/16/5. then power all peripherals on and power up the system last.hp. http://education. # cd / # shutdown -h (power off the system when instructed to do so) 5.1 tgt CLAIMED DEVICE disk 3 8/16/5.0 sctl CLAIMED DEVICE Initiator C. Edit the system file to include (configure) the spt driver into the kernel.3.P. # kmsystem -c y schgr # kmsystem -c y ssrfc C. L. Connect the new device to the system.prev B. scan for the new device in the ioconfig: # ioscan -f Class I H/W Path Driver S/W State H/W Type Description ===================================================================== ext_bus 3 8/16/5 c720 CLAIMED INTERFACE Built-in SCSI target 5 8/16/5. P.00 B-19 2003 Hewlett-Packard Development Company. We can test the new device file we built in the previous section to be sure that it allows us to pass commands to the autochanger.Appendix B HP-UX Library Configuration # lsdev -d schgr Character Block 231 29 Driver schgr Class autoch note the “Character (major) number for the schgr.hp. 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 bin bin bin bin bin bin bin bin bin bin bin bin bin bin bin bin bin bin bin bin bin bin bin bin sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys sys 231 231 231 231 231 231 231 231 231 231 231 231 231 231 231 231 231 231 231 231 231 231 231 231 0x033000 0x033013 0x033014 0x033015 0x033016 0x033017 0x033018 0x033019 0x03301a 0x03301b 0x03301c 0x03301d 0x03301e 0x03301f 0x033020 0x033021 0x033022 0x033023 0x033024 0x033025 0x033026 0x033001 0x033002 0x033027 Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan 26 26 26 26 26 26 26 26 26 26 26 26 26 26 26 26 26 26 26 26 26 26 26 26 14:56 14:56 14:56 14:56 14:56 14:56 14:56 14:56 14:56 14:56 14:56 14:56 14:56 14:56 14:56 14:56 14:56 14:56 14:56 14:56 14:56 14:56 16:48 14:56 c3t3d0 c3t3d0_10a c3t3d0_10b c3t3d0_11a c3t3d0_11b c3t3d0_12a c3t3d0_12b c3t3d0_13a c3t3d0_13b c3t3d0_14a c3t3d0_14b c3t3d0_15a c3t3d0_15b c3t3d0_16a c3t3d0_16b c3t3d0_17a c3t3d0_17b c3t3d0_18a c3t3d0_18b c3t3d0_19a c3t3d0_19b c3t3d0_1a c3t3d0_1b c3t3d0_20a 7. Check the device file(s) for the MO Jukebox unit Overview: The tape drive in the autoloader will autoconfigure at reboot time along with the autochanger robotics if the schgr driver is loaded in the kernel. a utility that will get installed with the media agent module.. Once the test is verified. .. configure the Logical Device. The utility is used for interacting with scsi changers.com U1610S B. 1. Start the uma utility using the -ioctl option for the new device file: http://education. L. Test the operation of the device Overview: HP OmniBack II provides uma (universal media agent). 231) 6. Verify the device file creation: # ls -l /dev/rac crw------crw-r----crw-r----crw-r----crw-r----crw-r----crw-r----crw-r----crw-r----crw-r----crw-r----crw-r----crw-r----crw-r----crw-r----crw-r----crw-r----crw-r----crw-r----crw-r----crw-r----crw-r----crw-r----crw-r----. B. 00 *** Copyright (C) 1996 Hewlett-Packard Company *** License is restricted for use with licensed *** HP OpenView OmniBack II products.com .Appendix B HP-UX Library Configuration # /opt/omni/lbin/uma -ioctl /dev/rac/c3t3d0 *** PROGRAM: UMA VERSION: HP OpenView OmniBack II A. /dev/rac/c3t3d0> inq SCSI Inquiry: Type: 8 Vendor ID: "HP " Product ID: "C1100J " F/W Revision: "4.00 B-20 2003 Hewlett-Packard Development Company.hp.P. S=Storage): 0 T1 Empty "" "" 10 X1 Empty "" "" 1 D1 Empty "" "" 2 D2 Empty "" "" 11 S1 Full "" "" 12 S2 Full "" "" 13 S3 Full "" "" 14 S4 Full "" "" 15 S5 Empty "" "" 16 S6 Empty "" "" 17 S7 Empty "" "" 18 S8 Empty "" "" 19 S9 Empty "" "" 20 S10 Empty "" "" 22 S12 Empty "" "" 23 S13 Empty "" "" 24 S14 Empty "" "" 25 S15 Empty "" "" 26 S16 Empty "" "" /dev/rac/c3t3d0> exit U1610S B. L. X=Im/Export. http://education.06" /dev/scsi_library> stat Element Status (T=transport. D=Drive.03. 00 S-1 2003 Hewlett-Packard Development Company.com U1610S B.Solutions to Review Questions http://education.P. . L.hp. hp.com . http://education.P.00 2003 Hewlett-Packard Development Company.Solutions S-2 U1610S B. L. Ultimately the limit has to do with the quantity of data that would be stored in the Data Protector embedded database. Data Protector Architecture 1. however HP recommends keeping the number of systems to 100 or less. . 8. The cell console is a distributed client interface that may be a member of multiple cells. on Windows. is the limit to how many systems may be in an Data Protector cell? The (supported) limit to the Data Protector cell is 1000 systems.com S-3 U1610S B. L.00 2003 Hewlett-Packard Development Company.P. 4. What are the main directories for the Data Protector programs: HP-UX: /opt/omni/lbin for agents and daemons. coordinates data transfer with disk agent 3.Solutions 2–25. What are the names of the 4 main components of the Data Protector architecture? • • • • Cell Manager (Cell Server) Cell Console Disk Agent Media Agent 2. Describe the function of each of the components listed above. How many Data Protector cells can a system be configured in? One 6. the inet server is started by the inetd.hp. • • • • Cell Manager: Maintain the configuration. and any number of disk and media agents. What if any. Which process starts the Data Protector agents? On HP-UX. The omni-inet process starts the agents. Which network port must be available for Data Protector? 5555 7. 5. the database. and control all sessions Cell Console: Provides a graphical and command-line interface Disk Agent: Read/write data to/from the disk. the omni-inet is running as a service (daemon). What is the Data Protector cell comprised of? The Data Protector cell is a logical collection of systems that have their backups centrally managed from a single cell manager. There must be only one cell manager. Media Agent: Read/write data to/from the tape. coordinates data transfer with media agent. /opt/omni/bin for commands Windows: C:\Program Files\Omniback\bin for commands and daemons http://education. The media pool may be used to represent data collections or physical locations of tapes. Media Management Review Questions 1. What is the purpose of a Media Pool? The Media Pool is a logical collection of media within the Data Protector Database. owned by the owner of the backup. 2. 5.00 2003 Hewlett-Packard Development Company. What protection features does Data Protector provide to safeguard the integrity of your backups? • • • Private (ownership) of the data in the database. which have a relatively large number of tapes available for backup.hp. Does the tape need to be loaded into a tape drive in order to change the label or location? S-4 U1610S B. Briefly. How can you change the label on an existing tape? What about the location? Use the Device and Media GUI. The omnimm command may also be used with the –modify_medium option. open a media pool. The media pool provides a mechanism to organize tapes that have a common set of attributes or sets of data. but order is not enforced. Loose: allows for automatic labeling of unused tapes. http://education. Tapes are requested in the allocation order. describe the purpose of these policies. apply changes to label as well as location. strict and loose.com . L. What Media Condition Factors does Data Protector implement? Age and number of overwrites.P. • Strict: forces even usage of media according to the allocation sequence number assigned to the tapes within the media pool. select the tape and then properties. The media pool that uses magazine support will manage the tapes within the magazine as a single unit. Managing media in magazines is more convenient if you routinely change the entire “set” of tapes as a set. The strict policy works best with tape libraries. as well as any unprotected tape to be used for backup. Data Protector provides two media allocation policies. When will you want to use Magazine Support? Magazine support is intended for small tape autochanges. Data Protector will expect the tapes within the magazine to be always in the same positions (slots) within the magazine. Media Retention (session level protection) to prevent media overwrite CRC (Cyclic Redundancy Check) written to the backup by the logical device 3.Solutions 6–18. • 4. 6. and does the media have to be loaded? Removes all of the protection for all sessions on an individual tape. . It may be possible to change the status of a tape by using the media verification process for Data Protector. The entire tape is not formatted.com S-5 U1610S B. 9. 12. This would be necessary if the catalog retention time expired. The only exception to this is the use of file media. When initializing media. then the media verify may restore the tape to a good status. Data Protector will automatically initialize blank media. TRUE or FALSE? Explain. and then you wanted to browse the (file level) contents of a particular tape. What does recycle do to media. and then restore the data. which are limited by the size specification. TRUE or FALSE? False.00 2003 Hewlett-Packard Development Company. http://education. 11. The media import process reads the header and catalog sections from the tape to restore data into the Data Protector catalog database.hp. If Data Protector detects data written in one of the formats that it recognizes it will fail to initialize the tape without the use of force. 13. Force will not overwrite a tape that is still under protection within the current cell. or dirty tape drive. as long as the media policy is loose. just the header. True. you can create another media pool and simply move the media that is marked as poor to the new pool. TRUE or FALSE? False.Solutions No! 7. If a tape was marked as poor because of a device failure. What must be done before Data Protector can use media? The tape must have an Data Protector header written to the tape. Data Protector uses this only for media reporting. The medium does not need to be in the drive for this operation 8. or formatting. TRUE or FALSE? Explain. When is force required? Force initialization is needed if the tape was previously used for another purpose. L. the size in megabytes set by specify or determine specifies the hard limit as to how much data it will hold. What happens during a media import? Explain why this would be necessary. you export it. To remove bad media from a pool. 14. Data Protector supports Vaulting. By default. this is called initialization. 10.P. hp.00 2003 Hewlett-Packard Development Company.P.Solutions True.com . using the location and multiple media pools you have a lot of flexibility in locating tapes in off-site locations. L. http://education. S-6 U1610S B. 00 2003 Hewlett-Packard Development Company. What command can be used to get a listing of all the logical devices in your cell? omnicellinfo -dev 9.P.hp. Logical Device Review Questions 1. or the HP-UX command MC. 7. barcode scan reads the barcode cache from tape library. What HP-UX driver does Data Protector use to control the robotics of library devices? HP-UX? SCSI autochanger (schgr) or SCSI pass-thru (sctl or spt) Windows? SCSI 4. . Describe the purpose of “Scanning” media? Scanning reads the tape header to identify the tape within the drive. this attempts to keep the tape drive streaming for maximum performance. http://education. 6. 5. 3. What Data Protector utility can be used to check communication with a library device before you configure it as a Logical Device? The “universal media agent” UMA.Solutions 7–26. What command can be used to create and modify logical devices? omniupload: reads a configuration file and uploads it into the database. What is the purpose of the “Mount Prompt Script”? External notification when the mount request state occurs. What is the purpose of the advanced option “Concurrency”? Concurrency allows multiple disk agents to write to a single media agent in parallel. L.com S-7 U1610S B. What is the difference between a “scan” and a “barcode scan”? Scan reads the tape header. What Data Protector device type would you use to configure a single DLT drive? Standalone 2. 8. The library controller understands the drive sequence. the logical device should use the same lock name. If you were able to. such as without hardware compression. The lock name is never “required. S-8 U1610S B. or use a different physical device configuration. What is the purpose of the Lock Name advanced option? Does Data Protector ever require it? If so. 14. why would you create more than one logical device for a single physical device? See answer in question 12 above.Solutions 10.hp.com . Each time a physical device is used again.” but device failures may result if it is needed and not used. Is it possible to have more than one logical device that maps onto the same physical device? True.00 2003 Hewlett-Packard Development Company. The drive index is the physical drive number within the library. Data Protector will lock logical devices using the lock name to prevent multiple opens of the same physical device. L.P. when? The lock name is needed if a physical device is configured with more than one logical device name. http://education. 13. The “Drive Index” is related to the SCSI address of the drive. 12. This is useful if you want to configure a single device with more than one set of Data Protector properties. not the host device file name. What command can be used to perform a “scan” of the media in a device? omnimm –repository_update <logical_device> 11. True/False? False. Name three types of objects Data Protector database UNIX file system Raw disk Windows file system Windows configuration (registry and recovery data) 6.P. . In brief terms. describe the advantages of Load Balancing. What is an object? Something that can be accessed by the disk agent for backup. L. What is a backup specification? A text file containing the 4 components listed above. or file may be an object. directory.hp. 7.com S-9 U1610S B. such as Oracle. 4. What are the four fundamental components of all Data Protector backups? • • • • Defaults Objects Devices Options 3. What command is used to perform a backup from the Data Protector command line interface? omnib 2. What is the purpose of setting the Ownership of a backup specification? To control the access from the restore users. A File system. Objects are balanced across the number of running devices to keep the drives running at their http://education.00 2003 Hewlett-Packard Development Company. Backup Review Questions 1. The backup specification is stored in the <OMNICONFIG>/datalists directory. Load balancing allows Data Protector to dynamically select devices for backup. 5.Solutions 8–35. and to allow 3rd party backup products to have access to the appropriate data. and may be edited with a text editor. The backup specification pre-exec runs first. http://education. then all of the object level executions.hp. 9. 11. 13. What is the purpose of a Template? The template allows for a set of defaults to be saved and used to define a backup job.00 2003 Hewlett-Packard Development Company. What is the meaning of Concurrency? Concurrency is multiple disk agents writing concurrently to a single media agent. What is the purpose of a Group? The backup specification group allow for organization of backup specifications.Solutions requested concurrency. When is it beneficial to use software compression? Software compression is useful when network bottlenecks are affecting the performance of backup. L. S-10 U1610S B. What are the differences between object level and backup specification level pre and post execution? Backup specification pre/post execution allows for a pre/post backup job control. 12. The object level scripts execute before and after individual objects.com . Load balancing allows Data Protector to work around failed devices by simply allocating the next available device. then finally the backup specification pos-exec executes last. 10.P. What is the purpose of pre and post execution? Pre/post execution allows for the automation of tasks before and after backup jobs. similar to a directory structure within a file system. or backup is affecting network performance. 8. What does a point in time restore mean? Selecting an individual object from any available version from the database. What is the difference between a normal restore and a parallel restore? Parallel restore allows for the reverse of the backup concurrency to be used to restore objects by making a single pass through a tape.P. http://education. When performing a restore. The level of detail available in the restore file browser depends on what factors? The detail level designated in the backup specification: log all. log file or no log are possible.00 2003 Hewlett-Packard Development Company. Data Protector allows for session level restore or object level restore based upon the objects that are previously backed up. TRUE/FALSE? False. (not commonly used anymore) 3. log directory. Regularly performed backups can be saved as Backup Specifications and scheduled via the Data Protector scheduler. 5. Yes. describe the limitations. only on HP-UX HFS file system.hp. 4. Normal restore may make several passes through a tape for the same data. The same functionality is available with Data Protector Restores. Data Protector will put together the restore chain of all of the needed media to perform the requested restore. restore missing files from tape onto disk 7. Major. 2. how would you suppress Warning messages? Choose the report level Minor. L. 6. Is it possible to restore a single file from a Rawdisk backup? If yes. . Restore Review Questions 1.com S-11 U1610S B. Describe the behavior of the Merge.Solutions 9–16. Overwrite and No Overwrite options: • • • Merge: restore missing files and newer files from tape onto the disk Overwrite: restore everything selected from the tape onto the system No-overwrite. or Critical when the restore session is started. By default. TRUE/FALSE? True. and then restarted after the data is restored. Give an example of a use for the pre/post-exec facility for restores: The pre-exec may be used to stop applications processes prior to restore of data.P.Solutions 8. What is the difference between Exclude and Skip? Exclude requires a full path. 10. 12.00 2003 Hewlett-Packard Development Company. L.hp. unmounting is always the best practice. Restore Into: change the location of a restored item 9. 11. Is it possible to restore a file backed up on one system to a different system? Must the system be a member of the same Data Protector Cell? The restore of data is only limited by cell access. and is a specific object. What is the difference between the Restore As and Restore Into options? Restore As: change the name of a restored item.com . even disk agents in remote cells. S-12 U1610S B. In order to perform a valid Rawdisk backup of a file system. the file system must first be unmounted. any cell manager may restore data onto any system that contains a disk agent. Skip allow for wildcards and may be anywhere within a file system. http://education. List three types of data that are stored in the Data Protector internal database. meta) Recovery index Transaction logs 5. Which database files are likely to be the biggest in the database.com S-13 U1610S B.dat: all of the pathnames of files that are backed up. What are their names? • • mmdb cdb 3. such as data from a tape that was overwritten. What does the term invalid mean when describing records in the database? Obsolete data ready to be purged. 6.hp.P.dat file by using the omnidbutil –extendfnames command. Name 5 parts of the Data Protector Database that are external to the tablespaces: • • • • • DCBF (detail catalog) SMBF (session messages) SIBF (server-less integrations. and what information do they hold? • Fnames. Under what directory is the Data Protector database located? • <OMNNIVAR>/db40 2.00 2003 Hewlett-Packard Development Company. L. Database Review Questions 1.Solutions 10–32. What does the term purging mean in relationship to the database? • • Marking data as obsolete via the GUI or omnidb command Removing obsolete data from the database 7. 8. http://education. The Data Protector internal database is comprised of two tablespaces. . What would you need to add to your database to increase its capacity beyond the 2-GB limit? An additional fnames. • • • Media pools File names Devices 4. Which option can be set in a backup to reduce the amount of detail information stored in the database? • The logging option. What command would you use to perform a thorough consistency check of the database? • omnidbcheck -extended 14. By default. S-14 U1610S B.dat (3.5version only) all of the file versions now kept in the DCBF. What combinations of commands are required to shrink the database? • • • omnidbutil –writedb … omnidbinit omnidbutil -readdb 15.P.hp. L. What command can be used to display information about database size and utilization? • • omnidbutil –info omnidbutil -extendinfo 16. TRUE/FALSE? False! Backing up the database as a file system will not be able to be restored as the database because it is open at the time of the backup. or no log. 9. according to the DailyMaintenanceTime global option. 10. http://education. Which file do you edit to change the purge schedule? • The global options file in <OMNICONFIG>/options/global 11. an automatic database purge takes place every day at midday. The database can be backed up as a normal file system. What variables in the <OMNICONFIG>/options/global file relate to the purge process? • • • DailyMaintenanceTime KeepObsoleteSessions KeepMessages 12. log directories.00 2003 Hewlett-Packard Development Company.Solutions • fvers. log file. 13.com . TRUE/FALSE? TRUE. 22. When should archiving be enabled? After one full backup cycle. to minimize the amount of archiving necessary when updating the filenames catalog. What action is performed automatically.ini.00 2003 Hewlett-Packard Development Company.P. before a backup of the database? omnidbcheck 18. as they are no longer needed.com S-15 U1610S B. What files are needed in order to recover a database? The obrindex. change ARCHIVING=1 21. .Solutions 17.dat and the transaction logs. Where are the transaction logs kept? <OMNIVAR>/db40/logfiles/syslog 20. How can archiving be enabled for the database? Edit the <OMNIVAR>/datafiles/catalog/velocis. What happens to the archive logs when the database is backed up? The archive logs are deleted. Where are the Data Protector configurations stored for: • • • • Backup Specifications: <OMNICONFIG>/datalists Backup Schedules: <OMNICONFIG>/schedules Logical Devices: mmdb tablespace Media Pools: mmdb tablespace http://education.hp. 23. L. 19. Solutions 11–25. Upon completion of a backup job. 4. Which file is used to store notification definitions? <OMNICONFIG>Notifications 6. For what events can notifications be generated? • • • • Database Internal Events Device Events Backup Events 2. TRUE/FALSE? TRUE. Broadcasts can only be sent to NT/Windows systems. http://education.P. More than one notification can be configured for the same event type. Notifications Review Questions 1. L. TRUE/FALSE? TRUE 5. What send methods are available for notifications? • • • • • • Email Log to file External program execution Broadcast to a windows system (net send) Event log file Execute a report group 3.00 2003 Hewlett-Packard Development Company. Why would you want to send a notification to a report group? This would be useful as notification that a session has finished.hp. several reports may be executed. S-16 U1610S B. you can have several different notifications configured for each event type.com . TRUE or FALSE? TRUE 5. What are the three default user groups? • • • Admin reserved for the Data Protector administrators Operator. L.P. http://education. What is the purpose of the Data Protector user groups? Controlling access to functional areas within the Data Protector GUI. and delegating capabilities to non-administrator users.Solutions 13–15.hp.com S-17 U1610S B. this file on HP-UX systems may be used to control access to applications that use the inetd to start their services 7. 2. UNIX and NT users can be added to the same Data Protector group. designed for end users capability to restore their own files 3. What is the allow_hosts file used for? To control (allow or prevent) remote cell managers from accessing the disk agent for restore.00 2003 Hewlett-Packard Development Company. Any user in the Admin group may run backup and restore? TRUE 6. Which two files store the Data Protector group and user assignments? • • <OMNICONFIG>users/Userlist <OMNICONFIG>users/ClassSpec 4. Security Review Questions 1. The /var/adm/inetd. TRUE or FALSE? FALSE. designed for full backup and restore capability User.sec must be modified for normal Data Protector operations. . TRUE/FALSE? False. Name four reasons for implementing Manager of Manager? • • • • Central Administration Central Licensing Central MMDB Shared Devices between cells 2. separation is not possible.M. Why? The remote cell managers must be able to access the Central MMDB to be able to perform backup.Solutions 15–12.hp. Each cell manager maintains its own catalog database. http://education. What configuration information can be distributed from the MoM GUI when using the Distribute Configuration function? • • • • User configuration Holidays Global options Vaulting locations 5. TRUE/FALSE? False. the license is required for each manager that will participate in the MOM configuration. M. Review Questions 1. why must a “license move” request be submitted to the password center? To obtain a consolidated password from all of the cell managers to put in a single license file on the cell manager. When using a centralized media management database.com .P. When using MoM. 6. A merged database can easily be unmerged. S-18 U1610S B.00 2003 Hewlett-Packard Development Company.O. the catalog databases can also be merged. 8. 3. the MoM system should be highly available. 4. TRUE/FALSE? TRUE. When implementing centralized licensing in an existing environment. What command is used to merge the media management databases? opmnidbutil -mergemmdb 7. once the database is merged. L. A special license must be purchased before MoM can be used. MoM only allows the media database to be merged.