CH112-19 Backup and Restore - RevB

800xA Minerals Training
Chapter 19 Backup and Restore
TABLE OF CONTENTS
Chapter 19 Backup and Restore..................................................................................................................................................... 1
19.1 General Information........................................................................................................................................................... 2
19.1.1 Objectives ................................................................................................................................................................... 2
19.1.2 Legend ........................................................................................................................................................................ 2
19.2 Backup Methods ................................................................................................................................................................ 3
19.2.1 Windows Backup........................................................................................................................................................ 3
19.2.2 Import/Export ............................................................................................................................................................. 3
19.2.3 Full Backup / Restore ................................................................................................................................................. 4
19.2.4 Cloning / Imaging ....................................................................................................................................................... 4
19.2.5 Disaster Recovery ....................................................................................................................................................... 4
19.3 Full Backup........................................................................................................................................................................ 5
19.3.1 Backup Procedure ....................................................................................................................................................... 5
19.3.2 How to Configure the Backup Service ....................................................................................................................... 5
19.3.3 How to Create a Backup Definition............................................................................................................................ 7
19.3.4 How to Run a Backup................................................................................................................................................. 8
19.3.5 Backup for System Messages and Basic History Data ............................................................................................. 10
19.4 Restore a System.............................................................................................................................................................. 11
19.4.1 Preparation Steps ...................................................................................................................................................... 11
19.4.2 How to Restore a System.......................................................................................................................................... 12
19.5 Import / Export ................................................................................................................................................................ 15
19.5.1 User Interface............................................................................................................................................................ 16
19.5.2 Precautions and Limitations...................................................................................................................................... 17
19.5.3 How to Export Data .................................................................................................................................................. 17
19.5.4 Hints for Exporting Data........................................................................................................................................... 19
19.5.5 How to Import Data .................................................................................................................................................. 19
19.5.6 How to Create a Difference Report........................................................................................................................... 22
19.5.7 Dependencies............................................................................................................................................................ 23
19.5.8 Resolving Errors ....................................................................................................................................................... 24
1 / 24
CH112-19 Backup and Restore - RevB
19.1 General Information

19.1.1 Objectives
On completion of this chapter you will be able to:
Describe the different Backup and Restore methods
Use the Backup and Restore procedure
Use the Import / Export Tool
19.1.2 Legend
2 / 24
<>
Indicates a key name.
Indicates when you go from one menu to a sub-menu.
Bold
Indicates a menu name or an option in a menu, or file structures
Indicates dialog box buttons, tabs, instructions etc.
Indicates start/explanation of student activity
19.2 Backup Methods

The backup and restore procedure consists of two different parts
Backup of standard Windows system
Backup of the System application data
19.2.1 Windows Backup

Windows backup tool could be used to backup specific file directory. It is useful for
backup of important operating system files. The backup repetition can be automated.
It is not possible to move a total Windows backup from one node to another. The
800xA system contains computer node specific data that the backup was taken from.
Thus this method is not recommended for making the full backup, but only used for
system messages and basic history data.
19.2.2 Import/Export
The Import/Export tool can be used to save 800xA system objects and aspects
information one portion at a time. It stores the information in files outside of the
running Aspect Directory. This tool can be used to transport applications between
different aspect systems. For example:
Import data from scratch.
Save user defined objects and aspects off line.
Use the Find Tool in Plant Explorer and export the results.
The Import/Export Tool should never be used for the purposes of performing backups
of your system. There are limitations on the number of total objects that the tool can
handle and it is difficult to restore from Export files and maintain the necessary
dependencies between objects and aspects that are threaded through a system.
The main difference to the backup tool is that individually exported portions of 800xA
information can be imported back into the original system or into a completely
different system while backed up 800xA information can only be used to restore a
specific system on specific workstations.
3 / 24
19.2.3 Full Backup / Restore

Full Backup must be performed in order to save and restore the Aspect Directory of an
800xA system. Backups are always made on a running system, but you have to stop
the system to perform a restore.
When a backup is used to restore a system, the following restrictions apply:
The backup can only be restored to an 800xA system that is equivalent to

the800xA system from which the backup was taken
All 800xA software must be installed and of the same level (version, service pack,
rollup, etc.) as when the backup was taken
The same system extension must be installed as when the backup was taken
The Domain server must contain the same configuration as when the backup was
taken
19.2.4 Cloning / Imaging

There are several software packages available for backing up a complete disk or
partition. For example, Norton Ghost is a cloning software that is often used. The
result will be a compressed file that then could be copied to a CD disk or other
computers disk.
It is recommended that cloning/imaging software be used to save (and restore if
necessary) an image of workstation hard drives after installation of third party
software and/or after installing all software.
However, it is important to understand the limitations and ramifications associated
with these utilities. In some cases, such as corrupted data, corrupted software, or hard
disk failures, these utilities can be useful. While in other cases, such as replacing a
workstation these utilities may be of limited use.
19.2.5 Disaster Recovery

Note that some information specific to certain functional areas is not saved during an
800xA system backup. The information that must be saved manually, such as
Foundation Fieldbus, Information Management, Asset Optimization, PC Network,
PLC Connect, 800xA for Harmony etc.
It must be stressed that recovering a complete System 800xA including Domain
Controller, historical data etc. is a quite complex task.
4 / 24
19.3 Full Backup

It is recommended to take a backup of your system regularly. Make sure the system
and the backup service provider is running while the backup is made.
Some requirements:
Backup is taken on-line but no changes shall be done in Aspect Directory during
an active backup.
Avoid using the backup when one or two secondary servers are down.
You should not backup to a network-mounted disc. This to assure a successful

storage of the backup, which will not be possible if the network fails.
The data is stored in afw files. Make sure that your local disk has enough space to
store the backup. After this you should always store your backup in another location
than the 800xA system.
19.3.1 Backup Procedure

Follow the recommendations below to make a Full Backup.
1. Create a Backup Definition object and configure the definitions of scope and
storage settings.
2. In the aspect, click the Start Backup button to start the backup.
3. A new Backup object is created when the Full Backup is running. It will be
created in the Maintenance Structure under the Backups object. It will be called
<Backup Definition Name>; <Date>; <Time>.
A state file called BackupInfo.xml and Backup.log are also produced, located in
selected backup directory.
19.3.2 How to Configure the Backup Service

The Backup Service runs on each aspect directory server node in a service group. The
Backup Service is not redundant, but the different backup service providers enable
backups to be run on different nodes.
1. Select the object Services | BackupService | Basic | BackupService_Basic_<Node
Name> in the Service Structure.
5 / 24
2. Select the tab Configuration on the Service Provider Definition aspect and
choose the node you want to put the backup on.
3. Select the tab Special Configuration and assign the backup path where the
backup should be stored.
It is possible to specify a free disk space limit. The backup service guarantees that
this amount of disk space is free after any backup is made. If the limit is passed
during a backup, the backup operation will fail and an error will be issued.
A low disk space warning limit can also be specified in this tab. If there is less
disk space available than the limit, a warning is issued.
6 / 24
19.3.3 How to Create a Backup Definition

Backup Definitions includes the configuration of backups to be made, but not the
actual data.
1. Create a new Backup object in the Maintenance Structure.
2. Select the tab Scope on the Backup Definition aspect and choose to backup the
Aspect Directory.
NOTE!
Backup of Basic History and System Message through

External Services is not supported yet.
3. Select the Backup Service Provider on the Storage tab. The Storage tab defines
the node on which the backup will be made. The nodes available are those that run
a backup service provider.
7 / 24
19.3.4 How to Run a Backup

You have now configured which data to store in which place.
1. Select the Backup Definition object in the Maintenance Structure.
2. Select the tab Summary and Start backup on the Backup Definition aspect and
start the backup manually.
3. A status window is displayed during the backup and indicates at the end whether
the backup was successfully.
8 / 24
4. A new object is created under Backup object. It will be called <Backup Definition
Name>; <Date>; <Time>.
The Backup objects can have three different object icons. These indicate Success
(green), Warning (yellow) and Failure (red).
NOTE!
Do not manually import or edit any information in

backup files.
9 / 24
19.3.5 Backup for System Messages and Basic History Data

Follow the steps below to copy the System Messages and Basic History data from one
system to another.
Save Event Data
In the system from where the messages are to be imported: stop the System
Message service provider from the Service structure
Use Windows Backup to backup all files in the directory

[disk]:\OperateITData\SystemMessage\{GUID} GUID is an identifier that is
different for each System Message service provider
Start the System Message service provider
Save History Service
Stop the history server from the Service structure
Use Windows Backup (not the 800xA Backup) to backup the files in
the[disk]:\OperateITData\History\{provider ID} directory
Start the history server again from the Service Structure
NOTE!
10 / 24
Information Manager is the appropriate tool to archive

historical data.
19.4 Restore a System

There are several restrictions upon when a backup can be restored a system:
Same version, Service Pack, Rollups and patch level for all OperateIT 800xA
software as when the backup was taken
Same System Extensions installed as when the backup was taken
Same configuration on the Domain server
No system exist in any node that is a target for the restore
The existing system must be deleted before the restore can be started. Make sure that
any redundant servers; clients and connectivity servers are removed before deleting
the system.
If a node is not properly disconnected from a system, the system will still remain as
files on the hard disk and registry keys. Old systems may cause conflicts if a new
system is loaded. Therefore its important to ensure that all old systems have been
successfully deleted before adding the node again.
19.4.1 Preparation Steps

The following steps outline the 800xA system restore procedure.
1. Minimize the system to a single node Aspect Server:
- Disconnect and shut down all redundant servers and clients
- Stop the 800xA system
- Restart the node for each Connectivity Server and Aspect Server
2. Stop and delete the system
3. Open the Configuration Wizard and verify there is no system remaining
4. Verify that OperateITData and/or OperateITTemp directories do not exist in
the root of any drive. Delete them manually if found.
5. Check that the system has been removed from all nodes, then shut down all nodes
except the one being used to restore the 800xA system. This is the same node
from which the backup was taken.
6. Start the restore procedure on the same node the backup was taken.
11 / 24
19.4.2 How to Restore a System

The restore will recreate an equivalent system, after a computer failure. A restore of a
800xA System is performed from the Configuration Wizard.
1. Select Restore System and click Next in the Configuration Wizard.
2. Specify the path to a location of the backup by pressing Select Path.
12 / 24
3. Specify the root directory and the application will search for backups below the
root.
4. Select one backup in the tree view to be restored. From the selected backup, the
aspect directory is restored.
5. Select the path where to write the system data.
13 / 24
6. Select a Node on the Primary or Secondary nodes area in the Node Configuration
dialogs. Click Next to continue.
7. Click Finish to complete the restore.
8. After the restore operation is complete the computer must be rebooted in order to
start all the services and start up the system.
NOTE!
14 / 24
Please refer to the manual how to restore System

Message Service Data and History Service
19.5 Import / Export

The Import/Export tool allows objects to be stored and restored with their aspects.
Objects are stored in structured afw-files. It is also possible to view the contents of an
archived file.
The Import/Export tool should be used to transport small applications in the form of
object types and/or object instances between configurations.
The three common ways of using the Import/Export Tool are:
Use the tool to import data from scratch.
Save user defined objects and aspects off line.
Use the Find Tool in Plant Explorer and export the results.
The Import/Export tool is a good tool for safe keeping of configurations. In a scenario
where an upgrade of the system software is required then the Import/Export tool can
be used. Use the tool to backup all project specific objects and aspects in an afw file.
If for any reason these objects become corrupt or lost during the upgrade then the tool
can be used to import them back into the system again.
15 / 24
19.5.1 User Interface

You can call the Import/Export tool in two ways:
Click on the icon
Select Start | Programs | ABB Industrial IT 800xA | System | Import Export
in the Engineering Workplace
The user interface is designed to resemble the Plant Explorer as much as possible. It
consists of two main areas; the object browser and the aspect list.
Object Browser
Aspect List
The figure above shows the Import/Export tool with a file opened and an object
selected. The aspects of the selected object are shown in the aspect list.
An action or option can be available from more than one place in the User Interface,
like the toolbar or the context menu.
NOTE!
16 / 24
Please refer to the Online Help for more information.
19.5.2 Precautions and Limitations

Do not export or import very large amounts of aspect objects at one and the same
time. It is very time consuming and as the Import/Export tool loads the system
significantly, you should avoid doing this for longer time periods.
Drag and drop is only used for exporting data. Dragging an object or aspect from the
Import/Export Tool to Plant Explorer is not the same as doing an Import/Export. It
will only make a copy of the object or aspect.
NOTE!
It will only make a copy of the object or aspect.

Creating new GUIDs
19.5.3 How to Export Data

Objects and aspects can be added to an export archive by dragging from the
Engineering Workplace into the Import/Export tool.
1. Drag an item and a new Add window appears which consists of three parts.
Include dependencies means objects and aspects from other structures will be
included in the archive as well.
For example, the Alarm List is dependent on the Alarm List Configuration aspect.
When an alarm list is exported, it is important that the Alarm List Configuration is
included. Otherwise the Alarm List aspect will not work correctly when imported
later on.
Include children includes the children of the object you have dragged into the
import/export tool.
The Overwrite existing data frame sets how the tools should react when data
already exists when performing an import or export.
17 / 24
2. With the advanced selection type aspects can be filtered.
3. When the settings are complete press Finish and the following progress window
appears.
4. Click Save as to save the file with a new name.
18 / 24
19.5.4 Hints for Exporting Data

It is important that the full path is exported when exporting objects on a lower level in
the hierarchy. Suggested items per structure are shown below:
Aspect System Structure

Only own defined Objects and Aspects
Library Structure
Only own defined Objects and Aspects
Object Type Structure

Only own defined Objects and Aspects (one file per library)
Control Structure
Control Network Object with no children
Control Project with no children
Each Application (one file per application / export all)
Functional Structure
One file per functional area
Location Structure
One file per Location area
Workplace Structure
Own defined workplaces
19.5.5 How to Import Data

Be extremely careful when importing objects and aspects into a running system.
Overwriting running objects with incorrect versions could cause unexpected results.
1. Click Open to open an archive file with the extension .afw.
19 / 24
2. You can import single objects or aspects.
You can as well import the complete archive by selecting Import All.
3. Select the system to which the import will be made.
20 / 24
4. Define the Import Settings.
If the Include Dependencies box is checked, the tool will import the selected
items in dependency order. If the Include Children box is checked the application
will import the selected objects children.
These boxes are enabled only if an object is selected when making an import. If
Import All is selected at the import, the items will always be imported in
dependency order.
5. Press Finish to start the import.
21 / 24
19.5.6 How to Create a Difference Report

Before import the file, we could check the difference between the file that is going to
be imported and the current system.
The dialog compares the current archive with other archives or the current system.
1. The dialog is launched from the View Menu. The Differences dialog is also
available from the context menu of both aspects and objects.
2. Select the target system/archive and the source system/archive.
3. The difference report is shown in a separate window.
22 / 24
19.5.7 Dependencies
The Import/Export function is dependency aware. This means that aspects which
require another object to exist will be exported together in the export file with the
objects upon which it is dependent.
For example, if your Control Structure contains a user-defined custom object (lets say
youve created an object type OPC Analog in the Object Type Structure) and you
export the object, the object type will be exported automatically as well (unless this
feature has been turned off in the tool options).
To view dependencies for an aspect, select the aspect and choose the dependent
aspects by a simple right-mouse click. Alternatively click the Dependencies button
in the tool bar.
Note that if the dependency is related to a system extension, then the dependency is
noted in the export file, but the dependency object is not exported since it is assumed
that it already exists as part of loading the extension into the system.
During an import, the imported file might be dependent on a specific version of the
System, a System Extension or a Library. In this case, it is necessary to resolve the
dependencies by installing them - before continuing the import.
23 / 24
19.5.8 Resolving Errors

While importing, there might be situations where a decision has to be made for the
import to be able to continue. One common situation is when the parent of the object
thats being imported, does not exist in the system.
In such a case the following dialog will be presented.
In the example above an object named B has been marked for an import, but the
parent of B (named A) does not exist in the system.
Another example below may be if an object already exists in the system, and the same
object has been marked for an import. In this case it needs to be resolved with a
decision to replace the object or aspect, skip the import for that object or aspect and
then continue with the rest of the import.
NOTE!
24 / 24
Every decision made is logged and visible in the message

window.

CH112-19 Backup and Restore - RevB

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

CH112-19 Backup and Restore - RevB

Enviado por

Direitos autorais:

Formatos disponíveis

800xA Minerals Training

Chapter 19 Backup and Restore