Mark Stapleton <[EMAIL PROTECTED]> wrote:
>> For example: my*file.txt
>
>Well, there's part of the problem there. '*' is an invalid character for
>a filename in any UNIX system I've ever heard of. Such filenames appear
>from time to time when using misconfigured moves and copies.
'*' is a perfect
ything.
>
> Richard Sims <[EMAIL PROTECTED]> on 12/19/2002 06:33:30 PM
>
> Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>
> To: [EMAIL PROTECTED]
> cc: (bcc: John Naylor/HAV/SSE)
> Subject: Re: Client tries to backup non-existing fi
Mark Stapleton wrote:
> Well, there's part of the problem there. '*' is an invalid character for
> a filename in any UNIX system I've ever heard of. Such filenames appear
> from time to time when using misconfigured moves and copies.
>
> Get the box's owner to rename the files so that the '*' does
Richard,
Yes, you might be right. I've started a SQL query
to find out if the server still thinks the
files are active.
Best regards,
Alexander
Richard Sims wrote:
> Hmmm... I wonder if the Sending error might be the client having seen
> the name in the active-files list it got from the server
[EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject: Re: Client tries to backup non-existing files
>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 pa
>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...
Hmmm... I wonder if the Sending error might b
On Thu, 2002-12-19 at 08:10, Alexander Verkooyen wrote:
> 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
19, 2002 9:58 AM
To: [EMAIL PROTECTED]
Subject: Re: Client tries to backup non-existing files
John Naylor wrote:
>
> I have exactly the same issue with a couple of my clients (netware).
> The files no longer exist on the client, but I see many ANS1228E failure
> messages.
> How
levels , with the
> clients due for replacement.
>
> Imre Csatlos <[EMAIL PROTECTED]> on 12/19/2002 02:59:04 PM
>
> Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>
> To: [EMAIL PROTECTED]
> cc:(bcc: John Naylor/HAV/SSE)
> Subject: Re
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 cli
Hi,
Imre Csatlos wrote:
> Is yout client backing up the whole file system or just specific files?
> Like 'dsmc inc "/bla/bla/my*files.txt`
They are making a backup of the whole file system like 'dsmc i /bla'
> Also you can try umount and fsck for those file system, but I suspect the
> problem i
ond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject: Re: Client tries to backup non-existing files
Hi,
Is yout client backing up the whole file system or just specific files?
Like 'dsmc inc "/bla/bla/my*fil
Hi,
Is yout client backing up the whole file system or just specific files?
Like 'dsmc inc "/bla/bla/my*files.txt`
Also you can try umount and fsck for those file system, but I suspect the
problem is somewhere in the
backup file specifications.
If all the other files are backed up apart from tho
13 matches
Mail list logo
