Building a Robust Backup Infrastructure

In the realm of data management, ensuring the security and accessibility of information is paramount. Recently, a significant step has been taken to enhance backup capabilities by establishing a secondary infrastructure at a different location. This initiative aims to safeguard data against potential issues that may arise within the primary setup.

Infrastructure Planning

The planning process for this new infrastructure includes several key components:

• A Fritzbox router to facilitate internet access.
• A switch configured with VLANs for network segmentation.
• Fujitsu servers designated for virtual machines (VMs) running Debian and Proxmox.
• A Synology system for data storage.
• An IPFire-based firewall to manage traffic between different networks.

Network Architecture

The proposed network architecture encompasses various segments, each serving a distinct purpose:

• Internet: Positioned before the Fritzbox.
• GreyNet: A type of DMZ located after the Fritzbox, represented by the firewall's red interface.
• Orange Interface: Another DMZ managed by the firewall.
• Blue Interface: Intended for WLAN but currently unused.
• Green Interface: Hosts internal VMs and the Synology system, with a direct tunnel to the home Fritzbox.
• DN42: Managed through a VM that establishes a VPN connection.
• AS34924: Also facilitated via a VPN on a VM.

Virtual Machines Setup

The infrastructure will include various virtual machines, each with specific roles:

• Univention as a site domain controller, replicating data with the home setup.
• A remote monitoring instance to oversee local systems.
• A load balancer to efficiently distribute web traffic across subordinate servers.
• Application servers dedicated to hosting websites.
• A VM for Shareaza, providing access to Linux ISOs and open-source software.
• Gateways connecting to AS34924 and DN42, as well as the local server network.
• Potential setups for a Tor server, BOINC, and Folding@Home.

Challenges Encountered

One notable challenge in the setup process has been the administration of the switch. Access via SSH is unavailable, and Telnet only allows for basic configuration changes, such as altering the IP address. More complex tasks like modifying VLANs and creating trunks can only be performed through a web interface, which is incompatible with modern browsers. To resolve this issue, there are plans to locate an older Windows NT VM that can effectively run the necessary browser for configuration.