bpbackup -f listfile | filenames [-p policy] [-s schedule][-S master_server...] [-t policy_type] [-L progress_log [-en]] [-w [hh:mm:ss]] [-k "keyword_phrase"]
bpbackup -i [-p policy] [-h hostname] [-s schedule] [-S master_server...] [-t policy_type] [-L progress_log [-en]] [-w [hh:mm:ss]] [-k "keyword_phrase"]
bpbackup -dssu DSSUname [-S master_server] [-w [hh:mm:ss]]
On UNIX and Linux systems, the directory path to this command is /usr/openv/netbackup/bin/
The bpbackup command can start a process on clients and master servers.
The -f option of bpbackup starts a user backup equivalent to what is performed by using the interface on the client. This type of backup can be started from any NetBackup client to back up files from that client.
bpbackup processes the files that you list on the command line or in the file that you specify with the -f listfile option. A file path can be a file name or a directory name. If the named files include a directory, bpbackup backs up all files and subdirectories of that directory; it starts at the directory itself.
On master servers:
The -i option of bpbackup starts an immediate manual backup of a client. The bpbackup option is available only to the administrator on the master server. It is equivalent to when you start a manual backup from the NetBackup Administration Console. Use the -h option to specify the host.
Because progress logs are written only on clients and this form of bpbackup is run from the master server only, the -L option is undefined.
The following restrictions apply to this command:
By default, you return to the system prompt after bpbackup is successfully submitted. The command works in the background and does not return completion status directly to you. The -w option lets you change this behavior so the command works in the foreground. It returns completion status after a specified time period.
If you create the file before you run the bpbackup command and then specify the file with the -L progress_log option, the following occurs: bpbackup writes informative and error messages to a progress-log file. If bpbackup cannot back up the requested files or directories, use the progress log to determine the reason for the failure.
If you create the following directory with public-write access, bpbackup creates a debug log file in the directory that you can use for troubleshooting:
On UNIX and Linux systems: usr/openv/netbackup/logs/bpbackup/
NetBackup sends mail on the backup completion status when the backup process is complete to mail_address when users specify the following:
If this option is not specified, NetBackup uses the first policy it finds that includes the client and a user backup schedule.
The -p option is required for an immediate-manual backup (-i option).
0 = Standard
4 = Oracle
6 = Informix-On-BAR
7 = Sybase
8 = MS-SharePoint
10 = NetWare
13 = MS-Windows
14 = OS/2
15 = MS-SQL-Server
16 = MS-Exchange-Server
19 = NDMP
Note that the following policy types apply only to the NetBackup Enterprise Server.
11 = DataTools-SQL-BackTrack
17 = SAP
18 = DB2
20 = FlashBackup
21\fR = Split-Mirror
22 = AFS
39 = Enterprise-Vault
On UNIX and Linux systems, for example: /home/tlc/proglog
The default is not to use a progress log.
The - L option is not supported for NDMP clients.
Include the -en option to generate a progress log that is in English. The name of the log contains the string _en. This option is useful to support personnel in a distributed environment where different locales may create logs of various languages.
The required date and time values format in NetBackup commands varies according to your locale. The /user/openv/msg/.conf file (UNIX and Linux) and the \fIinstall_path\VERITAS\msg\LC.CONF file (Windows) contain information such as the date-time formats for each supported locale. The files contain specific instructions on how to add or modify the list of supported locales and formats.
More information is available about the locale of your system.
See the "Specifying the locale of the NetBackup installation" topic in the NetBackup Administrator's Guide, Volume II.
You can optionally specify a wait time in hours, minutes, and seconds. The maximum wait time you can specify is 23:59:59. If the wait time expires before the backup is complete, the command exits with a timeout status. The backup, however, still completes on the server.
The bpbackup -w option causes the shell to wait for a return code. The operating system shell can only return one return code. Therefore, if you use -w without specifying a wait time or you specify a value of 0, NetBackup waits indefinitely for the completion status.
You can start a manual or an administrative backup using bpbackup -i along with the -w function. This type of backup has the potential to start multiple jobs because it is based on policy attributes. If the manual backup starts multiple jobs, the -w function still only returns one return code to the shell.
If you use -i with -w and more than one job begins, NetBackup waits until all jobs complete before it returns a completion status. However, because NetBackup only returns one status code to the shell, the job ID that the status code belongs to is unknown.
If multiple jobs are due to multiple clients and Allow Multiple Data Streams is not selected, use -h to restrict the operation to one client. However, if Allow Multiple Data Streams is selected in the policy and the selected client has multiple jobs, the returned status code is again unknown.
If you use the -i option with -k, NetBackup establishes an association between the keyword phrase and the backup policy and image.
The keyword phrase is a textual description of the backup that is a maximum of 128 characters in length.
On UNIX and Linux systems, all printable characters are permitted including space (" ") and period ("."). Enclose the phrase in double quotes ("...") or single quotes ( oq...cq) to avoid conflict with the UNIX shell.
The default keyword phrase is the null (empty) string.
The format that is required for the file list depends on whether the files have spaces, newlines, or returns in the names.
To back up the files that do not have spaces, newlines, or returns in the names, use the following format:
filepathWhere filepath is the path to the file you want to back up.
On UNIX and Linux systems, examples are /home, /etc, and /var.
To back up the files that have spaces, newlines, or returns in the names, use the following format:
filepathlen filepathWhere filepath is the path to the file you want to back up and filepathlen is the number of characters in the file path.
Examples on UNIX and Linux systems are the following:
5 /home 4 /etc 4 /var 19 /home/abc/test file
11 c:\Programs 8 c:\winnt 22 c:\documents\old memos
Example 1 - Perform a user backup of a single file, enter:
On UNIX and Linux systems: bpbackup /usr/user1/file1
Example 2 - Start a user backup of the files that are listed in a file that is named backup_list:
bpbackup -f backup_list
bpbackup -f backup_list
bpbackup -f backup_list
bpbackup -f backup_list
Example 3 - Start an immediate-manual backup (all on one line) of the client host named diablo, in the policy named cis_co. The policy type is Standard policy and is in the configuration on the master server named hoss.
UNIX and Linux: bpbackup -p cis_co -i -h diablo -S hoss -t 0
On UNIX and Linux systems: The following command associates the keyword phrase "Backup Home Dir 01/01/01" to the user backup of the directory /home/kwc. (Enter the command on one line or use the backslash continuation character.)
bpbackup -k "Backup Home Dir 01/01/01" -L /home/kwc/bkup.log \ /home/kwc
Example 5 - Associate the keyword phrase "Policy Win 01/01/01" to the immediate-manual backup of the client host named slater in the policy named win_nt_policy. (Enter the command all on one line.)
UNIX and Linux: bpbackup -k "Policy Win 01/01/01" -i -h slater \-p win_nt_policy -t 13
UNIX and Linux systems: $HOME/bp.conf
bp, bparchive, bplist, bprestore