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(CEP-18915) Licensing of Data Protection
Interaction Date: November 15 - November 29, 2023 Interaction Type: Online Survey The Veritas Data Protection product management team wants some input on your preferences for data protection licensing. If you are interested in getting more details about this opportunity or in participating in other exciting interactions and are not currently a member of our CPEP program, you can register here:https://cpep.veritas.comthencontact us atcustomer.engagement@veritas.com.
Custom Edition licensing Hyper-V / VMware licensing Windows/Linux agent question
I've come across this thread about licensing of the Hyper-V agent as we currently have an old Custom Edition licensing (or à la carte). The original license have been bought at least back when BE 15 was the current version and where no Subscription or Bronze/Silver/Gold editions even existed. Yet in the current BE 20.3 licensing guide on page 26 the same phrase appears but the Veritas support and the linked thread mentions that this would only apply to Windows agents, not Linux agents. All I can see there is that IF you have Bronze/Silver/Gold THEN the Hyper-V agent is included (not applicable to us as we have custom edition) yet still also says "Custom edition licensing: Each Agent for VMware and Hyper-V license includes unlimited deployment of Agent for Windows and Agent for Linux to the virtual machine guests of that licensed hypervisor host server only" In the old licensing guide of BE 15, page 17 the same phrase appears but without mentioning "custom edition" (since that was the modus operandi of licensing back then): https://www.veritas.com/content/support/en_US/doc/ka8f10000008Y28AAE So why if you have the custom edition AND have a support entitlement do we not have the Linux agents yet the licensing guide (if I try to read between lines and twist words) does not give us Linux agent support
Managed Service Account Issue within Backup Exec
Hi I'm desperately trying to update our license for our backup exec server which acts as disaster recovery. However whenever I try to (see screenshots below) it asks for the managed service account password. I didn't think it was possible to get the managed service account password!!! No one in my team nor those that used to work here know what it is. Is anyone able to advise a) how I can get that password or b) workaround the issue. Please help!!!
NBU Licensing doubt
Hi there, The principal site administrator with NBU 8.1 send us tape drives periodically andI need to restore those backups in a remote office with a differente console. These backup contain snapshots of VMware, SQL and Oracle. What is the minimum licensing I need on this remote office? Due to a only restore proven scenario(no backups)... Its ok a Netbackup Server and Library Based Tape Drive license only? Do I need agents for restore? What other considerations do I need to know to make it work? Thanks a lot!
vxlicrep ERROR V-21-3-1015 Failed to prepare report for key
Dear all, we got a INFOSCALE FOUNDATION LNX 1 CORE ONPREMISE STANDARD PERPETUAL LICENSE CORPORATE. I have installed key using the vxlicinst -k <key> command. But when I want to check it using vxlicrep I'm getting this error for the given key: vxlicrep ERROR V-21-3-1015 Failed to prepare report for key = <key> We have Veritas Volume Manager 5.1 (VRTSvxvm-5.1.100.000-SP1_RHEL5 and VRTSvlic-3.02.51.010-0) running on RHEL 5.7 on 64 bits. I've read that the next step is to run vxkeyless set NONE, but I'm afraid to run this until I cannot see the license reported correctly by vxlicrep. What can I do to fix it? Thank you in advance. Kind regards, Laszlo
