mysql-bin log file

--0016363b86a87dfe7f04848efa2e
Content-Type: text/plain; charset=ISO-8859-1

How can I remove old mysql-bin log file in log directory? A mysql full
backup will clear the old mysql bin log file or not?

Thanks,
Arshu Paul

--0016363b86a87dfe7f04848efa2e--

Re: mysql-bin log file

On Sun, Apr 18, 2010 at 8:58 PM, Angelina Paul wrote:
> How can I remove =A0old =A0mysql-bin log file in log directory? A mysql f=
ull
> backup will clear the old mysql bin log file or not?
>
> Thanks,
> Arshu Paul
>
You probably want
http://mysql2.mirrors-r-us.net/doc/refman/5.1/en/purge-maste r-logs.html


--=20
Rob Wultsch
wultsch@gmail.com

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg

Re: mysql-bin log file

--00163630fd5bf623d404848f8d72
Content-Type: text/plain; charset=ISO-8859-1

You can add a *expire_logs_days* Variable in my.cnf during the
configuration of replication server.

#* expire_logs_days = 7*

It will purged binary logs older than 7 days.The old logs will be purged
during the next bin-log switch.

Or, You can also delete bin-log manually using command :

PURGE BINARY LOGS TO 'mysql-bin.010';
PURGE BINARY LOGS BEFORE '2008-04-02 22:46:26';

but before you purge please make sure that slave is on sync with master or
confirm the current status from slaves.

Thanks,

On Mon, Apr 19, 2010 at 9:47 AM, Rob Wultsch wrote:

> On Sun, Apr 18, 2010 at 8:58 PM, Angelina Paul
> wrote:
> > How can I remove old mysql-bin log file in log directory? A mysql full
> > backup will clear the old mysql bin log file or not?
> >
> > Thanks,
> > Arshu Paul
> >
> You probably want
> http://mysql2.mirrors-r-us.net/doc/refman/5.1/en/purge-maste r-logs.html
>
>
> --
> Rob Wultsch
> wultsch@gmail.com
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
> http://lists.mysql.com/mysql?unsub=aim.prabhat@gmail.com
>
>


--
Best Regards,

Prabhat Kumar
MySQL DBA
Datavail-India Mumbai
Mobile : 91-9987681929
www.datavail.com

My Blog: http://adminlinux.blogspot.com
My LinkedIn: http://www.linkedin.com/in/profileprabhat

--00163630fd5bf623d404848f8d72--

Re: mysql-bin log file

On Sun, Apr 18, 2010 at 9:40 PM, Prabhat Kumar wrot=
e:
> You can=A0 add a expire_logs_days Variable in my.cnf during the configura=
tion
> of replication server.
>
> # expire_logs_days =3D 7
>
> It will purged binary logs older than 7 days.The old logs will be purged
> during the next bin-log swittch.
>


And if your slave's IO lags badly enough this will hose you. Further
it might well come in handy to an arbitrary number of bin logs for
pirt purposes.

--=20
Rob Wultsch
wultsch@gmail.com

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg

Re: mysql-bin log file

--001485e77336fa9b25048492722b
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Apr 19, 2010 at 6:48 AM, Rob Wultsch wrote:

>
> And if your slave's IO lags badly enough this will hose you. Further
>

True, but if you remove logs that haven't been transferred, yet, you lose
your slave.

Transfer of logs shouldn't be lagging that much, really, unless you're
replicating over some POTS line. Don't forget that log transfer doesn't have
to wait for processing on the slave.

--
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel

--001485e77336fa9b25048492722b--

Re: mysql-bin log file

On Mon, Apr 19, 2010 at 1:07 AM, Johan De Meersman wrote:
> On Mon, Apr 19, 2010 at 6:48 AM, Rob Wultsch wrote:
>>
>> And if your slave's IO lags badly enough this will hose you. Further
>
> True, but if you remove logs that haven't been transferred, yet, you lose
> your slave.
>
> Transfer of logs shouldn't be lagging that much, really, unless you're
> replicating over some POTS line. Don't forget that log transfer doesn't have
> to wait for processing on the slave.
>
> --

Agreed. 7 days is an absurd length of time for the io thread to lag.
However, if someone has setup replication but not monitoring it, 7
days isn't that long. The behavior of mysql after a crash (that is,
breaking the io thread) makes me weary of suggesting to a
inexperienced user that they should turn on this features.

In an ideal world the user should determined how many days of backups
they need and further how much pitr. It might be very sane to say 30
days of daily backups with 7 days of pitr. One way or another this
should be a conscious decision, not a copy and paste from a mailing
list.

--
Rob Wultsch
wultsch@gmail.com

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

Re: mysql-bin log file

--0016e64dc932a3ecc60484959f8e
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Apr 19, 2010 at 12:16 PM, Rob Wultsch wrote:

> One way or another this
> should be a conscious decision, not a copy and paste from a mailing
> list.
>

As is the case with most settings :-)


--
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel

--0016e64dc932a3ecc60484959f8e--