Chapter 25 Backup and Restore

System 800xA Training Chapter 25 Backup and Restore TABLE OF CONTENTS Chapter 25 Backup and Restore... 1 25.1 General Information... 2 25.1.1 Objectives... 2 25.1.2 Legend... 2 25.1.3 Reference Documentation... 2 25.2 Backup Methods... 3 25.2.1 Cloning / Imaging... 3 25.2.2 Windows Backup... 3 25.2.3 800xA System Backup / Restore... 3 25.2.4 Import/Export... 4 25.2.5 Disaster Recovery... 4 25.3 800xA System Backup... 5 25.3.1 Backup Procedure... 5 25.3.2 How to Configure the Backup Service... 5 25.3.3 How to Create a Backup Definition... 7 25.3.4 How to Run a Backup... 8 25.3.5 Backup Basic History Data... 9 25.4 800xA System Restore... 10 25.4.1 Preparation Steps... 10 25.4.2 How to Restore a System... 11 25.4.3 Restore Basic History Data... 14 25.5 Import / Export... 15 25.5.1 Introduction... 15 25.5.2 User Interface... 15 25.5.3 Precautions and Limitations... 17 25.5.4 Exporting Data... 17 25.5.5 Hints for Exporting Data... 20 25.5.6 Importing Data... 21 25.5.7 How to Place Aspects when Importing... 25 25.5.8 How to Export / Import Libraries... 28 25.5.9 Creating a Difference Report... 33 25.5.10 Dependencies... 34 25.5.11 Resolving Errors... 35 Chapter 25-1

T315-25 Backup and Restore - RevC 25.1 General Information 25.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 25.1.2 Legend > Indicates when you go from one menu to a sub-menu Italic Indicates object and file names Indicates dialog box buttons, tabs, menus etc. Bold Indicates important topics Indicates start/explanation of student activity 25.1.3 Reference Documentation 3BSE046784 3BSE035980 Industrial IT 800xA System Maintenance Industrial IT 800xA Control and IO Basic Control Software Introduction and Configuration Chapter 25-2

System 800xA Training 25.2 Backup Methods 25.2.1 Cloning / Imaging The backup and restore procedure consists of two different parts Backup of standard Windows system Backup of the System application data 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 computer s 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 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. 25.2.2 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. 25.2.3 800xA System Backup / Restore The 800xA system s Backup/Restore tool is for backing up and restoring the Aspect Directory and historical data. It is not for backing up operating system or 800xA software. Backups can be either full or incremental (incremental backups require an initial full backup). Backups are always made on a running system, but you have to stop the system to perform a restore. 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. NOTE! It is recommended to take the 800xA backup regularly. Information Manager is the appropriate tool to archive historical data. There is also a way to backup basic history data, which is explained later on in this chapter. Chapter 25-3

T315-25 Backup and Restore - RevC 25.2.4 Import/Export The Import/Export tool can be used to save 800xA objects and aspects information one portion at a time. The data is saved as objects and aspects in archive files (.afw) outside of the running Aspect Directory. This tool can be used to transport applications between different 800xA Systems. For example: Import data from scratch Save user defined objects and aspects 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 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 complete system. 25.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. NOTE! More information can be found in the course T305 System Administration and Installation. Chapter 25-4

System 800xA Training 25.3 800xA System 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. All system extensions that are part of the system must be installed and added on the node where the backup will be taken (usually the Primary Aspect Server). NOTE! Do not manually import or edit any information in backup files. 25.3.1 Backup Procedure Follow the recommendations below to make a full 800xA system backup. 1. Create a Backup Definition object and configure the definitions of scope and storage settings. 2. In the Backup Definition aspect, click the Start Backup button. 3. A new Backup object is created when the 800xA 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. 25.3.2 How to Configure the Backup Service The backup service runs on each Aspect 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. Chapter 25-5

T315-25 Backup and Restore - RevC 2. Select the tab Configuration on the Service Provider Definition aspect and check the Service Provider is enabled. 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. Chapter 25-6

System 800xA Training 25.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. 3. Select the Backup Service Provider on the Storage tab. It defines the node on which the backup will be made. The nodes available are those that run a backup service provider. Chapter 25-7

T315-25 Backup and Restore - RevC 25.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 click on Start Backup to start the backup manually. 3. A status window is displayed during the backup and indicates at the end whether the backup was successfully. Chapter 25-8

System 800xA Training 4. A new object is created under the 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. 25.3.5 Backup Basic History Data The procedures are basically the same as for taking a backup of the Aspect Directory. Go to the Maintenance Structure and select the Backup Definition Root object. Create a new Basic Definition object. But this time select External Services as the Backup Type. NOTE! Information Manager is the appropriate tool to archive historical data. Chapter 25-9

T315-25 Backup and Restore - RevC 25.4 800xA System Restore The restore will recreate an equivalent system, after a node failure. It is also a recommended way to transfer data between one version of the system to another during an upgrade. There are several restrictions upon when a backup can be restored a system: The same or a later version of 800xA System and any System Extension that was installed when the backup was taken, need to be installed before the system is being restored. Same System Extensions installed as when the backup was taken. Same configuration on the Domain server as when the backup was taken. 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 it s important to ensure that all old systems have been successfully deleted before adding the node again. 25.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. Chapter 25-10

System 800xA Training 25.4.2 How to Restore a System 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. Chapter 25-11

T315-25 Backup and Restore - RevC 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. Chapter 25-12

System 800xA Training 6. Select a node on the Primary or Secondary nodes area in the Node Configuration dialogs. Click Next to continue. 800xA in general supports restoring the configuration to a node other than the one it was backed up. To change the node name, right click on the name in the Nodes in restored system column and change it. 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. Chapter 25-13

T315-25 Backup and Restore - RevC 25.4.3 Restore Basic History Data Go to the Maintenance Structure and select the Backup object under the Backups, Backup Root object. Select the Backup Info aspect, select the Restore tab and click Apply. The Restore button will be enabled any you can then start the restore. Chapter 25-14

System 800xA Training 25.5 Import / Export 25.5.1 Introduction The Import/Export tool allows objects to be stored and restored with their aspects. The data is saved 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. 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, then the tool can be used to import them back into the system again. 25.5.2 User Interface You can call the Import/Export tool in two ways: Click on the icon in the Engineering Workplace Select Start > Programs > ABB Industrial IT 800xA > System > Import Export The user interface is designed to resemble the Engineering Workplace as much as possible. NOTE! The Import/Export tool has two views; Overview and Structured View. Please refer to the Online Help for more information. Chapter 25-15

T315-25 Backup and Restore - RevC The Overview view presents the entity and entity extensions in the archive. This view gives a simplified overview of items such as libraries and control applications. In the case where the archive does not contain any entities this view is disabled. Entity Area Object Browser Aspect List Info Area The view Structured View presents all objects and aspects arranged in structures. The aspects of the selected object are shown in the aspect list. The optional Info Area at the bottom shows the dependencies that are required in order to import the objects and aspects into a system or messages generated during export/import. Info Area Object Browser Aspect List Chapter 25-16

System 800xA Training 25.5.3 Precautions and Limitations 1. 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. 2. The export is completed only after saving data on the archive file (the tool holds only references to Aspect Directory). NOTE! Always complete exporting by File > Save. 3. 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. NOTE! Dragging to Plant Explorer only makes a copy of the object or aspect (new GUID will be created). 4. Reservation state of objects and aspects influences the import. NOTE! Reservation of an object or aspect by another user prevents the import (overwriting) 25.5.4 Exporting Data Exporting objects and aspects are done by drag and drop from the Engineering Workplace into the Import/Export tool. Examples: Sources of export are the Control Structure and Functional Structure After dragging and dropping the Add Items dialog appears as shown below in a few different use cases. The dialog shows a summary of what was dropped and in what context. Chapter 25-17

T315-25 Backup and Restore - RevC Case 1: Top level object Sxx_Control_Network is dropped: Case 2: Lower level object Applications is dropped: Case 3: Only one aspect Graphic Display is dropped: It is also possible include or exclude dependencies, children or extensions. Children is only available when an object or an entity has been dropped. Extensions is only available when an entity has been dropped. 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. Chapter 25-18

System 800xA Training Pressing the OK button starts the pre-export. The messages (if any) in the lower part of the dialog window are categorized in Errors, Warnings and Information. After clicking the Done button (or using the Close when finished checkbox) the main window shows the objects and aspects which are now ready to export finally. Case 2 (case 1 is similar): Lower level object Applications was dropped: Case 3: Only one aspect Graphic Display was dropped: Chapter 25-19

T315-25 Backup and Restore - RevC Select File > Save from the menu to write the data into an archive file (.afw). Check the messages if there are any, then press Done to close the dialog. 25.5.5 Hints for Exporting Data When saving objects and aspects, only export data which has been added as part of the project. The following list shows some typical data that need to be exported. Library Structure Only your own defined objects and aspects e.g. History Log Templates, Alarm & Event Configurations Object Type Structure Only your own defined libraries (one file per library) Control Structure Control Network object with no children Control Project object with no children Each application (one file per application / export all) Controllers object with children Functional Structure One file per Functional area Location Structure One file per Location area Workplace Structure Only your own defined workplaces User Structure Only your own defined / modified objects and aspects e.g. User Groups, Workplace Profile Values Admin Structure Only the modified aspects on your Domain object e.g. Logover Settings, Audit Trail Configuration Aspect System Structure Only your own defined objects and aspects e.g. User Role Bindings and Permissions NOTE! Please refer to section Import and Export Alternatives in the manual Basic Control Software and to section Additional Information in the manual Maintenance. Chapter 25-20

System 800xA Training 25.5.6 Importing Data Be extremely careful when importing objects and aspects into a running system. Overwriting running objects with incorrect versions could cause unexpected results. Click Open to open and start loading an archive file of type afw: Click the Done button (or use the Close when finished checkbox) to close the dialog. Chapter 25-21

T315-25 Backup and Restore - RevC There are basically 3 ways to select the items to be imported. 1) Import All: The Import All button starts the import of the entire archive. 2) Import a single aspect or an object with the related children: Click right on the item to be imported and select Import Chapter 25-22

System 800xA Training 3) Best praxis for the advanced users: Remove and Import All A bigger archive like a part of the project can be imported this way into the system. Select the unwanted objects, aspects, dependencies (hold down the <Ctrl> key and click left). Click right on selection and use Remove. After removing use Import All button to start the import. Chapter 25-23

T315-25 Backup and Restore - RevC A dialog window with two folders will appear, showing some summary information. Several options are given when selecting Import Options. Include Dependencies enables the import of object or aspect related dependencies (if they were included at the export). This option has to be used with caution in order to avoid overwriting objects or aspects which belongs to system or are newer than the ones in import file. NOTE! Normally only Include Children should be activated. Click the Finish button to continue the started the import. Click the Done button (or use the Close when finished checkbox). Chapter 25-24

System 800xA Training 25.5.7 How to Place Aspects when Importing The following examples assume that two graphic display aspects need to be imported. They are place on the Sxx_TempStorage1 object in the original export file. Since Sxx_TempStorage1 is not available in the new system, we want to place them on a different object Sxx_TempStorage2 when doing the import. 1. Open the afw file with two Graphic Display aspects and select Import Chapter 25-25

T315-25 Backup and Restore - RevC 2. Deselect Include Dependencies and press Finish to continue: 3. Click Yes to place the object manually: 4. Click right and select New Insertion Point : Chapter 25-26

System 800xA Training 5. Select an object (insertion point) and click OK. 6. Click OK to place the aspect on the new object: 7. Press Done as soon as the import succeeded. Chapter 25-27

T315-25 Backup and Restore - RevC The end result is like a copy (new GUI was created). In case of a graphic display, it needs to be deployed. 25.5.8 How to Export / Import Libraries This example shows the export/import of a library from System A to a second System B. The control module type StartStopCtrl is modified in System B and then the whole library imported back to the original System A. NOTE! The library state is Open and the version will not be changed. Chapter 25-28

System 800xA Training 1. Select the library in the Object Type Structure and click Export Library. Give a file name and save it as afw file. 2. Use the Import/Export Tool to import the library into the second System B with Import All. Chapter 25-29

T315-25 Backup and Restore - RevC 3. Select the following Import options: 4. Now modify the just imported library in System B. 5. Exported the modified library out of System B. Chapter 25-30

System 800xA Training 6. Import the modified library back to the first System A with Import All. 7. Click Yes on the following messages to replace the existing library. Chapter 25-31

T315-25 Backup and Restore - RevC 8. Press Done to close the import dialog. 9. The application shows some errors: select Check to update the instances. Finally the adapted application is ready. Chapter 25-32

System 800xA Training 25.5.9 Creating a Difference Report Before importing an afw file, we could check the difference between the file that is going to be imported and the current system. It is also possible to compare two different archive (afw) files. Press the Differences button or select it from the context menu for a certain object or aspect. Select the target system/archive and the source system/archive. The difference report is shown in a separate window. Chapter 25-33

T315-25 Backup and Restore - RevC 25.5.10 Dependencies The Import/Export tool is dependency aware and dependencies can be shown using the Dependencies button. For example, if your Control Structure contains a userdefined custom object type and you export the instance, the object type will be exported automatically as well (unless this feature has been turned off). Graphic Display aspect exported without dependencies: Graphic Display aspect exported with dependencies: 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. Chapter 25-34

System 800xA Training 25.5.11 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 that s being imported, does not exist in the system. In such a case the following dialog will be presented, as we have seen earlier. Another example may be if an aspect already exists in the system, and the same aspect has been marked for an import. In this case it needs to be resolved with a decision to replace the aspect, skip the import for that and then continue with the rest of the import. NOTE! Every decision made is logged and visible in the Message window. Chapter 25-35

T315-25 Backup and Restore - RevC Chapter 25-36