Actions
Incident #10101
closedMongo5-p-d4s: full backup not completed after 24h
Status:
Closed
Priority:
Normal
Assignee:
Category:
System Application
Target version:
Start date:
Oct 30, 2017
Due date:
% Done:
100%
Estimated time:
Infrastructure:
Production
Description
After the mongo5 full resync we have tried to perform a full backup but this backup process takes about 24 hours. I've stopped the process for the moment.
We need to understand why this process takes a long time
Related issues
Updated by Roberto Cirillo over 7 years ago
- Related to Incident #10063: Mongo5-p-d4s: disk space is critical added
Updated by Tommaso Piccioli over 7 years ago
- Status changed from New to In Progress
Updated by Tommaso Piccioli over 7 years ago
- Status changed from In Progress to Closed
The mongo backup process is OK now.
I created a new host definition on the backuppc server using a DNS alias of mongo5-p-d4s.d4science.org (mongo-backup.d4science.org) and the full backup takes quite the same time that we have before the full resync of the mongodb.
Actions