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™ DataStore SDK Programmer's Guide for XBSA 1.1.0
  3. Using the NetBackup XBSA interface
  4. Creating a NetBackup XBSA application
  5. Query - finding an object descriptor
  6. Querying for an object
Veritas NetBackup™ DataStore SDK Programmer's Guide for XBSA 1.1.0

Querying for an object

When querying for an object, the object attributes that the XBSA application is querying for are contained in a query descriptor. This query descriptor is made up of strings and enumerations. They are evaluated against the objects stored in the NetBackup catalog for objects that match all fields. Each field of the query descriptor must be populated. If a string field is populated with an empty string or NULL, it only matches objects that also have an empty string for that field. Wildcards and 'ANY' enumerations allow the XBSA application to search for objects that have some fields that are unknown.

There are two fields that are not part of the XBSA specifications but can be very useful. The createTime_from and createTime_to fields limit the search to the time period between these dates. These are optional fields, the default is to search all objects, but can greatly speed up the search when the NetBackup catalog is very large.

When doing the query, the XBSA application only returns objects that are owned by the logon user running the query, unless that user is a root admin. NetBackup XBSA Version 1.1.0 uses the logon user as the object owner. The objectOwner field is considered an attribute and is not used for security.

The query, by default, also only returns objects that were created on the hostname from which the query is being run. If the XBSA application needs to find an object that was created from a different host, the NBBSA_CLIENT_HOST environment variable must be set to the hostname from which the object was created. This variable can only be set before a transaction begins. If the application is looking for objects from multiple hosts, the application needs to do queries in separate transactions.

Feedback

Was this page helpful?
Previous

Query - finding an object descriptor

Next

Query example

Feedback

Was this page helpful?