Issues
- Incorrect processing of local storagePBM-328Resolved issue: PBM-328andrew.pogrebnoi
- cannot backup sharding cluster - mongodump finished, waiting to finish oplog on config nodePBM-323Resolved issue: PBM-323andrew.pogrebnoi
- backup user privileges need to be differentPBM-311Resolved issue: PBM-311Borys Belinsky
- PBM-agent do restore for hidden nodes with minio-s3PBM-300Resolved issue: PBM-300stefan.vinasi
- Cannot create backup for minio-s3 and shardingPBM-296Resolved issue: PBM-296stefan.vinasi
- Test large number of backupsPBM-292Resolved issue: PBM-292stefan.vinasi
- Test large backups and restoresPBM-291Resolved issue: PBM-291Sandra Romanchenko
- Test backup on 3.6 and restore on 4.0 and vice versaPBM-290Resolved issue: PBM-290
- Test TLS options with MongoDBPBM-288Resolved issue: PBM-288stefan.vinasi
- Test applying oplog on restore (diff. collection types, index types, aggregation updates)PBM-287Resolved issue: PBM-287stefan.vinasi
- restore issue - cannot restore full text index from oplog - invalid index key: no fields providedPBM-285Resolved issue: PBM-285stefan.vinasi
- test - add new package tests for PBMPBM-282Resolved issue: PBM-282stefan.vinasi
- Missed config file checks for pbm-agent.PBM-279Resolved issue: PBM-279stefan.vinasi
- check system collections when applying oplogPBM-267Resolved issue: PBM-267stefan.vinasi
- renameCollection: backup fails but no messages in pbm-agent or pbm-coordinator logsPBM-255Resolved issue: PBM-255stefan.vinasi
- pbm-agent lost session during backupPBM-253Resolved issue: PBM-253stefan.vinasi
- pbm-agent crashes if primary steps down during the restore with restore command running foreverPBM-214Resolved issue: PBM-214stefan.vinasi
- no upload/download log entries in agent/coordinator logPBM-191Resolved issue: PBM-191stefan.vinasi
- Test for consistent backup/restorePBM-82Resolved issue: PBM-82stefan.vinasi
19 of 19
Incorrect processing of local storage
Done
General
Escalation
General
Escalation
Description
Environment
None
relates to
Smart Checklist
Details
Assignee
andrew.pogrebnoiandrew.pogrebnoiReporter
Borys BelinskyBorys Belinsky(Deactivated)Labels
Components
Fix versions
Priority
Medium
Details
Details
Assignee
andrew.pogrebnoi
andrew.pogrebnoiReporter
Borys Belinsky
Borys Belinsky(Deactivated)Labels
Components
Fix versions
Priority
MediumSmart Checklist
Smart Checklist
Smart Checklist
Created September 16, 2019 at 11:02 AM
Updated March 5, 2024 at 7:22 PM
Resolved December 2, 2019 at 6:45 AM
Activity
Show:
Akira KuroganeOctober 7, 2019 at 6:17 AM
@andrew.pogrebnoi I was testing this today (2019-10-07) and found that it worked. Please see point #3 in https://perconadev.atlassian.net/browse/PBM-349#icft=PBM-349.
I don't know what happened, but it seems you fixed this during development and hadn't updated this ticket. Can we close it now?
Previous versions supported defining storages in the local file system. If the user supplies a local storage in the YAML file and runs pbm store set on it the program runs successfully without issuing a warning that this store type is not supported and updates the pbmConfig collection with meaningless information.