On 01/24 03:09 , Kenneth L. Owen wrote:
> But, I do have another question. Do I need to remove the old tar
> history for localhost? I don't trust any of the data anyway and it will
> free the storage.
You will likely free less space than you think. This is due to the fact that
BackupPC 'pools' (
On Tue, Jan 24, 2012 at 2:09 PM, Kenneth L. Owen wrote:
> Hi Les & Carl,
>
> I was pre-mature in thinking that the problem was solved. I am still
> getting the same result: No files transferred.
>
> I will rework the archiver system to switch from tar to rsync transfer.
> I believe that this wil
Hi Les & Carl,
I was pre-mature in thinking that the problem was solved. I am still
getting the same result: No files transferred.
I will rework the archiver system to switch from tar to rsync transfer.
I believe that this will work as the rsync method is working on all
other hosts.
But, I do
Thank you, Les!
That was my total problem. My backups are scheduled to begin at 01:00
and I just had time to get there, logon as backuppc and issue the
ssh-copy-id archiver. Immediately the tar backup began!
What I can't figure out now is why it was working some of the time
without the public k
On Mon, Jan 23, 2012 at 11:22 PM, Kenneth L. Owen
wrote:
>
>
> I am not wanting to generate a new private key on the archiver for
> backuppc user for just the reason you gave -- the clients are in sync
> with this key.
And you don't need a new key, you just need the public key that
matches your
On Mon, 2012-01-23 at 22:36 -0600, Les Mikesell wrote:
> On Mon, Jan 23, 2012 at 10:07 PM, Kenneth L. Owen
> wrote:
> > Hi Les,
> >
> > I'm not getting something about setting up to use rsync to backup /home
> > on localhost. The instructions that I filed for generating keys is:
> >
> > Setti
On Mon, Jan 23, 2012 at 10:07 PM, Kenneth L. Owen
wrote:
> Hi Les,
>
> I'm not getting something about setting up to use rsync to backup /home
> on localhost. The instructions that I filed for generating keys is:
>
> Setting up BackupPC software to run rsync using visudo:
>
> Create user backuppc
Hi Les,
I'm not getting something about setting up to use rsync to backup /home
on localhost. The instructions that I filed for generating keys is:
Setting up BackupPC software to run rsync using visudo:
Create user backuppc on the server and each client.
Then generate keys for your server bac
On Mon, Jan 23, 2012 at 8:13 PM, Kenneth L. Owen wrote:
> Hi Les,
>
> Now that's a thought! I didn't realize this.
>
> Hmmm, so does backuppc need a key for local host like the remote
> machines?
Yes, everything works exactly the same. It's slightly less efficient
than running tar locally, but t
Hi Les,
Now that's a thought! I didn't realize this.
Hmmm, so does backuppc need a key for local host like the remote
machines?
-- ken
On Mon, 2012-01-23 at 20:05 -0600, Les Mikesell wrote:
> On Mon, Jan 23, 2012 at 7:47 PM, Kenneth L. Owen
> wrote:
> >
> >
> > The home directory is not ver
On Mon, Jan 23, 2012 at 7:47 PM, Kenneth L. Owen wrote:
>
>
> The home directory is not very critical mostly because I don't trust it and
> copy all critical files to the data server which get backed up via rsync and
> seems to be working just fine.
>
> But I fear there may be some underlying pr
Hi Carl,
As I said in my opening problem description, I'm computer literate, but
not very Linux knowledgeable. Before I retired, my employer used
Windows and since I networked into the system, I had to comply with
their rules. Now I run Linux as my primary boot and resort to Windows
only when I
On Mon, Jan 23, 2012 at 1:44 PM, Carl Wilhelm Soderstrom
wrote:
> While you were running the BackupPC_tarCreate job, did you watch the
> processes on the system (using another login of course) using 'ps ax' or
> 'top' or the like? Was there actually a tar process started?
Also worth mentioning. "
Sorry about the slow (and probably unhelpful) reply to this.
On 01/16 05:31 , Kenneth L. Owen wrote:
> Reviewing my logs, a full backup of localhost usually takes about one
> and a half hours with the maximum being close to 2 hours and this is
> when this job is running concurrently with the rsync
On Mon, 2012-01-16 at 15:52 -0500, Kenneth L. Owen wrote:
> On Mon, 2012-01-16 at 13:25 -0500, Carl Wilhelm Soderstrom wrote:
> > On 01/16 11:38 , Kenneth L. Owen wrote:
> > > Before this problem started, it was backing up with no problem. Then I
> > > started getting errors:
> >
> > If you do a
On Mon, 2012-01-16 at 13:25 -0500, Carl Wilhelm Soderstrom wrote:
> On 01/16 11:38 , Kenneth L. Owen wrote:
> > Before this problem started, it was backing up with no problem. Then I
> > started getting errors:
>
> If you do a 'ls -al /home' using a command shell (command line) on the
> machine
On 01/16 11:38 , Kenneth L. Owen wrote:
> Before this problem started, it was backing up with no problem. Then I
> started getting errors:
If you do a 'ls -al /home' using a command shell (command line) on the
machine in question does it show files, or just the usual '.' and '..'
directory entrie
On Mon, 2012-01-16 at 09:49 -0500, Carl Wilhelm Soderstrom wrote:
> On 01/13 08:09 , Kenneth L. Owen wrote:
> > 2012-01-07 01:00:18 Got fatal error during xfer (No files dumped for share
> > /home)
>
> Are there any files in /home?
> BackupPC will exit if it does not find any files, because it as
On 01/13 08:09 , Kenneth L. Owen wrote:
> 2012-01-07 01:00:18 Got fatal error during xfer (No files dumped for share
> /home)
Are there any files in /home?
BackupPC will exit if it does not find any files, because it assumes some
disastrous error has occurred and it does not want to clobber good
Hi All,
I have been using BackupPC for a while now, starting with it running on
Fedora in 2007 before switching to Ubuntu LTS. I am using the sudoers
method of allow backuppc to access my systems. I'm using rsync
transfers from all remote machines and use tar to backup /home on
localhost of the
20 matches
Mail list logo
