Skip to main content

Upgrade to a new version and roll back

YTCC is upgraded with the setup program. A later version of the same version line, for example 1.5.x to a later 1.5.x, upgrades the installation in place: the projects, databases and settings stay, and going back means restoring a backup. The setup program of a new line, such as 1.6, does not touch the old line: it installs the new line next to it, you take the projects over one by one, and the old line stays available until you remove it.

Before you begin​

  • Back up every project on the home page with Back up… and keep the files off the server; see Backup and restore. Back up the history databases as well.
  • Inform the operators: during an upgrade of the running line, field monitoring pauses for about five minutes.

Steps​

1. Upgrade with the setup program​

Run the setup program of the new version on the server, choose Upgrade (recommended) on the YTCC on this computer page and complete it (see Upgrade with the setup program). It stops YTCC, replaces the programs, keeps the folder, the settings, the projects and the driver selection, upgrades the databases and starts the service again. It upgrades the registry and then every project that is not archived. Before it upgrades a project database, it backs the project up to data\backups\yukseltme-<time>\ in the installation folder. A project whose backup fails is not touched.

The upgrade of a project with about 1,000,000 signals takes about 10 to 30 seconds longer, because a search index is built; writes to that project wait during this time.

The setup program does not install an older version of a line over a newer one. To go back, install the older version after removing the newer one, and import the backups.

2. Upgrade a remaining project on the home page​

Read the last page of the setup program. Each project that could not be upgraded has its own configuration warning, with what happened and the command that fixes it, and the output of the upgrade is in logs\kurulum-veritabani.log. The project list of the home page shows Upgrade needed for that project. Right-click the project, choose Upgrade… and confirm with Back up and upgrade: YTCC takes a full backup first and upgrades the project database only if the backup was taken. See Upgrade a project from the home page.

To upgrade all databases on the command line, stop YTCC and run scada-manager migrate --all; see Database upgrade. The command ends with a non-zero exit code if a project was not upgraded.

An upgraded project cannot be opened in the older YTCC version any more.

3. Install a new version line next to the old one​

For a new line, run its setup program and choose Install (other installations stay as they are). It installs the line in its own folder, for example C:\ytcc\v16, with its own service, ports and databases, and leaves the old line running as it was. When the ports clash, accept the suggested port block. See Install versions side by side.

A new line starts without projects. Only one project runs on the computer at a time, so the old line keeps running the plant until you move the project.

4. Take a project over into the new line​

Take a project over between version lines on the command line. Stop the service of the new line (YTCC v16 in Services), then open a command prompt as administrator and run:

scada-manager v16 project adopt <project> --from v15

<project> is the part after scada_v15_proj_ in the project database name, for example pump_station. The command saves a read-only backup of the project from the old line in the new line's backups folder, copies the project into the new line keeping its identity, upgrades its schema and copies its port settings. The old line's databases and files are not changed.

The command refuses while the project runs in the old line. Stop it there first on the home page of the old line, or add --takeover, which asks the old line to stop the project. If the project already exists in the new line, add --replace; the existing copy is renamed and kept.

An early installation from before version lines (folder C:\YTCC, service YTCC) in another folder, for example D:\YTCC, is the source with --from-root D:\YTCC instead of --from. If it is in C:\YTCC, it overlaps the new folder: remove it with the setup program of the new line as described in Remove old installations, then install fresh, then import the backups on the home page.

5. Check the project in the new line​

Start the service of the new line again, open its home page with its shortcut, for example YTCC v16 (Edge), and start the project with Start. When the project runs in the old line, the window Project is running in another version offers Stop it there and start here… (see Run lock and side-by-side versions). Check the screens, the communication and the alarms.

6. Go back to the old line (optional)​

If the project does not work in the new line, take it back. With the old line running, in a command prompt opened as administrator:

scada-manager v15 project reclaim <project>

The command shows how many configuration changes were made in the new line; those changes are not visible in the old line. Confirm when the command asks. The command then asks the new line to stop the project and starts it in the old one. History recorded in the new line stays in the new line's databases.

7. Remove the old line​

When all projects run in the new line, remove the old one in Windows: Settings › Apps, the entry of the old line, for example YTCC 1.5, Uninstall. Remove the program only (recommended) keeps its data. To delete its databases as well, choose Full clean-up, or Back up the projects I pick, then clean up to keep a backup of selected projects. A database that the new line still uses, for example a history database it still reads, is not deleted. See Uninstall YTCC.

warning

Deleting the databases of the old line cannot be undone. Check the new line and your backups first.

Result​

The projects run in the new version. After an upgrade of the same line, the backup is the only way back; after installing a new line, the old line remains available until you remove it.

Good to know​

  • The commands of steps 4 and 6 and their options are listed in scada-manager commands. They need a command prompt opened as administrator, because they read the database password.
  • After an upgrade, open Licence on the home page. A server above 80 CU needs a licence file, and without one the 90-day count of the design lock starts. See Licence and Capacity Unit.