General Q&A About Cassandra Message Store
(Doc ID 2366575.1)
Last updated on MAY 05, 2021
Applies to:Oracle Communications Messaging Server - Version 8.0.2 and later
Information in this document applies to any platform.
Q1. With Cassandra message store, how can an admin remove a message from a particular users mailbox? For example, say a message that comes in that is deemed unsafe and needs removed from the users mailbox. In the classic message store we could traverse into the users mail box directory, find the message, remove it and then reconstruct the mailbox. How is this done in the Cassandra message store?
Q2. As an example, say we want to build an entirely new system and on that system we install the Cassandra message store for the backend. How would we migrate users from the current classic message store to the new one, if the systems are disconnected? Does the imsrestore work with the Cassandra message store?
Q3. Regarding backups of the Cassandra Message store, does Cassandra message store support imsbackup?
Q4. Where do store.expirerule files go in a Cassandra-based store?
Q5. Does imsrestore still work the same way?
Q6. Is the mailMessageStore attribute used with the Cassandra store?
Q7. Is the single-copy nature of the message store applicable to Cassandra?
Q8. We currently have "retraction" (removing mail accidentally sent to inappropriate recipients) processes which are based on imexpire or IMAP admin proxy and delete/expunge.
All of that should work the same, regardless of classic store vs cassandra store. But we are just wondering... if Cassandra makes use of single copy, might it be possible to remove the message at the Cassandra layer? Might that be quicker than our current methods?
Q9. Does store.relinker.enable do anything on a Cassandra store?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document