Netbackup 10.5 FETB Licensing enforcement
Hi I have a couple of questions regarding NetBackup 10.5/11 licensing. We’re currently running NetBackup 10.2 and are considering an upgrade to 10.5.1/11. I understand that perpetual licenses are still offered on a per front-end terabyte basis. Could you anyone please clarify if Veritas (or Cohesity, if applicable) will continue to offer perpetual licenses? Additionally, I've heard from a reseller that in NetBackup 10.5 onwards, if you exceed your licensed capacity, new backup jobs may be halted, even though existing backups remain available. Given that backup selections in NetBackup are mostly dynamic and can change from day to day also there is a possibility to suddenly have alot more TBs of data, I'm particularly concerned about how this enforcement mechanism works. If this claim is accurate, is there a grace period before backup operations stop, and how much time is typically provided to acquire additional licenses? Your insights would be incredibly helpful as we plan our upgrade strategy. Best regards, Mehrdad
Local account vs Service account for DNAS protection
Hi, I was interested to hear from the community as to if people tend to use local accounts or service accounts when it comes to configuring snapshot style protection for DNAS backups? Previously when we used ndmp we obviously had to use local accounts that were local to the storage array but we want to test moving away from NDMP to DNAS and as such it seems you can give it either local or domain based user so long as it has sufficient rights on the storage array. So what do people tend to use and for what reasons? Thanks in advance for any opinions/info
Storage options for OS upgrade
Hello, we have a NetBackup 10.4 server that we need to upgrade the OS from rhel 7 to rhel 9. Currently the MSDP is on the same disk that the OS will target (/dev/sda) so I need to copy/relocate the backup images during the upgrade. I opened a case with support and they suggested mounting SAN storage. Is this the only option to duplicate the backup data, or can we use DAS/NFS for setting up a new AdvDisk? This particular host has no other drives in it to relocate the data to, so it will need to be off the host during upgrade. Thank you
NBU setup in Cloud to Backup On-prem workload
Hello Experts & Legends, Hope everyone doing excellent..!! Happy joining community : ) As a beginner, Seeking some valuble guidance and inputs from you to get started for settingup Netbackup 10.x setup in cloud to backup On-prem clients. Planning like below: Cloud:- Netbackup Workloads primary -1 RH9 & Media -2 RH9 On-Prem: - VMware workloads <=100 clients Link via Direct Connect. For above requirement: what will be your recommendations for 1.VM size,Number of disks and type 2.OS perspective configurations like filesystem type, number of partitions, LVM FS, Kernel tuning etc. Any other recommendations? Any challenges you may warn about? Thank you, Mr.Tux
Did a catalogue restore, but seem to have missing information.
So I did a catalogue restore (full one) which honestly I felt went sideways. It said it finished partially but the only errors I could find were IOC_CHFLAG_SET errors. I had my profiles, on the file system the DB was backup to it's 375GB range. So I assumed all the data was loaded. When I login to the JavaGUI, ALL my volume pools are gone ALL my tapes are in 1 pool now. Is this normal? Because on the old system We had volume pools for each job which had tapes in it (We don't backup daily, we archive data so it goes on tape once and that's it so I believe that's why they used volume pools when they set it up ages ago). Either way. It just feels to me like I'm missing Data, and I'm not sure what to do now. I've opened a ticket but I'm running out of hours I can say "it's good let's test" vs "we need to roll back" (Let's just say it's been a long week getting to this point).
Notification emails not being sent on NetBackup appliance after 10.3/5.3 upgrade
TLDR: Not getting job failure notification or catalog backups emails from a Netbackup appliance after an upgrade to 5.3/10.3 but the email test notifications are working fine? Check the "mailq" command from a maintenance shell and see if mail is stuck in there. Then, check the postfix service on the appliance from the maintenance shell. The service might have stopped/died at some point. There may be a permissions error on a certain library: libpostfix-global.so -- Change permissions if needed and restart the postfix service from the maintenance shell. Not TLDR: I'm guessing this is one of those "one-offs" that likely won't happen to anyone else, however, if someone else ever sees something similar, here's what I went through: I recently upgraded a customer of mine. 2 x 5240 (edit: not 5230s! My bad) appliance, each acting as a Master/Media, with AIR. It was at version 3.1/8.1 , so it was a two-phase upgrade. To 4.1/9.1 first, did some quick backup and recovery testing, then 5.3.0.1/10.3.0.1 (current as of Sept 2024). Afterwards I ran the firmware upgrade for each appliance, successfully. After the upgrade, it looked like no backup job failure email notifications were being received from one appliance, and no catalog emails either. The other appliance was behaving normally. Both appliance notifications for job failures and catalog backups worked before the upgrade. Doing an "email test" from the Appliance CLISH under Settings > Notifications > Alert Configuration worked though -- No problem. There were no changes in email configuration in the administration console either in host properties, etc. All looked like it did before. Appliance CLISH hardware & software tests ran fine. bpps check of NBU services from the maintenance shell looked fine. It's been a while since I've had to dig into something like this, so it took me a while to figure out. This is opinion, impression, and anecdotal evidence only, and I do not claim to know what lies deep in the hearts and brains of Veritas engineers and developers. This was a weird one, but I'll admit I don't play with NBU appliances as much as I once did. First off I checked the SMTP configuration in the appliance WEBUI as I saw there was a note about the SMTP password sometimes needing to be re-entered after an upgrade. (https://www.veritas.com/support/en_US/article.100061042). But, no issues there. I checked the verbose bpdbm and bpbrm logs, and messages log for any errors or anything weird with mailing out notifications. I didn't see anything weird. I didn't think anything would change in the admin console, but I went through and checked the host properties and email settings for the master servers. All were exactly as they were before. As mentioned above, when I did an email test from the appliance CLISH... it worked. Came through without issue. I went into the maintenance shell and sent some mail manually from the command line, using mailx/sendmail. It worked fine, and arrived immediately. On a whim though and I don't know why I thought of it, I ran a "mailq" command from that maintenance shell: 107 emails in the queue. At that point I was asking myself "how is that possible when alert test emails and mailing from the command line are working immediately?" I didn't find any direct references to regarding appliances (and if someone has those, I'd love to see them), but I did see a few vague references and long-dead symantec tech articles, about checking postfix config on BYOS Linux NBU installs for unrelated issues, and it made me wonder. I went looking for a postfix service via 'service postfix status'. It was down. I then ran "journalctl -u postfix" and saw that the postfix service had died after the upgrades and subsequent reboots a few days ago. The error was: loading shared libraries libpostfix-global.so: permission denied In my case, I was able to do a "service postfix restart" from the elevated maintenance shell and it started cleanly and immediately processed the whole mail queue successfully. You may end up having to do some manual permissions changes to that library if that doesn't work. (if you're not comfortable with this or mucking around in the maintenance shell in general, please contact Veritas Support) My theory, and it's not like I can easily prove it, is this: The appliance itself uses sendmail (or another MTA) for sending out hardware failure notifications, test emails, etc. The NBU installation/application environment, for lack of a better term, seems to use its own postfix MTA with configuration inferred from initial appliance settings. When the postfix service errored out, job failure and catalog notifications just filed into the mail queue with no notification. The appliance itself is not aware of the postfix service. So it doesn't come up as a problem in the appliance software tests from the CLISH. The NBU environment itself does not care about the postfix service either. It sends mail out on job failures or other conditions, and because it ends up in the queue, there's no error, it doesn't care, nothing strange gets logged. I could be right, wrong, or anything in between on this. However, it fixed the problem for me. If someone has some further information and sources for the appliances and how this is configured, I'd love to see it. No logs to post as I do not have permission to do so from a sensitive environment. May you never encounter this. I've done upgrades on appliances before and never encountered this. But if you do, I hope this provides something to reference.NBU 10.4 Upgrade License XML Parsing Error
Running an upgrade from 9.1.0.1 to 10.4 on our master server running RHEL8 but the install script is stuck at the enter license file step due to the error: "State: Invalid ( Operation failed due to an XML parsing error. ) Key is direct from our support rep. Alternatively, can I cancel this step without restarting to add later as we've seen, it will be prompt at GUI's first launch once the upgrade completes. TIA
