-backup repository?
- Grant
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
on the destination file system supporting them.
To be sure I understand, the requirements in the nongnu.org quote
above only apply to restores?
Will ACLs/EAs be written to the files themselves in the case of the
most recent copy in the repository?
- Grant
Will rdiff-backup save and version ACLs? I'm hoping to use rsync
--fake-super to preserve ownership and permission info in ACLs and
then create an rdiff-backup repository from the rsynced files.
- Grant
___
rdiff-backup-users mailing list at rdiff
as far as corruption.
Offsite backups would negate the corruption threat completely I think.
Does that sound right?
- Grant
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
will add encryption soon.
- Grant
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
to tape? Because if
the backup server has the bad bits you mentioned then the corruption
goes to the tape, right?
- Grant
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
, you just keep recording full copies and changing
tapes?
We can't just use fsck on the HD to check for corruption?
- Grant
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
owner and
group do not exist on the system it was backed up to?
- Grant
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au
way to execute the regressing destination now operation
on the server without involving the client?
- Grant
I'm trying to back up from a remote system to my laptop but I get:
Previous backup seems to have failed, regressing destination now.
And then after a few hours:
Write failed: Broken
time and
during this process there seems to be long periods of time with no
data being transferred between my laptop and the remote system and no
disk activity on my laptop's backup disk which seems strange. How can
I get this working again?
- Grant
Hi Grant
The last releases of rdiff-backup were Feb 2009 (1.2.8 and 1.3.3) so these
*should* have included the fix described in the thread you found. But maybe
it wasn't included or maybe it doesn't work - or maybe you have verbosity
set to 5 or higher (though this does not appear from
I'm using this line to back up my files:
rdiff-backup --exclude '/home/grant/.gvfs' --include '/etc' --include
'/home/grant/backup' --include '/var/lib/portage/world' --include
'/usr/src/linux/.config' --exclude '/*' / /media/usbdisk/repository
I get this even though the file's path is excluded
-backup
to do the restore. The repository can, after all, reside on file systems
not compatible with Unix ownership/permissions (with varying degrees of
success, alas).
Thank you Bob.
- Grant
___
rdiff-backup-users mailing list at rdiff-backup-users
of the metadata (ownership, permissions, ACLs, ...)
is stored separately from the mirror and should restore correctly. All
bets are off, though, if you add, delete, or change the contents of any
file there.
Can I have the correct ownership and permissions re-applied to the mirror?
- Grant
and
they'll still be perfectly preserved when I restore?
- Grant
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php
the
repository since the hard disk is attached to a different system now. Does
rdiff-backup preserve the ownership info in a different way or is it gone
for good?
- Grant
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
https
is to make it harder for the backup server to be compromised.
That sounds pretty good, but how do you access that system remotely?
- Grant
Any automated system can be fooled when not supervised properly ;-)
--
Maarten
___
rdiff-backup-users mailing
-suited to automated backups?
- Grant
I'm using rdiff-backup in an automated push arrangement with access
to the backup server provided via SSH keys and restricted to the
rdiff-backup command like command=rdiff-backup --server. I think an
infiltrator could delete a compromised machine's backups
this:
rdiff-backup --remove-older-than 1s backup@12.34.56.78::/path/to/backup
Is there any way to prevent something like that from happening?
- Grant
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo
drive that is directly attached to
it. Anyway, that problem would be solved if I used your
'PermitRootLogin without-password' advice above.
- Grant
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
https://lists.nongnu.org/mailman
and the remote system can't read them via rsync unless
I allow root logins.
I also had a hard time restricting the SSH key on the backup server to
the rsync command and read-only. Can that be done?
- Grant
___
rdiff-backup-users mailing list at rdiff-backup
session, but the copy
on the extra remote system will be uselessly out of sync and not usable to
restore using rdiff-backup.
Would you use rsync or would you have the remote system described
above act as a second rdiff-backup server and run the entire backup
process a second time?
- Grant
to
localhost:tunneledport)
You're saying openvpn with UDP would be best, then SSH -R, then
openvpn with TCP?
- Grant
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http
2008 /2nd/usr/bin/chfn*
# ln /2nd/usr/bin/chfn /2nd/usr/bin/rdiff-backup.tmp.46775
# chflags schg /2nd/usr/bin/chfn
Is there any workaround for this?
Michael Grant
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http
, in read
self._read(readsize)
File /usr/local/lib/python2.4/gzip.py, line 273, in _read
self._read_eof()
File /usr/local/lib/python2.4/gzip.py, line 309, in _read_eof
raise IOError, CRC check failed
IOError: CRC check failed
Deleting increment at time:
Michael Grant
On Tue, Jun 2, 2009 at 04:18, Marcel (Felix) Giannelia fe...@skeena.net wrote:
On 01/06/09 18:45, John covici wrote:
I think this is a problem in the fact that * never includes anything
beginning wth . character. To do this, you need to back up a superior
directory to the Mail directory and
for this is simply to umount /backup/home before doing
the backup to /backup.
Michael Grant
Michael Grant
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff
27 matches
Mail list logo
