Hi,
If you read this Steve, (or somebody else that may be the right person for answering this question), I would appreciate a quick answer.
Earlier in this forum you’ve helped people with the nlogasio.exe window and message.
At a customer site I have the following configuration:
-
IBM x235 Server with 2GB RAM, 1 Xeon Proc. A lot of disk space
-
Windows 2000 standard server
-
Domino 6.5.1IF1 Server with DK LP installed
-
Running partitioned server with 3 partitions
-
All partitions using translog (different drives and paths)
-
TSM Backup Client 5.2
-
TDP for Domino Backup agent 5.1.5
Before 6.5.1IF1 the server ran 6.5 and TDP for Domino Backup Agent 1.1.2.
The system could backup and restore as it should without any problems. Then other things forced them to upgrade to 6.5.1IF1 and the restore no longer worked.
We upgraded TDP to 5.1.5 and then the backup worked again. The restore will function as designed if we chose to overwrite existing database, but it doesn’t work if we restore to another location eg. c:\temp. Then the file can not be renamed by the TDP client (activating the file) cause the Domino server is “holding” the file.
Doing a “dbcache show” will show the database is locked on the Domino server, even though the extension is .dad
The nlogasio.exe window never closes until the Domino server is shut down.
The message in the nslogasio.exe window is as follows…
comp = 11, fnc = 48, probeid = 31, errcode = 5010, extsympt = 000000
Any ideas???
Best regards
Morten Schaumann
IT-COMPANION ApS