 |
|
|
|
 |
Compliance Software IMS DB2 Mainframe Oracle |
|
|
TITAN Archive™ Supports Compliance and Data Management Needs
With an efficient, off-the-mainframe architecture, TITAN Archive lets you make the most of your high-performance storage area network (SAN) to protect and manage your archived data. The archive is designed and managed from an easily navigated Java interface that can be deployed as needed across the enterprise or secured to a single location.
By removing archived data from operational data storage, TITAN Archive allows you to recover large areas of your database, reducing overall operational costs and resource usage. By reducing the size of the database, maintenance tasks, such as database reorganizations, will take less time to perform, further reducing your costs of business.
The heart of TITAN Archive is the archive appliance, a LINUX server designated specifically for TITAN Archive processing. NESI can provide a preconfigured appliance for you, or you can install and configure an existing server to act as the appliance.
Both data and metadata are stored in an encapsulated archive data object (EADO™). The EADO format is independent of the source DBMS and can be accessed or queried using standard SQL queries or reports. TITAN Archive also provides the following utilities:
 |
|
| • |
The unload utility lets you format archived data in a standard load file that can be used to create a new database. |
| • |
The replay utility allows you to retrieve the archived data from the EADO™ in its original, bit-for-bit format. |
Key Features
|
|
| • |
Archives large amounts of data efficiently, with minimal or no effect on operational data store |
|
|
| • |
Stores archived data off of the mainframe, in your secured SAN or other networked locations |
|
|
| • |
Manages data for extremely long time periods, whether or not the DBMS continues to be maintained |
|
|
| • |
Protects against data loss |
|
|
| • |
Protects against data modification (either malicious or accidental) |
| • |
Provides access to the data that is independent from the original application and environment |
| • |
Stores a full explanation of the data (metadata) |
| • |
Persists through changes in application and data structure |
| • |
Provides a simple interface for planning and maintaining archive strategy |
| • |
Supports encryption and signature technology for archived data |
|
|
|
|
