Académique Documents
Professionnel Documents
Culture Documents
Agenda
Introduction Purpose & Assumptions History Terminology and Concepts Architecture Standards How Backups Work Managing NetBackup Client Implementation and Configuration Policies Troubleshooting Reporting Monitoring Overall Environment Shutdown/Restart NetBackup Tips and Tricks Education/Further Reading Q&A
KEEPING PEOPLE AND INFORMATION CONNECTED
Assumptions
Presentation assumes 6.5.3 Vague familiarity of NetBackup Know how to access environments Windows and/or Unix admin experience Please write down your questions for the Q&A session at the end
History
Corporate 1987 - proprietary software solution written by engineers at Control Data for Chrysler Corp. 1993 - renamed to BackupPlus (bp prefix) Late 1993 - OpenVision acquisition (/usr/openv/ install path) and rebranded product NetBackup 1997 - Veritas acquired OpenVision 2005 - Symantec acquired Veritas Version 1993 BackupPlus 1.0 (Control Data) 1994 NetBackup 1.6 (OpenVision) 1996 NetBackup 2.0 1997 NetBackup 3.0 (Veritas) 2000 NetBackup 3.4 2002 NetBackup 4.5 2003 NetBackup 5.0 2005 NetBackup 6.0 (Symantec) 2007 NetBackup 6.5
KEEPING PEOPLE AND INFORMATION CONNECTED
Start Window time when a backup can START Frequency how often the backup should execute Retention length of time backups are valid Policy grouping of like clients sharing similar attributes
KEEPING PEOPLE AND INFORMATION CONNECTED
Master Server
FC Switch Fabric A
Meta-data Nework
Disk Storage
Media Server 1
Media Server 2
Media Server 3
Media Server N
Backup Network
FC Switch Fabric B Enterprise Class Tape Library
Client Hosts
KEEPING PEOPLE AND INFORMATION CONNECTED
Standards
Infrastructure Server/OS Types
Unix Solaris 10 T2000 Naming Standards Defined Network Configuration Standards (Metadata, backup, mgmt)
Robot Types
LTO3/4 Tape Drives / Media Types Volume Serial Numbers (VolSers/bar codes) SAN connectivity Disk Array Standards DSSU Configuration Application/Configuration Documented on LiveLink
KEEPING PEOPLE AND INFORMATION CONNECTED
Quantum Scalar i2000 STK SL8500 Small Robots for legacy restores
Robots media currently in robot Standalone tapes no longer associated with robot/volume group Inventory Robot Ejecting media States Active, Full, Frozen, Suspended, Imported
KEEPING PEOPLE AND INFORMATION CONNECTED
Devices
Drives Robots
SCSI Robots have single Control Host ACS any server can control
Host Properties
Master Server Media Servers Clients Include/Exclude Lists Server authorization
Catalog
Offline backup (legacy method) Import images Verify Images Duplicate images
Reports Vault option that processes and tracks volumes sent offsite
KEEPING PEOPLE AND INFORMATION CONNECTED
Policies (Demonstration)
Policies - A backup policy allows the admin to configure how and when backups are to be performed for a group of clients. This group of clients share similar backup requirements (type, backup window, retention, etc.)
Attributes
Policy Type Destination
Classification Storage Unit Volume Pool
Check Points Limit Jobs per Policy Job Priority Media Owner
Active/Inactive Follow NFS Cross mount points Compression Encryption Collect DR Info Allow Multiple Data Streams Keyword Phrase Snapshot Client
Policies (contd)
Schedules
Attributes Tab
Name Type of Backup Full, Incremental, Differential, Cumulative., User Synthetic Schedule Type Calendar Based Frequency Based
Destination Multiple Copies Override Policy Storage Override Policy Vol Pool Override Media Owner Retention Media Multiplexing Start Window Tab
Defines when backup can START Defines when backup cannot run Only available when calendar sched type chosen Retries allowed after runday Specific Days or Recurring Days
Calendar Schedule
Policies (contd)
Clients Know hardware/OS type Backup Selections what to backup
ALL_LOCAL_DRIVES System_State:\ or Shadow Copy Components:\ NEW_STREAM for multistreaming
Manual backups
Troubleshooting
MSS Document When in doubt, ASK! Windows client Troubleshooting
Windows Clients Over 3000 servers across all environments 77% of all servers 85% of all failures
Error Codes Media related (8x) Network Communication related (4x) Configuration/Hardware related (5x) Most Common Codes:
41, 196, 5x, 219, 13, 14, 2x
Search error message on Google and Symantec Test recommended solution Lather, rinse, repeat Last resort/time sensitive open case with Symantec (800) 342-0652 Customer Number 3680-5196-9875
The connection is being reset internally to the host. Recommendation is to reload the NIC driver or replace the NIC. Error 41 can also produce TCP 10054 errors in the logs, but this is an external closing of the connection. These can be caused by loss of network connectivity, crashes or reboots. Error 41 has also been the result of corrupted VSS. Check the Event Log for any related error messages and consult with Systems Engineers, if necessary
Maximize logging values for client Verify log dirs created in <install>\netbackup\logs\* bpbkar bpcd tar Start backup/restore Review logs searching for errors (look for <4> <8> <16> <32>) Search error message on Google and Symantec sites Test solution Repeat until resolved Open case with Symantec (800) 342-0652 Cust. #: 3680-5196-9875
Reporting
NetBackup Reports Aptare
In depth historical reporting and trending Supports several backup products, incl. TSM Command Center Dashboard Job Reports The Dot Report Dont agitate the Dots Billing yes we can be a profit center IF we are successful Media Reports
Startup netbackup start Resume/Restart all jobs Start Aptare Verify environment functions
Suddenly, There's not half the files there used to be. And there's a milestone hanging over me. The system crashed, so suddenly.
I pushed something wrong, What it was, I could not say. Now all my data's gone, And I long for yesterday-ay-ay-ay. Yesterday, the need for back-ups seemed so far away. I knew my data was all here to stay, Now I believe in yesterday.