Date: Fri, 1 Aug 2003 09:01:48 +0400 From: Timofey Chernousov <tim@gwd.nnn.tstu.ru> To: "Dave [Hawk-Systems]" <dave@hawk-systems.com> Cc: freebsd-isp@freebsd.org Subject: Re: dump directly to remote HDD over ssh <-- take it up a notch Message-ID: <20030801090148.C78487@gwd.nnn.tstu.ru> In-Reply-To: <DBEIKNMKGOBGNDHAAKGNGEALCPAC.dave@hawk-systems.com>; from dave@hawk-systems.com on Thu, Jul 31, 2003 at 09:32:21AM -0400 References: <1457.192.168.23.97.1059613662.squirrel@webmail.schmut.com> <DBEIKNMKGOBGNDHAAKGNGEALCPAC.dave@hawk-systems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 31, 2003 at 09:32:21AM -0400, Dave [Hawk-Systems] wrote: > <continuing thread> > to ensure that we don't get too many servers trying to back up to the big > archive server at once, we want to run a script from the controller server... > > #!/bin/sh > ssh server1 "dump -3uf - /usr | ssh big_backup_server dd > of=/backups/server1.usr.dump" In this case you allow logon without password as _root_ to your server[12] AND allow logon without password as _user_who_can_read_dumps_ to your big_backup_server. It's too many security risks, isn't it? > ssh server1 "dump -3uf - / | ssh big_backup_server dd > of=/backups/server1.root.dump" > ssh server2 "dump -3uf - /usr | ssh big_backup_server dd > of=/backups/server2.usr.dump" > ssh server2 "dump -3uf - / | ssh big_backup_server dd > of=/backups/server2.root.dump" > > running it in this way should ensure that each dump completes before the next > one is started, keeping them stacked, but not overlaying each other and > effectively DOSing the box with all that data, correct? > > thanks for this and the verification on the previous > > Dave -- Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030801090148.C78487>