Migrating from BMC Real End User Experience Monitoring v2.7 to Software Edition

You can migrate the  BMC Real End User Experience Monitoring v2.7 database and configuration information to the new Software Edition.

Migrating is especially useful because it allows you to reuse configured information from the earlier version, including the Real User Analyzer's summary data. This saves time in getting started with the Real Analyzer or Collector Software Edition components.


Only proceed with the migration process after a BMC upgrade expert has reviewed and confirmed that the environment is ready for an upgrade. When you migrate this information to the Software Edition, any existing database and configuration information in the Software Edition machine is overwritten and cannot be recovered.


Before starting the migration process from the BMC Real End User Experience Monitoring v2.7 components to Software Edition components, you must:

  • You must open an Assisted MIGration Offering (AMIGO) support case before proceeding with the BMC Real End User Experience Monitoring migration from v2.7 to the software edition. Migrate only after a BMC upgrade expert confirms that the environment is ready for an upgrade.


    The AMIGO process includes the steps that will guide you from analysis through the implementation of your migration plan to the software edition.

    To start the AMIGO process, see the BMC Communities Knowledge Article that explains how the AMIGO process will help you complete a successful migration.

  • Confirm that the Perl DBI libraries are installed on your system to migrate the component's data and configuration.
  • If you configured access to an SNMPv3 MIB on a Real User Analyzer or Collector by using the Enable Authentication and Privacy (authPriv) security level option, you must be sure that an Authentication password and Privacy password are entered in the SNMP MIB information. For more information, see  Configuring the SNMP MIB.   
  • Review the following differences to understand the features available in different versions.

Feature differences between BMC Real End User Experience Monitoring versions

If you are migrating to the BMC Real End User Experience Monitoring Software Edition, the following table outlines the feature differences between the Virtual Edition and the newest Software Edition. 

BMC Real End User experience Monitoring 2.7 was a Virtual Edition that was part of the  BMC TrueSight App Visibility Manager 2.7.

Feature differences between BMC Real End User Experience Monitoring versions

FeatureVirtual edition 2.7Software edition 10.5Software edition 10.7Software edition 11.0
Integration with the TrueSight consoleNoYesYesYes

Service Context dashlet

View Incident Summary, Traffic Gauge, and Traffic dashlets from multiple Analyzers in single dashboard (APM Console)



Application Watchpoints
(including Page SLTs by specific Application Watchpoint)

Performance Analytics Engine YesNoNoNo
Reporting on performance and availability with SAP Business ObjectsYesNoNoNo
SNMP integrationYesNoYesYes
SSL key management using UI and APIYesNoNoNo
System server certificateYesNoNoNo

Syslog integration

Real User Collector data source testYesNoNoYes
Web/System update (includes software and Geolocation database)YesNoNoNo
Manually upload a new Geolocation databaseYesNoNoNo

Backup of system configuration and data


NTP and DNS configuration from BMC Real End User Experience Monitoring interface

Self-health monitoring (alarms)YesNoNoNo
Integration of BMC Real End User Experience Monitoring and Application VisibilityYesNoYesYes


To download the latest backup archive

The backup archive file includes the component's configuration. For the Real User Analyzer, the migrated information to the Software Edition includes the component's summary data.

A new archive file is created every day at 3:00 A.M. (GMT), by default. It is also possible to manually initiate a new backup archive.

Use the following procedure to view the status of the last archive, or initiate a new backup archive:

  1. Log into a Real User 2.7 component  (Analyzer, Collector, or Monolithic).
  2. In the address for the component, delete any address string after the component's IP address, and enter dsm.
    For example, https://collector.bmc.com/dsm or https://analyzer.bmc.com:434/dsm
  3. Click the Config link at the top of the window.
  4. From the Config window, you can either download the last automatic backup archive, or initiate a new backup archive. The date and time of the last backup archive is in the Archive date field.


    If the the date in the Archive date field shows no backup has been completed in the last three days, do not proceed with this migration process, and contact BMC Customer Support immediately.

    Component Config window

    • To download the last automatic archive, you can click Download, or run the following API command from a command line prompt.

      curl -k 'https://<EUEM component IP>/backup?usr=___&pwd=___&export' > backup_file.tgz

      For example:

      curl -k  'https:// machine-sample.com :443/backup?usr=test&pwd=sample&export' > backup.tgz

    • If you want to manually initiate a new backup file, click the Initiate backup creation button. The time required for a new backup archive depends on the amount of component data.
      When the backup starts, the State field changes to RUNNING, and the Progress field shows the completed steps of the backup process. You must refresh the browser window to see updates on the backup process. The new backup archive is ready when the State field changes to idle, and the date in the Archive date field is updated.
      When the backup is completed, you can click Download, or run the API command.

To migrate the data to the Software Edition

  1. Login to the machine where the Software Edition components are running.
  2. On the machine where the Software Edition components are installed, go to the following directory and locate the restore_2_7_backup.sh  script.
    <EUEM installation directory>/common/virtual_to_software_edition
  3. Run the restore_2_7_backup.sh  script with the following required parameters. This script stops the Software Edition components' services. When the migration process finishes, the components are automatically restarted.
    restore_2_7_backup.sh <backup_file> <euem_component> [location_to_unzip]

    • <backup_file> – The backup archive with the database and configuration information that will migrate to the Software Edition components.

    • <euem_component> – The component that you want to migrate to. 
      • --collector or -c
      • --analyzer or -a
    • [location_to_unzip] – Optional location to unzip the archive. The default location is /tmp.

      For example:

      ./restore_2_7_backup.sh /tmp/backup.tgz --analyzer /opt/bmc/euem

Working with multiple BMC Real End User Experience Monitoring instances

The migration process copies the device name and hostname to the Software Edition machine.

After the migration is completed, it is possible to continue working with the v2.7 machine, while the Software Edition machine is also operating. If this is the case, you must manually change the device name and hostname for the software edition components. The two Real End User Experience Monitoring instances cannot use identical device and hostnames.

For this scenario, the recommendations are as follows:

  • Give new device names and hostnames to the new Real User Analyzer and Collector Software Edition components.
  • Continue working with the v2.7 machine and the Software Edition machine for up to 90 days. This is the maximum retention period for the  Watchpoint  (summary) database.

After you see that the Real User Analyzer Software Edition version is collecting data correctly, you can stop sending traffic to the v2.7 deployment.


To perform this procedure, you must have Application Operator-level access, or higher.

To change device and hostname, complete the following steps for the Real User Analyzer and the Collector Software Edition components:

  1. In the Software Edition components, point to Administration > Integration, and then click Network identity.  

  2. On the Action menu for the Device name section, click Edit.
  3. In the Device name box, enter a new name for the device.
  4. Click Save.
  5. On the Action menu for the Hostname/Virtual IP section, click Edit.
  6. In the Hostname/Virtual IP box, enter a name or a virtual IP address (in a dot-decimal format) for the device to use when it generates links back to itself, for example, in mailouts.


    Ensure that host name does not contain any underscore (_) characters, because the system refers to such host names as IP addresses.

  7. Click Save.


Was this page helpful? Yes No Submitting... Thank you