Incident #8411
closed
mongodb production, problem with backup
100%
Description
Il backup di mongo si è interrotto in modo anomalo durante questo fine settimana, sto indagando sulle possibili cause.
Al momento ci manca un backup completo dei dati almeno dal 4 maggio (c'è un backup parziale il 6 maggio).
Updated by Roberto Cirillo almost 8 years ago
I've checked the mongo5-p-d4s instance and it is correctly synchronized with the primary node.
Updated by Tommaso Piccioli almost 8 years ago
- Status changed from New to In Progress
We are going to test it with a longer timeout config, next backup will start 19:53 today.
Updated by Tommaso Piccioli almost 8 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
It seems to be solved with tar over ssh transfer method instead of rsync.
I will check again after week-end
Updated by Pasquale Pagano almost 8 years ago
- Status changed from Resolved to Closed
Updated by Tommaso Piccioli almost 8 years ago
During the week-end mongo backup with the rsync method was OK (full and iocremental)
Restored the rsync method bcause it is faster.
Probably there was a corrupted file in a old backup that prevent the rsync differential mechanism towork correctly, using the tar method for a single full backup solved this issue.
