You could be cheap, install another MySQL daemon running on a different port
with different data folders, as a slave, and backup that one without a
performance hit.
On Mon, Dec 29, 2008 at 8:06 PM, Mike Lovell wrote:
> William Attwood wrote:
>
>> I was hoping that was a given. I should have ex
William Attwood wrote:
I was hoping that was a given. I should have explained better. Flush
tables, shut down MySQL, and then tarball the entire data folder.
-Will
An option that was explored where I work was have the MySQL tables on a
LVM volume, stop the server, create and LVM snapshot, s
I was hoping that was a given. I should have explained better. Flush
tables, shut down MySQL, and then tarball the entire data folder.
-Will
On Mon, Dec 29, 2008 at 7:57 PM, Jonathan Ellis wrote:
> That's a good way to get a corrupt export unless you shut down the server
> first.
>
> -Jonathan
That's a good way to get a corrupt export unless you shut down the server first.
-Jonathan
On Mon, Dec 29, 2008 at 5:18 PM, William Attwood wrote:
> You may also try just tarballing the entire data folder for MySQL; may be
> faster if you have that much data to export.
> -Will
>
> On Mon, Dec 29
On Mon, 2008-12-29 at 16:42 -0700, Charles Curley wrote:
> On Mon, Dec 29, 2008 at 04:18:16PM -0700, William Attwood wrote:
> > You may also try just tarballing the entire data folder for MySQL; may be
> > faster if you have that much data to export.
> > -Will
>
> And likely would break transactio
On Mon, Dec 29, 2008 at 04:06:20PM -0700, Ryan Byrd wrote:
> how can one throttle the mysqldump so it doesn't use as many system
> resources?
Unless there's something specific to mysql, "man nice".
--
Charles Curley /"\ASCII Ribbon Campaign
Looking for fine software
On Mon, Dec 29, 2008 at 04:18:16PM -0700, William Attwood wrote:
> You may also try just tarballing the entire data folder for MySQL; may be
> faster if you have that much data to export.
> -Will
And likely would break transactional integrity.
--
Charles Curley /"\ASCII Rib
On Monday 29 December 2008 04:22:38 pm Nicholas Leippe wrote:
> On Monday 29 December 2008 04:06:20 pm Ryan Byrd wrote:
> > So, let's say there is this centos box is running a mysql database
> > that has db tables that are pretty big, (some > 1x10^6 rows)
> >
> > and when one runs mysqldump on the
On Monday 29 December 2008 04:06:20 pm Ryan Byrd wrote:
> So, let's say there is this centos box is running a mysql database
> that has db tables that are pretty big, (some > 1x10^6 rows)
>
> and when one runs mysqldump on the database, it spikes the load
> average, as reported by top, on the box t
You may also try just tarballing the entire data folder for MySQL; may be
faster if you have that much data to export.
-Will
On Mon, Dec 29, 2008 at 4:11 PM, William Attwood wrote:
> Hmmm. You can set the MySQLDump memory usage in your MySQL Configuration
> file. [mysqldump]
> quick
> max_allo
Hmmm. You can set the MySQLDump memory usage in your MySQL Configuration
file. [mysqldump]
quick
max_allowed_packet = 16M
That should help with the processor load spike, hopefully.
-Will
On Mon, Dec 29, 2008 at 4:06 PM, Ryan Byrd wrote:
> So, let's say there is this centos box is running a
So, let's say there is this centos box is running a mysql database
that has db tables that are pretty big, (some > 1x10^6 rows)
and when one runs mysqldump on the database, it spikes the load
average, as reported by top, on the box to about 15
this box also is running apache
when the load averag
12 matches
Mail list logo
