iArchive

Compressed, Central Data Repository for iWatch™

iArchive™ is an optional utility for iWatch™ that allows organizations to maintain their iWatch™ data in compressed format on a central repository. Retention times for performance data can be significantly extended, while lowering overall storage costs.

Efficient, 20:1 Compression

iArchive™ compresses data by a ratio of 20:1 (95%), dramatically extending retention times for iWatch performance details. And because centralized storage is typically far less costly than the high-performance storage used on production class servers, implementing iArchive™ can often yield a compelling ROI based on storage savings alone.

Transparent Operation

The presence of iArchive™ is transparent to iWatch™ end users: if the data requested by the user is not found in the local iWatch™ database, iWatch™ will automatically look for it in the iArchive™. Impact on network traffic is also negligible: since iArchive™ compresses data before it is transmitted to the archive, in most cases this means a 1 to 2MB file is transmitted to the iArchive™ not more than a few times an hour.

Query Offload

iArchive allows organizations to shift the most intensive queries that might occur against iWatch™ data (for example, for post-event analysis) off of their production servers.

Audit & Compliance

iArchive™ can also provide significant benefits when iWatch™ data is used for Audit & Compliance applications. By allowing organizations the flexibility to run updated or modified audit polices against retained “raw” iWatch™ data, they may actually mitigate risks associated with errors in policy deployment.

Components & Implementation

An iArchive™ installation will consist of an iArchive Server and one or more iArchive Agents.
The iArchive™ Server is installed on the central repository, and can service many
iWatch™ instances. For example, a department using ten iWatch™ instances to
monitor five Sybase instances and five Oracle instances may use a single instance of
the iArchive™ server – provided that the underlying OS or file system is similar across
all of the platforms.

Other than the hardware and OS, no additional prerequisites are required to run the
iArchive™ Server. It does not require licensing of third-party RDMS software or other
tools; iArchive™ runs and operates in the same self-maintaining structure as your native
iWatch™ database.

One iArchive™ Agent is also required for each iWatch™ Server instance; this is installed on
the same host as the iWatch™ Server. In the example above, one (1) copy of the iArchive™
server would be installed for the entire department, and a total of ten (10) iArchive™
Agents would be installed, to allow each iWatch™ Server to communicate
with the Archive.

Note that mixed OS deployments may require a separate iArchive™ Server for each file
system type. For example, if the example above changed to five instances of Sybase on
Solaris, plus five instances of SQL Server on Windows – a separate iArchive™ would be
required for both the Solaris and the Windows databases.