It's fairly simple and quite common to set up passwordless ssh between trusted hosts for a non-privileged user.<br><br>I'll post a link or two on easy ways to do it later.<br><br>--Dennis<br><br><br><br><div><span class="gmail_quote">
On 8/4/06, <b class="gmail_sendername">eric</b> <<a href="mailto:eric@bootz.us">eric@bootz.us</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
is it proper to automate a ssh login?<br><br><br>Mark Musone wrote:<br><br>>I'm a little cleared up, but now you are mentioning a samba server..so I'm<br>>all confused again :)<br>><br>>Heres what my opinion is:
<br>><br>>It would be much better to run the backups on the local fileserver.<br>><br>>If you are saying the fileserver does not have that much space, I would then<br>>still try to do the backup locally, and then transfer the complete backup
<br>>file wherever else afterwards.<br>><br>>You can even do both together by simply piping tar into ssh (which is an<br>>extremely common way to do backups):<br>><br>>"tar cf - / | ssh destserver dd of=/dest/server/filename/"
<br>><br>>The point being that when you are tarring a file, it does a LOT of<br>>filesystem lookups for each and every file that goes into the tarball.<br>>Secondly, it needs to handle file locking. Doing tons of fstats() and file
<br>>locks would end up being expensive and slightly unreliable, and slow.<br>><br>>You want to try and do all of the on your local system, which would<br>>eliminate or considerably speed it up. You can then transfer the single
<br>>tarball over the network..or even get crazy and just copy it via nfs or<br>>samba. You're only dealing with a single file now, so the above converns are<br>>moot.<br>><br>>-Mark<br>><br>><br>>
<br>>-----Original Message-----<br>>From: <a href="mailto:nflug-bounces@nflug.org">nflug-bounces@nflug.org</a> [mailto:<a href="mailto:nflug-bounces@nflug.org">nflug-bounces@nflug.org</a>] On Behalf Of<br>>eric<br>
>Sent: Thursday, August 03, 2006 3:13 PM<br>>To: <a href="mailto:nflug@nflug.org">nflug@nflug.org</a><br>>Subject: Re: [nflug] backups on an nfs server<br>><br>>Mark I was very unclear how explained, my apologies. Your answer was my
<br>>question would it be better to just run tar on the nfs server itself and<br>>then running -u after the intial tar package is created... I said<br>>increment because I was used to ntbackup which is similar or the same
<br>>thing as -u update in tar<br>><br>>my only concern for running the backup on the samba server was their is<br>>limited space and I want to have a monday - friday backup which would<br>>eat all the space, thus I put the backups on a larger server the nfs server.
<br>><br>>Thank you,<br>>Eric<br>><br>>Mark Musone wrote:<br>><br>><br>><br>>>Why can't you just run the tar on the server itself?<br>>>What do you mean by "incrementing" ?<br>
>><br>>>-Mark<br>>><br>>><br>>>-----Original Message-----<br>>>From: <a href="mailto:nflug-bounces@nflug.org">nflug-bounces@nflug.org</a> [mailto:<a href="mailto:nflug-bounces@nflug.org">
nflug-bounces@nflug.org</a>] On Behalf Of<br>>>eric<br>>>Sent: Thursday, August 03, 2006 1:30 PM<br>>>To: <a href="mailto:nflug@nflug.org">nflug@nflug.org</a><br>>>Subject: [nflug] backups on an nfs server
<br>>><br>>>which would be better with a mounted nfs share from a nfs server.<br>>><br>>>executing a tar and gzip command to package a home dir on the servers<br>>>share from the client or<br>
>>executing a tar and gzip command to package a home dir on the client and<br>>>then moving the package to the servers share?<br>>><br>>><br>>>I will want to increment files once a full backup is created, so I'm not
<br>>>sure which would be better in the long run.<br>>>What seems to be quicker is to execute the increment on the share across<br>>>the network instead of always moving/coping a large package from client
<br>>>to server.<br>>><br>>>Thank you for your input,<br>>>Eric<br>>><br>>><br>>><br>>><br>>>_______________________________________________<br>>>nflug mailing list
<br>>><a href="mailto:nflug@nflug.org">nflug@nflug.org</a><br>>><a href="http://www.nflug.org/mailman/listinfo/nflug">http://www.nflug.org/mailman/listinfo/nflug</a><br>>><br>>>_______________________________________________
<br>>>nflug mailing list<br>>><a href="mailto:nflug@nflug.org">nflug@nflug.org</a><br>>><a href="http://www.nflug.org/mailman/listinfo/nflug">http://www.nflug.org/mailman/listinfo/nflug</a><br>>><br>
>><br>>><br>>><br>><br>>_______________________________________________<br>>nflug mailing list<br>><a href="mailto:nflug@nflug.org">nflug@nflug.org</a><br>><a href="http://www.nflug.org/mailman/listinfo/nflug">
http://www.nflug.org/mailman/listinfo/nflug</a><br>><br>>_______________________________________________<br>>nflug mailing list<br>><a href="mailto:nflug@nflug.org">nflug@nflug.org</a><br>><a href="http://www.nflug.org/mailman/listinfo/nflug">
http://www.nflug.org/mailman/listinfo/nflug</a><br>><br>><br><br>_______________________________________________<br>nflug mailing list<br><a href="mailto:nflug@nflug.org">nflug@nflug.org</a><br><a href="http://www.nflug.org/mailman/listinfo/nflug">
http://www.nflug.org/mailman/listinfo/nflug</a><br></blockquote></div><br>