Manage Compliant Archive | FAST LTA Dokumentation

Create Compliant Archive

Please read all information fully before proceeding. The configuration of a Compliant Archive cannot be reverted due to 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.

➤ Navigate to Archives in the User Interface.
➤ Click on 'Add'.

➤ The dialog for creating archives will open.

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

The following options are available when selecting the Silent Bricks to be used:

Shared Stage and WORM Brick.
- The Stage Area is located on one or more non-WORM Bricks.
- The Stage Area can be extended at any time thereafter.
- This option enables the use of a faster FLASH Brick as a Stage Area for numerous small files.
Combined Stage and WORM Brick
- The Stage Area is defined on the WORM Brick during initial setup.
- The size of the Stage Area on this WORM Brick cannot be modified afterwards.
- The WORM Area begins immediately after the Stage Area.
- Consequently, the Stage Area occupies storage space on the WORM Brick.

Area	Maximum number of Silent Bricks
Stage	Up to 9 Silent Bricks or 9 Silent Brick FLASH units
WORM with Embedded Stage	Up to 2 Silent Brick WORM units
WORM with separate Stage Area	No limitation

The following guidelines are recommended to decide which of the two options to use.

A very large number of files requires a larger Stage Area. A rule of thumb is 3600 bytes stage per file.
A large number of small files require a faster stage, for which the use of a FLASH Brick is recommended.
➤ To create a combined archive, select a Brick and proceed as follows:
- ➤ Select a Brick of type WORM.
- ➤ Click the button 'Add to Archive and Stage'.
- ➤ Use the slider to select the desired size of the Stage Area.
➤ To create separate Stage and WORM Areas, 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 definitively correct. The configuration of WORM Storage cannot be undone.

Create Subvolumes

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

➤ Click 'Add'.

➤ Select the desired Volume mode.
- ➤ Compliance: Deletion within the retention period is not permitted.
- ➤ Enterprise: Deletion is possible via specific API calls, even within the retention period. This requires a special user. For further details, please contact our support team.

➤ Assign a name to the Subvolume.
➤ The Volume type to select depends on the solution to be bound:

Volume Type	Description
WORM	This Volume type archives files to the WORM Storage after the expiration of a predefined time, the 'Minimum age before archiving'. This time represents the duration in seconds since the last modification. Files of the WORM type do not have retention and therefore cannot be deleted.
WORM with Versioning	This Volume type functions like the Volume Type 'WORM' but allows files to be overwritten, enabling the creation of different versions of a file. Switching between versions is achieved by creating a Version File in the File system. See the section Switching Between Versions.
WORM with Retention	This Volume type functions like the Volume Type 'WORM' but allows retention periods to be specified in years, months, days, and minutes. Once this period expires, archived files become eligible for deletion. Deletion removes access to these files; however, the storage space is not freed and thus remains unusable.
WORM with Versioning and Retention	This Volume type combines the two previously described Volume types.
WORM with Retention (RWRO triggered)	This Volume type does not archive files after a set period but upon actively setting the file's read-only flag. As long as this flag is not set, the file remains in the mutable Stage Area. Additionally, it is possible to specify a retention period in years, months, days, and minutes. Once this period expires, archived files become eligible for deletion. Retention can also be specified externally per file via the 'Last Access Date'. Deletion removes access to these files; however, the storage space is not freed and thus remains unusable.
WORM with Retention and Versioning (RWRO triggered)	This Volume type does not archive files after a set period but upon actively setting the file's read-only flag. As long as this flag is not set, the file remains in the mutable Stage Area. Additionally, it is possible to specify a retention period in years, months, days, and minutes. Once this period expires, archived files become eligible for deletion. Retention can also be specified externally per file via the 'Last Access Date'. Deletion removes access to these files; however, the storage space is not freed and is therefore unusable. Furthermore, this option allows files to be overwritten, thus creating different versions of a file. Switching between versions is achieved by creating a Version File in the File system. See the 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 data which is not triggered is also archived, while remaining overwritable. This Volume Type is suitable for integration with software solutions that, in addition to the triggered archival data, also store meta-information that is not triggered but required for operation.

➤ Enable the creation of Safe Files in the 'Safe Files' tab. This will cause a file with the same name but the extension '.safe' to be created after the archiving process, signaling successful archiving externally.
➤ Safe Files can be created in either XML or text format.

➤ Additional settings can be configured depending on the Volume Type in the 'Miscellaneous' tab:

Switch	Description
Prioritize Ingests	This switch causes the Volume to be prioritized during archiving. This switch is advisable to prioritize a Volume with many small files over one with large files during processing, to prevent a backlog.
Robocopy Optimization	With this function, timestamps used by Robocopy for internal management are ignored by the automatic archiving. This switch is strongly recommended when using Robocopy.
Do Not Archive 0-Byte Files	It is often possible to determine in advance whether empty files will be created or if they are errors. This switch can be used to prevent archiving of such files if necessary.
Prevent Renaming of Empty Directories	When enabled, renaming of empty directories is prevented.
Prevent Renaming of Files	When enabled, renaming of files is prevented.
Read Before Append	Enable this feature if your software solution modifies files by appending new content. This function ensures that the file is fully loaded before new data is appended.
Smart Replace	Enabling this feature allows files in the file system to be deleted even before the retention period expires. However, deletion results in the file being renamed to include the presumed deletion timestamp. This enables verifiable problem resolution for incorrectly written files.

Enable Caching

Starting with version 2.35.0.2, the Silent Brick System supports definable caching rules for subvolumes. This enables configuring the duration for which files of specified types and sizes remain in the staging area.

INFO

Caching is only supported in archives using Silent Brick FLASH as the staging area.

To activate caching, proceed as follows:

➤ Navigate to the "Caching & Eviction Policies" tab within the subvolume.

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

➤ Specify a retention period greater than 0 in the "Eviction Policy" section.

Switching Between Versions

When using versioned Volume types, the file system allows switching between different versions. The switching is performed via a version file associated with the respective file.

Example:

The data file abc.pdf is to 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' - where n is any number to indicate the corresponding version

The text 'revert' to indicate the top revision

examples

type abc.pdf.safe

echo switch 3 > abc.pdf.version

echo revert > abc.pdf.version

Replicate the Compliant Archive locally

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

➤ Click on the respective Volume.
➤ Click on the “General” tab.
➤ Click the “Replicate” button.

➤ The “Replicate” window opens.

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

Remotely replicate Compliant archive

Establish remote connection

To create remote replication of a Compliant archive, first establish a connection between both systems. Follow the instructions provided. Create remote connection.

Creating the replication

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

➤ The “Replicate” window opens.

➤ Select a name for the replica.
➤ Select “Encrypt Volume” to encrypt the replica.
➤ Enable 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.
➤ Verify the replication status using the Compliant Archive overview.

Verify archiving

➤ Click on the corresponding Compliant archive.
➤ Click the “Reports” tab.

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