On Mon, 17 Nov 2008, [EMAIL PROTECTED] wrote:
My biggest worry regarding these outside-of-BackupPC hacks is that when I
need them, I'm going to find that they're not going to work because it was
running, say, simultaneous to an actual backup.
Don't get me wrong: I'll take the hacks. It's
On Tue, 18 Nov 2008, Adam Goryachev wrote:
Christian Völker wrote:
My way to backup the backup ;-) is LVM
The pool is on a LVM as a LV. To backup the pool while backuppc is
running I can take a snapshot of the pool's LV and I rsync this one. So
there are no filesystem issues and backuppc can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Völker wrote:
My way to backup the backup ;-) is LVM
The pool is on a LVM as a LV. To backup the pool while backuppc is
running I can take a snapshot of the pool's LV and I rsync this one. So
there are no filesystem issues and backuppc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yohoo!
My way to backup the backup ;-) is LVM
The pool is on a LVM as a LV. To backup the pool while backuppc is
running I can take a snapshot of the pool's LV and I rsync this one. So
there are no filesystem issues and backuppc can stay running
Nils Breunese (Lemonbit) wrote:
[EMAIL PROTECTED] wrote:
Don't get me wrong: I'll take the hacks. It's better than
nothing. I, like I think *most* of us, would kill (or even pay
for!) a method of replicating a pool in a guaranteed-correct way,
especially at the host or even backup
dan wrote:
Also, I did try to do some software raid mirroring over iscsi but did
not do much more that basic testing. The problem here is that the raid
mirroring is syncronous so the slow iscsi connection will effect backup
performance quite a bit. I couldnt find any info on making the linux
Christian Völker [EMAIL PROTECTED] wrote on 11/18/2008 03:34:45 AM:
I think that you can use rsync v3 (on both sides) to sync pools
without
issue.
I'm assuming that you are using linux here also. With *solaris you
have
the zfs option as well.
I did some research a while back to use a
Hello,
the commentary from Rob Steele bellow the article in
http://jeremy.zawodny.com/blog/archives/010037.html seems quite relevant to me.
I have tried rsync and cp in the past but had the already mentioned memory and
time issues so I'm planning to give his suggestion (BackupPC_tarPCCopy to
Hi everyone,
i'm a backuppc user and i use it on several different linux servers,
with backuppc backupping in some cases to internal hdd, raid or external hdds.
I'd like to mirror the backuppc pool - I searched through ml archives
and found that mirroring the backuppc pool (wherever it is) with
Ermanno Novali wrote:
Hi everyone,
I'd like to mirror the backuppc pool - I searched through ml archives
and found that mirroring the backuppc pool (wherever it is) with rsync
on an external hard drive isn't efficient and doesn't scale good -
i've tried myself and is cpu and time consuming
Ermanno Novali wrote:
[...]
I'd like to mirror the backuppc pool - I searched through ml archives
and found that mirroring the backuppc pool (wherever it is) with rsync
on an external hard drive isn't efficient and doesn't scale good -
i've tried myself and is cpu and time consuming and very
Also, if your pool is only 10G of data, and your filesystem is 2TB, then
rsync or cp will work better. The above discussion mostly applies to
large pools. Although the definition of large pools is somewhat
murky, and it differs depending on your backuppc hardware, I would guess
something
Yes use dd (or even better dd-rescue that is restartable and gives progress
indication) for big pools. For smaller pools you might use cp -a or rsync
-aH (restartable). You have to find out the practical upper limit for the
latter methods depending on your requirements.
Thanks for dd-rescue
I use rsync v3 on a pool of about 280GB and about a few million files. With
rsync v3, the writes start within a few seconds of starting the sync and it
traverses the entire pool in 10-20 minutes. I only transfer about 3-4GB of
files each night with rsync reducing that to about 1GB over a T1 at
dan [EMAIL PROTECTED] wrote on 11/17/2008 09:29:19 PM:
I use rsync v3 on a pool of about 280GB and about a few million
files. With rsync v3, the writes start within a few seconds of
starting the sync and it traverses the entire pool in 10-20 minutes.
I only transfer about 3-4GB of files
[EMAIL PROTECTED] wrote:
Don't get me wrong: I'll take the hacks. It's better than
nothing. I, like I think *most* of us, would kill (or even pay
for!) a method of replicating a pool in a guaranteed-correct way,
especially at the host or even backup level. But I still worry
about
16 matches
Mail list logo
