This is a little reflection I wrote some years back that I just uncovered. I think most of the key points are still relevant as they ought to be. Regardless of what technology is used archiving is a generic information managment technique (like backups) that should be approached from the high level, first principles before assessing what tools an organisation can leverage.
Why Archive Anyway? To Manage RISK & Manage RETURN
- Reduce storage costs (acquisition and management).
- Improve email/file server performance.
- Manage unstructured information – security, business value, risk...
- User accessibility and user expiration/termination
- Simplify Discovery
- Simplify Protection (backup)
What to Think About?
- A long term perspective must be taken in considering an archive product. This product/mechanism/solution will be a strategic platform and is going to be there for a long time!
- Growth – staff/data?
- Mergers, multiple business unit integration?
- Retention policies should match the vendor’s longevity!!
- Data portability - can I move my archives around?
- Manageability and Security and Reporting
- Other applications that the archive may touch/be touched by
- Role based administration of the archive application
- Trending feedback – scale up before you hit the wall
- Focus on Content Intelligence
- Key organisational data types and storage locations
- Where and how will data be created
- Protect your archive application like a Tier 1 application
- The archive application must be deployed as if it were a Tier 1 system...it now stands as a critical link in business data access.
- Relate policy to Directory Services.
- Don’t re-invent the wheel...you will already have IT governance policy in some basic form in Directory Services...ensure your solution can utilise and hinge from this.
- IT Budget generally grows at about 2%, but Storage grows at about 7%...Stress that archiving is a ‘storage’ application not an email application.

