Hp Data Protector License Agreement

In our case, the required licenses increased from 76 TB to 191 TB after the upgrade to 9.06. The resolution turned out that I had a lot of archival sessions that I had to keep and that I was on cassette unlike D2D. The session was permanently marked and made me climb as high as 47 licenses on my purchase. We (HPE pointed out) discovered that my “old school” mentality and my permanent data catalog protection triggered the increase. I tried Sebastien`s export procedure from the MCF, and this seemed to help some, but makes recovery more difficult. What led me to an over-license of 12 was to remove the protection of the permanent Catalog data, and then isolate the tapes to protect them. I still have access to the data to retrieve my files via the catalog. All hpE software is provided in accordance with licensing restrictions. HPE`s end-user license agreement (“EULA”) regulates the use of HPE software, unless it is subject to a separate agreement between you and Hewlett Packard Enterprise and their subsidiaries.

In addition to the CLUE or such agreement, the software is subject to the following information about software licenses, including additional licensing permissions (ALC) and open source and third-party licensing conditions. the previous calculation model was imprecise and was not synchronized with the CBL licensing conditions. You`ll find updated SQL queries that are used in omniBack Bin-dbscripts-DP906. Now that I use a copy of objects to archive my ends of the month, they are not part of my data ability. — Hooray [138:716] 26 licenses must be purchased for the “HPE Data Protector – capacity based per TB SW” category. Run the “omnicc-check_licenses-detail” command. Thanks to Mark for your insight. I assumed a change in the calculation.

In the documentation I found, only the properties of VTL/Disk devices are mentioned. It`s a rude shock to have to almost double your licensing expenses. The calculation is changed to 9.06, there is a single data recorder on which the calculation is based now. Both are long, unsorted reports that can help those of you who also have problems with over-licensing. Look for the type – Backup and Conservation – Permanent to identify the session you might want to change. The big problem here is that last year I spent a lot of money to update the specifications recommended by the commercial engineer, I passed a “wellness” evaluation of my Data Protector 9.04 Operations and configuration and no one had any recommendation other than the 28 TB memory I had purchased/converted. It will be hard to sell my management as I will have to spend a lot of money this year to correct the mistakes of others last year. That is why I questioned that calculation. I may have misread the licensing criteria (I`ve already done so), but the HP team needs to make sure they have the same rules (know and use) and understand the rules. You can check your IDB for clearly protected long-term items that are no longer actively backed up.

A quick exmaple. If you changed the host name of a file server years ago and the object is still protected on a tape, while the same data is now backed up to a host name, this will also be included in the calculation (treated as two objects).