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
Client in a cluster
Running an XBSA application in a clustered environment is a valid mode of operation. The key thing about running in a cluster is to ensure that the client name used when an object is created is the same as the client name used when the object is being queried or retrieved. To ensure that the same client name is used, the XBSA application should use the virtual name of the clients in the cluster. The best way to do this would be to use the NBBSA_CLIENT_HOST variable and set it to the virtual name for both creating and retrieving an object. The virtual name needs to be the client name that is configured in the NetBackup policy. Another option is to configure the virtual name as the default NetBackup client name. Configuring in this way causes other NetBackup jobs, such as the file system backups, to use this virtual name also, which may not be desired. If neither of these options is used by the XBSA application, the XBSA interface uses the default client name, which is the physical address of the client. The objects are created successfully, but if the query or retrieval is done from a different node in the cluster, the object is not found.