Tech Specialist Turns Old Pixel Phone Into Redundant Backup Server
Using Termux and rsync, Oluwaniyi Raji built a subscription-free hardware backup to protect self-hosted data.
Tech specialist Oluwaniyi Raji has developed a method to eliminate single points of failure in self-hosted environments by repurposing an old Google Pixel phone as a secondary backup server. The setup provides a low-power, hardware-redundant alternative to paid cloud subscriptions for users hosting their own data.
To achieve this, Raji utilized Termux—installed via GitHub or F-Droid—to establish a terminal environment on the Android device, granting it a Debian-style package manager. The phone is configured to receive scheduled backups from a primary Raspberry Pi via a cron job that executes rsync over SSH, specifically targeting port 8022. This allows the phone to act as a dedicated storage node for critical data without requiring additional dedicated server hardware.
The Risk of Single-Device Hosting
Many enthusiasts move their personal data away from corporate cloud services to self-hosted setups, often relying on a single device like a Raspberry Pi. While this increases privacy and control, it creates a precarious situation where a single drive failure or a corrupted software update can result in total data loss. The traditional remedy is to pay for a secondary cloud backup, but this reintroduces the monthly subscription model that many self-hosters aim to avoid.
Hardware Advantages and Limitations
One of the primary benefits of using a smartphone as a server is the integrated battery, which functions as a built-in uninterruptible power supply (UPS). This ensures the backup server remains online during power outages that would otherwise shut down a Raspberry Pi.
However, the implementation requires navigating Android's aggressive power management. On Android 12 and newer, "phantom process" limits can automatically kill background tasks. Raji notes that this must be addressed using an ADB command for Android 12 and 13, or a specific toggle within Developer Options for those running Android 14+.
Implications for E-Waste and Data Sovereignty
This approach transforms potential e-waste into a functional utility, demonstrating that older mobile hardware can still provide significant value in a home lab. By creating a local, redundant loop, users can safeguard their data against hardware failure without relying on external providers. As Raji puts it: "Does resilience need a monthly bill for the failures I'm most likely to face? The answer is no."
What to Watch
While this setup provides a basic safeguard against local hardware failure, it remains a local backup solution. Users seeking protection against site-wide disasters, such as fire or theft, would still need to consider off-site replication. Future iterations of such setups may explore the use of external storage attached to the Android device to increase the total backup capacity.