NetWorker: Il backup MySQL ha esito negativo quando il file "binlog" non esiste

Summary: I primi backup di MySQL con NetWorker Module for Databases and Applications (NMDA) non vengono mai completati se il file "binlog" non esiste.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Il primo backup di MySQL non termina mai quando il file "binlog" non esiste nel database MySQL.

 

Cause

Poiché il file "binlog" di MySQL non esiste, il client NetWorker non continua l'attività di backup.

IMPORTANTE: Le prove relative a questa root cause vengono visualizzate solo quando il processo di backup di NetWorker viene eseguito con "Debug Level" uguale a "5".

Dal client NetWorker, il file di log di NetWorker (percorso predefinito: /nsr/logs) segnala il "binlog" mancante di quel database MySQL:

mysqlbackup: WARNING: binlog file '/data/mysql/mysql-bin.000331' does not exist. It could have been purged. PITR will not be possible from this backup.
  mysqlbackup: WARNING: binlog file '/data/mysql/mysql-bin.000332' does not exist. It could have been purged. PITR will not be possible from this backup.
  mysqlbackup: WARNING: binlog file '/data/mysql/mysql-bin.000333' does not exist. It could have been purged. PITR will not be possible from this backup.
  mysqlbackup: WARNING: binlog file '/data/mysql/mysql-bin.000334' does not exist. It could have been purged. PITR will not be possible from this backup.
  mysqlbackup: WARNING: binlog file '/data/mysql/mysql-bin.000335' does not exist. It could have been purged. PITR will not be possible from this backup.
  mysqlbackup: WARNING: binlog file '/data/mysql/mysql-bin.000336' does not exist. It could have been purged. PITR will not be possible from this backup.
  mysqlbackup: WARNING: binlog file '/data/mysql/mysql-bin.000337' does not exist. It could have been purged. PITR will not be possible from this backup.
  mysqlbackup: WARNING: binlog file '/data/mysql/mysql-bin.000338' does not exist. It could have been purged. PITR will not be possible from this backup.
  mysqlbackup: WARNING: binlog file '/data/mysql/mysql-bin.000339' does not exist. It could have been purged. PITR will not be possible from this backup.
  mysqlbackup: WARNING: binlog file '/data/mysql/mysql-bin.000340' does not exist. It could have been purged. PITR will not be possible from this backup.
  mysqlbackup: WARNING: binlog file '/data/mysql/mysql-bin.000341' does not exist. It could have been purged. PITR will not be possible from this backup.
  ...
  mysqlbackup: WARNING: binlog file '/data/mysql/mysql-bin.004583' does not exist. It could have been purged. PITR will not be possible from this backup.
  mysqlbackup: WARNING: binlog file '/data/mysql/mysql-bin.004584' does not exist. It could have been purged. PITR will not be possible from this backup.
 200901 14:37:32 mysqlbackup: INFO: Copying /data/mysql/mysql-bin.004585. <-- Activity log stuck in this step and backup does not send any new data.The backup job must be canceled manually or wait to timeout (in this case it was after 8 hours running).
 mysqlbackup: Progress in MB: 383400
 mysqlbackup: ERROR: Signal 15 received.

 

Resolution

Per risolvere questo problema, eliminare tutti i precedenti "binlog" mancanti fino al primo "binlog" disponibile.

IMPORTANTE: Nella procedura seguente, il primo "binlog" disponibile è denominato "mysql-bin.004585", ma questo è solo un esempio di un ambiente di laboratorio per spiegare una possibile soluzione.

Procedura

DICHIARAZIONE DI NON RESPONSABILITÀ: Prima di seguire questa procedura, Dell Technologies consiglia di coinvolgere un amministratore MySQL per convalidare in anticipo prima di applicare questo metodo come la migliore soluzione possibile in base al proprio ambiente.

  1. Accedere al server MySQL come utente "root".

  2. Connettiti alla console del database MySQL.

  3. Verificare la disponibilità corrente di "binlog" eseguendo il seguente comando:

    mysql> show master logs;  <-- Name of the DB that contains the information from the logs missed.

| mysql-bin.004580 |          0 |
| mysql-bin.004581 |          0 |
| mysql-bin.004582 |          0 |
| mysql-bin.004583 |          0 |
| mysql-bin.004584 |          0 | <-- Last missed log.
| mysql-bin.004585 | 1064394753 |

  4. Eliminare tutti i "binlog" mancanti precedenti al primo "binlog" disponibile eseguendo il seguente comando:

    Nota: In questo caso, "mysql-bin.004585" è il primo "binlog" disponibile. 
    mysql> purge binary logs to 'mysql-bin.004585';
Query OK, 0 rows affected, 4584 warnings (10.12 sec)

  5. Eseguire nuovamente il processo di backup per verificare che venga completato senza errori.

    • Prova di un job di backup riuscito (come mostrato nei log di NetWorker dal lato client):
    200903 09:38:14 mysqlbackup: INFO: Backup image created successfully.
mysqlbackup: INFO: Image Path = sbt:MYSQL:/MySQLTest
200903 09:38:14 mysqlbackup: INFO: MySQL binlog position: filename mysql-bin.004957, position 154

-------------------------------------------------------------
   Parameters Summary
-------------------------------------------------------------
   Start LSN                  : 15597868102656
   End LSN                    : 15597868102712
-------------------------------------------------------------
mysqlbackup completed OK! with 2 warnings.

 

Products

NetWorker Module for Databases and Applications
Article Properties
Article Number: 000173788
Article Type: Solution
Last Modified: 06 Mar 2026
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.