customkasce.blogg.se

1. #VERITAS BACKUP EXEC 16 DISCOVERING DEVICES UPGRADE#
2. #VERITAS BACKUP EXEC 16 DISCOVERING DEVICES FULL#
3. #VERITAS BACKUP EXEC 16 DISCOVERING DEVICES SOFTWARE#
4. #VERITAS BACKUP EXEC 16 DISCOVERING DEVICES DOWNLOAD#

The BE server windows firewall can also be setup to reject incoming connection from this port scanning (network security application) server IP to BE server IP:6101.

#VERITAS BACKUP EXEC 16 DISCOVERING DEVICES SOFTWARE#

Note: Refer Port scan software (network security application) or firewall software vendor documentation to accomplish the above. TCP 192.168.2.10:6101 192.168.2.1:41029 CLOSE_WAITĦ101 is the agent browse process for Backup Exec.ġ92.168.2.1 is the IP of port scanning application (network security application) server connecting to port 6101 on the Backup Exec server.Įnsure the port scanning software (network security application) is not scanning/connecting/blocking port 6101 on Backup Exec server.Īdditionally, use the same netstat command mentioned above to check if port scanning software (network security application) is not scanning/connecting/blocking port 6101 on the Backup Exec remote agent server, if the job appears to be hung backing up a remote server. Supported platforms include VMware and Hyper-V virtualization, Windows and Linux operating systems, Amazon S3, Microsoft Azure and Google cloud storage, among others.All management and configuration operations are. On the Backup Exec server, open command prompt and run the following netstat command to check which IP/servers are accessing port 6101: Veritas Backup Exec is a data protection software product designed for customers who have mixed physical and virtual environments, and who are moving to public cloud services.

#VERITAS BACKUP EXEC 16 DISCOVERING DEVICES DOWNLOAD#

Steps to download the Backup Exec Licenses and Installation Files within VEMS

#VERITAS BACKUP EXEC 16 DISCOVERING DEVICES UPGRADE#

This Issue is fixed in Backup Exec 21, upgrade Backup Exec to version 21. The port scanning application (network security application) may block connection between Backup Exec server and the Backup Exec remote agent server in some scenarios causing this hang. be coupled to storage device 135, and backup server 125 may execute backup. ( "Rate Mb/Min", float(line.replace(",",".Backup job stays in "Active: Discovering Resources". In response, the backup application performs a discovery process to identify. Return inventory #return empty list: nothing foundĭef check_backupexec_job(item, params, info):Įxceptions_are_ok = params.get("exceptions_are_ok")Ĭomment = "(end %s %s UTC, duration %s, size %s, rate %s Mb/min, dedup ratio %s)" %(line,line,line,line,line,line)

If line = "job": inventory.append( (line, None) )

If line = "error": inventory.append( (" ".join(line), None) ) If I hardcode the paramter “item” in the script to one of the backups name the details are “check failed - please submit a crash report! (Crash-ID: f43c6969-e8a4-11eb-9723-005056ba67c4)”.īackupexec_job def inventory_backupexec_job(info): Which I don’t understand is from which script does the Python-script get the “item”-parameter of the “def check_backupexec_job(item, params, info):” function? The Python-script is working well and also the Powershell-script is showing results of the agent. devices, an ordinary backup host must send the backup data over the local network to the media server. Multi-stream support is available for increased performance during backups and restores. Initiate backups and restores from the Backup Exec media server or from the Oracle RMAN console.

#VERITAS BACKUP EXEC 16 DISCOVERING DEVICES FULL#

We’re unsuccessfully trying to implent the BackupExec Plugin of “ Backup Exec plugin for check_mk | ” in checkmk-v2, which has already worked under checkmk-v1. Backup Exec 16 delivers full support for Oracle Recovery Manager (RMAN).