Hi,
I am just trying to understand the components in your query.
Correct me here : You have a Netbackup server which uses 'SQL anywhere' as back end Internal database.
From google I found this:
NetBackup 'Catalog' is a place where information about the NetBackup configuration and backups are stored such as records of the files that have been backed up and media where those files copied. NetBackup Catalog is kept on the NetBackup master server and consists of:
1) NetBackup configuration files such as policies, schedules - flat files.
2) NetBackup database (NBDB) - a relational database (Sybase SQL Anywhere)
My advise would be:
For FS (Binaries): If Netbackup master server is VM -> Take vmware snaphost
For Catalog - Configure and take a regular DR backups and keep this DR copy on the CIFS volume ---> Replicate this volume to remote site if you wish using SnapMirror.
In case for DR: Restore the VM and then restore the lastest catalog that you have protected, or install the Netbackup from scratch and use the DR file to bring it up to date.
How to configure a backup policy to protect NetBackup Catalog?
https://www.settlersoman.com/how-to-configure-a-backup-policy-to-protect-netbackup-catalog/
https://www.veritas.com/content/support/en_US/doc/18716246-126559472-0/v41273157-126559472
Another complicated option will be:
Using SnapCenter pre/post commands to quiesce SQL anywhere db using standard unix-plugin for file-system. But, this may or may not be fully dependable, b'cos you will be manually (using script) quiescing dbs, I doubt this is a good idea. Anyway, explore your options.
Good luck.
Thanks!