Veritas NetBackup™ Cloud Administrator's Guide
- About NetBackup cloud storage
- About the cloud storage
- About the Amazon S3 cloud storage API type
- About protecting data in Amazon for long-term retention
- Protecting data using Amazon's cloud tiering
- About Microsoft Azure cloud storage API type
- About OpenStack Swift cloud storage API type
- Configuring cloud storage in NetBackup
- Scalable Storage properties
- Cloud Storage properties
- About the NetBackup CloudStore Service Container
- About the NetBackup media servers for cloud storage
- Configuring a storage server for cloud storage
- NetBackup cloud storage server properties
- Configuring a storage unit for cloud storage
- Changing cloud storage disk pool properties
- Monitoring and Reporting
- Operational notes
- Troubleshooting
- About unified logging
- About legacy logging
- Troubleshooting cloud storage configuration issues
- Troubleshooting cloud storage operational issues
NetBackup cloud storage log files
NetBackup cloud storage exists within the Veritas OpenStorage framework. Therefore, the log files for cloud activity are the same as for OpenStorage with several additions.
Some NetBackup commands or processes write messages to their own log files. For those commands and processes, the log directories must exist so that the utility can write log messages.
Other processes use Veritas unified log (VxUL) files. Each process has a corresponding VxUL originator ID. VxUL uses a standardized name and file format for log files. To view VxUL log files, you must use the NetBackup vxlogview command.
More information about how to view and manage log files is available. See the NetBackup Logging Reference Guide.
The following are the component identifiers for log messages:
An sts_ prefix relates to the interaction with the plug-in that writes to and reads from the storage.
A cloud storage server prefix relates to interaction with that cloud vendor's storage network.
An encrypt prefix relates to interaction with the encryption plug-in.
A KMSCLIB prefix relates to interaction with the NetBackup Key Management Service.
Most interaction occurs on the NetBackup media servers. Therefore, the log files on the media servers that you use for disk operations are of most interest.
Warning:
The higher the log level, the greater the affect on NetBackup performance. Use a log level of 5 (the highest) only when directed to do so by a Veritas representative. A log level of 5 is for troubleshooting only.
Specify the NetBackup log levels in the Table: NetBackup logs for cloud storage.
host properties on the NetBackup master server. The log levels for some processes specific to certain options are set in configuration files as described inTable: NetBackup logs for cloud storage describes the logs.
Table: NetBackup logs for cloud storage
Activity | OID | Processes |
---|---|---|
Backups and restores | N/A | Messages appear in the log files for the following processes:
The log files reside in the following directories:
|
Backups and restores | 117 | The nbjm Job Manager. |
Image cleanup, verification, import, and duplication | N/A | The bpdbm database manager log files. The log files reside in the following directories:
|
Cloud connection operations | N/A | The bpstsinfo utility writes information about connections to the cloud storage server in its log files. |
Cloud account configuration | 222 | The Remote Manager and Monitor Service is the process that creates the cloud storage accounts. RMMS runs on media servers. |
Cloud Storage Service Container | N/A |
This is applicable to media server versions 7.7.x to 8.1.2 only. The NetBackup Cloud Storage Service Container (nbcssc) writes log files to the following directories:
|
NetBackup Web Management Console | 495 | The NetBackup Web Management Console (
|
NetBackup Service Layer | N/A | The NetBackup Service Layer (
|
csconfig utility | N/A | The NetBackup csconfig command-line utility writes logs to the following directories:
|
Credentials configuration | N/A | The tpconfig utility. The tpconfig command writes log files to the |
Device configuration | 111 | The nbemm process. |
Device configuration | 178 | The Disk Service Manager process that runs in the Enterprise Media Manager (EMM) process. |
Device configuration | 202 | The Storage Server Interface process that runs in the Remote Manager and Monitor Service. RMMS runs on media servers. |
Device configuration | 230 | The Remote Disk Service Manager interface (RDSM) that runs in the Remote Manager and Monitor Service. RMMS runs on media servers. |
More Information