I would not recommend using either SMB or NFS to access data
directories , especially if you expectingany kind of load. File locks
simply do do work effectively (or at all) across such mounts.

- michael dykman

On Tue, Apr 1, 2008 at 12:05 PM, Rob Wultsch <wultsch@gmail.com> wrote:
> Option 1:
> Assuming you do not need the databases to interact with each other I
> would setup two instances of mysql with separate datadirectories. This
> should make your back process easier. Read:
> http://dev.mysql.com/doc/refman/5.0/...ion-files.html
> http://dev.mysql.com/doc/refman/5.0/...tion-file.html
>
> Option 2:
> You could symlink (or NTFS junction for windows using a tool like
> winbolic link) the data directories for the individual databases to
> different locations.
>
> As for "One file per table" I don't think that is what you want/need.
> http://dev.mysql.com/doc/refman/5.0/...blespaces.html
> "Using multiple tablespaces can be beneficial to users who want to
> move specific tables to separate physical disks..." and you want to
> move the whole database.
>
>
>
>
>
>
>
> On 3/31/08, Reuven Nisser <rnisser@era-massis.com> wrote:
> > Hi All,
> >
> > I have two MySQL databases and I would like to place each one of them on
> > a separated disk, and backup each one of them separately.
> >
> >
> > I understand I need to use the "One file per table" option, right? It
> > will effect all the databases.
> >
> > How do I place each database on a different volume? Do I use file link?
> > How to do it on Windows platform?
> >
> > Thanks, Reuven
> >
> >
> >
>
>
> --
> Rob Wultsch
> (480)223-2566
> wultsch@gmail.com (email/google im)
> wultsch (aim)
> wultsch@hotmail.com (msn)
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=mdykman@gmail.com
>
>



--
- michael dykman
- mdykman@gmail.com

- All models are wrong. Some models are useful.