bvstone

Omitting License Key Data Areas from Replication for High Availability/Disaster Recovery

Posted:

Omitting License Key Data Areas from Replication for High Availability/Disaster Recovery

We are often asked, sometimes after the fact, which objects should be included or omitted from mirroring/copying when using an HA/DR machine and our software.

The license keys for our software are stored in a data area(s) in library QGPL.  Each piece of software will have it's own data area(s) and license key, unique to each partition and model number.

The name of the license key data area is the same as the software.  For example, the key for SPLTOOL will be stored in a data area named QGPL/SPLTOOL.  The key for MAILTOOL will be stored in a data area named QGPL/MAILTOOL (as well as MAILTOOL Plus having it's own data area named QGPL/MAILTOOLP).

If you are using a newer version there is also a data area named <software>D that also holds key information.  For example MAILTOOLD, SPLTOOLD, GETURID, MAILTOOLPD, etc.

So, when you are setting up your copying or mirroring of objects from your production partitions to your HA/DR partitions, remember to omit these objects from replication so that should you ever need to move to your HA/DR system the license keys will be up to date.

As always, feel free to contact us with any questions.

Brad


Last edited 11/28/2016 at 10:17:32




Reply




© Copyright 1983-2024 BVSTools
GreenBoard(v3) Powered by the eRPG SDK, MAILTOOL Plus!, GreenTools for Google Apps, jQuery, jQuery UI, BlockUI, TinyMCE and running on the IBM i (AKA AS/400, iSeries, System i).