From an Xbox 360 Shell to a Proxmox Backup Server

Thank you to u/_MynameItsNotKleber for contributing a story that begins with an accessible question: could a college team host its project without buying an elaborate server? The answer in this account was to reuse hardware already available, then keep adapting the installation as its purpose changed.

The Self-Hosting Day contribution describes an old computer, an Xbox 360 enclosure repurposed for a server, and a later decision to give that machine a backup role. The unusual case provides the visual hook. The more useful story is how a learning project developed into an installation whose data needed a separate recovery destination.

A College Assignment Established the Starting Point

The contributor explains the project's original constraint directly:

The project began when a college team needed an affordable server. The builder reused idle components that had been destined for disposal, demonstrating how existing hardware could support the assignment.

This gives the project a purpose beyond collecting equipment. The first machine existed to serve a team assignment. Reuse was part of the premise, so the later choices make sense as extensions of an approach already established at the beginning.

The First Server Used Familiar PC Components

The source lists a modest first configuration and then describes two later roles:

These are stages of this contributor's installation. They should not be read as current minimum requirements for Proxmox, Immich or any other application. The account does not provide workload measurements that would establish such a recommendation.

The Proxmox documentation is the appropriate reference for deployment requirements and platform operation. Here, the hardware list explains what the person built and how the roles changed.

Why an Xbox 360 Became Part of the Build

The initial computer used a case obtained from a scrapyard. Space then became a concern, and a cheap Xbox 360 listing prompted a different enclosure idea.

The creator links an original photograph of that stage. The photograph shows the PC-based build and the console enclosure together, documenting this stage of the project.

The source does not provide a complete mechanical conversion guide. It does not establish a universal mounting arrangement, power design or thermal result for an Xbox enclosure. The finished-build photograph is useful evidence of the project, but it does not document every step of the conversion.

Applications Turned the Server into a Learning Environment

The original account describes a rapid expansion in the services the builder tried:

Within a month, the builder was experimenting with an Arr stack, Immich photo uploads, SMB file access and smaller applications. The homelab became a place to test services and learn by using them.

That passage explains why the application list matters. It is a record of exploration, not a claim that every reader needs the same collection of containers. The installation gave the contributor a place to test services and learn how they behaved on hardware under their control.

There is a useful parallel with u/2Hard4Him's Pi-hole-to-family-server story: a small initial task expands until the system holds things people care about. The details of the two installations remain distinct.

The Proxbox Later Became a Backup Server

The change in role is the strongest part of the story:

The builder later reassigned the Proxbox 360 to backup duty, reducing it to 8 GB of RAM and three 500 GB hard drives. The change created a separate destination for protecting the college project and its snapshots.

This is the contributor's account of the transition. It should not be expanded into a claim that the installation has demonstrated complete disaster recovery. The source does not identify the backup application, retention policy, physical separation or results of restore testing.

The distinction matters for a photo workload too. Immich's backup and restore documentation covers the application-specific recovery process. A story that mentions photo uploads does not, by itself, prove that every part of a photo service is independently recoverable.

A Reused Shelf Brought the Equipment Together

The enclosure was one stage of a larger physical project. The contributor also links a starting shelf photograph, a rack-building album and a current setup album.

The text describes asking their father for help and finding discarded PVC boards for the build. That detail gives the story a human scale: organizing the equipment became another shared making project rather than an automatic purchase of a commercial rack.

The earlier case, the unfinished shelf and the later arrangement record different moments in the project rather than a single fixed configuration.

FAQ

Is this an Xbox running Proxmox on its original console hardware?

The contribution describes repurposing an Xbox 360 enclosure for a server built from PC components. It should not be presented as installing Proxmox on an unmodified Xbox console.

Did the author replace the original server immediately?

The account describes several stages, including a later decision to use the Proxbox for backups and build another main server. Keeping that sequence visible is important to understanding the project.

Does the post include a complete enclosure conversion guide?

It provides a narrative, hardware lists and image links. It does not document every mechanical and electrical step needed to reproduce the conversion.

Does a separate backup machine prove the data can be restored?

The source does not report a completed restore test. The article therefore describes a backup role without claiming an independently validated recovery result.

Conclusion

The Proxbox story shows how one constrained college assignment opened a longer path into self-hosting. Old components first provided a project server. An unusual enclosure made the hardware personal. A second machine then gave the original build another responsibility.

The result deserves attention for the sequence of decisions and the learning behind them. As in u/jc-21's small homelab story, the most useful way to understand the installation is to ask what each machine does and why its owner chose to keep it.