10/12/2012, 09:39 PM
From what I've read so far, the backup system generates a manifest with some statistics, fires off an event for different services to generate backup files, group and list those files in the manifest, then sends the manifest and files off to the backup servers. There are three servers used in this process: an authentication server, a metadata server, and blob storage server. There's an additional deviceImages server that I haven't figured out yet.
There are a lot of stats sent over with the manifests: battery percentage, signal strength, OS version, free disk space, and CPU/RAM load (I wonder what that's for). Backups are typically done incrementally, and each service comes with a description of what part of the system is backed up. Because it's modularized on services, maybe in the future people could select what parts they want to restore. And because of this modularization, new services could potentially be added. If that is indeed possible, maybe the WebOS Internals Backup/Restore app could be tied in and make it easier to restore flat file app settings (like used in games) without shuffling things on the USB drive.