Do following in a browser

Start Program

• Go to http://$GUIadminserver:$http-port/HarvestDefinition/

  • where GUIadminserver and http-port are specified in the deploy configuration file under the application named dk.netarkivet.common.webinterface.GUIApplication

  • In the one-machine setup (deploy_example_one_machine.xml ) the link will be : http://localhost:8074

• Go to the bitpreservation site:

  • Click on Bitpreservation in the side bar.

This page should currently be the same as last time, except that the replicas should have a number of files (the same number, different from 0):

Filestatus for: KBN
Number of files: 18
Missing files: 0
Last update at 1/1/1970 1:00:00AM
Update

Filestatus for: CSN
Number of files: 18
Missing files: 0
Last update at 1/1/1970 1:00:00AM
Update

Filestatus for: SBN
Number of files: 18
Missing files: 0
Last update at 1/1/1970 1:00:00AM
Update

Checksum status for: KBN
Number of files with error: 0
Last update at 1/1/1970 1:00:00AM
Update

Checksum status for: CSN
Number of files with error: 0
Last update at 1/1/1970 1:00:00AM
Update

Checksum status for: SBN
Number of files with error: 0
Last update at 1/1/1970 1:00:00AM
Update

• Do some refreshes of the bitpreservation page and verify that the number of files should now be updated automatically without clikcking on update. Files under upload will be shown as missing files until they are uploaded.
• Update the filelist for the replicas. Do the following for each replica:

  • Click on Update for the filelist for the replica. As this update can potentially take hours, this update is performed in the background, and the last update value when the update operation has completed

  • Check that a positive number of files is found, probably around 15-20 files, though at least 6 (minimum 2 per harvest).
  • Check that a no missing files are found for the replica.
• Check that no replica has a different amount of files.
• Update the checksum lists for the replicas.

  • Click on Update for the checksum status for any replica (since no checksum status has been found for any replica, then the checksum status for all replicas are updated). As this update can potentially take hours, this update is performed in the background, and the last update value when the update operation has completed.

  • Check that no replica has any corrupt files (number of files with error).

• Check that each replica no has the same 'Last update' date for both the filelist and checksum status. And that this date is now (or just a few moments ago).