Hello Vlad,
Please let me know if the below config files help.
1) Run the Snap Creator agent as root user
2) Unix User BD4 and BV4 with associated shell profiles
3) 2 different config files from Snap Creator perspective (example BD4.conf and BV4.conf)
4) In BD4.conf
SYBASE_SERVER=BD4 (instance name)
SYBASE_USER=BD4 (available in UNIX only)
SYBASE_DATABASES=DB1:USER:PASSWORD (refer syntax below for +ALL)
SYBASE=/sybase/BD4
SYBASE_ISQL_CMD=path-to-isql
5) In BV4.conf
SYBASE_SERVER=BV4 (instance name)
SYBASE_USER=BV4 (available in UNIX only)
SYBASE_DATABASES=DB1:USER:PASSWORD (refer syntax below for +ALL)
SYBASE=/sybase/BV4
SYBASE_ISQL_CMD=path-to-isql
#################All Options available in SYBASE plugin ##############
- SYBASE_SERVER the sybase dataserver name (-S option on isql)
example: SYBASE_SERVER=p_test
- SYBASE_DATABASES the list of databases within the instance to backup. Format is
"DB1:USER:PASSWD;DB2:USER:PASSWD" The master database is added as a matter of course. If a database
called "+ALL" is used then database autodiscovery will be used and excludes the sybsyntax,
sybsystemdb, sybsystemprocs and tempdb databases. The password are used are passwd to isql as -P.
encrypted passwords are supported if NTAP_PWD_PROTECTION is set.
example: SYBASE_DATABASES=DBAtest2:sa/53616c7465645f5f76881b465ca8ce3745c239b60e04351e
example: SYBASE_DATABASES=+ALL:sa/53616c7465645f5f76881b465ca8ce3745c239b60e04351e
- SYBASE_DATABASES_EXCLUDE allows databases to be excluded if the +ALL construct is used use ';'
to allow multiple databases to be used.
example: SYBASE_DATABASES_EXCLUDE=pubs2;test_db1.
- SYBASE_TRAN_DUMP allows post snapshot sybase transaction dump to be performed. Each database
requiring a txn dump needs to be specified. Format is "DB1:PATH;DB2:PATH" where path is a
directory.
example: SYBASE_TRAN_DUMP=pubs2:/sybasedumps/pubs2
- SYBASE_TRAN_DUMP_FORMAT Allows the dump naming convention to use specified to match site
specific formats. Three "keys" can be specified, %S = Instance name from SYBASE_SERVER
%D is database from SYBASE_DATABASES and %T is a unique timestamp. Default format is %S_%D_%T.cmn
example: SYBASE_TRAN_DUMP_FORMAT=%S_%D_%T.log
- SYBASE_TRAN_DUMP_COMPRESS Allows native sybase transaction dump compression to be enabled.
example: SYBASE_TRAN_DUMP_COMPRESS=Y
- SYBASE_ISQL_CMD defines the path to the "isql" command to use.
example: SYBASE_ISQL_CMD=/opt/sybase/OCS-15_0/bin/isql
- SYBASE the location of the sybase install
example: SYBASE=/sybase
- SYBASE_LOGDIR defines the directory where snap creator logs will be placed
example: SYBASE_LOGDIR=/usr/local/ntap/scServerX.X.X/logs
- SYBASE_MANIFEST allows those databases where a manifest file should be created and the location
where they should be placed. Needed for database mount to be supported.
example: SYBASE_MANIFEST=DBAtest2:/t_inf_nzl_devs/
- SYBASE_MANIFEST_FORMAT Allows the manifest naming convention to use specified to match site
specific formats. Three "keys" can be specified, %S = Instance name from SYBASE_SERVER
%D is database from SYBASE_DATABASES and %T is a unique timestamp which is the same as used for
snapshot naming. Default format is %S_%D_%T.manifest
example: SYBASE_MANIFEST_FORMAT=%S_%D_%T.manifest
- SYBASE_MANIFEST_DELETE allows the manifest to be deleted once the snapshot has been performed. The
manifest file should be captured within the snapshot so it is always available with the backup.
example: SYBASE_MANIFEST_DELETE=Y
