s
showing any CRC errors. Lastly, try an FTP from client server to TSM
server to establish if the network is performing outside of TSM.
Again, if I'm teaching you to suck hen produce, apologies.
Leigh
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Beh
at a normal time.
it is just this one backup that is extremely slow.
Cameron Ambrose wrote:
> Hello,
>
> We're currently experiencing backup failures/extreme slowness on a
> Netware 6.5 SP2 server
>
> TSM Client 5.3.0
> TSM Server 5.2.0
>
could also check if your switch is
showing any CRC errors. Lastly, try an FTP from client server to TSM
server to establish if the network is performing outside of TSM.
Again, if I'm teaching you to suck hen produce, apologies.
Leigh
-Original Message-
From: ADSM: Dist Stor Manager [
Hello,
Sorry resubmitting with a valid subject.
We're currently experiencing backup failures/extreme slowness on a
Netware 6.5 SP2 server
TSM Client 5.3.0
TSM Server 5.2.0
TSA's up to date as recommended by Client Doco
Client Logs
Hello,
We're currently experiencing backup failures/extreme slowness on a
Netware 6.5 SP2 server
TSM Client 5.3.0
TSM Server 5.2.0
TSA's up to date as recommended by Client Doco
Client Logs
10/05/2005 14:43:19 ANS1809W Session is lost;
Hi Flemming
I just tried this today on a netware 6 server with the 5.3.0 Client.
It seemed to work. It certainly created a trace dump file. I haven't tried
all the nuances yet. Here' s the entries in the dsm.opt file
tracefile sys:\tivoli\trace.out
traceflags service,-session,-s
Guys,
Is anyone out there experiencing extremely slow backup issue's with
netware 6.x servers? Some of the larger servers are taking days to complete
a backup. During this time the servers are running at 100% utilization.
Environment:
Tsm server is 5.2.0 on a solaris Platform
Ts
Thanks in advance.
I'm having some issue's trying to get a netware 6.0 server to backup.
The errors I recieve are listed below
(TSA600.NLM 6.0 259) This program cannot allocate a directory handle.
ANS1802E Incremental backup of 'SYS:' finished with 0 failure
ANS4024E Error
Hi Andy
I was under the impression(from an TSM rep) that TSM didn't pay any
attention to the archive bit, but tracked the dates/changes of files
itself.
Regards Cameron
Andy Carlson
<[EMAIL PROTECTED]To: [EMAIL PROTECTED]