From: Blaine Grady
Date: April 24 1999 11:14pm
Subject: Backups
List-Archive: http://lists.mysql.com/mysql/2335
Message-Id: <1287144975-167636469@webmail.knewell.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-Ascii"
Content-Transfer-Encoding: 7bit

I'm running Redhat 5.2 with Linux 2.0.36.  I am running MySQL 3.22.21. 
By default when I installed MySQL with the RPMs, mysqld is started with
--skip-locking.  Every night I want BRU to backup all the files on my drive. 
With skip-locking, can I be guaranteed I can backup the raw database
files and not have any problems with MySQL server or corrupt files, given that
no changes are being written to the file?  Is this correct?  So I can
keep mysqld running throughout the backup procedure, even if users are
reading from, but not writing to, the database?  The same for running isamchk? 
If not, I have to stop mysqld temporarily, make the backup, restart
mysqld, right?  What would happen if I started mysqld with no --skip-locking? 
Then I can copy the files with no problem.  Why do Linux machines need
this?  Thanks for any assistance.


Blaine Grady
Webmaster/Database Developer
Kragie Newell Integrated Marketing