archive_stage and archive_stage_repeat to different NSR_POOLs

[former_member272646]

Hello,

we are using networker for our maxdb backups. At the moment archive_stage is called

via scripts twice:

dbmcli -d TQ2 -U c -uUTL -c archive_stage NSRLOG Autolog NOVERIFY KEEP

dbmcli -d TQ2 -U c -uUTL -c archive_stage NSRLOG Autolog NOVERIFY

The 2 dbmcli-calls run with different env-Files where different NSR_POOLs are specified.

This can be done with setting the environment-Variable NSR_ENV to different files.

This solution has a drawback. In the second call, autolog-files are saved, which were

not saved in the first call. Our LiveCache-OneDB-Server-System generates a lot

of autolog-files.

So, I wanted to use archive_stage and archive_stage_repeat. But this only works

within one dbmcli-session. Within a dbmcli-Session is it not possible to change

the OS-Environment in order to the switch the NSR_ENV-File.

We have to save the autolog-Files twice and to differnt NSR_POOLs.

Does anybody know, how to manage this?

Regards

Thomas

[lbreddemann]

Hi Thomas,

just an idea (I did not test this out):

Don't use the environment variables but the dbm configset command as described in [Setting the Environment Variable NSR_ENV|http://maxdb.sap.com/doc/7_6/62/aba9a9444311d5992400508b6b8b11/content.htm]

I'm not aware of any reason why this should not work.

Simply put the dbm_configset command before each archive_stage* call.

So the script would look like this:

dbm_configset -raw NSR_ENV <path_to_setting#1>
archive_stage NSRLOG Autolog NOVERIFY KEEP
dbm_configset -raw NSR_ENV <path_to_setting#2>
archive_stage_repeat NSRLOG Autolog NOVERIFY 

You may put these commands into a script file and call this via:

dbmcli -U c -uUTL -i <scriptfile> -t <logfile>

(With XUSER data you don't need to specify -d <SID> as this is part of the XUSER data)

Regards,

Lars

[former_member272646]

Hi Lars,

the suggested solution works perfect!

Thank you very much!

Regards

Thomas