First Release (MVP)¶

Defining the minimal viable product for Famlab's first release.

MVP Goal¶

Validate the core distributed backup network concept with a working 3-node system that proves families can achieve disaster-resilient backup without cloud dependencies.

For the full rationale and problem statement, see Principles.

What "Distributed Backup Network" Means¶

Each family gets:

Multiple Famlab nodes across different locations (parents' house, adult child's apartment, etc.)
Local SMB backup targets that appear as network drives for Time Machine, File History, etc.
Automatic replication of backup data across all family nodes
True 3-2-1 backup without cloud dependencies or ongoing costs

Architecture¶

Famlab implements the distributed backup network architecture from ADR-0002.

Key points for MVP:

Each node: 1/3 local backup storage, 2/3 for peer replica storage (3-node configuration)
Mesh replication using rsync over SSH
Admin-managed enrollment with manual SSH key distribution
Built entirely on standard Linux tools (btrfs, rsync, SSH, LUKS)

MVP Feature Scope¶

Core Features¶

Local SMB backup target with automatic network discovery (mDNS/Bonjour)
Peer-to-peer replication - automatic rsync of backup data across family nodes
Node enrollment - admin manages SSH keys and peer lists
3 nodes - at least one physical node, the others can be virtual
Capacity management - 1/3 local, 2/3 peer storage allocation
Basic monitoring - replication health and storage usage across network

MVP Scope Boundaries¶

The first release focuses solely on distributed backup functionality. All other homelab services, advanced features, and infrastructure improvements are deferred to future releases (see Future Improvements section).

Hardware Requirements (Per Node)¶

Host: Any system capable of running Linux (mini PC, old laptop, NAS)
Storage: 1TB minimum
Network: Reliable internet for peer replication, wired LAN preferred

Storage Sizing Guidelines¶

Local backup needs: 100-500GB per family member
Peer replica space: 2x local backup needs (2/3 of total storage)
Example: 3TB node supports 1TB local + stores replicas for 2TB of peer data
Network scaling: Each additional node increases everyone's available backup space

MVP Limitation: Full replication requires all nodes to have capacity for the largest node's backup. Mismatched node capacities may cause storage exhaustion. This trade-off is acceptable for MVP validation.

Network Requirements¶

Local network: Standard home router with DHCP
Bandwidth: Gigabit Ethernet preferred for initial backup performance
Discovery: mDNS support (standard on most home networks)

Deployment Platform¶

Debian + Unattended Upgrades

For MVP, we prioritize simplicity and debuggability. Debian provides:

Well-understood installation process
Extensive documentation for troubleshooting
Stable foundation with automatic security updates

User Experience Goals¶

Initial Setup (First Node)¶

Install Famlab on first node (admin location)
Configure local SMB backup target
Set up family member backup workflows
Network enrollment: Add additional family nodes via SSH key distribution

Adding Nodes (< 15 minutes)¶

Install Famlab on new node at family member's location
Admin enrolls node (SSH key exchange, peer list update)
Automatic replication begins across all family nodes

Daily Operation (Zero Touch)¶

Local backups run automatically via Time Machine, File History, etc.
Peer replication syncs changed data incrementally
System monitors replication health across family network
Alerts only when nodes offline > 24 hours or storage full

Recovery Scenarios¶

Individual file recovery: Browse local SMB share or request from any family node
Full system restore: OS backup tools restore from local or any peer node
Node failure: Data remains available from all other family nodes
Disaster recovery: Family network continues operating with remaining nodes

Success Metrics¶

Technical Metrics¶

Uptime: > 99.5% availability
Backup reliability: > 99% successful backup completion rate
Setup time: < 30 minutes from box to working backups

User Experience Metrics¶

Zero maintenance weeks: Goal of > 90% of weeks requiring no admin intervention
Support requests: < 1 per household per month after initial setup
Family adoption: All family members successfully using backups within 1 week

Next Steps¶

With this scope defined, the implementation path becomes:

3-node prototype - Build basic rsync replication between family nodes
Node enrollment - SSH key distribution and peer discovery process
Local backup target - SMB share configuration for Time Machine/File History
Basic monitoring - Replication health and storage usage tracking
Installation process - Streamlined setup for family members

This MVP validates the core distributed backup network architecture despite known storage efficiency limitations. The full replication approach proves the concept before migrating to more sophisticated solutions.

Future Improvements to Evaluate¶

Ideas and enhancements to consider after MVP validation

Infrastructure and Platform Evolution¶

Base Operating System

Immutable infrastructure: Atomic updates, immutable base system
Declarative configuration: Infrastructure described as code
Reproducible deployments: Same input always produces same result

Service Architecture

Multi-user isolation: Layered federation vs. traditional multi-user approaches
Container-based services: Per-user service instances for better isolation
Advanced capacity management: Handle mismatched node sizes more elegantly

Storage and Replication Enhancements¶

Storage Efficiency

Erasure coding: Replace full replication for better storage efficiency
Smart deduplication: Advanced deduplication beyond basic incremental sync
Sophisticated replication: Advanced network topologies beyond simple mesh

Alternative Storage Target

Allow target public-cloud object/file storage: Provide an alternative to multi-node replication when there's no peers to network with (bootstrapping problem)

Extended Functionality¶

Remote Access and Web Interfaces

VPN integration: Secure remote access to family data
Web file interfaces: Browser-based file access and management
External connectivity: Access when away from home network

Media and Content Management

Photo management: Automated organization and privacy-focused sharing
Video services: Advanced media organization and streaming
Document sharing: Enhanced collaboration tools for family documents

Communication Services

Email infrastructure: Family email server and management
Calendar services: Shared family scheduling and coordination

Security and Monitoring¶

Advanced Security

Enhanced encryption: Beyond full-disk + SSH transport security
Advanced access controls: More sophisticated permission systems

Operational Improvements

Enhanced monitoring: More sophisticated health tracking and alerting
Streamlined enrollment: Automated node discovery and key management
2-node optimization: Reduce minimum node requirements for smaller families

These improvements will be evaluated based on real-world MVP usage and family feedback.