The data of the archive is always located in a single directory. This is always the data directory in the archive installation.

It is however still possible to use multiple storage for the archive. This can be a very useful feature. It is possible, for example, to store  recent data in a fast (more expensive) storage and and older data in a slower (cheaper) storage.

The data folder of the archive should in the case not directly contain the data but point with symbolic links to the actual storages.

This is possible with all of the supported open archive versions.

Since 2024.02 additional support for this configuration is added to the harvester process:

• It is possible to configure a dedicated harvester for each storage, Harvesters for different storages can run simultaneously 
• The catalogue can be cleared for a specific storage
• The incremental harvester can be configured to run for a specific storage, so that also can be used in a configuration with multiple storages

These new feature will explained with an example. In our example we have an archive which consists of two storages, the warm and cold storage.

The warm storage contains the recent data. After a configured period data is moved from the warm storage to the cold storage.

The data directory contains of two sub directories warm en cold. Both directories are symbolic links to the actual storages.

To configure a dedicated harvester for each storage the following configuration can be used.

	<scheduledArchiveTask>
		<internalHarvesterTask id="harvester warm storage">
			<storage>warm</storage>
		</internalHarvesterTask>
		<description>harvester warm storage</description>
		<startTime>03:00:00</startTime>
		<endTime>20:30:00</endTime>
		<runInterval>2</runInterval>
		<active>false</active>
	</scheduledArchiveTask>
	<scheduledArchiveTask>
		<internalHarvesterTask id="harvester cold storage">
			<storage>cold</storage>
		</internalHarvesterTask>
		<description>harvester cold storage</description>
		<startTime>03:00:00</startTime>
		<endTime>20:30:00</endTime>
		<runInterval>2</runInterval>
		<active>false</active>
	</scheduledArchiveTask>