At this point I would advocate testing it yourself to be sure. I never
did a "q tsa nds" (I did do a "q tsa" however), and my eDir backups have
been working fine. Patrick seems to have had a different experience
though, so it could be determined by some unknown detail like tsm client
version, tsa
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
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" t
I differ a little, There is some nlm (nds.nlm?) if loaded the q tsa nds is
required to generate a password file as while. But that information is a
little dated ...
>>> [EMAIL PROTECTED] 03/01/06 10:38AM >>>
A plain "q tsa" will accomplish that. There's no need to do an
additional "q tsa nds".
A plain "q tsa" will accomplish that. There's no need to do an
additional "q tsa nds".
>>> [EMAIL PROTECTED] 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 i
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
with 1/4 of
the
> clients currently able to back up properly.
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
Of
> Troy Frank
> Sent: Tuesday, February 28, 2006 4:56 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Novell
tsa nds' for some of the clients? Bear in mind, I
used the same procedure for install and configuration, with 1/4 of the
clients currently able to back up properly.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Troy Frank
Sent: Tuesday, Februa
ion, with 1/4 of the
clients currently able to back up properly.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Troy Frank
Sent: Tuesday, February 28, 2006 4:56 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Novell Backup Errors
During instal
On Behalf Of
Troy Frank
Sent: Tuesday, February 28, 2006 4:56 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Novell Backup Errors
During install, there's a step where you're supposed to specify the
username/password that the tsm client runs under (dsmc, q tsa). That
username needs
ciated.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
Of
Richard Sims
Sent: Tuesday, February 28, 2006 6:43 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Novell Backup Errors
On Feb 27, 2006, at 5:34 PM, Bell, Charles (Chip) wrote:
> 02/27/2
6 6:43 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Novell Backup Errors
On Feb 27, 2006, at 5:34 PM, Bell, Charles (Chip) wrote:
> 02/27/2006 16:21:15 (TSA500.NLM 5.4 259)
> This program cannot allocate a directory handle.
Search on the above message text at
On Feb 27, 2006, at 5:34 PM, Bell, Charles (Chip) wrote:
02/27/2006 16:21:15 (TSA500.NLM 5.4 259)
This program cannot allocate a directory handle.
Search on the above message text at www.ibm.com, for starters.
Here is my log from one backup attempt below...Server 5.3.1.2, Client
5.3.0.0
Incremental kicks off on this note...
02/27/2006 16:21:15 (TSA500.NLM 5.4 259) This program cannot allocate a
directory handle.
02/27/2006 16:21:15 fioScanDirEntry: root dir is not accessible, object
to scan 'SYS
14 matches
Mail list logo
