In planning for replication of data from one location to another and/or disaster recovery scenarios within Netmail Store, it is advisable to ensure that you are both fully utilizing the system metadata automatically stored with every stream as well as adding custom metadata that will allow you to create dynamic rules for distributing your content. Metadata can be stored with a stream from one of several sources outlined below.
The “Castor-System-Cluster” metadata attribute is automatically stored with each stream in Netmail Store based on the cluster name specified in your cluster or node configuration files. This attribute ensures that a stream that is replicated to a disaster recovery cluster can always be traced back to its cluster of origin in the event of a disaster. This is particularly important in scenarios where multiple satellite clusters are replicated into a centralized disaster recovery cluster.
Messaging Architects recommends a naming scheme similar to: uniquename_yourcompanydomainname (e.g., cluster1_messagingarchitects_com) for each cluster to ensure global uniqueness. In addition to the cluster name, the date the stream was stored in Netmail Store (Castor-system-created) is also written with each stream and can be used for date-based rules.
Content File Server Metadata
If you are using Caringo’s File System Gateway (FSG) client, the following metadata is stored with CFS streams and can be used for content distribution or replication rules:
- Castor-CFS-Filepath: The full path to the file when it was originally stored
- Content-Disposition: The filename of the stream
- Castor-CFS-Server: The name of the server from which the file was originally stored
- Castor-CFS-Version: The version of the CFS software that originally stored the file
- Content-Type: The file's mimetype
- CAStor-CFS-CFSID: The name of the mountpoint id through which the file was originally stored
- Castor-CFS-FileId: The filesystem id for the file in the CFS namespace
- Castor-CFS-Uid: The file's user id at the time it was stored
- Castor-CFS-Gid: The file's group id at the time it was stored
- Castor-CFS-Mode: The file's permission mode in decimal at the time it was stored
If you are using a custom-developed client to write to Netmail Store, additional HTTP headers (e.g., Content- Language, Content-Type, etc.) and optional custom metadata can also be stored with a stream to aid in content distribution and processing with the new Content Router. CFS also allows definition of custom metadata at the mountpoint level.