From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NrvGr-0003tQ-Mf for garchives@archives.gentoo.org; Wed, 17 Mar 2010 15:34:58 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3B9CAE0B4A; Wed, 17 Mar 2010 15:33:39 +0000 (UTC) Received: from mail-pv0-f181.google.com (mail-pv0-f181.google.com [74.125.83.181]) by pigeon.gentoo.org (Postfix) with ESMTP id F0FC9E0B4A for ; Wed, 17 Mar 2010 15:33:38 +0000 (UTC) Received: by pvg16 with SMTP id 16so542617pvg.40 for ; Wed, 17 Mar 2010 08:33:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=JwHYJhr4mVJWFvae+Fi0D7yjV9aHuCU+5Y2/hodljQQ=; b=w3hOWthCkJ/YE/6JZkpCciEg82EBBOTdsZwPJ4QkpEF9LahIPmAhlSO9TmQjtpQRdz PYCpj5w7itAIq6QptFuAUxPFZFPWobCseiBHhPzP7Iz4+5/b/VTbtuS++y/cAQxred78 PTJGICovNQHITBZplAXNXmxnc0Ej3ooPXdEoo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=ntzEFJ0CdWNBLULKWS6UcAQ4qHA+PRlJj/Q6zJdA5e70V3YklMgzszBMgVOxQEGdVe xtPYtGMOkvwaYjoJbC+8khbt6q/OTciR0VlEXuGASwPkwgBZIxh1JvnbCh9PdNRUoSZd nrH9u+yuUCVX4oJVwOZjAv2ta/5H9mki/WhLo= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.141.13.3 with SMTP id q3mr969203rvi.245.1268840018408; Wed, 17 Mar 2010 08:33:38 -0700 (PDT) In-Reply-To: References: <49bf44f10911190844i5cb77185me60d5eb44ff2bfc7@mail.gmail.com> <20100224205159.71dd79be@digimed.co.uk> <201002251741.13525.alan.mckinnon@gmail.com> Date: Wed, 17 Mar 2010 16:33:38 +0100 Message-ID: Subject: Re: [gentoo-user] rsync backup system From: Ward Poelmans To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 6a7683e2-3019-40df-b7d0-69f5b5ab0253 X-Archives-Hash: 347840ed98aac499a6ccac51846d1a92 On Thu, Feb 25, 2010 at 17:11, Ward Poelmans wrote: > On Thu, Feb 25, 2010 at 16:41, Alan McKinnon wrote: >> A much better way is to run a dedicated agent on the client. If the server >> needs to schedule backups, it can ask the agent to do so using regular tcp >> traffic. The client can then do it's backup and rsync it over to the server >> when it's done, and that push can be done as a regular user on both ends. The >> actual backing up on the client must be done by root of course, no other user >> has the necessary access. If anyone is still interested, i had some time and this is what i did: On the client: rsync -a -X -b --backup-dir=../backup.0/ --link-dest=../backup.0/ /home/ward backupserver:Backup-Laptop/backup.cur/ ssh backupserver /home/ward/shiftbackups.sh This makes a directory backup.cur on the backupserver with a full backup in it, but it's exactly only a incremental backup as it hardlinks from backup.0 (the previous backup). The script shiftbackups.sh moves backup.0 to backup.1 and backup.cur to backup.0 and so on... This does more or less exactly what i wanted. Regards, Ward