Hi Richard, The howto you quote is ok and shows the full procedure, however there are easier ways to accomplish this in day-to-day ops.
1. Create the key (on the system from where you plan to automatically logon to the BlueOnxy). Make sure you create a key with at least 2048 bits length, 1024 is not bad per se, but we're doing something that will probably stay in use for a few years, so my recommendation is to use 2048 bits: ssh-keygen -t rsa -b 2048 Make sure you do NOT enter a passphrase (press Enter twice and accept all default file locations) 2. As Taco mentioned: make sure you have root access enabled. Personally I'm pretty sure checking the box "SSH root Login" under "Server Management" | "Network Services" | "Shell" is enough to accomplish this. However Tacos way does probably exactly the same at the end. 3. Now on most half way modern unix-like OSes there is a script called ssh-copy-id. It does everything from now on for you with one command, so on the system where you created keys, do this (from the account you plan to automatically logon to the BlueOnyx, i.e. for backuppc su to backuppc first with "su - backuppc"): ssh-copy-id -i ~/.ssh/id_rsa.pub root@HostName-of-Blueonyx-Server The script will ask you for a password (which is the password of root at the BlueOnyx server). Once you have entered this password the script will copy your public key to the right place and everything should be fine. Eventually you have to make sure that /root/.ssh directory exists on the BlueOnyx server before you complete step 3. If the directory doesn't exist just try to ssh from the BlueOnyx server to itself, it will create the directory when you accept your own keys. Hth, Christoph Richard Morgan wrote: > Hi > > Many thanks indeed for sharing the scripts and knowledge about rsync. > I'm getting close to what I need, but seem stuck on one key element: > > How should I create the authentication key pair for SSH? I'lve > followed the instructions to the letter, but is there something else I > should be doing? > > http://wiki.centos.org/HowTos/Network/SecuringSSH#head-9c5717fe7f9bb26332c9d67571200f8c1e4324bc > > I've also kept quite detailed notes, so once I crack it I'll try and > post it back in case it's useful (and for my future reference). > > Thank you all very much. > > Richard > > ----- Original Message ----- > *From:* Christoph Schneeberger <mailto:[email protected]> > *To:* BlueOnyx General Mailing List <mailto:[email protected]> > *Sent:* Friday, January 21, 2011 9:44 AM > *Subject:* [BlueOnyx:06358] Re: Backup solutions via rsync and > single DB dumps > > Richard Morgan wrote: >> There's been some talk recently of transferring from one server >> to another using rsync. I've tried setting this up but as an >> rsync newby, I can't see quite where to get started. Does anyone >> have any scripts or little recipes that can be shared to get the >> ball rolling? >> >> The same applies to dumping MySQL databases one at a time, rather >> than by RAQBackup's method of dumping them all en-masse. >> >> Any help would be greatly appreciated. Many thanks indeed. >> >> Regards >> >> Richard > > You may want to check our mysql backup script: > http://www.telemedia.ch/publ/blueonyx-mysqlbackup.html > > For rsync backups, checkout backuppc: http://backuppc.sourceforge.net/ > > hth, > Christoph > > ------------------------------------------------------------------------ > _______________________________________________ > Blueonyx mailing list > [email protected] > http://www.blueonyx.it/mailman/listinfo/blueonyx > > ------------------------------------------------------------------------ > > _______________________________________________ > Blueonyx mailing list > [email protected] > http://www.blueonyx.it/mailman/listinfo/blueonyx > _______________________________________________ Blueonyx mailing list [email protected] http://www.blueonyx.it/mailman/listinfo/blueonyx
