NetBackup™ OpenStorage Solutions Guide for Disk
- Introducing disk appliance storage solutions
- Planning your deployment
- Planning your OpenStorage deployment
- About OpenStorage requirements and limitations
- About OpenStorage storage servers for backups
- About OpenStorage server credentials
- About OpenStorage data movers for backups
- About the OpenStorage plug-in
- About OpenStorage disk pools for backups
- About OpenStorage optimized duplication and replication
- About OpenStorage optimized synthetic backups
- About storage unit groups for OpenStorage
- About OpenStorage direct to tape
- Provisioning the storage
- Licensing OpenStorage
- Configuring OpenStorage in NetBackup
- Configuring OpenStorage disk appliance storage
- Configuring an OpenStorage storage server for backups
- Configuring an OpenStorage disk pool for backups
- Configuring an OpenStorage storage unit
- Configuring OpenStorage optimized synthetic backups
- Configuring OpenStorage direct to tape
- Configuring optimized duplication to an OpenStorage device within the same NetBackup domain
- Configuring replication to an OpenStorage device in a different domain
- About storage lifecycle policies
- About the storage lifecycle policies required for Auto Image Replication
- Creating a storage lifecycle policy
- Creating a backup policy
- Adding OpenStorage functionality to an existing environment
- Managing OpenStorage
- Managing OpenStorage storage servers
- Viewing OpenStorage storage servers
- Determining OpenStorage storage server state
- Changing OpenStorage storage server properties
- Setting OpenStorage storage server attributes
- Removing OpenStorage storage server attributes
- Updating an OpenStorage storage server to reflect plug-in updates
- Deleting an OpenStorage storage server
- Managing OpenStorage server credentials
- Managing OpenStorage data movers
- Managing OpenStorage disk pools
- Viewing OpenStorage disk pools
- Determining an OpenStorage disk pool state
- Changing OpenStorage disk pool state
- Determining OpenStorage disk volume state
- Changing OpenStorage disk volume state
- Changing OpenStorage disk pool properties
- Setting OpenStorage disk pool attributes
- Removing OpenStorage disk pool attributes
- Adding volumes to an OpenStorage disk pool
- Merging OpenStorage disk pools
- Removing a volume from an OpenStorage disk pool
- Updating an OpenStorage disk pool to reflect plug-in updates
- Updates to NetBackup OpenStorage entities
- Deleting an OpenStorage disk pool
- Monitoring OpenStorage storage capacity and usage
- Viewing OpenStorage disk reports
- Reporting on Auto Image Replication jobs
- About catalog backups to OpenStorage devices
- About restoring from OpenStorage backup copies
- About restoring from a backup at a target primary domain
- Managing OpenStorage storage servers
- Troubleshooting
- Index
About legacy logging
In NetBackup legacy debug logging, a process creates log files of debug activity in its own logging directory. By default, NetBackup creates only a subset of logging directories, in the following locations:
Windows | install_path\NetBackup\logs install_path\Volmgr\debug |
UNIX | /usr/openv/netbackup/logs /usr/openv/volmgr/debug |
To use legacy logging, a log file directory must exist for a process. If the directory is not created by default, you can use the or the mklogdir batch files to create the directories. Or, you can manually create the directories. When logging is enabled for a process, a 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.
Note:
It is recommended to always use the mklogdir utility present in Windows and Linux to create the legacy log directories for each platform, in order to have appropriate permissions on them.
You can use the following batch files to create all of the log directories:
Windows: install_path\NetBackup\Logs\mklogdir.bat
UNIX: /usr/openv/netbackup/logs/mklogdir
Follow these recommendations when you create and use legacy log folders:
Do not use symbolic links or hard links inside legacy log folders.
If any process runs for a non-root or non-admin user and there is no logging that occurs in the legacy log folders, use the mklogdir command to create a folder for the required user.
To run a command line for a non-root or non-admin user (troubleshooting when the NetBackup services are not running), create user folders for the specific command line. Create the folders either with the mklogdir command or manually with the non-root or non-admin user privileges.