Wednesday, November 07, 2012 7:09 AM
> To: 'Gary'; mysql@lists.mysql.com
> Subject: RE: How to verify mysqldump files
>
> In the past when I used mysqldump, I used a slave database for backups and
> periodically testing restores.
>
> My process for testing:
> -
gj-my...@yahoo.co.uk]
Sent: Wednesday, November 07, 2012 7:52 AM
To: mysql@lists.mysql.com
Subject: How to verify mysqldump files
Can anyone suggest how I could verify that the files created by mysqldump are
"okay"? They are being created for backup purposes, and the last thing I want
to
2012/11/7 Ananda Kumar
> you can use checksum to make sure there are not corruption in the file
That would work for the file integrity itself not for the data integrity
_in_ the file.
As Claudio suggested, probably going thru the whole recovery process from
time to time is the best way to mak
you can use checksum to make sure there are not corruption in the file
On Wed, Nov 7, 2012 at 6:39 PM, Claudio Nanni wrote:
> Gary,
>
> It is always a good practice to test the whole solution backup/restore.
> So nothing is better than testing a restore, actually it should be a
> periodic procedu
Gary,
It is always a good practice to test the whole solution backup/restore.
So nothing is better than testing a restore, actually it should be a
periodic procedure.
As for the validity of the file usually is delegated to the operating
system.
If you want to check it yourself you may create an al
uge 500GB drives running one of *Nix's
Regards,
Mikhail Berman
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, January 29, 2007 3:27 PM
To: Mikhail Berman
Cc: mysql
Subject: RE: Mysqldump Files
Hi Mikhail,
I don't think that would save mu
huge 500GB drives running one of *Nix's
Regards,
Mikhail Berman
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, January 29, 2007 3:27 PM
To: Mikhail Berman
Cc: mysql
Subject: RE: Mysqldump Files
Hi Mikhail,
I don't think that would save muc
erman
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, January 29, 2007 2:33 PM
To: mysql
Subject: Mysqldump Files
Howdy Guys and Gals,
We are acquiring data on background radiation in a master-slave server
environment (RH9.0, MySQL 4.0.24) at the r
lection of tables to be used by web server. Or do full
replication to another server from the first one for full backup?
Regards,
Mikhail Berman
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, January 29, 2007 2:33 PM
To: mysql
Subject: Mysqldump Files
Howd
Howdy Guys and Gals,
We are acquiring data on background radiation in a master-slave server
environment (RH9.0, MySQL 4.0.24) at the rate of approximately 19,000
records per day. The data are insert-only into about 25 of 31 tables in
the database -- no updates are ever applied to the data. Inf
At 4:03 PM +0530 8/19/06, Anil wrote:
Hi List,
We are facing a problem of managing mysqldump out put file which is
currently of size 80 GB and it is growing daily by 2 - 3 GB, but we have a
linux partition of only 90 GB.. Our backup process is first generate the
mysqldump file of total data
August 2006 8:03 PM
To: mysql@lists.mysql.com
Subject: Managing big mysqldump files
Hi List,
We are facing a problem of managing mysqldump out put file which is
currently of size 80 GB and it is growing daily by 2 - 3 GB, but we
have a
linux partition of only 90 GB.. Our backup process is
Hi List,
We are facing a problem of managing mysqldump out put file which is
currently of size 80 GB and it is growing daily by 2 - 3 GB, but we have a
linux partition of only 90 GB.. Our backup process is first generate the
mysqldump file of total database and then compress the dump file and
PROTECTED]>
Subject: Re: Too slow recovering mysqldump files
Date: Wed, 21 Jan 2004 21:21:18 +0200
Mikel,
- Original Message -
From: "Mikel -" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, January 21, 2004 7:19 PM
Subjec
Mikel,
- Original Message -
From: "Mikel -" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, January 21, 2004 7:19 PM
Subject: Re: Too slow recovering mysqldump files
> I'll set up those parameters in my.cnf and tr
oth?
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
To: "Mikel -" <[EMAIL PROTECTED]>
CC: <[EMAIL PROTECTED]>
Subject: Re: Too slow recovering mysqldump files
Date: Wed, 21 Jan 2004 05:10:27 +0200
Mikel,
it is apparently disk-bound.
I recommend setting innodb_buffer_po
MAIL PROTECTED]>
> >To: <[EMAIL PROTECTED]>
> >Subject: Re: Too slow recovering mysqldump files
> >Date: Mon, 19 Jan 2004 22:44:50 +0200
> >
> >Mikel,
> >
> >have you set the size of the InnoDB log files as recommended in the manual?
> >
>
ect: Re: Too slow recovering mysqldump files
> Here we are my options:
>
> set-variable = innodb_log_file_size=150M
> set-variable = innodb_log_buffer_size=8M
>
> I follow the example that came here:
> "http://www.mysql.com/doc/en/InnoDB_start.html";
>
> Greetin
>
To: <[EMAIL PROTECTED]>
Subject: Re: Too slow recovering mysqldump files
Date: Mon, 19 Jan 2004 22:44:50 +0200
Mikel,
have you set the size of the InnoDB log files as recommended in the manual?
Best regards,
Heikki Tuuri
Innobase Oy
http://www.innodb.com
Foreign keys, transactions, and ro
]>
Subject: Re: Too slow recovering mysqldump files
Date: Mon, 19 Jan 2004 22:44:50 +0200
Mikel,
have you set the size of the InnoDB log files as recommended in the manual?
Best regards,
Heikki Tuuri
Innobase Oy
http://www.innodb.com
Foreign keys, transactions, and row level locking for MySQL
InnoD
MySQL technical support from https://order.mysql.com/
- Original Message -
From: ""Mikel -"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Monday, January 19, 2004 7:25 PM
Subject: Too slow recovering mysqldump files
> Hi list, does anyone k
Hi list, does anyone know a faster way to recover a mysqldump file cause
When I recovered one dump file it took 26 hours ! to finish, I think it's
too slow.
Thnx in advanced, greetings
MySQL server 3.23.58
RedHat 7.3
4GB RAM
2 scsi disk via fiber channel (333GB each)
2 processor Xeon 1.6GHZ
dum
22 matches
Mail list logo