Section 11
Back Up and Restore
Introduction
This section provides information on how to back up and restore system data for the purpose of an upgrade. These databases should be part of the maintenance plan and scheduled to be backed up automatically at a convenient time interval but it can be manually backed up. This data should be saved to avoid loss of data due to workstation problems and to be able to use the same data after a software upgrade.
Backup Procedures
Configuration server workstations contain all the Operate IT system configuration data and backing them will preserve the data. Histo-rian server workstations must also be backed up to prevent the loss of collected data that was not yet been saved. The databases can be backed up while the workstation on offline or online (with the follow-ing restrictions).
Restrictions • Do not use the CREATE DATABASE or ALTER DATABASE
state-ments during backup operations.
• Do not create indexes during backup operations.
• Do not perform any non-logged operations (bulk loading of data,
SELECT...INTO statement, WRITETEXT statement, UPDATETEXT
statement, etc.) during backup operations.
• Adhere to standard SQL server naming conventions when
nam-ing databases.
Configuration Data The SQL server configuration database contains all the configura-tion data. In addiconfigura-tion to the configuraconfigura-tion database, other files must also be saved in order to have a complete set of information. To com-pletely back up the configuration data of a configuration server manually:
1. Open the SQL server enterprise manager.
Backup Procedures
3. Expand the databases folder.
4. Right-click the ConfigServer database.
5. Select All Tasks > Backup Database from the pop-up menu. 6. Select ConfigServer in the database field of the general tab of the SQL server backup dialog box (Fig. 11-1).
7. Enable Database - complete as the backup type.
8. Specify a destination to receive the backup information. 9. Enable Verify backup upon completion on the options tab (Fig.
11-2).
10. Complete any other section of the general and options tabs deemed necessary.
TC02706A
Backup Procedures
11. Click OK.
12. After the backup operation completes, save the contents of the following directories to a safe storage media that will not be affected by workstation hardware failures.
• \Maestro NT\Reports\Templates. • \Conductor\lib\models\graphics. • \Conductor\lib\models\submodels. • \Conductor\lib\models\config\graphics. • \Conductor\lib\models\config\submodels. • \Symphony\default\Machine. • \Symphony\<language> Machine. • \Symphony\default\User. • \Symphony\<language>\User. • \Symphony\default\Project. TC02707A
Restore Procedures
• \Symphony\<language>\Project. • \Symphony\default\AddOns
13. Click Cancel to exit the backup procedure.
Restore Procedures
The following procedure describes how to restore backed up infor-mation after an update.
NOTE: This procedure restores configuration and historian data. Skip the steps that
do not apply to this workstation.
To restore backed up information:
1. Open the SQL server enterprise manager.
2. Expand the SQL server group that represents the configuration server workstation.
3. Right-click Databases.
4. Select New Database from the pop-up menu.
5. Enter a name (a new name) for the database that will receive the stored configserver data and click OK.
6. Right-click the new database.
7. Select All Tasks > Restore Database from the pop-up menu. 8. Select ConfigServer in the show backups of database field of the general tab of the SQL server backup dialog box (Fig. 11-3).
9. Select the restore type. Enable Database when restoring from a backup of this actual database. Enable From device when restoring from a backup file unknown to this workstation.
10. If database restore was enabled, select the appropriate backup to restore from and verify the restore from path is correct.
11. If from device restore was enabled: a. Select Devices.
b. Choose the backup device containing the backup information.
Restore Procedures
d. Verify Restore backup set - complete is enabled.
e. On the options tab, verify the original file name field reflects the present location of the backup information.
f. Verify the restore as field indicates the new database.
12. Enable Force restore over existing database and leave database
operational on the options tab (Fig. 11-4) and click OK.
13. Select Program Files > ABB Automation > Configuration >
Config-uration Upgrade Manager from the Windows NT start menu.
14. Click Next in the migration wizard opening dialog box. 15. Verify Upgrade a Maestro 3.1 or Operate IT Configuration is enabled and click Next.
16. Specify that both the source and destination databases are on this workstation (in the select a migration scenario dialog box) and click Next.
TC02708B
Restore Procedures
17. Enter the names of the source and destination databases in the appropriate fields of the migrate local dialog box and click Next. 18. Click Finish. A message window will show the progress of the migration.
19. After the migration operations are complete, open the Windows NT task manager and verify that SQL server is using 100 percent of the CPU assets for no more than 10 seconds. If 100 percent of the CPU assets are used for more than 10 seconds, stop and restart the SQL server application.
20. Restore the contents of the following directories from the safe storage media but do not overwrite existing read-only files.
• \Maestro NT\Reports\Templates. • \Conductor\lib\models\graphics. • \Conductor\lib\models\submodels. • \Conductor\lib\models\config\graphics. • \Conductor\lib\models\config\submodels. TC02710A
Restore Procedures • \Symphony\default\Machine. • \Symphony\<language> Machine. • \Symphony\default\User. • \Symphony\<language>\User. • \Symphony\default\Project. • \Symphony\<language>\Project. • \Symphony\default\AddOns
21. Open the SQL server enterprise manager. 22. Expand the SQL server group as follows:
configserver_workstation_name > Replication Monitor > Agents >
Snapshot Agents
23. Verify the status of ConfigServer_Mirror and ConfigServer_RTDS is Succeeded. Do not proceed until this status is achieved.
24. Restart the workstation.
25. Open the SQL server enterprise manager.
