ECTED]
Subject: Re: Archive errors
Curt,
I thought it odd to see these messages too. I can see these messages further
up the log and I have also seen the error messages on another server with
Journaling. It just so happens this computer does have Journaling on it, but
I am logged on via Timbuktu r
Been trying to get this archive going and for whatever reason I don't
understand the error from the error log. From what I recall this used to
work fine when it was on a 4.2 level on the client.
Client is NT4 SP6
TSM version 5.1.5.2
DSM.OPT is as follows: Some of the names have been changes to pr
AIC
E-Mail: [EMAIL PROTECTED]
Phone: (858) 826-4062
Pager: (877) 905-7154
> -Original Message-
> From: Magura, Curtis [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 04, 2003 4:15 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Archive errors
>
>
> Geoff,
]]
Sent: Monday, February 03, 2003 10:58 AM
To: [EMAIL PROTECTED]
Subject: Archive errors
Been trying to get this archive going and for whatever reason I don't
understand the error from the error log. From what I recall this used to
work fine when it was on a 4.2 level on the client.
Client i
As has been noted there are some new nlm's available from Novell for 5.0 and 5.1
servers. They are packaged as tsa5up3. Check Novell's support site.
Tom Bebee wrote:
> After upgrading our ADSM 3.1 server to TSM 3.7.4, we had problems with archiving
>volumes from a Novell client running extrem
After upgrading our ADSM 3.1 server to TSM 3.7.4, we had problems with archiving
volumes from a Novell client running extremely slow. We ran a CLEAN ARCHDIR
DELETEDIRS command and a couple of archives were run successfully with the elapsed
time being close to that of the ADSM 3.1 server.
Howe
