Hi Eric,
I was happy too soon...
The first (large) backups ran great, but next day the problem returned.
Seems definitely disturbance on the network. Our other server (on the same
physical system but with different storage) has errors like these as well.
Looks like we need some network sniffing.
Thanks
David
n.b. others with problems like this? Could you solve it ? any "network timeout
parameter" we can set ?
Server log:
07-07-2025 18:56:39 ANR2012W Error encountered for storage pool directory:
\\medbackup.med.ad.bgu.ac.il\tsmc26 in storage pool:
CPOOL.
07-07-2025 18:56:39 ANR2012W Error encountered for storage pool directory:
\\medbackup.med.ad.bgu.ac.il\tsmc1 in storage pool:
CPOOL. (SESSION: 8067)
07-07-2025 18:56:39 ANR0530W Transaction failed for session 8067 for node
MEDFS2 (WinNT) - internal server error detected.
(SESSION: 8067)
07-07-2025 18:56:41 ANR0403I Session 8063 ended for node MEDFS2 (WinNT).
(SESSION: 8063)
07-07-2025 18:56:44 ANR0403I Session 7975 ended for node MEDFS2 (WinNT).
(SESSION: 7975)
Dsmffdc log:
[07-07-2025 18:56:24.948][ FFDC_GENERAL_SERVER_ERROR ]:
[127](psfile.c:2909)(SESSION: 8063) Error (platform specific) 59 writing to
file \\medbackup.med.ad.bgu.ac.il\tsmc15\55\000000000000555c.dcf, amtWritten 0,
size 774144 loc 2413883392.
[07-07-2025 18:56:25.519][ FFDC_GENERAL_SERVER_ERROR ]:
[121](sdcreate.c:2172)(SESSION: 8063) Exiting with bad rc 2528 for bfId
1608710764.
[07-07-2025 18:56:32.057][ FFDC_GENERAL_SERVER_ERROR ]: [423](psfile.c:2909)
Error (platform specific) 59 writing to file
\\medbackup.med.ad.bgu.ac.il\tsmc1\6a\0000000000006a44.dcf, amtWritten 0, size
1048576 loc 577073152.
[07-07-2025 18:56:40.247][ FFDC_GENERAL_SERVER_ERROR ]:
[172](psfile.c:2909)(SESSION: 8065) Error (platform specific) 59 writing to
file \\medbackup.med.ad.bgu.ac.il\tsmc26\6a\0000000000006a4a.dcf, amtWritten 0,
size 692352 loc 6642896896.
[07-07-2025 18:56:40.299][ FFDC_GENERAL_SERVER_ERROR ]:
[172](sdprodcon.c:5009)(SESSION: 8065) Flushing write control: rc=2528.
-----Original Message-----
From: David de Leeuw
Sent: Saturday, July 5, 2025 12:58 PM
To: ADSM: Dist Stor Manager <[email protected]>
Subject: RE: incr backups fail repeatedly because of link to container storage
Hi Eric,
We upgraded the server from 8.1.25 to 8.1.27.
Seems to solve the problem.
I ran a massive backup, took 10 hours. No errors.
Thanks
David
-----Original Message-----
From: ADSM: Dist Stor Manager <[email protected]> On Behalf Of Loon, Eric
van (ITOP DI) - KLM
Sent: Friday, July 4, 2025 10:27 AM
To: [email protected]
Subject: Re: [ADSM-L] incr backups fail repeatedly because of link to container
storage
Hi David,
Have a look at the dsmffdc.log in the instance directory on your server. What
error does it show at 03-07-2025 08:06:40?
Kind regards,
Eric van Loon
Air France/KLM Core Infra
-----Original Message-----
From: ADSM: Dist Stor Manager <[email protected]> On Behalf Of David L.A. De
Leeuw
Sent: Thursday, July 3, 2025 9:55 AM
To: [email protected]
Subject: incr backups fail repeatedly because of link to container storage
HI TSM's
We run Storage protect (versions 8.1) quite some time, with "container"
storage on a windows server. The pool is on a remote system with 10Gb internet
connection.
This works fine a number of years. We recently upgraded to server 8.1.25.
Now every few hours the backups fall with messages as
03-07-2025 08:06:39 ANR0950I Session 65175 for node MEDFS2 is using inline
server data deduplication or inline compression.
(SESSION: 65175)
03-07-2025 08:06:40 ANR2012W Error encountered for storage pool directory:
XXX in storage pool:
CPOOL. (SESSION: 65174)
03-07-2025 08:06:40 ANR1181E sdtxn.c(1409): Data storage transaction
0:35162311 was aborted. (SESSION: 65174)
Other backups continue at the same time.
There are no damaged or unavailable containers.
When restarting the INCR all works fine.
Seems to be a time-out or something.
Any ideas were to look for ?
David de Leeuw
Ben Gurion University of the Negev
********************************************************
For information, services and offers, please visit our web site:
https://protect.checkpoint.com/v2/r02/___http://www.klm.com___.YzJlOmJlbmd1cmlvbnVuaXZlcnNpdHlvZnRoZW5lZ2V2OmM6bzo3NGYzZmZiY2RjMzFiNWQ5ODRlNjJkZDc2NmM3NDA1Yjo3Ojk0ZjY6YTk5MWE4Y2E0NTY1ZjYyYTMzMjEzYjg1NWIyYTdjYTE4ZGQ0YTE4ZDUzM2FiNzVlZGE1MmU4NDllNGZmNTA2ZTpwOlQ6Tg.
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
********************************************************
