Foolz Archive – Technical Details

We’ve been contacted by a few potential individuals and groups who are interested in continuing the Foolz Archive. However, we’ve been asked multiple questions regarding our hardware, workload, and some technical details about running the Foolz Archive itself. I will address every single inquiry below.

Server Specifications

Database Server
Intel(R) Xeon(R) CPU E3-1270 v3 @ 3.50GH
4x 8 GB DDR3 1600 MHz
2x 240 GB SAMSUNG MZ7WD240HCFV-00003 (RAID-1)
The average load on this server is: 0.83, 0.92, and 0.94. The total disk space usage is at 70%.
Storage/Fetcher Server
Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
2x 8 GB DDR3 1333 MHz
4x 4 TB HGST HMS5C4040BLE640 (RAID-5)
The average load on this server is: 30.50, 34.52, and 37.15. The total disk space usage is at 36%. The load can be decreased by adding a hardware raid which would increase the monthly cost of the server.
Search Server
Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz
2x 8 GB DDR3 1066 MHz
2x 750 GB
The average load on this server is: 1.44, 1.98, and 2.09. The total disk space usage is at 14%.

These servers alone should last for a few years. However, the only server that would need an upgrade would be the database server with additional SSDs in the future. Otherwise, it is perfectly fine to run the archive with the current hardware listed above for a few years without any monitoring.

Note: We will not be transferring ownership of our back-end web server or front-end servers. This makes up approximately 40€ per month out of the 200€ needed to operate the service.

Network Details

Due to our “complex” network configuration, it is slightly difficult to give exact bandwidth usage statistics. However, we will try our best to give you a general idea of the bandwidth consumption both RX and TX.

The daily RX of the storage/fetcher server is approximately 70 GiB. Furthermore, the daily TX of the storage/server is approximately 300 to 400 GiB. It should equate to almost 10 TiB of TX and 2.5 RX traffic per month.

Content Moderation

This actually requires a fairly active group of motivated individuals. You would be required to take down highly illegal material from the servers in a timely manner. Depending on the content itself, you would often be required to take down said content immediately or within an hour before facing server suspension or service cancellation. The is actually the primary concern in handling the archive.

Constant Battle

It is a constant battle to keep the “front-end” servers online and maintain its upkeep. We’ve been through approximately 10 front-end servers throughout the years and have been burned from 4 to 5 hosting providers. This is the primary reason the archive will become inaccessible at any given moment.

Note: I would also like to point out that CloudFlare does not protect you from reports. CloudFlare will forward them to you and your hosting provider. This is to make sure they are not held liable for any materials you host. Furthermore, their terms of services allows them to do so.

Any Additional Questions? Offers?

Please contact us via IRC or email.