Hello everyone,
TSM server - Server Version 6, Release 3, Level 5.100
TSM server is on AIX, 7.1.0.0
I am having an ongoing problem with a small set clients that Miss nightly
backups.
All our client schedules are server prompted.
They worked just fine before an incident had where the SAN was disrupted.
I go in daily and restart the dsmcad.
There are no errors in the dsmerror.log or dsmsched.log.
There are entries in the dsmsched.log that show the time scheduled for the
daily backup was picked up early in the day, but then nothing happens.
(It seems that that might be irrelevant given that they are server prompted, I
have not worked with server prompted sched's before.)
These are Windows servers.
To get these servers to backup up, instead of running a manual dsmc -i from the
client, we have a manually triggered "ONCE" backup script that creates a one
time backup schedule for that client, then runs it immediately.
All that the script does is copy the existing schedule, prefix it with
"ONCE_", then change the schedule date and time to (startd=today startt=now
perunits=onetime).
THAT works:
So communication from the TSM server to the client should not
be a problem.
And compatibility between the client versions and the TSM
Server version should not be an issue.
So, if it can work by schedule, why doesn't it?
I get these error messages in the actlog:
ANR2716E Schedule prompter was not able to contact client <prob_child_1> using
type 1 (xx.xxx.xx.xxx nnnn)
User response: Verify that the address type and address are correct for
this client. The only valid address type is 1 (for TCP/IP). Make sure
that the client scheduler is not using an invalid address, obtained at
the time the client scheduler was started, from either the client's
options file or from the command line. Verify that the client scheduler
for node node name is running and that the necessary communication links
to that scheduler are operational. Firewalls must allow traffic from the
server to the client and from the client to the server without the
session timing out. Ensure that the DNS configuration is correct.
Clients are not identical:
Node Name: <Prob_child_1>
Client Version: Version 6, release 4, level 2.0
Locked?: No
Compression: Client
Last Communication Method Used: Tcp/Ip
Maximum Mount Points Allowed: 1
Session Initiation: ClientOrServer
Deduplication: ClientOrServer
Hypervisor:
Client OS Name: WIN:Windows Server 2008 R2
Client Processor Architecture: x64
Node Name: <Prob_child_2>
Client Version: Version 7, release 1, level 6.0
Invalid Sign-on Count: 0
Locked?: No
Compression: Client
Last Communication Method Used: Tcp/Ip
Maximum Mount Points Allowed: 1
Session Initiation: ClientOrServer
Deduplication: ServerOnly
Hypervisor: VMware
Client OS Name: WIN:Windows Server 2012 R2
Client Processor Architecture: x64
George Huebschman
******************************************************************************
This email and any files transmitted with it are intended solely for
the use of the individual or agency to whom they are addressed.
If you have received this email in error please notify the Navy
Exchange Service Command e-mail administrator. This footnote
also confirms that this email message has been scanned for the
presence of computer viruses.
Thank You!
******************************************************************************
