Hi Community
For a while now SM has had a great feature called second path which allows a second storage path to be added to a domain account.
this function allows emails over X days to be moved to a secondary storage path creating tired storage.
the added benefit of this function is it provides resiliency for disconnects as the data lives on an SMB/ NFS share, emails are spooled locally until the second path storage reconnects and are then moved on the next scheduled task to the share.
Unfortunately Archival storage does not have the same function.
Currently if shared storage disconnects we get data drift with archive emails landing in a mount path and when shared storage reconnects a manual process needs to be action to fix the data drift, its a tedious task at best not to mention the potential of data loss if not dealt with correctly.
the feature request here is to have archive storage mirror the same function as second path storage.
Benefits.
- better utilization of shared storage away from production allowing production storage to be kept smaller and more portable. - data portability.
- improved functionality if the second storage path is temporarily disconnected, simply put primary storage can work independently of shared storage in the event of a disconnect, planned or unplanned and reconnects gracefully. - better resilience and uptime lessening the impact to mailflow.
- Storage tearing for Archival - indexes or data under X Days to remain on faster local SSD and only archived data older than X will be moved to the shared storage. - better use of tiered storage that can work independently of production cluster.
- all of these benefits together allow SM to deliver a more enterprise level of functionality to better compete with O365 and exchange hosting significantly setting apart SM from other competitors..
Here for your consideration.
""Cheers
G