1 / 32

NetBackup Shared Storage Option

Learn about SAN components and architecture, hardware and software configuration and testing, common problems, rules of thumb, plans for the future, and references for Veritas NetBackup Shared Storage Option.

davidmcdowell
Télécharger la présentation

NetBackup Shared Storage Option

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NetBackup Shared Storage Option VERITAS Bill.Coleman@veritas.com

  2. Agenda • SAN Components/Architecture • Hardware Configuration & Testing • Software Configuration & Testing • Common Problems • Rules of Thumb • Plans for the Future • References

  3. Enabling Technology Application Host A Media Server MM Daemons (avrd) (ltid) (vmd) (tldd) Host Bus Adapter Application Host B Media Server MM Daemons (avrd) (ltid) (vmd) (tldd) (tldcd) Host Bus Adapter Hardware Connection

  4. FC Tape Tape SAN Components Application Host Host Bus Adapter Fibre Channel FC-AL Hub or Switched Fabric Fibre Channel Fibre Channel Bridge SCSI

  5. Specific Hardware Connections

  6. Hardware Testing • Determine the physical drive within robot • Connect tape drives to SCSI adapters • Record physical configuration • Record adapter • SCSI address • Fibre Channel Logical Unit Numbers (LUN) • Create device files manually or automatically depending on OS (ex. boot -r) • Ensure tape drive is visible to Operating System (ex. mt -f /dev/rmt/0 status)

  7. Physical to Logical Mapping # /usr/openv/volmgr/bin/sgscan /dev/sg/c2t1l0: Tape (/dev/rmt/21): "Quantum DLT4000" /dev/sg/c2t2l0: Tape (/dev/rmt/18): "Quantum DLT4000" /dev/sg/c2t4l1: Tape (/dev/rmt/19): "Quantum DLT4000" /dev/sg/c2t4l2: Tape (/dev/rmt/20): "Quantum DLT4000" /dev/sg/c2t5l0: Tape (/dev/rmt/12): "QUANTUM DLT7000" /dev/sg/c5t0l0: Changer: "ADIC Scalar 1000" /dev/sg/c5t2l0: Tape (/dev/rmt/13): "QUANTUM DLT7000" /dev/sg/c5t3l0: Tape (/dev/rmt/14): "QUANTUM DLT7000" /dev/sg/c5t4l0: Tape (/dev/rmt/15): "QUANTUM DLT7000" /dev/sg/c5t5l0: Tape (/dev/rmt/16): "QUANTUM DLT7000" /dev/sg/c6t2l0: Changer: "STK 9738" /dev/sg/c6t3l0: Changer: "STK 9730"

  8. Media Manager Configuration

  9. Adding a New Shared Drive

  10. Naming Shared Drive

  11. Robot Controlling Shared Drive

  12. Completing SSO Configuration

  13. Reconfigure Existing Drive

  14. Changing SSO Configuration

  15. Adding Another Server to SSO

  16. Adding Host/Changing Drive Path

  17. Logical Tape Drive Shared Name

  18. Completing SSO Configuration

  19. SSO Wizard Flow

  20. tpconfig # /usr/openv/volmgr/bin/tpconfig -d Index DriveName DrivePath Type Multihost Status ***** ********* ********** **** ********* ****** 2 s1kd1 /dev/rmt/12cbn dlt Yes DOWN TLD(55) Definition DRIVE=1 3 s1kd2 /dev/rmt/13cbn dlt Yes UP TLD(55) Definition DRIVE=2 Currently defined robotics are: TLD(55) robotic path = /dev/sg/c5t0l0, volume database host = sunflower

  21. Configuration Analyzer

  22. Configuration Error

  23. Analyzer (mmcrawl) • Common errors found are: • Inconsistent robotic paths • Shared drive with different robot drive numbers • Daemons cannot communicate • All daemons not running • Duplicate robotic definitions (robot control on only one host) • Drive configured as both shared & dedicated • Storage unit not defined for each media server • Using tpconfig instead of configuration wizards • Not testing drive paths on every Media Server

  24. Number of Drives in Cluster

  25. Software Testing • Start NetBackup & Media Manager daemons on server controlling robotics • Identify Device Allocator (volmgr/bin/vmdareq) • Use volmgr/bin/robtest to verify each server can access all tapes & drives • Test each Media Server accessing drives separately • Run volmgr/bin/tpreq to write/read tape • Use Device Monitor to verify mounting status • Use vmdareq or Java Device Monitor status in Drive Summary report

  26. Definitions • Scan host - media server monitoring tape drive (avrd). Only one host in a shared drive configuration monitors a particular tape drive. If scanning host is unavailable, scan host moves to another Media Server. Each tape drive could have a different scan host. • Device Allocator - media server controlling access to shared drives. This is the same host has the Media Manager volume database host for the drive. Typically there is one volume database host for a site, therefore one DA can manage multiple robotics connected to many Media/Master servers.

  27. Daemons Application Host A Media Server MM Daemons (avrd) (ltid) (vmd) (tldd) Host Bus Adapter Application Host B Media Server MM Daemons (avrd) (ltid) (vmd/DA) (tldd) (tldcd) Host Bus Adapter Voldb Data Path Control path Hardware Connection Data Path

  28. Device Allocation #/usr/openv/volmgr/bin/vmdareq -h host1 drive1 - AVAILABLE hostA SCAN_HOST hostB drive2 - AVAILABLE hostA SCAN_HOST hostB #/usr/openv/volmgr/bin/vmdareq -h host1 -unavailable -H host1 drive1 - AVAILABLE hostA hostB SCAN_HOST

  29. Common Problems • Not installing SSO software on each server • Forgot to add VERITAS tape-config-list entries into /kernel/drv/st.conf (Solaris) • No configuration entries for fast/wide adapter cards in sg.links and sg.conf files (Solaris) • Forgot to manually add device file (Tru64) • Did not use Berkeley-Style close on tape path • Using outdated firmware in Hub, Switch, HBA, Bridge (rapid change) • Configuring same robotic path on every server - only single server controls robot • Forceload sg/st/fcaw drivers on Solaris • Set JNI failover to “0” seconds to avoid I/O hangs (working with bridge/HBA vendor fix)

  30. Rules of Thumb • Ensure hardware and SAN configuration is understood and stable before configuring NetBackup Media Manager • Configure one host to have Volume database for multiple servers or masters • Test backup/restore with dedicated tape drives before sharing • Start sharing with a small number of tape drives between 2-3 Media Servers • Try to duplicate Storage Area Networking issues with native Operating System usage • Mixing SAN components adds risk (ex. GBIC or Host Bus Adapter)

  31. Plans for the Future • Improved configuration automation of tape drives, robotics and shared tape drive (SSO) configurations • Automatic configuration of serialized peripherals starting with NB3.3 (not SSO) • Continued testing (ex. Compaq) • Frequently Asked Questions (FAQ) • Improved documentation on Verifying a SSO Configuration • Continue supporting configurations beyond what is tested • More VERITAS product interoperability testing in SAN configurations

  32. References • 3.2 Media Manager Device Configuration Guide (100-001009A) • Chapter for each specific Operating System • 3.2 Media Manager System Administrator’s Guide (100-000986A) • Appendix B (page 310) Multihosted Drives • Chapter 2 Configuring Storage Devices (page 37) • 3.2 NetBackup Troubleshooting Guide (100-001046A) • Appendix A Functional Overview • Appendix B Networks & Hostnames • Appendix C Robotic Test Utilities • NetBackup 3.2 Shared Storage Option White Paper • http://www.veritas.com/library/pi/SSO_SAN_WP.pdf • NetBackup 3.2 Datasheet • http://www.veritas.com/products/nbux/datasheet.html • NetBackup 3.2 SAN Tested Matrix • http://dept-slo.veritas.com/prodman/products/products/netbackup/netbackup/supported_platforms.htm

More Related