Member Avatar for preist

I need to buy a Server Platform, have Linux and a system that tracks and logs all the network traffic. Do you have any links to information about choosing Hardware, Software and all that. Thank you very much.

The second, less important, choosing hardware for a ASP.net server.
Thank you guys, God bless them who'll reply.

  • 2 Contributors
  • 2 Replies
  • 105 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by preist

Dani AI

Generated

Brief summary: is planning to buy hardware for a Linux/PHP host and wants network traffic tracking/logging, plus guidance for an ASP.NET box. correctly flagged hosted/dedicated options as an alternative. Below is a tight, practical checklist and a few up-to-date pointers for buying, deploying and monitoring hardware you will own.

Start with requirements and consolidation

  • Workload estimate (concurrent users, DB size, peak I/O) drives CPU, RAM and storage choices.
  • For small-to-medium setups consider one physical server with virtualization (separate VMs/containers for PHP, DB, and ASP.NET) before buying two full boxes. See for a common Linux hypervisor.

Hardware checklist (minimum considerations)

  • Server-class board/CPU, ECC RAM, hot-swap bays, and dual PSUs for uptime.
  • NVMe/SSD for web/app tiers; separate disks or a fast array for databases (consider ZFS or hardware RAID + backup).
  • 1GbE NICs for low traffic; 10GbE for heavier loads or SAN access.
  • Remote management (IPMI/iLO/DRAC) and an off-site backup plan.
  • Warranty/replace policies and colocation vs on-prem power/cooling logistics.

Network tracking, logging and monitoring

  • Capture traffic via a SPAN/TAP, then analyze with tools such as Zeek or Suricata for inspection and alerts (see ).
  • Use a central logging/analytics stack (Elasticsearch/Kibana or Grafana + Prometheus/Loki) and plan retention and disk sizing early (Elasticsearch).
  • Log rotation, secure storage, and legal/privacy requirements matter—plan retention and purging.

Reading and workflow

  • Core admin books: The Practice of System and Network Administration; Unix and Linux System Administration Handbook; Site Reliability Engineering; Building Scalable Web Sites.
  • Practical path: lab VM images -> staging (same topology) -> production; automate builds (Ansible/Chef/Puppet), test backups and failover, and maintain patching schedules.

Caveat: classic ASP.NET needs Windows Server/IIS; modern .NET (Core/5+) runs cross-platform on Linux, so hardware choices can be consolidated depending on framework version.

Recommended Answers

All 2 Replies

Member Avatar for preist

FDC Servers has a nice selection of dedicated servers with your choice of operating systems.

http://www.fdcservers.net/

What I actually need is to buy my own hardware and set up my own system. I am well informed, but I need additional things to know and I am seeking for some books that cover "the providing of Hosting Solutions".

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.