[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [rdiff-backup-users] Help - rdiff-backup removing permision on targe

From: Dominic Raferd
Subject: Re: [rdiff-backup-users] Help - rdiff-backup removing permision on target folder
Date: Sat, 24 May 2014 09:10:02 +0100
User-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0

Can you give us a bit more informationj? What is the full rdiff-backup line that apparently causes the problem? What linux os are you running on the server?

On 24/05/2014 05:57, bt101 wrote:
I'm been stumped by a problem for days.

I use nothing but linux and have been using rdiff-backup for years to backup 
all my machines to one central server.  I use the traditional method of the 
central server reaching out using ssh.

A friend wanted me to setup a backup of their windows machine to a linux server.
I tested this at home by making windows machine with cygwin on it.
It works just like my linux clients where the central backup server reaches out 
with ssh.
It works great.

I then setup a linux server and windows machine at the friends house.  As far 
as I can tell, the setup is (almost) identical to my test system at home.

I setup the linux server at the frien's house the same as my home system. I 
have a user called rbackup that performs the backup.  I pre-created the 
destination/target folder and made rbackup the owner.  When rdiff-backup runs 
for the first time, it does a complete backup successfully.  However, for some 
reason,when rdiff-backup is finished, it removes some permissions from the root 
of the destination folder.

The permissions change from:

The next time rdiff-backup runs, it fails with many permission errors.
For example, it says permission denied for 
The reason for this seems to be because (at some point in this second backup) 
rdiff-backup removed even more permissions from the root of the target folder.
They end up as:

Firstly, why is rdiff-backup making modifications to the root of the target 
Secondly, why does it do the most asenine thing that it can possibly do by 
removing all the permissions?

As a test, on the system with the problem, I tried to run a local backup.  That 
is, the central server makes an ssh connection to itself to run a backup.  This 
backup runs fine and does not modify the root of the target folder.

I gather I must have some difference between my test system (at home) which 
works, and this troublesome system, but I can't finger it out!

Any ideas?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]