Just to update (and close) this thread... the issue here was that while I run NMSAP 8.2SP1 on SAP HANA, my backup server was still 8.0.x and that server does not understand this module (at least not for SAP HANA). As soon as I changed it to use another server which was 8.2.SP1 it went well.
Yes, we use user store key, but to my knowledge that is not used unless you run scheduled backup (that's why you call it in CFG and not profile file). I do get above when running manual backup DB backups from HANA studio (or autolog backups). This is standalone SAP HANA env so it is quite simple.
As noted in initial mail, this was done in form of user=*, host= . Initially I did it for DB admin and operator, but afterwards I extended this to admin group as well - still the error is the same.
ble1
4 Operator
•
14.4K Posts
1
April 21st, 2015 12:00
Just to update (and close) this thread... the issue here was that while I run NMSAP 8.2SP1 on SAP HANA, my backup server was still 8.0.x and that server does not understand this module (at least not for SAP HANA). As soon as I changed it to use another server which was 8.2.SP1 it went well.
ZennaroNicola
1 Rookie
•
88 Posts
0
March 25th, 2015 02:00
Hi
may you share more details please?
Are you using a user store key ?
Is it a stand-alone or scaled out SAP hana enviroment?
regards,
-Nicola
ble1
4 Operator
•
14.4K Posts
0
March 25th, 2015 05:00
Hi Nicolino,
Yes, we use user store key, but to my knowledge that is not used unless you run scheduled backup (that's why you call it in CFG and not profile file). I do get above when running manual backup DB backups from HANA studio (or autolog backups). This is standalone SAP HANA env so it is quite simple.
ZennaroNicola
1 Rookie
•
88 Posts
0
March 25th, 2015 08:00
I don't know if this can help you but from guide:
You have to grant the NetWorker server User Group resource privileges to the SAP user
who performs the SAP HANA operations.
regards,
-Nicola
ble1
4 Operator
•
14.4K Posts
0
March 25th, 2015 09:00
As noted in initial mail, this was done in form of user=*, host= . Initially I did it for DB admin and operator, but afterwards I extended this to admin group as well - still the error is the same.