Hello,
I'm trying to backup my OS/2 Warp4 Clients with BackupPC v.3.0.0 . I
created a share that i can access/read/write from a Windows machine and
my linux server that runs BackupPC.
But everytime I want to run a full backup of that shre it says:
Running: /usr/bin/smbclient pc-60\\D -U ADM
I've installed BackupPC on Fedora Core 5 and have encountered a problem that I
can't solve. I have user backuppc, group backuppc running Apache (httpd) and
BackupPC (ps -Al shows both processes owned by backuppc). When logged in as
backuppc, if I run BackupPC_Admin from a terminal window, I ge
Dear users,
I'm quite new with Backuppc running on Debian, and I
am very impressed by the ease of use (configuration,
web interface, etc...)
One question concerning incremental backup with rsync:
in case a file is found to have been modified and
retrieved with backuppc, is the entire modified fil
On Tue, 27 Feb 2007 07:00:54 -0800 (PST), Reef Morse
<[EMAIL PROTECTED]> wrote:
> I've installed BackupPC on Fedora Core 5 and have encountered
> a problem that I can't solve. I have user backuppc, group
> backuppc running Apache (httpd) and BackupPC (ps -Al shows both
> processes owned by backup
nestor picasse wrote:
>
> I'm quite new with Backuppc running on Debian, and I
> am very impressed by the ease of use (configuration,
> web interface, etc...)
>
> One question concerning incremental backup with rsync:
> in case a file is found to have been modified and
> retrieved with backuppc, i
Hi Les,
That's what I thought, but this is really the ideal
(essential?) feature (almost) every backup software is
lacking!
As rsync sends only the modified bytes, there is a big
opportunity to store only these bytes and not the full
file!
This would be a huge advantage: imagine you use
whatever
nestor picasse wrote:
>
> That's what I thought, but this is really the ideal
> (essential?) feature (almost) every backup software is
> lacking!
>
> As rsync sends only the modified bytes, there is a big
> opportunity to store only these bytes and not the full
> file!
>
> This would be a huge a
Tareq,
That error means you logged in, but for some reason (usually permissions
problems), your logged in user cannot see those files.
Have you tried to log into that share manually on your Linux box, using
a similar command line? You can leave off a few flags and just log in
to poke around.
This is going to be unsupported, I know, but for my own amusement (and
possibly yours!) can someone help me understand the ramifications of
subverting some of the tar options during the backups?
Specifically, take this scenario:
#1 full backup of / (tar -cvf - --totals -C / ./)
so tar backs
