Migrated index storage space

Content Manager OnDemand supports automatic migration of indexes from the database to archive storage so that you can maintain seldom used indexes for long periods of time. However, you should migrate indexes only after you do not need to retrieve reports that refer to the indexes. For example, suppose that all of the queries for a report occur in the first 24 months after the report is loaded into the system, after that time, there are no more queries for the report. The indexes might be eligible to be migrated from the database to archive storage. Migration of index data is optional; you can choose to migrate indexes for all, some, or none of the application groups on your system. In addition, you determine the length of time that indexes stay in the database before Content Manager OnDemand migrates them to archive storage.

You can use the following calculation to determine the archive storage space that is required to hold migrated indexes: ArchiveMediaDBSpace = ( Database size per month * compression ratio ) * ( life of data - months before migrating data )

For example, if the index data requires 1.5 MB of space in the database per month, you need to maintain the indexes for 84 months, and the indexes remain in the database for 24 months before being migrated, then the archive storage required to hold the migrated indexes is: ArchiveMediaDBSpace = ( 1500000 * .33 ) * ( 60 ) = 29,700,000