[Netarchivesuite-users] Upload errors

[Kåre Fiedler Christiansen]

On Wed, 2008-06-18 at 14:43 +0200, aponb at gmx.at wrote:
> >
> > As for recommendation:
> >
> > As I assume you are currently having the four machines in one geographic
> > location, I would suggest the following layout:
> >
> > 1) A bitarchive machine
> > Running the BitarchiveApplication. Try to restrict shell access to this
> > machine as much as possible.
> > 2) A harvester machine
> > Running four HarvestControllerApplications. If you use the
> > snapshot-harvest functionality, let one have "LOWPRIORITY", to take
> > those jobs.
> > 3) An access machine
> > Running the index server and a viewerproxy.
> > 4) An admin machine
> > Running the BitarchiveMonitorApplication, the ArcRepositoryApplication,
> > and the GUIApplication
> >
> >   
> Coming back to your recommendation, why is it necessary to have a 
> dedicated bitarchive machine?
> Do you think one machine can do the job for the bitarchive and the for 
> the access applications, so that I can use two Machines for Heritrix?

It isn't necessary, and it won't put much of a strain on the machine to run more applications on it.

My recommendation is based solely on the fact that you may want to have a bitarchive machine with heavier access restrictions and better security measurements to better protect your data. We designed our bitarchives to have a very high bit safety, and my recommendation may be biased by the fact that we have had such a big focus on that aspect.

Especially, if you give external access to your access machine, a flaw in our access application may give local read/write access to the bitarchive if it runs on the same machine.

In the end it is all a question of your needs and wishes, but with regard to performance there is no reason you couldn't merge the access and bitarchive machines.

Best,
  Kåre
-- 
Kaare Fiedler Christiansen - NetarchiveSuite developer
THE STATE AND UNIVERSITY LIBRARY, 
Universitetsparken 1, 8000 Aarhus C, Denmark.
Phone: +45 89462036