Académique Documents
Professionnel Documents
Culture Documents
Release 400
Document
Release
Issue
Date
400
4.0
January, 2011
Disclaimer
This document contains Honeywell proprietary information. Information contained
herein is to be used solely for the purpose submitted, and no part of this document or
its contents shall be reproduced, published, or disclosed to a third party without the
express permission of Honeywell International Srl..
While this information is presented in good faith and believed to be accurate,
Honeywell disclaims the implied warranties of merchantability and fitness for a
purpose and makes no express warranties except as may be stated in its written
agreement with and for its customer.
In no event is Honeywell liable to anyone for any direct, special, or consequential
damages. The information and specifications in this document are subject to change
without notice.
Copyright 2011 - Honeywell International Srl.
www.honeywell.com
Contents
About this guide ................................................................................................................. 7
Before you begin ................................................................................................................ 9
Experion system migration .......................................................................................................... 10
Migration applications and tools .................................................................................................. 11
About Experion Migration Storage Node (EMSN) .......................................................... 11
Migration tool ................................................................................................................... 13
Migration Application ...................................................................................................... 13
Migration planning ....................................................................................................................... 14
Develop a migration plan ................................................................................................. 14
Develop a migration timetable ......................................................................................... 14
Review hardware upgrades .............................................................................................. 15
Review software requirements ......................................................................................... 15
EMSN space requirements ............................................................................................... 15
Considerations for Local Windows groups and local user accounts ................................ 16
Migrating other Honeywell products and applications .................................................... 17
Migrating non-Experion third-party applications ............................................................ 18
CONTENTS
www.honeywell.com
CONTENTS
CONTENTS
www.honeywell.com
Description
Base release
Experion Migration Storage A location used to store the data (databases, system
Node (EMSN)
configuration, operating system preferences, and so on)
when migrating an Experion platform. For setting up an
EMSN, a node in the same network, other than the one which
is being migrated, is used.
Installation application
Migration Application
System migration
Term
Description
Migration Tool
www.honeywell.com
10
www.honeywell.com
There are several options that users can perform to manually work around this
problem, with option 3 being the preferred method:
11
1. If the machine is local to the system, (both computers operating within the same
network).
a. Use normal UNC.
b. For security (account and password), create a local account (and password)
on the domain system that will match the account used to perform the
migration on the node being migrated.
Add this account to the Share and File Permissions on the EMSN.
The account entered should be the Account Name, and the associated
password. Or, you can specify an account on the EMSN by entering
EMSNHostName\Account.
2. If the machine is not local to the system, (computers must communicate across a
router).
a. Define the server UNC path in the following format: \\ESMN Host IP
Address\<<EMSN ShareName>> For example: \\192.168.0.1\ESMN
b. For security (account and password), create a local account (and password)
on the domain system that matches the account used to perform the migration
on the node being migrated.
Add this account to the Share and File Permissions on the EMSN.
3. All Cases:
A reconnection failure may occur during migration, (after the hardware platform
upgrade and/or Operating System install).
a. Cancel migration.
b. Enter the DNS, WINS, and other information into the IP Address
configuration of each network card. (TCP/IP properties.)
c. Add system back into the domain. (Reboot of system is required.)
d. Restart migration by starting Setup.exe on the installation media or clicking
Install/Migrate link on the Installer page.
12
www.honeywell.com
Migration tool
Experion Vista R301 and HS R301 migration is performed using the migration tool.
The migration tool saves the server data before migration. The server data includes
the Quick Builder Project, custom displays, groups, trends, recipes, reports, history
archives, and other configuration data. The tool is available at Server-Client
\Server_Migration_Tool folder in the installation media.
Migration Application
The Migration Application is a software application that coordinates the migration
of system software to the latest release for servers and clients. The application is run
on a server/client to be migrated and safely handles system database and
configuration information so that it can be reloaded to the server after the new
release system software is installed. It also allows for hardware and Operating
System upgrades during the migration process.
13
Migration planning
Preparation for system migration requires careful planning and should begin well in
advance. A successful migration requires coordination and cooperation among
various departments and plant personnel.
Develop a comprehensive migration plan that addresses the considerations
described in the following sections. A plan will also provide information on what to
expect in the migration process and will help the plant personnel to be alert.
This section provides information about preliminary planning, considerations, and
tasks that are essential for a successful system migration.
14
Migration Task
Estimated Time
Overall planning
12 days
8 hours
OS reinstallation
www.honeywell.com
Migration Task
Estimated Time
34 hours each
12 hours each
To determine Total space (T), right-click Drive C: and click Properties. The
used space is displayed in the dialog box that appears.
The Base size in is the estimate for the Experion software installed in the server/
client node, minus Experion data and database files stored on the node.
Options (O) include third-party applications, although the applications are not
saved or migrated forward during migration.
If you plan to use the same EMSN as storage for other node migrations, you must
consider the additional disk space needed. Space on the EMSN that was used for
15
prior system migrations can be recovered. Identify a system (computer name) in the
EMSN file structure that has completed migration and delete all folders and data
located under the system name to free up space on the EMSN for future migrations.
Table 1: EMSN estimated space
Node Type
Total space
(T)
Base size
(B)
Server
8 GB
+ Options
8.7
Flex Station
9.6 GB
3 GB
12.6
Custom local user groups and custom local user accounts must be saved or
documented in order to restore them after the migration, if needed. You must capture
the specific configurations and settings for these groups and accounts, so that they
can be restored. Any user specific files/folders and their associated Access Control
Lists (ACLs) settings and any user-defined security policies that are not created
during the Experion installation must be saved, so that they can be loaded to the
migrated system.
Note that Experion standard local groups, user accounts and policies are saved and
restored to the system by Experion Migration.
The R400 Experion standard local groups include the following:
16
Local Engineers
Local Supervisors
Local Operators
www.honeywell.com
Local Servers (which in R400 limits the account for use by services/servers only)
LocalComServer
mngr
Attention
Both the Experion standard local accounts are used only by services/servers. They are
not allowed to be used interactively.
Customized system components and display files must be manually saved since
they are not migrated and restored in the new release. For example:
Point detail displays
Customized Faceplates and Customized displays
Custom Station menu configurations (*.stb files)
*.css files
Safety Manager - If you have Experion systems with Safety Manager, consider
the following before migration:
Check if the new Windows platform used on a migrated Safety Station (the
station running Safety Builder Safety Manager's Safety Station software)
is supported by the release of Safety Builder you have installed. For more
information refer to the Safety Manager Software Reference or the Release
Notes of Safety Manager installed in the system.
17
Attention
Safety Builder is not recommended on Experion server/station nodes.
Are the third-party applications currently operating with the Experion system
compatible with the new release Operating System requirements?
18
www.honeywell.com
You have read the Experion HS Release Notes which contain the last-minute
information that was not included in the standard documents. You must read this
document to find out any migration related information that is applicable to the
system you are migrating.
You have read the migration planning information for information related to
your system and the planned migration.
Related topics
Migration considerations on page 20
Getting the latest software and documentation updates on page 22
Time synchronization during migration on page 23
HMIWeb Display Builder and HMIWeb custom displays on page 24
Restoring Excel data exchange on page 26
Considerations for canceling the migration on page 27
19
Migration considerations
Attention
The following sections contain important information that you should consider before
you begin a migration. The information is arranged by system function or feature and
describes conditions where data may be lost through the migration process, if
precautions are not taken or procedures are not followed. Where possible, workarounds
are provided to help safeguard and restore data.
Therefore, if your Experion system contains certain configurations of system
components or uses these features, you must read the related topics of interest to
determine if the information is relevant to your system or situation. If so, take
precautions to backup your data files and follow any required workarounds.
Description
Microsoft Office
Faceplate displays
MasterLogic
The MasterLogic interface is now included as standard interface in the
controller interface Experion HS R400 installation.
20
Enterprise Model
Windows user
security
configuration
Any custom local user security groups, local user accounts or local
security policies must be recreated after migration.
www.honeywell.com
Item
Description
Event history
The recent online events are retained during the migration, but the
SQL event history are lost. If you want to generate the Alarm and
Event reports, save this information prior to the migration.
Custom displays
System displays
Operator security
Station menus
Station
If you have changed the station.ini file, the changes must be reapplied
configuration file .. after the migration.
\Windows
\station.ini
Station setup file .. The new default Station setup file is configured as static Station 1.
\Station\Default.stn The Station 1 configuration settings must be reapplied after the
migration.
System acronyms
Scan periods
Allen Bradley
RSLinx
Quick Builder
projects
When opening an old project file with the new version of Quick
Builder, you will be prompted to migrate the project file to the new
format.
Localization
21
22
Click Experion HS to access the links that contain the latest notifications,
software and documentation updates.
www.honeywell.com
Additionally, check the time zone setting on other servers in the system, and make
the changes so that all the nodes are set to the same time. .
Experion software includes support for the latest Daylight Savings Time fixes.
However, due to recent global time zone adjustments, it may be necessary to reset
the time zone settings during some migration scenarios. You need to verify the time
zone and set the time (if necessary) after the software upgrade, but before reestablishing server redundancy, and all other nodes.
23
You must back up any file that contains user-defined information, (such as
customized displays) before starting the migration. These files may not be migrated
as part of the migration process and need to be reinstalled after migration.
Any custom display files may be stored in a user-defined location and may not be
migrated forward. Hence you must manually save these files before migration and
then restore it after migration. For example, you must back up and save the following
files before starting migration.
Faceplates
*.css files
*.htm files
The references to server data in the custom displays are limited to point
parameters and data in user tables.
In Display Builder when you save a display (.dsp file), you can specify the display
release for the file. This allows you to save the display in an old format which would
allow you to use the display file with an older release of Station. Once a display file
has been updated or saved for a newer release, it cannot be displayed on a Station
operating on an older release.
24
www.honeywell.com
you migrate a node to the new release, you must use either HMIWeb Display Builder
or the Bulk Display Migration tool to migrate the display files before you can display
the custom or user-defined HMIWeb displays (.htm files) in Station. For example,
when a display file (created in an older release) is opened using a new release of
HMIWeb Display Builder, the file is automatically converted to the new display
format by saving the file in the new format. If you want to update the HMIWeb
displays in bulk, you can use the Bulk Display Migration tool
(bulkdisplaymigrator.exe).
25
26
www.honeywell.com
27
28
www.honeywell.com
Attention
When migrating redundant server systems, you must migrate ServerB first. After
completing ServerB migration, verify if the migration is successful and then
proceed with the migration of rest of the nodes.
Ensure you have created a disk image of ServerB before you stop it. If you want to
rollback the migration, a disk image can make the process easier. If you restore
ServerB from a disk image and ServerB is part of a domain, you need to remove the
computer from the Windows domain and then add again and reestablish the trust
relationship.
All the nodes (servers and stations) must be migrated to the target release before the
system is restarted and nodes start communicating again.
When migrating non-redundant server systems, perform all the migration tasks on
the non-redundant server.
Related topics
Complete the pre-migration tasks on page 30
Migrating ServerB/non-redundant server on page 38
Migrating Flex Stations on page 43
This chapter describes the tasks that you need to perform to complete the
migration of Flex Stations.
Migrating ServerA on page 45
Post migration tasks on page 50
Troubleshooting Migration on page 54
29
Considerations
If you are unable to verify the passwords, you must change the password on each
node. Use the Password utility to change Experion Windows account passwords
across the Experion system.
To change the Experion Windows account passwords
30
Click Allow.
Select mngr.
www.honeywell.com
Type the new password in the Password and Confirm Password dialog boxes
and then click OK.
Click Done.
Click OK.
Attention
If the Password utility warns you that an existing Windows account is no longer
required, you must delete these Windows accounts, unless another application,
other than Experion, uses these Windows accounts.
The server data must be saved in a computer on the same network as the server. If
this is not possible, the data must be saved to the local hard disk before copying it
to a removable media.
31
Prerequisites
Install DotNet 3.5 SP1 before proceeding with installation of the migration tool.
1. In the Experion Application Software DVD, navigate to \Packages
\Microsoft\DotNet3.5 directory.
2. Double-click dotnetfx35SP1.exe.
3. Follow the instructions on-screen to complete the installation.
4. Restart the computer.
Ensure you clear Launch the program check box before you click Finish.
Migration Tool.msi
file.
32
Estimate the free disk space required to save the server data, by adding 400MB to
the size of the history archives.
If the estimated size is greater than the free disk space on the server (or the
destination computer), then copy the history archive files to a removable media
and delete these files from the server before proceeding further.
www.honeywell.com
Print the contents of the Command Prompt window or record these settings.
In addition, record your mapped network drives, so that they can be restored after
the migration.
Open Station.
Verify that there are no critical alarms or failures. If there are any critical alarms
of failures, resolve the issue and proceed with migration.
33
On the file replication page, clear all the Send check boxes.
Attention
While reinstalling the OS, review each custom file replication configuration on the
computer which uses custom file replication to send files, and note the following:
The share name and path used for each custom file replication on each Experion
server involved in the migration.
The computer name, share name, and path on every computer listed as a
specific computer (PC) within those custom file replications, if they are
different from the server's share name and path for the same replication.
Close Station.
Create a local account on the Windows domain, and assign full control
permissions to the shared folder for this user.
34
In the Share name box, type the name of the share as Backup.
If you have created a local account on the Windows domain to access this shared
folder, do the following:
a
Click Permissions.
Click Add to locate the local account created on the Windows domain, and
then click OK.
www.honeywell.com
In the Group or user names list, select the account name that you have
added.
Click OK.
Open Windows Explorer and choose Tools > Disconnect Network Drive.
If there is a network connection listed as drive Z: then select this drive and click
OK to disconnect the network drive. This procedure maps the shared directory as
drive Z: the backup process will fail if there is another directory already mapped
as drive Z.
Type hscserver
Choose Start > Settings > Control Panel > Administrative Tools > Services to
display the Services window.
Click Stop and then Yes to stop both the browser services.
/unload /y
10 Click Next.
11 Enter the destination computer name in the EMSN Machine Name box and the
shared directory name (Backup) in the EMSN Share box and click Next.
The Migration Tool Phase 1 dialog box displays the size of the data to be backed
up to the shared directory.
35
12 Compare this size with the disk space requirement determined previously and if
for an account that has administrator rights on the destination computer, and then
click OK.
The migration tool tests the connection to the shared directory and start the file
copy operations.
Attention
There is no indication of the progress during the file copying. Wait for the final
dialog box to be displayed and then click Exit. If this step fails, click Exit and check
the permissions on the shared (Backup) directory. The permissions must be set to
allow Everybody Full Control. Repeat this procedure from Step 8.
14 Using Windows Explorer navigate to C:\Program Files\Honeywell\Experion
PKS\Migrate\Plug-in\HSCServer
directory.
If the log file contains error or failure messages, repeat this procedure from Step
8.
Choose View > System Status > Server Redundancy to open the Server
Redundancy Status display.
Check that the backup server (ServerB) is running and that the servers are
synchronized.
36
www.honeywell.com
Click Continue.
Click Continue.
The Services window appears.
37
38
www.honeywell.com
Open Station.
Click Save to save the changes and close the dialog box.
On the node, choose Start > All Programs > Honeywell Experion PKS >
Server > HMIWeb Display builder .
On the General tab, clear the Save AutoRecover info every minute check box.
Click OK.
39
On the client node, back up all directories that contain the display files.
PKS
\Client\Abstract)
Click Go to run the bulk Display Migration tool on these folders to update the
display files.
Attention
Be sure to enable the autosave option (if desired) after the display files have been
updated.
Obtain the printout or log of the configuration settings recorded before migration
of the server. Refer to the section, Windows network configuration settings.
40
This procedure must be performed after installing the Experion HS R400 server
software.
www.honeywell.com
Attention
Considerations
If the new system has redundant servers, perform this procedure on the primary
server.
Copy the shared folder (Backup) in the EMSN to the C:\ drive on the new server.
Choose Start > All Programs > Honeywell Experion PKS > Server >
Diagnostic Tools > Experion Command Prompt > .
Type the following command at the command prompt using the full path name
from Step 1 and the \data enclosed in quotes.
For example: C:\Backup\Honeywell Experion PKS\Migrate\ServerName
\HSCServer\ServerData\data sysbld -restore path\data -y
/load /y
Using Windows Explorer copy the .TSV files from C:\Backup\ .. \HSCServer
\ServerData\OPCIntegrator to C:\ProgramData\Honeywell\Experion PKS
\Server\Data\OPCIntegrator.
41
PKS
\Server\data
When you open Configuration Studio for the first time after migration,
the Quick Builder migration wizard is launched to migrate the database file. Do
not click cancel during this migration process and allow the wizard to complete
its task.
See the Quick Builder Guide in Knowledge Builder for more information.
42
www.honeywell.com
43
Obtain the printout or log of the configuration settings recorded before migration
of the server. Refer to the section, Windows network configuration settings.
44
Recreated the custom local user security groups, local user accounts or local
security policies, if any.
Required modifications are made to the custom displays that are migrated.
www.honeywell.com
Migrating ServerA
Migrate ServerA only when you are satisfied with the operation of the migrated
ServerB and clients. Once ServerA is migrated, the two servers (ServerB and
ServerA) are synchronized and operate as redundant servers running on the new
release software. The following sections describes the tasks that you need to
perform, and the order in which these tasks must be performed.
45
46
Open Station.
Click Save to save the changes and close the dialog box.
www.honeywell.com
Obtain the printout or log of the configuration settings recorded before migration
of the server. Refer to the section, Windows network configuration settings.
On the Server Redundancy Status display on the primary server, the LEDs in
the Link Status group should change from red to green and indicate the
following:
Running
Link n (LINK0n)
47
On the display page, under the General heading, click File Replication.
Close Station.
48
www.honeywell.com
PKS\server\Data
Review the file and re-apply any backup requests disabled previously by placing
an S at the start of the line.
Refer to the flbkup.def file saved to the remote location before migration and add
any user-defined file backups from this file to the new filbkup.def file.
In the asset model tree, right-click on the parent for the new asset and click Add
Asset.
or
In the alarm group model tree, right-click on the parent for the new alarm group
and click Add Alarm Group.
The Enterprise Assets or Alarm Groups dialog box appears.
Type the name of the asset or alarm group and click OK.
The new asset/alarm group appears as a child of the parent asset/alarm group.
49
Choose View > System Status > Server Redundancy to open the Server
Redundancy Status display.
Option
Description
50
www.honeywell.com
Option
Description
7. After a few minutes, click Synchronize, and
then Yes to resynchronize the databases. (If
you start synchronization immediately after
the failover, an error might occur.)
Insert the Experion installation media in the disk drive of the domain controller
node.
Using Windows Explorer, browse to \Packages\dcsecurity folder and doubleclick Honeywell security model domain controller.msi.
Click Finish.
Perform steps 5 through 9 in the Experion nodes that are added to the domain.
Choose Start > All Programs > Accessories and right-click Command
Prompt and click Run as an Administrator.
Click OK in the confirmation dialog box and follow the instructions on-screen to
complete the configuration.
Select Experion Security Policy in the list of installed programs and click
Uninstall.
51
Attention
Honeywell-provided Group Policy Objects (GPOs) are over-written when the new
domain controller security package is installed. Therefore, any customizations
made to the GPOs must be recreated once the new domain security package is
installed. Users should create their own GPOs for settings they want to customize,
rather than modifying the Honeywell-provided GPOs.
The procedure to add a node to a Windows domain is applicable only if you want
your computer to be assigned to a Windows domain.
Refer to the Experion Software Installation User's guide for more information on
adding a node to a Windows domain.
52
www.honeywell.com
53
Troubleshooting Migration
Restarting the migration application
If you find that migration application must be stopped to correct an error, the
migration application can be restarted and resumed from the last operation. In most
cases, nothing is lost and migration resumes from the point where it stopped. To
restart the migration application, eject the installation media from the disk drive and
then re-insert it. The migration application should launch and resume from the last
operation completed.
Attention
If you encounter errors while using the migration tool, acknowledge the errors. After
you acknowledge the error, the system restarts. You need to restart the migration tool to
continue with the migration.
Choose Start > All Programs > Honeywell Experion PKS > Server >
Diagnostic Tools > Experion Command Prompt.
Files\Honeywell\Experion PKS\Server
Search and replace the old computer name with the new computer name to
update the following entries:
<BlockName> ComputerName </BlockName>
<EntityName> ComputerName </EntityName>
<ParamName> NODENAME </ParamName>
<ParamValue> ComputerName </ParamValue>
54
www.honeywell.com
Attention
Note: If this node is a part of the redundant pair, then the new computer name is its
base name without the suffix A or B.
6
This setting must be OFF for a non-redundant server and ON for a redundant
server.
7
55
56
www.honeywell.com