Unsolved
77 Posts
0
590
July 14th, 2022 06:00
Generic errors - Any indications as to what may cause them ?
Hi,
I've been working with NetWorker for a long time, but i get sometime some errors that look like this, if anyone has an idea what might cause them, i'll like to have the information. Note, that those errors may happen one day, but may not appear for many months afterward.
ERROR #1
Error opening tape session for MSSQL:/
38008:nsrsqlrc: Failed to read on "EMC#5894c16f-18e1-8730-ba7c-af67af87d31a"
ERROR #2
The restore session could not start: Unable to execute 'U?': Cannot allocate memory.
ERROR #3
155552:nsrsqlrc: The software found a time difference of 10 minutes between the backup creation time and the savetime. This might be caused by the clock skew between NetWorker client and server, or a busy server.
Any help appreciated, thank you,
Chris
bingo.1
2.4K Posts
0
July 18th, 2022 13:00
I can't help on the first issue.
'Cannot allocate memory' - if not a software problem the system obviously needs more RAM. Ple use the appropriate tools to check which software uses most and take appropriate action.
'time difference' between client and server is too much. This in fact is something NW monitors. So take care that both systems are in sync or pretty close.
CarC8
77 Posts
0
July 20th, 2022 05:00
Hello,
For the memory, i've looked at the system usage, but it doesn't seem to be running out, it is actually configured on 64Gb. This error has happened only 1 day, so i'm waiting for it to reappear to analyse more.
For the time difference problem, that too, we had only one time. I've checked allready if i have a time difference between NetWorker server and the client, and as far as i can tell, both system have very close time if not the same. I don't think it is related to the time of the system, but maybe NetWorker server was too busy at the time this error was recorded, what do you think ?
Thank you for your recommandations.
Chris
bingo.1
2.4K Posts
0
July 20th, 2022 06:00
In general, it is pretty hard to investigate sporadic errors. Only when they occur it is a good time to check what might be the troublemaker.
I have no doubt that you have enough RAM available. The question just is: which process - at this time - is using so much memory that not enough can be allocated for other processes. Maybe a subprocess is just consuming so much at that moment, that new jobs cannot be started. This smells like a software issue which you need to verify next time.
The time difference issue is also hard to check. If you have setups your environment properly, it should not occur. NW will definitively compare the client and the server time und it will report a problem. Of course, it does not know why it occurs. If both errors happen on the same machines and at the same time, it could well be that the 'low memory' problem might cause a malfunction which then results in a temporary time difference. But again - only a thoruogh look at the systems could uncover the mystery.