Veritas NetBackup 8.

2: Administration

Lesson 4: Performing File System Backups

© 2019 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC
or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.

This is the Performing File System Backups lesson in the Veritas NetBackup 8.2:
Administration course.

4-1
Lesson introduction
• Lesson 0: Course Introduction • Lesson 10: Performing VMware Restores
• Lesson 1: Introducing NetBackup • Lesson 11: Protecting Hyper-V environment
• Lesson 2: Configuring NetBackup Storage • Lesson 12: Duplicating Backups Using Storage
• Lesson 3: Configuring Policies Lifecycle Policies
• Lesson 4: Performing File System Backups • Lesson 13: Managing and Protecting the
NetBackup Catalog
• Lesson 5: Performing File System Restores
• Lesson 14: Optimizing File System Backups
• Lesson 6: Configuring Disk Pools
• Lesson 15: Collecting Logs and Diagnostic
• Lesson 7: Configuring Media Server Deduplication
Information
• Lesson 8: Configuring and Managing Tape Storage
• Lesson 9: Performing VMware Backups

This lesson is the fourth lesson in this course.

4-2
Lesson objectives
Topic Objective
Using and customizing the Use and customize the Activity Monitor, and suspend, resume,
NetBackup Activity Monitor restart, and prioritize jobs.
Performing manual backup Initiate a manual backup job, and monitor backup jobs using the
operations Activity Monitor.
Configure and perform user-directed backups using the Backup,
Performing user-directed backups
Archive, and Restore console.

Backup job-related tips Identify common backup job-related status codes.

The table on this slide lists the topics and objectives for this lesson.

4-3
 Topic: Using and customizing the NetBackup Activity
Monitor

After completing this topic, you will be able to use and customize the
Activity Monitor, and suspend, resume, restart, and prioritize jobs.

This is the Using and customizing the NetBackup Activity Monitor topic.

4-4
Monitoring jobs using the Activity Monitor
Icon Legend
Successful
Partially
successful
Active
Queued
Failed
Incomplete
Suspended

• Shows completed jobs < 78 hours old

• Customize with KEEP_JOBS_HOURS = hours
bpdbjobs

The Jobs tab within the Activity Monitor provides a listing of jobs that are queued, are
currently running, have completed successfully (status code 0), have completed partially
successfully (status code 1), or have failed. The Activity Monitor periodically deletes
completed jobs that are more than three days old (specifically any completed jobs older
than 78 hours). To keep jobs in the Activity Monitor longer than the default value, for
example by changing the timeframe from 78 hours to 192 hours, use one of the
following methods:
• On a Windows or UNIX master server, run the command:
echo KEEP_JOBS_HOURS = 192 | nbsetconfig
• On a UNIX master server, add the entry “KEEP_JOBS_HOURS = 192” to the
/usr/openv/netbackup/bp.conf file.
Alternatively, note that you can view older jobs in the NetBackup report found under
NetBackup Management > Reports > Status of Backups. The Status of Backups report
does not show job details, and only specific types of jobs, such as backup jobs. For
additional settings and details, refer to the NetBackup Administrator’s Guide.

4-5
Customizing the Activity Monitor

You can use the Activity Monitor in the NetBackup Administration Console to monitor
and control NetBackup jobs. To display job information, in the NetBackup
Administration Console, click Activity Monitor. Summary information about all jobs is
displayed under the Jobs tab in the details pane. By default, not all columns are
displayed. The following procedure describes how to show or hide columns:
1. In the Activity Monitor, select View > Column > Layout. The Column Layout dialog
box is displayed.
2. Select the column to display or hide by selecting its heading from the list.
• Click Show to display the column.
• Click Hide if you do not want to see the column heading.
3. To change the order in which the columns appear, select the column heading. Then,
click the Move Up or Move Down button to reorder the columns. Columns can also
be reordered from within the NetBackup Administration console by simply using
drag and drop.
4. Click OK to apply the changes.

4-6
Filtering jobs in the Activity Monitor

Show / hide
custom filters

Show all jobs Show filter

and clear results
applied filters

Filtering jobs in the Activity Monitor simplifies troubleshooting and reporting. For
example, you can filter for jobs that were started before a specific date, queued jobs, or
jobs with status completion codes within a specified range. The Filter dialog box can be
viewed in by accessing the View > Filter menu option, or by clicking on the Show or
Hide Custom Filter button in the top-right corner of the Activity Monitor. Clicking on the
View All button clears currently applied filters and displays all original rows again. To
create a filter:
1. In the Activity Monitor, show the custom filter pane, as shown on the slide.
2. Click Create, and in the Create Filter dialog box provide a name for the filter.
3. Under the Advanced tab, select the Field, Comparison, and Value desired.
4. Click Add to List to add your selections to the filtering criteria.
5. Click Save to create the filter. The filter is immediately applied.
You can edit an existing filter operation with the Edit button. Once the filter is modified,
save the filter by either choosing Save or Save And Apply Filter. There is also
functionality to export and import filters as a binary file, to share frequently used filters
with other hosts and users.

4-7
Controlling jobs

A NetBackup administrator can cancel a job at any time from both the Activity Monitor
and from the command line. A NetBackup administrator can suspend a job that has
checkpoint restart enabled. In the example on the slide, Suspend Job is greyed out, this
means the job cannot be suspended as there are no checkpoints enabled in the policy
or if enabled a checkpoint hasn't been reached. Jobs cancelled “cleanly” as described
here, exit with NetBackup status code 150 (termination requested by administrator). If
you cancel a scheduled backup job, but the number of retries is not yet exceeded and
the backup window is still open, the backup is reattempted. Also, note that after you
cancel a backup job, the cancellation process can take several minutes. For example, if
the backup is being written to tape, the tape must be rewound and unmounted before
the cancellation process is fully completed.

4-8
Understanding job priorities

• Determines which job is assigned available backup

resources.
• Apply to new and queued jobs only (have no effect
on active jobs). Job priority
range is
• Set in these locations:
0 – 99999
– Default: Host Properties > Master Server > Default
Job Priorities
– Policy: Policy > Job priority
– Dynamic: Activity Monitor > Action > Change Job
Priority

Job priorities provide a method to help determine which jobs get available resources.
This can be used to help administrators prioritize certain high priority clients and data
against other clients with a lower priority. Job priorities can be set as a default value for
different job types in the policy, before the job runs, or on jobs that have already been
added to the Activity Monitor in NetBackup. The NetBackup Resource Broker (nbrb)
uses the job priorities to determine which job is assigned available backup resources, in
addition to other factors, such as multiplexing requirements. The NetBackup resource
broker re-evaluates resource requests every five minutes, or when triggered by an
external event, such as a resource release.
In Master Server Properties > Default Job Priorities, you can set the default job
priorities for different job types. The Default Job Priorities host properties list 18 job
types and the configurable default priority for each. The job priority range is 0–99999.

4-9
Setting specific job priorities
Can be set on backup policy Can be set on queued or running jobs

10

This slide shows how to set job priorities on a policy and on running jobs. Note that
although you can change the job priority of a running job, because it has already
started, this priority has no effect. However, if the job fails, and then gets re-queued for
another attempt, it is re-queued with this new priority.

4-10
Checkpoint restart
Configured under the Policy Attributes tab

ckpt1 ckpt3 ckpt5 ckpt7 ckpt9 ckpt11 ckpt13 ckpt15 ckpt17 ckpt19 ckpt21 1
Backup fails
ckpt2 ckpt4 ckpt6 ckpt8 ckpt10 ckpt12 ckpt14 ckpt16 ckpt18 ckpt20 ckpt22
The job is marked
as incomplete

HOURS
HOURS
SS
TT EE 3
AA 11 22 33 44 55 66
NN Job is
RR DD
TT
done

2 Job resumes
Job starts from the point in the file system ckpt22 ckpt24 ckpt26 ckpt28
indicated in the last checkpoint: “ckpt22”
ckpt23 ckpt25 ckpt27

11

The Take checkpoints every check box indicates whether NetBackup takes checkpoints
during backup jobs based on this policy at the frequency indicated. Taking checkpoints
during a backup is beneficial in the event that a backup based on this policy fails.
Without Take checkpoints every enabled, a failed backup based on this policy is
restarted from the beginning of the job. By taking checkpoints periodically during the
backup, NetBackup can retry a failed backup from the last checkpoint rather than
restarting the entire job.
The number of times that NetBackup automatically reattempts a failed backup is
configured by the Schedule Backup Attempts property located in the Master Server
Properties > Global Attributes dialog box. Policy types MS-Windows (for Windows
clients) and Standard (for UNIX clients) support checkpoints for backup jobs. Job types
that do not support checkpoint restart include catalog backups, duplication jobs, Vault
jobs, import jobs, synthetic backup jobs, and most database agents.
Note: Any of the database agents would not support a Checkpoint restart functionality,
it’s basically supports the OS file level type backups.
How often NetBackup takes a checkpoint during a backup is configurable. The
administrator determines on a policy-by-policy basis how to balance more frequent
checkpoints with the likelihood of less time lost in resuming a backup because of more
checkpoints. The default is checkpoints every 15 minutes. The minimum supported
value is every 5 minutes, and maximum is every 180 minutes (every 3 hours).

4-11
Resuming a suspended or incomplete job

Configured under master server

host properties > Clean-up

12

To resume a suspended or an incomplete job:

1. In the NetBackup Administration Console, open the Activity Monitor and click the
Jobs tab.
2. Select the suspended or the incomplete job you want to resume. Only backup and
the restore jobs that contain checkpoints can be suspended.
3. Select Actions > Resume Job.
Note that if incomplete jobs are not resolved after 3 hours, by default, their state
changes from Incomplete to Done. This settings can be changed in the master server
host properties under the Clean-up tab. A screenshot of that setting is shown on the
slide.

4-12
Checkpoint restart limitations

Windows system
• No checkpoints are taken.
state backup

Disk-image (raw)
• No checkpoints are taken.
backup

NTFS single-instance • No checkpoints are taken after NetBackup encounters an NTFS

store (SIS) single-instance store.

NTFS resumed • Archive bits cleared for files backed up after the resume.
incremental backup • Archive bits not cleared for files backed up prior to the resume.

13

The following are checkpoint restart limitations:

• No checkpoints are taken during the backup of a system state or shadow copy
components on a Windows client.
• No checkpoints are taken during a disk-image (raw) backup.
• No checkpoints are taken for the remainder of the backup after NetBackup
encounters an NTFS single-instance store (SIS).
Single-instance store is an architecture designed to maintain duplicate files with a
minimum of disk, cache, and backup media overhead. For more information on NTFS
single-instance store, see the Knowledge Base on the Microsoft Web site at
https://technet.microsoft.com/en-us/library/dd573308%28v=ws.10%29.aspx.
On a Windows client's NTFS file system, when a differential incremental backup is
resumed and then completes successfully, the archive bits are cleared for the files
backed up since the resume, but not for the files backed up prior to the resume. This
means that the files backed up prior to the resume are backed up again on the next
differential incremental backup.

4-13
 Topic: Performing manual backup operations

After completing this topic, you will be able to initiate a manual backup job,
and monitor backup jobs using the Activity Monitor.

14

This is the Performing manual backup operations topic.

4-14
How backups are initiated
Automatic
• Initiated based on the policy schedule
• Can be on a calendar or frequency-based schedule

Manual (immediate)
• Initiated from the NetBackup Administration Console
• Initiated from OpsCenter
• Initiated from command line on a NetBackup server

User-directed
• Initiated by users or scripts on the client
• Performed on authorized NetBackup clients only

15

Backups can be initiated:

• Automatically, based on the policy schedule.
• Manually from the NetBackup Administration Console, OpsCenter or command line
on a NetBackup server.
• By users or scripts, from authorized client servers. This type of backup is not
initiated by an automatic schedule.

4-15
Manual backups
What are manual backups?

• Backups performed on automatic schedules (not user-directed schedules).

• Do not require an open start window.
• Run by NetBackup administrators, or by an external scheduler.
• Also known as immediate backups.
• May be mistaken for user-directed backups.

When to run manual backups?

• Testing a configuration.
• Resubmitting a missed or failed backup.
• Preserving an old configuration prior to upgrading.

How to run manual backups?

• Using the NetBackup Administration Console, OpsCenter or bpbackup -i

16

A manual backup (sometimes called an immediate backup) is a manual submission of an

automatic policy. NetBackup administrators can invoke manual backups, assuming that
an appropriate policy has been defined. Do not confuse manual backups with user-
directed backups:
• Manual backups are performed from the NetBackup server by the backup
administrator and apply only to automatic schedules.
• User-directed backups are performed from the client machine.
A manual backup is not dependent on the policy’s backup window or the time specified
by the schedule. That is why it is also called immediate. In fact, you can create a policy
schedule without an open window and run only manual backups defined by that policy,
as needed.
Since you can invoke a manual backup outside a policy’s normal backup window, a
successful manual backup job can affect a frequency-based schedule because it qualifies
as a successful backup. Consider that frequency-based schedules are based on the
amount of time (frequency) since the last successful backup job. This may therefore
mean that an automatic backup does not run when you next intended it to.

4-16
More backup jobs can start (one job per client per second)
Current limitation of Jobs

• Current “limitation” is 86,400 jobs in a 24 hour period (actual number is lower due to the system load).
• Currently, each new Job is tagged with a UNIX time incremented per second, per Master.
• Mostly customers will not notice a change. Customers are not coming close to this threshold value.

From 8.2 onwards

• From NetBackup 8.2 onwards more backup jobs can start, one job per client per second.
• In 8.2 jobs are tracked, one job per client per second within a time stamp, vs. per Master server.
For example: Internal testing has run +- 362,000 jobs per day.
• If required, this option can be reverted to the older requirement.
• Tuning options are being developed for customers to enable this requirement.

17

This slide displays the information about NetBackup 8.2 and onwards, more backup jobs
can start: one job per client per second.
Note:
• The default parameter is DBM_NEW_IMAGE_DELAY, you can modify this value to
it’s default settings: DBM_NEW_IMAGE_DELAY = N
o Where N > 0 and N <=1000, and N is the time in milliseconds to sleep after each
image creation. If N <= 0, no delay is performed. If N > 1000, only 1000
milliseconds (1 second) delay is used.
• Setting the DBM_NEW_IMAGE_DELAY = 1000 value approximates the previous
requirement.

4-17
Performing a manual backup using the Administration Console

bpbackup -i

18

To initiate a manual backup from the NetBackup Administration Console:

1. From the object tree pane of the NetBackup Administration Console, expand
NetBackup Management and select Policies.
2. In the All Policies pane, click the policy name and select Actions > Manual Backup.
Alternatively, right-click the policy and select Manual Backup.
The Manual Backup dialog box is displayed.
3. Select a schedule and the clients you want to back up.
• If you do not select any schedules, NetBackup uses the schedule that runs least
often. For Automatic schedules, the Frequency is generally used. If there are
multiple equivalent candidates, then schedule with the highest retention level is
chosen. It is therefore recommended to explicitly specify the schedule that you
wish to use.
• If you do not select any clients, NetBackup backs up all clients.
• If a User schedule exists, they are not displayed in the schedules list and cannot
be manually backed up because they do not have a backup selection list (the user
selects the files). These types of backups are run from the client system, either by
an application or script, or an administrator (user).
4. Click OK to start the backup.

4-18
Verifying successful completion of backup jobs

Status Code Icon Description

0 The backup was successful.

1 The backup was partially successful.

157 A checkpoint backup was suspended manually.

Any other status code A backup has experienced a problem.

Any other status code A checkpoint backup has experienced a problem.

19

You can expect backup success to be the norm in a properly configured and well-
maintained NetBackup environment. NetBackup is a very robust application in terms of
detecting and reporting errors, therefore, when problems do occur, you should be able
to track them down and correct them quite reliably.
A status code 0 (and the accompanying success icon:) I in the Activity Monitor
indicates that a backup job has completed successfully. Any other status code or icon
indicates that a backup was only partially successful or has failed. There are other
methods by which you can determine if a problem has occurred with a backup job,
including reports and activity logging.
A status code 1 (and the accompanying partial success icon:) in the Activity Monitor
indicates that the job has partially succeeded. For file system backups, this could mean
that some of the targeted files did not get backed up. It could be only one file was
missing, or many files, and there is no indication how important these missing files are.
Look at the job details for information on which files are not included. If those files are
not important (such as temporary or cache files that aren’t needed for recovery),
consider excluding them from future backups, so that you instead complete with status
code 0. Using Windows VSS or other snapshots may fix these issues.
Other reasons may exist for status code 1 backups, and for application and database
backups, a status code 1 may indicate a larger problem, and may result in the inability to
perform restores.

4-19
Viewing job details in the Activity Monitor

20

To view the details for a specific job, double-click the job under the Jobs tab. The Job
Details dialog box is displayed. Detailed job information is contained under three tabs:
• Job Overview provides a high level view of the job.
• Detailed Status lists the step by step actions performed during the job. Under the
Detailed Status tab, a Troubleshooter button is available to launch the
Troubleshooter, which can help determine the cause of the problem and
recommend corrective actions.
• Job Hierarchy shows the job hierarchy, discussed in more detail on the following
slide.

4-20
Viewing job hierarchy in the Activity Monitor

21

Hierarchical jobs, when one job is a parent of one or more child jobs, is a behavior seen
frequently with Storage Lifecycle Policies, snapshot jobs, catalog backup jobs, and many
other job types. The Activity Monitor in the NetBackup Administration Console can
optionally show a hierarchical job view. There is a button on the toolbar which enables
this functionality, or you can select View > Jobs in Hierarchical Manner from the menu
bar to toggle this view.
You can get this information by moving the Parent Job ID column, which by default is
placed to the far right, close to the Job ID column. In this way, you can see the job
associations. However, the hierarchical job view makes this easier to visualize. The job
hierarchy can also be seen in the Job Hierarchy tab of the job details.

4-21
Viewing jobs with multiple attempts

22

In some cases backup jobs may initially fail, but then, when retried by NetBackup, they
succeed in a future attempt. You are able to see the details for each job attempt in the
Detailed Status tab of the job details. Simply use the up and down arrows to the right of
the Attempt field. The slide displays one of these cases, where the first attempt to run a
backup job resulted in a status code 157: suspend requested by Administrator. The
second attempt at running the job succeeded and exited with a status code 0.

4-22
 Topic: Performing user-directed backups

After completing this topic, you will be able to configure and perform user-
directed backups using the Backup, Archive, and Restore console.

23

This is the Performing user-directed backups topic.

4-23
User-directed backups
What are user backups?

• Initiated from the client host.

• Specify the files and folders to be included in the backup.
• Enabled with a User Backup schedule in the policy.
• Enabled only for clients configured in the policy.
• Have storage type and retention level as configured in the policy.

When to run user backups?

• To regularly back up a customized selection of files on a system, manually.

• To initiate backups using a script on the host or client system.

How to run user backups?

• Using the Backup, Archive, and Restore interface or using bpbackup

24

A user-directed backup is invoked by an operator on the client machine either by using

the Backup, Archive, and Restore console, the command line or by running a script. This
type of backup is ad-hoc and can be initiated at any time as permitted by the start
window defined in the user backup schedule. Although the term user backup or user-
directed backup is commonly used, operations are most likely performed by client
administrators, or system administrators on the behalf of users, and a more suitable
description is client-directed or application-directed backups. However, the term “user-
directed” is used throughout the documentation.
The policy must have a user backup schedule that defines the start window during
which users can initiate a backup. The client must be in the policy’s client list. Users
select files and directories to back up. NetBackup ignores the policy’s backup selections
list. Clients can obtain status information using progress logs, e-mail notifications, and
the activity monitor. User-directed backups and archives can be initiated by:
• An interactive user, such as a file owner, system administrator, or DBA by using the
BAR console, or NetBackup commands.
• A backup script launched at regular intervals.
• An event trigger that kicks off a backup script.

4-24
Setting the user schedule and client list for a user-directed backup

Backup Selections is ignored

25

User-directed backups require a backup policy that contains a User Backup schedule,
and the client names added into the Clients tab of that policy. Consider the following:
• When you establish a user backup schedule, you provide users with a start window
during which they can perform their own backups or archives. Users can start
backups and archives only during the times permitted under the schedule’s Start
Window tab. When you set the start window, consider the times that users typically
are at work and likely to need to initiate user-directed backups. If a user starts a
backup outside of this window, the backup job fails.
• User backup schedules can be included in a policy that contains automatic backup
schedules. If you create separate policies for user backups, the considerations are
similar to those for automatic backups. Jobs running user backup schedules ignore
the policy’s backup selection list. The files backed up are specified as part of the
request to run the backup job at the time the request is made by the user.
• The policy name you choose is significant. By default, NetBackup alphabetically
searches (uppercase characters first) for the first available policy with a user backup
schedule with an open backup window, and a matching host name under the Clients
tab of the policy. If no user backup schedule is found, the backup fails with a status
code 240: no schedules of the correct type exist in this policy.

4-25
Initiating a user-directed backup from the BAR console

26

Users can initiate backups and archives using the Backup, Archive, and Restore interface
on the client machine. These operations can be performed without administrator
intervention, and the user does not need to log on to any of the NetBackup servers.
When performing user-directed operations using the NetBackup BAR console, only files
for which the logged-in user has rights are shown. Perform the following steps to start a
user backup operation:
1. From the BAR console, click Select for Backup.
2. Select the desired files and folders for backup by selecting the check box to the left
of the file or folder. To mark all files and folders that currently appear, select Edit >
Mark Displayed Files.
3. Start the backup operation by clicking the Backup button. The Backup Options
window is displayed. The NetBackup server drop-down allows you to select the
master server you wish to use for this backup, if more than one master server exists
for this client. If a specific policy or schedule should be used, use the Action>
Specify Policy and Schedule dialog prior to clicking on the Backup button.
4. Confirm the backup selection and click Start Backup.

4-26
Viewing user-directed backup job details

BAR
console

Activity
Monitor

27

The View Status dialog box enables you to view the progress of a NetBackup operation.
The status is displayed in the top pane. Select the job that you want to monitor. The
lower pane reflects the progress of the item selected in the upper pane. The NetBackup
operation is finished when the status changes to Successful. If NetBackup is unable to
back up all of the requested files, a status code is displayed a few lines before the end of
the progress report. The NetBackup Status Codes Reference Guide lists the meaning of
the final status code. You can also monitor user-directed jobs using the Activity Monitor
in the NetBackup Administration Console. User-directed backups display as
User_backup in the Job Schedule column. You can use this to keep track of how many
user-directed backups are being run in your environment.

4-27
 Topic: Backup job-related tips

After completing this topic, you will be able to identify common backup job-
related status codes.

28

This is the Backup job-related tips topic.

4-28
Common backup policy issues

• Mis-defined schedules.
Schedule issues • Status code 196 (The client backup was not attempted because the
start window closed).

• Incorrect policy type or client definition.

Client issues • Client software not installed.
• Client connection or access (firewall connections).

Backup • An incorrect backup selections list.

selections issues • Status code 71 (None of the files in the backup selections list exist).

29

The slide describes some common backup policy issues and troubleshooting. For
additional troubleshooting assistance, refer to the NetBackup Troubleshooting Guide, to
the NetBackup Status Code Reference Guide, or attend the Veritas NetBackup
Maintenance and Troubleshooting course.
• Schedule issues: Problems with schedules typically involve incorrect definitions of
policy elements. Mis-defined schedules, clients, or backup selections can lead to a
backup failure. The most common status code associated with policy schedule errors
is: “Status code 196: The client backup was not attempted
because the backup window closed”. Due diligence is required on your
part to verify that such oversights are corrected. Evaluate and adjust the policy
attributes, as necessary. Extend the backup window to avoid errors resulting from the
backup window being closed.
• Client issues: The slide highlights some common client issues. Some of these are
configuration issues, and a common problem is trying to back up a client, which has
not had the NetBackup client software installed, in which case NetBackup cannot
communicate with any NetBackup processes on that client.

4-29
 If client connection is a problem, it could be the result of the client being shut down,
NetBackup services not running, networking issues including firewalls, and so on.
Common first steps in troubleshooting are running network testing commands such
as ping, however note NetBackup has its own set of network troubleshooting
utilities.
Refer to Article 100017942: Explanation of bpclntcmd options and recommended
troubleshooting when the commands return errors at:
http://www.veritas.com/docs/100017942. Also refer to the NetBackup Commands
Reference Guide for utilities such as nbsu (the NetBackup Support Utility),
bptestbpcd, nbdna, and bptestnetcon commands.
• Backup selection issues: Another common set of issues has to do with incorrectly
specifying the backup selection list. If incorrect directories are specified, or if
directories or folders have changed on the client, then what gets backed up may not
match the expectations of the organization.
If at least one file is backed up then the backup job should return either a status code
of 0 (successful) or 1 (partially successful). If no files are backed up, a status code 71
(None of the files in the backup selections list exist) is displayed.
For additional troubleshooting assistance, refer to the NetBackup Troubleshooting
Guide, or the NetBackup Status Code Reference Guide, or attend the Veritas NetBackup
Maintenance and Troubleshooting course.

4-30
Common NetBackup status codes

Status code Description

1 The backup completed, but not all files were backed up.
71 None of the files in the backup selections list exist.
196 The client backup was not attempted because the backup window closed.

31

The slide highlights some common NetBackup job status codes that indicate that there
was an issue encountered when running a backup job.
• NetBackup status code: 1 indicates that the backup was partially successful. With
this status code, you know that at least one file was backed up, but beyond that a
problem occurred.
• NetBackup status code: 71 indicates that none of the files in the policy’s backup
selections list exist. Verify the policy file list to ensure that the file names are correct.
If a single client is the source of the error, consider moving it to a different policy.
• NetBackup status code: 196 indicates that the backup job was queued, but the start
window closed before the backup could run. A 196 error is usually indicative of a
resource issue, such as there is not enough time for all backups to complete, the
network can be slow, or there may not be enough tape drives to handle the data
load.
For a detailed explanation of these and other status codes, see the NetBackup Status
Codes Reference Guide.

4-31
Reporting on backups
Type of Information Administration Console Command Line OpsCenter

Backed up or archived files Backup, Archive, and bplist

Restore console bpflist
nbfindfile
Job status Activity Monitor bpdbjobs Monitor > Jobs
Reports > Backups > Job
Browser
Reports > Backups >
Status
Reports > Job Reports
Backup status Reports > Status of bperror –backstat -U Reports > Backups >
Backups Status
Reports > Client Reports

32

The table on this slide summarizes how backup jobs can be managed using the
NetBackup Administration Console (GUI), NetBackup commands (CLI), and NetBackup
OpsCenter.

4-32
Lesson summary
• Key points
– You learned to customize the Activity Monitor and suspend, resume, restart, and prioritize jobs.
– You also became familiar with how to initiate manual backup jobs, and how to monitor backup jobs
using the NetBackup Activity Monitor.
– You learned to configure and perform user-directed backups using the Backup, Archive, and Restore
console.
– Finally, you learned how to identify common job-related status codes and to perform basic steps to
troubleshoot failed backup jobs.
• Reference materials
– NetBackup Administrator’s Guide
– NetBackup Commands Reference Guide
– NetBackup Status Codes Reference Guide
– NetBackup Troubleshooting Guide
– OpsCenter Administrator’s Guide
– http://www.veritas.com/support

33

For more information about the topics discussed in this lesson, refer to the resources
listed on the slide and remember to check the Veritas Support web site frequently.

4-33
Lab 4: Performing File System Backups
Lab objectives
• Perform tasks to become familiar with the layout and use of the NetBackup Activity
Monitor
• Manually initiate backup jobs using the Java NetBackup Administration Console
• Use the Activity Monitor to monitor and view automated and scheduled backup jobs
• Use the Backup, Archive, and Restore GUI to perform user-initiated backup jobs
• Use the Backup, Archive, and Restore GUI and the Activity Monitor to monitor the status
of user-initiated backup jobs

34

The slide shows the objectives for the lab associated with this lesson. Refer to the
corresponding lab guide for specific instructions and lab steps.

4-34
What did you learn?
You are about to be asked a series
of questions related to the current
lesson.

35

The next section is a quiz. In this quiz, you are asked a series of questions related to the
current lesson.

4-35
Question 1: End-user initiated backups
Which type of backup can be performed from a client machine by a user or script?

A. Immediate
B. Automatic scheduled
C. Manual
D. User-directed

36

4-36
Answer 1: End-user initiated backups
Which type of backup can be performed from a client machine by a user or script?

A. Immediate
B. Automatic scheduled
C. Manual
D. User-directed

The correct answer is D.

37

4-37
Question 2: Manual backups
Manual backups apply only to automatic schedules.

A. True
B. False

38

4-38
Answer 2: Manual backups
Manual backups apply only to automatic schedules.

A. True
B. False

The correct answer is A.

39

4-39
Question 3: Methods for initiating backups
Backups can be initiated by many methods. Which method does not apply?

A. Automatically, based on a policy schedule

B. Manually from the NetBackup Administration Console
C. Manually from the command line
D. As a user scheduled backup using the NetBackup scheduler

40

4-40
Answer 3: Methods for initiating backups
Backups can be initiated by many methods. Which method does not apply?

A. Automatically, based on a policy schedule

B. Manually from the NetBackup Administration Console
C. Manually from the command line
D. As a user scheduled backup using the NetBackup scheduler

The correct answer is D.

41

4-41
End of presentation

4-42