Sharon Jones, the system administrator at the JKL Toy Company, wants to archive older data currently stored on one of the systems to media. You can use this example to plan and configure archive policies using BRMS.
The JKL Toy Company stores large monthly sales invoices in an Accounts database on their JKLPROD system. Unfortunately these records have been kept on the system for several years and the large volume of data is negatively impacting the performance of the application. JKL wants to archive any records that are older than two years old. For this older data, the company wants to save it off the system to media, but ensure that it can be accessed, if necessary. Although this data is not current, employees occasionally need to access payment histories and other account information for these accounts. Users will typically be responding to a customer inquiries into this data, such as validating payment or addresses. Accounts that are younger than two years are considered active. Data in these accounts are updated regularly and are saved as part of the backup policy for JKLPROD system.
For data that is older than two years, they would like to save it to media but retain it in case it is needed. Using the BRMS archive function, Sharon plans to save these monthly sales records to write once, read many (WORM) media and set criteria on what objects will be saved. She plans to create an archive policy for this data.
This scenario assumes that several prerequisite steps have been completed and tested prior to beginning any steps. These prerequisites are assumed to have been completed for this scenario: