Am 24.12.2011 23:13, schrieb Igor Shevtsov:
> Hi Reindl,
> what do you delete by
>> rm -f /Volumes/dune/mysql_data/bin*
> and why?
this should be "/mysql_data/bin*" to match to the rest of the sample
why?
because this is my script to make a new backup of a mysqld-master to
re-init the slave an
Hi Reindl,
what do you delete by
> rm -f /Volumes/dune/mysql_data/bin*
and why?
Many thanks.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
Am 23.12.2011 22:42, schrieb Wm Mussatto:
>> so you have a REAL consistent backup with minimal downtime you can restore
>> on any machine and pull dumps of whatever you really need instead of
>> breaindead hughe dumps with long locking time while they are done or
>> withut locking inconsistent st
On Fri, December 23, 2011 12:27, Reindl Harald wrote:
>
>
> Am 23.12.2011 21:14, schrieb Jim McNeely:
>> Hello all, happy holidays!
>>
>> What is the best way to run a mysqldump to get the tables, the data, the
>> triggers, the views, the procedures, the privileges and users,
>> everything? It seem
Hi Jim happy holidays to you!
actually you just need to add the --routines trigger
mysqldump --all-databases --*routines* > fulldump.sql
with this you get all databases including the system one with privileges
(mysql), triggers is on by default, you enable routines with the flag --*
routines*
*
Am 23.12.2011 21:14, schrieb Jim McNeely:
> Hello all, happy holidays!
>
> What is the best way to run a mysqldump to get the tables, the data, the
> triggers, the views, the procedures, the privileges and users, everything? It
> seems confusing in the online documentation, or is that just me?
