On Mon, Apr 10, 2006 at 06:32:48PM +0200, jdd wrote:

of course I can't answer for Suse :-)

I am not asking SUSE, I am asking openSUSE who use SUSE Linux.

said this, if you have an universal solution, I will try it :-)))

There never will be a universal solution and we both know it. I am not looking for a universal solution. I am not even looking for a solution, because I already have one. I am just interested what other people use and if they found it on the SUSE Linux Distribution. The reason I ask is because I have a feeling that there is not good backup-script available om SUSE Linux. So again: what do you all use for backup? houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau

On Mon, Apr 10, 2006 at 08:26:50PM +0200, jdd wrote:

houghi wrote:

...

I am just interested what other people use and if they found it on the SUSE Linux Distribution. The reason I ask is because I have a feeling that there is not good backup-script available om SUSE Linux.

my answer was to say such a script don't exist, suse or not suse...

My opinion is that there are several scripts out there, backup2l being one of them, for the standard home PC. Yet none of them are on the SUSE Linux distribution. Not perfect scripts, but good scripts. If I compare it to the rest of tools available and look at the importance of backups (and recovery) I think it to be strange there are no better backup tools on SUSE Linux available.

I tried dozens of scripts, not one was good at recovery time...

I had the "luck" to test the recovery of backup2l and it worked great. Both for a single file as for a whole directory. You have a good point. Recovery is more important then backup.

the only way I keep using is writing cd/dvd (directly readable). I use others things also, but with little luck, so...

How do you do that? Do you use a script, or do you just copy stuff there?

and I keep a tree with a size consistent with the support size

Not sure what you mean here. houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau

Quoting houghi :

On Mon, Apr 10, 2006 at 06:32:48PM +0200, jdd wrote: [snip] So again: what do you all use for backup?

I currently use Bacula, but a version from the Bacula CVS repository, not the SuSE version. Backups are to disk, manually spooled to DVD. Previously, I used AMANDA with TR5/NS20 Travan tapes. Jeffrey

On Mon, Apr 10, 2006 at 07:30:52PM +0200, Chris Maaskant wrote:

Op ma, 10-04-2006 te 18:03 +0200, schreef houghi:

...

The reason is that I do not want a GUI tool for backups. So what are you using that is on SUSE itself? Or do you run your own script? Have I overlooked some great script that is available?

I use rsync. rsync -avptgoHq --delete-excluded '/home/chris' '/etc' '/boot' '/usr/local' '/opt' /backup

If I understand correctly, this is more a copy then a backup, or does it do recursive backups as well?

I also have the backup drive not mounted during boot, so that when the system crashes, the backup drive will not be corrupted.

I do that as well.

Chris Maaskant.

PS: This is my first post to the list Yay!! :-)

Welcome. :-) houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau

Chris Maaskant wrote:

...

or does it do recursive backups as well?

If that means copying directories + subdirectories, then yes.

may be he mean incremental backups. the problem is different if you works on one very big file, or many small files (or a mix) and do you want to keep most of the versions of a small file (programming with undo) or only the last one. backing up a multi gigabyte file may prove difficult without special hardware, and howmany copies do you need to keep? backing up many small files is easy, but restoring them is very hard (what is the good version, and where?) do you download many distribution images? do you want to keep them? and if, as I do, you have sometime one case and others moment the other, you understand than automatic backup is rarely good. to be more positive, * I keep images... on cd's * I burn small files to cd. I copy them to USB drive or to an other computer. time to time I make a "recollection". That is I copy all my text files on the same support (cd, dvd) to have all them at hand. I _never_ discard any cd... I have still 5 years ones. and I have a copy of the most important cd/dvd on a other location... and I have a fire resistant wallet... jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos

to be more positive as the question is important. should it not be a good idea to open a wiki page with a list of actual backup solution and they avantages/disadvantages? I see a handfull of them in yast... jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos

On Mon, Apr 10, 2006 at 09:20:43PM +0200, Chris Maaskant wrote:

Yes it copies all files in the given directory's to /backup

I don't understand the difference between copying files/directories and a backup?

Look below.

...

or does it do recursive backups as well?

If that means copying directories + subdirectories, then yes.

Sorry, brainfart on my side. I ment to say `incremential backups` http://en.wikipedia.org/wiki/Incremental_backup What it does basicaly is first it makes a complete backup. The next backup is only the differences since the last time. I do 4 backups per day. A complete backup of what I want to have is about 5GB. I can go back to 2005-12-06 for restores and yet it only takes 20GB. The last full backup was done 2006-02-08. So aproximatly every 2 months I have a full backup. In between I get partial backups. The longer I go back, the more time is in between them. Situation that happend to me. I change a script and screw it up completely. I close it, safe it and am happily unaware that I screwed up. Two days later I look at the then empty file. Somehow I had managed to safe an empty file. A copy would have copied the empty file and I could then only recover the empty file. With an incremential, I could first recover the empty file, see that it was empty, then go back to the day that I knew I still had a working file and retrieve that. Although I lost some, I had not lost all of the content. houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau

On Mon, Apr 10, 2006 at 11:14:07PM +0200, Chris Maaskant wrote:

Ah i understand. This what "rsync -avptgoHq --delete-excluded" does. It only transfers files that are changed or added since the last backup, the "--delete-excluded" option deletes files that are deleted since the last backup.

There still is a difference. With rsync you get a 1:1 copy. With a backup you get much more then 1:1 With a backup you get this: backup 01: all files backup 02: differences with backup 01, keep backup 01 backup 03: all files, keep 01-02 backup 04: differences with 03, keep 01-04 backup 05: all files, delete 01+02, keep 03+04 backup 06: differnce with 05, keep 03-05 backup 07: all files, delete 03+04, keep 05+06 That way you always have (in this example) at least 2 backups of each file. The reason you do not do a full backup each time is space and time. Naturaly you can do a 2a, 2b, 2c, 2d ... e.g. each sunday-night a full backup, monday through saturday incremential backups. Always keep the backups from last week. Something wrong? Data lost? You can go back two weeks. Like I said, I can go back 2 months. For me that is plenty. Wether or not this is a space and timesaver depends on your type of data you want to backup. If you backup mostly fixed data, like /etc, it will safe much room and time. If you backup mailboxes that change frequently, a complete backup might be better suited, as they are always different. The end result could be that you do two backups. One for mostly fixed data. One for mostly variable data. houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau

On Tue, Apr 11, 2006 at 10:03:12PM +0200, Chris Maaskant wrote:

Thanks for explaining that to me Houghi. But i'll stick with my rsync method, i see no need for me to having backups that can take me back more than a week. That might make sense when you do a lot of system configuration editing or do some developing or something, but i just play games surf the net do some graphic editing and listen/watch to music/movies.

I do not do a lot of system configuration editing. That makes it so easy to go back such a long time. I now can go back 2 months. This takes 20GB. And that with 4 backups per day. If I would go back 1 week with a backup each day (only one per day) it would take 35GB. So I save space by doing it like I do, because I do not change things that much. The first question I asked myself was how to backup as much with as little space as possible. As a result I got the backup that lasted 2 months. I believe the default settings would be almost one year. This still with 20GB for a 5GB in backups. The extra time is just that, an extra. Not trying to convince you, just explaining it. houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau

On Tue, Apr 11, 2006 at 10:05:43PM +0200, Bjoern Voigt wrote:

I use it successfully on some servers since some month. rdiff-backup is included in SuSE 10.0 and 10.1.

Also looks nice. Less complicated then storeBackup at first sight. houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau

On Tue, Apr 11, 2006 at 11:51:27PM +0200, Pascal Bleser wrote:

(just noticed there's a 1.0.4, building it right now... have the authors never heard of freshmeat.net ? ;))

Freshmeat.net? Nah, they are waiting for the Novell build server. ;-) Does that have a name already? Just wondering. houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau

On Wed, Apr 12, 2006 at 09:24:25AM +0200, jdd wrote:

houghi wrote:

...

On Tue, Apr 11, 2006 at 10:05:43PM +0200, Bjoern Voigt wrote:

...

I use it successfully on some servers since some month. rdiff-backup is included in SuSE 10.0 and 10.1.

Also looks nice. Less complicated then storeBackup at first sight.

houghi could you open a wiki page to summarise that thread? I have too many things on the fire to get this one also :-)

At this moment I do not see real content for a wiki-page. The only thing it would say is: Backup There are several backup tools: On the SUSE distribution 1 ... 2 ... Not on the SUSE distribution 3 ... 4 ... Other people use rsync for backup. I don't call that something worth of spending a page on. I think thinking about SLICK and SUPER is more important. (see other thread in Wiki and Factory) houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau

On Wed, Apr 12, 2006 at 02:06:35PM +0200, jdd wrote:

one should add the reason why he use one or the other.

I use rsync because I don't bother to keep all the obsolete versions I have big files adited often or small files edited...

If the large files are realy large files and they indeed change between every update, then I would use rsync for those. However I would see that e.g system settings and the majoruity of the files I do not change on a daily basis will be done by an other way as backup. I have done the backup way with rsync and had the situiation where the backup was useless, because it contained the same problem as the original file.

the reason why one app is used by one people and not by the others

A list why someone uses one program and another uses another is not something I think is worth a web page. There are several hundred backup programs and scripts around and each has its own users.

...

I don't call that something worth of spending a page on.

if it's worth several mails, it's probably worth a page :-)

They are two different mediums. During these mailings you can change ideas. See above. A list of programs that can be used for backup can be done by explaining how a searchengine works.

I think thinking

...

about SLICK and SUPER is more important. (see other thread in Wiki and Factory)

completely different beast, may be o no importance if 10.1 1cd install is proved...

1CD install will not have KDE or Gnome. There you need CD1-3. I know it is different. I think it is just more importand to spend my time on the 1-CD page then on a page with a list of backup programs and the reason why somebody uses it. That last page can only seriously be written by somebody who tries them all in different situaltions. houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau

Hallo Leute, Am Dienstag, 11. April 2006 22:50 schrieb houghi:

On Tue, Apr 11, 2006 at 10:05:43PM +0200, Bjoern Voigt wrote:

...

I use it successfully on some servers since some month. rdiff-backup is included in SuSE 10.0 and 10.1.

Also looks nice. Less complicated then storeBackup at first sight.

Without knowing rdiff-backup in detail, I can't believe that. storeBackup isn't complicated, it just has lots of options you _can_ (not: "have to") use for finetuning ;-) If you want to use the default options, simply run storeBackup -s /home/mydata -t /backup Regards, Christian Boltz --

I want to get off this list You can't leave the list... your soul is now attached to the SUSE server. If you leave, you must put the soul of someone who you love in your place. [> Robert and joao marka in suse-security]

On Monday 17 April 2006 00:57, houghi wrote:

I am sure it is a great tool, but it is not one I would use in my current situation. Also strange that I did not find a word about restoring data, or at least not realy. What I found was: You can use this information to write your own tools to restore or to analyze the backups.

For me restoring is more important then a backup. With so much information, at least 1 alinea about how restoring works should not be too much to ask.

Sorry, not my kind of tool.

houghi You are right on the money with these comments.

Storebackup is probably not what you want for your situation. For the list let me explain the backup needs that storebackup fullfills. The easiest way to do this is to explain what it does in a production environment where it's advantages are used. In a lawyers office here in Basel I've set a Samba based office server. As a production server it multiple layers of backups each serving different purposes. Storebackup is just one of the layers. It covers "User/Software errors". Here a for example: The problem: As is normal in the real world, the secretaries often open old documents, modify them, and save them as new documents. At least once a month someone forgets to "save as" to a new document name, and overwrites the old document with the new. In this case the old document needs to be retrieved from the backup. The Solution: With storebackup, I save "all" samba shares to a backup directory. This directory contains all documents that the users can access in multiple versions: - the last 7 Nightly versions - the last 4 "End of week" versions - the last 3 "End of month" versions Each version is stored in a separate directory named by date of backup. Under each "Date" directory, is a subdirectory for each share. Each share subdirectory contains the exact structure of the original share, so that the users can find the documents they are looking for. Since this "Backup" directory is also accessible via samba, the users can go directly to the backup directory and get the backups themselves. The files are individually zipped so that each document can be looked at without long "restore" processes. (This is the entire restore procedure, and also helps understand the lack of documentation thereof). All access rights of the original shares are respected within the backup directory structure, so that the Secretary cannot see the personal letters of the Boss, etc. etc. This solution is extremely elegant, and requires absolutely no maintenance after setup. But I agree this is not the solution that you are looking for, (for now at least ;-) Jerry

On Monday 17 April 2006 13:10, houghi wrote:

On Mon, Apr 17, 2006 at 12:30:42PM +0200, Jerry Westrick wrote:

<snip great explanation>

...

Since this "Backup" directory is also accessible via samba, the users can go directly to the backup directory and get the backups themselves. The files are individually zipped so that each document can be looked at without long "restore" processes. (This is the entire restore procedure, and also helps understand the lack of documentation thereof).

Even then 1 alinea describing the above would be welcome. I first looked at it and saw something like /usr/bin/storeBackupRecover.pl More parameters to fill in an what if that is part of the problem?

I have personally experienced (and I am sure many others with me) that restoring is much more importand then backing up. Backing up takes only space and time for yourself and for your system. Restoring will recover your data.

So when I started first looking for a backup tool, I started looking for restore information. When that was not available, I started looking for another tool. Restoring is what people are really interested in.

houghi

Ahhh, that is a problem. The /usr/bin/storeBackupRecover.pl is an attempt to recover the original files from a specific "Date" of the backup. It is there if you absolutetly need it, but it's a bonus not the real purpose of storebackup. maybe a line like: "Since storebackup is made to backup to disk, the access to the individual backuped files is via normal disk access." would be helpfull? Hmmm, now that we've solved a problem with the documentation of storebackup how do we "Release" the solution to the storebackup group? Jerry

...

So when I started first looking for a backup tool, I started looking for restore information. When that was not available, I started looking for another tool. Restoring is what people are really interested in.

there are two kind of backups in this respect: *system backups. restore when system is no more responding-must keep clear of this *data backup. Restore can be done at hand with available tools jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos

On Wed, Apr 12, 2006 at 10:13:25AM +1000, scsijon wrote:

would you be willing to share the total script (text not attachment please)

The best would be to place it on a website, unless it is a small script. Then it can be included. With small I mean 20 lines or so. houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau

On Wed, Apr 12, 2006 at 09:58:22AM +0300, HG wrote:

But I'm still amazed that there is no backup solution on SUSE. (No need to mention tar and rsync again... they are not in the same league...)

You must not have the thread. There are several of them. There are StoreBackup and rdiff-backup that can be interesting. There are some others as well. It just seems that backing up is such a personal choice that each system needs a different apraoch and then each person also wants to do it differently. A search on Freshmeat on 'backup' gives me 279 projects. Somewhere even SUSE has to make a choice on what to include and what not. Due to the huge amount of programs and the differences in need, it will be unpossible to inlude the correct tool for everybody. e.g. I am looking at storeBackup and are still reading on how this thing works. Can't figure it out, so it is not realy for me. Too many possibilaties and choices. rdiff-backup is the next one I am looking at. Still does a bit more then I need. houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau

On Wed, 2006-04-12 at 07:07 -0600, Boyd Lynn Gerber wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

...

What always amazes me is that nobody has even copied the Windows NT Backup onto linux. At work we use XBRU, which really sucks compared to what is delivered on each Windows XP Pro. And we haven't found a better one. On the other end of the spectrum, there are some "huge" solutions - they are based on backup server and then clients all around. And cost money.

But I'm still amazed that there is no backup solution on SUSE. (No need to mention tar and rsync again... they are not in the same league...)

I prefer backup edge. http://www.microlite.com

As do I. And the cost is not that great compared to the value of the data being backed up. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

Hello, Am Mittwoch, 12. April 2006 18:46 schrieb Chris Maaskant:

#!/bin/bash [...] shutdown -h now done

I see no "do" in your script, so this will give you a "syntax error near unexpected token `done'" after shutdown ;-)) SCNR, Christian Boltz, just searching for easter eggs in mails ;-) -- A: Weil es die Lesbarkeit des Textes verschlechtert. F: Warum ist TOFU so schlimm? A: TOFU F: Was ist eins der groesste Aergernisse im Usenet?

On Mon, Apr 10, 2006 at 09:33:42PM +0200, Christian Boltz wrote:

As you can see, my favorite tool is storeBackup. IMHO, it is the perfect tool if you want to backup to a harddisk:

Sounds interesting. Will re-look at it.

Of course, you should backup to a removable harddisk (and _really_ remove it when not doing backups) or to another machine using NFS mounts (again: umount if not needed). Doing backups to your local harddisk is pointless in several cases.

I do not have that possibilaty here, so I use a HD that I mount only when doing the backup or restore. houghi@penne : less /usr/share/doc/packages/storeBackup/README /usr/share/doc/packages/storeBackup/README: Permission denied [23:12:42] [/usr/share/doc/packages] houghi@penne : ldir|grep sto drwxr-xr-x 4 root root 176 2005-10-06 15:45 dosfstools drwxr-xr-x 3 root root 192 2006-02-24 10:28 pstoedit drwxr-xr-x 2 root root 152 2006-03-03 14:22 scsirastools drw-r--r-- 2 root root 320 2006-04-10 23:06 storeBackup drwxr-xr-x 3 root root 192 2005-10-06 15:53 yast2-storage Why is the directory not chmodded to 755? Then I can read the README like YaST tells me to. :-) Bug 165030 Submitted houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau

Hello, Am Dienstag, 11. April 2006 08:59 schrieb Leen de Braal:

[Christian Boltz]

...

I use storeBackup + several types of network-based tools:

PS: If someone is interested in the scripts, just ask.

Well, I am interested. I am trying out the best way of backing up remote machines, now at the moment using rsync. But it is rather simple atm, because i only end up with a full copy of the machines. If remote users ask for something already deleted, then in the "backup" it will also be deleted, if the question comes overnight. So I am eager to know more about this, your scripts are welcome as "educative" material.

OK, here we are ;-) My solution consists of several scripts in /home/backup/bin/: ### do_backup - main script including mail notification (this script is run via cron) --------------------------------------------------------------------- #!/bin/bash # use running ssh-agent eval `cat /root/.cron-ssh-agent` # do the backup ( time /home/backup/bin/do_rsync_backup2 2>&1 echo ; echo ; echo time /home/backup/bin/do_storebackup 2>&1 echo ; echo ; echo echo ">> df -h" df -h 2>&1 df -ih 2>&1 ) | mail -s "backup report" me@myhost --------------------------------------------------------------------- ### do_rsync_backup - the script running rsync (called by do_backup) --------------------------------------------------------------------- #!/bin/bash function do_rsync { dir="$1" option="$2" OPTS="--bwlimit=60" echo -e "\n\n> Backup of $dir/" SOURCE="root@myserver:$dir/" DEST="/home/backup/rsync-backup$dir" test -d "$DEST" || { echo "Creating directory $DEST..." mkdir -p "$DEST" } rsync $OPTS -az $option --delete-after -e ssh "$SOURCE" "$DEST" || echo "> *** ERROR *** (Exitcode $?)" echo "> rsync-Backup of $dir/ done." >&2 } do_rsync "/boot" "-v" do_rsync "/etc" "-v" do_rsync "/home" "" do_rsync "/root" "-v" do_rsync "/srv" "-v" do_rsync "/usr/local" "" do_rsync "/var/lib/mailman" "" do_rsync "/var/lib/rpm" "-v" do_rsync "/var/log" "" --------------------------------------------------------------------- Of course, you should have a SSH key (passphrase protection recommended) to allow passwordless login to the server you want to backup - and the public key on the server's ~/.ssh/authorized_keys file. In addition, you need a ssh-agent running: ### cb-keychain - RUN MANUALLY (once after booting), asks you to enter the passphrase for the SSH key --------------------------------------------------------------------- #!/bin/bash ssh-agent > /root/.cron-ssh-agent eval `cat /root/.cron-ssh-agent` ssh-add --------------------------------------------------------------------- A note about security: If someone can hack your backup server, he can access the ssh-agent also and connect to your server. You might want to use command=the_one_and_only in authorized_keys (see man sshd) - but this restricts you to _one_ (rsync) command (read: it won't work if you rsync several directories separately as I do). When your backup server is unplugged or rebooted, the ssh key will be locked again until you run cb-keychain. If you don't need root permissions for reading files on the server (like /etc/shadow), connect as user. ### do_storebackup - the script running storeBackup, quite simple (called by do_backup) --------------------------------------------------------------------- #!/bin/bash /usr/bin/storeBackup -f /home/backup/storebackup.conf --------------------------------------------------------------------- You can generate a storebackup.conf template using storeBackup -g Then customize the settings as needed. Hint: If you have lots of small files, storeBackup will need _lots_ of inodes. Keep this in mind when creating the filesystem of the partition used by StoreBackup... Regards, Christian Boltz PS: I don't claim this the perfect solution. If anyone finds a bug in the above scripts, please tell me ;-) -- Das ist mir jetzt ehrlich wirklich richtig peinlich... Ich hätte geschworen, damals vsftp installiert zu haben. Hab' ich gar nicht, sondern proFtp... Ähem... also gut, dann bin ich eben damit sehr zufrieden. [Ratti in suse-linux]

On Sun, Apr 16, 2006 at 11:45:29PM +0200, Christian Boltz wrote:

Of course, you should have a SSH key (passphrase protection recommended) to allow passwordless login to the server you want to backup - and the public key on the server's ~/.ssh/authorized_keys file.

How to do that can be seen on http://houghi.org/ssh A complete explanation is given there. houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau

Hello, Am Montag, 17. April 2006 01:00 schrieb houghi:

On Sun, Apr 16, 2006 at 11:45:29PM +0200, Christian Boltz wrote:

...

Of course, you should have a SSH key (passphrase protection recommended) to allow passwordless login to the server you want to backup - and the public key on the server's ~/.ssh/authorized_keys file.

How to do that can be seen on http://houghi.org/ssh A complete explanation is given there.

Nice page, but it can be enhanced ;-) * Copying the ssh pubkey to the remote server can be done in one step: [1] cat ~/.ssh/id_dsa.pub | ssh user@host \ "mkdir -p .ssh; cat >> .ssh/authorized_keys" * If you use the default filename for your key, you don't have to give the filename with every ssh call (or to use an alias): ssh-keygen -t dsa -b 2048 # without -f filename You can then login with simply ssh user@host # without -i filename * "no passphrase" isn't something I like... Regards, Christian Boltz [1] taken from german SUSE Linux FAQ: 10.3. Wie erstellt man einen SSH-Key? Wie kommt der Key auf den Zielrechner? http://suse-linux-faq.koehntopp.de/q/q-ssh-keygen.html -- Versuchst du mal bitte zu formulieren, was du eigentlich möchtest? Mit diesem Posting hast du gute Chancen auf den "Marcel Stein Award". [Christian Paul in suse-linux]

Hello, Am Montag, 17. April 2006 15:03 schrieb houghi:

On Mon, Apr 17, 2006 at 02:22:20PM +0200, Christian Boltz wrote: [...]

...

* If you use the default filename for your key, you don't have to give the filename with every ssh call (or to use an alias): ssh-keygen -t dsa -b 2048 # without -f filename You can then login with simply ssh user@host # without -i filename

It still asks for the password and the point is that it shouldn't. At least that happens with me.

Works without problems here ;-) # ssh server 'date' Mo Apr 17 15:23:02 IST 2006 # ls -l /home/cb/.ssh/ | grep id -rw------- 1 cb users 1264 2004-01-28 17:07 id_dsa -rw-r--r-- 1 cb users 1108 2004-01-28 17:07 id_dsa.pub Try renaming your key to those (default) filenames, add eval `ssh-agent` to your ~/.profile and call ssh-add once after login.

...

* "no passphrase" isn't something I like...

If I don't use that, I can't run a remote script automagially. It keeps asking for a passphrase. Now why would I eneter a passpfrase if I son't want to enter a password.

I might need a real example on how to run a remote script.

see "cb-keychain" in my mail about the rsync/storeBackup combination and eval `cat /root/.cron-ssh-agent` at the start of the backup script ;-) Regards, Christian Boltz -- [tgz Datei entpacken] tar xzf <Archiv> Für weitere Informationen lesen Sie bitte die Manpage oder Ihren Admin. [Torsten Hallmann in suse-linux]

Hi, Christian Boltz schrieb:

* Copying the ssh pubkey to the remote server can be done in one step: [1]

cat ~/.ssh/id_dsa.pub | ssh user@host \ "mkdir -p .ssh; cat >> .ssh/authorized_keys"

Why so complicated? ssh-copy-id -i ~/.ssh/id_dsa.pub user@host does the same. Regards, Carl-Daniel -- http://www.hailfinger.org/