Re: Client tries to backup non-existing files
2002-12-19 10:56:43
On the TSM Client, check for domain or inclexcl statements in dsm.sys,
dsm.opt or any inclexcl files. If the TSM Client has a defined Client
OptionSet on the TSM Server, also check there. The best way might be to
just do a 'dsmc show opt' and 'dsmc q inclexcl' on the client.
Also, check the client's crontabs (all of them, not just root's) for
scripts that invoke 'dsmc incr' or 'dsmc sel' commands, and check any TSM
Server schedules of type 'Command' that this client is associated with - if
any exist, investigate their 'object' and 'option' settings.
-HTH
Kent Monthei
GlaxoSmithKline
"Alexander
Verkooyen"
<alexander@SAR
A.NL> To: ADSM-L
Sent by: cc:
"ADSM: Dist Subject: Client tries to backup
non-existing files
Stor Manager"
<ADSM-L AT VM DOT MAR
IST.EDU>
19-Dec-2002
09:10
Please respond
to
ADSM-L AT VM DOT MARI
ST.EDU
Hi all,
I have a rather bizarre problem.
One of our customers tries to backup a
file system on a Solaris 5.8 system
using a 4.1.2.0 TSM client.
Our server is 4.2.3.1 on AIX 4.3.3.0
Every night the backup fails because
the client is unable to backup hundreds
of files. The log file is filled with
messages like these:
12/19/02 04:43:43 ANS1228E Sending of object '/bla/bla/file' failed
Every night the client complains about the same files.
And now for the bizarre part: According to our
customer these files have been removed from
the client some time ago. They are no longer present
on the disks of the system. And yet the client
tries to backup them (and because they are not there
any more it fails).
I found one strange thing about these ghost files:
Their names contain an *
For example: my*file.txt
Has anybody seen this before? I can't find anything in
the FAQ or the archives about a similar problem.
Regards,
Alexander
--
-----------------------------------------------
Alexander Verkooijen (alexander AT sara DOT nl)
Senior Systems Programmer
SARA High Performance Computing
|
|
|