From owner-freebsd-questions@FreeBSD.ORG Tue Oct 7 14:37:04 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59F0D1065694 for ; Tue, 7 Oct 2008 14:37:04 +0000 (UTC) (envelope-from mcoyles@horbury.wakefield.sch.uk) Received: from smtp2-wak.yhgfl.net (smtp2-wak-ext.yhgfl.net [89.207.208.43]) by mx1.freebsd.org (Postfix) with ESMTP id CEDD58FC17 for ; Tue, 7 Oct 2008 14:37:03 +0000 (UTC) (envelope-from mcoyles@horbury.wakefield.sch.uk) Received: from horbury.wakefield.sch.uk ([10.126.96.34]) by smtp2-wak.yhgfl.net (8.13.8/8.13.8/Debian-3) with ESMTP id m97EankA004479 for ; Tue, 7 Oct 2008 15:36:50 +0100 Received: from ITTEAM02 [10.126.96.253] by horbury.wakefield.sch.uk with ESMTP (SMTPD32-7.07) id A3FB96D008A; Tue, 07 Oct 2008 15:36:43 +0100 From: "Marc Coyles" To: Date: Tue, 7 Oct 2008 15:36:41 +0100 Message-ID: <008101c9288a$1cffbdd0$56ff3970$@wakefield.sch.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AckoihzU9ZBBonnQTsibzsu0lL6Wbg== Content-Language: en-gb X-YHGfL-MailScanner-Information: Please contact the YHGfL Foundation for more information X-YHGfL-MailScanner: Found to be clean X-YHGfL-MailScanner-MCPCheck: MCP-Clean, MCP-Checker (score=0, required 0.5) X-YHGfL-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.399, required 5, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60) X-MailScanner-From: mcoyles@horbury.wakefield.sch.uk Subject: Consistency of MySQL dumps... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mcoyles@horbury.wakefield.sch.uk List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Oct 2008 14:37:04 -0000 Here's one that's puzzling me... If I use /usr/local/bin/mysqldump to make a backup of a database, the file it produces fails to restore with "Check syntax near..." error. If I then head into cPanel, to their "Backup" menu, and take a backup of the database from there, the file it produces also fails to restore with "Check syntax near..." error, but at a COMPLETELY different point thru the restore. If I head into cPanel, to phpmyadmin, and do an export from there... the file restores PERFECTLY without errors. Sooo... how can I write a script that'll backup a MySQL database and produce a useable file?? This problem is occurring on 2 of my 8 databases... it appears the chosen software used to produce the dump of MySQL data is the culprit... what is the best commandline (ie: cron-able) tool to use for the task? Marc A Coyles - Horbury School ICT Support Team Mbl: 07850 518106 Land: 01924 282740 ext 730 Helpdesk: 01924 282740 ext 2000