System 1 Database Administration User Guide - 156M4815

System 1 Database Administration
User Guide
Bently Nevada Machinery Condition Monitoring 156M4815 Rev. -
User Guide 156M4815 Rev. -
Copyright 2021 Baker Hughes Company. All rights reserved.
Bently Nevada, Orbit Logo and System 1 are registered trademarks of Bently Nevada, a Baker
Hughes Business, in the United States and other countries. The Baker Hughes logo is a trademark
of Baker Hughes Company. All other product and company names are trademarks of their
respective holders. Use of the trademarks does not imply any affiliation with or endorsement by
the respective holders.
Baker Hughes provides this information on an “as is” basis for general information purposes.
Baker Hughes does not make any representation as to the accuracy or completeness of the
information and makes no warranties of any kind, specific, implied or oral, to the fullest extent
permissible by law, including those of merchantability and fitness for a particular purpose or use.
Baker Hughes hereby disclaims any and all liability for any direct, indirect, consequential or
special damages, claims for lost profits, or third party claims arising from the use of the
information, whether a claim is asserted in contract, tort, or otherwise. Baker Hughes reserves the
right to make changes in specifications and features shown herein, or discontinue the product
described at any time without notice or obligation. Contact your Baker Hughes representative
for the most current information.
The information contained in this document is the property of Baker Hughes and its affiliates;
and is subject to change without prior notice. It is being supplied as a service to our customers
and may not be altered or its content repackaged without the express written consent of Baker
Hughes. This product or associated products may be covered by one or more patents. See
Bently.com/legal.
1631 Bently Parkway South, Minden, Nevada USA 89423

Phone: 1.775.782.3611 (US) or Bently.com/support
Bently.com
2/119
Contents
1. Database Manager 5
Failed to fetch data 5
1.1 View Database Description 5
1.2 Review Data Storage Requirements 6
1.3 Manage Database Settings 9
1.4 Back up PostgreSQL Databases 10
1.5 Restore a PostgreSQL Database 12
1.6 Migrate PostgreSQL 9.6 to 11 13
1.7 Move PostgreSQL Database 14
1.8 Move Data Store to a New Server 17
1.9 Upgrade System 1 Database 19
1.10 Grant Database Permissions 22
1.11 Clean Database 33
1.12 Delete Database 34
1.13 Rename Database 35
1.14 Overwrite Configuration Database 37
1.15 Retransmit Replicated Database 40
1.16 Migrate Data 43
Migrate Data from System 1 Classic 44
Migrate Ascent Data to System 1 52
Migrate Proficy Data to PostgreSQL 56
1.17 Manage Server Security 58
1.18 Enable Data Collection 61
1.19 View Data Stores Health 63
1.20 Get Install Base Summary 64
2. Manage Proficy Databases 66
2.1 Change Proficy Machine Name 66
2.2 Move Proficy Database 70
2.3 Database Directory Locations 74
2.4 Restore Databases When Installation Folder Structures Differ 77
2.5 Back Up and Restore Using Acronis 78
2.6 Back Up and Restore Using Windows Server 82
3. Configure Database Replication 87
3.1 Setup and Limitations 93
3.2 Configure Transmitter Database 94
3.3 Configure Receiver Database 95
3.4 Configure Replication Service 98
3.5 Configure Transmitter Database 100
3/119
3.6 Configure Remote File Transfer Service 101

3.7 Create SFTP Connection 101
3.8 Client SFTP Batch File Script 109
3.9 Data Replication Errors 112
3.10 Retransmit Replicated Database 114
4. Backup and Restore Issues 118
4/119
1. Database Manager
Launch the Database Manager
To launch Database Manager:
l In Windows, choose Start Menu > System 1 Database Management.

l In System 1, choose Tools > Database Manager.
When you open a System 1 database, you can use Database Manager to upgrade the database.
Database Manager Warnings / Errors Pane

The Warnings / Errors pane in the Database Manager displays messages about database
health, including but not limited to database wrapping, connection issues, calculation issues,
and validation issues.
When importing System 1 Classic data, you may encounter a warning about storage
availability. This is because System 1 Evo cannot calculate available storage. If you
continue migrating data, data may be wrapped. We recommend you exit migration and
use the Database Manager tool to verify database health. Then continue migration.
Failed to fetch data

To resolve this issue, try these steps:
l Check the version of the selected database. If older than the current release of System 1,
upgrade to the latest version to view database details.
l Check your network connection. The Database Manager may not be able to fetch
database details because of network connection issues.
Troubleshooting the Database Manager

For details, see Database Manager Errors in online help.
1.1 View Database Description

To view details of a database, use System 1 Database Manager.
1. Launch the Database Manager using one of two options:

o Choose Windows Start Menu > System 1 Database Management.
o In System 1, choose Tools > Database Manager.
2. The System 1 Database Manager is displayed.
3. In the General pane, select a server and click Connect.
5/119
4. The Database Manager displays storage details:

o Consumed Size: The total disk space currently used by the database.
o Estimated Size: The estimated disk space necessary to collect data for the current
database configuration.
o Age: The current age of the data in the data store based on the oldest data sample.
o Overall Health: Database health rating. System 1 uses the available space and
space consumed by all databases to determine the health rating of a database.
Possible values are Good, Risk, Wrapping, or Stopped. See View Data Stores Health.
Also see Review Data Storage Requirements.
1.2 Review Data Storage Requirements

Types of Data Stores
Data stores are created depending on the type of database license you purchase.
Fundamental Package
Portable Data Store
The portable data store consists of data from offline devices. This store grows on demand and is
only limited by the disk space available.
Premium and Advanced Packages
Alarm Data Store
Whenever an alarm event is triggered, the high-resolution trend and waveform data is captured.
The alarm store is configured in terms of storage size and the space is reserved. When the
designated space is filled, the data begins to wrap.
Transient Data Store
When a start up/shutdown event is triggered, the high-resolution trend and waveform data is
captured. The transient store is configured in terms of storage size and the space is reserved.
When the designated space is filled, the data begins to wrap.
Short-Term Data Store
The short-term data store can retain up to a minimum of 1-second data for trended variables
and up to a minimum of 10-minute data for spectrum and waveforms over a period of time. No
disk space is reserved upfront, and the data store grows on demand. When storage is no longer
available, the short term data store begins to drop this high-resolution data in 3-days
increments.
Long-Term Data Store
6/119
The long-term data store consists of summary data tiers for trended variables. It also consists of
spectrum and waveform samples based on the configured long term storage rate. No disk
space is reserved upfront, and the data store grows on demand.
Summary Data Tiers for Trended Variables
To simplify data storage in System 1, long-term trend data is summarized into data tiers
designed to preserve the nature of a measurement's curve while enabling appropriate plotting
performance. Summarized data tiers provide the long-term data required for condition
monitoring without requiring excessive hard disk space. Below is a comparison of how long data
is stored in each data tier:
The incoming one-second short-term trend data is evaluated by the data store and
summarized into the tiers by storing each measurement's:
l First-in value and timestamp.

l Minimum value and timestamp.
l Maximum value and timestamp.
l Status for each summary tier, as required.
This method of reducing data is only applied to trended data and is never applied to
alarm or transient data.
This figure is an example of how each sample is categorized for each data tier and bucket:
7/119
When launching a trend plot with a selected time range, System 1 will choose the most
appropriate data tier to provide the highest resolution without exceeding sample plotting limits.
Both min and max values are plotted.
If the selected tier does not contain the desired number of samples, the algorithm continues to
the higher-density tiers. Once data is plotted, you can expose higher density long-term trend,
short-term trend, alarm, and transient data by simply zooming within the plot.
Online and Scanning Data Store Properties

Default properties for online and scanning data stores are:
l Alarm Data Store: 20% of available disk space

l Transient Data Store: 10% of available disk space
l Short-Term Data Store: thirty (30) days of storage
l Long-Term Data Store (static plus waveform): five (5) years of storage
l Highest supported resolution rate of storage:
o Static Data: one second
o Waveform Data: ten minutes
To modify these defaults, configure the state points. See the System 1 Machinery
Management User Guide (document 109M8639).
Verify that the recommended minimum disk space is available at all times while the system is
functioning. For recommended disk space, see the System 1 Datasheet (document 108M5214).
Low Disk Space Data Wrapping
8/119
When available disk space falls below 5 GB + 1% of the total disk space, short term unfiltered trend
data shrinks to six (6) days of storage. For example, this storage limitation is triggered if the
available disk space on a 1000 GB hard disk falls below 15 GB (5 GB + 1% of 1000).
l If disk space is exhausted, new trend data is collected but not stored.
l Freeing up disk space reverts the storage limitation back to the default thirty days of
storage and resume storage of new trend data.
l When the available disk space falls below 5 GB, all data collection reverts.
Troubleshooting Recommendations
If your database begins to wrap data, complete either of the following recommended
troubleshooting actions:
l Free disk space.

l Increase disk space.
l Store data at a slower rate. This is recommended for spectrums and waveforms.
1.3 Manage Database Settings

Configure Storage Settings
To modify storage settings:
1. Open the Database Manager and select the General tab.

2. In the Storage Settings pane, data store settings are displayed. View Data Stores Health is
also displayed.
3. You can modify the default span.
Data Span
Default Span Value Span Range
Stores Units
Short Term
Time 30 days 10 to 90 days
Data
Long Term
Time 5 years 3, 5, 7 and 10 years
Data
20% of available disk space The application calculates

Disk
Alarm Data the available space using the
store If less than 250 GB is available, alarm data
spans.
defaults to 2% of available disk space.
10% of available disk space

start up / The application calculates
Disk If less than 250 GB is available, start up /
Shutdown the available space using the
store shutdown data defaults to 1% of available
Data spans.
disk space
Configure Device Rates

To configure global collection rates for each device group:
9/119
1. Open the Database Manager and select the General tab.

2. The Device Rates pane displays current storage rates for specific device types. The default
storage rates are:
o Trended Variables - Short Term Storage Rate. 1 second. (vbOnline Pro devices have
a default of 30 seconds.)
o Spectrums and Waveforms - Short Term Storage Rate. 10 minutes.
o Spectrums and Waveforms - Long Term Storage Rate. 3 hours.
3. If a device you recently connected to System 1 is not displayed, click Connect. The device
list is updated.
When you modify these device rates, every device of that type is affected, unless you
modified the individual device's storage rate. When you modify the global rate, any
devices you add afterward use the device's default rate.
4. In the Database Manager, choose File > Save. The new storage rates are saved. Changes
take about 10 minutes to propagate.
OPC Server Update and Storage Rates

OPC Servers store only trended variables. Storage rates for spectrums and waveforms are not
available.
The Update Rate property for OPC Servers and OPC Groups as viewed in the General tab of the
Configure workspace's Standard Mode indicates the rate at which current values are updated.
The Trended Variables - Short Term Storage Rate in the General tab of the System 1 Database
Manager indicates how often the data is written to the database. These rates can be different.
Storage Rates for Configured States

To configure storage rates individual states, see the System 1 Machinery Management User
Guide (document 109M8639). The default storage rate for states reflects the current storage rate
of the device, which can either reflect the global collection rate or be a user-modified rate. Once
the states are added, any changes to the device rates or global rates does not affect the state
storage rates.
1.4 Back up PostgreSQL Databases

You can use System 1 to backup databases to local or network locations for later restoration. To
back up databases to certain locations, you must have the required permissions.
The Database Manager backs up only Fundamental or online PostgreSQL databases. To

backup Proficy databases, you can use a third-party tool like Visual Source Safe.
Back Up System 1 Database

To back up a database:
10/119
1. Choose Tools > Database Manager. The Database Manager is displayed.

2. Choose Back Up and Restore > Back Up.
3. Select the database to back up. To choose a database, choose Browse. The Open
Database dialog box is displayed.
4. In the Back Up Type field, select the type of Database you want to restore.
o Configuration and Data Includes the configuration and data. This is a System 1
Backup (.S1BKP) file.
o Configuration Includes the configuration only. This is a System 1 Configuration
Export (.S1CFG) file .
5. In the Destination field, click Browse. The Windows Open dialog box is displayed. Navigate
to a preferred back up directory. Click OK.
6. Choose Back Up. When backup is complete, a confirmation message is displayed.
Back up Ranger Pro Device Configuration

If you have added the Ranger Pro Gateway, you must manually back up the Ranger Pro
database.
1. In Windows File Manager, navigate to the default directory location, which varies
depending on which version of System 1 is installed:
C:\ProgramData\GE Bently Nevada\System 1\RangerPro
2. Copy the file ECORE.db to a directory location outside of the Bently Nevada directory
structure.
11/119
1.5 Restore a PostgreSQL Database

You can restore databases to local or network locations from a System 1 backup file. If you need
to restore a database, you may need additional permissions.
The Database Manager tool can only Fundamental or online PostgreSQL databases.
To restore your database:

2. Choose Back Up and Restore.
3. Choose Restore tab.

4. In the Restore tab, choose Browse and choose a database to restore. The Browse for
Backup File dialog box is displayed.
12/119
5. Navigate to the location where the System 1 Backup (.S1BKP) or System 1 Configuration
Export (.S1CFG) file is located.
6. Select the file and click Open.
7. Select a Restore Type. If you selected a:
o Backup file (.S1BKP ), choose a restore option:
n Restore Database Create a new database from the back up.
n Restore as Rx Database Restore the database on the Rx when setting up
replication.
o Configuration Export (.S1CFG), choose a restore option:
n Restore as New Database Create a new database from the back up.
n Restore as New Rx Database Restore the database on the Rx when setting up
replication.
n Restore Config Database Restore the database on a server to make offline
changes to the database.
n Overwrite Config Database Overwrite the database.
8. Click Restore. When the process is complete, a confirmation message is displayed.
1.6 Migrate PostgreSQL 9.6 to 11

When you upgrade System 1 from any prior version to System 1 19.2, PostgreSQL11 is installed and
all PostgreSQL9.6 data is migrated to PostgreSQL11.
To restore a database backup from any prior version of System 1 to a new installation of System 1
19.2 or later, and if the backup was created using Windows or Acronis backup:
13/119
1. Install PostgreSQL9.6 from System 1 installation disk.

a. Open Command Prompt in Administrator mode.
b. Navigate to the postgresql-9.6.15-1-windows-x64 directory. Enter
{postgresql-windows-x64}\postgresql-9.6.15-1-windows-x64.exe --install_runtimes no
c. When prompted, select the default path for Installation Directory.

d. When prompted to enter a path for Data Directory, use the PostgreSQL96 folder in the
back up file. For more information, see System 1 Folder Structure.
e. Complete the installation process.
2. Restore the backup created via Acronis or Windows backup.
3. Use the pgAdmin tool to verify that the PostgreSQL11 does not contain any user-created
databases. If the tool identifies a user-created databases, you must delete the database.
4. To migrate PostgreSQL9.6 data to PostgreSQL11 data:
a. Open VersionIno.xml from Store folder and check if PreviousPostgresVersion is 9.6.
b. If not, modify <PreviousPostgresVersion>11</PreviousPostgresVersion> to
<PreviousPostgresVersion>9.6</PreviousPostgresVersion>
c. From System 1 installation location (e.g. C:\Program Files (x86)\System 1\), run
PostgreSQLMajorVersionUpgrade.exe as Administrator.
d. Wait for migration completed message.
1.7 Move PostgreSQL Database

If you need more room to save your System 1 database, you can move the database, even if you
are already using it.
To move your PostgreSQL database to a new directory on the same machine:
1. Back up all System 1 offline databases.

2. In System 1, open the online database you want to move.
a. Disable online data collection.
b. Close the System 1 application.
3. Open Microsoft Management Services: click Windows > Run and enter services. Press
Enter.
4. In the Microsoft Management Services, locate and stop the PostgreSQL and System 1
Server services.
5. In Windows File Manager, locate a folder where you want to store the database.
6. Create a new directory within that folder named Stores.
14/119
7. Grant the account to be used to run the Starter service full control:
a. Right-click the new Stores folder and choose Properties.
b. Choose Security tab.
c. Choose Edit.
d. Choose Add.
e. Choose Locations and choose your machine from the list of available computers.
f. Enter NT Service\Starter in the object names panel.
g. Click OK.
8. Select the Starter account from the list of available groups and usernames.
9. In the Permissions panel, choose Full Control.
10. Click Apply and OK.
11. In the Properties dialog box, click Close.
12. Open Microsoft Registry Editor:
a. Choose Windows > Run.
b. Enter regedit. The Microsoft Registry Editor is displayed.
13. Navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\GE Bently Nevada\System 1
14. Select the System 1 folder.

15. Navigate to the Stores folder designated by the value of Enterprise_Database_Location.
Enterprise_Database_Location displays the location of the current Stores folder.
16. Cut and paste all items from the current Stores folder to the newly created Stores folder:
o All folders containing a DbHint.text file
o The PostgreSQL9.6 and PostgreSQL11 folder
o The VersionInfo file
17. Open Microsoft Registry Editor:
18. Navigate to

20. Double-click Enterprise_Database_Location and update its value with the path to the
newly created Stores folder. Change:
C:\ProgramData\GE Bently Nevada\System 1\Stores\
to
15/119
D:\Stores\ (The new Stores folder created)
21. In Windows File Explorer, navigate to:

C:\ProgramData\GE Bently Nevada\System 1\EnterpriseServer
22. Delete the file EnterpriseStore.db (db3)

23. Return to or reopen Microsoft Registry Editor:
24. Depending upon which version of PostgreSQL is installed, navigate to the correct directory:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\postgresqlx64-9.6
or
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\postgresqlx64-11
25. Double-click the binary named ImagePath. Depending upon which version of PostgreSQL
is installed, the complete ImagePath is:
C:\Program Files\PostgreSQL\9.6\bin\pg_ctl.exe" runservice -N "PostgreSQL-x64-9.6" -D "C:\Stores\PostgreSQL96 "
-w
or
C:\Program Files\PostgreSQL\11\bin\pg_ctl.exe" runservice -N "PostgreSQL-x64-11" -D "C:\Stores\PostgreSQL11 "

-w
26. Depending upon which version of PostgreSQL is installed, modify the directory path
enclosed in double quotes after the -D option: The new directory path must also be
enclosed in double quotes:
"C:\Program Files\PostgreSQL\9.6\bin\pg_ctl.exe" runservice -N "postgresql-x64-9.6" -D "D:\Stores\PostgreSQL96"
or
"C:\Program Files\PostgreSQL\11\bin\pg_ctl.exe" runservice -N "postgresql-x64-11" -D "D:\Stores\PostgreSQL96"
27. Depending upon which version of PostgreSQL is installed, navigate to the correct directory:
HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\services\postgresql-x64-9
or
HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\services\postgresql-x64-11
28. Double-click Data Directory and change its value to the new directory path.
29. Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresqlx64-9.6
or
16/119
HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-11
30. Double-click Data Directory and change its value to the new directory path where the
database is to be stored.
31. Close Microsoft Registry Editor.
32. In Windows File Explorer, grant full control to the account used to run the PostgreSQL
service:
a. Right-click on the newly copied PostgreSQL11 / PostgreSQL9 folder under the new
Stores folder and choose Properties.
b. Click Security tab. In the Group or usernames pane, click Edit. The Permissions
dialog box is displayed.
c. Click Add.
d. The Select Users, Computers, Service Accounts or Groups dialog box is displayed.
e. Click Locations. The Locations dialog box is displayed.
f. Choose Locations and choose your machine from the list of available computers.
g. In the Enter the object names to select field, enter Network Service.
h. Click OK. The Permissions dialog box is re-displayed.
i. In the Groups or user names pane, select the Network Service account.
j. In the Permissions pane, choose Full Control.
33. Press Windows+R; enter dcomcnfg and click OK. Component Services is displayed.
a. Start the PostgreSQL Server service.
b. Start the System 1 Server service.
34. Attach the Postgres databases:
a. Navigate to the directory where System 1 is installed. The default installation directory
is:
C:\Program Files (x86)\System 1
b. Run GE.Energy.System1.RestoreManagement.exe. The wizard guides you through a series of

steps to stop services, finalize restoration process, and add required permissions.
c. When complete, click Finish. The Restore Manager starts the System 1 Server
Service and the postgres 9.6/11 service.
35. Open the System 1 application.
36. Open your online database to verify it has been moved successfully. Close the online
database.
37. Open your offline databases to verify you can access the data. If you cannot open an
offline database, restore it from the backup.
1.8 Move Data Store to a New Server

These steps assume the default folder structure has not been modified. If your install uses a
custom installation folder, modify the paths given to match your local directory structure.
17/119
To move your database to a new System 1 server:
On the Current Server

1. Open your database in System 1, disable data collection, and close the application.
2. Navigate to the Stores folder of System 1. The default location is:
C:\Program Data\GE Bently Nevada\System 1\Stores
3. Copy the contents of this folder to a temporary directory.
On the New Server

1. If System 1 is already installed, and there are offline databases:
o Back up your databases using the Database Management tool.
o Delete the databases using the Database Management tool.
2. Otherwise, install System 1.
3. Navigate to the directory where System 1 is installed. The default location is:
CC:\Program Files (x86)\System 1
4. Run GE.Energy.System1.RestoreManagement.exe to launch the System 1 Restore Management tool.

5. In the Welcome dialog box of the Restore Management tool, click Next. The tool stops all
data acquisition services and backs up the Historian configuration database.
o Do not proceed to other steps in the Restore Management tool.
o Do not close the tool.
6. Backup the Stores/Archives folder of System 1.
7. Backup the Stores/postGreSQL96 folder of System 1.
8. Copy the contents of the temporary directory from the current server to the Stores folder of
the new server. Overwrite all of the existing content on the new server. The default location
is:
C:\Program Data\GE Bently Nevada\System 1\Stores
9. Open the Restore Management tool and complete the restoration process.
10. Restore offline databases as needed.
For System 1 and Proficy Licenses

To use the existing System 1 and Proficy licenses, you must move these licenses from the current
server to the new server:
1. Move your System 1 license to the new System 1 Server. See Move Licenses to a New
Machine topic in System 1 Machinery Management User Guide (document 109M8639).
2. Return your Proficy license on the current server. See Return a Proficy License topic in
System 1 Machinery Management User Guide (document 109M8639).
3. Assign a Proficy license to the new server. Refer to these topics in System 1 Machinery
Management User Guide (document 109M8639):
18/119
o Proficy License Server

o Finalize Licensing
1.9 Upgrade System 1 Database

Upgrading System 1 is similar to installing it. If you are using:
l PostgreSQL as your historian, follow the steps provided by the installation wizard.
l Proficy as your historian, we recommend you first migrate to PostgreSQL.
Before upgrading System 1:
l Back up your existing databases.

l Launch Windows Services application and stop all services whose names include
Enterprise Impact System 1 Client Proxy. For complete information, see the Enterprise
Impact User Guide (document 115M4065) available from Bently Nevada Technical Support.
If you are upgrading from System 1 Classic to System 1 Evo version 17.2 or later, refer to the Bently
Nevada System 1 6.x to 17.2+ Migration Guide available from Bently Nevada Technical Support.
When you upgrade a System 1 database version 1.4 to version 2.0 or later, train diagrams may be
disconnected. No data or functionality is lost. We recommend attaching the diagrams again.
Upgrade a Replicated Database

If you are upgrading a receiver database, you must first ingest all configuration files. You cannot
ingest configuration files produced by a different version of System 1. Verify which version of
System 1 was used to produce the replicated configuration files. If you are unable to ingest the
configuration files, or if they were produced by a different version of System 1, you can retransmit
the replicated data.
To upgrade a replicated system:
1. Stop the replication service on the transmitting server.

2. Allow all replication files to be consumed by the receiving server.
3. Stop the replication service on the receiving server.
4. Upgrade System 1 software on the receiving server. For a replicated system, you must
upgrade the receiving environment first.
5. Upgrade the receiving database For details, see Upgrade Database below. See Upgrade
System 1 Database.
6. Upgrade System 1 software on the transmitting server.
19/119
7. Upgrade the transmitting database. For details, see Upgrade Database below. See
Upgrade System 1 Database.
8. Start the replication process.
Upgrade a Database
You must be a Windows Administrator to upgrade the database.
To upgrade a System 1 database:
1. Choose Tools > Database Manager.

2. In the left panel. choose Upgrade > Browse. The Open Database dialog box are displayed.
3. Select the database you want to upgrade and click Open.

4. (Optional) To remove out-of-date configuration changes, choose Clean Up Database.
This option is available for offline databases only.
20/119
5. Verify the information displayed and choose Upgrade.
Database Manager relaunches in administrator mode and displays a message.

6. Click OK.
7. Click Upgrade.
8. Click Yes to confirm you would like to proceed.
Once the database has been upgraded successfully, a confirmation message is

displayed.
9. Click OK.
10. Close the Database Manager and open the database in System 1.
Configure a Transmitter Database

To configure the transmitter database
1. Choose Tools > Database Manager. The Database Manager is displayed

2. Select the Database Replication pane
21/119
3. Click Browse. The Open Database dialog box is displayed

4. Select the Database to replicate
5. Set the Replication Type to Transmitter
6. In the General pane, choose Data Location, and click Browse.
The data location is a folder where replicated files are stored. Verify that the
account running System 1 Replication Service has read and write access to the
selected folder.
7. In the Replication Settings pane, select the data and events to be replicated.
8. Click Save.
1.10 Grant Database Permissions

Specific local and remote scenarios are described below to help you grant the necessary
security permissions. Before you grant permissions, verify that both the client and server are
running on the same domain.
Backup Folder Structure Recommendations

When you select a destination location to backup a database, we recommend that you create a
specific folder to house the backup files. It is not a good idea to use the drive root (such as C:\).
Login Types
System 1 utilizes permissions based on user logins to either allow or deny communication within
and between domains and workgroups.
Available login types used in the different communication scenarios:
Login
Scenario
Type
Admin Administrator account on the machine.
User domain account. These accounts enable the user to log in to any machine
Domain located on the same domain regardless if the user has a local account on the
machine.
User account on the machine. These accounts only enable the user to log in if the
Local machine has a user's account on the machine. In the workgroup example, the Local
account has the same user name and password on all machines.
A second user's account on a machine. As mentioned in the Local example above,

Local2
Local2 has the same user name and password on all machines.
About Local Accounts vs. Domain Accounts

A Local account is tied to a single machine. That account holds no access to other machines on
22/119
the network unless a duplicate account is created on each machine.
A Domain account, on the other hand, is tied to a network. This account can log in to any
machine in the network domain even though the user holds no local account on the machine.
The following scenarios assume that you are trying to communicate between two different
machines. Communicating within the same physical machine does not require permissions.
Within the Same Domain

If accessing a machine located on the same domain as your machine, use these login account
scenarios:
Server Login Client Login
Admin Admin
Admin Domain
Local Local
Admin Local
Between Different Trusted Domains

If accessing a machine located on a different but trusted domain than your machine, use these
login account scenarios:
Admin Admin
Admin Domain
Local Local
Admin Local
Login From a Workgroup to a Domain

If accessing a machine located on a workgroup while your machine is on a domain, use these
Local Local
Local Local2 (run as Local)
Login From a Domain to a Workgroup

If accessing a machine located on a domain while your machine is on a workgroup, use these
23/119
Local Local
Login Within the Same Workgroup

If accessing a machine located on the same workgroup as your machine, use these login
account scenarios:
Local Local
Local2 Local (run as Local2)
Login Between Different Workgroups

If accessing a machine located on a different workgroup than your machine, use these login
account scenarios:
Local Local
Local2 Local (run as Local2)
Local (different password) Local
Grant Permissions on a Local Computer

There are two scenarios that are defined as backing up locally:
Local Same Source and Destination Computer
24/119
l You are either backing up to or restoring from the local computer you are using.
l The source computer is the same as the destination computer.
l This computer has both Client and Server installed.
Network Same Source and Destination Computer
l You are either backing up to or restoring a database from a network computer to a folder
located on the same network computer.
l The source computer is the same as the destination computer.
l Your computer has Client installed while the network computer has Server installed.
Fix Folder Insufficient Access Rights

If you get an error message that states something like you have "insufficient access rights to
perform the operation", you need to modify the security permissions to allow the System 1 Server
service to modify the selected folder.
To grant security permissions to the System 1 Server service:
1. Select the folder where the database is to be backed up.

2. Right-click on the folder and select Properties.
25/119
3. Select the Security tab and click Edit... The Permissions dialog box is displayed.
4. Click Add... The Select Users, Computer, Service Accounts, or Groups dialog box is
displayed.
5. In the Enter the object names to select field, enter network service.
6. Click OK. The Permissions dialog box is re-displayed.
26/119
7. Select Full Control.
8. Click OK.
Remote Computer Scenarios
There are two scenarios you might use to create a remote back up.
Remote Network to Local Computer
27/119
l You are either backing up to or restoring from a network computer to the local computer
you are using.
l The source computer is different from the destination computer.
l Your computer has both Client and Server installed while the network computer has Server
installed.
Remote Network Computer to Another Network Computer
l You are either backing up to or restoring a database from a network computer to a folder
located on a different network computer.
l The source computer is different from the destination computer.
l Your computer has Client installed while the two network computers have Server installed.
Fix Network Destination Folder is Not Shared
If you get an error message that states something like you have "Destination folder is not
shared", you need to modify the security permissions for the selected folder.
To grant permissions for remote computer scenarios using the destination folder:
Step 1: Grant Folder Share Permissions
Modify the folder Properties Security settings to enable sharing. Do not use right-click on
the folder and select "Share with" or "Give access to" options. The latter options do not
work in these scenarios.
To grant full permissions to both the System 1 Server service computer and domain user:
28/119

3. Select the Sharing tab. Click Advanced Sharing. The Advanced Sharing dialog box is
displayed.
29/119
4. Choose Add... The Select Users, Computers, Service Accounts, or Groups dialog box is
displayed.
5. Click Object Types...
6. The Object Types dialog box is displayed. Verify that Computers is enabled; if not select it.
Click OK.
7. The Select Users, Computers, Service Accounts, or Groups dialog box is re-displayed.

8. In the Enter the object names to select field, enter the name of the destination server
computer.
30/119
For example, we entered Server_01 as the computer name.
9. Click OK.
Step 2: Grant Remote Computer Security Permissions

On the remote computer, navigate to the location where you want to back up the database.

3. Select the Security tab. Click Edit... The Permissions dialog box is displayed.
31/119
4. Click Add... The Select Users, Computer, Service Accounts, or Groups dialog box is
displayed.
5. The Object Types dialog box is displayed. Verify that Computers is enabled; if not select it.
Click OK.
6. Click OK. The Permissions dialog box is re-displayed.

7. In the Enter the object names to select field, enter the name of the destination server
computer.
32/119
For example, we entered Server_01 as the computer name.
8. Click OK.
1.11 Clean Database

To reduce the size of the database, you can remove old, stored configuration changes.
Before you clean a database, close it and back it up.
To clean a database:

2. Select the Clean Up pane.
33/119
3. Click Browse. The Open Database dialog box is displayed. Select a database.
4. Click Clean Up. Confirm that you want to proceed.
Setpoint historical data is retained when cleaning up a database.
1.12 Delete Database

Before you delete a database, close it. The database is deleted permanently. You cannot
undo this operation.
To delete your database:

2. Select the Delete pane.
34/119
3. Click Browse. The Open Database dialog box is displayed. Select a database.
4. Choose Open.
5. Click Delete. Confirm that you want to proceed.
1.13 Rename Database

Before you rename a database, close it.
To rename your database:

2. Select the Rename pane.
35/119
3. Click Browse. The Open Database dialog box is displayed.
4. Select a database and click Open.

5. Enter a new database name in Enter New Name. Special characters are not permitted.
36/119
6. Click Rename. Confirm that you want to proceed.
1.14 Overwrite Configuration Database

There are two reasons you may want to overwrite a configuration database:
A. Make changes off-site. You can make changes to a configuration on an off-site server
and then apply the modified System 1 Configuration Export (.S1CFG) file to the on-site
database. You can also overwrite the configuration of a standalone or replication (Tx and
Rx database) setup. Once you make a copy of the database for off-site use, any further
changes made to the local database are overwritten when you restore the modified offline
configuration.
B. Create a configuration checkpoint. When making large changes to a configuration
database, you can first backup the configuration database. If the changes fail, or for other
reasons, you may choose to restore the check point configuration.
When you overwrite the database configuration, the configuration does not modify the historian
database configuration. When you restore a database, be sure to enable data collection.
Configuration overwrite is only supported if you are use PostgreSQL as the data historian, and for
System 1 20.2 and later. The version of the back up file and the database must match. If you need
to revert an overwrite operation, the Database Manager maintains a configuration database
snapshot in the database store folder.
Configuration Features Supported

What is Overwritten
l Configuration
l HMI
l Plot Sets (you must use the same System 1 user account on both computers)
l Custom Templates
l Custom Units
l Plot record
l New machines, devices, and so forth.
What is Not Overwritten

l User preferences
l Status
l Notes
l Reviews
l Events
l Data
l Permissions/authorizations
Standalone Setup
Server Locations
l The local server contains the master copy of the database. Data is collected by
37/119
connecting to devices.
l The off-site server is an alternate server where you can make offline changes to the
configuration.
Overwrite Database
Before you overwrite the local database with the off site configuration changes you made, verify
that the database GUID (Globally Unique Identifier) of the database you are about to restore
matches the GUID of the local database. In Windows File Manager, navigate to the location of
each database folder. Open the file DbHint.txt and compare the value of ConfigDhpID, EnterpriseID and
DatabaseId. If they are not identical, delete the offsite database and restore again, making sure you
select Restore Config Database.
To overwrite a configuration database:
1. On the local server, create a Configuration Export (.S1CFG) backup. In the Back Up Type
field, choose Configuration. See Back up PostgreSQL Databases .
2. If you are creating a configuration checkpoint (reason B above), continue to step 3.
Otherwise, on the off-site server:
a. Restore the database. In the Restore Type field, choose Restore Config Database.
See Restore a PostgreSQL Database.
b. Make offline changes as required.
c. Create a Configuration Export (.S1CFG) backup. In the Back Up Type field, choose
Configuration. See Back up PostgreSQL Databases .
3. On the local server, restore the database. In the Restore Type field, choose Overwrite
Config Database. See Restore a PostgreSQL Database.
Replication Setup
Server Locations
l The local Tx server contains the master copy of the database. Data is collected by
connecting to devices. The database is set as Transmitter.
l The local Rx server contains the master copy of the database. The database is set as
Receiver.
l The off-site server is an alternate server where you can make offline changes to the
configuration.
38/119
Overwrite Tx Database
To make offline changes or create and restore a checkpoint on a Tx database in a replicated
setup of System 1:
1. If you are making changes off-site (reason A above), stop data replication on the local Tx
server. On the Tx server, modify database replication from Transmitter to None. See
Configure Transmitter Database.
2. On the local Tx server, create a Configuration Export (.S1CFG) backup. In the Back Up Type
3. On the local Rx server, create a Configuration Export (.S1CFG) backup. In the Back Up Type
4. On the off-site server:
a. Restore the database. In the Restore Type field, choose Restore Config Database.
See Restore a PostgreSQL Database.
5. On the local Rx server:
a. Restore the Rx database backup. In the Restore Type field, choose Overwrite Config
Database. See Restore a PostgreSQL Database.
b. Restart the Replication service. See Start Replication Service.
6. On the local Tx server, restore the Tx database. In the Restore Type field, choose Overwrite
Config Database. See Restore a PostgreSQL Database.
7. On the local Tx server:
a. If you did stopped the replication service in Step 1, modify database replication from
None to Transmitter. See Configure Transmitter Database.
b. If you did not stop the replication service in Step 1:
i. Retransmit the replicated configuration. See Retransmit Replicated
Configuration.
ii. Retransmit the replicated data. See Retransmit Replicated Data.
Overwrite Rx Database
To make offline changes or create and restore a checkpoint on a Rx database in a replicated
setup of System 1:
1. On the local Rx Server, create a Configuration Export (.S1CFG) backup. In the Back Up Type
2. If you are creating a configuration checkpoint (reason B above), continue to Step 3.
Otherwise, on the off-site server:
39/119
a. Restore the Rx database. In the Restore Type field, choose Restore as New Rx
Database. See Restore a PostgreSQL Database
3. On the local Rx Server:
a. Restore the Rx database backup. In the Restore Type field, choose Overwrite Config
Database. See Restore a PostgreSQL Database.
b. Restart the Replication service. See Start Replication Service.
4. On the local Tx server, retransmit the replicated configuration. See Retransmit Replicated
Configuration.
1.15 Retransmit Replicated Database

During the replication process, a transmitter database periodically packages new data, events,
and status information that are eventually sent over the network to the destination database.
When this process is interrupted due to network issues or database problems, the transmitter
and destination databases become out of sync. When this happens, you must retransmit the
replicated configuration using the Config Sequence Number from the receiver machine.
When you retransmit replicated configuration data, System 1 also retransmits any
corresponding configuration templates for the specified configuration sequence ID. For example,
if you know that a template was created for configuration after configuration sequence 50, then
entering 50 for the configuration sequence ID also retransmits this corresponding configuration
template. If you are unsure when configuration templates were created, enter 1 for the
configuration sequence ID and the entire configuration is retransmitted.
Retransmit Replicated Configuration

To retransmit replicated configuration and corresponding template configuration:
1. On the receiver machine, choose Windows Start Menu > System 1 Database
Management. The Database Manager is displayed.
2. Select the Database Replication tab.
3. In the General pane, verify the values of replication type, database name and data
location. These fields are set during replication configuration.
4. In the Replication Retransmit pane, choose Replication Config Retransmit Tool.
40/119
5. Note the configuration Sequence ID on the receiver machine:
6. Go to the transmitter machine and launch the Database Manager.

41/119
10. Enter the configuration Sequence ID from the receiver machine:
11. Choose Request Retransmit. The tool retransmits and recovers the configuration changes
based on the configuration Sequence ID.
Retransmit Replicated Data

To retransmit replicated data:
1. On the transmitter machine, launch the Database Manager.

3. In the General pane, verify that Replication Type, Database Name and Data Location are
correct. These fields are set during replication configuration.
4. In the Replication Retransmit pane, choose Replication Data Retransmit Tool.
5. Enter the desired start and end timestamps for the period from which you wish to
retransmit data:
42/119
6. Choose Request Retransmit. The tool initiates a background process that retransmits
data files within the specified timestamps.
If a previous retransmit request is still being processed, a message is displayed. You

must choose to overwrite the previous request or wait until the previous request is
completed. The retransmit request may take several hours for each day of data
requested before it finishes.
7. To view the status of the retransmit requests, you can view four log files. The log files are
continuously updated. To view the files, we recommend a third-party application like
SnakeTail or BareTail. The files are updated here:
C:\ProgramData\GE Bently Nevada\System 1\ReplicationService\
8. There is one log for each of the four data types. The file names are prefixed with
DataRetransmitLog:
o Alarm and Transient
o Trend Static
o Trend Waveform
o Portable/Offline
The log files are continually updated for every hour of data that is processed and indicate
when its data retransmission is complete. When all four log files are complete,
retransmission is complete.
1.16 Migrate Data

You can migrate data from the following sources into System 1:
43/119
l System 1 6.x database. See Migrate Data from System 1 Classic.

l Ascent database. See Migrate Ascent Data to System 1 .
l Proficy Data to PostgreSQL. See Migrate Proficy Data to PostgreSQL .
Migrate Data from System 1 Classic

To migrate System 1 Classic enterprise data and configuration into a System 1 Evo database, use
Database Manager.
To avoid negatively impacting a device's performance, System 1 sets a device offline during data
migration.
When to Use 6.81+ Enterprises Data Source

The 6.81 enterprises data source refers to devices that are supported by the System 1 Classic
application. Use this data source to migrate native device's configuration and data from a
System 1 Classic enterprise version 6.81 or later into a System 1 database.
After migrating the configuration and data, you can use the System 1 Evo application to modify
device configuration, collect data, and so forth.
Before You Migrate

Before you migrate configuration or data, verify that you have resolved any issues relating to
these topics.
44/119
Topic Description
Licensing Apply licenses to online databases in System 1 as needed:
l For 3500 devices, Premium package license is required.

l For OPC, Advanced or Premium package license is required.
l For Trendmaster DSM, Advance or Premium package license is required.
Migration is not supported for all other devices.
Configuration You can migrate both at once, or migrate configuration first and data later.
and data The exception is Recip Monitors. See Migrate Recip Monitors . Also see
Historical Data next.
Historical data You must migrate historical data before new data, and before you begin
collecting data. You cannot migrate historical data after migrating current
data or once you begin collecting new data. If migrating 3500 data, you can:
l Migrate 3500 Rack from S1 Classic to an offline S1 17.2 enterprise.

l Change IP address of 3500 Rack in S1 Classic and migrate it to same
System 1 17.2 online database. Keep it disabled for online data collection.
l By default, the Data Migration tool migrates data for the last five years.
To migrate data up to 10 years old, change the Long Term Data settings.
See Modify Long Term Data Store Setting.
Types of data l Historical trend, alarm and SUSD data

l Software alarm configuration
l Collection group configuration
l Alarm list
l Live hardware alarms
l Spectral band configuration, setpoints and data (fault frequency
bands configured in S1 Classic are migrated as spectral bands).
Backup First restore the backups and register them to the enterprise. If necessary,
database install System 1 Classic temporarily instead of restoring the backup manually.
Make sure you use a version of SQL that is the same or newer than the version
used to create the backup.
Archive data First convert the archive into S1 Classic enterprise and then migrate it to S1
17.2+. To convert an archive into a enterprise, see the S1 Classic Knowledge
Base.
Multiple Classic You can migrate configuration and data from multiple System 1 Classic 6.x
enterprises enterprises or Data Acquisition Units (DAQs) into a System 1 Evo 17.x database
or later. For assistance, contact Bently Nevada Technical Support and ask for
information on the S1 Server Calculator.
Old Classic You can migrate from System 1 6.81 and above. If you are using a version
versions earlier than 6.81, first upgrade to 6.81, then migrate.
45/119
Topic Description
Device During migration, only devices and servers that need to be migrated are
detection detected. The migration process skips devices and servers whose
configuration has already been migrated.
Resume If migration is interrupted, given the same devices, servers and time range,
migration migration is resumed from the point it was stopped.
3500 Rack l When you migrate a 3500 Rack, it is initially disabled to prevent data
collection. When you migrate the older data, enable data collection for
the 3500 Rack in System 1.
l The IP addresses of 3500 racks must be unique for migration. Before
migration, change the IP addresses of 3500 racks in System 1 Classic 6.x
enterprises.
l To prevent data loss, if a monitor you want to import uses the same
IP address of a connected monitor, deactivate the monitor before
swapping cards.
3500/50 After migrating a 3500 Rack and 50 monitor, when you attempt to
Monitor synchronize the configuration, a message falsely indicates that a
50M monitor is being replaced with a 50 monitor. To resolve this, obtain a
patch from Bently Nevada Technical Support
OPC Server Before migrating OPC server configuration, establish connectivity between

System 1 database and the OPC server. Add a test point in System 1 database
and check its current data value. If the current value is available, the OPC
server can communicate with System 1 database, and you can migrate OPC
server configuration and data. You can also enable online data collection for
the migrated OPC server. See the System 1 Machinery Management User
Guide.
SQL Credentials To migrate a 6.x enterprise, you must have valid SQL credentials.

l You cannot use the System1Admin windows credentials.
l The default SQL user credentials are System1DBUser or sa.
l To verify your SQL credentials, open the SQL Management Studio on the
System 1 Classic server. Connect using SQL Server Authentication mode.
Verify that the connection works.
l To reset the SQL password, use the System 1 password tool on the
System 1 Classic server.
SQL Version Any version of SQL supported by System 1 Classic 6.81 and later is acceptable.
Server Verify that the server you are migrating to meets minimum specifications.
Specifications Refer to the current System 1 Machinery Management Software Datasheet
(document 108M5214) available from Bently Nevada Technical Support.
Firewall If there is a firewall between the S1 6.x and S1 20.1+ server, open port 1433 on the
46/119
Topic Description
S1 6.x server. This port is used by SQL to communicate.
Software Don't add software measurements before migrating data. You cannot link the
Measurements measurements to the historical data. Instead, add software measurements
with historical data calculations.
Inactive When you migrate inactive channels and measurements, they are migrated
Channels and as active to allow you to verify historical data post migration. When you
Measurements enable data collection and synchronize the rack, System 1 updates the state
of the channel and measurements to reflect their current status.
Shrink and Re- On System 1 6.x server, use the System 1 Database Manager to complete these
index the two steps on both the configuration and historical database:
Classic
Shrink database.
Database
l
l Re-index database.
For details, see System 1 Version 6.96 Classic Installation Guide (document
181136).
Configuration l Using the 6.x connector, you can import System 1 Classic 6.x archives
after converting them into System 1 Classic 6.x enterprises.
l Use 6.x connector to import configuration and data from a System 1
Classic 6.x enterprise into a System 1 Evo 18.x database or later. Imported
6.x devices are read-only in a System 1 database.
What You Cannot Migrate

l Machine configurations
l Software measurement configurations
l HMI views
l Plot sessions
l Reference data
l User security settings
Migrate Hydro Monitors

You must migrate Hydro monitors configuration before you migrate the data. System 1 supports
migrating only 3500 / 46M Hydro Air Gap and Multimode Hydro Air Gap channels.
To migrate data for Hydro Air Gap and Multimode Hydro Air Gap Channels:
1. Migrate only the configuration from 6.x to 21.x+.

2. Synchronize the device or import the rack file.
3. Add and configure the Hydro Turbine and Generator.
47/119
4. Configure these properties of the Hydro Generator:

o Rotation direction
o Design Air Gap
o Number of teeth in stator
o Direction of tooth numbering (increasing)
o Tooth aligned with reference direction
5. Map the Hydro Air Gap channels to the Hydro Generator.
6. Migrate the data.
Migrate Recip Monitors

You must migrate Recip monitors' configuration before migrating data.
To migrate data for 70M, 72M and 77M Recip monitors:
1. Migrate the configuration from 6.x to 20.x+.

2. Configure your Recip compressor in the System 1 database.
3. Map the Recip channels to the compressor.
4. Use the Data Manager tool in System 1 to configure the data storage.
5. Migrate the data.
Migrate OPC Configuration

The following restrictions apply to OPC configuration migration:
l If the configuration has already been migrated, t he Data Migration tool does not migrate
the configuration again.
l The default number of OPC servers is 20. The migration summary displays a message
when the number of OPC servers exceeds this limit.
l An OPC server may have no more than 200 OPC groups. The tool migrates no more than
200 OPC groups. The migration summary displays a message when the number of OPC
groups exceeds this limit.
l A database may have no more than 6,000 OPC items. The tool migrates no more than
6000 OPC items. The migration summary and log display a message when the number of
OPC items exceeds this limit.
l If an OPC group in a 6.x enterprise has more than 1,000 OPC items, the tool creates a new
OPC group for the same server and appends the following suffixes to each group's name:
48/119
OPC Items Suffix
1-1,000 New 1
1,001-2,000 New 2
2,001-3,000 New 3
3,001-4,000 New 4
4,001-5,000 New 5
5,001-6,000 New 6
l In a 6.x enterprise, if an OPC group has duplicate OPC items, the tool migrates only the first
active OPC item. Duplicate OPC items have the same ids but may or may not have the
same user or tag names.
l In a 6.x enterprise, if duplicate OPC items are set to inactive, the tool migrates the first
inactive OPC item. The tool also writes a message to the event log for each skipped OPC
item. The migration summary displays a message for each OPC server when an OPC
group contains duplicate OPC items.
After migrating the configuration of OPC enum measurements, their enum values are undefined
in System 1. You can assign values to these measurements. See the System 1 Machinery
Management User Guide.
Modify Long Term Data Store Setting

If you want to migrate data older than five years, you must change the Long Term Data Store
setting in System 1:
1. Create an online System 1 database. Then enable data collection.

2. Open the System 1 Database Manager. Choose Tools > Database Manager. The Database
Manager tool is displayed.
3. In the General pane, select a server and click Connect.
4. In the Storage Settings pane, enter a value for Long Term Data. The default setting is five
49/119
years.
Migrate System 1 Classic 6.81+

System 1 6.81+ is for System 1 Classic databases version 6.81 or later on native devices. Verify that
you have reviewed the topics described in Before You Migrate , especially Shrink and Re-index
the Classic Database.
To migrate data, on the System 1 20.x+ server:
1. Launch the Database Manager. Choose a method:

o Choose Windows Start Menu > System 1 Database Management.
2. The System 1 Database Manager is displayed.
3. In the General pane, browse for the System 1 Destination Database.
4. In Data source, choose S1 6.81+.
5. Choose Import Options:
o All - Migrate the configuration and the historical data at the same time.
o Configuration - If you migrate Configuration only, you must migrate the
Configuration before Historical Data. Do not enable data collection in System 1 Evo
until you migrate historical data. Once you begin to collect new data, you cannot
migrate historical data.
o Historical Data - You can migrate only static, dynamic, and alarm event data.
50/119
6. In the Source Database pane, identify the source database and provide user credentials:
Fields Description
Database location System 1 configuration server name or IP address.
SQL account user name SQL credentials required to connect to a System 1 6.x
and password configuration SQL server.
Browse for and select the System 1 6.x database from which
Database name
configuration and data is migrated.
7. Click Next. The Data Sources dialog box is displayed.

8. Select a Data source. Data sources are groups of configured devices from your System 1
6.x enterprise.
9. If you are importing historical data, select a Data range:
o All - Import all data for selected devices and servers.
o Custom data range - Select the start time and end time.
10. Choose Next and then Finish.
The time it takes to migrate configuration and data depends on multiple parameters like the S1
Classic server specifications, S1 20.1+ server specifications, network bandwidth available between
the two servers, condition of S1 Classic databases, and the number of racks and the number
years of data to be migrated. Generally, it takes about 25-30 minutes to migrate one year of
data for one Rack. If you are migrating 5 years of data for 5 Racks (or 25 years of data), it may
take approximately 12.5 hours.
When migration is complete, a summary is dipslayed.
Resolve Connection Issues

You may have problems connecting with a remote System 1 6.x server.
To connect to a remote System 1 6.x server, on the System 1 20.x server:
1. Edit this file as an administrator:

C:\Windows\System32\drivers\etc\hosts
2. Add the IP address and machine name of the System 1 6.x server to the hosts file.
Examples:
10.7.0.85 6xSERVER1
10.7.3.161 6xDAQ1
3. Save the hosts file, and try connecting again.
After You Migrate

After you migrate, verify if these topics apply to the migration:
51/119
Topic Description
Migrate After you migrate:

Additional
You can migrate a newly added instrument group configuration. Just
Configuration
l
and Data select the new device type in the migration setup.
l You can migrate a newly added device. Just select the instrument group
type in the migration setup.
l You can migrate data collected by the DAQ service during or after
migrate. Just re-run the migration to collect the newer data.
Alarms l When an alarm is active in System 1 Classic 6.x enterprises, and the data
migration process is triggered, the alarm is cleared. After data migration
is complete, and when System 1 is online, the application logs a new
alarm for the corresponding channel or measurement type.
l System 1 Classic 6.x application logs alarm events at channel level not
measurement level.
l After migrating alarm data from System 1 Classic 6.x enterprises, the
following variables in System 1 database are blank :
o Measurement
o Value
o Setpoint
When you enable online data collection, System 1 logs new events.
l Duplicate hardware alarm events may be displayed. This can happen if

you:
o Stop the Data Collection Module on a 6.x server and start the
module on a 6.x data acquisition server.

o Disable hardware alarms in 6.x display and enable them again.
System 1 clears the active alarm and displays the new alarm event whose
time stamp is the same as the previous one.
Devices After data migration, you must create your asset hierarchy in System 1. Asset
hierarchy hierarchy data is not migrated from the source to the destination database.
You can map points to assets while data migration is in progress.
Channel Channel activities and configurations are retained. Synchronous and

Migration asynchronous waveforms are added to those channels in the System 1 20.x+
database.
Filtering System 1 Classic 6.x and System 1 Evo 18.x applications differ in change filtering.
Events The former uses hysteresis. The latter uses a tiered data system with averaging.
Data You can set the data retention size only if you have enabled data collection.
Retention Size
Migrate Ascent Data to System 1
52/119
You can use the Data Migration tool to migrate data from an Ascent database to a System 1
database. The tool supports Ascent databases versions 2015+ (internal version 248 and above).
Information You Can Migrate

You can migrate:
l Ascent machine hierarchy

l These schedule entries:
o Spectrum
o Waveform
o Demod
o 6 Pack
o Keypad
l These alarms:
o Power
o Waveform peak-to-peak
o Waveform Crest factor
o Numeric data alarm
l Notes
Information You Cannot Migrate

You cannot migrate:
l Linear speed assets

l Fault frequencies
l Gear and bearing definitions
l Attached file schedule entry
l vbOnline* schedule entries
l Average value
l These alarms:
o Peak alarms
o Alarm templates
o Envelope alarms
o Statistical alarm definitions
l Routes
l Online definitions
l Reports
l On chart remarks
l Instrument connection information
l Images
l Recordings whose type or domain is different from their associated measurements
Step 1. Convert Ascent Data

To convert an Ascent Firebird database to an interim SQL database, run the Ascent Conversion
Utility tool:
53/119
1. Open the System 1 installation disk and locate the Ascent Conversion Utility Tool.
(Alternatively, download it from Bently Nevada Tech Support.)
2. Install the tool on the computer where the Ascent database resides. Also install, as needed:
o Microsoft .NET Framework 4.6.

o Ascent 2015 or Firebird database plugin (available in the Ascent Conversion Utility
package).
3. Run Ascent Conversion Utility.
a. Browse and select the Ascent database you want to convert.
b. Enter required credentials. The default values are:
o Username: sysdba
o Password: masterke
If you cannot access the database using the default user name and password,
contact your Ascent administrator.
c. Select a destination directory for the converted SQLite database.

d. Click Convert. The utility does not modify your data. It rebuilds the database in
SQLite.
4. To import the Ascent data to System 1, copy the converted SQL database to the local folder
on the machine hosting System 1. The default path is:
C:\ProgramData\GE Bently Nevada\System 1\CommtestVbOnline\AscentDatabases.
If you don't copy an Ascent database to this location, System 1 creates a default, empty
database, containing an empty configuration hierarchy.
You can store multiple Ascent databases in the same location, but the serial numbers for
any Commtest vbOnline Device you add must be contained in a single database. A
duplicate serial number found in more than one database causes the migration to fail.
If you modify the Commtest VbOnline devices configuration, repeat the conversion process and
replace the SQL database on the machine running System 1. After you update the database,
synchronize the Commtest VbOnline devices with System 1. See .
Step 2. Migrate Ascent Data

If you are adding a Commtest vbOnline device, first see the System 1 Machinery
Management User Guide.
Run the Data Migration tool only once. If you import the same database again, you will create
duplicate machines in the database.
Due to limitations of the Proficy Historian, you can migrate a maximum of 10 years data.
To launch the Data Migration tool:
54/119
1. Choose Tools > Data Migration. The Data Migration wizard is displayed.

2. In the General pane, identify the destination database and the type of data to migrate:
o System 1 destination database
o Source Database type
n Ascent 2015+ for an Ascent* database version 2015 or later
o Select import options:
n All - Select this option to migrate the data and its configuration.
n Configuration - Select this option to migrate only configuration.
You cannot migrate data without its configuration.
3. Click Next.
4. In the Source Database pane, identify the source database and Data Sources. To migrate
Ascent configuration axes that do not contain scheduled entries, Choose Include
Unscheduled Axes. Ascent points are always migrated even if this option is not selected.
5. Click Next.
6. The wizard displays a message to inform you that data migration may take hours to
complete for very large databases. Choose Yes to proceed.
7. After migrating data, the wizard displays the migration summary and generates a log file.
You can copy the migration summary and save it for future reference. The Migration
Summary window supports these operations:
o CTRL + A to select all information
o CTRL + C to copy information
o Right-click copy option
The log file contains a brief summary of the migration process, warnings and errors. The log file is
located here:
%AppData%\GE Bently Nevada\Log Files.
Step 3. Enable Data Collection

After you migrate historical Ascent data, enable data collection. Once you enable data
collection, you can not migrate additional historical data.
FAQ and Troubleshooting

Q: How can I improve the speed of the migration?
To improve the speed of the migration, we recommend:
l Place the source and destination databases on your local file system, not a shared
folder on the network. During migration, the network traffic may become the
bottleneck, slowing down the migration process.
l Close all System 1 clients accessing the destination database.
55/119
Q: Can I monitor data as it is migrated?

You can use a System 1 client to view the configuration and data as it is being migrated.
However, the System 1 client slows down the migration process.
Q: How do machines from an Ascent database appear in System 1?
After migration, machines from an Ascent database appear as generic machines in
System 1. You can create complex machines using the asset libraries in System 1. To move
the points from a generic machine, cut and paste them to the complex machine.
Q: How is alarm handling in Ascent different from System 1?
For discrete keypad entries in historical data, System 1 might generate alarms that do not
exist in Ascent. These applications use slightly different criteria to compare vibration data
against alarm setpoints:
l Ascent generates an alarm if vibration data is greater than an alarm setpoint.

l System 1 generates an alarm if vibration data is greater than or equal to an alarm
setpoint.
For normal vibration data, this distinction is unlikely to generate alarms. Discrete values,
however, may match the alarm setpoints more readily.
Migrate Proficy Data to PostgreSQL

You can use the Database Manager to migrate data from a Proficy database to a PostgreSQL
database. After migrating data, you cannot use Proficy as a data historian again.
Launch the Database Manager

You must be a Windows Administrator to migrate Proficy data.
To launch the Database Manager:

Migrate the Proficy Database

To migrate the Database:
1. In Database Manager, choose Tools > Proficy Data Migration. The Proficy Data Migration
2. Click Browse. Recent databases are displayed. Select the database you want to migrate.
(The amount of required disk space is displayed.)
3. If disk space is limited, you are prompted to select an alternative location or drive for the
Proficy database.
4. Click Migrate. Migration progress is displayed. Depending on the amount of data and
points, the migration may take several hours. When migration is complete, the Proficy
Database Migration dialog box confirms that the migration is complete.
Migrate a Replicated Database

You can migrate a replicated database from Proficy to PostgreSQL.
56/119
If you are migrating a replicated database from Proficy to PostgreSQL on a Transmitter

(Tx) Server, you must replicate all trended variables.
To migrate a replicated database:
1. If you have not yet upgraded the databases, you must upgrade all databases to the
current version of System 1. You can begin the upgrade with either the Tx or Rx server.
2. Start data migration on the Tx server. Once progress is displayed on the Tx server, you can
begin to migrate data on the Rx server.
Once you begin migrating data, all new data is stored in PostgreSQL.
Change Default Historian

You can change the default System 1 historian from Proficy to PostgreSQL. If the current historian
is currently PostgreSQL, the Preferences > Historian tab is not displayed.
To change the default System 1 historian:
1. In Database Manager, choose File > Preferences. The Preferences dialog box is displayed.
2. Select the Historian tab.
3. In the Historian field, choose PostgreSQL.
4. Click Save.
All future databases will use PostgreSQL as the default historian.
Cleanup After Proficy Database Migration
After you migrate a Proficy database, verify that all databases have been migrated and then
remove the migrated and now obsolete Proficy database.
1. In Database Manager, choose Tools > Proficy Clean Up. A Proficy Clean Up message is
displayed.
2. Click OK. The clean up process may take some time. When complete, the summary page
describes what was cleaned up.
3. Open Windows Services.msc. Restart the System 1 Server service.
4. Wait one minute before restarting the System 1 application.
5. Launch System 1. Verify that it operates as expected.
6. Return Proficy license. For details, refer to the Proficy licensing documentation.
7. Launch Windows Add and Remove Programs.
a. Uninstall the Proficy Add-on. During uninstallation, choose Delete Archives -
Continue Uninstall.
b. Uninstall Common Licensing.
8. In Windows File Manager, navigate to the directory in which the Proficy database was
located. Delete any remaining .iha files.
57/119
1.17 Manage Server Security

A Server Administrator and built-in Administrator on an S1 installed server has administrative
rights to all databases on a System 1 server. A Server Administrator may or may not be a
database Administrator.
Server Administrator Role

A Server Administrator can:
l Manage users with administrative rights on the System 1 server.

l Manage authorized Administrators of the server.
l Modify rights of users with Advanced or Basic roles.
l Control who can create new databases on the server.
l Access all databases residing on a locally installed System 1 server.
The rights applied to a role are propagated across all databases.
These features are not available if System 1 server is installed remotely.
Launch Database Manager

To launch Database Manager:

Create and Manage Server Administrators

To create and manage Server Administrators on a System 1 server:
1. If you are not currently an administrator on a System 1 server, you must log into the
computer using a Windows administrator account.
2. Choose Tools > Database Manager. The Database Manager application is launched.
3. Choose Tools > Server Security. The Server Security dialog box is displayed.
4. Choose Add to create a new Server Administrator. The Add User dialog box is
displayed.
58/119
a. Enter a Domain name for the new Server Administrator.

b. Enter the Windows User/Group Name for the Server Administrator.
5. Choose Add. The Database Manager adds the new Server Administrator.
6. (Optional) To allow only Server Administrators to create a new database:
a. In the Database Restriction pane, select the New Database Creation field.
b. Choose Only Server Administrator.
7. Click Save.
Modify User Rights

When disabled, the User Management right named Read User Settings prevents users from
viewing the Roles Tab. You cannot modify Administrator rights.
To modify user's rights:
1. Choose Tools > Database Manager. The Database Manager application is launched.

2. In Database Manager, choose Tools > Server Security. The Server Security dialog box is
displayed.
59/119
3. Select the Roles tab. User roles and permissions are displayed.
4. Modify the rights of the Advanced and Basic roles as needed.

5. Click Save.
Default User Rights

Action Permissions Administrator Advanced Basic
Configure
Add Predefined Notes Add custom Notes
Edit Configuration Edit configuration
Override lock and save

Override Configuration
database
Database Management
60/119
Action Permissions Administrator Advanced Basic
Create Audit File Create audit file
l Restore, rename,
delete, and clean up
Manage Database
database
l Open audit file
Enable/disable database
Online Data Collection
and device data collection
Display
Acknowledge Alarms Acknowledge alarms
Delete Notes Delete notes
l Delete / overwrite
reference dataset
l Suppress /
Machine Health Admin unsuppress events
l Reset alarm latch
l Add / Edit / Delete
notification
Add Plot set and Plot

Machine Health User
Record
l Check historical
calculation on
addition of trended
Manage Data
measurement
l Delete Data
(Portables)
User Management
l Assign roles to user

Edit User Settings
l Add / delete users
Read User Settings View user roles and rights
1.18 Enable Data Collection
61/119
To gather data from online devices, you must enable your database for online data collection. A
database that is enabled for online data collection runs regardless of System 1 client
connections and interactions with other databases.
You can enable data collection for multiple PostgreSQL databases per System 1 Server. If using a
Proficy database, you can only enable data collection for a single database. To enable another
Proficy database on the same server, disable data collection on the active database.
The System 1 Server service automatically starts collecting data for the online database during
machine start up and shut down without waiting for you the user to open the online database.
Enabling online data collection does not change the configuration. You do not have to save
changes to the database to enable data collection.
Enable Database Data Collection
To enable online data collection, choose a method:
Machine or Devices Hierarchy

1. Select the Configure Workspace and Standard Mode.
2. Select a hierarchy locations. Choose an option:
o From the Machines hierarchy, right-click the database node.
o From the Devices hierarchy, right-click the device node.
3. Choose Online Data Collection. The online status is indicated by a check mark on the
menu.
To disable data collection, complete the same steps, and choose Online Data Collection again.
Data Import Health Icon

1. In the footer bar, click the Data Import Health icon.
2. Choose Enable | Disable Online Data Collection.
Enable Device Data Collection
You can enable or disable data collection for a specific device while a database data collection is
enabled.
To enable or disable device data collection:
1. Select the Configure Workspace and Standard Mode.

2. Select the General tab.
62/119
3. In the Devices hierarchy, select a hierarchy level:

o Devices node
o Device category node
o Device node
4. Select the Data Collection tab.

5. Click the device drop-down and choose Enabled or Disabled.
Disabled Device Behaviors

A disabled device is displayed using a gray status color.
l The Status tab does not record status changes while the device is disabled.
l The Events tab does not record new alarm events, and existing active alarms remain
active.
l Current Values mode does not display any data in the Plots tab, but historical data for the
device is still available to plot.
l No data is displayed in the Bar Graph tabs.
1.19 View Data Stores Health
Data Stores Health

Data stores health is indicated by a status icon in the footer bar. These status corresponds to the
Device Status column in the Status List tab.
63/119
Ico Health
Description Possible Solutions
n Status
Good There is enough space available to

retain data the configured long- N/A
term data store span.
Risk There is not enough space available l Increase physical disk space.
to retain data for the configured l Adjust the global storage rate.
long-term data store span. l Decrease span time.
Wrappi When disk space is low, older files

ng are deleted one by one to make
room for new data. The last two files l Increase physical disk space.
are not deleted. The wrapping l Increase disk span.
criteria must be satisfied before l Manage alarms better. To analyze
older files are deleted. This formula is existing data and how to reduce
used to determine whether disk alarm count, launch Quick
space is low: Configure Alarms.
Available Drive Space < 5 GB + Total Drive
Size * 1%
Data Occurs if the Historian Service has l Increase disk span.

Storage stopped or is not installed properly, l Increase data collection storage
Stoppe or System 1 cannot connect to the rates by device type or individual
d Historian Service. device to collect data less often.
l Decrease data collection length
within transient state.
l Increase physical disk space, use
the following formula to determine
the size of the available space:
Available Drive Space < 5GB + Total Drive
Size * 3%
1.20 Get Install Base Summary

Use the Install Base Summary tool to display a summary of the all System 1 databases on the
current server.
To create the Install Base Summary:
1. Launch Database Manager. Choose a method:

o In Windows, choose Start Menu > System 1 Database Management.
2. Choose Tools > Install Base Summary. The Database Manager displays a process dialog
box until the summary is complete.
64/119
3. The path to the completed Base Summary is displayed. The Database Manager produce a
log file and a .CSV summary file.
4. Click OK. The exported file is displayed.
65/119
2. Manage Proficy Databases

Before backing up and restoring an online database, you must understand System 1's folder
structure. For details, see Database Directory Locations.
Ask your IT department to recommend a tool compatible with Volume Shadow Copy Service
(VSS )to back up and restore online Premium and Advanced databases. For Acronis Backup and
Recovery, see Back Up and Restore Using Acronis.
Notes and Recommendations

To avoid corrupting your database and losing data, follow the instructions below. These
instructions only apply to backing up and restoring Advanced or Premium license databases.
l When setting up your system, use a separate drive to store backup files. You cannot store
backup files on the same drive that is being backed up.
l We recommend configuring scheduled back ups to ensure your system is backed up
regularly.
l Unlike Fundamental license databases, you cannot backup individual Advanced and
Premium license databases. When you back up Advanced and Premium databases, all
databases are backed up.
To Restore an
Advanced or Premium Then...
database...
On a new machine You must rename or delete an existing database with the same name.
Otherwise, the database may be corrupted and you may lose data.
On the same machine You do not need to rename or delete the database. The restore
process overwrites the existing database.
Back Up and Restore Databases on Windows

l For Windows Server 2008 R2, 2012 R2, and 2016, see Back Up and Restore Using Windows
Server.
l For Windows 7 and Windows 8.1, we recommend using third-party tools.
l When setting up your system for Windows back up and restore, use a separate drive to
house backup files. You cannot store the backup files on the same drive that is being
backed up.
2.1 Change Proficy Machine Name

If you need to change name of a machine running a Proficy database, locate your Proficy
activation code and open a case to reset the license code with Bently Nevada Technical Support.
If the database is using PostgreSQL, you do not need to change the machine name or
reset your System 1 license.
66/119
To change the machine name and prevent Proficy errors:
Step 1: Release or Reset the Proficy Activation code

1. Release the license from the System 1 Server machine.
2. Change the machine name.
3. Reboot the machine.
Step 2: Reactivate Proficy License

1. For device locked licenses:
a. Open the Proficy Common License Client.
b. Select the Advanced tab.
c. Choose the Clean license information on this computer option.
d. Choose the Clean option, and choose Confirm.
e. Once the license information has been cleaned, navigate to the Activate Licenses
tab at the top of the dialog box.
f. Select the Yes, for this computer from the GE Cloud License Server option.
g. Follow the instructions on-screen to activate the license.
h. Close the License Client.
2. For licenses leased from a local license server:
a. If the Local License Server Administration tool is not installed on your machine, run
Proficy License Manager to install it.
b. Launch the Local License Server Administration tool.
c. If the license server has not been connected:
i. Select the Server Operations tab.
ii. Select the option to edit connection settings.
iii. Enter the local license server's name or its IP address.
iv. Choose Verify to test the connection.
v. Click Save.
d. Choose Connected Clients tab.
e. Select the license assigned to the machine whose name has changed.
f. Choose Recover License.
g. Close the Local License Server Administration tool.
h. On the System 1 Server machine, open the Proficy Common License Client.
i. Navigate to the Activate Licenses tab.
j. Select the Yes, for this computer from a local license server option.
k. Follow the instructions on-screen to activate the license.
l. Close the License Client.
67/119
If you receive a storage binding broken error, clean the license using the steps for a
device locked license above.
Step 3: Update the Proficy Historian Administrator connection settings

1. Launch Proficy Historian Administrator.
2. Choose .. button:
If this screen is not displayed, choose Main to launch it.
68/119
3. From the Historian Servers dialog box, complete the following actions:
a. Select the old machine name from the list of Servers.

b. Click Remove.
c. Click Add and add the new machine name.
d. Click OK.
Step 4: Restore the Proficy Historian configuration file

1. Launch services.msc, and stop the Historian Data Archiver service.
2. Launch regedit.exe.
3. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Intellution, Inc.\iHistorian\Services\DataArchive
4. Note the data in the registry value named ARCHIVEPATH. This is the path where the *.IHC file
can be found.
5. Close regedit.exe.
69/119
6. Navigate to the ARCHIVEPATH folder you noted in step 4. This folder may be hidden. The
folder contains a .IHC file with a name containing the old machine name. There may also
be .ihc file with a name containing the new machine name.
7. Save a backup copy of each .IHC file to another location in the event of errors.
8. Delete the NEW_MACHINE_NAME_Config.ihc file.
9. Rename OLD_MACHINE_NAME_Config.ihc to NEW_MACHINE_NAME_Config.ihc.
10. From services.msc, start the Historian Data Archiver service, and restart the System 1 Server
service.
Step 5: Update the List of Recent Databases

1. Launch the System 1 client.
2. Choose File and Open. System 1 displays a list of recent databases you have used.
3. Right-click the database you wish to open, and choose Remove from connection list.
4. Choose Open Database . System 1 displays the Open Database dialog box.
5. Enter the new server name, and choose Connect. System 1 displays a list of available
database on the server.
6. Select a database from the list.
7. Choose Open.
2.2 Move Proficy Database

If you need more room to save your System 1 database, you can move the database, even if you
are already using it.
To move your Proficy database to a new directory on the same machine:
1. Back up all System 1 offline databases.

2. In System 1, open the online database you want to move.
a. Disable online data collection.
b. Close the System 1 application.
3. Open the Services Microsoft Management Console. Choose Windows > Run and enter
services . Press Enter.
4. Locate and stop the System 1 Server service.
5. Locate and stop the Historian Data Achiever service.
6. Create a folder called Stores in the new directory where the database will reside.
7. Grant full control to the account used to run the Starter service:
a. Right-click the new Stores folder and choose Properties.
b. Choose Security tab.
c. Choose Edit.
d. Choose Add.
70/119
e. Choose Locations and choose your machine from the list of available computers.
f. Enter NT Service\Starter in the object names panel.
g. Click OK.
h. Select the Starter account from the list of available groups and user names.
i. Choose Full Control from Permissions panel.
8. Choose Apply and Ok.
9. Close Properties dialog box.
10. Open Microsoft Registry Editor. Choose Windows > Run, enter regedit, and press Enter.
11. Navigate to

13. Navigate to the Stores folder designated by the value of Enterprise_Database_Location. This
displays the location of the current Stores folder.
14. Cut and paste these items from the current Stores folder to the newly created Stores folder:
o All folders containing a DbHint.text file
o The Archives folder
o The BufferFiles folder
o The LogFiles folder
15. Open Microsoft Registry Editor again.
16. Navigate to

18. Double-click Enterprise_Database_Location and update its value with the path to the newly
created Stores folder. Change
C:\ProgramData\GE Bently Nevada\System 1\Stores\
to
D:\Stores\
19. In the Registry Editor, navigate to

HKEY_LOCAL_MACHINE\SOFTWARE\Intellution, Inc.\iHistorian\Services\DataArchiver
20. Double-click ARCHIVEPATH, and update its value with the path to the Archives folder of the
newly created Stores folder.
Example
Set ARCHIVEPATH to D:\Stores\Archives.
71/119
21. In the Registry Editor, navigate to

HKEY_LOCAL_MACHINE\SOFTWARE\Intellution, Inc.\iHistorian\Service
22. Double-click BUFFERPATH and update its value with the path to the BufferFiles folder of the
Example
Set BUFFERPATH to D:\Stores\BufferFiles.
23. Double-click LOGFILEPATH, and update its value with the path to the LogFiles folder of the
Example
Set LOGFILEPATH to D:\Stores\LogFiles.
24. Using Windows Explorer, navigate to

25. Delete the file

EnterpriseStore.db
26. Move PostgreSQL data. See Move PostgreSQL Data to a New Directory After Installation.
27. Attach the Proficy databases:
o Navigate to the directory where System 1 is installed. The default installation directory
is
o Run GE.Energy.System1.RestoreManagement.exe. The wizard guides you through a series of

steps to stop services, finalize restoration process, and add required permissions.
o When complete, click Finish. The Restore Manager starts the System 1 Server Service
and the Historian Data Achiever service.
o Re-assign the System 1 Licenses from System 1 License Manager to the server in the
new location.
28. Launch System 1 application.
29. Open your online database to verify it has been moved successfully. Close the online
database.
30. Open your offline databases to verify you can access the data. If you cannot open an
offline database, restore it from the backup.
Move PostgreSQL Data to a New Directory After Installation

To move the PostgreSQL folder to a new directory on the same machine:
2. Locate and stop the PostgreSQL and System 1 Server services.
72/119
3. In Windows File Explorer, copy the PostgreSQL folder to a new location.
Example
Copy C:\ProgramData\GE Bently Nevada\System 1\Stores\PostgreSQL to D:\Stores\PostgreSQL.
4. Grant full control to the account used to run the System 1 Server service:
a. Right-click the newly created PostgreSQL folder and choose Properties.
b. Click Security tab. In the Group or user names pane, click Edit. The Permissions
c. Click Add. The Select Users, Computers, Service Accounts or Groups dialog box is
displayed.
d. Click Locations. The Locations dialog box is displayed.
e. Select your machine and click OK. The Select Users, Computers, Service Accounts
or Groups dialog box is re-displayed.
f. In the Enter the object names to select field, enter NT Service\Starter.
g. Click OK. The Permissions dialog box is re-displayed.
h. In the Groups or user names pane, select the Starter account.
i. In the Permissions pane, choose Full Control.
j. Click Add. The Select Users, Computers, Service Accounts or Groups dialog box is
displayed.
k. Click Locations. The Locations dialog box is displayed.
l. Select your machine and click OK. The Select Users, Computers, Service Accounts
or Groups dialog box is re-displayed.
m. Choose Locations, and choose your machine from the list of available computers.
n. In the Enter the object names to select field, enter Network Service.
o. Click OK. The Permissions dialog box is re-displayed.
p. In the Groups or user names pane, select the Network Service account.
q. In the Permissions pane, choose Full Control.
5. Open Microsoft Registry Editor. In Windows Start, enter regedit.
6. Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\postgresql-x64-9
7. Double-click ImagePath and modify the directory value after -D option. You must enclose the
new directory path in double quotes.
Example
ImagePath may contain:
73/119
"C:\Program Files\PostgreSQL\9.6\bin\pg_ctl.exe" runservice -N "PostgreSQL"

-D "C:\Stores\PostgreSQL96" -w
Change the directory path enclosed in double quotes after -D option:
"D:\Stores\PostgreSQL96"
8. Navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\services\postgresql-x64-9.
10. Navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-9.
13. Start the PostgreSQL Server service.
14. Start the System 1 Server service.
2.3 Database Directory Locations

Before Beginning a Backup
l When setting up your system, use a separate drive to store backup files. You cannot store
the backup files on the same drive that is being backed up.
l We recommend configuring scheduled back ups to ensure your system is backed up
regularly.
l Unlike Fundamental license databases, you cannot backup individual Advanced and
Premium license databases. When you back up Advanced and Premium databases, all
databases are backed up.
To restore an
Advanced or Then...
Premium database...
l You must rename or delete an existing database with the same

name. Otherwise, the database may be corrupted and you
may lose data.
On a new machine
l You can open only the newly restored database on that
computer. Existing and old databases are no longer available
on the new machine.
l You do not need to rename or delete the database. The restore

process overwrites the existing database.
On the same machine
l Where the original database resides, you can open the newly
restored database as well as the original one.
74/119
We do not recommend using Windows back up and restore tools due to their limitations. For
Windows 7 and Windows 8.1, we recommend using third-party tools.
Default Installation Folder Structure

The folder structure for the default installation is:
C:\ProgramData\GE Bently Nevada\System 1\AuthorizationServer

C:\ProgramData\GE Bently Nevada\System 1\Stores\Archives †
C:\ProgramData\GE Bently Nevada\System 1\Stores\BufferFiles †
C:\ProgramData\GE Bently Nevada\System 1\Stores\LogFile†
C:\ProgramData\GE Bently Nevada\System 1\Stores\PostgreSQLXX ‡
C:\ProgramData\GE Bently Nevada\System 1\Stores\<Database Name 1>
C:\ProgramData\GE Bently Nevada\System 1\Stores\<Database Name 2>
† Exists only if Proficy is the default Historian.

‡ PostgreSQLXX refers to either PostGreSQL96 or PostgreSQL11. The PostgreSQL96 folder only
exists if a backup of System 1 database was created on or upgraded from System 1 19.1 or
earlier versions.
Custom Installation Folder Structure

The folder structure for a database stored in a custom location is:
C:\ProgramData\GE Bently Nevada\System 1\AuthorizationServer

D:\<Custom Folder Name>\Archives †
D:\<Custom Folder Name>\BufferFiles †
D:\<Custom Folder Name>\LogFile†
D:\<Custom Folder Name>\PostgreSQLXX ‡
D:\<Custom Folder Name>\<Database Name 1>
D:\<Custom Folder Name>\<Database Name 2>
† Exists only if Proficy is the default historian.

‡ Exists
If you are restoring a custom installation folder structure to the same machine, restore only this
folder structure:
C:\ProgramData\GE Bently Nevada\System 1
If restoring to a new, different, or reformatted machine, System 1 Restore Manager creates this
folder structure:
Locate the System 1 Database

To locate your System 1 database:
1. Choose Tools > Database Manager.

75/119
3. Select the Back Up tab.

4. Select a Database using Browse. Database Path List in Online Database pane.
5. In the Online Database pane, choose Copy Path to save the Database Path List. To back
up a database, all the folders in the database path list are necessary.
Examples
l For default installations, database path list is:

l For custom installations, database path list includes both parent folders:
D:\<Custom Folder Name>
Default Database Restore Location

The System 1 Database Restore Manager places the restored database in these folders:
l For default installations, the database is located here:

l For custom installations, the database is at the path you selected.

76/119
2.4 Restore Databases When Installation Folder Structures

Differ
Restore Default Installation to Custom Installation
When you back up a database with the default installation folder structure, but the destination
machine uses a custom installation folder structure, complete these restore operations:
Restore Operation 1
1. Follow the restore process for your operating system.

2. When selecting items to restore, choose these child folders:
AuthorizationServer
EnterpriseServer
3. When selecting the recovery destination, use the file path identified by the System 1
Restore Manager:
4. Complete the restore operation.
Restore Operation 2

2. When selecting items to restore, choose all of the child folders of the Stores folder (Archives,
BufferFiles , LogFiles , PostGreSQL96, and your database folders).
Restore Manager.
Restore Custom Installation to Default Installation

When you back up a database with a custom installation folder structure, but the destination
machine uses the default installation folder structure, complete these restore operations:
Restore Operation 1

2. When selecting items to restore, choose the child folders:
C:\ProgramData\GE Bently Nevada\System 1AuthorizationServer
C:\ProgramData\GE Bently Nevada\System 1EnterpriseServer
Restore Manager.
77/119
Restore Operation 2

2. When selecting items to restore, choose all of the child folders of the D:\<Custom Folder Name>
folder (Archives, BufferFiles, LogFiles, PostGreSQL96, and your database folders).
3. Create a new folder named Stores in this folder.
4. When selecting the recovery destination, use this file path.

C:\ProgramData\GE Bently Nevada\System 1\Stores
2.5 Back Up and Restore Using Acronis

Use the third-party application Acronis Backup and Recovery to restore data to machines with
different operating systems than the machine whose data was backed up. You can choose
other third-party tools.
These steps describe how to use Acronis Backup and Recovery v11.5. For other versions, refer to
the software's documentation.
One-Time, Full Back Up

To complete a one-time, full back up:
1. Launch Acronis Backup and Recovery.

2. Select the Back up now from the main screen.
3. From What to back up, choose Items to back up..
4. To identify the location of the folders you need to back up, see See Database Directory
Locations on page 74.. Select the locations displayed in the What do you want to back
up? screen.
5. Enable Show hidden files and folders on the machine where your files reside.
6. From Data to Back Up, choose Data to back up drop-down and choose Files.
7. From the Data to Back Up dialog box, select folders to back up. Click OK.
8. From the Back up now dialog box, choose Location.. from the Where to back up.
9. Choose where you want to store your backup files, and choose OK.
10. From the Back up now dialog box, click Backup options.. in the Plan parameters section.
11. Choose Volume Shadow Copy Service. Choose Use Volume Shadow Copy Service (VSS).
Click OK.
78/119
12. From the Back up now dialog box, choose OK to start backing up. The backup operation
must be completed successfully.
Troubleshoot Backup Status

Ensure the status of back up operation is Succeeded or Completed. When the status is
Succeeded with Warnings, Error, or Failed, the backup may be inconsistent, or there may have
been a failure to back up all of the selected files.
To resolve this problem:
1. Select the failed back up operation and choose Details.

2. Perform the recommended corrective action.
3. Retry the back up operation.
4. Perform recovery only when the status of back up operation is Succeeded or Completed.
Configure a Scheduled Back up (Recommended)

To Configure a scheduled back up:
1. Choose Create backup plan from the main screen.

2. From What to back up, choose Items to back up..
3. Enable Show hidden files and folders on the machine where you files reside.
4. From the Files to backup dialog box, choose Files/Folders.
5. From the Data to Back Up dialog box, select folders to back up. Click OK.
6. From the Create backup plan dialog box, choose Where to back up and Location..
7. Choose a location to store your backup files. Click OK.
8. From the Create backup plan dialog box, choose Plan parameters and Backup options..
9. Choose Volume Shadow Copy Service. Choose Use Volume Shadow Copy Service (VSS)
option. Click OK.
10. From the Create backup plan dialog box, choose How to back up and Schedule..
11. Create a back up schedule. Click OK.
12. From the Create backup plan dialog box, choose How to back up and Retention Rules.
Choose the option that best suits your backup requirements.
13. From the Create backup plan dialog box, choose OK to start backing up. The backup
operation must be completed successfully.
79/119


Prepare to Restore System 1

To restore System 1, launch the System 1 Restore Manager.
Launch System 1 Restore Manager

To prepare the machine for restoration:
1. Navigate to the System 1 installation path.

2. Right-click on GE.Energy.System1.RestoreManagement.exe and run as administrator.
3. Click Next when System 1 Restore Manager opens. The tool shuts down all data
acquisition services and backs up the historian configuration database in preparation for
the recovery process.
4. Once preparations have been completed successfully, click Next and then OK.
Restore from a Backup

To restore from a backup:
1. In Windows File Manager, enable Show hidden files and folders on the machine.
2. Launch the Acronis Backup & Recovery tool.
3. Select the Recover option from the main screen.
4. From the Recover data dialog box, choose What to recover and Select data..
5. In Windows, navigate to the backup location you selected during the back up process.
6. Choose the files to recover. If file paths of differing drive names were backed up, recover
each drive path separately. For example, the custom installation folder structure might
have file paths with different drive names. When selecting the database files, only select
the child folders and not the parent folder to avoid nesting the folders. For example, select
the folders in
but not
80/119

Click OK.
7. From the Recover data dialog box, choose Where to recover and Destination. Set the
recover destination using the Restore to following path entries found in the System 1
Restore Manager. If you are restoring to a different installation folder structure, see
Database Directory Locations. Click OK.
8. From the Recover dialog box, choose OK to start recovering the data.
Complete Restore
When restoring a database, <machine name>_Config.ihc file must be in the Archives
folder. After completing the restore operation, if this file has been removed accidentally,
restore it from your database backup before finalizing the restoration.
When the restoration is complete:
Restore to Same Location on Same Machine

If you restored to the same location on the same machine:
1. Click Next in System 1 Restore Manager.

2. Click Finish.
You can now open your restored databases.
Restore to Different Location or New Machine

If you restored to a different location on the same machine or to a new machine:

2. Click Next.
This step removes user profiles on all databases. You must recreate the profiles
later. The current user is added as an administrator to the restore databases.
3. Once the operation completes, Click Finish.

4. Recreate the user profiles on all of the restored databases. See Security Manager topic in
System 1 Help.
5. Re-enable databases previously enabled for Online Data Collection.
6. Update the credentials of all password protected devices. See the Authenticating Device
topic in System 1 Help.
81/119
Confirm Restore
After a successful restore operation:
1. Launch System 1.
3. Confirm the list of available databases include the restore databases.
If the restored databases do not appear or if the restore operation fails:
1. Ensure proper folders are selected and the restored path is correct.
2. If the restored path is not in the expected Restore to following path: file path format
displayed in the System 1 Restore Manager, execute the first step of the System 1 Restore
Manager. Then move the restored folders to the expected location.
3. Perform the remaining steps in System 1 Restore Manager tool.
2.6 Back Up and Restore Using Windows Server

You must be a member of the Backup Operators or Administrators group to back up and
restore databases using Windows Server operating systems.
Install and Launch Windows Server Backup

Windows Server 2008 R2
1. Open the Server Manager.
2. From the Features section, click Add Features.
3. From the Add Features Wizard dialog box, select these options:
o Windows Server Backup Features
n Windows Server Backup
n Command-line Tools
4. Click Next.
5. On the confirmation page, click Install.
6. After successfully installing, close the dialog box.
7. From the Storage section of the Server Manager, choose Windows Server Backup.
8. Expand Windows Server Backup in the Actions pane on the right side.
o For a one-time back up, click Backup Once..
o For a scheduled back up, click Backup Schedule..
Windows Server 2012 R2 and 2016

1. Launch the Server Manager application.
2. From the Dashboard section of the Server Manager, click Add roles and features.
3. From the Before You Begin screen of the Add Roles and Features Wizard dialog box, click
Next.
82/119
4. From the Installation Type screen, choose Role-based or feature-based installation, and

click Next.
5. From the Server Selection screen, select a destination server from the Server Pool, and
click Next.
6. To skip the Server Roles screen, click Next.
7. From the Features screen, choose Windows Server Backup, and click Next.
8. From the Confirmation screen, click Install.
9. You can keep track of the installation progress from the Results screen.
10. From the Tools menu of the Server Manager, choose Windows Server Backup.
11. With Local Backup selected on the left side, perform one of these actions:
o For a one-time back up, click Backup Once.. from the Actions pane on the right side.
o For a scheduled back up, click Backup Schedule.. from the Actions pane on the right
side.
One-Time (Full) Back Up

1. From the Backup Once Wizard, ensure that Different Options is selected, and click Next.
2. Select the Custom option, and click Next.
3. Click the Add Items.
4. To identify the location of the folders you need to back up, see See Database Directory
Locations on page 74. Click OK.
5. Enable Show hidden files and folders on the machine.
6. Click Next.
7. Select the drive or network share where you want to store the backup files.
8. If you choose the Local drives option, choose the drive to which you want to back up from
the Backup destination drop down.
9. From the Confirmation screen, click Backup.
10. The backup is created. You can monitor the status from the Backup Progress screen.


Configuring a Scheduled Back Up (Recommended)
83/119
If you decide to switch back up strategies from One-Time to Scheduled, the destination drive for
the backup file are reformatted. If you have previous One-Time backups located on this drive,
We recommendthat you move them to another drive as they are overwritten and lost.
1. From the Backup Schedule Wizard dialog box, click Next.

2. Select the Custom option, and click Next.
3. Click the Add Items. This step is similar to the Backup Once Wizard.
4. Identify the location of the folders you need to back up, and click OK. Enable Show hidden
files and folders on the machine.
5. Click Next.
6. From the Specify Backup Time screen, select a time to create the backup. We
recommendto chose a time when the system is minimally loaded for optimal
performance. Click Next.
7. From the Specify Destination Type screen, choose the appropriate destination, and click
Next. If you choose to back up to a shared network folder, you are prompted to enter the
folder network path and verify your user credentials.
8. Validate the Confirmation screen, and click Finish.
9. View the summary of your scheduled backup.


Prepare for Restoration

Launch System 1 Restore Manager
To prepare the machine for restoration:
1. Navigate to the System 1 installation path.

2. Right-click on GE.Energy.System1.RestoreManagement.exe and run as administrator.
3. Click Next when System 1 Restore Manager opens. The tool shuts down all data
acquisition services and backs up the historian configuration database in preparation for
the recovery process.
4. Once preparations have been completed successfully, click Next and then OK.
84/119
Restore
Enable Show hidden files and folders on the machine.
Launch Recover Wizard using Server 2008

1. From the Storage section of the Server Manager, choose Windows Server Backup.
2. Expand Windows Server Backup in the Actions pane on the right side, and click Recover..
Launch Recover Wizard using Server 2012

1. From the Tools menu of the Server Manager, choose Windows Server Backup.
2. With Local Backup selected on the left side, click Recover.. from the Actions pane on the
right side.
Using the Recover Wizard

1. In the Recover Wizard, select either This server (SERVERNAME) or A backup stored on
another location, depending on where the backup file is located. If you choose This server
(SERVERNAME), skip the next few steps and go to Step 5 below.
2. For a backup stored on another location, you need to specify the location type: Local
drives or Remote shared folder.
3. Depending on the type of location you specified, specify Remote Folder or Select Backup
Location. This location is the folder to which you backed up. It contains a
"WindowsImageBackup" child folder.
4. Click Next to continue.
5. Select the date and time of the backup you want to restore, and click Next.
6. On the Select Recovery Type screen, choose Files and folders, and click Next.
7. Expand the Available items folders to locate the folders you backed up, and click Next. If
file paths of differing drive names were backed up, ensure that you recover each drive path
separately.
For more information about custom drive names, Database Directory Locations
Finalize the Restoration

If you are using System 1 19.1 or older with a Proficy database, when restoring a database,
<machine name>_Config.ihc file must be in the Archives folder. After completing the
restore operation, if this file has been removed accidentally, restore it from your database
backup before finalizing the restoration.
To restore a database backup from any prior version of System 1 to a new installation of
System 1 19.2, and the backup was created using Windows or Acronis backup, you must
first migrate PostgreSQL.9.6 to PostgreSQL11.
You can restore a database backup created using Windows or Acronis backup, but
85/119
System 1 19.2 does not allow you to open a Proficy database on a machine using Postgres
as the default datastore.
Complete these steps after the restoration is complete.
Restore to Same Location on Same Machine

If you restored to the same location on the same machine:

2. Click Finish.
You can now open your restored databases.
Restore to Different Location or New Machine

If you restored to a different location on the same machine or to a new machine:

2. Click Next.
This step removes user profiles on all databases. You must recreate the profiles
later. The current user is added as an administrator to the restore databases.
3. Once the operation completes, Click Finish.

4. Recreate the user profiles on all of the restored databases. See Security Manager topic in
System 1 Help.
5. Re-enable databases previously enabled for Online Data Collection.
6. Update the credentials of all password protected devices. See the Authenticating Device
topic in System 1 Help.
Confirm Restore
After a successful restore operation:
1. Launch System 1.
3. Confirm the list of available databases include the restore databases.
If the restored databases do not appear or if the restore operation fails:
1. Ensure proper folders are selected and the restored path is correct.
2. If the restored path is not in the expected Restore to following path: file path format
displayed in the System 1 Restore Manager, execute the first step of the System 1 Restore
Manager. Then move the restored folders to the expected location.
3. Perform the remaining steps in System 1 Restore Manager tool.
86/119
3. Configure Database Replication

Why Replication is Necessary
Data replication copies data from one System 1 database to another, making data available
across one or more network architectures. Replication works around two issues necessitated by
data security:
l System 1 acquires data from devices such as 3500 monitors that reside in the field on a
process control network. On these networks, elevated security controls limit or block
access to System 1 data and tools.
l Data diodes are used in secure topologies to permit unidirectional communication from
more secure to less secure networks.
These network security practices can prevent System 1 clients from accessing data residing on
different networks. The replication model of moving data and making it available in different
locations across multiple security layers allows you to access critical condition monitoring
information in a secure and controlled manner.
Once the data has been replicated to an accessible location, you can use display information in
a System 1 client and perform condition monitoring and root cause analysis. You cannot
configure assets and devices or modify data on System 1 clients.
Data Replication Requirements

To replicate data, System 1 uses Secure FTP (SFTP). The replication process uses a source or
transmitter database and a destination or receiver database.
Transmitter Database
The transmitter database is the source database to be used for data replication that is
connected to the online devices, OPC sources, and portable devices. This is the System 1 data
acquisition system that collects and store the data for condition monitoring.
Receiver Database
The receiver database is the duplicated database whose primary data source is the files
delivered to the receiver Drop Location folder via either a firewall or data diode file transfer
solution.
You can configure System 1 to define the following:
l Source database
l Destination database
l The path of source replication folder
l The path of destination replication folder
l Type of data replicated
l How often data is replicated
87/119
You must also configure third-party software services and data diodes to transfer data files from
the replication folder on the process control network to the replication folder on the business tier
network.
To replicate data, you must enable online data collection.
How Data Replication Works

You must define the configuration used to collect the data on the transmitter System 1
database. The receiver System 1 can only view the replicated data. For related
information, see Setup and Limitations
1. After the database is configured and data collection is enabled, the transmitter database
gathers data from the monitored devices and assets.
2. The System 1 Replication Service pulls configuration data, events, and status information
from the transmitter database.
3. The Replication Service packages and writes the data to the transmitter Data Location
folder.
4. Either secure file transfer methods or data diodes support tools are used to move the files
across the network to the receiver Data Location folder.
The files are later read into the receiver database. The updated data is stored in the receiver
Historian on the business tier network and can be used for analysis and decision making.
Data Replication File Names and Extensions

The transmitter database on the process control network creates the files listed below and writes
them to a source replication folder. The Database ID between the priority number and the
sequence number is a fixed-length alphanumeric string.
88/119
Replicated Data File Name and Extensions
Heartbeat P010_<enterpriseGUID>_<sequenceNumber>.S1hb
Replication properties P015_<enterpriseGUID>_<sequenceNumber>.S1rp
Configuration changes P020_<enterpriseGUID>_<sequenceNumber>.S1c
Alarm events P040_<enterpriseGUID>_<sequenceNumber>.S1ae
Alarm & transient P050_<enterpriseGUID>_<sequenceNumber>.S1atd
Trend measurement P060_<enterpriseGUID>_<sequenceNumber>.S1tsd
Trend spectrum & waveform P070_<enterpriseGUID>_<sequenceNumber>.S1twd
System events P080_<enterpriseGUID>_<sequenceNumber>.S1se
Reference data P090_<enterpriseGUID>_<sequenceNumber>.S1rd
System 1 configuration export files <EnterpriseName>_<DateAndTime>.S1CFG
Portable data P075_<enterpriseGUID>_<sequenceNumber>.S1pd
Retransmitted Alarm & Transient Data P100_<enterpriseGUID>_<sequenceNumber>.S1hatd
Retransmitted Trend Static Data P110_<enterpriseGUID>_<sequenceNumber>.S1htsd
Retransmitted Trend Waveform Data P120_<enterpriseGUID>_<sequenceNumber>.S1htwd
Retransmitted Offline/Portable Data P130_<enterpriseGUID>_<sequenceNumber>.S1hpd
Template Configuration Changes P025_<enterpriseGUID>_<sequenceNumber>.S1ct
Data Replication Health

The data replication status is displayed in the footer bar:
l To determine replication ingestion health for a receiver database, click the Data Import
Health icon .
l To determine data replication health for a transmitter database, click the Data Export
Health icon .
Replication Service Health Status Messages

System 1 displays messages to indicate the health and status of the replication service. Unique
conditions cause each message to be displayed as a System Health Event and indicated in the
health status icon. Before most of these messages can be cleared, a healthy status must persist
for a variable amount of time, ranging from a few minutes to several hours.
89/119
Message Description
Displayed when the replication service does not run for one
minute. On the receiver, this message can take up to five minutes
to display. The receiver database ingests events like this from the
Replication service is not
transmitter, which can be confusing. If unsure, check the Source
running.
Computer Name column in the System Health page of System 1
for details. This message is cleared immediately when System 1
detects that the replication service is running again.
Error ingesting replicated

Displayed when the receiver is unable to ingest replicated files.
files
Missing replicated Displayed if after one minute a missing sequential data file is not
configuration file received.
File ingestion rate less than Displayed if the receiver takes longer than five seconds to ingest a
configured value. data file.
Displayed when the replication service waited one minute for a

Missing replication data file
file to arrive, and subsequent files have already arrived.
File ingestion rate less than

Displayed when it takes longer than five seconds to ingest a file.
configured value
Displayed if the receiver attempts to ingest a corrupt replicated

Detected corrupt
data file. This can occur if a data file is properly constructed and
replication file
zipped or due to network transmission error.
Displayed on the transmitter if the transmitter fails to replicate a

Error replicating files
data file.
Displayed if the number of replicated data files in the source

replication folder exceeds the threshold of 20 files. Exceeding the
Error transmitting threshold indicates a problem with transmitting the files from the
replicated files source replication folder to the target folder on the Rx network.
This message is immediately cleared when the threshold file
count is no longer exceeded.
File replication rate less Displayed if the replication service takes longer than five seconds
than configured value to replicate a data file.
Displayed on the receiver if no new files are received by the Rx for

Error receiving files ten minutes in its target replication folder. This message is
immediately cleared upon receiving new files.
To view replication service health and status messages:
l Select the System Health tab.

l Select the Data Import Health icon in the application's footer bar to determine
replication ingestion health.
90/119
l Select the Data Export Health icon in the application's footer bar to determine data
replication health.
About File Transfer

Our research has found that file transfer methods are supported by all major data diode
vendors. We offer a single solution that works with the leading data diode vendors, such as OWL
and Waterfall. Also, System 1 operates in multiple reference architectures that leverage the use of
routers and firewalls.
Using the file transfer approach, we can identify the following issues while transmitting data
across network layers:
l Detect the loss of data

l Prioritize how the data is transferred
l Detect data or file tampering
l Enable the solution scale in a controlled way
l Enable effective verification and validation of the overall solution
Logical Architecture
The following picture represent a logical architecture depicting the relationship between the
transmitter system on the process control network and the receiver system on the business
network via a firewall:
91/119
The following picture represents a logical architecture depicting the relationship between the
transmitter system on the process control network and the receiver system on the business
network via an OWL data diode using the RFTS software service:
92/119
3.1 Setup and Limitations

Setup Criteria
The following criteria applies to System 1 v16.2 or newer.
Before you configure your database for replication, Enable Data Collection.
Limitations
When replicating data, these limitations exist:
Transmitter Database Configuration Updates

l Configuration update files (*.S1c) are sent to the drop folder in two minute intervals and
contain all configuration changes made during that time period.
l If data associated with these configuration changes is replicated prior to the configuration
update file, the data will wait to be consumed until the configuration update files are
available for consumption.
l All configuration files must be consumed in the order of their creation.
Failed Replication Wait Time
93/119
l If replicated data files fail to replicate or arrive on the receiver system, the receiver
database institutes a one minute delay before resuming processing the remaining files.
This is a default wait time to verify the receipt of data.
Transmitter Replication Service Not Running

l If the System 1 Replication Service is not configured and running on the transmitter
computer when an alarm or start up/shutdown event occurs, the data is not replicated.
Starting the replication service after the alarm or start up/shutdown event does not
retrieve previously stored data.
l Starting the transmitter System 1 Replication Service after it has not been running does
not replicate previously stored trend, alarm, and transient data. However, previous alarm
events is replicated.
Version Requirements
l The System 1 receiver installation must be at least version 16.2.
l The System 1 receiver installation must be the same version as the System 1 transmitter
system.
Use of Enterprise Impact

l Before installing Enterprise Impact, ensure the replication system is configured.
l Upon installation, the Enterprise Impact proxy automatically detects if it is on a transmitter
or receiver system.
o On a transmitter system, detect device DHP status is enabled.
o On a receiver system, detect device DHP status is disabled.
For complete information, see the Enterprise Impact User Guide (document 115M4065) available
from Bently Nevada Technical Support.
3.2 Configure Transmitter Database

To configure the transmitter database:

3. Choose Back Up and browse for a Database.
4. Choose a Destination for the backup file.
5. If you want to configure databases offline and deploy them on a different computer, in the
Database pane, choose Back Up Configuration Only.
6. Click Back Up. Even if you created the original transmitter database from an existing S1CFG
file, you need a new S1CFG file to create the receiver database.
7. After the back up process finishes, copy the S1CFG file to a location accessible by the
receiver computer.
8. Select the Database Replication pane.
94/119
10. Select the Database to replicate. It must be the same as the one your previously selected.
11. Set the Replication Type to Transmitter. Additional fields are displayed.
12. In the General pane, choose Data Location, and click Browse. This folder is the drop
location from which the data diode transfers data to the receiver computer.
o From Data to Include, choose:
n Trend data.
n Alarm and Start up/Shutdown data.
o From Events to Include, choose:
n Alarms: Replicates all alarm events.
n System Health: Replicates all system events.
14. Click Save.
3.3 Configure Receiver Database

Database Manager Configuration
If the transmitter database has historical data, you can use the Database Manager to create a
full backup of that database and restore it on the receiver machine. If it is a Proficy database, you
can use Windows Backup or any third-party Volume Shadow Copy Service (VSS) tool to back up
and restore the database.
To configure the receiver database:
1. Launch Database Manager.
2. Select the Back Up and Restore tab.
3. From the Restore tab, select the S1CFG file you created as the Backup File.
4. Check Create Replicated Database. Choose Restore. If Create Replicated Database is not
checked, and you create a transmitter database from the S1CFG file, you must delete the
restored database and repeat this operation with Create Replicated Database checked.
5. After the restore process finishes, select the Database Replication tab.
6. In the General pane, select the restored Database.
7. Ensure Replication Type is Receiver. If you have configured the transmitter (Tx) and the
receiver (Rx) databases correctly, Replication Type is set to Receiver automatically and
cannot be modified. Replication Type is set to Receiver when these conditions apply:
o On the transmitter (Tx) side, you must back up the configuration only. Check
Backup > Backup Configuration Only.
o On the receiver (Rx) side, you must create a replicated database. Check Restore
> Create Replicated Database.
8. In the General section, select the Data Location folder. This folder is the drop location to
95/119
which the data diode transfers data from the transmitter computer.
9. Click Save.
Configure Replication Service

To configure the replication service:
1. Create a new local user account with administrator privileges on the domain or
workgroup used by the System 1 Replication Service. We recommend using this user
account only for the replication service.
2. Open the System 1 database you want to configure.
3. Launch System 1 Security Manager.
4. Use System 1 Security Manager to grant the newly created user Administrator rights on
the database being replicated. If the System 1 Replication Service is not modified to run
under a specific user account with System 1 administrator rights, the service starts, but
errors are logged to the Windows application event log.
5. Navigate to the %ProgramData%/GE Bently Nevada/System 1 directory in Windows Explorer.
6. Right-click on the folder in Windows Explorer and choose Properties.
7. Select the Security Tab.
8. In Locations.., select the computer name.
9. In Enter the object names to select, grant the newly created user account Full Control.
10. Click OK and close the Properties dialog box.
11. For details on how to grant permissions for both workgroup and domain scenarios, see
Grant Database Permissions in the System 1 User Guide (109M8639).
Start Replication Service

To start the replication service:
1. Launch the Windows Services.

2. Locate the service named System 1 Replication Service.
3. Right-click the service and choose Properties.
4. In the General tab, open the start up type drop-down list box and choose Automatic
(Delayed Start).
5. Navigate to Log On tab.
6. Select the This account: option and enter the user name created in the first step of the
Configure Replication Service steps above.
7. Enter the password for the user account.
8. Navigate to Recovery tab and change the following drop-down list box to Restart the
Service:
96/119
o First failure
o Second failure
o Subsequent failures
9. Click OK.
10. Start the service.
Connect OPC Server on a Replicated Network

The credentials needed to access an OPC server are unique to every computer that requires a
connection to the server. The credentials cannot be replicated to the receiver (Rx) machine.
To configure an OPC server on the transmitter (Tx) database on a replicated network:
1. In System 1, open the transmitter (Tx) database connected to an OPC server.

2. In the Devices hierarchy, choose OPC device. The General > OPC Server properties are
displayed.
3. In the Server Location field, choose Replicated Network.

4. Choose File > Save.
On the receiver (Rx) machine:
1. Run the OPC Authentication Manager. Navigate to:

2. Run System1.OpcAuthenticationManager.exe. The OPC Authentication Manager is displayed.
97/119
3. Enter the authentication information:

o Domain name
o Server name
o User name
o Password
4. Click Save. The information is saved in a * .S1opc file. The OPC client uses this file to connect
to the OPC server.
3.4 Configure Replication Service

Before you configure the replication service, you must first create a new user with Administrative
rights.
Create a New Administrative User

To create the new user:
1. In Windows:
a. Create a new user account on the domain or workgroup used by the System 1
Replication Service.
b. Give the user administrator privileges. We recommend using this account only for
the replication service.
2. Navigate to the Program Data directory on your operating system. In Windows Explorer,
enter %ProgramData% and the directory is displayed.
3. Navigate to:
4. To give the newly created user account full access to this folder, right-click on the System 1
folder in Windows Explorer:
a. Choose Properties.
b. Select the Security tab.
c. In Locations.., select the computer name.
d. In Enter the object names to select, grant the user Full Control.
e. Click OK
5. The Properties dialog box is displayed. Close it.
For details on how to grant permissions for both workgroup and domain scenarios, see Grant
Database Permissions in the System 1 Bently Performance User Guide (document 142M7884).
Configure Data Replication Service

You can configure data replication for databases 16.2 or later. If your database is older, you must
first upgrade your database. After you upgrade to System 1 18.2 or later versions, historical
portable data is replicated when you start the System 1 replication service the first time.
98/119
To configure the replication setup for a database or to view an existing configuration:
1. Open the Database Manager.

2. Choose Database Replication tab.
3. In the Database Replication tab, select a replication type for your database.
Select this
If you: Replication Description
Type
Are using an None or The database does not use data replication. If
online database transmitter replication type is not set, the default value is none.
Have backed up The database creates the data for transmission. Only
only configuration an online database can be a transmitter. When a
Receiver
data into a database in transmit mode goes offline, it does not
database replicate any new data.
Have restored a
database as a Receiver The database receives the transmitted data.
receiver
4. In the General pane:

a. Click Browse and select a database.
b. Click Browse and select a data location. The data location is a folder where
replicated files are stored.
5. If you are creating a transmitter database, configure these options:
o File creation rate is the maximum rate at which data files are created when new
data is available. The default value is 20 seconds. You can modify the value to
minimize disk access.
o Data to Include
n Trended Variables. To migrate the database, you must replicate all trended
variables. Choose All.
n Spectrum and Waveforms. Trend and waveform data can be configured for
replication at different time intervals. High speed replication of trended
measurements is also available. To enable this, choose All. When enabled,
spectrum and waveform measurement data is collected and stored at the
rate configured for the device.
n Alarm and start up / shutdown
o Events to Include. If you enable Alarms and System Health events for replication,
System 1 replicates only events that are active when you start the replication service.
6. Click Save.
Start Replication Service

To start the replication service:
99/119
1. Launch the Windows Services.

2. Locate the service named System 1 Replication Service.
3. Right-click the service and choose Properties.
4. In the General tab, open the start up type drop-down list box and choose Automatic
(Delayed Start).
5. Navigate to Log On tab.
6. Select the This account: option and enter the user name created in the first step of the
Configure Replication Service steps above.
7. Enter the password for the user account.
8. Navigate to Recovery tab and change the following drop-down list boxs to Restart the
Service:
o First failure
o Second failure
o Subsequent failures
9. Click OK.
10. Start the service.
3.5 Configure Transmitter Database

To configure the transmitter database:

3. Choose Back Up and browse for a Database.
4. Choose a Destination for the backup file.
5. If you want to configure databases offline and deploy them on a different computer, in the
Database pane, choose Back Up Configuration Only.
6. Click Back Up. Even if you created the original transmitter database from an existing S1CFG
file, you need a new S1CFG file to create the receiver database.
7. After the back up process finishes, copy the S1CFG file to a location accessible by the
receiver computer.
8. Select the Database Replication pane.
10. Select the Database to replicate. It must be the same as the one your previously selected.
11. Set the Replication Type to Transmitter. Additional fields are displayed.
12. In the General pane, choose Data Location, and click Browse. This folder is the drop
location from which the data diode transfers data to the receiver computer.
100/119
o From Data to Include, choose:
n Trend data.
n Alarm and Start up/Shutdown data.
o From Events to Include, choose:
n Alarms: Replicates all alarm events.
n System Health: Replicates all system events.
14. Click Save.
3.6 Configure Remote File Transfer Service

Consult the documentation provided with your selected data diode to enable communication
between the transmitter Data Location file and the receiver Data Location file.
If using the OWL Remote File Transfer Service, the Client must be installed on the
transmitter system and the Server must be installed on the receiver system. Typically, the
transmitter system is on the process control network while the receiver is on the business
network.
OWL Parallel Transfer Setup Notes

If you are configuring an OWL data diode for parallel file transfer, the receive side needs to be
configured to overwrite existing files. If this is not configured, any duplicated file transferred are
renamed with its file name appended with the date and time, as illustrated:
Before:
P060_5af499d2e7354a24a01769bcb395edfa_0000005389.S1tsd
After:
P060_5af499d2e7354a24a01769bcb395edfa_0000005389-20161012-112408-000.S1tsd
Renamed files are not consumed by the receiver database and accumulate. This configuration
is not recommended as this consumes hard drive space.
To correct this:
1. Open the runtcpfileserver.bat file in a text editor like Notepad.

2. Remove the -t command from the line set PARAMS= %PARAMS% -t. This line is about 35 lines
from the bottom of the file.
3. Save the .BAT file.
4. Run the .BAT file.
3.7 Create SFTP Connection
101/119
You need to create a secure file transfer protocol (SFTP) connection on Windows. You can use
either Bitvise SSH or OpenSSH to create a SFTP connection. We recommend Bitvise.
Create Bitvise SSH Server Connection

To create a secure Bitvise SSH server connection:
1. Download Bitvise SSH server from here:

https://www.bitvise.com/ssh-server-download
2. To install OpenSSH, follow the instructions in the Bitvise SSH installation wizard.

3. When prompted, choose Standard Edition.
4. If you are naming the server on which Bitvise SSH runs, when prompted to enter a named
instanced, enter the server name.
5. When complete, the Bitvise SSH control panel is displayed.
Create a Virtual Account

To create a virtual account:
1. In the Bitvise SSH control panel, view the Server Settings tab. Verify that the default
Listening Port for SSH is 22.
2. Choose Virtual Accounts tab. Click Add. The Adding New entry for Simplified virtual
accounts dialog box is displayed.
3. Enter a user name. Retain this user name for later use when connecting the Bitvise
SSH client and server.
4. Click Virtual Account Password. The Virtual Account Password dialog box is displayed.
5. Enter a password and click OK.
6. Accept the default root directory. (Optional) Browse and select an existing empty
directory, or create and select a new one.
7. Click OK. The Virtual Accounts tab is displayed.
8. Click Save Changes. The Initial Settings Confirmation dialog box is displayed.
9. Choose Save settings and start the server. The Confirm Windows Firewall Open for
Local Network Only dialog box is displayed.
10. Click Start Server.
11. In the Bitvise SSH control panel, select the Server tab. Verify that the service is running.
12. Verify that the Bitvise user account has been added to Windows.
a. Open Windows Control Panel.
b. Depending on which version of Windows is running, choose Manage User Accounts
or its equivalent.
c. In the User Accounts dialog box, in the Users for this computer field, verify that the
user name you created in Step 3 is displayed.
13. Restart Windows.
102/119
Manage Folder Permissions

Verify that the Bitvise SSH client has read/write permissions to the directory used for file transfer.
To manage folder permissions:
1. In Windows File Explorer, navigate to the directory used for file transfer.
2. Right-click on the folder and choose Properties.
3. Select the Security tab and click Advanced. The Advanced Security Settings for <folder_
name> dialog box is displayed.
4. Click Add. The Permission Entry for <folder_name> dialog box is displayed.
5. Click Select a principal. The Select User, Computer, Service Account, or Group dialog box
is displayed.
6. In the Enter the object name to select field, enter the user name of the account you
previously created.
7. Click Check Names. Click OK.
8. In the Basic Permissions pane, choose Full Control.
9. Click OK and close all dialog boxes.
Create Bitvise SSH Client Connection

Install the Bitvise SSH Client on the computer you use to connect to the Bitvise SSH Server.
To create a secure Bitvise SSH client connection:
1. Download Bitvise SSH client from here:

https://www.bitvise.com/ssh-client-download
2. To install OpenSSH, follow the instructions in the Bitvise SSH installation wizard.

3. When prompted, choose Run Bitvise SSH Client when done.
4. Complete the installation.
Connect Bitvise Client and Server

Install the Bitvise SSH Client on the computer you use to connect to the Bitvise SSH Server.
To create a secure Bitvise SSH client connection:
1. On the Bitvise SSH Client computer, open Bitvise Client.

2. On the Login tab, enter the Server Host name or IP address of the computer running the
Bitvise Server.
3. Enter the Port number. The default is 22.
4. In the Authentication pane:
a. In Username, enter the user name you entered in Create a Virtual Account.
b. In Initial Method, choose Password.
103/119
c. Choose Store encrypted password in profile.

d. Enter the password you created in Create a Virtual Account.
5. Click Log In. If this is the first time connecting the client to the server, click Accept and Save.
When successful, a terminal window displays confirming that files can be transferred using
SFTP.
Create OpenSSH Connection
To create a secure OpenSSH connection:
1. Download OpenSSH from Github:

https://github.com/PowerShell/Win32-OpenSSH/wiki/Install-Win32-OpenSSH
2. Extract the contents into a folder named OpenSSH and move the directory under C:\Program
Files\.
3. Launch Powershell with Administrative privileges. Run:
powershell.exe -ExecutionPolicy Bypass -File install-sshd.ps1
4. In Powershell, add a new firewall rule:

New-NetFirewallRule -Name sshd -DisplayName 'OpenSSH Server (sshd)' -Enabled True -Direction Inbound -
Protocol TCP -Action Allow -LocalPort 22
5. In PowerShell, generate host keys. Start sshd and ssh-agent:

net start sshd
net start ssh-agent
The host keys are created in %programdata%\ssh
6. In PowerShell, start the services using these commands:

Set-Service ssh-agent -StartupType Automatic
Set-Service sshd -StartupType Automatic
Get-Service -Name ssh-agent,sshd
7. Select the Windows Start menu and open Services.msc. Verify that these two services are
running. If not, start them:
OpenSSH Server
OpenSSH Authentication Agent
8. Repeat these steps to install OpenSSH on the Tx server, file server, and Rx server.
Set up Client SSH on the Tx Server

The Tx server is a cilent for the file server, and the file server is a client for the Rx server.
1. Launch Powershell with Administrative privileges. Generate the public private key pairs:
cd 'C:\Program Files\OpenSSH'
.\ssh-keygen
104/119
2. Two files are created in C:\Users\<USER>\.ssh (where <USER> is the username for the currently
logged in user):
o RSA private key: id_rsa
o RSA public key: id_rsa.pub
3. Copy the file id_rsa.pub to the file server.
Set up SSH on the File Server

1. Rename file id_rsa.pub to administrators_authorized_keys. Do not add a file extension.
2. If there are multiple Tx servers, you must copy the contents of the file id_rsa.pub on each Tx
server to a new line in the administrators_authorized_keys file on the file server.
3. Move the file to C:\ProgramData\ssh\.
4. Right-click on the file administrators_authorized_keys. Choose Properties > Security.
5. Remove Authenticated Users. Keep only SYSTEM and Administrators.
6. Restart these SSH services:
OpenSSH Server
OpenSSH Authentication Agent
7. Verify that you can connect to the server without entering a password. Enter:
.sftp.exe <USER>@<SERVER>
where:
<USER> is the username of the user who set up the server.
<SERVER> is the name of the server or computer.
8. When you first connect to the server, you are prompted to verify that you want to connect
to the server. Enter Yes.
The Rx server is a server for the file server.
Set up SFTP Client

To set up SFTP on the client or Tx computer:
1. Open Windows PowerShell with Administrator rights.

2. Navigate to the OpenSSH folder:
C:\Program Files\OpenSSH
3. Generate the private key:

.\ssh-keygen
o When prompted to enter a file name to save the key, leave it blank.
o When prompted to enter a passphrase and passphrase verification, leave it blank.
105/119
o Two files are created in C:\Users\<USER>\.ssh (where <USER> is the username for the
currently logged in user):
n RSA private key: id_rsa
n RSA public key: id_rsa.pub
4. Open id_rsa.pub in a text editor (like Notepad).
5. Before proceeding, complete setting up the SFTP Server. See Set up SFTP Server .
6. Copy the entire contents of id_rsa.pub on the SFTP or Tx client.
7. On the SFTP or Rx server, paste the content into the authorized_keys file. Each key must be on
its own line.
8. Save the file on the SFTP server in this location:
C:\ProgramData\ssh\
9. Right-click on the file you just saved. Choose Properties > Security.

10. Remove Authenticated users rights. Only SYSTEM and Administrators are displayed.
11. On the SFTP or Rx server, restart the sshd service.
Restart-Service sshd
12. Connect to the server:

.sftp.exe <USER>@<SERVER>
where:
<USER> is the username of the user who set up the server.
<SERVER> is the name of the server or computer.
13. The first time you initiate the connection, you are asked to verify that you want to connect
to the server. To confirm and add the server to the list of known hosts, enter Yes.
14. If you are prompted for a password, you did not enter the key to the server correctly. To
proceed, repeat the prior step.
15. In Windows Powershell, the prompt sftp> is displayed. To exit, enter bye.
Set up SFTP Server

To set up SFTP on the server computer:
1. Open Windows PowerShell with Administrator rights.

2. To store the public keys, create a new .ssh folder .mkdir ~\.ssh
3. Using a text editor (like Notepad) with Administrator rights, create a file named authorized_
keys and save it to
C:\Users\<USER>\.ssh.
106/119
The file \authorized_keys file does not have an extension. If you are using Notepad
to create a file without an extension, choose “All (*.*)” as the file type and add a
period to the end of the name.
Set up Scheduled Task

To enable SSH to transfer files from one computer to the other:
1. Access the System 1 install disk. Find the replication folder and a file named:
SFTP_Client_Script.ps1
2. Copy that file to the client machine:

C:\Program Files\OpenSSH
3. Open the file in a text editor (like Notepad) using Administrator privileges. To see all files,
choose All (*.*) as the file type.
C:\Program Files\OpenSSH\SFTP_Client_Script.ps1
4. Modify the file:
Parameter Enter this Value
The user account on the SFTP Server computer running the

$SftpUserAccount
SSH services.
$SftpServerComputername The name of the computer running the SSH Server services.
The folder that was configured for the replicated data file in
$S1EvoDataFileDirectory the System 1 Database Manager replication settings.
(Maintain the format displayed in the example.)
The folder share on the SFTP Server that is currently being

$SftpServerFolderPath monitored by the RFTS Client. (Maintain the format
displayed in the example.)
5. Save the document.

6. Open a new document.
7. Copy and paste the following into the document:
powershell.exe -file "C:\Program Files\OpenSSH\SFTP_Client_Script.ps1"
8. Save the document as start up.cmd in the folder C:\Program Files\OpenSSH\. (To be sure the file
name is correct, choose All (*.*) for the file type and enter start up.cmd as the file name.)
9. Close the text editor.
10. Launch the Windows Task Scheduler app.
11. Choose Task Scheduler Library.
12. In the Actions pane, choose Create Task. The Create Task dialog box is displayed.
13. In Name, enter SFTP Client Script.
107/119
14. Enter a description, for example, Automated script to transfer System 1 Evolution data files to File Server using
SFTP .
15. In Security options, modify When running the task, use the following user account.
Select a user account with permissions to run scripts.
16. Choose Run whether user is logged on or not.
17. Select the Triggers tab and click New.. The New Trigger panel is displayed.
a. In the drop-down list box Begin the task, choose On a schedule.
b. In Settings, choose Daily.
c. In Advanced Settings, select the Repeat task every drop-down list box and choose 1
hour.
d. In the for a duration of drop-down list box, choose Indefinitely.
e. Click OK. The Create Task dialog box is displayed.
18. Select the Actions tab and click New.. The New Action panel is displayed.
a. In the drop-down list box Action, choose Start a program.
b. In Settings, Program/script, enter C:\Program Files\OpenSSH\start up.cmd.
c. Click OK. The Create Task dialog box is displayed.
19. Select the Settings tab. The Settings panel is displayed. Enable these settings:
a. Run task as soon as possible after a scheduled start is missed
b. Select the If the task fails drop-down list box, and choose 1 minute.
c. Click OK. The Create Task dialog box is displayed.
21. Select the SFTP Client Script task in the central pane.
22. In the Actions pane, choose Export.. The Save As dialog box is displayed.
23. Choose a folder in which you want to save the script. Remember this location for step 27.
24. In the File name field, enter SFTP Client Script.xml .
25. Click Save.
26. Using Windows File Explorer, access the script file.
27. Open the folder location in which you saved SFTP Client Script.xml .
a. Open the file in a text editor (like Notepad).
b. Find this code: <Priority>7</Priority>. The number may be different.
c. Change 7 to 1. This causes Task Scheduler to run the process as high priority.
d. Save and close the file.
28. Launch the Windows Task Scheduler app.
108/119
30. Delete the task named SFTP Client Script you previously created.
a. In the Actions pane, choose Import Task.. The Open dialog box is displayed.
b. Navigate to the folder where you previously saved the script.
c. Select the SFTP Client Script.xml file.
d. Click Open. The Create Task dialog box is displayed.
31. Click Save.
3.8 Client SFTP Batch File Script

###############################################################################
# SCRIPT: SFTP_Client_Script.ps1
# DESCRIPTION: The purpose of this PowerShell script is to automate the process
# of calling the SFTP Client (sftp.exe) with the list of System 1
# Evolution data files that are to be moved to the SFTP Server.
# TODO:
# - Automate Script through Scheduled Tasks
# - Secure Script
# - Add logging to Script
###############################################################################
# SFTP User Account

$SftpUserAccount = "<user_account>"
# SFTP Server Computername

$SftpServerComputername = "<computer_name>"
# Location on System 1 Evolution Server where replicated files are being created
$S1EvoDataFileDirectory = "D:/ReplicationFiles/"
# File filter criteria for System 1 Evolution related files

$S1EvoAllFilter = "*.S1*"
# SFTP Executable
$SftpExecutable = "sftp.exe"
# Folder Location of SFTP Client (sftp.exe)

$SftpExeFolderPath = "C:/Program Files/OpenSSH/"
# Filename for SFTP.exe commands

$SftpCommandFileName = "sftp_file_transfer_script.txt"
# Folder on SFTP Server where System 1 Evolution Data Files are to be placed
$SftpServerFolderPath = "/C:/REPdata"
# Log files created from call to sftp.exe

$SftpProcessStandardOutputFileName = "sftpProcessStandardOutput.log"
$SftpProcessStandardErrorFileName = "sftpProcessStandardError.log"
109/119
# Sleep Delay (seconds) for SFTP processing loop

$SleepDelay = 1
# SFTP Max Files to Batch per call

$SftpBatchMaxFileCount = 500
###############################################################################
# FUNCTION: CreateSftpBatchFile()
# INPUTS: $ListOfS1EvoDataFiles - This list contain the S1 Evo Data Files
# that are to be pushed to the SFTP Server.
# OUTPUTS: $SftpCommandFileName - This is the text file containing the
commands used
# by sftp.exe.
# This function is used to construct the text file used as input to sftp.exe
# There are basically three parts to this text file:
# - Add a command to change to the appropriate directory on the SFTP Server
computer.
# - Looping function that will take each S1 Evo Data File passed into the
function and
# append a "put" command before the file.
# - Call to "bye" to finish the SFTP client session with the SFTP Server.
###############################################################################
Function CreateSftpBatchFile{
param([string[]]$ListOfS1EvoDataFiles)
$SftpBatchFileContent = $null
$PutCommand = "put"
$ByeCommand = "bye"
$SftpBatchFileContent += "cd $SftpServerFolderPath `r`n"
foreach($file in ($ListOfS1EvoDataFiles | sort))

{
$SftpBatchFileContent += "$PutCommand " + [char]34 +
"$S1EvoDataFileDirectory$file" + [char]34 + " `r`n"
}
$SftpBatchFileContent += "$ByeCommand `r`n"
New-Item -Path $S1EvoDataFileDirectory -Name $SftpCommandFileName -Value

$SftpBatchFileContent -ItemType file -Force
}
Write-Host "Starting SFTP Transfer Script..."
while($true)
{
# --- STEP 1: Retrieve the current list of S1 Evo replication files
# Currently just finding all data files produced by S1 Evo
110/119
$FilteredDirectory = "$S1EvoDataFileDirectory$S1EvoAllFilter"
#Write-Host $FilteredDirectory
if(Test-Path $FilteredDirectory)
{
$ListOfS1EvoFilteredDataFiles = $null
$ListOfS1EvoFilteredDataFiles = Get-ChildItem -Path $FilteredDirectory -
name | sort
if ($ListOfS1EvoFilteredDataFiles.Count -gt 0)
{
if ($ListOfS1EvoFilteredDataFiles.Count -gt $SftpBatchMaxFileCount)

{
$ListOfS1EvoFilteredDataFiles = $ListOfS1EvoFilteredDataFiles
[0..$SftpBatchMaxFileCount]
}
# --- STEP 2: Construct the SFTP script file

#Write-Host "Constructing SFTP Script File"
$SftpFilteredBatchFile = CreateSftpBatchFile
$ListOfS1EvoFilteredDataFiles
# --- STEP 3: Call SFTP with script file
Write-Host "SFTP Transferring File(s)"

Start-Process -FilePath "$SftpExeFolderPath/$SftpExecutable" `
-ArgumentList "-b $S1EvoDataFileDirectory/sftp_file_
transfer_script.txt $SftpUserAccount@$SftpServerComputername" `
-Wait `
-NoNewWindow `
-WorkingDirectory $SftpExeFolderPath `
-RedirectStandardOutput
"$S1EvoDataFileDirectory/sftpProcessStandardOutput.log" `
-RedirectStandardError
"$S1EvoDataFileDirectory/sftpProcessStandardError.log"
if ((Get-Item
$S1EvoDataFileDirectory/$SftpProcessStandardErrorFileName).length -gt 0kb)
{
Write-Host "ERROR: There was an issue calling sftp.exe`r`n"
}
else
{
# --- STEP 4: Remove the list of S1 Evo Data Files that have
been transmitted
Write-Host "Removing transferred File(s)"
foreach($remFile in $ListOfS1EvoFilteredDataFiles)
{
111/119
Remove-Item $S1EvoDataFileDirectory/$remFile
}
}
}
else
{
#Write-Host "No System 1 Evolution Files found during this run"
}
}
else
{
#Write-Host "No System 1 Evolution Files found during this run"
}
#Write-Host "Sleeping script for $SleepDelay seconds"

Start-Sleep -s $SleepDelay
}
3.9 Data Replication Errors

The System 1 Replication Service does not start.
Recommended troubleshooting actions:
l Verify that the System 1 Replication Service is set to run as the Windows user account
recommend in the previous steps, and confirm that the user has System 1 Administrator
rights on the database selected for replication.
l Open the Windows Event Viewer, navigate to Applications and Services Logs > Bently
Nevada, and verify that no errors are logged from the System 1 Replication Service.
Data files are not being written to the target folder on the transmitting
System 1 database on the plant control network.
l Open the System 1 Database Manager application. Navigate to the Database Replication
tab, and select the System 1 database. Verify that the data location is configured properly
and all of the replication settings are set to enable the various types of data to be
replicated.
l Verify that current values data displays up in the System 1 Client application.
l Verify that the user account that the System 1 Replication Service is set to run as has the
proper read and write permissions on the replication data file folder.
l Restart the System 1 Replication Service in case any replication parameters have been
changed since it was last started.
112/119
Data files are not being transferred from the data folder on the plant
control network to the folder on the business tier network.
l Verify that the data diode devices are powered on.

l Verify that the file transfer software applications provided by the data diode vendor are
properly configured to read and delete the data files from the plant control network file
folder.
l Check the logs for the data diode file transfer software applications for any errors.
Data files are arriving on the business tier network folder but data files are
not being processed and no data is being sent in to the replication receiver
System 1 database.
l Open the System 1 Database Manager application with the -r command line argument.
Navigate to the Database Replication tab, and select the System 1 database. Verify that
the data location is configured properly and the database replication type is Receiver.
l Verify that the user account that the System 1 Replication Service is set to run as has the
proper read and write permissions on the replication data file folder.
l Restart the System 1 Replication Service in case any replication parameters have been
changed since it was last started.
When a transmitter database is taken offline, its Replication Type is set to

None.
If a transmitter database is taken offline after the replication setup is completed, its Replication
Type is set to None.
To resume replication, change the Replication Type to Transmitter.
Data files are not being written after clearing disk space.
If low disk space occurs, the System 1 Replication Service reverts writing files. After clearing disk
space, ensure that the Historian Data Archiver service is running. If the service is not running,
data files are not written.
Data replication has stopped because a configuration file was not

transmitted.
113/119
l Verify that the System 1 Server and System 1 Replication Service services are running on
both the transmitter and receiver machines.
l If both services are running, check the Windows Event Logs to determine when the receiver
failed to detect the expected configuration file.
l Repair and recover the data:
a. Launch the Database Manager on the Receiver machine.
a. Click the Database Replication tab.
b. Under the Data Recovery section, click the Replication Config Retransmit
Tool button.
c. Note the configuration sequence number displayed in UTC (Coordinated
Universal Time) for use below.
b. Now launch the Database Manager on the Transmitter machine.
a. Click the Database Replication tab.
b. Under the Data Recovery section, click the Replication Config Retransmit
Tool button.
c. Enter the configuration sequence number you noted on the Receiver
machine displayed in UTC.
d. Click Retransmit.
c. Data transmission is restarted from the last received file and Replication continues.
System 1 needs to be upgraded

For details, see help for the Database Manager and find the topic Upgrade Database..
3.10 Retransmit Replicated Database

During the replication process, a transmitter database periodically packages new data, events,
and status information that are eventually sent over the network to the destination database.
When this process is interrupted due to network issues or database problems, the transmitter
and destination databases become out of sync. When this happens, you must retransmit the
replicated configuration using the Config Sequence Number from the receiver machine.
When you retransmit replicated configuration data, System 1 also retransmits any
corresponding configuration templates for the specified configuration sequence ID. For example,
if you know that a template was created for configuration after configuration sequence 50, then
entering 50 for the configuration sequence ID also retransmits this corresponding configuration
template. If you are unsure when configuration templates were created, enter 1 for the
configuration sequence ID and the entire configuration is retransmitted.
Retransmit Replicated Configuration

To retransmit replicated configuration and corresponding template configuration:
1. On the receiver machine, choose Windows Start Menu > System 1 Database
Management. The Database Manager is displayed.
114/119

5. Note the configuration Sequence ID on the receiver machine:
6. Go to the transmitter machine and launch the Database Manager.

115/119
10. Enter the configuration Sequence ID from the receiver machine:
11. Choose Request Retransmit. The tool retransmits and recovers the configuration changes
based on the configuration Sequence ID.
Retransmit Replicated Data

To retransmit replicated data:
1. On the transmitter machine, launch the Database Manager.

3. In the General pane, verify that Replication Type, Database Name and Data Location are
correct. These fields are set during replication configuration.
4. In the Replication Retransmit pane, choose Replication Data Retransmit Tool.
5. Enter the desired start and end timestamps for the period from which you wish to
retransmit data:
116/119
6. Choose Request Retransmit. The tool initiates a background process that retransmits
data files within the specified timestamps.
If a previous retransmit request is still being processed, a message is displayed. You

must choose to overwrite the previous request or wait until the previous request is
completed. The retransmit request may take several hours for each day of data
requested before it finishes.
7. To view the status of the retransmit requests, you can view four log files. The log files are
continuously updated. To view the files, we recommend a third-party application like
SnakeTail or BareTail. The files are updated here:
C:\ProgramData\GE Bently Nevada\System 1\ReplicationService\
8. There is one log for each of the four data types. The file names are prefixed with
DataRetransmitLog:
o Alarm and Transient
o Trend Static
o Trend Waveform
o Portable/Offline
The log files are continually updated for every hour of data that is processed and indicate
when its data retransmission is complete. When all four log files are complete,
retransmission is complete.
117/119
4. Backup and Restore Issues


Acronis Issues
Known Issues and Limitations Back Up Mode Solution
Wait for two to

One-time Back three minutes. If
Recovering data from a backup located on a network Up the problem
path can sometimes take longer than one minute to persists, check
load. Scheduled Back your network
Up connection and
retry.
Windows Issues
Use a third-party
One-time Back
back up and
Backup files created with one operating system cannot Up restore tool to
be restored onto a different operating system. Scheduled Back move between
operating
Up
systems.
One-time Back Select a drive

When backing up files from a drive, that same drive Up other than the
cannot be selected as the backup file destination drive location of
location. Scheduled Back the back up
Up source files.
Select a network
During the back up process, a network path destination
Scheduled Back path location on
must reside on a separate machine than the machine
Up a different
performing the back up operation.
machine.
Both the backup source machine and destination Scheduled Back Confirm the user
118/119
credentials on
machine or path must have the same user credentials both the source
Up
for access, including password. and destination
machine or path.
One-time Back
Up Relaunch the
An idle VSS tool closes automatically after ten minutes.
Scheduled Back tool.
Up
OPC Issues
The following error is displayed when the unique ID of Reconfigure the

One-time Back OPC tags in the
the restored database conflicts with the unique ID of the
Up existing OPC
existing database on the same server:
Scheduled Back Clients for the
Reconfigure the OPC Tags already existing in the OPC restored
Up
Clients for the database <database name>. database.
119/119

System 1 Database Administration User Guide - 156M4815

Uploaded by

Copyright:

Available Formats

System 1 Database Administration User Guide - 156M4815

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

System 1 Database Administration User Guide - 156M4815

Uploaded by

Copyright:

Available Formats

System 1 Database Administration

Copyright 2021 Baker Hughes Company. All rights reserved.

1631 Bently Parkway South, Minden, Nevada USA 89423

3.6 Configure Remote File Transfer Service 101

l In Windows, choose Start Menu > System 1 Database Management.

Database Manager Warnings / Errors Pane

Failed to fetch data

Troubleshooting the Database Manager

1.1 View Database Description

1. Launch the Database Manager using one of two options:

4. The Database Manager displays storage details:

Also see Review Data Storage Requirements.

1.2 Review Data Storage Requirements

Portable Data Store

Premium and Advanced Packages

Alarm Data Store

Transient Data Store

Short-Term Data Store

Long-Term Data Store

Summary Data Tiers for Trended Variables

l First-in value and timestamp.

Both min and max values are plotted.

Online and Scanning Data Store Properties

l Alarm Data Store: 20% of available disk space

Low Disk Space Data Wrapping

l Free disk space.

1.3 Manage Database Settings

1. Open the Database Manager and select the General tab.

20% of available disk space The application calculates

10% of available disk space

Configure Device Rates

1. Open the Database Manager and select the General tab.

OPC Server Update and Storage Rates

Storage Rates for Configured States

1.4 Back up PostgreSQL Databases

The Database Manager backs up only Fundamental or online PostgreSQL databases. To

Back Up System 1 Database

1. Choose Tools > Database Manager. The Database Manager is displayed.

Back up Ranger Pro Device Configuration

1.5 Restore a PostgreSQL Database

The Database Manager tool can only Fundamental or online PostgreSQL databases.

To restore your database:

1. Choose Tools > Database Manager. The Database Manager is displayed.

3. Choose Restore tab.

n Overwrite Config Database Overwrite the database.

8. Click Restore. When the process is complete, a confirmation message is displayed.

1.6 Migrate PostgreSQL 9.6 to 11

1. Install PostgreSQL9.6 from System 1 installation disk.

c. When prompted, select the default path for Installation Directory.

1.7 Move PostgreSQL Database

To move your PostgreSQL database to a new directory on the same machine:

1. Back up all System 1 offline databases.

14. Select the System 1 folder.

Enterprise_Database_Location displays the location of the current Stores folder.

19. Select the System 1 folder.

D:\Stores\ (The new Stores folder created)

21. In Windows File Explorer, navigate to:

22. Delete the file EnterpriseStore.db (db3)

C:\Program Files\PostgreSQL\11\bin\pg_ctl.exe" runservice -N "PostgreSQL-x64-11" -D "C:\Stores\PostgreSQL11 "

"C:\Program Files\PostgreSQL\11\bin\pg_ctl.exe" runservice -N "postgresql-x64-11" -D "D:\Stores\PostgreSQL96"