We have come up with a disk partitioning system for our MySQL system which
seems to me like a good idea, but I worry that there may be some kind of
hidden downside that I don't see. I would therefore like to query the
wisdom of the list to see if you can point out the error, if any, of my
ways.
We are going to sell a system with a PC whose sole purpose is to run MySQL
and a layer of associated middleware. I have designed the system so that
the middleware keeps *all* its memory in the MySQL database. In order to
avoid config files, I kave put a key/value table into the database. The
system is running on Win2K.
What we plan to do is to partition the disk into two sections: C: contains
all the executlable software - Windows, MySQL and our middleware. D: is
intended to contain *only* the MySQL data. It is therefore mounted as C:
\mysql\data. The idea is then that if we get any kind of corruption of the
Windows system, we can simply "Ghost" the original C: back onto it, which
will repair all the original software, but leave the database unchanged.
Is this a sensible idea, or is there some fundamental problem I have
missed?
Alec Cawley
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
