Restore an archive

You can restore a single HMI server, an application, or an application and the
FactoryTalk Directory
. When restoring an archive with redundant servers, you can restore both the primary and secondary servers at the same time when restoring an archive with redundant servers. You can also re-host contents on another server machine, as long as it is part of the FactoryTalk directory.
TIP:
Before restoring an application, make sure the target application is closed and not in use. If you view the log file in the archive, some log information at the end may be missing.
The steps may vary if you are using a legacy .apa archive.
Starting from FactoryTalk View SE version 14.00, the data log configuration for the ODBC database is bound with a specific FactoryTalk Directory. As a result, when importing data log MDF files or restoring an HMI server with data logs within a different FactoryTalk Directory, you must enter a username and password on the
Setup
 tab of the Data Log Models editor to connect to the ODBC database.
To restore an archive
  1. In
    FactoryTalk View SE
     Application Manager, select the application type and click the
    Restore an Archive
    tab.
  2. In the
    Choose Archive
    area, select an archive.
  3. If the archive is encrypted, enter the correct password and click
    Submit
    .
  4. In the
    Review and Customize
     area, specify the following fields:
    • Scope of Restore
       to specify the contents to restore.
    • Primary Host
       to specify the primary server.
    • Secondary Host
       to specify the secondary server. The field is not available if redundancy is not set up.
  5. In the
    Finalize and Begin Restore
     area, enter another name to restore the application with a new name if needed.
  6. Click
    Restore
    .
    TIP:
    When the restore completes, you need to:
    • Relink your data server shortcuts to the right data sources.
    • Manually restore driver configurations in your OPC data server if you have set up the OPC data server in the archive.
    • Manually restore historical databases, such as FactoryTalk Historian SE server, ODBC database, DataLogPro InfluxDB, Alarms and Events historical logging database.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal