Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Replicating the databases

BMC recommends that you replicate the databases used by your data sources and use the replicated database as your reporting instance. This replicated database should be configured with regular refreshes from the production database.

Note

When you install BMC Analytics for BSM, you must point to a live database. This creates all the BMC Analytics for BSM related DB tables and views on the live database and are automatically populated into the replicated instance according to the replication policy.

Once the replication process is complete, import the ITSM Universe using the Universe Designer Tool and then provide the connection details of the replicated instance.

The main benefit of using a replicated database is to reduce the performance issues on the live database and improve the application reliability, as the data is spread into multiple systems. This also helps in data retention in case of any failure. If you concurrently refresh certain BMC Analytics for BSM reports, depending upon the amount of data on the replicated database, the reports may take a long time to refresh. In this case, the live database is not impacted. Additionally, if the live database is down, you can still use the replicated database as a backup for reporting and continue with the analytical reporting.

For more information about the replicated BMC Remedy AR System database, see BMC Analytics for BSM with a replicated BMC Remedy AR System database.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*