1) Why does version 3.0 have quite a few more nodes than previous versions?

There are various reasons for this increase.
First, certain node information maintained by the server was not formerly
accessible.  It now is.
Second, a bug fix has allowed more nodes to be correctly scanned.  
Third, normal node count growth over time has occurred.

2) Why does version 2.0 have a fewer number of nodes (versus version 1.2) yet number of 
   files and total data size has grown?
   
Analysis of this run showed that approximately 80 nodes were not surveyed due to an 
internal problem that prevented the script from getting information on those nodes.
Furthermore, approximately 300 nodes were removed from the backup system and 340 new
nodes were added. The net effect was a reduction in total nodes.  

The new nodes identified by this run accounted for much of the growth in terms of 
file counts and data size.  Approximately 209 million files belonged to these new
nodes, while the number of files related to the nodes no longer backed up was much 
lower.  This resulted in a net gain of files. 

3)  Will anonymous node names and file space names persist over the life of this project?

Yes, The node name and filespace will be unique to that particular node over the life 
of this project.  A future survey of the nodes will identify those nodes that have 
already been assigned an anonymous name and that name (anonymous)  will be retained. 

4)  Why does the inactive files histogram have min bucket and max bucket values 
    of equal size?

This project re-used code that created histograms based on bucket ranges.  Since this 
histogram is meant to show inactive files (1,2,3,4) a range is not necessary.  This
will be fixed in a future version.  See the README contained in the tarball for 
more information.