New Case Case Status
Log In



KB000036 - Using the EtaPRO Cl…
  • RSS Feed

Last modified on 10/17/2019 2:00 PM by User.


KB000036 - Using the EtaPRO Clone Tool

Product EtaPRO Service Manager
Version 10.3 and newer
Date 10/18/2018
Error Message None
Resolution Instructional



EtaPRO systems beginning with Server 10.3 with a local SQL server wishing to duplicate an EtaPRO unit.

NOTE: The SQL account used in the cloning process must have “attach” and “dbcreator” rights and should be mapped to the “master” database in SQL server for the tool to work.

Failure to use a SQL account with the appropriate permissions could result in an unusable database.


The Clone Unit Database Wizard may be run from any EtaPRO Server Service Manager providing EtaPRO databases are attached and running from a local instance of SQL Server. A local instance of SQL Server is defined as being installed to the same hardware as the EtaPRO Server software.

  1. Stop all EtaPRO Services
  2. From the EtaPRO Service Manager, click Configuration Settings

  1. Enter a SQL username and password with dbcreate permissions (for best results, use a sysadmin account)
  2. Highlight the row of the database you wish to clone.
  3. Click the Clone Unit button.

NOTE: If the Clone Unit button is not visible, a local instance of SQL Server is not installed and this tool may not be used.

  1. The Clone Database Wizard form will be displayed. Click Next.

  1. Follow the prompts for each step of the Clone Database Wizard.

Several message will appear, including Updating Point table...,Updating External table...,Updating Archive Items...,Updating Screens...and others

When the process is complete:

Following completion of the wizard, the following should be verified. These steps are not considered to be part of the cloning process.

  1. EtaPRO Input Validation
    1. Were acquired points renamed properly?
    2. Are additional/substitute inputs needed?
  2. EtaPRO Settings
    1. User Management (assign appropriate levels of access to users)
    2. Custom Screen Labels (screens must be updated manually)
    3. Rename Diagnostic files and check inputs
    4. Check screen buttons to link to correct unit
    5. Footprints will be unit specific by design
  3. VirtualPlant Settings
    1. Design Data (different performance or correction curves?)
    2. Performance Test/Tuning Data
  4. Database Validation

a. Ask a SQL database administrator to compare the resulting cloned database against the host database

b. If any tables are missing, please contact EtaPRO Support