---------------------------- Top of message ----------------------------
>>--> 04-13-06 11:58 S.SHEPPARD (SHS) Re: [ADSM-L] Netware FAS
The admin supplied me with his OPT file and it appears the DOMAIN
statement is correct:
DOMAIN ALL-LOCAL NDPS:
Don't see any errors in the DSMERROR.LOG and, interestingly, only one
file inspected/backed up; the Server Specific Info. No SYS: volume or
anything else. So I suspect some problem on the Netware setup side,
although, not knowing anything about Netware, I have no idea what it
might be. He also has some excludes of the form:
EXCLUDE.DIR NDPS1:\iobw.tst
which makes it appear there is an NDPS1 volume somewhere also. More
testing this afternoon, but right now I'm kind of at the mercy of the
Netware folks.
Thanks
Sam Sheppard
San Diego Data Processing Corp.
(858)-581-9668
ssheppard AT sddpc DOT org
---------------------------- Top of message ----------------------------
>>--> 04-13-06 06:46 ..NETMAIL (001) Re: [ADSM-L] Netware FAS
Date: Thu, 13 Apr 2006 08:40:36 -0500
From: "Troy Frank" <Troy.Frank AT UWMF.WISC DOT EDU>
Subject: Re: [ADSM-L] Netware FAS Volume
To: ADSM-L AT VM.MARIST DOT EDU
_________________________________Top_of_Message_________________________________
I'm not familiar with Network Appliance FAS devices, but I do know the
volume name seemed odd to me. The first reason is that you preceded it
with a /. Generally on netware the volumes are labeled like this,
NDPS:
He should be able to see how netware is labeling the volume by doing a
"volumes" command at the server prompt. Whatever shows up there, add a
colon to the end of it in the DOMAIN statement.
The other thing I wondered about is whether this volume name worked ok
on directly attached storage? NDPS is an actual novell product name,
and as such, I'm not sure if it's a "reserved keyword" that's not safe
to use. Could test that by creating a small dummy-volume with a
different name, and seeing if that shows up better.
>>> SHS AT SDDPC.SANNET DOT GOV 4/12/2006 5:58:29 PM >>>
We are migrating Netware file/print data from an existing SAN to a
Network Appliance FAS device. The Netware volume in question is named
/NDPS and, apparently, the Netware administrator is unable to see that
volume when he attempts to run a backup.
Is there anything special that has to be done to backup Netware
volumes
residing on a NAS device? He supposedly put the /NDPS: in his DOMAIN
statement, but I haven't yet seen his OPT file.
Anyone out there doing this with the standard Netware client or is it
possible you can only do this using NDMP?
Thanks
Sam Sheppard
San Diego Data Processing Corporation
(858)-581-9668
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.
-----------------------------------------------------------------------`
|
