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.