Veritas NetBackup™ DataStore SDK Programmer's Guide for XBSA 1.1.0
- Introduction to NetBackup XBSA
- How to set up the SDK
- Using the NetBackup XBSA interface
- NetBackup XBSA data structures
- NetBackup XBSA environment
- XBSA sessions and transactions
- Creating a NetBackup XBSA application
- Initiating a session
- Backup - creating an object
- Query - finding an object descriptor
- Restore - retrieving an object's data
- Delete - deleting an object or image
- Media IDs - obtaining media IDs
- How to build an XBSA application
- How to run a NetBackup XBSA application
- About How to run a NetBackup XBSA application
- API reference
- Function calls
- Function specifications
- Type definitions
- Process flow and troubleshooting
- How to use the sample files
- Support and updates
- Appendix A. Register authorized locations
NetBackup XBSA object data contains the actual data entity that is archived or backed up by an XBSA application. The NetBackup XBSA API supports only one type of object data, which is a variable-length, unstructured and uninterpreted byte-stream.
To a specific XBSA application, however, the XBSA object data can contain an internal structure that reflects the data of the application objects that the XBSA application has archived or backed up. In this context, the XBSA object data can contain one of the following examples: a UNIX file system, a UNIX directory, a file, a document, a disk image, a data stream, or a memory dump.
Through the NetBackup XBSA interface, object data can be stored, retrieved, or deleted, but not searched or modified. Since the object data can be stored on slow (or offline) media, it is generally not advisable for an XBSA application to store metadata in object data, especially the information that can influence a data-retrieval decision.
However, the metadata of an XBSA object, that is stored in the catalog, can be replicated in its object data if it enhances the performance of the object restore. This is an XBSA application implementation decision.