DSM_DIR not used by TDP for SAP with Oracle

[benoit16]

Good morning,

I would like to perform a SAP system refresh.
On the target system, I would like to run a restore with backfm by specifying an alternate dsm.sys.

I have set DSM_DIR:
% echo $DSM_DIR /var/tmp/restore-XXX

But backint still tries to read only standard location dsm.sys.
% strace /sapmnt/XXX/exe/backint -p /var/tmp/restore-XXX/initXXX.utl -f password | & grep -i open | grep dsm.sys
open("/opt/tivoli/tsm/client/api/bin64/dsm.sys", O_RDONLY) = 4
open("/opt/tivoli/tsm/client/api/bin64/dsm.sys", O_RDONLY) = 5
open("/opt/tivoli/tsm/client/api/bin64/dsm.sys", O_RDONLY) = 5

Then, of course the server name is not found:
% /sapmnt/XXX/exe/backint -p /var/tmp/restore-XXX/initXXX.utl -f password

Data Protection for mySAP(R)

Interface between BR*Tools and Tivoli Storage Manager
- Version 5, Release 3, Modification 3.0 for Linux x86_64 -
Build: 293 compiled on Jul 11 2006
(c) Copyright IBM Corporation, 1996, 2006, All Rights Reserved.

BKI2027I: Using TSM-API version 6.3.2.0 (compiled with 5.3.0.1).
BKI2000I: Successfully connected to ProLE on port tdpr3ora64.
BKI0005I: Start of program at: Fri 16 Sep 2016 11:39:43 AM CEST .
BKI2017I: Blocksize is set to 131072 bytes
BKI0049I: Please enter password for node on server RESTORE-XXX:
BKI0052E: Password verification for node on server RESTORE-XXX failed.
BKI5001E: Tivoli Storage Manager Error:
Server not found in configuration file.
BKI0020I: End of program at: Fri 16 Sep 2016 11:39:44 AM CEST .
BKI0021I: Elapsed time: 01 sec .
BKI0024I: Return code is: 2.

1. Why is the DSM_DIR env variable ignored?
2. How can I configure TDP to use a specific path?

Thanks in advance for your answers.

 

[marclant]

1. Why is the DSM_DIR env variable ignored?

DSM_DIR is for the baclient
DSMI_DIR is for the API, all TDP products use the API.

2. How can I configure TDP to use a specific path?

https://www.ibm.com/support/knowled...itsm.erp.doc/t_dperp_c_cfg_tsmclientunix.html
Typically, you use the dsm.sys in api64, but you use your own dsm.opt with the SERVERNAME pointing to an existing stanza in dsm.sys. And use DSMI_CONFIG to specify which option file you are using. More details in the link above.

 

[benoit16]

Good afternoon,

DSM_DIR is for the baclient
DSMI_DIR is for the API, all TDP products use the API.

You are right. Setting DSMI_DIR has worked.
I also had to copy the /opt/tivoli/tsm/client/ba/bin/EN_US in the DSMI_DIR,
to have backfm working.

Would you know why?

Regards,

 

[marclant]

DSMI_DIR is supposed to point to the API directory. The proper config would be:

DSMI_CONFIG=/var/tmp/restore-XXX/dsm.opt
DSMI_LOG=/var/tmp/restore-XXX
DSMI_DIR=/opt/tivoli/tsm/client/api/bin64

/var/tmp/restore-XXX/dsm.opt:

SERVERNAME  SAPNODE

/opt/tivoli/tsm/client/api/bin64/dsm.sys:

SERVERNAME  FILENODE
   NODENAME ....
   ...

SERVERNAME SAPNODE
   NODENAME ....
   ....

 

[benoit16]

Good afternoon,

I not want to add "SERVERNAME SAPNODE" in the standard dsm.sys.
This is why I use DSMI_DIR.

By the way, with the dsm.sys that you have provide, how do you ensure that a dsmc inc chooses FILENODE and not SAPNODE?

Thanks in advance for your answer.

 

[marclant]

I not want to add "SERVERNAME SAPNODE" in the standard dsm.sys.
This is why I use DSMI_DIR.

That's not the purpose of DSMI_DIR, it's to point to the API.

By the way, with the dsm.sys that you have provide, how do you ensure that a dsmc inc chooses FILENODE and not SAPNODE?

the dsm.opt (DSM_CONFIG) used by the filesystem backup will have: SERVERNAME FILENODE in it to tell it which stanza to use.

 

[benoit16]

Good afternoon,

That's not the purpose of DSMI_DIR, it's to point to the API.

But that it is the only way that offer TSM to use an alternate dsm.sys.
As I do not want to change the default dsm.sys, I do not have other alternatives.
Do you agree with me?

the dsm.opt (DSM_CONFIG) used by the filesystem backup will have: SERVERNAME FILENODE in it to tell it which stanza to use.

My question was no precise enough.
In the case there is no SERVERNAME FILENODE, in dsm.opt, how is dsmc going to decide which stanza is going to be used?

Thanks in advance for your answers.

 

[marclant]

But that it is the only way that offer TSM to use an alternate dsm.sys.
As I do not want to change the default dsm.sys, I do not have other alternatives.
Do you agree with me?

You are right that TSM doesn't offer alternatives to use a different path. And if you do it with a hack like you are suggesting, you are adding complexity to the environment and the next time you upgrade the API, it will update the default path and ignore your alternate path. It's your environment, you do whatever you want, just be aware that you may be creating more work than what it's worth.

In the case there is no SERVERNAME FILENODE, in dsm.opt, how is dsmc going to decide which stanza is going to be used?

By default, it connects to the first servername in dsm.sys. If you have more than one and want to use a different one, you need to use the servername option. https://www.ibm.com/support/knowled....ibm.itsm.client.doc/t_cfg_crtmodoptunix.html