Backup

Objectives

• Allow to recover personal data. Personal data consists of (order of importance):

  • Identity & Passwords -- Browser passwords, ssh keys, certificates, VPN credentials

  • Configuration
  • Installed apps (metadata, not actual apps)
  • Data managed by apps (Photos, Documents, Music...)

Use cases

• Set up where to store backups. Probably during initial setup.
• Recover a machine after a drive failure

Possibly

• Find a specific deleted document. Might be a realm of version control in app space.

Non use cases

• Migrate to a new machine (Design/Apps/Migration leveraging the same backend)

• Syncing all files/random junk from ~/
• Recovering unbootable system

Relevant Art

User oriented

DejaDup

Time Machine OS X 10.5:

• Welcome screen

• Select Disk Drive

• Excluded files

• Exclude more files

• Ready to Go

Time Machine OS X 10.7:

• single drive

• multiple drives

• notification adding a drive

RecImg Windows 8:

• RecImg

Business-oriented

Out of scope but may give some ideas:

• Backup Assit

• Nova Backup

• SpiderOak

Constraints

Many applications don't manage their own data privately. Photos for example stores photo metadata inside a global tracker database, linking specific photos to albums. We should probably approach our backup story with an opt-in mindset. Start with things we can backup/restore and work towards this goal on an app-by-app base. Lot of private data is scattered around the filesystem rather than contained in app

Discussion

Current Deja Dup UI: Apps/DejaDup/Screenshots

Guidelines

Tentative Design

• Design/Playground/Backups

Comments