Back Up the Alarms and Events Data

Before you begin

Install the following components in the given sequence:
  1. Historian
  2. Alarms and Events
  3. Collectors
  4. Client Tools
  5. Standalone Help
If, however, the alarms and events data is currently in a version earlier than Microsoft SQL 2008, you must first migrate the data to Microsoft SQL 2008, and change the compatibility level to SQL Server 2008.


  1. Go to the <Historian installation folder>\Proficy DataBase folder, and open the Proficy.Historian.AandE.Migration.exe file.
    The Backup Existing Alarms and Events window appears.
  2. In the Time Range section, in the From and To fields, select the start time and end time of the backup duration.
    We recommend that you select small duration if you have many alarms. If you want to migrate the alarms in blocks of time, choose the oldest alarms first.
  3. In the Database Name field, enter the name of the database that you want to back up. Typically, this will be the same as the Microsoft SQL server you are using.
  4. Depending on whether you want to use Windows credentials or Microsoft SQL credentials, select either Use Windows Authentication or Use SQL Authentication, respectively.
  5. In the User Id and Password fields, enter the login credentials. Provide the username of a user who has the permission to connect and back up alarms.
  6. In Backup Folder Path field, provide the absolute path, including the file name, to store the backed up alarms (for example, c:\temp\March2010.bak). You can enter the path of a local file or a remote one, depending on whether the Microsoft SQL server is installed on the local machine or a remote machine.
  7. Select Test Connection to check if the source database is active and the information is accurate.
    The Begin Backup button is activated.
  8. Select Begin Backup.
    The alarms and evens data is backed up. The count of the rows that are backed up appears.

What to do next

Install a supported version of Microsoft SQL, and restore the data that you have backed up. Refer to Software Requirements for a list of supported versions.