/
How volume data is stored in tia® Content Server

How volume data is stored in tia® Content Server

The tia® Content Server stores operation information and configurations with the repository in a separated folder. The data is signed and protected from manipulation.

The folder is located below the repository root folder .kgs encoded (BASE32) and split by the storage path configuration. See Storage path.

 

The table below lists the locations based on configuration:

 

contrepinpath

false (default)

true

maxfolders

 

4

(4 is default for content services: splitfilesystemv2, netapp, icas)

<repositoryRoot>/FZVW/O4Y

<repositoryRoot>/<repo>/FZVW/O4Y

8 or 16

(8 is default for content services: splitfilesystemv3, netappv3, icasv3)

<repositoryRoot>/FZVWO4Y

<repositoryRoot>/<repo>/FZVWO4Y

 

When backing the repository storage up, include this system folder as well in the backup. The configuration data is important when restoreing.

It is essential that the data is readable and writeable for Content Server to function properly.
If tia® Content Server handles the retention management for supported storages and has full access rights, .

Is this not possible as for WORM storages, see Repositories on WORM storage.

For blob storages like Azure Blob Storage and S3 it is vital to let Content Server handle the retention of the .kgs encoded (BASE32)-folder.



 

 

Related content

Volume Measurement and Storage Configuration
Volume Measurement and Storage Configuration
More like this
Storage path
Storage path
More like this
Multi root configuration (splitfilesystemv3, netappv3, icasv3)
Multi root configuration (splitfilesystemv3, netappv3, icasv3)
More like this
Content Service
Content Service
More like this
Config Data Service - Type storage (tC)
Config Data Service - Type storage (tC)
More like this