Veritas NetBackup™ Logging Reference Guide
- Using logs
- Changing the logging levels
- About unified logging
- About legacy logging
- Backup process and logging
- Media and device processes and logging
- Restore process and logging
- Advanced backup and restore features
- Storage logging
- NetBackup Deduplication logging
- OpenStorage Technology (OST) logging
- Storage lifecycle policy (SLP) and Auto Image Replication (A.I.R.) logging
- NetBackup secure communication logging
- NetBackup proxy helper logging
- NetBackup proxy tunnel logging
- Snapshot technologies
- Locating logs
- NetBackup Administration Console logging
- Using the Logging Assistant
Media and device management startup process
Media and device management processes are automatically initiated during NetBackup startup. To start these processes manually, run
bp.start_all (UNIX) or bpup (Windows). The ltid command automatically starts other daemons and programs as necessary.
See Figure: Starting media and device management.
For robotic daemons like tl8d and tlhd, the associated robot must also be configured for the daemon to run. Additional ways to start and stop daemons are available. You must know the hosts that are involved to start all the daemons for a robot.
See Table: Media and device management directories and files.
TL8, TLH, and TLD require following types of daemons:
Each host with a robotic drive attached must have a robotic daemon. These daemons provide the interface between ltid and the robot. If different drives within a robot can attach to different hosts, the robotic daemon communicates with a robotic-control daemon (see Figure: Starting media and device management).
Robotic-control daemons centralize the control of robots when drives within a robot can connect to different hosts. A robotic-control daemon receives mount and unmount requests from the robotic daemon on the host to which the drive is attached. It then communicates these requests to the robot.