Case Scenario (Mirroring to Cold Storage AWS S3 - Google Cloud)

Mirroring activation

This is the main metadata descriptor that determines which content is eligible for mirroring. These metadata descriptors must exist in all metadata schemas that are to be applied to objects that can be mirrored. In all metadata schemas, this descriptor must have the same IECODE, and the descriptor must be of type Boolean in all of them.

Metadata for mirroring policies

These metadata descriptors are used to decide the destination of each file or folder in the mirrors. Depending on the values found in these descriptors for each file or folder, it will be possible to determine in which storage providers the content will be mirrored. These metadata descriptors must exist in all metadata schemas that are to be applied to objects that can be mirrored.

Hierarchy

The Mirroring module selects items for mirroring based on their metadata. This can be done from the container level down (folder mode) or from the item level up to the container root (file mode).

Usually, folder mode is preferred. It starts from the root, checking each folder to see if it should be mirrored. If a folder is marked for mirroring, all its contents are mirrored too. File mode starts from the last item and checks upwards to see if it should.

Adding a folder to a mirroring plan

First of all, we need to select a container within our tree of nodes that has an Object Metadata Schema with the fields we configure for our mirroring.

Then we will choose the folder we would like to mirror.

After accessing its metadata, we will be able to configure it to agree with the policies we have set up; in this case, we set up PRESERVED to yes to activate the process. And 2 other metadata that will mirror its content with Google Cloud.

When the process starts (we recommend a daily or weekly interval), we can see its progress in our log, being able to gather information of the steps and errors if any.