bp.conf file


 

The bp.conf is the master configuration file for the backup client software. With it the allowed servers and other options are included. On NetBackup UNIX clients, the main bp.conf file is located in the following pathname: /usr/openv/netbackup/bp.conf. As installed, NetBackup uses internal software defaults for all options in the bp.conf file, except SERVER. During installation, NetBackup sets the SERVER option to the name of the master server where the software is installed. Note The SERVER option must be in the /usr/openv/netbackup/bp.conf file on all NetBackup UNIX clients. It is also the only required entry in this file.

If a single UNIX system is running as both a client and a server, both the server and client options are in the /usr/openv/netbackup/bp.conf file.

Each nonroot user on a UNIX client can have a personal bp.conf file in their home directory as follows: $HOME/bp.conf The options in personal bp.conf files apply only to user operations. During a user operation, NetBackup checks the $HOME/bp.conf file before /usr/openv/netbackup/bp.conf. Root users do not have personal bp.conf files.
NetBackup uses the
/usr/openv/netbackup/bp.conf file for root users. The following topics describe the options that you can specify in the /usr/openv/netbackup/bp.conf and $HOME/bp.conf files on a NetBackup UNIX client. Note PC clients provide similar options that you can change either through the client-user interface or in a configuration file, depending on the client.

ALLOW_NON_RESERVED_PORTS
Specifies that the NetBackup client daemon (bpcd) can accept remote connections from non-privileged ports (port numbers 1024 or greater). If this entry is not present, then bpcd requires remote connections to come from privileged ports (port numbers less than 1024). This option can be useful when NetBackup clients and servers are on opposite sides of a firewall. You can add this option to the /usr/openv/netbackup/bp.conf file on a UNIX client. In addition to adding ALLOW_NON_RESERVED_PORTS to the client, execute the following commands as root on the master server. cd /usr/openv/netbackup/bin/admincmd ./bpclient -client client_name -add -connect_nr_port 1 Where client_name is the name of the client where you added the ALLOW_NON_RESERVED_PORTS option. These commands instruct the master server to use nonprivileged ports.

BPARCHIVE_POLICY
Specifies the name of the policy to use for user archives. Default: BPARCHIVE_POLICY is not in any bp.conf file and NetBackup uses the first policy that it finds that has the client and a user archive schedule. For example: BPARCHIVE_POLICY = arch_1 You can add this option to the /usr/openv/netbackup/bp.conf and $HOME/bp.conf files on a UNIX client. The value in the user’s $HOME/bp.conf file takes precedence if it exists.

BPARCHIVE_SCHED
Specifies the name of the schedule for user archives. Default: BPARCHIVE_SCHED is not in any bp.conf file and NetBackup uses the first archive schedule in the first policy that it finds that has this client. For example BPARCHIVE_SCHED = user_arch1 You can add this option to the /usr/openv/netbackup/bp.conf and $HOME/bp.conf files on a UNIX client. The value in the user’s $HOME/bp.conf file takes precedence if it exists.

BPBACKUP_POLICY
Specifies the name of the policy name to use for user backups. Default: BPBACKUP_POLICY, is not in any bp.conf file and NetBackup uses the first policy it finds that has both the client and a user backup schedule. For example, BPBACKUP_POLICY = userback_1 You can add this option to the /usr/openv/netbackup/bp.conf and (or) $HOME/bp.conf files on a UNIX client. The value in user’s $HOME/bp.conf file takes precedence if it exists. NetBackup Configuration Options

BPBACKUP_SCHED
Specifies the name of the schedule to use for user backups. Default: BPBACKUP_SCHED is not in any bp.conf file and NetBackup uses the first policy it finds that has both the client and a user backup schedule. For example: BPBACKUP_SCHED = user_back1 You can add this option to the /usr/openv/netbackup/bp.conf and $HOME/bp.conf files on a UNIX client. The value in the user’s $HOME/bp.conf file takes precedence if it exists.

BUSY_FILE_ACTION
Note This parameter does not apply to Apollo clients. Directs the action that NetBackup performs on busy files when busy-file processing is enabled. You can add this option to the /usr/openv/netbackup/bp.conf and $HOME/bp.conf files on a UNIX client. The value in the user’s $HOME/bp.conf file takes precedence if it exists. There can be multiple entries of the following form: BUSY_FILE_ACTION = filename_template action_template Where

BUSY_FILE_DIRECTORY filename_template is the absolute pathname and file name of the busy file. The shell language metacharacters *, ?, [], [ - ] can be used for pattern matching of filenames or parts of filenames. BUSY_FILE_DIRECTORY action_template is one of the following: MAIL | mail Directs NetBackup to E-mail a busy file notification message to the user specified by the BUSY_FILE_NOTIFY_USER option. REPEAT | repeat [repeat_count] Directs NetBackup to retry the backup on the specified busy file. A repeat count can be specified to control the number of backup attempts. The default repeat count is 1. IGNORE | ignore Directs NetBackup to exclude the busy file from busy file processing.

BUSY_FILE_DIRECTORY
Note This parameter does not apply to Apollo clients. The BUSY_FILE_DIRECTORY option specifies the path to the busy-files working directory when busy-file processing is enabled. Default: BUSY_FILE_DIRECTORY is not in any bp.conf file and NetBackup creates the busy_files directory in /usr/openv/netbackup. You can add this option to the /usr/openv/netbackup/bp.conf and $HOME/bp.conf files on a UNIX client. The value in the user’s $HOME/bp.conf file takes precedence, if it exists.

BUSY_FILE_NOTIFY_USER
Note This parameter does not apply to Apollo clients. The BUSY_FILE_NOTIFY_USER option specifies the recipient of the busy file notification message when BUSY_FILE_ACTION is set to MAIL or mail. Default: BUSY_FILE_NOTIFY_USER is not in any bp.conf file and the E-mail recipient is root. You can add this option to the
/usr/openv/netbackup/bp.conf and $HOME/bp.conf files on a UNIX client. The value in the user’s $HOME/bp.conf file takes precedence, if it exists.

BUSY_FILE_PROCESSING
Note This parameter does not apply to Apollo clients. The BUSY_FILE_PROCESSING option lets the user control the actions that NetBackup performs when it determines that a file is changing while it is being backed up. Default: BUSY_FILE_PROCESSING option is not in bp.conf and busy-file processing does not occur. (See “Busy-File Processing (UNIX Clients Only)” on page 449 for instructions on setting this option.) You can add this option to the
/usr/openv/netbackup/bp.conf file on a UNIX client.

CLIENT_NAME
Specifies the name of the client as it is known to NetBackup. There can be one CLIENT_NAME entry and it must match the name used in the policy that is backing up the client. The only exception is for an alternate client restore, where the name must match that of the client whose files are being restored. (See “Allowing Redirected Restores” on NetBackup Configuration Options 486 NetBackup DataCenter System Administrator’s Guide - UNIX page 309.) The client installation procedures automatically set CLIENT_NAME to the value specified on the ftp_to_client or install_client command in the installation scripts. You can add this option to the /usr/openv/netbackup/bp.conf file on a UNIX client. It can also be added to a $HOME/bp.conf file on a UNIX client but this is normally done only for alternate-client restores. If the value is not in any bp.conf file, NetBackup uses the value returned by the gethostname() library function.

CLIENT_PORT_WINDOW
Specifies the range of nonreserved ports on this computer that are used for connecting to NetBackup on other computers. (See “CLIENT_PORT_WINDOW” on page 467.)

CLIENT_READ_TIMEOUT
Specifies the number of seconds for the client-read timeout on a server or a database agent. (See “CLIENT_READ_TIMEOUT” on page 467.)

CLIENT_RESERVED_PORT_WINDOW
Specifies the range of reserved ports on this computer that are used for connecting to NetBackup on other computers. (See “CLIENT_RESERVED_PORT_WINDOW” on page 468.)

COMPRESS_SUFFIX
Note This option has a reasonable default and has to be changed only if problems are encountered. This option does not apply to Apollo clients. Specifies a list of file extensions. During a backup, NetBackup does not compress files with these extensions because the file can already be in a compressed format. Default, COMPRESS_SUFFIX is not in the bp.conf file. (See “Compression” on page 112 for more information on compressing files.) You cannot use wildcards when specifying these extensions. For example, you can specify the following: .A1 You cannot specify either of the following: .A* or .A[1-9] You can add this option to the /usr/openv/netbackup/bp.conf file on a UNIX client.

CRYPT_OPTION
Note CRYPT_OPTION applies only to clients that have the NetBackup Encryption option installed. See the NetBackup Encryption System Administrator’s Guide.

CRYPT_OPTION specifies the encryption options on NetBackup clients. NetBackup creates this entry automatically in the /usr/openv/netbackup/bp.conf file on a UNIX client when you run the bpinst_crypt command on the NetBackup master server. Do not alter the entry or create this file manually unless it has been accidentally deleted. The allowable values follow: DENIED|denied Specifies that the client does not permit encrypted backups. If the server requests an encrypted backup, it is considered an error. This option is the default for a client that has not been configured for encryption. ALLOWED|allowed Specifies that the client allows either encrypted or unencrypted backups. REQUIRED|required Specifies that the client requires encrypted backups. If this value is specified and the server requests an unencrypted backup, it is considered an error.

CRYPT_STRENGTH
Note CRYPT_STRENGTH applies only to clients that have the NetBackup Encryption option installed. See the NetBackup Encryption System Administrator’s Guide. Specifies the encryption strength on NetBackup clients. NetBackup creates this entry automatically in the /usr/openv/netbackup/bp.conf file on a UNIX client when you run the bpinst_crypt command on the NetBackup master server. Do not alter the entry or create it manually unless it has been accidentally deleted. The possible values follow: DES_40|des_40 Specifies 40-bit DES encryption. This is the default value for a client that has not been configured for encryption. DES_56|des_56 NetBackup Configuration Options 488 NetBackup DataCenter System Administrator’s Guide - UNIX Specifies 56-bit DES encryption.

CRYPT_LIBPATH
Note CRYPT_LIBPATH applies only to clients that have the NetBackup Encryption option installed. See the NetBackup Encryption System Administrator’s Guide. Specifies the directory that contains the encryption libraries for NetBackup clients. NetBackup creates this entry automatically in the /usr/openv/netbackup/bp.conf file on a UNIX client when you run the bpinst_crypt command on the NetBackup master server. Do not alter the entry or create it manually unless it has been accidentally deleted. BUSY_FILE_DIRECTORY The following is the default value on UNIX systems: /usr/openv/lib/ BUSY_FILE_DIRECTORY The following is the default value on Windows systems: install_path\bin\ Where install_path is the directory where NetBackup is installed and by default is C:\Program Files\VERITAS. BUSY_FILE_DIRECTORY The following is the default value on Macintosh systems: :System Folder:Extensions:

CRYPT_KEYFILE
Note CRYPT_KEYFILE applies only to clients that have the NetBackup Encryption option installed. See the NetBackup Encryption System Administrator’s Guide. Specifies the file that contains the encryption keys on NetBackup clients. NetBackup creates this entry automatically in the /usr/openv/netbackup/bp.conf file on a UNIX client when you run the bpinst_crypt command on the NetBackup master server. Do not alter the entry or create it manually unless it has been accidentally deleted. The default values follow: BUSY_FILE_DIRECTORY On UNIX systems: /usr/openv/netbackup/keyfile BUSY_FILE_DIRECTORY On Windows systems: install_path\bin\keyfile.dat Where install_path is the directory where NetBackup is installed and by default is C:\Program Files\VERITAS. Chapter 10, Additional Configuration 489 NetBackup Configuration Options BUSY_FILE_DIRECTORY On Macintosh systems: :System Folder:Preferences:NetBackup:keyfile

DISALLOW_SERVER_FILE_WRITES
Prevents the NetBackup server from creating files on the NetBackup client. For example, this prevents server-directed restores or server-directed updates of the bp.conf file on the client. You can add this option to the /usr/openv/netbackup/bp.conf file on a UNIX client. By default, server writes are allowed.

DO_NOT_RESET_FILE_ACCESS_TIME
Note DO_NOT_RESET_FILE_ACCESS_TIME does not apply to Apollo clients. This setting affects software and administration scripts that examine a file’s access time. DO NOT use this option or USE_CTIME_FOR_INCREMENTALS if you are running Storage Migrator on the system. Setting these options causes the atime for files to be updated every time they are backed up. This makes it appear as if the files are frequently used and stops Storage Migrator from selecting them for migration. Specifies that if a file is backed up, its access time (atime) will show the time of the backup. Default: NetBackup preserves the access time by resetting it to the value it had before the backup. You can add this option to the /usr/openv/netbackup/bp.conf file on a UNIX client.

GENERATE_ENGLISH_LOGS
Enables the generation of an English error log, and English trace logs for the bparchive, bpbackup, bpduplicate, bpimport, and bprestore commands. This option is useful to support personnel assisting in distributed environments where differing locales result in logs with various languages. You can add this option to the /usr/openv/netbackup/bp.conf file on NetBackup servers and clients.

INFORMIX_HOME
Specifies the path to the Informix home directory and is required when the client is using NetBackup for Informix. NetBackup Configuration Options 490 NetBackup DataCenter System Administrator’s Guide - UNIX You must add this option to the /usr/openv/netbackup/bp.conf file on UNIX clients that are running NetBackup for Informix.

INITIAL_BROWSE_SEARCH_LIMIT
Reduces the default number of days back that NetBackup searches for files to restore. You can add this option to the /usr/openv/netbackup/bp.conf file on NetBackup master servers and clients. (See “INITIAL_BROWSE_SEARCH_LIMIT” on page 472.)

KEEP_DATABASE_COMM_FILE
Causes NetBackup to keep database agent logs for seven days. Default: NetBackup keeps database agent logs for only one day. You can add this option to the /usr/openv/netbackup/bp.conf file on a UNIX database agent (for example, a client that is running NetBackup for Informix). KEEP_LOGS_DAYS Specifies the number of days to keep job and progress logs generated by the NetBackup Java program, Backup, Archive, and Restore. NetBackup writes these files in the usr/openv/netbackup/logs/user_ops/username/jobs and /usr/openv/netbackup/logs/user_ops/username/logs directories. There is a directory for each user that uses the Backup, Archive, and Restore program. Default: Three days. You can add this option to the /usr/openv/netbackup/bp.conf file on a UNIX client. LIST_FILES_TIMEOUT Specifies the number of minutes to wait for a response from the NetBackup server when listing files by using the client-user interface or bplist. If this time is exceeded, the user receives a socket read failed error even if the server is still processing the user’s request. Default: LIST_FILES_TIMEOUT is not in any bp.conf file and NetBackup uses a value of 30 minutes. You can add this option to the /usr/openv/netbackup/bp.conf and $HOME/bp.conf files on a UNIX client. The value in the user’s $HOME/bp.conf file takes precedence if it exists.

LOCKED_FILE_ACTION
Note This parameter does not apply to Apollo clients. Specifies the behavior of NetBackup when it tries to back up a file that has mandatory file locking enabled in its file mode (see chmod(1)). If LOCKED_FILE_ACTION is specified and has a value of SKIP (the only legal value), NetBackup skips files that currently have mandatory locking set by another process and logs a message to this effect. You can add this option to the /usr/openv/netbackup/bp.conf files on a UNIX client. Default: NetBackup waits for files to become unlocked.

MEDIA_SERVER
Specifies that the listed machine is a media server only. Machines listed as media servers can back up and restore clients, but have limited administrative privileges.

MEGABYTES_OF_MEMORY
Note This option does not apply to Apollo clients. This option has a reasonable default and has to be changed only if problems are encountered. Specifies how much memory is available on the client to use when compressing files during backup. If you select compression, the client software uses this value to determine how much space to request for the compression tables. The more memory that is available to the compress code, the greater the compression. The percentage of machine resources used is also greater. If other processes also need memory, it is generally best to use a maximum value of 1/2 the actual physical memory on a machine to avoid excessive swapping. You can add this option to the /usr/openv/netbackup/bp.conf file on a UNIX client. Default: NetBackup assumes a value of one megabyte.

NFS_ACCESS_TIMEOUT
Specifies the number of seconds that the backup process waits when processing an NFS mount table before considering an NFS file system unavailable. You can add this option to the /usr/openv/netbackup/bp.conf file on a UNIX client. Default: Timeout period is five seconds. Note Only NetBackup DataCenter can back up NFS-mounted files. NetBackup Configuration Options 492 NetBackup DataCenter System Administrator’s Guide - UNIX

RANDOM_PORTS
Specifies whether NetBackup chooses port numbers randomly or sequentially when it requires one for communication with NetBackup on other computers. (See “RANDOM_PORTS” on page 168.)

RESTORE_RETRIES
Note This option has a reasonable default and will have to be changed only if problems are encountered. Specifies the number of times to retry a restore after a failure. Default: There are no retries. You can add this option to the /usr/openv/netbackup/bp.conf file on a UNIX client.

REQUIRED_INTERFACE
Specifies the network interface that NetBackup uses when connecting to another NetBackup client or server. (See “REQUIRED_INTERFACE” on page 168.)

SERVER_PORT_WINDOW
Specifies the range of nonreserved ports on which this computer accepts connections from NetBackup on other computers.

SERVER
Defines the list of NetBackup master servers and media servers that can access the NetBackup client. During client installation, the SERVER is set to the name of the primary master server for this client. Other SERVER entries can be added for any other master servers for this client, and for media servers for this client. (Media servers for this NetBackup client can also be added using the MEDIA_SERVER option.) If you configure media servers, you must have a SERVER or MEDIA_SERVER entry for each media server in the NetBackup client’s bp.conf file. The following is an example bp.conf file on a client: SERVER = Master_server (default master server) SERVER = NBU_server (other master server) SERVER = Media_server_#1 MEDIA_SERVER = Media_server_#2 . . . The first SERVER entry denotes the master server to which the client would connect by default for any requests (for example, backing up, listing or restoring files). The SERVER option must be present in the /usr/openv/netbackup/bp.conf file on all UNIX clients. It is also the only required entry in the bp.conf file for clients. This option is not used in a $HOME/bp.conf file. On NetBackup UNIX servers, the SERVER entry applies to the both the client and the server. SYBASE_HOME Specifies the path to the Sybase home directory and is required when using NetBackup for Sybase to back up Sybase databases. Default: SYBASE_HOME is not in the bp.conf file. You must add this option to the /usr/openv/netbackup/bp.conf file on a NetBackup for Sybase client.

USE_CTIME_FOR_INCREMENTALS
Note If you specify USE_CTIME_FOR_INCREMENTALS, you must also specify

DO_NOT_RESET_FILE_ACCESS_TIME
DO NOT use these options if you are running Storage Migrator on the system. Setting these options causes the atime for files to be updated every time they are backed up. This makes it appear as if the files are frequently used and stops Storage Migrator from selecting them for migration. Causes NetBackup client software to use both modification time (mtime) and inode change time (ctime) during incremental backups to determine if a file has changed. You can add this option to the /usr/openv/netbackup/bp.conf file on a UNIX client. Default: NetBackup uses only mtime.

USEMAIL
Specifies the E-mail address where NetBackup sends status on the outcome of operations for a UNIX client. Default: USEMAIL is not present in any bp.conf file and no E-mail is sent. Note You can use multiple addresses or an E-mail alias as long as there are no blanks or white space between them. You can add this option to the /usr/openv/netbackup/bp.conf and $HOME/bp.conf files on a UNIX client. NetBackup Configuration Options BUSY_FILE_DIRECTORY If the /usr/openv/netbackup/bp.conf file specifies an address, NetBackup sends automatic backup and manual backup status to that address. BUSY_FILE_DIRECTORY If the $HOME/bp.conf file specifies an address, NetBackup also sends status on the success or failure of user operations to that address.

VERBOSE
Causes NetBackup to include more information in its logs. Default: Disabled. You can add this option to the /usr/openv/netbackup/bp.conf file on a UNIX client.


UNIX Client Examples
Example /usr/openv/netbackup/bp.conf File
SERVER = hare
CLIENT_NAME = freddie
USEMAIL = abc@bdev.com
COMPRESS_SUFFIX = .Addrs
COMPRESS_SUFFIX = .Counts
VERBOSE
RESTORE_RETRIES = 1
BPBACKUP_POLICY = U1userdir
BPBACKUP_SCHED = userbackups
BPARCHIVE_POLICY = U1userdir
BPARCHIVE_SCHED = userarchives
LOCKED_FILE_ACTION = SKIP



Example $HOME/bp.conf File
Nonroot users on UNIX clients can have a personal bp.conf file in their home directory.
A personal bp.conf file can have any of the following options
Note A root user cannot have a personal bp.conf file. For root users, NetBackup uses
the /usr/openv/netbackup/bp.conf file.
USEMAIL = mars@bdev.com
BPBACKUP_POLICY = user1
BPBACKUP_SCHED = userback
BPARCHIVE_POLICY = user1
BPARCHIVE_SCHED = userarch
LIST_FILES_TIMEOUT = 10
CLIENT_NAME

© Copyright 2000 Lawrence Berkeley National Laboratory
Page Owner: Christopher Manders

Suggestions


Veritas Netbackup Status Code


 

0 the requested operation was successfully completed
1 the requested operation was partially successful
2 none of the requested files were backed up
3 valid archive image produced, but no files deleted due to non-fatal problems
4 archive file removal failed
5 the restore failed to recover the requested files
6 the backup failed to back up the requested files
7 the archive failed to back up the requested files
8 unable to determine the status of rbak
9 an extension package is needed, but was not installed
10 allocation failed
11 system call failed
12 file open failed
13 file read failed
14 file write failed
15 file close failed
16 unimplemented feature
17 pipe open failed
18 pipe close failed
19 getservbyname failed
20 invalid command parameter
21 socket open failed
22 socket close failed
23 socket read failed
24 socket write failed
25 cannot connect on socket
26 client/server handshaking failed
27 child process killed by signal
28 failed trying to fork a process
29 failed trying to exec a command
30 could not get passwd information
31 could not set user id for process
32 could not set group id for process
33 failed while trying to send mail
34 failed waiting for child process
35 cannot make required directory
36 failed trying to allocate memory
37 operation requested by an invalid server
38 could not get group information
39 client name mismatch
40 network connection broken
41 network connection timed out
42 network read failed
43 unexpected message received
44 network write failed
45 request attempted on a non reserved port
46 server not allowed access
47 host is unreachable
48 client hostname could not be found
49 client did not start
50 client process aborted
51 timed out waiting for database information
52 timed out waiting for media manager to mount volume
53 backup restore manager failed to read the file list
54 timed out connecting to client
55 permission denied by client during rcmd
56 client's network is unreachable
57 client connection refused
58 can't connect to client
59 access to the client was not allowed
60 client cannot read the mount table
61 wbak was killed
62 wbak exited abnormally
63 process was killed by a signal
64 timed out waiting for the client backup to start
65 client timed out waiting for the continue message from the media manager
66 client backup failed to receive the CONTINUE BACKUP message
67 client backup failed to read the file list
68 client timed out waiting for the file list
69 invalid filelist specification
70 an entry in the filelist expanded to too many characters
71 none of the files in the file list exist
72 the client type is incorrect in the configuration database
73 bpstart_notify failed
74 client timed out waiting for bpstart_notify to complete
75 client timed out waiting for bpend_notify to complete
76 client timed out reading file
77 execution of the specified system command returned a nonzero status
78 afs/dfs command failed
79 unimplemented error code 79
80 Media Manager device daemon (ltid) is not active
81 Media Manager volume daemon (vmd) is not active
82 media manager killed by signal
83 media open error
84 media write error
85 media read error
86 media position error
87 media close error
88 Auspex SP/Backup failure
89 fatal error in Unitree file system
90 media manager received no data for backup image
91 fatal NB media database error
92 media manager detected image that was not in tar format
93 media manager found wrong tape in drive
94 cannot position to correct image
95 requested media id was not found in NB media database and/or MM volume database
96 unable to allocate new media for backup, storage unit has none available
97 requested media id is in use, cannot process request
98 error requesting media (tpreq)
99 NDMP backup failure
100 system error occurred while processing user command
101 failed opening mail pipe
102 failed closing mail pipe
103 error occurred during initialization, check configuration file
104 invalid file pathname
105 file pathname exceeds the maximum length allowed
106 invalid file pathname found, cannot process request
107 too many arguments specified
108 invalid date format specified
109 invalid date specified
110 Cannot find the NetBackup configuration information
111 No entry was found in the server list
112 no files specified in the file list
113 unimplemented error code 113
114 unimplemented error code 114
115 unimplemented error code 115
116 unimplemented error code 116
117 unimplemented error code 117
118 unimplemented error code 118
119 unimplemented error code 119
120 cannot find configuration database record for requested NB database backup
121 no media is defined for the requested NB database backup
122 specified device path does not exist
123 specified disk path is not a directory
124 NB database backup failed, a path was not found or is inaccessable
125 another NB database backup is already in progress
126 NB database backup header is too large, too many paths specified
127 specified media or path does not contain a valid NB database backup header
128 unimplemented error code 128
129 unimplemented error code 129
130 system error occurred
131 client is not validated to use the server
132 user is not validated to use the server from this client
133 invalid request
134 unable to process request because the server resources are busy
135 client is not validated to perform the requested operation
136 unimplemented error code 136
137 unimplemented error code 137
138 unimplemented error code 138
139 unimplemented error code 139
140 user id was not superuser
141 file path specified is not absolute
142 file does not exist
143 invalid command protocol
144 invalid command usage
145 daemon is already running
146 cannot get a bound socket
147 required or specified copy was not found
148 daemon fork failed
149 master server request failed
150 termination requested by administrator
151 Backup Exec operation failed
152 required value not set
153 server is not the master server
154 storage unit characteristics mismatched to request
155 unused b
156 unused f
157 unused d
158 failed accessing daemon lock file
159 licensed use has been exceeded
160 authentication failed
161 Evaluation software has expired. See www.veritas.com for ordering information
162 unimplemented error code 162
163 unimplemented error code 163
164 unable to mount media because its in a DOWN drive or misplaced
165 NB image database contains no image fragments for requested backup id/copy number
166 backups are not allowed to span media
167 cannot find requested volume pool in Media Manager volume database
168 cannot overwrite media, data on it is protected
169 media id is either expired or will exceed maximum mounts
170 unimplemented error code 170
171 media id must be 6 or less characters
172 cannot read media header, may not be NetBackup media or is corrupted
173 cannot read backup header, media may be corrupted
174 media manager - system error occurred
175 not all requested files were restored
176 cannot perform specified media import operation
177 could not deassign media due to Media Manager error
178 media id is not in NetBackup volume pool
179 density is incorrect for the media id
180 tar was successful
181 tar received an invalid argument
182 tar received an invalid file name
183 tar received an invalid archive
184 tar had an unexpected error
185 tar did not find all the files to be restored
186 tar received no data
187 unimplemented error code 187
188 unimplemented error code 188
189 the server is not allowed to write to the client's filesystems
190 found no images or media matching the selection criteria
191 no images were successfully processed
192 unimplemented error code 192
193 unimplemented error code 193
194 the maximum number of jobs per client is set to 0
195 client backup was not attempted
196 client backup was not attempted because backup window closed
197 the specified schedule does not exist in the specified class
198 no active classes contain schedules of the requested type for this client
199 operation not allowed during this time period
200 scheduler found no backups due to run
201 handshaking failed with server backup restore manager
202 timed out connecting to server backup restore manager
203 server backup restore manager's network is unreachable
204 connection refused by server backup restore manager
205 cannot connect to server backup restore manager
206 access to server backup restore manager denied
207 error obtaining date of last backup for client
208 failed reading user directed filelist
209 error creating or getting message queue
210 error receiving information on message queue
211 scheduler child killed by signal
212 error sending information on message queue
213 no storage units available for use
214 regular bpsched is already running
215 failed reading global config database information
216 failed reading retention database information
217 failed reading storage unit database information
218 failed reading class database information
219 the required storage unit is unavailable
220 database system error
221 continue
222 done
223 an invalid entry was encountered
224 there was a conflicting specification
225 text exceeded allowed length
226 the entity already exists
227 no entity was found
228 unable to process request
229 events out of sequence - image inconsistency
230 the specified class does not exist in the configuration database
231 schedule windows overlap
232 a protocol error has occurred
233 premature eof encountered
234 communication interrupted
235 inadequate buffer space
236 the specified client does not exist in an active class within the configuration database
237 the specified schedule does not exist in an active class in the configuration database
238 the database contains conflicting or erroneous entries
239 the specified client does not exist in the specified class
240 no schedules of the correct type exist in this class
241 the specified schedule is the wrong type for this request
242 operation would cause an illegal duplication
243 the client is not in the configuration
244 main bpsched is already running
245 the specified class is not of the correct client type
246 no active classes in the configuration database are of the correct client type
247 the specified class is not active
248 there are no active classes in the configuration database
249 the file list is incomplete
250 the image was not created with TIR information
251 the tir information is zero length
252 unused TIR error 2
253 unused TIR error 1
254 server name not found in the bp.conf file
255 unimplemented error code 255

Source ://www.veritas.com

Virtual Tape Library (VTL)

Virtual Tape Library (VTL)

A Virtual Tape Library (VTL) is a data storage virtualization technology used typically for archival storage purposes. A VTL presents a storage component (usually hard disk storage) as tapes available for use with tape drive and media changer emulations.
Virtualizing the storage as tape hardware allows integration of VTLs with existing archiving policies and backup software while taking advantage of the benefits of storage virtualization. The benefits of tape virtualization include storage consolidation and faster data restore processes.
Most current VTL solutions use ATA or SATA disk arrays as the primary storage component due to their relatively low cost. The use of array enclosures increases the scalability of the solution by allowing the addition of more disk drives and enclosures to increase the storage capacity.
By backing up data to disks instead of tapes, VTL often increases performance of both backup and recovery operations. In some cases, the data stored on the VTL's disk array is exported to other media, such as tapes, for disaster recovery purposes.
Historically, tape drives and libraries mostly featured SCSI Parallel Interface and Fibre Channel external interfaces. Likewise, VTL solutions generally support popular SCSI transport protocols such as SPI, Fibre Channel, and iSCSI.

Today, so many product has been offered in the market, such as :
- EMC DL210, EMCDL4100, EMCDL4200, EMCDL440 from EMC
- VTF Open(tm), VTF Mainframe, ProtecTIER VT from HDS
- NearStore Virtual Tape Library from NetApp

Configuring Device on Media Server (Version 5.0)

There are several way for configuring device especially tape drive on one media server. Maybe the easiest way is using wizard, but sometimes is not going well so we have to configure manually. I try to summarize how device configuration is done. Here is :
  1. Device Configuration wizard
  2. Using tpconfig command
  3. Shared Drive wizard
  4. Using several command line

1. Using Wizard
Using "Device Configuration wizard" is recomended by Veritas rather than "Shared Drive wizard". This wizard performs device discovery, and adds robotic libraries and shared drives to any Media Manager configuration. To perform theese tasks, this wizard uses device serialization. This wizard should be run on a master server.
Here is dialog box for performing Device Configuration wizard :

2. Using tpconfig command
tpconfig command can be used as a command line interface or menu interface to configure robots and drives for use with Netbackup. This command (/usr/openv/volmgr/bin/tpconfig ) starts the Media Manager Device Configuration Utility. This menu-based utility creates and modifies identitiy database in the /usr/openv/volmgr/database directory. Theses database identify the robotics and drives that are under control of ltid (the Media Manager device daemon). ltid uses these files to correlate drives in the operator's drive status display to the device files in the /dev dirctory.
Here is an example when using tpconfig command :

3. Shared Drive wizard
The Shared Drive wizard has limited usage and does not configure robots. Since this wizard does not use device serialization, it requires prior configuration details from you about your configuration before starting. For example: the names of the hosts that will share a drive, drive paths, and the robotic drive parameters and number of the robot that will control the drive.
When using this wizard you can configure only one drive at a time. This may be beneficial if you want to add an individual shared drive without disrupting the other configured drives.
VERITAS recommends the following usage:

- Use the Device Configuration wizard when possible rather than the Shared Drive

Use the Shared Drive wizard with caution after initial device configuration.


4. Using several command line
Here are the steps for configuring device on a media server :
1. login as root
2. go to /usr/openv/volmgr/bin directory

3. execute command ./vmglob -set_gdbhost
4. execute command ./tpautoconf -upgrade
5. execute command ./vmglob -listall

Here is an example command result:

# pwd
/opt/openv/volmgr/bin
# ./vmglob -set_gdbhost master
# ./tpautoconf -upgrade
The NetBackup Installer is now upgrading your device configuration database
in order to maintain compatibility with device discovery...

Finished upgrading device configuration database.
MM host name is Media3, no action required
# ./tpautoconf -a

*some materials is taken from Veritas Netbackup 5.0 Shared Storage Option
System Administrator Guide for UNIX and Windows

RAID

RAID

RAID Short for Redundant Array of Independent (or Inexpensive) Disks, a category of disk drives that employ two or more drives in combination for fault tolerance and performance. RAID disk drives are used frequently on servers but aren't generally necessary for personal computers.
There are number of different RAID levels:
  • Level 0 -- Striped Disk Array without Fault Tolerance: Provides data striping (spreading out blocks of each file across multiple disk drives) but no redundancy. This improves performance but does not deliver fault tolerance. If one drive fails then all data in the array is lost.
  • Level 1 -- Mirroring and Duplexing: Provides disk mirroring. Level 1 provides twice the read transaction rate of single disks and the same write transaction rate as single disks.
  • Level 2 -- Error-Correcting Coding: Not a typical implementation and rarely used, Level 2 stripes data at the bit level rather than the block level.
  • Level 3 -- Bit-Interleaved Parity: Provides byte-level striping with a dedicated parity disk. Level 3, which cannot service simultaneous multiple requests, also is rarely used.
  • Level 4 -- Dedicated Parity Drive: A commonly used implementation of RAID, Level 4 provides block-level striping (like Level 0) with a parity disk. If a data disk fails, the parity data is used to create a replacement disk. A disadvantage to Level 4 is that the parity disk can create write bottlenecks.
  • Level 5 -- Block Interleaved Distributed Parity: Provides data striping at the byte level and also stripe error correction information. This results in excellent performance and good fault tolerance. Level 5 is one of the most popular implementations of RAID.
  • Level 6 -- Independent Data Disks with Double Parity: Provides block-level striping with parity data distributed across all disks.
  • Level 0+1 – A Mirror of Stripes: Not one of the original RAID levels, two RAID 0 stripes are created, and a RAID 1 mirror is created over them. Used for both replicating and sharing data among disks.
  • Level 10 – A Stripe of Mirrors: Not one of the original RAID levels, multiple RAID 1 mirrors are created, and a RAID 0 stripe is created over these.
  • Level 7: A trademark of Storage Computer Corporation that adds caching to Levels 3 or 4.
  • RAID S: EMC Corporation's proprietary striped parity RAID system used in its Symmetrix storage systems.

Network Data Mamagement Protocol (NDMP)

NDMP is a widely used protocol through which an NDMP-conformant backup application can control the backups and restores of any NDMP host that is running an NDMP server application.
The following shows an example of NDMP architecture in a NetBackup configuration


NDMP architecture follows the client/server model.

  • The NetBackup master or media server that has NetBackup for NDMP installed is called a NetBackup for NDMP server.
  • The host where the NDMP server application resides is called an NDMP host.
  • The NetBackup software is a client of the NDMP server application. NetBackup for NDMP is the application that allows NetBackup to be an NDMP client. The NDMP server application on the NDMP host performs backups and restores of the NDMP host, directed by commands received from an NDMP client (NetBackup):

During a local backup or restore:

  • The data travels between the NDMP host’s disk and its locally attached storage devices.
  • During a three-way backup or restore:
  • The data travels over the network, between an NDMP host and a storage device that is attached to another NDMP host configured on the network.
  • During a three-way backup called remote NDMP:
  • The data travels over the network between an NDMP host and a storage device that is attached to a NetBackup media server.

*from support.veritas.com

Veritas NetBackup for Oracle

Veritas NetBackup for Oracle

VERITAS NetBackup is an enterprise backup and recovery solution that provides highly scalable support for a wide variety of servers and clients, together with extensive media management capabilities. NetBackup supports all leading tape vaults and optical disk libraries, and incorporates years of expertise in managing distributed backups, securely and safely, for optimal performance.
As an Oracle Backup Solutions Partner, VERITAS has created database-specific support for Oracle databases using Oracle-supplied interfaces. NetBackup for Oracle is tightly integrated with Oracle’s Recovery Manager (RMAN) product for Oracle 8.x, and the Enterprise Backup Utility (EBU) for Oracle 7.x databases. These interfaces, created and supported by Oracle Corporation, manage the basic backup and recovery operations, packaging much of the work that the DBA previously performed manually. The NetBackup server manages backup policies and schedules, and communicates with the storagemedia.
A single NetBackup server can manage multiple Oracle database backups, providing centralized storage management and leveraging high speed or high capacity storage devices. This solution combines both storage management and Oracle expertise to improve the availability, manageability and reliability of Oracle data and servers.

Improving the Availability of Oracle Databases
VERITAS NetBackup for Oracle is a flexible and scalable solution for enterprise database backups. Whether used for a small, critical database or a number of large databases, NetBackup gives DBAs the tools to protect both the data itself and the availability of the database applications.
Netbackup optimizes database availability in two important ways. Superior backup performance and hot backup support minimizes the impact of backups on production systems. Fast data restoration and simplified recovery brings databases back online faster after failures.

Hot backup support
VERITAS NetBackup supports any combination of cold or hot backups, so DBAs can create the backup schedules that best suit their needs and adjust those schedules as the database grows.
Through its integration with Oracle RMAN (or EBU for Oracle 7.x), NetBackup for Oracle simplifies the process of making and maintaining hot backups. It manages the processes of altering the database state for backups, backing up all of the appropriate files and archived redo logs, and tracking all of the backup information needed for a fast and accurate recovery.

Oracle incremental backups
RMAN supports incremental backups, in which only changed data is written to the backup. During an Oracle incremental backup, RMAN scans the database for changed database blocks. However, with the NetBackup Block Level Incremental Backup Extension, NetBackup for Oracle supports an additional kind of incremental backup. NetBackup can write only the changed file system blocks. This kind of backup typically writes smaller block sizes, and does not require scanning the database.


* from www.veritas.com
Veritas Netbackup

Veritas Netbackup

Veritas NetBackup delivers high-performance data protection that scales to protect the largest UNIX, Windows, Linux, and NetWare environments. With complete protection from the desktop to the data center, NetBackup offers a single console for management of all backup and recovery operations.

Product Highlights

End-To-End Data Protection
Data protection for all environments, from desktop to datacenter to vault.
Single Solution for All Platforms. NetBackup helps you to consolidate and standardize your backup and recovery operations, protecting all major UNIX variants,Windows, Linux, and NetWare systems.

Unlimited Scalability

Centralized management and control, high-performance technology and a flexible multitier architecture enable NetBackup software to adapt to the growing needs of the modern data center.

Unparalleled Performance
Synthetic backups consume less network bandwidth and decrease the impact on the application host since files are backed up only once. Multiplexing up to 32 different data streams to a single tape drive helps to realize the maximum rated throughput of your storage hardware.

Management and Reporting
The NetBackup Operations Manager delivers web based management and reporting for large NetBackup enterprise users. Provides real-time monitoring, historical reporting, administration, alert management and troubleshooting assistance.

Advanced Data Protection

Perform low impact, high performance backup and restores with the NetBackup Advanced Client. This consolidated suite of snapshotbased technologies enables FlashBackup, Instant Recovery, Offhost and Block-Level Incremental data protection.

Automate Disaster Recovery

The NetBackup Vault option automates the disaster recovery process by helping to simplify tape rotation and the creation and management of tape duplicates for offsite vaulting. NetBackup Bare Metal Restore streamlines the server recovery process.
NetBackup Administration Console provides a single point of management that enables backup administrators to manage a larger number of servers more efficiently.

Extensive Media Management

Allows users to share an automated tape library between heterogeneous systems UNIX, Windows, Linux, NetWare or network attached storage (NAS) — allowing NetBackup users to more effectively leverage their expensive tape and drive resources.

Security

Secure your backup data by selecting from NetBackup software’s 40-, 56-, 128-, or 256-bit encryption. NetBackup software’s low-impact encryption option ensures the data is secure before it leaves the client. NetBackup Access Control offers the flexibility to restrict or provide specific access levels to NetBackup software’s administrative functionality.

Storage Networking

NetBackup software supports a broad range of tape library, tape drive and Storage Area Network (SAN) interconnect technologies from leading vendors. Dynamically share individual tape drives over SCSI or a SAN, or utilize the optional NetBackup for NDMP agent to help protect popular network attached storage (NAS) devices.

*www.veritas.com/www.symantec.com


Backup Type

Backup Type

1. Full backup
Full backup is the starting point for all other backups, and contains all the data in the folders and files that are selected to be backed up. Because full backup stores all files and folders, frequent full backups result in faster and simpler restore operations. Remember that when you choose other backup types, restore jobs may take longer.

2. Cumulative-Incremental Backup
A differential backup contains all files that have changed since the last FULL backup. The advantage of a differential backup is that it shortens restore time compared to a full backup or an incremental backup. However, if you perform the differential backup too many times, the size of the differential backup might grow to be larger than the baseline full backup.

3. Differential-Incremental Backup
An incremental backup stores all files that have changed since the last FULL OR DIFFERENTIAL backup. The advantage of an incremental backup is that it takes the least time to complete. However, during a restore operation, each incremental backup must be processed, which could result in a lengthy restore job.

4. Synthetic Backups
A synthetic full backup is a backup assembled from a previous, non synthetic full backup, adn subsequent differential backups and/or a cummulative incremental backup. A client can then use the synthesized backup to restore files and directories in the sam wa that the clients restore from traditional backup.
About Fibre Optic

About Fibre Optic

For modern glass optical fiber, the maximum transmission distance is limited not by attenuation but by dispersion, or spreading of optical pulses as they travel along the fiber. Dispersion in optical fibers is caused by a variety of factors. Intermodal dispersion, caused by the different axial speeds of different transverse modes, limits the performance of multi-mode fiber. Because single-mode fiber supports only one transverse mode, intermodal dispersion is eliminated. For single-mode fiber performance is limited by chromatic dispersion, which occurs because the index of the glass varies slightly depending on the wavelength of the light, and light from real optical transmitters has nonzero spectral width. Polarization mode dispersion, which can limit the performance of single-mode systems, occurs because although the single-mode fiber can sustain only one transverse mode, it can carry this mode with two different polarizations, and slight imperfections or distortions in a fiber can alter the propagation velocities for the two polarizations. Dispersion limits the bandwidth of the fiber because the spreading optical pulse limits the rate that pulses can follow one another on the fiber and still be distinguishable at the receiver.

Because the effect of dispersion increases with the length of the fiber, a fiber transmission system is often characterized by its bandwidth-distance product, often expressed in units of Mhz×km. This value is a product of bandwidth and distance because there is a tradeoff between the bandwidth of the signal and the distance it can be carried. For example, a common multimode fiber with bandwidth-distance product of 500 MHz×km could carry a 500 MHz signal for 1 km or a 1000 MHz signal for 0.5 km.

In single-mode fiber systems, both the fiber characteristics and the spectral width of the transmitter contribute to determining the bandwidth-distance product of the system. Typical single-mode systems can sustain transmission distances of 80 to 140 km (50 to 87 miles) between regenerations of the signal. By using an extremely narrow-spectrum laser source, data rates of up to 40 gigabits per second are achieved in real-world applications.
Advanced Technology Attached (ATA) Disk

Advanced Technology Attached (ATA) Disk

The ATA standard define a simple, inexpensive method for attaching disk drive to host system and was one of the first attempts at developing a storage standard. The original ATA standard (ATA-1) was formally defined in 1993 and has gone through five major revisions up to the current standard, ATA-6. The standard defines a simple method to connect high-volume disk devices with internal controllers to host systems. It incorporates all layers of the protocol in a single standard, from the 80-pin parallel connector to the commands recognized by the disk drives.

In the late 1990s, many companies started to recognize that the existing ATA standard had many limitations that would prevent it from scaling up to support future generation systems. The biggest issues were :
  • It required a 5-volt signal, while many newer integrated circuits were moving to a 3.3-volt standard.
  • The cable require 80 wires, making them expensive and subject to electronic magnetic interface (EMI). This EMI limited the maximum speed that could be used with a parallel ATA interface and reduce reliability.
  • In 2000, a group of companies announced the formation of the SATA Working Group to explore the development of a next-generation serial ATA standard.

Serial ATA addresses the limitations of the ATA standard by allowing the commands to be sent over a serial cable connection with significantly fewer wires, which greatly reduces the EMI and allows much higher data speed to be obtained. It also reduces the complexity of the cabling and reduces the voltage requirements from 5 volts to 3.3 volts. These changes allow first version of the serial ATA specification to provide 150 MB/s throughput, compared with parallel ATA’s limitation of 133 MB/s. The serial ATA-2 standard, release in 2003, increase this to over 300 MB/s and even more advanced versions are under development. This ensures that Serial ATA drives can provide significantly higher levels of performance while maintaining the low coast per megabyte associated with ATA disk drives.

Another advantage to Serial ATA specification is reliability and availability. There are three primary reliability/availability benefits inherent in the basic SATA specification:
  • Simplified cabling
  • Integrated Cyclic Redundancy Checks (CRC)
  • Hot-swappability
The simplified cables significantly reduce the impact of EMI and improve reliability of the data getting to the disk. They also reduce the number of failures attribute to bad cables. Integrated CRC checking helps ensure that the data that actually gets stored on the drives is what the application sent. Host-swappable drives ensure that a failed drive can be replaced without having to bring an entire system down. For data that is stored redundantly-either through mirroring or some from of parity mechanism-a failed drive can be replaced without interrupting a host’s access to the data.

*from http://www.emc.com
Host Bus Adapter (HBA)

Host Bus Adapter (HBA)

A host bus adapter (HBA) is a circuit board and/or integrated circuit adapter that provides input/output (I/O) processing and physical connectivity between a server and a storage device. Because the HBA relieves the host microprocessor of both data storage and retrieval tasks, it can improve the server's performance time. An HBA and its associated disk subsystems are sometimes referred to as a disk channel.

The differences between a NIC and an HBA
Host Bus Adapters (HBAs) differ from network interface cards (NICs) in a fundamental way. A NIC relies heavily on the server CPU for protocol processing, including such functions as main­taining packet sequence order, segmentation and re-assembly, error detection and correction, and flow control. Functions actually performed by a NIC are limited to low level duties such as framing packets and controlling the flow of data to the link layer. As a result, I/O requests that rely on a NIC for execution put a considerable compute burden on the host server CPU and severely impact overall system performance. A NIC can utilize 80% or more of a server CPU to deliver 50-80MB/s on a Gigabit Ethernet link. This method of using an expensive server to perform I/O processing adds considerable real cost to what may appear to be an inexpensive network interface card.

By contrast, an HBA manages the entire I/O transaction with little or no involvement of the server CPU. The HBA receives an I/O request from the operating system and completely handles such activities as segmentation and re-assembly, flow control, error detection and correction, as well as the SCSI command processing. By off-loading the server CPU, HBAs can provide throughput at nearly link speed with typically less than 10% server CPU utilization.
In simple terms, HBAs provide I/O processing and the physical connection between servers and storage. Host bus adapters provide critical server CPU off-load, freeing servers to perform application processing. As the only part of a storage area network that resides in a server, HBAs also provide the physical link between the SAN and the OS and application software. In this role the HBA enables a range of high-availability and storage management capabilities, including load balancing, fail-over, SAN administration, and storage management.

Why does server CPU off-load matter?
The need for CPU off-load is becoming increasingly important because of the wide adoption of storage area networking, and the emergence of processing intensive protocols such as iSCSI.

Host bus adapters differ from network interface cards (NICs) in a fundamental way. A NIC relies heav­ily on the server CPU for protocol processing. Historically, I/O data rates increased at approximately the rate of Moore’s law, which allowed servers to maintain I/O processing performance from one product generation to the next. Network­ing technologies, however, have historically increased data rates in 10x increments. The adoption of storage networking has driven increases in storage I/O data rates closer to those of traditional networking technologies, with increases of 4x to 10x. This trend shows no signs of slowing down as iSCSI and Fibre Channel prepare to support up to 10Gb/s data rates in the future.

The accelerating I/O data rates creates an “I/O processing gap” in which the compute power needed to fill a fast pipe is grow­ing faster than the CPU power available in the server. Without sufficient processing power, a high-speed storage network will be under-utilized. An HBA is needed to fill the I/O processing gap and provide the performance and efficiency that storage network­ing promises.

Host Bus Adapter architecture
HBA architectures vary, but the most capable products have an on-board processor, a protocol controller ASIC, buffer memory to maintain data flow, and specialized hardware to provide superior performance in complex storage area networks.
HBAs also provide a critical interface between the SAN and the server. With on-board intelligence providing the ability to analyze each frame of data that passes through it, as well as awareness of each SAN device and the server OS, the HBA provides a criti­cal control point for management applications. Using industry standard Application Programming Interfaces (APIs), HBAs can provide management applications with access to information about the SAN, and the ability to manage storage devices and the storage network itself.

Summary
HBAs provide critical server CPU off-load that enables high-performance storage networking. By completely managing I/O processing, HBAs free the server’s CPU to process application and database activities. HBAs also play a key role in enabling the management of storage networks.


*http://www.emulex.com
Back To Top