Planning your on-premises to on-premises environment migration
Plan your data migration from an on-premises to on-premises system by configuring the BMC Helix Data Manager architecture to optimize data throughput and minimize the impact to your infrastructure and network.
On-premises to on-premises migration architecture
The following infographic shows the four key architecture components required to support data migration from a source on-premises BMC Helix ITSM instance to a target on-premises BMC Helix ITSM instance:
Component | Summary |
|---|---|
BMC Helix Data Manager on-premises system | You can install BMC Helix Data Manager components on a single Windows machine. This machine needs connectivity to the source database, the file system, and the target database. To avoid conflicts with Java versions and other software, we recommend you to install BMC Helix Data Manager on a standalone machine. |
Source database | To migrate data, BMC Helix Data Manager exports directly from the source database. It does not require an AR System Server connected to this database. BMC Helix Data Manager exports data quickly by creating temporary database tables. However, this action might overload the database because temporary database tables require additional space. To avoid this issue, we recommend that you restore an overnight backup of the production system to a separate database server from which BMC Helix Data Manager can extract data to the file system. This database must be read/write enabled for BMC Helix Data Manager to create the temporary database tables. To set up this configuration, replicate the production database to the development environment. |
File system | BMC Helix Data Manager exports data to a file system. The file system must have enough space to accommodate the export of the entire database. We recommend that the file system must have a space of the existing size of the database on disk and an additional 20% space. The faster the disks underpinning the file system, the faster the export will be. The file system should be local to the BMC Helix Data Manager VM if possible because network round trips can impact the performance of data export. |
Target database | BMC Helix Data Manager imports the data files from the file system into the target database. |
API connectivity
BMC Helix Data Manager requires API connectivity to connect to the AR System server in the development system.
BMC Helix Data Manager uses the API connectivity details to trigger AR System API to build workflows associated with the following data:
- Approval Chains
- Approval Notifications
- SLA data sources
- SLA targets
- SLA Agreements