I can't quite follow all the issues and the merging that needs to be done,
and I can see that the Python 3 code is important. I just hope when the
smoke clears and you make a new release, that the poor Windows folks (me)
don't get left behind.
thanks for all the work you guys do.
Dean
__
st, 2019 9:48:42 AM
> Subject: [rdiff-backup-users] Windows
> I can't quite follow all the issues and the merging that needs to be done,
> and I can see that the Python 3 code is important. I just hope when the
> smoke clears and you make a new release, that the poor Windows folks (
).
KR, Eric
Dave
From: "Dean Rettig"
To: "Rdiff Backup"
Sent: Thursday, 8 August, 2019 9:48:42 AM
Subject: [rdiff-backup-users] Windows
I can't quite follow all the issues and the merging that needs to be done,
and I can see that the Python 3 code is important.
I could have sworn that I saw somewhere that there is an additional package
that can be installed to allow for the backup of Windows file permissions using
rdiff-backup. I've been googling like crazy and can't seem to find it again.
Is it possible to backup a windows source to a *nix destinati
Hi,
I am using rdiff backup from windows (by cygwin) to a unix server
without any problem for a while.
I decided to have also a local copy of my backups, and created another
batch file for local backups. But it is not working.
Any help would be appreciated.
Error I received is here:
C:\cygwin\
1. When a rdiff-backup is backing up files from a WinXP PC, the
user might invadvertently do a shutdown or there may be a power failure.
What happens to the backup structure for this rdiff-backup on the
backup-server.
Is it then corrupt and unusable ?
Does it autocorrect itself the next time rd
I'm using the latest rdiff-backup (1.3.2) in cygwin to backup one ntfs folder
onto another ntfs drive. The backup and incrementing works great. But when it's
done backing up the folder is no longer accessible to me (Windows won't let me
open it). If I then run rdiff-backup with the --delete-old
I was not able to install either of those two python apps under cygwin. The
first gives me a "don't know your system" error and the second fails during a
gcc compile.
@Andrew adding --no-acls did not work
I got the information about permissions through the Windows Explorer interface
(right cl
Ok, here it goes:
1. 1.2.7 behaves identically to 1.3.2
2. Running Vista x64 with latest cygwin.
3. icacls output on source:
PS C:\Users\Tommy> icacls C:\Users\Tommy\Documents
C:\Users\Tommy\Documents NT AUTHORITY\SYSTEM:(RX)
CHESED\Tommy:(RX)
The data you requested:
> to...@chesed ~
> $ ls -l /cygdrive/b/chesedrdiff/
> total 48
> drwxr-xr-x+ 3 Tommy None 0 Apr 10 2008 Users
> drwx--+ 4 Tommy None 49152 Mar 10 11:21 rdiff-backup-data
>
> to...@chesed ~
> $ ls -l /cygdrive/c/Users/Tommy/
> total 5529
> drwx--+ 5 Tommy
Thought I should also include the ls -l results for the parent directory of the
destination:
>
> to...@chesed ~
> $ ls -l /cygdrive/b/
> total 384
> drwx--+ 3 Administrators None0 Feb 19 16:11 $RECYCLE.BIN
> d---rwx---+ 2 Administrators SYSTEM 0 Mar 10 01:05 System Volume
>
Can I get some instructions or help on building rdiff-backup on
Windows? I have the source and a python install including pywin32. I
am pretty familiar with Python, but not so much with projects that also
need compiling.
Thanks.
--
--
Randy Syring
Intelic
- Original Message -
From: Oytun Yılmaz <[EMAIL PROTECTED]>
Date: Friday, August 17, 2007 7:00 pm
Subject: [rdiff-backup-users] Windows Backup Problem
To: rdiff-backup-users@nongnu.org
> Hi,
>
> I am using rdiff backup from windows (by cygwin) to a unix server
> without
On Mar 7, 2009, at 12:44 AM, tkeene wrote:
I'm using the latest rdiff-backup (1.3.2) in cygwin to backup one
ntfs folder onto another ntfs drive. The backup and incrementing
works great. But when it's done backing up the folder is no longer
accessible to me (Windows won't let me open it). I
Hi Tommy,
> But when it's done backing up the folder is no longer
> accessible to me (Windows won't let me open it). [...]
> I did some digging and it looks like rdiff-backup changes the
> permissions of the folder each time it increments, setting the
> folder to read-only and giving its owner no
On Mar 8, 2009, at 12:32 PM, tkeene wrote:
I was not able to install either of those two python apps under
cygwin. The first gives me a "don't know your system" error and the
second fails during a gcc compile.
Yes, those packages are Linux-only.
@Andrew adding --no-acls did not work
I go
On Mar 8, 2009, at 10:14 PM, tkeene wrote:
4. Finally: ls -l on source:
PS C:\Users\Tommy> ls -l C:\Users\Tommy\Documents
Tommy,
Can you run `ls -l /cygdrive/c/Users/Tommy/` in Cygwin? Since you are
running rdiff-backup under Cygwin, we need to see how Cygwin is
presenting the permissi
On Mar 10, 2009, at 11:34 AM, tkeene wrote:
d-+ 4 Tommy None0 Mar 10 01:37 chesedrdiff
Whoa! I guess that's the issue. The Unix permissions presented by
Cygwin are 000, but there's an ACL on there (the + ). You can read the
ACL using the getfacl command.
How is
Hi all,
I've just started experimenting with rdiff-backup and have it working fine in
the following way.
local backuprdiff-backup c:\source c:\dest
network backup using mapped network drive on windows 7 to our networked backup
server.rdiff-backup c:\source z:\dest
The network computer is microcor
I am attempting to utilize rdiff-backup v 1.1.7 on Cygwin as a solution
for backing up some developer laptops at the company I work for.
rdiff-backup will send the file data to a remote Linux server. I have
one problem though and that is that some files (in this case, some
supporting files from Ecl
I am trying to use rdiff-backup to backup my Windows Vista machine,
however, I keep getting stuck with Vista's infinitely recursed
directories.. rdiff-backup keeps digging down levels and it could be
left forever and never get anywhere.
For example, I am getting stuck within:
C:\Users\All Users\Ap
Heck did Microsoft not copy Time Machine as well?
Just letting everyone know I am looking.
+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+-
I'm running the following command in a batch script (with some other
variables set):
rdiff-backup.exe -v5 --no-hard-links --force --print-statistics
--remote-schema "plink.exe -P %RPORT% -i privatekey.ppk %%s
rdiff-backup --server" --exclude "**/AppData/Local/Application Data"
--exclude "**Recycle
I have successfully been using rdiff-backup for backing up a windows
directory to a samba share on a linux box for more than a year. Since a
month or so the backup does not work. It seems that for some reason one of
the temporary files (high_perms_file) on the samba share is created with the
permi
Remus,
I think there have been reports here of problems both with using
rdiff-backup via samba (smb) and, independently, to a Windows
destination. By contrast, backup from Windows to Linux via ssh is well
tested and reliable - except perhaps (others may know better) when
restoring Windows ACL
hi,
we use to backup all of our server to backup acls and xattrs too. ie. we
use the pylibacl and pyxattr on the server. although we backup windows
servers too. we mount them with cifs on the backup server and backup the
mounted dir. but after we install the pylibacl and pyxattr on the server
we no
Jim Hodapp wrote:
> I am attempting to utilize rdiff-backup v 1.1.7 on Cygwin as a solution
> for backing up some developer laptops at the company I work for.
> rdiff-backup will send the file data to a remote Linux server. I have
> one problem though and that is that some files (in this case, some
On Fri, 2 Feb 2007, Andrew Ferguson wrote:
> Jim Hodapp wrote:
> > I am attempting to utilize rdiff-backup v 1.1.7 on Cygwin as a solution
> > for backing up some developer laptops at the company I work for.
> > rdiff-backup will send the file data to a remote Linux server. I have
> > one problem
On Fri, 2 Feb 2007, Andrew Ferguson wrote:
I believe this is a Cygwin bug. A quick Google search reveals that
Cygwin seems to have PATH_MAX values around 256 or so. Most Linux
systems have a PATH_MAX around 4096. Technically, the POSIX PATH_MAX is
defined as 256, but XOpen recommends a minimum
What happens if you try "**System Volume Information" (i.e. without the
slash)?
JoshN
Austin Roberts wrote:
I'm running the following command in a batch script (with some other
variables set):
rdiff-backup.exe -v5 --no-hard-links --force --print-statistics --remote-schema "plink.exe -P %RPOR
or: **System Volume Information**
Dominic
Josh Nisly wrote:
What happens if you try "**System Volume Information" (i.e. without
the slash)?
JoshN
Austin Roberts wrote:
I'm running the following command in a batch script (with some other
variables set):
rdiff-backup.exe -v5 --no-hard-links
Hi Guys,
I'm trying to test the --test-server switch with the Windows version
(1.2.8).
On the server side, i defined (trough authorized keys) "--restrict backup/".
On the windows, if i try to backup something :
rdiff-backup.exe --remote-schema """C:\cbackup_test\plink.exe"" -2
-batch -P 22 -i
anybody has any tip about it?
Farkas Levente wrote:
> hi,
> we use to backup all of our server to backup acls and xattrs too. ie. we
> use the pylibacl and pyxattr on the server. although we backup windows
> servers too. we mount them with cifs on the backup server and backup the
> mounted dir. bu
If someone have the same problem, is not related to Windows itself, it's
a bug in 1.2.8 version. I didn't see the problem on debian/ubuntu
because debian/ubuntu patch rdiff-backup to fix this bug.
https://bugs.launchpad.net/ubuntu/+source/rdiff-backup/+bug/349072
I rebuild rdiff-backup for window
Hi all,
I'm hitting a few issues with long paths in windows. I understand
windows has issues with paths longer than 260 characters which is
annoying... but we can deal with that. My problem seems to be with the
rdiff-backup-data folder where files quite easily hit the 260 character
limit when
Hello all,
I'm hoping to use rdiff-backup to perform backups on Windows retaining
full ACLs, including for files which the administrator cannot access.
Unlike on a POSIX system in which the superuser can access any files
regardless of the permissions set, on Windows it is possible to
restrict any
I'm getting the error
ImportError: No module named rdiff_backup.Main
Running the current rdiff-backup version in cygwin under Windows 7.
I see in the FAQ the recommendation is to manually set PYTHONPATH. Here's
what I tried:
# ls /usr/local/lib/python2.5/site-packages
rdiff_backup rdiff_back
The only thing I found to work was SubInACL. Make sure that you have the
5.2.3790.1180 version because the earlier versions are broken and it must be
run on a 32 bit environment. This means on 64 bit windows, run it in the 32
bit Powershell. This will allow you to take ownership of the file
You can use long path tool for such issues.
--
View this message in context:
http://nongnu.13855.n7.nabble.com/Windows-rdiff-backup-data-path-too-long-tp175440p179583.html
Sent from the rdiff-backup-users mailing list archive at Nabble.com.___
rdiff-b
Long Path Tool (http://longpathtool.com/) looks like a Windows GUI
application. Does it really integrate with rdiff-backup?
On Tue, Feb 25, 2014 at 7:27 AM, aliceten wrote:
> You can use long path tool for such issues.
> --
> View this message in context: Re: Window
Hi,
I'm backing up from windows to linux over ssh using the new 1.2.0 on both
client and server. Dispite my efforts and fiddling with clocks, it stores a
diff for every file even when there are no changes. It isn't a big deal, but
I have some large files which take several minutes to generate dif
On Aug 2, 2008, at 6:55 AM, kartweel wrote:
I'm backing up from windows to linux over ssh using the new 1.2.0 on
both
client and server. Dispite my efforts and fiddling with clocks, it
stores a
diff for every file even when there are no changes. It isn't a big
deal, but
I have some large fil
Andrew Ferguson wrote:
Josh, does Windows even support hardlinks properly? The problem is
that rdiff-backup uses the inode numbers to keep track of hardlinks
and since the inode numbers are all zero on Windows, rdiff-backup
believes the file has changed. (iirc) The relevant function is
Hardlin
Andrew Ferguson wrote:
On Aug 2, 2008, at 6:55 AM, kartweel wrote:
I'm backing up from windows to linux over ssh using the new 1.2.0 on
both
client and server. Dispite my efforts and fiddling with clocks, it
stores a
diff for every file even when there are no changes. It isn't a big
deal, but
On Aug 18, 2008, at 10:39 PM, Josh Nisly wrote:
Andrew Ferguson wrote:
On Aug 2, 2008, at 6:55 AM, kartweel wrote:
I'm backing up from windows to linux over ssh using the new 1.2.0
on both
client and server. Dispite my efforts and fiddling with clocks, it
stores a
diff for every file even
45 matches
Mail list logo
