mysqlbinlog failing with " ERROR 1032 (HY000) at line 48: Can't find record in `` " Error
PROBLEM

You are starting from the wrong log. You should start with mysql-bin.000034 not mysql-bin.000035

The timestamp on each binlog shows the last time a binlog event was written to it


mysql-bin.000033 was last written Dec 27 18:26
mysql-bin.000034 was last written Feb  2 18:58. That's 18 hrs 58 min after Feb  2 00:00
mysql-bin.000035 had to be created Feb  2 18:58


Given the timestamps mentioned, mysql-bin.000034 is the log you need to start with.

SOLUTION

You should collect the binlog events from Feb  2 00:00

Please run the following

MYCHANGES=ChangesSinceFeb2Backup.sql
BINLOGS="mysql-bin.000034 mysql-bin.000035"
cd /var/lib/mysql
mysqlbinlog --start_datetime="2014-02-02 00:00:00" ${BINLOGS} &gt; ${MYCHANGES}


Restore the Feb 2 mysqldump Backup, then play all the events

mysql -u root -p db &lt; ${MYCHANGES}


This will bring back everything up to Feb 18 15:50

If you want to do the PITR up to today at 12:45, you do this 

MYCHANGES=ChangesSinceFeb2Backup.sql
cd /var/lib/mysql
mysqlbinlog --start_datetime="2014-02-02 00:00:00" --stop_datetime="2014-02-18 12:45:00" ${BINLOGS} &gt; ${MYCHANGES}


SUGGESTION

Note that mysql-bin.000035 contains several days worth of binlog events.

Before you run the midnight backup, you should run

FLUSH BINARY LOGS;


That way, you can clearly identify what binary logs to use in PITR

Give it a Try !!!