Ürünlerimiz - Modüller

HSM is a data saving technique enabling less used documents on cheaper media, while keeping important or extensively used documents on faster and trustable media. When it is used in document management systems, it enables documents to be transferred to cheaper media according to document types, last access and creation dates.

How does PaperWork HSM work?

Within PaperWork, documents can be saved either on a hard disk or a database according to installation parameters. Each method has its own advantages and disadvantages. Documents are saved in CAS (Content Addressable Storage) files created on disks by PaperWork HSM. No profit CASCommunity organization defines world standards related with CAS. PaperWork HSM supports all standards defined here.
CAS prevents documents to be changed from outside thanks to built-in structure. Each changed version of electronic documents within system is saved as separate documents and guaranteed that it will not be changed. Moreover, CAS files are extremely secure since they are encrypted by MD5.
During installation, place and sizes of CAS files are defined. All documents saved in system are archived in CAS files according to these predefinitions.
Each CAS file archives a document at a specific size defined system parameter, documents bigger than this size are directed to next CAS file. The rest of the operation automatically continues this way.
Information such as record date and last access date of each document are saved.
Information of last written/read, backup dates and on-line/off-line status is saved for each CAS file.
Backup time is reduced by backing up only CAS documents not backed up.
When he deems necessary, system administrator can transfer documents according to date of creation and last access to new CAS files (only by using PaperWork interfaces). While transferring these CAS onto different media (e.g. DVD), he can save them to off-line. Even under these conditions, documents are included in search results. When user tries to open document, he/she is warned by a message explaining on which date and media document is transferred. Normal work continues after related media (DVD in this example) is put into system and made document on-line.

Example Usage Scenario;

Let us think that there are currently 800.000 scanned A4 size pages and in TIFF G4 format in our example organization archive. Let us suppose that the size of each page is about 50K.
Total size = 800.000 * 50 = 40.000.000 K / 1024 = 39.06 MB / 1024 = 38.14 GB document we have.
Let us again suppose that size of each CAS file is about 4GB. In this case;
38.14 / 4 = 9.5 that is 10 CAS files we have and installation on server is;
00001.CAS
00002.CAS
...
00010.CAS.
1. Let us think that after the first backup of these files new additional documents come into only 00010.CAS file. In this case only this CAS file will be backed up.
2. Let us think that documents in 00001.CAS file are older than three years. In this case, related file can be written onto DVD and erased from disk to have extra disk space. If user needs any of the documents in this CAS file, system demands the DVD having 00001.CAS files to be put into DVD drive. After DVD is put into drive, user can reach document.
3. Let us suppose that disk has broken down and bad sectors have formed on physical part of disk where 00002.CAS file exists. In this case, system administrator can restore from backup and runs system.
4. Let us think that these CAS files are on fiber RAID-5 disks and there is capacity problem. In case of need, less used ones from CAS files are transferred to a cheaper media (e.g. IDE disks, DVDs, USB disks etc.) and extra disk space is gained. Thus, we have more spaces on available hard disks for extensively accessed data.
5. When he deems necessary, system administrator may transfer documents in current CAS files into new CAS files according to various properties and save them on different media by compressing.

What is Hierarchical Storage Management (HSM)?

How does PaperWork HSM work?

Example Usage Scenario;