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
- How to build an XBSA application
- 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
Backup transaction
An XBSA application can create a NetBackup XBSA object in a backup transaction. The first BSACreateObject() call defines the backup transaction. The BSACreateObject() function takes as input an object descriptor that has all of the XBSA attributes of the object. After the BSACreateObject() call, the object's data is passed to NetBackup in buffers using a sequence of BSASendData() calls. When all data has been sent, the object is completed with a BSAEndData() call. Multiple objects may be created in one transaction, although BSAEndData() must be called before the next BSACreateObject() is called.
The NetBackup XBSA interface treats backup and archive transactions the same. The XBSA application performs any extra operations that can be associated with an archival. The XBSA application is also responsible for any other backup types such as an incremental backup. The NetBackup archive and incremental backups do not apply to the NetBackup XBSA interface. All of the information that is required to restore an object needs to be contained in the object descriptor or object data.
Within a backup transaction, query, delete, and restore operations are not allowed.