Public:Backup PVSS Database

Notice:
The following procedures should be executed by experienced PC users only. If the procedures are not followed correctly, files can be deleted, data will be lost, hard disk file systems can become full and proper operation of the IPC system will not be possible. To prevent damage, it is best to contact Brückner before these procedures are executed.

In the following procedure, the name Template:KomNam must be replaced by the appropriate commission name where it appears in the directory or computer names.

General Information about the PVSS database:

The active PVSS database contains the configuration of all Datapoints in the system together with their properties (also called configs) and actual values. It also contains the historical data used by the trend, alert and event functions. Depending on how the data storage is configured, an active database can fill a large part of the available hard disk space, for example: 100 Gb.

A backup database contains the same information but the historical data is limited to the last 2 hours so that it takes up less disk space, about 500 MB for an average size stretching plant with a typical configuration.

Within the database, the alert history data is stored in subdirectories with names of the form alnnnnnnnnn, where nnnnnnnnnn is a number. A new subdirectory is generated every day, as can be seen by the dates of the directories. Old data is removed after a configurable number of days has been reached. The data can only be viewed from the alert screen in the PVSS user interface.

Also within the database are subdirectories for the event history data with names of the form VA_000N where N is a number of the archive class from 0 to 5. Each of these directories contains files with names of the form AR_000N_YYYY.MM.DD-HH.MM.SS where again N is the archive class and YYYY.MM.DD-HH.MM.SS is the Greenwich mean date and time at which the file was generated. When a file is full of data, then a new one is generated. Old data is removed after a configurable number of files has been filled.The data can only be viewed from the event screen and trend history in the PVSS user interface.

Most of the setpoints and parameters set on the operating screens are stored in the PLCs so that even if an old backup database is reactivated, the settings in the PLCs will overwrite the database contents as soon as the communication to the PLCs is started.

The main exception to this rule is the TCE system whose configuration is stored only within the database. Therefore any changes, including the thickness setpoints, should be checked when a backup database is activated. If a backup database is activated while the line is running, it is important to switch off the thickness scanning gauge to prevent the TCE from controlling to old setpoints. The gauge can be restarted after the setpoints are checked and corrected if necessary.

1 Backing up the PVSS Database

It is only necessary to back up the database when the configuration and properties of the datapoints has changed. This is usually only done by the Brückner engineers.

• Log on to any IPC operating stationPC as user PVSS with the password you have received from Brückner.
• Check the backup Directory for an existing backup of the database and remove it if necessary:
  • in a Windows Explorer, go to the Directory
    • P:\Template:KomNam\db.backup\db
      Note:
      drive P: should be automatically mounted to \\Template:KomNam\projects during the Login procedure so that this directory is called:
      Template:PathUncKomdb.backup\db in UNC file Notation
  • If a backup database directory named pvss already exists there, then delete it. Do not delete any other files or directories.

• Start an online backup from the System Management Panel of any PVSS operating Station:
  • Press the Online Backup button
    Template:Image
  • Then press the Star Backup button in the PVSS backup Panel.

Template:Image

• the Status field will turn green as shown, indication that the backup is running.

• The following message will appear. It is only relevant for Brückner engineers. Acknowledge it by pressing OK.

• The backup is complete when the status field turns grey again. This can take several minutes depending on the size of the database.

2 Restoring the backup copy of the PVSS database

It is only necessary to restore the backup copy of the PVSS database in the unlikely event that it becomes corrupt. This could happen, for example, if the power to the Linux computer is switched off before the PVSS and linux systems have shut down, though the UPS will automatically power down the systems at a power cut. Messages in the PVSS project log files can give indications that the database may be corrupt.

• Log on to any IPC operating station PC as user pvss with the password you have received from Brückner.

• Open the telnet connection to the linux server using the Run command in the Windows start button.

• In the telnet window, log on to the linux server as user pvss with the password you have received from Brückner.

• In the telnet window check if the PVSS system is running using the command pvsspss which lists all running PVSS processes. If processes are running, the Output will look something like this:

If no processes are running, the output will look something like this:

• If any processes are running, stop them in the telnet window using the command kill_pvss2 and wait for the command to complete which may take a few minutes. This will also cause the PVSS user interface on all operating stations to disappear. Then recheck for running processes as described above.
• In the Windows Explorer, go to the active database directory

P:\Template:KomNam\db

and rename the active database directory pvss to pvss.old.

• In the Windows Explorer, use copy and paste to copy the backup database pvss.bms from the backup database directory.

P:\Template:KomNam\db.backup\db

to the active database directory

P:\Template:KomNam\db

Do not use drag and drop, because this will move the backup database instead of copying it!