Another firewall question. Basic setup one sever, 10 clients
I have looked at the firewall rules in https://www.veritas.com/support/en_US/article.100017208 My setup is just a single backup exec server with locally attached disks for backup to disk (no cloud, not tape no remote storage). No other servers are used (apart from the agents). No alerts, no deduplication (I think). Clients are windows servers. Here we go... The backup server needs to initiate communicate to the agents on port 10000 to the clients The backup server then needs to inititiate communicate with agents on a dynamic address range (1024 to 65535 --can be customised) The server also initiates with the agents on port 6101 for "browsing"(??). Do I need this? Do I need to open up 3527/6106 (beserver), if so is it.. The agents need to initiate communication with the backup server on ports 3527 and 6106 OR The backup server needs to initiate communication with the agents on ports 3527 and 6106 Same question with Backup Exec Job Engine(beengine) on port 5633 I am going to say that "backup exec managment" (port 5014) does not need to be open in a simple setup. With the above in place ..... I do not need to touch any other FWs.BE_ST Tool, VxGather and tracer.exe viewer
Hi team, I´m working providing Symantec Support for Backup Exec with a Partner Hardware Manufacturing and some times I need to use the follow troubleshooting tools as a bellow: Be_ST (Backup Exec Support Tool) VxGather Tracer.exe Log Debug (From Register entries) SGMON (Live Debug) I´d like to know if there are any tool that help to viewer these logs. I usually have difficult to interpreter the because these logs aren´t easy. Thank in advance for any help. Fginacio
Implement Netbackup 6.5 using vnetd over public & private LANs
I'm trying to implement Veritas Netbackup 6.5 with one master server, 3 media server and a dozen of clients. On the production LAN, I want to install the master server, a media server and a few clients. In the DMZ, I want to install another media server and a few clients. Another media server and a handful of clients will need to be installed on our reference (engineering/development) LAN. The production LAN, reference LAN and DMZ are separated by firewalls which will allow communication between all servers and clients over the vnetd port. Netbackup control communication is allowed to pass through the firewalls. User data (backups) should not be allowed to pass through the firewall but should go to the media server in it's own LAN (in prod LAN, ref LAN or DMZ). To limit the impact of backups/restores on the bandwidth/saturation of the public LAN (e.g. 20.30.x.x), I'd like to send user data (backups) between the clients and the media servers over a private LAN (e.g. 192.168.x.x). Would it be possible to implement this? - Send all Netbackup control communication over the public network through the firewalls using vnetd. - Send all Netbackup data (backups) between clients and media server over a private LAN. Any hints, tips, user experience would be highly appreciated.