Configuration for consolidating data
The following diagrams shows the high-level architectural configuration of the key systems for consolidating data.
The creation of a dedicated data migration and testing systems is essential. The following systems are recommended.
System name | Description |
|---|---|
Production source | The production system from which data is exported. |
Production target | The production system into which data is imported. |
Data migration source | BMC Helix Data Manager uses this system as the source BMC Helix ITSM system from which data is extracted. This has three key benefits:
The data migration source system is created by using a full database backup taken from the production source, typically using the scheduled overnight database backup that is typically performed for production systems. To ensure data integrity, data cannot be changed in this system after the restore of the database from the production source system. Therefore, all user access (except by data migration engineers) should be blocked, and all scheduled actions performed by the AR System server are disabled. The data migration source system is a barebones AR System instance, typically consisting of a single mid tier and AR System server, used to enable the data migration engineers to inspect the data by using the AR System mid tier web user interface. BMC Helix Data Manager does not require a connected AR System server to perform data migration operations. |
Data migration target | BMC Helix Data Manager uses this system as the target BMC Helix ITSM system into which data is imported. This system is created by using a full database backup taken from the production target, typically using the scheduled overnight database backup that is typically performed for production systems. The data migration target system supports the development and unit testing of the data migration and transformation configuration. To ensure data integrity, user access and data changes in this system are tightly controlled. Unless this system is being used for unit testing, all user access (except by data migration engineers) should be blocked, and all scheduled actions performed by the AR System server are disabled. This is a barebones AR System instance, typically consisting of just a single mid tier and AR System server. |
Data migration target reference | The import of data from the data migration source system affects the data migration target system. This system provides a reference of the production target data exactly as it was prior to any changes. This is valuable for validation and remediation of any issues identified during unit or user acceptance testing. The data migration target system is created by using a full database backup taken from the production target, using the same database backup that is used to create the data migration target environment. To ensure data integrity, data cannot be changed in this system after the restore of the database from the production source system. Therefore, all user access (except by data migration engineers) should be blocked, and all scheduled actions performed by the AR System server are disabled. This is a barebones AR System instance, typically consisting of just a single mid tier and AR System server. |
User acceptance testing | This system is used to perform a range of activities including user acceptance testing and integration development and testing. This system is created by using a full backup taken from the data migration target system after data migration is completed. A distinct system is recommended for these activities as it allows the data migration target to be used as a reference for any issues reported during testing. Furthermore, logistical issues, data integrity issues, and impact to the project timeline can be a consequence of shared usage of the data migration target system. This system typically has multiple mid tier and AR System servers to better emulate the behavior of the production system. |
The shared components comprise the following:
- Database server—The server that hosts the source and target database. Hosting the source and target databases on the same logical database server is useful when investigating issues, and it makes management easier.
- Shared file system—The file system that export data is written to and import data is read from. While you can configure a separate file system for the source and target database, it introduces a file transfer operation into each data migration. A shared file system increases the speed of data transfers.
- BMC Helix Data Manager—The installation of BMC Helix Data Manager. The installation is completely flexible depending on the security restrictions of your data center. You can install all components within a single machine or distribute the components across multiple tiers of your data center. See Installing.