Re: Re: Feature Request[s]

Miek Gieben wrote:

> [On 26 May, @19:05, robs_maill wrote in "[hdup-user] Re: Feature Reques ..."]
>>
>>1.   add a -i (for ignore tar errors) function. 
>>     This is needed sometimes during a restore. 
>>The other day I was attempting a network restore. 
>>Tar complained about not being able to mkdir a directory. 
>>The restore stopped after the monthly and never continued with weekly/daily's. 
>>There was nothing I could do with the tar file itself, It was OK. 
>>I had to create a tar.sh and point the config file to that. 
>>In the tar.sh I exited with 0 regardless. 
> 
> 
> ah, someone with more experience with restoring than me :-) 
> This looks like a worthwhile feature to have.

Had to do a few restores lately ;)
although the -s option did not work and restored the whole archive.



>>2.   If a second -V is appended to the command line.
>>     Display all the commands that are executed.
>>     It helps if I'm trying to debug some sort of network problem. 
> 
> 
> Also worthwhile (and easy... :-) )

I may use this to help write an FTP filter.
One situation about a restore...
You have to have a working environment that has an ssh server up and 
running already. Makes a rescue disk a bit more complex.


>>3.   add  
>>     group = 
>>     in the /etc/hdup/hdup.conf
>>     user = is helpful, but I prefer to apply permissions based on group. 
> 
> 
> easy.



>>4.   If possible allow storage of  
>>     backup acct = 
>>     backup host = 
>>     in the /etc/hdup/hdup.conf file
>>     They don't need to be used, just accepted as non errors.
>>     we have many machines and two massive backup servers.
>>     I would like to be able to control which uses what machine 
>>     from the conf file instead of modifying the 20 backup scripts. 
> 
> 
> so, this would me moving the @remote syntax into the config file...?


Allow both.
config file first.
command line second (if exists to allow override config file).
If neither then local hard disk.



>>     I can always have my perl utility pull the info from the hdup.conf file.
>>     however, hdup.conf barfs when it finds directives it does not know about.
> 
> 
> don't mind my asking, what is the difference between 20 different
> commandlines and 20 different configuration files? (if that is what
> you want)

the way hdup works now.
I can have one large hdup.conf file that I rsync to 20 machines.
Instead of multiple jobs that I have to modify cron files in 
/etc/cron.daily. It's cleaner if everything is in the conf file.



>>5.   This may be a long shot as it may require more work. 
>>     add an hdup "list" option.
>>     i.e.
>>     hdup list host date
>>     list on stdout the full path of all tar files that would be required
>>     to do a restore as of that date.
>>     I would like to use that list to create an "on demand" backup tape
>>     when required for offsite storage. 
>>     The list would give the all the tar files I need to dd to a tape.
> 
> 
> That would be also easy,

And helpful in the event I have to restore but do not have a machine 
running ssh yet. at the very least I can identify what files are needed
and either copy them to a USB hard drive or dd them to a tape.



> As of today, I'm officially "on holiday", but I won't leave until next
> week. I'll see what I can do until then,


Thanks, and enjoy your holiday.