Manage Compliant Archive

Create Compliant Archive

Please read the information completely first. The configuration of a Compliant Archive cannot be undone by the WORM storage.

The 'Compliant Archive' function is not supported by the Silent Brick Pro System.

To create a new Compliant Archive, proceed as follows.

➤ Switch to Archives in the User Interface
➤ Click on 'Add'

➤ The dialog for creating archives opens

➤ Assign a name for the archive
➤ Assign a description for the archive
➤ Select 'Encrypt Archive' to encrypt the archive

When selecting the Silent Bricks to use, the following options are available:

Shared Stage and WORM Brick
- The Stage Area is located on one or more non-WORM Bricks
- The Stage Area can be expanded at any time afterwards
- This option allows for a faster FLASH Brick to be used as the Stage Area for many small files
Combined Stage and WORM Brick
- The Stage Area is defined on the WORM Brick upon initial creation
- The size of the Stage Area on this WORM Brick cannotno longer be changed
- The WORM area begins after the Stage area
- The Stage area thus consumes storage space of the WORM Brick

Area	Maximum number of Silent Bricks
Stage	Maximum 9 Silent Bricks or 9 Silent Brick FLASH
WORM with Embedded Stage	Maximum 2 Silent Brick WORM
WORM with separate Stage area	No restriction

To decide which of the two options should be used, the following rules are recommended.

A very large number of files require a larger Stage area. A rule of thumb is3600 Bytes Stage per file.
A very large number of small files require a faster Stage, which makes the use of a FLASH Brick advisable.
➤ To create a combined archive, select a Brick and proceed as follows:
- ➤ Select a Brick of type WORM.
- ➤ Click the 'Add to Archive and Stage' button.
- ➤ Use the slider to select the desired size of the Stage Area.
➤ To create a separate Stage and WORM area, proceed as follows:
- ➤ Select one or more Bricks of type WORM.
- ➤ Click 'Add to Archive'.
- ➤ Select one or more Bricks of type Brick or FLASH.
- ➤ Click 'Add to Stage'.

CAUTION

Confirm your selection using the 'Confirm' button only when the configuration is definitely correct. The configuration of WORM storage cannot be undone.

Create Subvolumes

➤ Select the desired Compliant Archive in the sidebar.
➤ Switch to the Sub-Volumes tab.

➤ Click on 'Add'.

➤ Select the desired volume mode.
- ➤ Compliance: Deletion within the retention period is not possible.
- ➤ Enterprise: Deletion is possible through certain API calls even within the retention period. These require a special user. For further details, please contact our support.

➤ Assign a name for the sub-volume.
➤ The volume type to be selected depends on the solution to be bound:

Volume Type	Description
WORM	This volume type archives files in the WORM storage after a preset time 'Minimum age before archiving' has elapsed. This time describes the duration in seconds that has passed since the last modification. Files of the WORM type do not receive retention and therefore cannot be deleted.
WORM with Versioning	This volume type works just like the volume type 'WORM', but offers the ability to overwrite files and thus create different versions of a file. The switch between versions occurs through the creation of a version file in the filesystem. See section Switching between Versions.
WORM with Retention	This volume type works just like the volume type 'WORM', but allows specifying retention in years, months, days, and minutes. After this time has expired, archived files can be deleted. Deletion removes access to these files, but the storage space is not freed and is therefore no longer usable.
WORM with Versioning and Retention	This volume type represents a combination of the two previously described volume types.
WORM with Retention ( RWRO triggered )	This volume type does not archive files after a certain period, but rather after the active setting of the Read-Only flag of the file. As long as this flag is not set, the file remains in the mutable stage area. Additionally, there is the option to specify a retention period in years, months, days, and minutes. After this time has expired, archived files can be deleted. The retention can also be provided externally based on the 'Last Access Date' per file. Deletion removes access to these files, but the storage space is not freed and is therefore no longer usable.
WORM with Retention and Versioning ( RWRO triggered )	This volume type does not archive files after a certain period, but rather after the active setting of the Read-Only flag of the file. As long as this flag is not set, the file remains in the mutable stage area. Additionally, there is the option to specify a retention period in years, months, days, and minutes. After this time has expired, archived files can be deleted. The retention can also be provided externally based on the 'Last Access Date' per file. The deletion removes access to these files, but the storage space is not released and is therefore no longer usable. Additionally, there is the option to overwrite files and thus create different versions of a file. The switch between versions occurs through the creation of a version file in the filesystem. See section Switching between Versions.
WORM with Retention ( RWRO triggered, Autosafe )	This volume type fundamentally represents a volume type "WORM with Retention (RWRO triggered)". Additionally, the autosafe feature ensures that even non-triggered data is archived, while remaining overwriteable. This volume type is suitable for integration with software solutions that, in addition to the triggered archive data, also store meta-information that, while not triggered, is necessary for operation.

➤ Activate the creation of safe files in the 'Safe Files' tab. This will create a file with the same name but with the extension '.safe' after the archiving process to signal the successful archiving externally.
➤ The safe files can be created in XML or text format.

➤ In the 'Miscellaneous' tab, further settings can be made depending on the volume type:

Switch	Description
Prioritize Ingests	This switch will prioritize this volume during archiving. This switch is suitable for prioritizing a volume with many small files in processing over a volume with large files to prevent a backlog.
Robocopy Optimization	With this function, timestamps that Robocopy uses for internal management are ignored by the automatic archiving. This switch is strongly recommended when using Robocopy.
Do Not Archive 0-Byte Files	Often, it can be determined in advance whether empty files can be created or if they are errors. This switch can potentially prevent the archiving of such files.
Prevent Renaming of Empty Directories	When activated, renaming of empty directories is prevented.
Prevent Renaming of Files	When activated, renaming of files is prevented.
Read Before Append	Activate this feature if your software solution modifies files by appending new content. This feature ensures that the file is fully loaded before new data is appended.
Smart Replace	By activating this feature, files in the filesystem can be deleted even before the retention period expires. However, the deletion will rename the file to a filename that includes the supposed deletion timestamp. This allows for a verifiable problem resolution in the case of incorrectly written files.

Enable Caching

Starting from version 2.35.0.2, the Silent Brick System supports definable caching rules for subvolumes. This allows you to set how long files of certain types and sizes remain in the staging area.

INFO

Caching is only supported in archives with Silent Brick FLASH as the stage.

To enable caching, proceed as follows:

➤ Switch to the "Caching & Eviction Policies" tab in the subvolume.

➤ Enable caching by checking the box for "Keep Files in Cache After Ingest."
➤ Define retention rules for the files using the "Add" button.

➤ Define a retention period in the "Eviction Policy" section that is greater than 0.

Switching between versions

When using versioned volume types, you can switch back and forth between different versions in the filesystem. The switching is done via a version file of the corresponding document.

Example:

The data abc.pdf should be switched.

Navigate to the file
Check the version by opening the (invisible) safe file abc.pdf.safe
Create the version file "abc.pdf.version" with one of the following contents

'switch n' - n is any number to display the corresponding version

The text 'revert' to display the top revision

Examples

CODE

type abc.pdf.safe

CODE

echo switch 3 > abc.pdf.version

CODE

echo revert > abc.pdf.version

Replicate Compliant Archive locally

To create the local replication of a Compliant Archive, proceed as follows:

➤ Click on the corresponding volume.
➤ Click on the 'General' tab.
➤ Click on the 'Replicate' button.

➤ The window “Replicate” opens.

➤ Choose a name for the replica.
➤ Click the “Add” button to create the replica.
➤ The window “Add Bricks to Volume” opens.
➤ Add a sufficient number of bricks to your replication archive.
➤ Check the replication status using the archive overview.

Remotely replicate compliant archive

Establish remote connection

To create the remote replication of a compliant archive, first establish a connection between both systems. Follow the description.Create remote connection.

Creating the replication

➤ Click on the corresponding compliant archive.
➤ Click on the 'General' tab.
➤ Click the “Create Replication” button.

➤ The window “Replicate” opens.

➤ Choose a name for the replica.
➤ Select 'Encrypt Volume' to encrypt the replica.
➤ Activate the 'Remote Replication' button and select a remote connection.
➤ Click the “Add” button to create the replica.
➤ Open the target system.
➤ Add a sufficient number of bricks to your replication volume.
➤ Check the replication status using the Compliant Archive overview.

Check archiving.

➤ Click on the corresponding compliant archive.
➤ Click on the 'Reports' tab.

➤ In the upper area, you can download all existing archiving reports.
➤ In the lower area, you can check pending files by type.