I'm in the process of retiring two legacy business applications this year that house a mix of database records and various file attachments like PDFs, invoices, and emails. I'm currently exploring dedicated archiving platforms such as Archon Data Store, OpenText InfoArchive, Veritas, and Mimecast, but I'm not sure how to determine the right choice. What factors should I consider when evaluating a tool that can handle queryable structured data, rather than just cold storage?
6 Answers
For archiving emails and their attachments, consider using a dedicated email server that handles Maildir or Mailbox formats. As for databases, typically, you'd want to use the application’s built-in tools for backups or file restoration. For everything else, traditional backup and restore methods work well. Just remember to maintain two copies of everything in distinct locations to ensure safety.
This is a major consideration in any business. Ideally, you'd want to migrate old data into your current system instead of leaving it behind. Those involved in management often don't prioritize the old systems as much as they should, leaving operations to deal with them long-term. I witnessed a scenario where an old Oracle system continued to be used for two years after a switch, mainly because some users hadn’t exported all the historical reports from it. Make sure to engage with decision-makers early on to avoid complications later.
When evaluating your archiving options, be aware that if the data can be queried on demand, especially if it's in a proprietary format, that may not actually be true archiving. The specific storage method plays a huge role in keeping data queryable. Sometimes you might even need to keep the application online but in a read-only mode, depending on how your data is structured. Can you share more about the specific application or data type you are planning to archive? Also, consider factors such as data availability, cost, volume, and compliance requirements. It's all about understanding how much access you need and the restoration capabilities.
Before you choose an archiving solution, think about your information retention policy. Why is this data being retained instead of destroyed? If a platform becomes obsolete, the data might feel like a burden rather than an asset. Will this data still be useful in the long run, or is it safer to just let it go?
HubStor is a great tool for this situation. It allows you to pull in data from core systems and can restore it on demand. Collaborating with your business unit helps clarify the retention needs so you can find the best solution!
My approach is to leave it up to the application owners to decide the fate of their data. If there's any necessary data left, it should ideally be migrated to the new system during the transition. Keeping an eye on what data needs to go is crucial.

Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures