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
BSA_ObjectOwner
The BSA_ObjectOwner structure is the name of the owner of an object. It is defined as follows:
typedef struct { char bsa_ObjectOwner[BSA_MAX_BSAOBJECT_OWNER]; char app_ObjectOwner[BSA_MAX_APPOBJECT_OWNER]; } BSA_ObjectOwner;
The usage of the structure fields is defined as follows:
Table: BSA_ObjectOwner Structure Fields
Field Name | Definition |
---|---|
bsa_ObjectOwner | The name that the NetBackup XBSA interface authenticates |
app_ObjectOwner | The name defined by the application |
In NetBackup XBSA Version 1.1.0, the actual object owner is determined between the NetBackup XBSA interface and NetBackup. If the XBSA application specifies the bsa_ObjectOwner, the value is stored with the object or validated against it, but it does not define the object ownership. If the object was created by a different user, unless you are a root administrator, you cannot restore the object even if you specify the correct bsa_ObjectOwner.
An app_ObjectOwner is an optional name, such as an actual end-user name, provided by the respective XBSA application, so that the NetBackup XBSA interface can provide assistance to support application-specific access control by optimizing access for the given app_ObjectOwner.
The app_ObjectOwner can have multiple components defined in the application, such as a group name and a user ID. In general, it is a hierarchical character string. An app_ObjectOwner is not registered with the NetBackup XBSA interface. Its registration and authentication is the responsibility of the XBSA application. Examples of a typical app_ObjectOwner are Smith, AccountingDept.Clerk1 and * (unspecified).