and use the binary log (you do keep a binary log, right?) for incremental
backups. If we need to restore near the end of the month, it's a bit of a
pain, but better than forking all that cash for the bandwidth to do complete
backups every day.
Have you doublechecked that you can connect to the server with those
credentials, and that the user has the needed access to the DB in question?
Here's the specific command line we run (on RedHat 8, MySQL 4.0):
mysqldump -u<username> -p<password> --add-drop-table --add-locks --all
--quick --disable-keys --extended-insert --single-transaction --quote-names
<db> | gzip > /path/to/backup/dir/<db>.<date>.sql.gz
Cheers,
barneyb
> -----Original Message-----
> From: Spectrum WebDesign [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 14, 2004 7:31 AM
> To: CF-Talk
> Subject: Backing up MySQL InnoDB DB
>
> Hi all
>
> our app run this .bat file to create a sql script(backup)
> from our MySQL DB.
>
> c:\mysql\bin\mysqldump.exe --single-transaction -quick -u name_user
> -ppass_user ourDB > c:\mysql\data\backups\ourDB_#datePart#.sql
>
> But results 0(zero) size... what's happened?
>
>
> Do you have experience in backing up MySQL?
>
> Thanx for your time.
>
> p.s.: Windows 2003/MySQL 4.0.16/CF MX 6.1
> --
> ___________________________________________________________
> Sign-up for Ads Free at Mail.com
> http://promo.mail.com/adsfreejump.htm
>
>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
