Hi,
Good day to all forum members.
Need help to solve schedule status Failed with my Lotus Domino, TDP for Domino.
The log is not accused of any database failure however the schedule status is Failed
The error is: ANR0482W.
I found this forum the following explanation on this ANR:
ANR0482W Session <SessionNumber> for <NodeNode> name (<ClientPlatform>)
terminated - idle for more than N minutes.
If the messages reflects 15 minutes, your server still has the product
default IDLETimeout of 15 minutes, which is much too small. Boost it to
60: you need a large value to accommodate clients rummaging around in a
large, relatively inactive file system looking for changed files to back
up. If you have a good-sized value already, investigate why your client
is idle so long...which could occur if you need a password on the
command line and neglected to specify one, which causes the *SM client
to prompt and wait indefinitely.
This message can be expected with dsmadmc sessions, which are commonly
idle for long period where an administrator starts such a session but
only looks in a couple of times a day.
Note that the type of session which times out can be expected to be a
Producer Session - the type responsible for querying the server,
establishing communication with the server, and reporting results to the
server. Producer Sessions are inherently idle as they wait for their
companion Consumer sessions to complete their work. Where a Producer
Session times out and goes away, a new one will appear (ANR0406I,
ANS1810E) as TSM starts it when the Consumer session reaches a point
where it needs some session management work conducted with the TSM
server. The client scheduler log will not show any evidence of the
producer session timeout: its consumer session continues processing the
client files, uninterrupted. Larger RESOURceutilization values make for
more Producer Sessions and thus more exposure to idle timeouts.
-------------
Following excerpts from the activity log
Server Name Date/time Message Number Message
MYTSMSERVER 9/12/2013 20:00 ANR2561I Schedule prompter contacting MY_DOMINO_DOM_DIA (session 1315850) to start a scheduled operation. (SESSION: 32)
MYTSMSERVER 9/12/2013 20:00 ANR0403I Session 1315850 ended for node MY_DOMINO_DOM_DIA (). (SESSION: 32)
MYTSMSERVER 9/12/2013 20:00 ANR0406I Session 1315864 started for node MY_DOMINO_DOM_DIA (WinNT) (Tcp/Ip domino.mycompany.net(51624)). (SESSION: 1315864)
MYTSMSERVER 9/12/2013 20:00 ANR0403I Session 1315864 ended for node MY_DOMINO_DOM_DIA (WinNT). (SESSION: 1315864)
MYTSMSERVER 9/12/2013 20:00 ANR0406I Session 1315866 started for node MY_DOMINO_DOM_DIA (WinNT) (Tcp/Ip domino.mycompany.net(51626)). (SESSION: 1315866)
MYTSMSERVER 9/12/2013 20:04 ANR0406I Session 1315912 started for node MY_DOMINO_DOM_DIA (TDP Domino WIN64) (Tcp/Ip domino.mycompany.net(51661)). (SESSION: 1315912)
MYTSMSERVER 9/12/2013 20:04 ANE4991I (ANE4985I Session: 1315912, ANE4986I Node: MY_DOMINO_DOM_DIA) TDP Domino WIN64 ACD5208 Data Protection for Domino: Starting selective database backup from server MY_DOMINO. (SESSION: 1315912)
MYTSMSERVER 9/12/2013 20:04 ANE4991I (ANE4985I Session: 1315912, ANE4986I Node: MY_DOMINO_DOM_DIA) TDP Domino WIN64 ACD5200 Data Protection for Domino: Starting backup of database activity.nsf from server MY_DOMINO. (SESSION: 1315912)
MYTSMSERVER 9/12/2013 20:04 ANE4991I (ANE4985I Session: 1315912, ANE4986I Node: MY_DOMINO_DOM_DIA) TDP Domino WIN64 ACD5201 Data Protection for Domino: Backup of database activity.nsf from server MY_DOMINO completed successfully. (SESSION: 1315912)
MYTSMSERVER 9/12/2013 20:04 ANE4991I (ANE4985I Session: 1315912, ANE4986I Node: MY_DOMINO_DOM_DIA) TDP Domino WIN64 ACD5200 Data Protection for Domino: Starting backup of database activity.ntf from server MY_DOMINO. (SESSION: 1315912)
MYTSMSERVER 10/12/2013 00:00 ANR0482W Session 1315866 for node MY_DOMINO_DOM_DIA (WinNT) terminated - idle for more than 240 minutes. (SESSION: 1315866)
MYTSMSERVER 10/12/2013 02:37 ANE4991I (ANE4985I Session: 1315912, ANE4986I Node: MY_DOMINO_DOM_DIA) TDP Domino WIN64 ACD5200 Data Protection for Domino: Starting backup of database tmpddm.nsf from server MY_DOMINO. (SESSION: 1315912)
MYTSMSERVER 10/12/2013 02:37 ANE4991I (ANE4985I Session: 1315912, ANE4986I Node: MY_DOMINO_DOM_DIA) TDP Domino WIN64 ACD5201 Data Protection for Domino: Backup of database tmpddm.nsf from server MY_DOMINO completed successfully. (SESSION: 1315912)
MYTSMSERVER 10/12/2013 02:37 ANE4991I (ANE4985I Session: 1315912, ANE4986I Node: MY_DOMINO_DOM_DIA) TDP Domino WIN64 ACD5461 Data Protection for Domino: Selective database backup from server MY_DOMINO complete. Total Domino databases backed up: 4906 Total Domino databases deduplicated: 0 Total bytes inspected: 468,080,573,607 Total bytes transferred: 424394878772 Total LanFree bytes transferred: 0 Total bytes before deduplication: 0 Total bytes after deduplication: 0 Data compressed by: 10% Deduplication reduction: 0,00% Total data reduction ratio: 9,34% Elapsed processing time: 23590,23 Secs Throughput rate: 17568,63 Kb/Sec (SESSION: 1315912)
MYTSMSERVER 10/12/2013 02:37 ANR0403I Session 1315912 ended for node MY_DOMINO_DOM_DIA (TDP Domino WIN64). (SESSION: 1315912)
MYTSMSERVER 10/12/2013 02:37 ANR0406I Session 1321215 started for node MY_DOMINO_DOM_DIA (WinNT) (Tcp/Ip domino.mycompany.net(53174)). (SESSION: 1321215)
MYTSMSERVER 10/12/2013 02:37 ANR2579E Schedule MY_DOMINO_DOM_DIA in domain PD_DOM_DIA for node MY_DOMINO_DOM_DIA failed (return code 402). (SESSION: 1321215)
MYTSMSERVER 10/12/2013 02:37 ANR0403I Session 1321215 ended for node MY_DOMINO_DOM_DIA (WinNT). (SESSION: 1321215)
MYTSMSERVER 10/12/2013 02:37 ANR0406I Session 1321216 started for node MY_DOMINO_DOM_DIA (WinNT) (Tcp/Ip domino.mycompany.net(53175)). (SESSION: 1321216)
MYTSMSERVER 10/12/2013 02:37 ANR0403I Session 1321216 ended for node MY_DOMINO_DOM_DIA (WinNT). (SESSION: 1321216)
--------------------------------
Output query opt
Server Option Option Setting Server Option Option Setting
----------------- -------------------- ----------------- --------------
CommTimeOut 15,000 IdleTimeOut 240
AdminCommTimeOut 60 AdminIdleTimeOut 15
DateFormat 1 (mm/dd/yyyy) TimeFormat 1 (hh:mm:ss)
-------------
Can anyone assist me in resução this problem?
I'm several days without backup this environment.
Already.
Thank you for your attention.
Good day to all forum members.
Need help to solve schedule status Failed with my Lotus Domino, TDP for Domino.
The log is not accused of any database failure however the schedule status is Failed
The error is: ANR0482W.
I found this forum the following explanation on this ANR:
ANR0482W Session <SessionNumber> for <NodeNode> name (<ClientPlatform>)
terminated - idle for more than N minutes.
If the messages reflects 15 minutes, your server still has the product
default IDLETimeout of 15 minutes, which is much too small. Boost it to
60: you need a large value to accommodate clients rummaging around in a
large, relatively inactive file system looking for changed files to back
up. If you have a good-sized value already, investigate why your client
is idle so long...which could occur if you need a password on the
command line and neglected to specify one, which causes the *SM client
to prompt and wait indefinitely.
This message can be expected with dsmadmc sessions, which are commonly
idle for long period where an administrator starts such a session but
only looks in a couple of times a day.
Note that the type of session which times out can be expected to be a
Producer Session - the type responsible for querying the server,
establishing communication with the server, and reporting results to the
server. Producer Sessions are inherently idle as they wait for their
companion Consumer sessions to complete their work. Where a Producer
Session times out and goes away, a new one will appear (ANR0406I,
ANS1810E) as TSM starts it when the Consumer session reaches a point
where it needs some session management work conducted with the TSM
server. The client scheduler log will not show any evidence of the
producer session timeout: its consumer session continues processing the
client files, uninterrupted. Larger RESOURceutilization values make for
more Producer Sessions and thus more exposure to idle timeouts.
-------------
Following excerpts from the activity log
Server Name Date/time Message Number Message
MYTSMSERVER 9/12/2013 20:00 ANR2561I Schedule prompter contacting MY_DOMINO_DOM_DIA (session 1315850) to start a scheduled operation. (SESSION: 32)
MYTSMSERVER 9/12/2013 20:00 ANR0403I Session 1315850 ended for node MY_DOMINO_DOM_DIA (). (SESSION: 32)
MYTSMSERVER 9/12/2013 20:00 ANR0406I Session 1315864 started for node MY_DOMINO_DOM_DIA (WinNT) (Tcp/Ip domino.mycompany.net(51624)). (SESSION: 1315864)
MYTSMSERVER 9/12/2013 20:00 ANR0403I Session 1315864 ended for node MY_DOMINO_DOM_DIA (WinNT). (SESSION: 1315864)
MYTSMSERVER 9/12/2013 20:00 ANR0406I Session 1315866 started for node MY_DOMINO_DOM_DIA (WinNT) (Tcp/Ip domino.mycompany.net(51626)). (SESSION: 1315866)
MYTSMSERVER 9/12/2013 20:04 ANR0406I Session 1315912 started for node MY_DOMINO_DOM_DIA (TDP Domino WIN64) (Tcp/Ip domino.mycompany.net(51661)). (SESSION: 1315912)
MYTSMSERVER 9/12/2013 20:04 ANE4991I (ANE4985I Session: 1315912, ANE4986I Node: MY_DOMINO_DOM_DIA) TDP Domino WIN64 ACD5208 Data Protection for Domino: Starting selective database backup from server MY_DOMINO. (SESSION: 1315912)
MYTSMSERVER 9/12/2013 20:04 ANE4991I (ANE4985I Session: 1315912, ANE4986I Node: MY_DOMINO_DOM_DIA) TDP Domino WIN64 ACD5200 Data Protection for Domino: Starting backup of database activity.nsf from server MY_DOMINO. (SESSION: 1315912)
MYTSMSERVER 9/12/2013 20:04 ANE4991I (ANE4985I Session: 1315912, ANE4986I Node: MY_DOMINO_DOM_DIA) TDP Domino WIN64 ACD5201 Data Protection for Domino: Backup of database activity.nsf from server MY_DOMINO completed successfully. (SESSION: 1315912)
MYTSMSERVER 9/12/2013 20:04 ANE4991I (ANE4985I Session: 1315912, ANE4986I Node: MY_DOMINO_DOM_DIA) TDP Domino WIN64 ACD5200 Data Protection for Domino: Starting backup of database activity.ntf from server MY_DOMINO. (SESSION: 1315912)
MYTSMSERVER 10/12/2013 00:00 ANR0482W Session 1315866 for node MY_DOMINO_DOM_DIA (WinNT) terminated - idle for more than 240 minutes. (SESSION: 1315866)
MYTSMSERVER 10/12/2013 02:37 ANE4991I (ANE4985I Session: 1315912, ANE4986I Node: MY_DOMINO_DOM_DIA) TDP Domino WIN64 ACD5200 Data Protection for Domino: Starting backup of database tmpddm.nsf from server MY_DOMINO. (SESSION: 1315912)
MYTSMSERVER 10/12/2013 02:37 ANE4991I (ANE4985I Session: 1315912, ANE4986I Node: MY_DOMINO_DOM_DIA) TDP Domino WIN64 ACD5201 Data Protection for Domino: Backup of database tmpddm.nsf from server MY_DOMINO completed successfully. (SESSION: 1315912)
MYTSMSERVER 10/12/2013 02:37 ANE4991I (ANE4985I Session: 1315912, ANE4986I Node: MY_DOMINO_DOM_DIA) TDP Domino WIN64 ACD5461 Data Protection for Domino: Selective database backup from server MY_DOMINO complete. Total Domino databases backed up: 4906 Total Domino databases deduplicated: 0 Total bytes inspected: 468,080,573,607 Total bytes transferred: 424394878772 Total LanFree bytes transferred: 0 Total bytes before deduplication: 0 Total bytes after deduplication: 0 Data compressed by: 10% Deduplication reduction: 0,00% Total data reduction ratio: 9,34% Elapsed processing time: 23590,23 Secs Throughput rate: 17568,63 Kb/Sec (SESSION: 1315912)
MYTSMSERVER 10/12/2013 02:37 ANR0403I Session 1315912 ended for node MY_DOMINO_DOM_DIA (TDP Domino WIN64). (SESSION: 1315912)
MYTSMSERVER 10/12/2013 02:37 ANR0406I Session 1321215 started for node MY_DOMINO_DOM_DIA (WinNT) (Tcp/Ip domino.mycompany.net(53174)). (SESSION: 1321215)
MYTSMSERVER 10/12/2013 02:37 ANR2579E Schedule MY_DOMINO_DOM_DIA in domain PD_DOM_DIA for node MY_DOMINO_DOM_DIA failed (return code 402). (SESSION: 1321215)
MYTSMSERVER 10/12/2013 02:37 ANR0403I Session 1321215 ended for node MY_DOMINO_DOM_DIA (WinNT). (SESSION: 1321215)
MYTSMSERVER 10/12/2013 02:37 ANR0406I Session 1321216 started for node MY_DOMINO_DOM_DIA (WinNT) (Tcp/Ip domino.mycompany.net(53175)). (SESSION: 1321216)
MYTSMSERVER 10/12/2013 02:37 ANR0403I Session 1321216 ended for node MY_DOMINO_DOM_DIA (WinNT). (SESSION: 1321216)
--------------------------------
Output query opt
Server Option Option Setting Server Option Option Setting
----------------- -------------------- ----------------- --------------
CommTimeOut 15,000 IdleTimeOut 240
AdminCommTimeOut 60 AdminIdleTimeOut 15
DateFormat 1 (mm/dd/yyyy) TimeFormat 1 (hh:mm:ss)
-------------
Can anyone assist me in resução this problem?
I'm several days without backup this environment.
Already.
Thank you for your attention.
