On Wed, May 30, 2012 at 8:00 PM, Brad Alexander wrote:
> I can't really do that, since I tend to segregate my filesystems
> anyway. I used to have my non-standard stuff in /media/archive (which
> was backed up), I just turned off /media/cdrom and an nfs mount there.
> When I rebuilt, I decided /da
I can't really do that, since I tend to segregate my filesystems
anyway. I used to have my non-standard stuff in /media/archive (which
was backed up), I just turned off /media/cdrom and an nfs mount there.
When I rebuilt, I decided /data was a better choice, but didn't think
to turn off /media.
--
On Wed, May 30, 2012 at 1:05 PM, Neal Becker wrote:
> Using rsync (via ssh), default is aes encryption, which is expensive.
>
> I wanted to try setting
>
> Host * Ciphers arcfour,blowfish-cbc
>
> I put that in user backuppc .ssh/config, but that didn't seem to work
> (according
> to the output of
Using rsync (via ssh), default is aes encryption, which is expensive.
I wanted to try setting
Host * Ciphers arcfour,blowfish-cbc
I put that in user backuppc .ssh/config, but that didn't seem to work
(according
to the output of ps, not showing the args to ssh).
I did find that putting it in
On Wed, 2012-05-30 at 10:15 -0400, Brad Alexander wrote:
> I think I just found it. Ironically enough, it was my workstation. I
> have an external drive that is normally plugged into my laptop for
> files I need to transport I had plugged (and left plugged) this drive
> into my desktop, which was b
On 31/05/12 00:59, Michael Stowe wrote:
> Not only are you exactly correct, but your fix is exactly what I left out
> when I posted it the first time (I apparently deleted that line and hadn't
> noticed.) The client side hasn't changed, but I'm updating the scripts
> with the fixes this week, and w
> First, thanks for doing this.
>
> I've had the original post bookmarked for quite some time (years, it
> seems)
> with plans to implement, and this simplifies the process quite a bit.
> Performance is much better than rsync-over-autofs-smb (for any number of
> reasons).
>
> 5) I got a passing er
BackupPC Server:
---
RHEL6.2
BackupPC-3.2.1-7.el6.x86_64 (EPEL)
rsync-3.0.6-5.el6_0.1.x86_64
/var/lib/BackupPC is an NFS mount point (i.e. the BackupPC server is
an NFS client)
mounted via /etc/fstab entry:
nfsserver.example.comoh :/mnt/backup/gs-444-e10285
/var/lib/Ba
I think I just found it. Ironically enough, it was my workstation. I
have an external drive that is normally plugged into my laptop for
files I need to transport I had plugged (and left plugged) this drive
into my desktop, which was being indexed and attempted to be backed
up. Apparently, this fill
Try RsyncRestoreArgs. GUI -> host -> Edit Config -> Xfer.
Regards,
Tyler
On 2012-05-30 13:51, Neal Becker wrote:
> Is there an easy way to set restore options (using rsync), I want to not
> restore
> files on the destination that have mod time newer than the backup.
>
>
>
Is there an easy way to set restore options (using rsync), I want to not
restore
files on the destination that have mod time newer than the backup.
--
Live Security Virtual Conference
Exclusive live event will cover all
On 2012-05-30 00:27, Brad Alexander wrote:
> I know it is bad form to respond to one's own post, but I was digging
> around in my Munin graphs, and noticed that the filesystem skyrocked
> from about 70% to 100% late on the 26th or early on the 27th. I have
> included both the 4-week pool graph from
On Tue, 2012-05-29 at 19:27 -0400, Brad Alexander wrote:
> I know it is bad form to respond to one's own post, but I was digging
> around in my Munin graphs, and noticed that the filesystem skyrocked
> from about 70% to 100% late on the 26th or early on the 27th. I have
> included both the 4-week p
13 matches
Mail list logo
