Professional Documents
Culture Documents
1) Disable PlantTriage start on re-boot by un-checking Services start automatically after reboot on the Services tab of the PlantTriage Administrator window. 2) Bring up the PlantTriage Administrator window Directories tab and note the Logging and Archive directories on your hard drive. 3) Re-boot the computer. Note: as part of the Restoration procedure, all user accounts that were configured in the Backup database will be restored. Ensure that you have a known valid user acct. and password in the Backup PlantTriage installation to use to log into the restored PlantTriage database. 4) If the Admin Backup function was selected to back up to 3 .zip files: uncompress the files Archive.zip and Logging.zip on the backup disk. Also if restoring to a different computer, copy all of the files in the Xtune\PT\TRENDS folder from the server being backed up to the server where the PlantTriage database will be restored because these files will not be restored using the below-described procedure. 5) Delete all the files and subdirectories from the Logging directory on your hard drive. You may have to make the files not read-only before you can delete them. Right-click the files, choose Properties and un-check the readonly box. Copy all the files and subdirectories in the Logging directory on the backup disk to the PlantTriage Logging directory on your hard drive subfolders 6) If the Admin Backup function was selected to back up to 3 .zip files: uncompress the file TriageSqlBackup.zip and copy the files CalcSqlBackup.dat, TriageSqlBackup.dat; and if restoring a PlantTriage v.9 or higher database also the file CountsSqlBackup.dat that are in the decompressed Logging folder and copy them into the Logging directory on your hard drive. 7) Right-click on the Logging root directory, choose Properties, un-check the read-only box and apply this change to all subfolders and included files. 8) Delete all the files and subdirectories from the Archive directory on your hard drive. You may have to make the files not read-only before you can delete them. Right-click the files, choose Properties and un-check the readonly box. Copy all the files and subdirectories in the Archive directory on the backup disk to the PlantTriage Archive directory on your hard drive. 9) Right-click on the Archive root directory, choose Properties, un-check the read-only box and apply this change to all subfolders and included files. Page 1 of 8
Page 2 of 8
19)
Page 5 of 8
Procedure to Restore a PlantTriage Database from Backup Using one computer for two different PlantTriage datasets
This is a requirement on a demonstration system where the user wants to show an example of data from a real plant and the PlantTriage demonstration loops on the same computer. It is not possible to use one computer for two different PlantTriage datasets at the same time. At any one time there can only be one set of logging/archive data and one database. The location of the PlantTriage logging and archive directories on your hard drive is defined within the historian.ini file in the \xtune\Canary\Historian folder or the \xtune\Canary\Shared folder. Therefore to move between different datasets requires some file copying and re-booting. For the purpose of this description, suppose Dataset A contains the Demonstration loops. It has been generated by doing a backup from a live PlantTriage demonstration system. Perhaps Dataset A resides on a network drive. Suppose Dataset B contains data from a live plant. Perhaps Dataset B resides on a removable drive that has been dumped from a PlantTriage system that is connected to a live plant. The procedure for replacing Dataset A by Dataset B, or vice-versa, is identical. It is the same as the procedure described above for restoring a PlantTriage database from backup. In both cases the TriageSqlRestore.sql file created at step (6) above is used. In summary you must:
Reboot the computer. Prior to reboot make sure then Auto restart after reboot in the Engineering Interface Administrator window, Services tab is not checked. Delete \xtune\Canary\Shared\historian.ini. If the file has already been deleted since PlantTriage installation, it will be in the \xtune\Canary\Historian folder. Run the TriageSqlRestore.sql file. (osql -E I "...\TriageSqlRestore.sql") Restart PlantTriage from the normal or /Offline icon From Tools, Administrator: o Directories tab: Set the Logging and Archive directories to the directories where the Logging and Archive backup datasets reside. This procedure creates a new historian.ini file in the \xtune\Canary\Historian folder. o Services tab: Reinitialize button if you used the PlantTriage /Offline icon or Start button if you used the PlantTriage normal icon.
Page 6 of 8
Page 7 of 8
3) Automatically after a re-boot. There is a PlantTriage service, called XpPtStartServ, which runs automatically after a re-boot. This starts PlantTriage in online mode. It is designed for use in a live PlantTriage system so that a live system automatically goes online if it is re-booted. Whether or not this service starts automatically after a reboot is governed by checking or un-checking Services start automatically after reboot on the Services tab of the PlantTriage Administrator window. If you plan to use your computer for demonstrating PlantTriage with different datasets, you will not want PlantTriage to automatically start in online mode after a re-boot.
Page 8 of 8