asked on
old mysql machine - migration, best practices, and other questions
Hi,
Have a situation where a small company has an old desktop computer that's running Debian Linux, with a MySQL database that I believe a Microsoft Access front end is connecting to (I may be wrong on the Access part). I'm trying to implement a 'best practices' solution for them. This is not a case of moving to the cloud, or investing tens of thousands of $ - it's a small company, but they need some best practices implemented.
I have 0 experience with MySQL - all my experience is on the MS sql server side.
Was thinking - could they set up a (physical or virtual) windows 2008 or 2012 machine and run mysql on it? That way it could be included as part of their backup plans.
Is it possible to go from a Linux MySQL database to a windows MySQL database? What's the easiest method to create a daily backup of a MySQL database? Is there a script I can run to export it to a file share somewhere (perhaps with the date in the filename)?
Just looking for overall best practices to go from a 10 year old debian server running the MySQL database, to '?'
Have a situation where a small company has an old desktop computer that's running Debian Linux, with a MySQL database that I believe a Microsoft Access front end is connecting to (I may be wrong on the Access part). I'm trying to implement a 'best practices' solution for them. This is not a case of moving to the cloud, or investing tens of thousands of $ - it's a small company, but they need some best practices implemented.
I have 0 experience with MySQL - all my experience is on the MS sql server side.
Was thinking - could they set up a (physical or virtual) windows 2008 or 2012 machine and run mysql on it? That way it could be included as part of their backup plans.
Is it possible to go from a Linux MySQL database to a windows MySQL database? What's the easiest method to create a daily backup of a MySQL database? Is there a script I can run to export it to a file share somewhere (perhaps with the date in the filename)?
Just looking for overall best practices to go from a 10 year old debian server running the MySQL database, to '?'
MySQL Server
Last Comment
mankowitz
What is the long term plan with that application? When there is no further development, then I would simply migrate/clone that machine to a VM.
ASKER
I am still going to gather additional information like the version of mysql, etc.
My understanding is they are planning to keep using this applicaton although apparently it requires using an old version of access. That part I'm not going to be responsible for handling. Mainly I just need to make a best practice recommendation on getting the database running on a real server instead of an old desktop, and get a good backup practice in place
My understanding is they are planning to keep using this applicaton although apparently it requires using an old version of access. That part I'm not going to be responsible for handling. Mainly I just need to make a best practice recommendation on getting the database running on a real server instead of an old desktop, and get a good backup practice in place
ASKER
Anyone?
Anyone what? You haven't given us the additional detailed information. At least I was waiting for it.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
It's definitely a doable project but you may want to gather some more details before you try moving the data. Are they actually using Access and if so, what version and what version of the MySQL ODBC driver are they using? Are they using any programming languages like ASP, VBScript, or PHP to access the database?