Thank you, I solved the mistake, it was problem in the password of config.pl
thank´s
Jose Guilherme G. Dias
On Wed, 2006-03-01 at 14:52, Jose Guilherme Gomes Dias wrote:
> Can you connect to this share from the backuppc server with
> smbclient using the same username and password that you have
> in the config.pl file?
>
> I am using the same configuration that I use for
2006/3/1, Les Mikesell <[EMAIL PROTECTED]>:
On Wed, 2006-03-01 at 14:26, Jose Guilherme Gomes Dias wrote:>> Contents of file /var/lib/backuppc/pc/db2.ufpel.edu.br/LOG, modified
> 2006-03-01 06:00:16> 2006-03-01 01:49:31 full backup started for share SISACDIA$> 2006-03-01 01:49:40 Got fatal error d
On Wed, 2006-03-01 at 14:26, Jose Guilherme Gomes Dias wrote:
>
> Contents of file /var/lib/backuppc/pc/db2.ufpel.edu.br/LOG, modified
> 2006-03-01 06:00:16
> 2006-03-01 01:49:31 full backup started for share SISACDIA$
> 2006-03-01 01:49:40 Got fatal error during xfer (No files dumped for share
2006/3/1, Les Mikesell <[EMAIL PROTECTED]>:
On Wed, 2006-03-01 at 13:28, Jose Guilherme Gomes Dias wrote:> Last status is state "idle" (backup failed) as of 3/1 16:00.
> Last error is "No files dumped for share SISACDIA$".> Pings to db2.ufpel.edu.br have succeeded 54 consecutive timesWhat does the
On Wed, 2006-03-01 at 13:28, Jose Guilherme Gomes Dias wrote:
> Last status is state "idle" (backup failed) as of 3/1 16:00.
> Last error is "No files dumped for share SISACDIA$".
> Pings to db2.ufpel.edu.br have succeeded 54 consecutive times
What does the LOG file or Last bad XferLOG say (from
Last status is state "idle" (backup failed) as of 3/1 16:00.
Last error is "No files dumped for share SISACDIA$".
Pings to db2.ufpel.edu.br have succeeded 54 consecutive times Configurei e rodei o backuppc em uma micro com debian onde faz acesso a um micro com nt4, não efetuou o backup
On 03/01 05:18 , Khaled Hussain wrote:
> I really dont want to have to permit root login because if I do, then Ill
> have to do it for 10s of other servers - which doesn't make our network
> secure at all.
you set up a special user for backuppc to log in as (I use 'rsyncbakup',
myself); then set u
Here's a document I wrote up last year, describing how I set up the machines
to be backed up, such that I don't have to log in as root, and there are
several layers of restriction on what the backup server's login can do.
The setup has since been automated by a custom Debian package. Because of
th
Hello,
How can I get around this? I know I can change the user to be used in the
per-pc config file but I need to create a user that has root privelages. The
only solution seems to be to create another user with root's privelages: but
the problem seems to be that certain files that have only own
Hi all,
I am in a bit of a dilemma:
I have setup rsync+ssh to backup a freebsd server. However, the importance
of this server is such that I cannot permit root logon in the sshd_config
file. This in turn means that backuppc cannot login as root on the remote
server.
How can I get around this? I
Craig Barratt wrote:
> Tristan Krakau writes:
>
>
>> due to the rsync-cygwin-ssh problem when backing up Windows clients
>> using 'rsync' as transfer, I tried to use 'rsyncd' through a ssh tunnel
>> instead (since the Windows client can only be accessed via ssh).
>>
>> I found other threads deal
On Tue, Feb 28, 2006 at 10:27:42AM -0600, Bryan Penney wrote:
> On the status page the pool information is reported as
>
> Pool is 227.53GB comprising 1157013 files and 4369 directories (as of
> 2/28 08:33),
>
> When I run df -h /dev/sda3 (the raid backuppc is on) I get:
>
> Filesystem
13 matches
Mail list logo
