Unsolved
This post is more than 5 years old
1 Rookie
•
37 Posts
0
3544
July 30th, 2017 17:00
Unable to get a new shared memory segment
Hello Experts,
Backup of one server is failing with below error. It has 8 tb drive. However some drives got completed. Please help.
One Drive
86798:save: Unable to get a new shared memory segment: xdr flush for mm session failed3996:save:
lost connection to server
42665:save: failed to reserve 1136 bytes for immediate mark
5203:save: save failed on \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy300\Report.pdf
74209:save: Quit signal received.
99123:save: Handling an abort while processing Windows backup.
Second Drive.
100049:save: Unable to determine jobd version, assuming version 7.3: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
76677:save: RPC receive operation failed; peer = ::1:[8352], errno = An existing connection was forcibly closed by the remote host.
bingo.1
2.4K Posts
0
July 31st, 2017 01:00
On the first view it looks seems to be a memory related problem.
However, other parameters could also apply as obviously the connection has dropped (network, timeout).
Other imortant questions:
- Is this a new configuration? - Has this already worked at all?
- Does the problem always occur aith the same file?
- What is the OS of the NW client?
- Is this true that we this client uses NW 7.3?
Hargyan
1 Rookie
•
37 Posts
0
August 1st, 2017 12:00
Hello Bingo,
1) its not new configuration
2) Yes this happes only for specific files and drives
3) Its 8.2.3
4) No client is not using 7.3
Please help.
bingo.1
2.4K Posts
0
August 1st, 2017 13:00
If so, the first thing I would do is checking the file system and/or boot the NW client.
Hargyan
1 Rookie
•
37 Posts
0
August 4th, 2017 15:00
Hi Bingo,
I didnt get this please explain "checking the file system and/or boot the NW client.
Now below is the error. There are 4 such kind of errors for all 4 failed drives.
3996:save: lost connection to server
86798:save: Unable to get a new shared memory segment: xdr flush for mm session failed3996:save: lost connection to server
42665:save: failed to reserve 1136 bytes for immediate mark
5203:save: save failed on \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy295\Document\Database\2016.08.08.pdf
74209:save: Quit signal received.
99123:save: Handling an abort while processing Windows backup.
bingo.1
2.4K Posts
0
August 4th, 2017 22:00
"checking the file system and/or boot the NW client" = "run a file system check ..."
But you should also consider the starting message : "3996:save: lost connection to server"
If the client can not communicate with the server any longer, a failing process is no surprise.
Just that you run only backups this time. And if you have n drives, you most likely will receiver error for each of them.