The following are some examples of how to modify the PortsConfig.cfg file.
sqlagenttcpservice 8000 machine_name
or
fsbackupservice 7000 machine_name
or
exchangeagenttcpserverlevel 6000 machine_name
On machine B - client agent, add following lines to the PortsConfig.cfg file:
fsbackupservice 7000 MachineB
fsbackupserviceudp 7000 MachineB
fsbackupservice 7000 MachineB
fsbackupserviceudp 7000 MachineB
To allow the client agent from machine A to communicate with the Arcserve Backup machine D, add the following lines to the PortsConfig.cfg file on machine A:
fsbackupservice 8000 MachineA
fsbackupserviceudp 8000 MachineA
You must restart the Universal Agent on machine A.
Note: You can apply this theory to the Arcserve Backup Agent for Microsoft SQL Server (sqlagenttcpservice) and the Arcserve Backup Agent for Microsoft Exchange Premium Add-on (exchangeagenttcpserverlevel) for TCP services (fsbackupservice, sqlagenttcpservice, exchangeagenttcpserverlevel).
MSRPC listens over “ncacn_ip_tcp” and “ncacn_np” protocols. The “ncacn_ip_tcp” uses system assigned ports by default, rather than hard-coded ports. The hostname and IP address are not required for the RPC Services.
For example, a change for an MSRPC service could be:
dbagentsrpcserver 9000
Arcserve Backup Agent RPC Server will try to use port 9000.
dbagentsrpcserver 9000;9001
Arcserve Backup Agent RPC Server will try to communicate using port 9000; if it does not succeed it will try to use port 9001. If it does not succeed Arcserve Backup will write a message in the Windows Application Activity Log.
dbagentsrpcserver 9000-9500
Arcserve Backup Agent RPC Server tries to communicate using port 9000. If it does not succeed Arcserve Backup will try to communicate using port 9001, and continue to attempt to communicate up to port 9500.
If it cannot use any port in the range, will write a message in the Windows Application Activity Log.
Copyright © 2015 Arcserve. All rights reserved. |
|