Veritas NetBackup Inspection Method

tar -tvxf xxx.tgz

4.1 Inspection Requirements

Status Check

Backup Policy Check

Backup Data Check

Backup Device Check

4.2 Backup Software Status Assessment

1. Confirm Network Connectivity

Server cannot connect to port 13782

nbu processes are running

2. Confirm Library Hardware is Normal

Check for logs via the library panel

3. Test Backup Management Software Interface

Manage backup devices via GUI

Backup policies

Manage tapes

Task monitoring function

Report function

4. Check Library and Tape Drive Status

Click device monitor in the GUI

Or run vmoprcmd -d

Check tape drive status; all drives must be in UP state

If any are DOWN, select UP for that drive in the GUI

Or use vmoprcmd -up <device_index>

In an SSO environment, the vmdareq command does not display SCAN_HOST

Execute netbackup stop; netbackup start to restart processes, or

Via the GUI, select 'restart media manager daemon'

In an SSO environment, if mmcrawl reports an issue with a specific host, on that machine

View the library configuration information and parameter files

# vmoprcmd -d
# tpconfig -dl

5. Check Tape Status

Execute the available_media command; ensure sufficient tapes are in ACTIVE or AVAILABLE state. View media via the GUI.

# available_media

6. Confirm Robotic Arm Functionality

Open the media management GUI and select robot inventory to update tape configuration information.

Ensure consistency by updating NetBackup records.

If displayed correctly

inventory & update for TLD(0) on bkup_pc2650

7. Check Backup Status

Start activity monitor

Click activity monitor in the GUI; the job column displays current and completed backup jobs.

#bpdbjobs | grep ndmp_ENG_vol
#bperror -all -jobid 22289 -U > /usr/openv/tmp/flh/bperror.log

The most critical information is in the state and status columns.

Check the state: active indicates a job is running; done indicates a job has finished.

The elapsed column and %complete indicate how long the backup job has been running

Check the status; it should be 0. If any other status appears, it is abnormal.

#bpdbjobs -summary

8. Check backup performance and backup window

activity monitor

9. Check historical backup reports

netbackup management-> report

10. Backup the NetBackup catalog database

# bpdbjobs -summary
# nbemmcmd -listhosts
# nbemmcmd -getemmserver
# nbemmcmd -listsettings -machinename szcnbu1
# more databases.conf
# bpgetconfig

11. Clean tapes

On the library panel, check command->I/O station to see if a cleaning tape has been used.

12. Display current backup processes using bpps

/usr/openv/Netbackup/bin/bpps -a

13. Check database archive log space

Failure to back up database logs in a timely manner can cause the log space to fill up, leading to database failure. A check of the database log space is required.

For each host backing up the database, use bdf or df -k to confirm sufficient log space. Also, verify via the output of the NBU database backup script that logs are being deleted normally after backup.

14. Backup and check bp.conf and vm.conf

# more bp.conf

15. Collect overall host information

# bpstulist -L -U
# bpplclient

Display the backup policy list using bppllist

# bppllist -U -allpolicies

Backup data validity

Use available_media to confirm the status of all tapes

Check /usr/openv/netbackup/db/media/errors to identify which tapes have I/O errors

Use the verify function to validate backups of critical tapes