I've been going thru backuppc in some detail to see if it's applicable for a
wider rollout in my org and the config file is a source of problem - on the
upside it can be configured to infinity to provide just the kind of tuning
that is needed. On the downside, ditto.
It seems to me that I can strip out all the server settings that clients don't
need and just include a per-client config file that contains only those
settings that are applicable there. The backup appears to run fine when I do
this, but is this manipulation officially blessed/allowed?
Also, because of the config file, it's a significant hurdle for a naive admin
to set up. I DON'T want a GUI application - I want an appliance
application - that I can set and forget and Backuppc seems to be such a
beast, but the one place where it looks like it might benefit from a portable
GUI is one that helps set up the config file (a la fetchmail). Is there such
a side project in progress? If not, I'd consider looking into it.
hjm
On Wednesday 07 June 2006 07:15, Craig Barratt wrote:
> Just create a per-PC config.pl for each of those clients and
> set $Conf{FullKeepCnt}, $Conf{FullPeriod} as needed.
>
> Craig
>
>
> _______________________________________________
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/backuppc-users
> http://backuppc.sourceforge.net/
--
Harry Mangalam - NACS, E1127, Engineering Gateway, UC Irvine 92697
949 824 0084(o), 949 285 4487(c) [EMAIL PROTECTED]
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
