Hi guys,

I'm testing the new Data Protection 8.1.9 client on a new SP server which uses 
node replication. When the user starts a backup he receives the following 
errors:

02/12/2020 14:19:33 ANS4058I A write failure occurred while attempting to save 
node replication failover values to the options file.
02/12/2020 14:19:33 ANS0361I DIAG: cacheobj.cpp        ( 594): dbOpen(): error 
opening/creating lock file 
'/opt/tivoli/tsm/client/api/bin64/tsmnrtable.DB.Lock' .

I cannot find any instructions which specify that you have to give the SAP user 
write access to the dsm.sys file. Is this a new requirement?
I found a post from Zoltan Forray on Backupcentral with the exact same errors, 
only for the Data Protection for Oracle client. The error seems to be gone as 
soon as you disable replication. Has anybody encountered the same issues? How 
should one solve these?
Thanks you very much for any help in advance!

Kind regards,
Eric van Loon
Air France/KLM Storage & Backup
********************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message.

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286
********************************************************

Reply via email to