Veritas NetBackup™ Cloud Administrator's Guide
- About NetBackup cloud storage
- About the cloud storage
- About the cloud storage vendors for NetBackup
- About the Amazon S3 cloud storage API type
- Amazon S3 cloud storage vendors certified for NetBackup
- Amazon S3 storage type requirements
- Amazon S3 cloud storage provider options
- Amazon S3 cloud storage options
- Amazon S3 advanced server configuration options
- Amazon S3 credentials broker details
- About private clouds from Amazon S3-compatible cloud providers
- About Amazon S3 storage classes
- Amazon virtual private cloud support with NetBackup
- Protecting data in Amazon Glacier for long-term retention
- Permissions required for Amazon IAM user
- About NetBackup character restrictions for Amazon S3 cloud connector
- About EMC Atmos cloud storage API type
- About Microsoft Azure cloud storage API type
- About OpenStack Swift cloud storage API type
- OpenStack Swift cloud storage vendors certified for NetBackup
- OpenStack Swift storage type requirements
- OpenStack Swift cloud storage provider options
- OpenStack Swift storage region options
- OpenStack Swift add cloud storage configuration options
- OpenStack Swift proxy settings
- About Rackspace Cloud Files storage requirements
- Rackspace storage server configuration options
- About private clouds from Rackspace
- Configuring cloud storage in NetBackup
- Before you begin to configure cloud storage in NetBackup
- Configuring cloud storage in NetBackup
- Cloud installation requirements
- Scalable Storage properties
- Cloud Storage properties
- About the NetBackup CloudStore Service Container
- Deploying host name-based certificates
- Deploying host ID-based certificates
- About data compression for cloud backups
- About data encryption for cloud storage
- About key management for encryption of NetBackup cloud storage
- About cloud storage servers
- About object size for cloud storage
- About the NetBackup media servers for cloud storage
- Configuring a storage server for cloud storage
- Changing cloud storage server properties
- NetBackup cloud storage server properties
- About cloud storage disk pools
- Configuring a disk pool for cloud storage
- Saving a record of the KMS key names for NetBackup cloud storage encryption
- Adding backup media servers to your cloud environment
- Configuring a storage unit for cloud storage
- About NetBackup Accelerator and NetBackup Optimized Synthetic backups
- Enabling NetBackup Accelerator with cloud storage
- Enabling optimized synthetic backups with cloud storage
- Creating a backup policy
- Changing cloud storage disk pool properties
- Managing Certification Authorities (CA) for NetBackup Cloud
- Monitoring and Reporting
- Operational notes
- Troubleshooting
- About unified logging
- About legacy logging
- NetBackup cloud storage log files
- Enable libcurl logging
- NetBackup Administration Console fails to open
- Troubleshooting cloud storage configuration issues
- NetBackup Scalable Storage host properties unavailable
- Connection to the NetBackup CloudStore Service Container fails
- Cannot create a cloud storage disk pool
- Cannot create a cloud storage
- Data transfer to cloud storage server fails in the SSL mode
- Amazon GovCloud cloud storage configuration fails in non-SSL mode
- Data restore from the Google Nearline storage class may fail
- Backups may fail for cloud storage configurations with Frankfurt region
- Backups may fail for cloud storage configurations with the cloud compression option
- Fetching storage regions fails with authentication version V2
- nbcssc service does not start after installation in clustered environment
- Troubleshooting cloud storage operational issues
About legacy logging
Legacy logging and unified logging are the two forms of debug logging used in NetBackup. All NetBackup processes use either unified logging or legacy logging.
In legacy debug logging, each process creates log files of debug activity in its own logging directory. The NetBackup legacy debug log directories are located in the following directories:
Windows | install_path\NetBackup\logs install_path\Volmgr\debug |
UNIX | /usr/openv/netbackup/logs /usr/openv/volmgr/debug |
These top-level directories can contain a directory for each NetBackup process that uses legacy logging. By default, NetBackup creates only a subset of all of the possible log directories. For example, the following directories are created by default on UNIX servers:
nbfp
nbliveup
nblogadm
user_ops
To enable logging for all of the NetBackup processes that use legacy logging, you must create the log file directories that do not already exist, unless you use the Logging Assistant. For more information about the Logging Assistant, see the NetBackup Administrator's Guide, Volume I. The guide is available at the following location:
http://www.veritas.com/docs/DOC5332
You can use the following batch files to create all of the debug log directories at once:
See the NetBackup Commands Reference Guide for a complete description about the mklogdir command. The guide is available at the following location:
http://www.veritas.com/docs/DOC5332
After the directories are created, NetBackup creates log files in the directory that is associated with each process. A debug log file is created when the process begins. Each log file grows to a certain size before the NetBackup process closes it and creates a new log file.
To enable debug logging for the NetBackup Status Collection Daemon (vmscd), create the following directory before you start nbemm.
As an alternative, you can restart vmscd after creating the directory.
More Information