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
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 claudio.na...@gmail.comwrote:
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
2012/11/7 Ananda Kumar anan...@gmail.com
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
...@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 do is find out
, 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:
- Stop the slave process (so the db doesn't get updated).
- Run
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 much space, in terms of file size
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.
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
Howdy Guys
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 rate of approximately 19,000
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 much space, in terms of file
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
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
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
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
InnoDB Hot Backup
: 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_pool_size as high as 1.4 GB during such
big import. Adjust
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 try again the recovery from the
dump file
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
Subject: Re: Too slow recovering mysqldump files
I'll set up those parameters in my.cnf and try
: 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
InnoDB Hot
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 row level
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
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 know a faster way to recover
21 matches
Mail list logo
