[rancid] Re: DONE: Implementation of the (generic) linux configuration backup-versioning DEVELOPMENT VERSION
Lance Vermilion
rancid at gheek.net
Tue Jul 7 16:45:04 UTC 2009
This sounds like a very nice tool but unless I missed something I don't see
that it uses SVN/CVS to show the different revisions. That is scary
considering that it might overwrite a good file with a bad file should
someone change something.
On Tue, Jul 7, 2009 at 7:51 AM, Ryan West <rwest at zyedge.com> wrote:
> Backuppc does a really good job of this BTW. It uses RSYNC, performs basic
> file level de-duplication and will allow to restore to any version from
> their interface. It's free and pretty much designed for *NIX boxes already.
>
> This is listed as their main feature:
>
> A clever pooling scheme minimizes disk storage and disk I/O. Identical
> files across multiple backups of the same or different PCs are stored only
> once resulting in substantial savings in disk storage and disk I/O.
>
> http://backuppc.sourceforge.net/info.html
>
> -ryan
>
>
> -----Original Message-----
> From: rancid-discuss-bounces at shrubbery.net [mailto:
> rancid-discuss-bounces at shrubbery.net] On Behalf Of Thomas Donnelly
> Sent: Tuesday, July 07, 2009 10:45 AM
> To: Michael W. Lucas
> Cc: rancid-discuss at shrubbery.net
> Subject: [rancid] Re: DONE: Implementation of the (generic) linux
> configuration backup-versioning DEVELOPMENT VERSION
>
> Maybe a way to pass the locations of the configs for each box
> individually? The RANCID interface is nice and I wouldnt mind making a
> list of each file to be backed up for each box, as most of it would be
> copy paste. Also if you do everything from ports (like a good little
> UNIX user) all your configs should be in /etc and /usr/local/etc,
> backing up anything.conf in all those directories would cover 99% of the
> applications out there.
>
> -=Tom
>
> Michael W. Lucas wrote:
> > FreeBSD's base config would be fairly easy: /etc/rc.conf.
> >
> > The problem would be the configuration of all the secondary daemons:
> > ntpd, sendmail, etc.
> >
> > To do this properly, you're probably better off using a real system
> > configuration tool. RANCID is absolutely awesome at what it does, but
> > trying to extend it to accomodate one of my highly customized FreeBSD
> > boxes would be extremely difficult.
> >
> > On Tue, Jul 07, 2009 at 04:38:11PM +0200, Diego Ercolani wrote:
> >
> >> ....and of course.... it should work also with FreeBSD....
> >> Diego
> >>
> >> In data marted? 07 luglio 2009 16:29:12, Thomas Donnelly ha scritto:
> >>
> >>> Also with FreeBSD remote root logins are not permitted by default so I
> >>> would have to change that on every one of my servers.
> >>>
> >>> -=Tom
> >>>
> >>> Sam Munzani wrote:
> >>>
> >>>> Diego,
> >>>>
> >>>> Many companies don't allow root user for the SSH. So usually its login
> >>>> as normal user then either "su -" or "sudo su -". I think this script
> >>>> can be more useful if it considers non root logins.
> >>>>
> >>>> My 2 cents.
> >>>>
> >>>> Thanks,
> >>>> Sam
> >>>>
> >> _______________________________________________
> >> Rancid-discuss mailing list
> >> Rancid-discuss at shrubbery.net
> >> http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss
> >>
> >
> >
>
> _______________________________________________
> Rancid-discuss mailing list
> Rancid-discuss at shrubbery.net
> http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss
> _______________________________________________
> Rancid-discuss mailing list
> Rancid-discuss at shrubbery.net
> http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.shrubbery.net/pipermail/rancid-discuss/attachments/20090707/3b18c307/attachment.html
More information about the Rancid-discuss
mailing list