Data Refresh Details

For multi-tenant CloudSuite clients, the basic purpose of a data refresh is to copy the data from one Landmark environment (the source) to another Landmark environment (the target) in order to create or maintain an environment that is nearly identical to the source environment. The target environment is then typically used for testing or development.

Because of the goal of a nearly identical target tenant, the following apply:

• A data refresh for Landmark is for all of the Landmark applications that you have. That is, you cannot perform the refresh for one application but not another.
• The Landmark Technology versions and the Landmark application versions must be the same on both the source and target, and the security keys of the source and target tenants must match.
• To avoid potential issues, the configurable features must be set the same on both the source and target tenants.
• If you have Inventory Intelligence configured on the source tenant, you must also have it configured on the target tenant.
• To ensure no issues with user access after the data refresh, you must ensure that the actor IDs match precisely between the source and target tenants, and custom security roles are in sync between the source and target tenants.
• In general, with only a few exceptions, you should think of a data refresh as achieving a replacement of the target tenant with the source tenant.

Given that there are a few exceptions to the target being completely replaced during a data refresh, it is important to understand what data is copied during a data refresh and what data is not copied. You can then employ the correct strategy to deal with both the case where data is not copied from the source to the target and the case where data is copied over the target data but you may want to retain the target data.

For certain business classes, if data exists in them in the target tenant, that data is purged. For details on which business classes are purged, see Viewing a list of business classes excluded from or purged during data copy process.

For data that is not copied from the source to the target, data being overwritten is not a concern. However, this means that you must maintain that data separately in the target environment. For example, entries in the ConfigurationParameter table are not copied during a data refresh. This is because those entries often contain URLs specific to that environment. This means that the ConfigurationParameter table in each data area in the target must be set up independently (nothing is copied from source data areas for them). For example, if you use Vertex or Infor Document Management (IDM), those products rely on configuration parameters. Those parameters must thus be set up in the target data areas for those products to function. The parameters will be retained on subsequent data refreshes.

When data is overwritten in the target, if you need to preserve the target data, you must make a backup of that data and reload it after the refresh. For example, since configurations and personalizations are overwritten, if you want to retain those in the target, you must create a backup and then reload them after the refresh. You should work with the appropriate support personnel to identify what target data should be saved off before the refresh and then restored after the refresh based on your business needs for the target tenant environment.

During the data refresh the target tenant is deactivated and, optionally, user access to the source tenant can be restricted. Async processing should be suspended in the target tenant before the data refresh to prevent queued jobs from starting before the data refresh is done.

For information about performing a data refresh, see the CloudSuite Self-Service Portal User Guide. For more information about the steps that need to be performed before and after the data refresh, see the Data Copy section of the Multi-tenant administration guide in the integration documentation library for your CloudSuite.