~ubuntu-branches/ubuntu/saucy/cedar-backup2/saucy-proposed

</p></div><div class="sect2" title="Step 1: Decide when you will run your backup."><div class="titlepage"><div><div><h3 class="title"><a name="id341020"></a>Step 1: Decide when you will run your backup.</h3></div></div></div><p>

</p></div><div class="sect2" title="Step 1: Decide when you will run your backup."><div class="titlepage"><div><div><h3 class="title"><a name="idp6009856"></a>Step 1: Decide when you will run your backup.</h3></div></div></div><p>

There are four parts to a Cedar Backup run: collect, stage, store

and purge. The usual way of setting off these steps is through a

set of cron jobs. Although you won't create your cron jobs just

Backup on the first day of the week, your backups will likely be

<span class="quote">“<span class="quote">confused</span>”</span> until the next week begins, or until you

re-run the backup using the <code class="option">--full</code> flag.

</p></div></div><div class="sect2" title="Step 2: Make sure email works."><div class="titlepage"><div><div><h3 class="title"><a name="id341064"></a>Step 2: Make sure email works.</h3></div></div></div><p>

</p></div></div><div class="sect2" title="Step 2: Make sure email works."><div class="titlepage"><div><div><h3 class="title"><a name="idp6015088"></a>Step 2: Make sure email works.</h3></div></div></div><p>

Cedar Backup relies on email for problem notification. This

notification works through the magic of cron. Cron will email any

output from each job it executes to the user associated with the

that you may prefer to configure root's email to forward to some

other user, so you do not need to check the root user's mail in

order to see Cedar Backup errors.

</p></div><div class="sect2" title="Step 3: Configure your writer device."><div class="titlepage"><div><div><h3 class="title"><a name="id336106"></a>Step 3: Configure your writer device.</h3></div></div></div><p>

</p></div><div class="sect2" title="Step 3: Configure your writer device."><div class="titlepage"><div><div><h3 class="title"><a name="idp5420384"></a>Step 3: Configure your writer device.</h3></div></div></div><p>

Before using Cedar Backup, your writer device must be properly

configured. If you have configured your CD/DVD writer hardware to

work through the normal filesystem device path, then you just need

Due to the underlying utilities that Cedar Backup uses, the

SCSI id may only be used for CD writers,

<span class="emphasis"><em>not</em></span> DVD writers.

</p></div></div><div class="sect2" title="Step 4: Configure your backup user."><div class="titlepage"><div><div><h3 class="title"><a name="id341227"></a>Step 4: Configure your backup user.</h3></div></div></div><p>

</p></div></div><div class="sect2" title="Step 4: Configure your backup user."><div class="titlepage"><div><div><h3 class="title"><a name="idp6034656"></a>Step 4: Configure your backup user.</h3></div></div></div><p>

Choose a user to be used for backups. Some platforms may

come with a <span class="quote">“<span class="quote">ready made</span>”</span> backup user. For other

platforms, you may have to create a user yourself. You may

Standard Debian systems come with a user named

<code class="literal">backup</code>. You may choose to stay with this

user or create another one.

</p></div></div><div class="sect2" title="Step 5: Create your backup tree."><div class="titlepage"><div><div><h3 class="title"><a name="id341270"></a>Step 5: Create your backup tree.</h3></div></div></div><p>

</p></div></div><div class="sect2" title="Step 5: Create your backup tree."><div class="titlepage"><div><div><h3 class="title"><a name="idp6039824"></a>Step 5: Create your backup tree.</h3></div></div></div><p>

Cedar Backup requires a backup directory tree on disk. This

100

directory tree must be roughly three times as big as the amount of

101

data that will be backed up on a nightly basis, to allow for the

132

directory structure within some existing Debian directory such

133

as <code class="filename">/var/backups</code> or

134

<code class="filename">/var/tmp</code>.

135

</p></div></div><div class="sect2" title="Step 6: Create the Cedar Backup configuration file."><div class="titlepage"><div><div><h3 class="title"><a name="id341349"></a>Step 6: Create the Cedar Backup configuration file.</h3></div></div></div><p>

135

</p></div></div><div class="sect2" title="Step 6: Create the Cedar Backup configuration file."><div class="titlepage"><div><div><h3 class="title"><a name="idp6049344"></a>Step 6: Create the Cedar Backup configuration file.</h3></div></div></div><p>

136

Following the instructions in <a class="xref" href="ch05s02.html" title="Configuration File Format">the section called “Configuration File Format”</a> (above) create a configuration

137

file for your machine. Since you are working with a pool of one,

138

you must configure all four action-specific sections: collect,

153

configure any extensions that require passwords or other similar

154

information, you should make the file readable only to root or

155

to the file owner (if the owner is not root).

156

</p></div></div><div class="sect2" title="Step 7: Validate the Cedar Backup configuration file."><div class="titlepage"><div><div><h3 class="title"><a name="id341402"></a>Step 7: Validate the Cedar Backup configuration file.</h3></div></div></div><p>

156

</p></div></div><div class="sect2" title="Step 7: Validate the Cedar Backup configuration file."><div class="titlepage"><div><div><h3 class="title"><a name="idp6055696"></a>Step 7: Validate the Cedar Backup configuration file.</h3></div></div></div><p>

157

Use the command <span class="command"><strong>cback validate</strong></span> to validate your

158

configuration file. This command checks that the configuration file

159

can be found and parsed, and also checks for typical configuration

162

Note: the most common cause of configuration problems is in not

163

closing XML tags properly. Any XML tag that is

164

<span class="quote">“<span class="quote">opened</span>”</span> must be <span class="quote">“<span class="quote">closed</span>”</span> appropriately.

165

</p></div><div class="sect2" title="Step 8: Test your backup."><div class="titlepage"><div><div><h3 class="title"><a name="id341433"></a>Step 8: Test your backup.</h3></div></div></div><p>

165

</p></div><div class="sect2" title="Step 8: Test your backup."><div class="titlepage"><div><div><h3 class="title"><a name="idp6059376"></a>Step 8: Test your backup.</h3></div></div></div><p>

166

Place a valid CD/DVD disc in your drive, and then use the

167

command <span class="command"><strong>cback --full all</strong></span>. You should execute

168

this command as root. If the command completes with no output,

178

179

To be safe, always enable the consistency check option in the

180

store configuration section.</em></span>

181

</p></div><div class="sect2" title="Step 9: Modify the backup cron jobs."><div class="titlepage"><div><div><h3 class="title"><a name="id341489"></a>Step 9: Modify the backup cron jobs.</h3></div></div></div><p>

181

</p></div><div class="sect2" title="Step 9: Modify the backup cron jobs."><div class="titlepage"><div><div><h3 class="title"><a name="idp6066048"></a>Step 9: Modify the backup cron jobs.</h3></div></div></div><p>

182

Since Cedar Backup should be run as root, one way to configure the

183

cron job is to add a line like this to your

184

<code class="filename">/etc/crontab</code> file:

Older »