NDS Replicas - Arcserve 7 & Groupwise 5.5 1

[saf23]

I have recently started at a large govenment site and the NDS design is pretty awful, too many replicas, spanned WANs, everything that can be done wrong has been.
Anyway, i'm looking to reduce the number of replicas on the hub site and cannot remember the replica requirements for Arcserve 7.0 and Groupwise 5.5

I think Arcserve 7 servers do not need replicas as it no longer relies on bindery services - correct?

Groupwise agents sitting on Netware 5.1 boxes do not need a replica? However, for NDS\Groupwise sync the MTA server needs a replica? POAs, GWIA, WebAcc, do not?

many many thanks for any advice..

 

[TheLad]

Arcserve servers do not require NDS replicas. All of our dedicated backup servers do not have replicas and they work fine as long as there is (at least) a R/W replica on the same LAN segment.

You do have to be aware that sometimes, servers running Arcserve have a tendency to loose communication with the Backup queue. This can be easily noticed by not being able to view the jobs in the Scheduler and the Log file reports the disconnection. A reboot resolves the issue but what you need to do is to assign the Arcserve queue object in NDS full SRWCEMF to the queue directory on the server. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[saf23]

Thanks for the info.

I tried it on one of their quiet servers and Arcserve immediately started complaining about Bindery Emulation not being present so I put the replica back.
Tested queues with ASUTIL.NLM (without replica) and it to complained about Bindery Emulation not being present.

However, I know that SLP, DNS & NDS is very unhealthy so that is going to have nasty effects on AS7. Will try again after I fix the other stuff.

 

[TheLad]

What you can also do is the following:

SET NDS BOOTSTRAP ADDRESS=<IP ADDRESS>

The NDS Bootstrap Address parameter is for servers
that do not hold a replica. This value specifies the IP
address of a remote server with which it can perform
tree connectivity operations. When attempting to set this parameter to an IP address, you may receive the following error message:

Error: &quot;Unable to set NDS bootstrap address&quot;

If this occurs, include the NCP/IP port number 524 in
the SET command as well. An example setting would
look like this:

SET NDS BOOTSTRAP ADDRESS=192.168.10.105:524 -----------------------------------------------------
&quot;It's true, its damn true!&quot;
-----------------------------------------------------