Does anyone know if you can update a clients version information on the TSM
server? Example - The TSM server says that a node is version 4.2.0.0 when in
reality the node is at 3.7. Now when the client tries to contact the server
for anything (schedule, backup, restore) it fails with the error that
We recently upgraded our TSM Server to 4.2.0.1 (AIX)and now we have a few
clients that will not connect to the server and spit out the following
error:
ANS1357S Session rejected: Downlevel client code version
I am getting these errors on 3.1, 3.7 and 4.1 clients, all Windows (NT and
2000). It wo
ember the specifics ... just know they
>were inclexcl and domain related.
>
>Ric Cross
>
>Lead Integration Engineer
>
>WorldCrest
>1600 RiverEdge Parkway, Suite 100
>Atlanta, Georgia 30328
>
>
>-Original Message-
>From: Dwight R. Wood [mailto:[EMAIL PROTECTED]]
&
Has anyone experienced this before:
I have many Solaris 2.6 and 2.7 machines getting backed up to a TSM server
on Solaris (4.1.2). Each night the backups run with a 'completed' report.
But I have run into a HUGE problem. When the backup runs automatically at
night, it misses almost the entire fil
Hi Gill, I am not sure what OS you are running TSM on but I am running mine
on Solaris and I have a cron job set up to run every morning at 6:00. The
script in the cron job is as follows:
echo "** TSM Backup Report **" > /usr/local/adsm/log
echo For 'date' >> /usr/local/adsm/log
echo "The
Hi Doug, yes - the scratch tapes need to be checked in to the library in
order for the backup and other processes to use them. If there are no
scratch tapes then you will receive the same error. ADSM/TSM does not issue
a request for scratch tapes. Also, if you assign those scratch tapes to a
stora
