Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

NDS backup Arcserve 6.6 For Netware

0 views
Skip to first unread message

az...@uneca.org

unread,
Dec 24, 2003, 3:59:55 AM12/24/03
to

envt : Nw51 sp4
Arcsercve 6.6It for Netware sp4
Arcsevre manager: Installed on a win 98 machine

We are not able select the NDS tree as part of a backup job fom the
manager on the win98 machine.
On the source we see Novell directory services but expanding it doesnot
show the tree.
Manager installed on another win98 machine -same problem.
Can we modify the submitted job on the server console to add the NDS or
any other soln?

Tks


Marcel Cox

unread,
Dec 26, 2003, 11:21:46 AM12/26/03
to
What Arcserve version do you have? Single server, workgroup or
Enterprise?

--
Marcel Cox (using XanaNews 1.15.8.4)

az...@uneca.org

unread,
Dec 27, 2003, 1:37:42 AM12/27/03
to
> What Arcserve version do you have? Single server, workgroup or
> Enterprise?
>
> -- Arcserve IT for Netware 6.6 Enterprise edition.

Marcel Cox

unread,
Dec 27, 2003, 5:32:47 AM12/27/03
to
Well, in that case, there should not be an Arcserve restriction
preventing you from doing the backup.
What client are you using on your Win98 machine? Are you using an IPX
or IP connection?

--

az...@uneca.org

unread,
Dec 29, 2003, 2:22:07 AM12/29/03
to
I am using IP.
Does the protocol matter ?

Marcel Cox

unread,
Dec 29, 2003, 4:21:14 AM12/29/03
to
az...@uneca.org wrote:

> I am using IP.
> Does the protocol matter ?

The protocol used matters for the Device Manager which only works with
IPX. It might not matter for managing backup jobs.

--
Marcel (using XanaNews 1.15.8.5)
I can resist everything but temptation

GT

unread,
Jan 13, 2004, 6:19:05 PM1/13/04
to

<az...@uneca.org> wrote in message
news:fAcGb.476$VM1...@prv-forum2.provo.novell.com...
Make sure you have a bindery context assigned on the server the manager is
connecting to. We had similar problems expanding the NDS on some servers
from within the manager, and assigning a bindery context on each server
where the ArcServe manager was connecting to solved our issues.

Good Luck...

GT


0 new messages