Hello,
First of all, I know the first thing mentioned in PcVue help, that the folder configured for Proprietary Archive (default is TH) must always be accessible.
I have a question regarding this from the user, I can guess the answer, but I want to get confirmation from any of you. The user gives a scenario like the below :
1) I have one server, that server has 3 hard disks. (each C, D, E local drive)
2) PcVue and Project are installed in C drive, and Trend data is saving in D drive. (Trend data is saved in file format.)
3) A disk error occurred in the D drive while saving trend data.
4) EVENT("The Device is not ready") is output from PcVue and the trend data is not saved.
5) We repaired the disk in drive D and made it work normally, but the problem in item 4 above is not resolved.
(The PcVue program cannot be closed because it is monitoring important data.)
So the question is if there is any way to make reconnection to the drive again from PcVue once the disk has been repaired? I have tried a similar case, by configuring the proprietary storage to an external SSD and unplug it during operation. After plug-in again the SSD, I will see error like below in the PcVue event viewer.
2021/10/08,17:39:52.888,8,I,,8312,,200,Error on file : 'G:TEST_PROPhisto.sav'. 2021/10/08,17:39:52.888,8,I,,8314,,200,Error : 'The device is not ready. '. 2021/10/08,17:40:02.891,8,I,,8312,,200,Error on file : 'G:TEST_PROPhisto.sav'. 2021/10/08,17:40:02.892,8,I,,8314,,200,Error : 'The device is not ready. '.
The question arises because, in HDS, we have the capability to automatically resume archiving after the SQL connection is re-established.
My answer would be, the archive operation of HDS and proprietary are different and not comparable.
HDS writes directly to SQL server, and in the case of SQL connection missing, it will start recording in local disk, and once connection re-established, it will be resumed back automatically.
For Proprietary, it writes to a temp file HISTO.SAV, which is located in the destination folder, and from here it will write to the archive files. So if the disk loses connection, access to HISTO.SAV file is gone too, so the archive process is interrupted, and the only way to recover is by restarting PcVue.
And of course, in an ideal case, the situation described by the user should not happen for the second time. The moment the disk is having a problem, the system integrator/owner must do proper repair and ensure that it does not happen again, especially for an important system that does not allow downtime.
To elaborate on Kantha's feedback, if availability of archiving is a thing, going with the proper RAID set up is a must.
Properly done, it brings the best guarantees of availability and integrity that may be related to disk access issues.


