Daily Opscenter Activities “Netbackup”

This document helps you with the basic steps to be taken when we get an Opscenter Alert .

This explains the first action point, in case the issue again comes we need to create an incident ticket and
inform the US team.

1. Error Code – 196

Reason of Failure - client backup was not attempted because backup window closed

Details of Failure - this backup failed because it did not get triggered inside its defined backup window

Action 1 - Locate parent job and restart backup.

a) From the alert check the Node name - that is the master server where the backup has failed.
b) Check the client name for which backup has failed.
c) Check the backup policy name.
d) Now restart the failed backup job from the Opscenter.
e) Go to Monitor -> Policies
f) Select the master server ( it will show you the policies only for that master server )
g) Select the Policy and Click "Manual Backup"
h) Select appropriate schedule and client name and hit ok.

i) You also have to check the schedule for which backup has failed.
j) Rerun the backup according to defines schedule .

2. Error Code – 13
Reason of Failure – File read failed
Details of Failure – There are many reasons for this failure, eg . the file size may be very very
small or the file has corrupted.

Action 1 - Follow steps same as above ( for error code 196)

3. Error Code – 58
Reason of Failure – Can’t connect to client
Details of Failure – This failure occurs due to communication issue between master & the client .

Action 1 - Follow steps same as above ( for error code 196)

4. Error code – 96
Reason of Failure – No media available for backup
Details of Failure – Either there are no scratch tapes available or the existing tapes are frozen.
 Action 1 –
1. Check in opscenter if there is any media in “frozen” or “suspended” state; if yes unfreeze or
unsuspend the media and try rerunning the backup once .
Monitor -> Media
2. If again the backup fails with same reason inform to US team.
3. If more than 10 alert phone US On-call with Master Server and Robot information during off
hours or notify Netbackup team during on hours to assure this is picked up immediately..
(Note***Job policy empty in alert or listed as UNKNOWN signifies a failure to mount on
Vault or duplication. We will receive other alerts for these from Netbackup Vault itself)

5. Error code – 800

Reason of Failure- resource request failed
Details of Failure – backup failed to get the requested tape drive

Action –
a) Go to Monitor -> Devices
b) See if the drives are UP .
c) In case you see any drive “down” shown as Red arrow , make it UP
d) If more than 5 alerts in a row phone US On-call with Master Server and Robot information
during off hours or notify Netbackup team during on hours to assure this is picked up
immediately.
6. Error code – 84
Reason of Failure- media write error
Details of Failure – backup fails due to writing on the particular media

Action –
1. In this also please check if the media used in the failed backup job is frozen ( then
unfreeze it )
2. If failure repeats please inform US team

7. Netbackup master services failure alert –

Reason of Failure- If one or more of the netbackup services have stopped we will get an alert
through Opscenter .
Action –
a) Check which service has failed from the alert .
b) Select that master server from the list.
c) Start that service from Opscenter.
d) If does not restart monitor jobs to verify if they begin to fail from console. Phone US On-
call with Master Server and service failure information during off hours or notify
Netbackup team during on hours to assure this is picked up immediately.
8. High % Job Failure Alert –
Reason of Failure- This alert will only alert if 20% of all jobs on the masters begin to fail at
once.
Action –
a) First assure there is no planned change or outage causing this.
b) If not in Opscenter locate the Master Server causing the issue.
c) Verify Error codes.
d) If not in Opscenter locate the Master Server causing the issue. Verify Error codes. Phone
US On-call with Master Server and service failure information during off hours or notify
Netbackup team during on hours to assure this is picked up immediately.
9. Down Tape Drive Alerts –
Reason of Failure- Drive has went to down status
Action –
a) Locate down drive in Opscenter and attempt to up drive.
b) If unable to up drive open ticket to the US team for investigation.
10. Frozen tape alerts –
Reason of Alert- Track and update in excel spread sheet all the frozen tapes then tell
onshore to unfreeze them
Action – Inform US support team to unfreeze the frozen media

11. Monitor scratch tapes in all the Backup servers

12. Monitor the cleaning media alerts
Reason of Alert- If the tape drive needs cleaning this alert comes.
Action –
a) Check in opscenter for the frozen media and unfreeze it as shown before .
b) Monitor -> Media
c) If again the backup fails with same reason inform to US team.

13. Follow up with Symantec vendors for any backup failure issues and inform onshore
team on follow ups

14. Monitor EDL Alerts.

15. Monitor catalogue alerts.

Reason of Alert- If the catalog backup ( backup of netbackup master database ) fails it will
generate the alert .
Action –
a) Locate the catalog backup job in the Opscenter as per the alert and do its manual backup .
b) If the issue still exists inform the US support team.