Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ Commands Reference Guide
  3. Appendix A. NetBackup Commands
  4. vltinject
Veritas NetBackup™ Commands Reference Guide

Name

vltinject — inject volumes into a robot for a specified vault configuration

SYNOPSIS

vltinject profile|robot/vault/profile [-version]

 

On UNIX systems, the directory path to this command is /usr/openv/netbackup/bin/

On Windows systems, the directory path to this command is install_path\NetBackup\bin\

DESCRIPTION

vltinject injects volumes into a robot and updates the Enterprise Media Manager Database. It runs vmupdate and assigns it the robot number, robot type, and robotic volume group from the vault configuration that matches the specified profile.

If the following directory exists and has public write access, vltinject writes to the daily debug log file:

UNIX systems: usr/openv/netbackup/logs/vault

Windows systems: install_path\netbackup\logs\vault

The daily debug log file is log.DDMMYY; the DDMMYY is the current date.

You then can use this file for troubleshooting. Public-write access is needed because not all executables that write to this file can run as administrator or root.

Any authorized user can run this command.

For more information about NetBackup authorization, refer to the NetBackup Security and Encryption Guide.

OPTIONS

profile|robot/vault/profile

The name of a profile or a robot number, vault, and profile that are nested within the vault configuration file. If profile is used without robot and vault, the profile must be unique. vltinject executes vmupdate with the robot number, robot type, and robotic volume group from this profile's configuration.

-version

Display the vltinject version and exit.

EXAMPLES

Example 1 - Inject the volumes that the Payroll profile has vaulted and that were returned from the off-site vault, enter the following:

# vltinject Payroll

Example 2 - Inject the volumes that the Weekly profile (in the Finance vault) vaulted and that the off-site vault has returned. The user enters the following:

# vltinject 8/Finance/Weekly

RETURN VALUES

0 - The EMM database was successfully updated.

Non-zero - A problem was encountered updating the EMM database.

Vault may exit with a status code greater than 255. Such status codes are called extended exit status codes. For such a case, the exit status that is returned to the system is 252. The actual exit status is written to stderr in the format, EXIT status = exit status.

FILES

UNIX systems:

/usr/openv/netbackup/logs/vault/log.mmddyy

Windows systems:

install_path\NetBackup\logs\vault\mmddyy.log

Feedback

Was this page helpful?
Previous

vlteject

Next

vltoffsitemedia

Feedback

Was this page helpful?