Ludovic Drolez wrote:
> Le jeudi 28 février 2008 18:50, vous avez écrit :
>> I have an idea. It would be cool if the graphs also showed the total size
>> prior to pooling/compression as a line overlayed on the existing graphs.
>>
>> I think this data is exposed as $fullSizeTot and $incrSizeTot. I'
Re RAID5 vs RAID6 vs other things.
I did a study a little while ago on such things comparing Areca and
3ware hardware RAID cards for a storage brick, mainly to compare the
performance correlates of Linux filesystems, # of spindles, and
other parameters. To my surprise, I found very little di
Le jeudi 28 février 2008 18:50, vous avez écrit :
> I have an idea. It would be cool if the graphs also showed the total size
> prior to pooling/compression as a line overlayed on the existing graphs.
>
> I think this data is exposed as $fullSizeTot and $incrSizeTot. I'll see if
> I can figure it
Nils wrote:
| I like to keep things separated. BackupPC does backups,
| my monitoring software does the monitoring.
| Also keeps upgrades simple.
| But yeah, I can see others might like this.
I agree, but as a compromise - it would be a nice option
to ./configure --with-graphs :)
So, every
--On Tuesday, March 04, 2008 5:30 PM +0100 "Nils Breunese (Lemonbit)"
<[EMAIL PROTECTED]> wrote:
> Select the host from the drop-down menu and click either 'Start
> incremental backup' or 'Start full backup', depending on what you want.
Thanks! As so often happens, I tripped across it just after
Rahul writes:
> i have enabled the ssh for the user and then tried to take backup, but this
> time i got following error
>
> --Running: /usr/bin/ssh -q -x -n -l root 192.168.0.83 env LC_ALL=C
> --/bin/gtar -c -v -f - -C /data/BackupPC --totals .
If you pasted this correctly, then the "--/bin/g
Kenneth Porter wrote:
> --On Friday, February 29, 2008 3:03 PM -0600 Les Mikesell
> <[EMAIL PROTECTED]> wrote:
>
>> You can also give things a hint about timing by manually starting a
>> backup from the web interface at the right time of day and letting
>> the
>> approximately 24 hour interval t
--On Friday, February 29, 2008 3:03 PM -0600 Les Mikesell
<[EMAIL PROTECTED]> wrote:
> You can also give things a hint about timing by manually starting a
> backup from the web interface at the right time of day and letting the
> approximately 24 hour interval take it from there.
Where in the we
The "extra" stuff is apparently just to be more readable in RsyncArgs.
These options look fine. What version of rsync are you running? I don't
think it should matter as long as its a recent version
to me, this sounds like a filesystem issue. no matter what you do to make
the transfer more
Im sorry, I did mean raid1 mirror, not raid0 stripping.
On Tue, Mar 4, 2008 at 2:40 AM, Tomasz Chmielewski <[EMAIL PROTECTED]> wrote:
> dan schrieb:
>
> > with 3 drives in a raid5, you can lose 1/3 of the drives and still keep
> > data but you are 3x more likely to lose a drive. in raid 0, you a
Dan,
Thanks for response, this is what's in my config, even though it doesn't
match the log I gave you. where are these extra arguments coming from?
I changed the block size that is it.
$Conf{RsyncArgs} = [
#
# Do not edit these!
#
'--num
David Rees schrieb:
> On Mon, Mar 3, 2008 at 5:01 PM, Christopher Derr <[EMAIL PROTECTED]> wrote:
>> Is backuppc up to the task of backing up TBs of data? Or should I be
>> looking at software that explicitly states "for the enterprise" like
>> Symantec Backup Exec, Legato, or even open source
dan schrieb:
> with 3 drives in a raid5, you can lose 1/3 of the drives and still keep
> data but you are 3x more likely to lose a drive. in raid 0, you are 1/2
> as likely to lose a data drive because losing a disk is not losing a
> data drive, just a backup. in other words, with raid5 you c
Adam Goryachev schrieb:
>> Having battery backed RAM on the RAID controller can help, because the
>> controller can lie to the OS and say the data is written to disk
>> immediately instead of waiting for an read-calculate-write cycle,
>> since it's sure that if it does lose power, it can store the
Hello,
Don't you need a password with ssh and the root account ?
Cheers,
Hervé
Rahul Awasthi wrote:
i have enabled the ssh for the user and then tried to take backup, but
this time i got following error
--Running: /usr/bin/ssh -q -x -n -l root 192.168.0.83 env LC_ALL=C
--/bin/gtar -c -v
i have enabled the ssh for the user and then tried to take backup, but this
time i got following error
--Running: /usr/bin/ssh -q -x -n -l root 192.168.0.83 env LC_ALL=C --/bin/gtar
-c -v -f - -C /data/BackupPC --totals .
--full backup started for directory /data/BackupPC
--Xfer PIDs are now 29
Adam Goryachev schrieb:
(...)
> Recently some optimisations were discussed that made a significant
> difference:
> 1) Mount your filesystem with noatime or equivalent so every time
> backuppc looks at a file it doesn't need to write the new atime. The
> atime is not relevant to backuppc anyway. Y
17 matches
Mail list logo
