Historian Data Storage

Unless otherwise configured, Historian tags will save data to a VTScada proprietary database system within the application's data folder. These files are designed for use solely by VTScada. Values can be read only by VTScada and cannot be modified by any means without damaging system integrity.

Do not use the same storage location for multiple applications.
               Do not attempt to use an external USB drive for your Historian data.
               Do not configure your Historian to write to a storage device located elsewhere on your network.
For all the above, you run the risk of data loss or corruption. Your safest course is always to do initial data storage on the machine that is the current server, using the proprietary VTScada format.
Rely on backup servers for remote redundancy and if you want to use 3rd party databases, keep your default Historian tags intact and create new Historian tags dedicated to your databases.

While the properties described in this topic can be set in the Edit Properties dialog (StorageLocation & StorageType), you are strongly advised to use the configuration fields of the Historian tag instead. See: Historian properties Datastore tab

Storage Requirements

Storage requirements vary wildly depending on the size of your system, the type of data being collected, and the strictness of your tolerances. If you're looking for a very broad ballpark estimate of a reasonable magnitude of storage, consider 1000 data changes per second will require roughly 800 GB per year ±40%.

It is wise to use deadbands on I/O tags and set polling frequency as large as safely possible to minimize storage requirements. Also, do not save information that you will never need to retrieve in any report. Logging is enabled by default on every I/O tag, but may not be required in every case.

As of VTScada version 12.3, Historian storage can be extended. See: Extended Historian Storage

Requirements and Installation

Customizing Historian Storage Location

Extended Historian Storage