Welcome to your hub for enterprise data protection discussions. Learn more about recent changes to the VOX Community here.
Forum Widgets
Recent Discussions
Editing Host file on Netbackup 5520 appliance
I could do with some help on what options are available to add entries to the host file on the 5520 appliance. I am familiar with using the CLISH and navigating to >>Network from the main menu and the using the following command: hosts add 10.0.0.1 nbutest.nbappliance.lab nbutest host show - will provide an output of information in the file. Is there anyway to access the the host file by going through Support>>Maintenance(Enter Password)>>Elevate I believe you can drop in to the normal Linux directory structure and navigate to \usr\openv\netbackup... But where is the host file located and what is is called since most Linux articles seem to refer to \etc\hosts I have tried to use vi and view the hosts & hosts.conf files located in the \usr\openv\netbackup\bin directories, but they do not seem to list the same info as what I see when running hosts show through CLISH. Any assistance would be appreciated with the above. Thanks In Advance
Readiness Analyzer is not working properly
Hello Everyone, I would like to ask how to resolve our issue when running the latest Readiness Analyzer on our NetBackup appliance. Our appliance is currently on version 4.1, and we are planning to upgrade to version 5.1.1. However, after installing the Readiness Analyzer, it does not run completely and only displays an output. This is appliance 5240 model. See below screenshot: Thank you. Kind Regards, HeiNBA 5260 FLEX OS 6.1 NBU v. 11 and DR emails
Hello, I am trying to get working emails for hot catalog backup. Unfortunately it is not working. In previous releases it was working. Not sure if I am doing something wrong, or missing some part of configuration. So the hot catalog policy has the recipient set, on NBU gear icon I did configure alerts and notification settings... But no dr related emails are coming in... When I am running /usr/openv/netbackup/bin/mail_dr_info.sh with needed switches I am getting the following: [root@master bin]# pwd /usr/openv/netbackup/bin [root@master bin]# ./mail_dr_info.sh email@exampleaddress.com TestSubject mail_dr_info.sh mail_dr_info.sh s-nail: Cannot start /usr/sbin/sendmail: executable not found (adjust *mta* variable) /root/dead.letter 55/1688 s-nail: ... message not sent [root@master bin]# Anyone has an idea what I am missing here? NBU is in version: [root@master bin]# cat /usr/openv/netbackup/version HARDWARE LINUX_RH_X86 VERSION NetBackup 11.0 RELEASEDATE Mon Mar 10 18:39:55 CDT 2025 BUILDNUMBER 0055 Running on NBA5260 FLEX OS 6.1.
all bonded interfaced changed after the OS to 6 update
Hi Got a strange issue. had to cluster to update from 5.1 to 6. one cluster was ok no errors, all green all went through. Second cluster also all green but all bond were changed from 802.3ad to active-backup during the OS update. very strange. never saw that before. of course try to manually correct the config file but now it's read-only FS. Had some many vlans attached to those interfaces which are part of the instances too. cannot recreate all of that. and on top, I can edit the instance settings but cannot add new Network config I created on node, nothings is displayed in "managed pair". Any ideas how to modify an existing bond? of course will create a ticket but must wait till the support extension in place (one to two weeks with no backups is a bit bad).
pairing 2 flex appliances for replication failed
Hi all We have 2 flex appliances and while configuring pairing we get two failed jobs on the monitor 1st job error message : failed to create high availability replication link 2nd job error message : failed to configure replication service anyone can help please ? knowing that the host0 is on the management network and we configured a bond with two interfaces for replication on a replication network when starting pairing we used the bond for replication and we gave an address in that network (on dr appliance) when finnishing pairing (on primary appliance) we used also the same bond configured for replication and we gave an ip in that network
