Backup Central

After this has been set up, the rest should be easy:
a. learn how to use rdiff-backup
b. adjust BACKUPUSER's authorized_keys file, tightening
up security, perhaps adjusting so that the relevant
line looks somewhat like this (one long line):

from="11.22.33.44",no-pty,no-port-forwarding,no-X11-forwarding,no-
agent-forwarding,command="rdiff-backup --server" ssh-rsa
AAAA....XXXX root < at > production-host


Hi there,

this is syntax for running a remote command, right? that is _not_ what I am
attempting to do. I want to initiate the rdiff-backup command on the server
that is getting backed up.

Do you have any clues how I can designate the destination ssh port?

cheers,

Noah






(Read ssh's manual pages for more on this.)

--
Greetings from Troels Arvin

_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users < at > nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Noah wrote:
this is syntax for running a remote command, right? that is _not_ what I am
attempting to do. I want to initiate the rdiff-backup command on the server
that is getting backed up.

Noah, this is NOT the syntax for running a remote command. At the risk
of repeating what I and others have said here, and also what I've said
in personal mail, you need to READ the ssh documentation.

Do you have any clues how I can designate the destination ssh port?

man 5 ssh_config

--
Keith Edmunds

+---------------------------------------------------------------------+
| Tiger Computing Ltd | Helping businesses make the most of Linux |
| "The Linux Company" | http://www.TheLinuxConsultancy.co.uk |
+---------------------------------------------------------------------+

On Thu, 18 Aug 2005 16:18:01 +0100, Keith Edmunds wrote
Noah wrote:
this is syntax for running a remote command, right? that is _not_ what I am
attempting to do. I want to initiate the rdiff-backup command on the server
that is getting backed up.

Noah, this is NOT the syntax for running a remote command. At the
risk of repeating what I and others have said here, and also what
I've said in personal mail, you need to READ the ssh documentation.

Do you have any clues how I can designate the destination ssh port?

man 5 ssh_config



Hi again,

okay I got everything configured correctly - well almost everything.

i am finding that ownership on the backup rdiff sevrer is wrong - called
backup-host below.

look at this.
"-r-xr-xr-x 1 backup backup 3833936 Apr 16 17:19 kernel"

in fact all the files and directories are owned by backup:backup

what can I do about this. here is my configuration command. this command is
intiated by root on the machine that is being backedup.

--- snip ---

rdiff-backup --print-statistics --exclude-globbing-filelist
/somedir/cron_scripts/rdiff-backup.exclude /
backup < at > backup-host::/home/backup/typhoon

--- snip ---

any clues here?

cheers,

Noah

this should


--
Keith Edmunds

+--------------------------------------------------------------------
-+ | Tiger Computing Ltd | Helping businesses make the most of
Linux | | "The Linux Company" |
http://www.TheLinuxConsultancy.co.uk | +------------------------
---------------------------------------------+

On Thu, 18 Aug 2005, Noah wrote:

okay I got everything configured correctly - well almost everything.

i am finding that ownership on the backup rdiff sevrer is wrong - called
backup-host below.

look at this.
"-r-xr-xr-x 1 backup backup 3833936 Apr 16 17:19 kernel"

in fact all the files and directories are owned by backup:backup

what can I do about this. here is my configuration command. this command is
intiated by root on the machine that is being backedup.

This is normal behaviour when you back up files to a normal user account
on the backup host. In the backup tree (on the backup server), you will
find a directory named 'rdiff-backup-data' containing (a.o.) one or more
files named mirror_metadata.[TIMESTAMP].snapshot.gz
The metadata file contains correct ownership and file mode information
needed to restore the files to the production server.

If you want the files etc. on the backup server to have the same uid/gid
as on the production server, you need to run rdiff-backup as root on both
sides. I have no experience with that, and in most cases it isn't even
necesary. Unless you have the same user accounts on both the production
server and the backup server, file ownership wouldn't make much sense
anyway.

HTH,
Maarten

"Noah" <admin2 < at > enabled.com>
wrote the following on Thu, 18 Aug 2005 12:22:19 -0800
in fact all the files and directories are owned by backup:backup

This is further evidence that the "Unable to change ownership" warning
should be removed---it apparently doesn't clear up confusion :)


--
Ben Escoto