> > Another option is to use bare-metal restore/migration software which
> allows for a restore to be done to a different target machine -- Make one
> master system/config, create a backup and then restore to hardware as
> required.
>
> Not sure either of those options will work with VIA ITX boxes? Half the
> machines I install use 'set top' like boxes, and I think the 'Atom'
> powered boxes require a completely different driver set as well? But I
> really need a setup I can hold on the shelf and WHEN a machine goes down
> I can simply swap it out. I don't see any way that can be done 'legally'
> when the licenses are in many cases locked to a site! I can't hold
> machines for every site.
>
> As a slight aside, since at least one of my customers keeps pushing ...
> Is there ANY reason one would use 'virtualization' on a machine that is
> ONLY running Firebird ( and/or Apache/PHP )? I've even followed advice
> given here and dropped any graphic desktop on the Linux servers but I
> need a better explanation on why - since the machines spend 99% of there
> time idle anywa - you do not want them sharing things with other
> servers? :(

If you use a virtualized application deployment, then you could create a single application VM which would run on all the clients, without any regard to the nature/composition of the host machine (VIA vs. Atom vs. xxx).

The only requirement would be that the host be able to support your selected VM software.

In many respects it could make deployment, maintenance and recovery much easier -- you wouldn't need to care about the host OS, and if the hardware failed, they would need to install the OS, the VM host SW and then copy your base VM into the system.


Sean