Page History

...

• Auditing for site differences: Running an audit will check if there are differences between DSpace Content and AIP backup content. A full site AIP audit can be run from the command line, or scheduled via a cron job (or similar). For example, the following command will run a site-wide audit for a DSpace site with a handle.prefix of "10673" (and writes the results of the audit to a "siteaudit.log" file).

  Code Block
  [dspace]/bin/dspace curate -t auditaip -i 10673/0 -r - > siteaudit.log

  • This command runs the "auditaip" task on your entire site (The identifier "[handle-prefix]/0" refers to the entire DSpace Site...in this case we used the example handle-prefix of "10673")
  • The "-r -" pare part of this command ensures that the results of the audit are reported back to you on the command line, rather than being logged to the main dspace.log file. 
  • Then the "> siteaudit.log" takes those reported results and writes them to a "siteaudit.log" file.

• A refresh of your full backup: If you decided not to synchronize your backup (as described above), you will want to ensure that you are re-running your entire site replication on a scheduled basis.  For example, the following command will regenerate & transmit AIPs for every object in a DSpace site with a handle.prefix of "10673" (and writes the results of the audit to a "sitebackup.log" file).  It's nearly identical to the "auditaip" command above, except that you are executing "transmitaip" and writing to a different log file.

  Code Block
  [dspace]/bin/dspace curate -t transmitaip -i 10673/0 -r - > sitebackup.log

...