NetBackup™ Backup Planning and Performance Tuning Guide
- NetBackup capacity planning
- Primary server configuration guidelines
- Media server configuration guidelines
- NetBackup hardware design and tuning considerations
- About NetBackup Media Server Deduplication (MSDP)
- MSDP tuning considerations
- MSDP sizing considerations
- Accelerator performance considerations
- Media configuration guidelines
- How to identify performance bottlenecks
- Best practices
- Best practices: NetBackup AdvancedDisk
- Best practices: NetBackup tape drive cleaning
- Best practices: Universal shares
- NetBackup for VMware sizing and best practices
- Best practices: Storage lifecycle policies (SLPs)
- Measuring Performance
- Table of NetBackup All Log Entries report
- Evaluating system components
- Tuning the NetBackup data transfer path
- NetBackup network performance in the data transfer path
- NetBackup server performance in the data transfer path
- About shared memory (number and size of data buffers)
- About the communication between NetBackup client and media server
- Effect of fragment size on NetBackup restores
- Other NetBackup restore performance issues
- About shared memory (number and size of data buffers)
- Tuning other NetBackup components
- How to improve NetBackup resource allocation
- How to improve FlashBackup performance
- Tuning disk I/O performance
Legacy error log fields
This section describes the fields in the legacy log files that are written to the following locations:
Linux/UNIX:
/usr/openv/netbackup/db/error
Windows:
install_path\NetBackup\db\error
On Linux/UNIX, there is a link to the most current file in the error directory. The link is called daily_messages.log.
The information in these logs provides the basis for the NetBackup ALL LOG ENTRIES report. For more information on legacy logging and unified logging (VxUL), refer to the NetBackup Troubleshooting Guide.
Here is a sample message from an error log:
1021419793 1 2 4 nabob 0 0 0 *NULL* bpjobd TERMINATED bpjobd
Table: Meaning of daily_messages log fields defines the various fields in this message. The fields are delimited by blanks.
Table: Meaning of daily_messages log fields
Field | Definition | Value |
---|---|---|
1 | Time this event occurred (ctime) | 1021419793 (= number of seconds since 1970) |
2 | Error database entry version | 1 |
3 | Type of message | 2 |
4 | Severity of error: 1: Unknown 2: Debug 4: Informational 8: Warning 16: Error 32: Critical | 4 |
5 | Server on which error was reported |
|
6 | Job ID (included if pertinent to the log entry) | 0 |
7 | (optional entry) | 0 |
8 | (optional entry) | 0 |
9 | Client on which error occurred, if applicable. Otherwise *NULL* | *NULL* |
10 | Process which generated the error message |
|
11 | Text of error message | TERMINATED bpjobd |
Table: Message types lists the values for the message type, which is the third field in the log message.
Table: Message types
Type Value | Definition of this message type |
---|---|
1 | Unknown |
2 | General |
4 | Backup |
8 | Archive |
16 | Retrieve |
32 | Security |
64 | Backup status |
128 | Media device |