<?xml version="1.0"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.1 20050630//EN" "http://uploads.ingentaconnect.com/docs/dtd/ingenta-journalpublishing.dtd">
<article article-type="research-article">
  <front>
    <journal-meta>
      <journal-id journal-id-type="aggregator">72010361</journal-id>
      <journal-title>Archiving Conference</journal-title>
      <abbrev-journal-title>archiving</abbrev-journal-title>
      <issn pub-type="ppub">2161-8798</issn><issn pub-type="epub"/>
      <publisher>
        <publisher-name>Society of Imaging Science and Technology</publisher-name>
        <publisher-loc>7003 Kilworth Lane, Springfield, VA 22151, USA</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta><article-id pub-id-type="doi">10.2352/issn.2168-3204.2009.6.1.art00039</article-id>
      <article-id pub-id-type="sici">2161-8798(20090101)2009:1L.183;1-</article-id>
      <article-id pub-id-type="publisher-id">ac_v2009n1/splitsection39.xml</article-id>
      <article-id pub-id-type="other">/ist/ac/2009/00002009/00000001/art00039</article-id>
      <article-categories>
        <subj-group>
          <subject>Articles</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>A Case Study in Distributed Collection Monitoring and Auditing Using the Audit Control Environment (ACE)</article-title>
      </title-group>
      <contrib-group>
        <contrib>
          <name>
            <surname>Smorul</surname>
            <given-names>Michael</given-names>
          </name>
        </contrib>
        <contrib>
          <name>
            <surname>JaJa</surname>
            <given-names>Joesph</given-names>
          </name>
        </contrib>
      </contrib-group>
      <pub-date>
        <day>01</day>
        <month>01</month>
        <year>2009</year>
      </pub-date>
      <volume>2009</volume>
      <issue>1</issue>
      <fpage>183</fpage>
      <lpage>186</lpage>
      <permissions>
        <copyright-year>2009</copyright-year>
      </permissions>
      <abstract>
        <p>We describe the deployment of the Audit Control Environment (ACE)[1] on the Chronopolis distributed archive environment. The ACE system provides a scalable, auditable platform to actively ensure the availability and integrity of digital archival holdings over the lifetime of the archive.
 The core of ACE is a small integrity token issued for each monitored item that is part of a larger, externally auditable cryptographic system. Two components that describe this system, the Audit Manager and Integrity Management Service, have been developed and were released in October 2008.ACE
 allows for the policy driven active monitoring of collections on a variety of disk and grid based storage systems. Each collection in ACE is subject to monitoring based on a customizable policy.The Chronopolis archiving environment consists of three sites located at the University of Maryland(UMD),
 San Diego Supercomputing Center(SDSC)/UCSD Libraries, and the National Center for Atmospheric Research(NCAR). Data that has been ingested into storage at SDSC is replicated to UMD and NCAR. Current collections from data providers in Chronopolis range from a relatively few large files to collections
 containing millions of mostly small files. In total, these collections represent over 5.5 million files and 17 Terabytes of data.With three copies of each object, the problem of ensuring the integrity of each copy across the three sites arises. An ACE Audit Manager at each site provides
 continuous monitoring of files to ensure no corruption occurs locally. In addition, periodic audits of each collection across the sites are made to ensure that the collection contents are consistent across all three sites.We describe the deployment and performance of the Audit Manager
 at each of the three sites. Specifically, we compare peak theoretical ACE performance against varying collections.</p>
      </abstract>
    </article-meta>
  </front>
</article>
