esherril
Joined: 31 Aug 2007
Posts: 8
|
 Port 5555/TCP for starters....
First off please Read The Fine Manuals. Now that that is out of the way....
You typically have to have port 5555 TCP open for Data Protector to work at all. I believe this can be changed in the config files, but that is the default. Other random high (>1024) TCP ports (typically above 5555) can be used for backup data streaming, but 5555/TCP is where the DP client listener lives.
There are 3 main services that run on Windows, Data Protector CRS (Cell Manager Service), Data Protector Inet (Backup Client Service - listens on port 5555 for backup data requests from the server), and Data Protector RDS (DP Cell Manager Database service a/k/a "Velocis daemon"). They should all run as LocalSystem account.
The 4 vital services on UNIX are rds (Velocis DB), mmd (media management DB), crs (cell mgr.) and omnitrig (basically an every 15 minutes cron job that will trigger new backups as scheduled). The regular UNIX inetd (or xinetd on Linux) will handle the port 5555 TCP listener for you; needed entries in /etc/services and /etc/inetd.conf will be installed automatically with the DP software install.
Examples:
dphost:/# egrep omni /etc/services
omni 5555/tcp # DATA-PROTECTOR
dphost:/# egrep omni /etc/inetd.conf
omni stream tcp nowait root /opt/omni/lbin/inet inet -log /var/opt/omni//log/inet.log
dphost:/# omnisv status
ProcName Status [PID]
===============================
rds : Active [1562]
crs : Active [1569]
mmd : Active [1568]
omnitrig: Active
Sending of traps disabled.
===============================
Status: All Data Protector relevant processes/services up and running.
|
