<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Thanks for the suggestions guys.<br>
<br>
I like the sound of the offsite diff backups.<br>
And I'm looking for a backup product - have tried custom scripts and
they're too much work and hard to support.<br>
I guess I've avoided diff backups so far due to a fear of one piece
of the diff failing and making my whole backup useless. Do tools
like Bacula and duplicity prevent this?<br>
<br>
To answer Duane's question, for now I need to backup files and a
database from my file server.<br>
<br>
Thanks,<br>
Phil<br>
<br>
<br>
On 29/04/2012 5:13 p.m., Dagan wrote:
<blockquote cite="mid:1335676431.2350.12.camel@tighnacheo.pro.local"
type="cite">
<pre wrap="">On Sun, 2012-04-29 at 09:23 +1200, Phil Donaldson wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi, I just joined this list.
Can anyone suggest a good tool to use to set up rotating backups on my
suse 10.1 file server?
Backups will be written to my NAS disk and I'll swap the disk every
week so I have offsite backups.
I'm looking for both daily and fortnightly rotating backups.
Every day the backup will be written to a file named daily-mon,
daily-tue, daily-wed etc so I end up with 7 daily backups going back 1
week that over-write each other.
Every fortnight the backup file will be written to a file named
weekly-1, weekly-2, weekly-3 etc so I end up with 26 fortnightly
backups going back a year that over-write each other.
I'm also interested in paying someone to set it up so I'd appreciate
any info on where to find good linux support in Welly or someone who'd
interested in doing this for me.
</pre>
</blockquote>
<pre wrap="">
I would suggest a plan that covers the loss of your off-site disk, and
you need to plan to do a restore test at least once a month (pick a
random day to restore, test key files for corruption).
If you are not restore testing the back-ups, then you are not managing
back-ups properly.
If you have small amounts of data, a full back-up each night would
work.
For larger amounts of data, you can do differential back-ups each
night, a full back-up on weekends. That way you have less back-ups to
worry about (full & nightly differential) should anything go wrong.
I recommend back-up tools rather than shell scripts. The back-up tool
will have better features (eg checking files were modified)
I have used Bacula, but the Duplicity/lDeja-Dup tool mentioned by Jim
is good (comes default with Fedora now).
In terms of paid support, I believe Open Systems Specialists
<a class="moz-txt-link-freetext" href="http://oss.co.nz/">http://oss.co.nz/</a> have a Wellington office, and Catalyst IT might be
able to handle all the back-ups for you in their data centre.
Not sure the costs there, but they are both good companies.
Dagan
</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<div style="width:500;">
<div style="width:180; float:right;">
<a href="http://www.anyware.co.nz/vision.php?source=emailsig"><img
src="cid:part1.02000309.07090803@anyware.co.nz"
alt="Anyware Core Value #1, Service: relentless pursuit of
the perfect customer experience. Click here for more
info." border="0" height="184" width="200"></a>
</div>
<p style="font-family: verdana, geneva, sans-serif;
font-size:12px;"><b style="font-size:14px;">Phil Donaldson</b><br>
Managing Director<br>
<br>
Anyware Limited<br>
<i>insightful web solutions</i></p>
<p style="font-family: verdana, geneva, sans-serif;
font-size:12px;">Phone: 64 4 939 1708<br>
email: <a href="mailto:phil@anyware.co.nz">phil@anyware.co.nz</a><br>
Internet: <a href="http://www.anyware.co.nz">www.anyware.co.nz</a><br>
<br>
<a href="http://www.anyware.co.nz/?source=emailsig"><img
src="cid:part5.00040209.06070009@anyware.co.nz"
alt="Anyware Web Design" border="0" height="45"
width="237"></a><br>
</p>
<div style="font-family: verdana, geneva, sans-serif; font-size:
9px;">This communication, including any attachments, is
confidential. If you are not the intended recipient, please do
not read it - contact me immediately, destroy it, and do not
copy or use any part of this communication or disclose
anything about it. And definitely do not eat it.</div>
</div>
</div>
</body>
</html>