[nflug] backups on an nfs server ..on and on

eric eric at bootz.us
Tue Aug 8 16:18:35 EDT 2006


wow, ok I'm probably just rambling on maybe I need to get out of this cave.

I had been backing up with "tar" on my samba server locally for about
three years, I decided on tar gz instead of dump because of what I read
from linus three years ago.   I created a script to automatically remove
the tar gz  file every morning after it had copied itself to a win2000
server that had a tape backup, I forgot that I turned off all the
scripts on the samba server after turning the win200 server into a linux
server, so a couple of very large tar gz files still existed in the
samba home directory.  I've since deleted them and have a whopping lot
"o" space enough for 5 days of backups ....for now.... until I figure
out a more fine tuned space saving savoy approach.  The linux server I
backup to now is using RAID 5 with hot swap and is only used for the
purpose of backing up, I feel comfortable with that.






eric wrote:

>doing a tiny bit of searching brought me to here:
>
>The parameter to -g is not the backup itself, but a snapshot file that
>stores information about the previous tar dump.  It needs to have been
>created by that previous backup.  For example, you could do something
>like the following to get a daily incremental backup:
>
>tar -cjf backup'+%Y%m%d'.tar.bz2 -g daily-snapshot-file /etc /usr/local/etc
>
>
>Is a "snapshot or incremental" simply a captured difference from the directory and tarball file.
>
>I read the man pages again but I don't speak their language that well yet.
>
>Thank you again,
>Eric
>
>
>
>eric wrote:
>
>  
>
>>Cool, my server works great and it's really easy to recover files
>>....then I discover that my home dir is 60 gb and my network server has
>>only 170 gb of space, definitly not enough room for a mon-fri bkup.
>>
>>Isn't their a way (through tar) to delta files like in SCCS? Is it
>>called increment?
>>
>>Thanks,
>>Eric
>>
>>
>>Robert Meyer wrote:
>>
>> 
>>
>>    
>>
>>>SSH security done with keys is dependant on keeping the private key secure.  I
>>>use ssh keys for some things.  The private key goes in your $HOME/.ssh
>>>directory.  Your home directory cannot be writable by anyone than yourself and
>>>the .ssh directory must be mode 700 (rwx------).  You wouldn't use
>>>public/private keys in an environment where you cannot guarantee the security
>>>of the private key, even with a password on it.
>>>
>>>The use for unpassworded keys is typically in an aggregate envronment where you
>>>would be trying to use SSH and SCP to handle a group of machines as a single
>>>entity.
>>>
>>>Again, not a good idea unless you're sure the private keys can be safeguarded.
>>>
>>>BTW, the private key is on the machine initiating the connection and the public
>>>key is in the "authorized_keys" file on the remote machine (the recipient).
>>>
>>>Hope this helps...
>>>
>>>Cheers!
>>>
>>>Bob
>>>
>>>--- eric <eric at bootz.us> wrote:
>>>
>>>
>>>
>>>   
>>>
>>>      
>>>
>>>>This doesn't sound good?  Is it because only I know what the key is and
>>>>that is sort of like a password to sshd?
>>>>
>>>>*** IMPORTANT **
>>>>do NOT enter a password/passphrase if you want uninterupted login's
>>>>*** IMPORTANT **
>>>>
>>>>
>>>>
>>>>Darin Perusich wrote:
>>>>
>>>>>from one of my cheat sheets...
>>>>  
>>>>
>>>>     
>>>>
>>>>        
>>>>
>>>>>--------------------------
>>>>>ssh login with NO password
>>>>>--------------------------
>>>>>
>>>>>to access/logon a system using ssh without being prompted for a password
>>>>>we need to generate ssh keys as that user, see SSH-KEYGEN(1) for
>>>>>detailed info.
>>>>>
>>>>>log into the systems you wish to access with entering a password.
>>>>>generate ssh keys. there are differect types of key's that can be
>>>>>generated, if the systems is using ssh protocol 1 or 2 there will be
>>>>>different keys. you can also employ different type a keys for the
>>>>>differenc protocol versions, des, rsa, etc. see the man page for a
>>>>>breakdown.
>>>>>
>>>>>     system1:> ssh-keygen -t rsa  (ssh protocol version 2)
>>>>>
>>>>>*** IMPORTANT **
>>>>>do NOT enter a password/passphrase if you want uninterupted login's
>>>>>*** IMPORTANT **
>>>>>
>>>>>this will create multiply files, id_rsa and id_rsa.pub for version 2,
>>>>>and identity and identity.pub for version 1. on the remote system in the
>>>>>users .ssh folder create an authorized_keys2 and copy the contents of
>>>>>id_rsa.pub into it for protocol version 2, authorized_keys gets the
>>>>>contents of identity.pub for protocol version 1.
>>>>>
>>>>>test by ssh'ing to the remote system.
>>>>>
>>>>>
>>>>>eric wrote:
>>>>>
>>>>>
>>>>>    
>>>>>
>>>>>       
>>>>>
>>>>>          
>>>>>
>>>>>>is it proper to automate a ssh login?
>>>>>>
>>>>>>
>>>>>> 
>>>>>>
>>>>>>      
>>>>>>
>>>>>>         
>>>>>>
>>>>>>            
>>>>>>
>>>>>    
>>>>>
>>>>>       
>>>>>
>>>>>          
>>>>>
>>>>_______________________________________________
>>>>nflug mailing list
>>>>nflug at nflug.org
>>>>http://www.nflug.org/mailman/listinfo/nflug
>>>>
>>>>  
>>>>
>>>>     
>>>>
>>>>        
>>>>
>>>__________________________________________________
>>>Do You Yahoo!?
>>>Tired of spam?  Yahoo! Mail has the best spam protection around 
>>>http://mail.yahoo.com 
>>>_______________________________________________
>>>nflug mailing list
>>>nflug at nflug.org
>>>http://www.nflug.org/mailman/listinfo/nflug
>>>
>>>
>>>   
>>>
>>>      
>>>
>>_______________________________________________
>>nflug mailing list
>>nflug at nflug.org
>>http://www.nflug.org/mailman/listinfo/nflug
>> 
>>
>>    
>>
>
>_______________________________________________
>nflug mailing list
>nflug at nflug.org
>http://www.nflug.org/mailman/listinfo/nflug
>  
>

_______________________________________________
nflug mailing list
nflug at nflug.org
http://www.nflug.org/mailman/listinfo/nflug



More information about the nflug mailing list