The newer versions of what was once called simply Btrieve (BSERVER on client-server Novell systems) later became Pervasive, with newer engines also referred to as PSQL and more recently as Actian Zen. These more modern engines will be collectively referred to here as PSQL.
After the 16-bit Btrieve 5.10a, Windows versions first in 16-bit and then 32-bit versions were released by Btrieve Technologies, Inc. over the 1982 to 1995 time frame. With a corporate name change to Pervasive Software, Inc. there were versions 7, 8, and by 2006, version 9. Unlike with older pre-Pervasive versions, these newer versions required unique licenses. The PSQL licenses were eventually linked to CPU or other installed hardware in versions 10 and 11. But that was changed starting in version 12 to be tied to solely the computer (server) name and that continues to be the case through the latest version, Actian Zen v16.
So these newer PSQL licenses which since v12 are solely tied a computer name can only be active on one computer at a time. Both workgroup for smaller installations and server class licenses are available (more recently both "enterprise" and "cloud" versions are options in newer versions). It is mainly server type licenses that are being referenced below but could also relate to workgroup licenses that can be configured to support small client-server networks.
In a normal situation where the production server is operating, when migrating to a new server (or setting up a backup PC for a "just in case" scenario), you would want to install from your original downloaded media and leave the PSQL software in an unlicensed state (a temporary license will automatically be installed and its expiration date can be viewed in the PSQL License Administrator) on that new server. It will then operate in a temporary license mode (the periods have changed over time, with older versions it normally has been 30 days but could be shorter such as two weeks; the trial version for v16, the latest version, is apparently for just one day) that gives you time to test the new server and verify that everything is working. Then when finally migrating you would deauthorize the license on the production server (via the installed PSQL License Administrator which can be accessed either separately or via the PSQL Control Center; take a screen shots before deauthorizing) and apply the license on the new server. Internet access is required when deauthorizing and then also when authorizing on the new server. There used to be a limit as to how many times you could authorize/deauthorize but currently that appears to no longer be the case.
But, as previously mentioned, only one server can be authorized by any one PSQL key at any one time. (The only away around that would be to buy a second license and they are not inexpensive; inexpensive compared to Oracle and perhaps Microsoft SQL, but not cheap.)
In case of the situation where the production server goes down and cannot be brought back to life, that is when it is critical to have an image-level backup for the Zen/Pervasive install (which is not installed in the same folder as the Advanced Accounting or other TAS-based system and is completely separate; the image-level backup for the accounting software would have to then be supplemented by a recent file level backup as well as any programs that have since been changed via ongoing updates as well as for any custom modified programs). Without the image-level backup which which you could restore the PSQL license in the event of total failure of the production server, in the past you would simply contact Actian (formerly Pervasive) to get around the problem of not being able to deauthorize the license. In the last few years however Actian has taken a reversal in their approach and now requires an expensive tech support contract instead of a free, simple support ticket.
See for example this warning on the pricing pages at Goldstar:
 |
| https://www.goldstarsoftware.com/prices16.asp |
Goldstar now includes that cautionary language on versions going back to v11 (although the image-level backup would only help starting with v12).
See also:
https://communities.actian.com/s/supportservices/actian-licensing/actian-zen-licensing
We've already had two users who were forced into buying new licenses in light of this draconian policy that we can only hope they will reverse in the future (we and others have complained; there is also talk of a class action suit).
Even if you have an image-level backup, that will only work if the replacement server has the exact same computer name as the prior production server. Otherwise you will receive a key validation failure error message indicating that there has been a change to the machine signature and an indication that it relates to the different computer name.
Note that the foregoing does not apply to the many users we still support that are running valid legacy Btrieve 6.15 32-bit engines nor to the even older Btrieve.exe that loaded as a TSR from 16-bit ("DOS") versions although an image-level backup for those systems could still be useful.
No comments:
Post a Comment