All work
- PBM fails to catch up PITR if oplogOnly option is enabledPBM-1542
- Option to exclude in-memory nodes from backups in a sharded clusterPBM-1541
- PBM status returns error if pbm --force-resync and --file are called togetherPBM-1540
- pbm cannot connect to db due to invalid PBM_MONGODB_URI with requireTLSPBM-1539
- Backup is marked as successful despite oplog wasn't uploadedPBM-1538
- Enable PBM to monitor storage changes and automatically update metadata in the PBM system collectionPBM-1537
- Restore backup from replica set to a sharded clusterPBM-1536
- PBM backup is not starting for 40 shard cluster.PBM-1535
- Log information about throughput and %progressPBM-1534
- Improve 'Point-in-time restore from physical backups' sectionPBM-1533Anastasia Alexandrova
- Latest PBM (2.9.1) tar package is emptyPBM-1532Resolved issue: PBM-1532Sandra Romanchenko
- Expiring Kerberos Ticket requires automatic renewalPBM-1530
- PBM doesn't return a clear error if backup can't be started in mixed envPBM-1528
- Custom S3 TLS Certificate support in PBMPBM-1525radoslaw.szulgo
- Possibly incorrect namespaces excludePBM-1523Boris Ilijic
- Users restored incorrectly in selective restorePBM-1522Resolved issue: PBM-1522Boris Ilijic
- PITR selective restore does not restore usersPBM-1521
- Missing PBM 2.9.0 in compatibility matrixPBM-1520Resolved issue: PBM-1520radoslaw.szulgo
- PBM logs inexistent PITR error during physical restorePBM-1519Boris Ilijic
- Document that priorities cannot be set using "config --set"PBM-1518Resolved issue: PBM-1518Anastasia Alexandrova
- Improve resync performancePBM-1514Jakub Vecera
- Add configurable timeout for pbm backupPBM-1513
- PBM unable to take physical backup in mixed deploymentsPBM-1512Resolved issue: PBM-1512Boris Ilijic
- Configuration for Fallback dbpath featurePBM-1511Boris Ilijic
- Allow pbm-agent to run with no database connectionPBM-1510
- Oplog collection stops without any apparent reasonPBM-1509
- Remove any db queries during physical restorePBM-1508
- Fallback dbpath for physical restorePBM-1507Boris Ilijic
- GCS support concurrent downloading of the single filePBM-1506Jakub Vecera
- Remove the copy of users and roles during logical backupPBM-1505
- Add PBM support for Workload Identity AuthenticationPBM-1504
- pbm describe-restore returns empty output if a profile used in config filePBM-1503Resolved issue: PBM-1503radoslaw.szulgo
- pbm profile sync failsPBM-1502Resolved issue: PBM-1502Jakub Vecera
- Restore from pbm hangs after some time.PBM-1501Resolved issue: PBM-1501Boris Ilijic
- Document PBM SDKPBM-1500Anastasia Alexandrova
- Unformatted error in restore metadataPBM-1499
- HMAC support for GCSPBM-1498Jakub Vecera
- Ability to set a timeout duration for stopping the balancerPBM-1496
- Wrong s3 URI in pbm statusPBM-1494Boris Ilijic
- Sharded cluster restoration failure in 2.8.0PBM-1493Boris Ilijic
- Avoid exposing db credentials in /etc/sysconfig/pbm-agentPBM-1492
- Configuration profiles are not shown in statusPBM-1491
- Physical backup with files that have reached remote storage limitsPBM-1490
- Integrate PBM with cloud provider snapshot technology
PBM-1489 - PITR will stop saving the oplog if the process of copying the oplog from the backup failsPBM-1488
- Error Location6493100 on mongos after successful logical restore or PITRPBM-1487Boris Ilijic
- Queryable backup and restore for PBMPBM-1486radoslaw.szulgo
- pbm-agent.init file has misspelled group name and it fails to start the pbm agentPBM-1485Resolved issue: PBM-1485Sandra Romanchenko
- Allow/ignore "Z" marker in the restore timestampsPBM-1481Resolved issue: PBM-1481Boris Ilijic
- PBM cannot restore/resync from a read-only datastore, improve to allow this to work even if some restrictionsPBM-1480
50 of
Incorrect Advisor Insights
General
Escalation
General
Escalation
Description
How to test
None
How to document
None
Created February 20, 2025 at 9:22 AM
Updated February 26, 2025 at 10:45 AM
Activity
Show:
Under PMM Advisor insights, it says mongodb journaling is not enabled. We are using MongoDB version 7 and journaling is enabled by default.
If we still add journaling, MongoDB refuses to start. Please correct Advisor config.
PMM version: 2.44
Mongo version: 7.0.9-15
Error message if we add journaling:
{"t":{"$date":"2025-02-20T09:17:08.596Z"},"s":"W", "c":"CONTROL", "id":29117, "ctx":"main","msg":"The storage.journal.enabled option and the corresponding --journal and --nojournal command-line options have no effect in this version of Percona Server for MongoDB. Journaling is always enabled. Please remove those options from the config","tags":["startupWarnings"]}