Previous Topic: Upgrading CA DataMinderNext Topic: Requirements


Version Compatibility

Ideally, when upgrading individual CA DataMinder machines we recommend that you upgrade all your CA DataMinder servers (gateways, Event Import machines, policy engines, and so on) at the same time as the CMS. Do this during a period of minimal user activity, beginning with the CMS and then working down the machine hierarchy to each server successively. When this is complete, we also recommend that you upgrade your client machines as soon as possible to reduce the amount of event data that needs to be periodically upgraded.

In practice, this is not possible and an upgrade rollout can easily take several weeks. Likewise, unforeseen complications may force you to upgrade some child machines before their parent server has been upgraded. For these reasons, you will inevitably have different version machines operating alongside each other during the upgrade rollout. Before starting the rollout, you need to understand how CA DataMinder handles data transfers (policy changes and captured data) between machines running different versions of the product. Full details about version compatibility are provided in the Upgrade Guide.