← Back to branch summary

~ubuntu-branches/ubuntu/karmic/cedar-backup2/karmic

« back to all changes in this revision

Viewing changes to doc/manual/ch02s04.html

  • Committer: Bazaar Package Importer
  • Author(s): Kenneth J. Pronovici
  • Date: 2006-12-18 22:59:17 UTC
  • mfrom: (1.1.5 upstream)
  • Revision ID: james.westby@ubuntu.com-20061218225917-gwos76xdo3jewj6i
Tags: 2.9.0-1
http://bugs.debian.org/403546
http://bugs.debian.org/403448
http://bugs.debian.org/403662
* New upstream release.
  - Provide way to configure dev=/dev/cdrw and the like (closes: #403546).
  - Fix, clean up and reorganize parts of user manual (closes: #403448, #403662).

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/manual/ch02s04.html
1
 
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>The Backup Process</title><link rel="stylesheet" href="styles.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.70.1"><link rel="start" href="index.html" title="Cedar Backup Software Manual"><link rel="up" href="ch02.html" title="Chapter�2.�Basic Concepts"><link rel="prev" href="ch02s03.html" title="Cedar Backup Pools"><link rel="next" href="ch02s05.html" title="Coordination between Master and Clients"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">The Backup Process</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s03.html">Prev</a>�</td><th width="60%" align="center">Chapter�2.�Basic Concepts</th><td width="20%" align="right">�<a accesskey="n" href="ch02s05.html">Next</a></td></tr></table><hr></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cedar-basic-process"></a>The Backup Process</h2></div></div></div><p>
 
1
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>The Backup Process</title><link rel="stylesheet" href="styles.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.71.0"><link rel="start" href="index.html" title="Cedar Backup Software Manual"><link rel="up" href="ch02.html" title="Chapter�2.�Basic Concepts"><link rel="prev" href="ch02s03.html" title="Cedar Backup Pools"><link rel="next" href="ch02s05.html" title="Coordination between Master and Clients"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">The Backup Process</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s03.html">Prev</a>�</td><th width="60%" align="center">Chapter�2.�Basic Concepts</th><td width="20%" align="right">�<a accesskey="n" href="ch02s05.html">Next</a></td></tr></table><hr></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cedar-basic-process"></a>The Backup Process</h2></div></div></div><p>
2
2
         The Cedar Backup backup process is structured in terms of a set of
3
3
         decoupled actions which execute independently (based on a schedule in
4
4
         <span><strong class="command">cron</strong></span>) rather than through some highly coordinated
74
74
            files and directories out of the backup.  For instance,
75
75
            administrators can configure an <em class="firstterm">ignore indicator
76
76
            file</em> 
77
 
            <sup>[<a name="id2552029" href="#ftn.id2552029">10</a>]</sup> 
 
77
            <sup>[<a name="id2543926" href="#ftn.id2543926">10</a>]</sup> 
78
78
            or specify absolute paths or filename patterns 
79
 
            <sup>[<a name="id2552041" href="#ftn.id2552041">11</a>]</sup>
 
79
            <sup>[<a name="id2543938" href="#ftn.id2543938">11</a>]</sup>
80
80
            to be excluded.
81
81
         </p><p>
82
82
            This action is optional on the master.  You only need to configure
192
192
            Extensions <span class="emphasis"><em>cannot</em></span> be executed as part of the
193
193
            all action.  If you need to execute an extended action, you must
194
194
            specify the other actions you want to run individually on the
195
 
            command line.  <sup>[<a name="id2552341" href="#ftn.id2552341">12</a>]</sup>
 
195
            command line.  <sup>[<a name="id2544238" href="#ftn.id2544238">12</a>]</sup>
196
196
         </p><p>
197
197
            The all action does not have its own configuration.  Instead, it
198
198
            relies on the individual configuration sections for all of the
226
226
            The rebuild action does not have its own configuration.  It relies
227
227
            on configuration for other other actions, especially the store
228
228
            action.
229
 
         </p></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2552029" href="#id2552029">10</a>] </sup>Analagous to <code class="filename">.cvsignore</code> in CVS</p></div><div class="footnote"><p><sup>[<a name="ftn.id2552041" href="#id2552041">11</a>] </sup>In terms of Python regular expressions</p></div><div class="footnote"><p><sup>[<a name="ftn.id2552341" href="#id2552341">12</a>] </sup>Some users find this surprising,
 
229
         </p></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2543926" href="#id2543926">10</a>] </sup>Analagous to <code class="filename">.cvsignore</code> in CVS</p></div><div class="footnote"><p><sup>[<a name="ftn.id2543938" href="#id2543938">11</a>] </sup>In terms of Python regular expressions</p></div><div class="footnote"><p><sup>[<a name="ftn.id2544238" href="#id2544238">12</a>] </sup>Some users find this surprising,
230
230
            because extensions are configured with sequence numbers.  I did it
231
231
            this way because I felt that running extensions as part of the all
232
232
            action would sometimes result in surprising behavior.  I am not