Novell Client 3.1.0.8

Remeta, Mark

unread,

Mar 16, 2000, 3:00:00 AM3/16/00

to

Does anyone know if there is a problem with the latest Novell client and
backing up NDS. I installed it about 20 days ago and I just noticed today
that the DIR for one of my Novell servers hasn't been backed up for 20 days.
I checked the DSM.OPT and it lists all-local and DIR for the domain, just as
it was before I upgraded. When I check the DSMSCHED.LOG I do not see any
errors about not being able to backup the directory, it just doesn't list
it. If I check the DSMERROR.LOG I have been getting these for about the last
20 days...
03/15/2000 00:19:09 (TSA410.NLM 4.15 266) This data set is in use and cannot
be accessed at this time.
03/15/2000 00:19:10 (TSA410.NLM 4.15 266) This data set is in use and cannot
be accessed at this time.
03/15/2000 00:19:10 (TSA410.NLM 4.15 266) This data set is in use and cannot
be accessed at this time.
03/15/2000 00:19:10 (TSA410.NLM 4.15 266) This data set is in use and cannot
be accessed at this time.
03/15/2000 00:19:10 (TSA410.NLM 4.15 266) This data set is in use and cannot
be accessed at this time.
If I manually backup the directory with a I DIR: it works fine. It seems it
is only with the scheduler that the problem occurs. Anyone else see this?

Here is the client version info:
ADSTAR Distributed Storage Manager
Command Line Backup Client Interface - Version 3, Release 1, Level 0.8
(C) Copyright IBM Corporation, 1990, 1999, All Rights Reserved.

Mark Remeta
Seligman Data Corporation
100 Park Avenue
New York, NY 10017

Remeta, Mark

unread,

Mar 16, 2000, 3:00:00 AM3/16/00

to

Well I changed the domain statement in the dsm.opt to all-local NDS. I will
see what happens tonight. The previous version was 3.1.0.7f I think.

Thanks,
Mark

-----Original Message-----
From: Jim Kirkman [mailto:j...@EMAIL.AIS.UNC.EDU]
Sent: Thursday, March 16, 2000 2:01 PM
To: ADS...@VM.MARIST.EDU
Subject: Re: Novell Client 3.1.0.8

What client did you upgrade from? At some point the syntax changed from
Directory to NDS. You may just be looking for the wrong thing.

"Remeta, Mark" wrote:

--
Jim Kirkman
AIS UNC-Chapel Hill
966-5884

Remeta, Mark

unread,

Mar 17, 2000, 3:00:00 AM3/17/00

to

Okay, I tried DIR and NDS. Scheduled commands do not seem to include the
directory.
I am going to try to create a scheduled backup command that only includes
the directory and see if it works.

Mark

Remeta, Mark

unread,

Mar 17, 2000, 3:00:00 AM3/17/00

to

If I create an immediate client action that has as an object DIR: it works.
If I create an immediate client action or a scheduled command that does not
have any objects defined, it is suppose to take the objects from the dsm.opt
file which I have tried coding as all-local DIR: and all-local NDS:. Neither
of these work. It just skips the directory all together. Am I the only one
seeing this? The client is running NetWare 4.11 and the ADSM client is
3.1.0.8.

Kevin Corning-Hyman

unread,

Mar 17, 2000, 3:00:00 AM3/17/00

to

Mark,
I just did some testing on one of our Netware v5 servers. I put "DOMAIN
all-local nds" in the dsm.opt file, ran DSMC INC and NDS did not backup.
Same thing for "DOMAIN all-local dir" When I put "nds" or "dir" before
"all-local" NDS backed up. So, in the dsm.opt file, I ended up with "DOMAIN
nds all-local" I also experimented with using a separate line, eg. "DOMAIN
nds" or "DOMAIN dir" along with a line that reads "DOMAIN all-local" These
also worked. Client is v3.1.0.8.

----- Original Message -----
From: "Remeta, Mark" <MRe...@SELIGMANDATA.COM>
To: <ADS...@VM.MARIST.EDU>
Sent: Friday, March 17, 2000 12:40 PM
Subject: Re: Novell Client 3.1.0.8

Remeta, Mark

unread,

Mar 20, 2000, 3:00:00 AM3/20/00

to

Thank you Kevin. That did the trick. I move DIR before all-local in the
domain statement and now it is backing up the NDS again.

Many thanks,
Mark