ADSM-L

Re: Novell Backup Errors

2006-03-02 08:25:20
Subject: Re: Novell Backup Errors
From: Timothy Hughes <Timothy.Hughes AT OIT.STATE.NJ DOT US>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 2 Mar 2006 08:23:08 -0500
Just to add,

If  "nds' is not being backed up is there a need to do a "q tsa nds"?

Patrick Boutilier wrote:

> Troy Frank wrote:
> > A plain "q tsa" will accomplish that.  There's no need to do an
> > additional "q tsa nds".
> >
>
> When you use "q tsa nds" you are prompted to login to tree, not the server.
>
> I just proved on my test server that if you remove tsm.pwd, "dsmc q
> sess" to store TSM password, "dsmc q tsa" to store TSA password, and
> then do "dsmc i nds:" to backup the actual NDS you will get prompted to
> login to the tree.
>
> http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/com.ibm.itsmc.doc/ans30000312.htm
>
> >
> >>>> boutilpj AT EDNET.NS DOT CA 3/1/2006 9:25 AM >>>
> > Troy Frank wrote:
> >> My confusion was the use of "q tsa nds" during setup of the client,
> >> since it's not necessary to make nds backups work. All you need for
> >> that is to add NDS: to your dsm.opt DOMAIN statement.
> >
> >
> > But you still have to provide a NDS user and password to backup the
> > NDS
> > with at aome point. Using "q tsa nds" lets you specify that
> > userid/password combo from the prompt instead of having a scheduled
> > backup sitting there waiting for that information. :-)
> >
> >
> >
> >
> > Also, oddly
> >> enough you've gotta be careful to try older tsa versions also. I
> > always
> >> try the newer first, but for the last several versions things have a
> >> tendency to break, then be fixed, then break again in the next
> > version.
> >>
> >> One thing I forgot to ask previously was what netware version/patch
> >> revision he's at. I'm assuming he's at some rev of Netware5 given
> > the
> >> tsa he's using, which also leads to questions about what kind of
> > volume
> >> vol1: is (tfs/nss). He may want to run a vrepair, or nss poolverify,
> >> just to make sure all's well with the filesystem. Might also be a
> > good
> >> idea to run a full repair of the nds partition that this server is
> > in.
> >>
> >> Troy Frank
> >> Network Services
> >> University of Wisconsin Medical Foundation
> >> 608.829.5384
> >>
> >>>>> boutilpj AT EDNET.NS DOT CA 2/28/2006 5:43 PM >>>
> > <snip>
> >
> >
> > Confidentiality Notice follows:
> >
> > The information in this message (and the documents attached to it, if any)
> > is confidential and may be legally privileged. It is intended solely for
> > the addressee. Access to this message by anyone else is unauthorized. If
> > you are not the intended recipient, any disclosure, copying, distribution
> > or any action taken, or omitted to be taken in reliance on it is
> > prohibited and may be unlawful. If you have received this message in
> > error, please delete all electronic copies of this message (and the
> > documents attached to it, if any), destroy any hard copies you may have
> > created and notify me immediately by replying to this email. Thank you.

<Prev in Thread] Current Thread [Next in Thread>