1 / 7

Transforming System Recovery: The Undo Paradigm for System Administrators

In the realm of system recovery, the 'Undo' paradigm offers a fresh approach that transforms how system administrators handle failures, mistakes, and data losses. This concept removes the burden of pre-planned recovery strategies, allowing for seamless and continuous recovery akin to undoing actions in a word processor. By integrating features like rewind, repair, and redo, system recovery becomes more intuitive and encourages experimentation without fear of permanent loss. The goal is to create a forgiving environment where users can learn and explore, supported by a framework for implementation.

chaman
Télécharger la présentation

Transforming System Recovery: The Undo Paradigm for System Administrators

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Bringing Undo to system admin:a new paradigm for recovery Aaron Brown UC Berkeley CS Division abrown@cs.berkeley.edu http://roc.cs.berkeley.edu

  2. Motivation • Recovery is important • people screw up • software and hardware break • upgrades fail • hackers break in • etc. • and sysadmins have to clean up the mess • can we make life easier?

  3. What makes recovery easy? • Not having to think about it beforehand • do you have a backup strategy to handle your typos? • Having a consistent strategy system-wide • no trying to disambiguate user/system data • Being familiar with it • recovery: it’s not just for catastrophes anymore • easy recovery => more freedom to experiment, learn • Not having to do it at all • export recovery to users • This is not what we have today!

  4. reason we call it undo: more like a WP, where you don’t sit around explicitly defining backups to recover from typos we’re all familiar with undo in editors and word processors. It’s a much more natural recovery paradigm compared to what we do today for system recovery. While working in your editor, I doubt many of you worry about a backup strategy for your edits or are afraid to try things (xxx). Undo: a new recovery paradigm • Make system recovery as painless and natural as undoing mistakes in a word processor • Continuous recovery with undo: the 3 R’s • Rewind: roll system state backwards to any time point • Repair: fix problem; reconfigure to avoid problem • Redo: roll system state forward, replaying user interactions lost during rewind users are familiar with the model

  5. Undo makes recovery easy • No explicit definition of recovery points • Covers system and user data • repair corruption, virus damage, trojans, ... • Redo means no loss of user data on rollback • Provides forgiving environment • encourages learning via experimentation • Can export to users

  6. Status • Now: defining the conceptual model • input welcome! would undo improve your life? where would you like to see it? • Next: studying implementation techniques • no-overwrite storage • logging of state and user actions • using dependencies between state to guide rollback • Goals: • proof-of-concept implementation (email service) • set of design guidelines for building undo-recoverable systems • if possible, an API and infrastructure for undoable systems

  7. Contact Aaron Brown, UC Berkeley abrown@cs.berkeley.edu This work is part of the ROC (Recovery-Oriented Computing) Project, run by Dave Patterson http://roc.cs.berkeley.edu

More Related