On Fri, 13 Jul 2001 at 8:39am, Joshua Baker-LePain wrote
Not a d*mn thing, because he hit 'CTRL-X Y' instead of 'CTRL-C Y'. Sorry
about that. What he decided not to write was...
> On Thu, 12 Jul 2001 at 10:35pm, Philip J. Hollenback wrote
>
> > So my thought was that I would have the gateway system that sits
> > between these two nets nfs-mount the filesystems from the system I
> > want to back up. amanda could then back up the nfs dirs. Any problem
> > with that?
You'll probably need to mount no_root_squash (or the equivalent), if I'm
not mistaken.
> > Problem: how does the amanda user on the backup server tell the root
> > user on the gateway to make the nfs mounts? If I can do that, it's a
> > simple matter to do some sort of wrapper script around the backup
> > process that takes care of the mounts.
> >
> > Any ideas on that? Only thing I've thought of so far is some sort of
> > tomfoolery with ssh, like allowing root logins w/o passwords. Seems
> > dangerous, though.
> >
What I would do would be to setup private key ssh access to the gateway
box for the amanda user on the backup server. On the gatewy box,
give the amanda user 'sudo' access to the mount command. Instead of just
'amdump', have the backup cronjob run a script which, among whatever else
you want it do, does the following:
ssh $gateway 'sudo mount -t nfs $laptop:/data /backup'
amdump $CONFIG
ssh $gateway 'sudo umount /backup'
That way you don't need to allow remote root access. And, since logins as
'amanda' are probably disabled, you don't need to worry about the sudo
access for 'amanda'. If the laptop isn't there, the mount will timeout
and the filesystem will just get reported as OFFLINE by amanda.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
