pbm should print a friendly error when trying to execute physical backup in the inMemory engine

Description

When running pbm backup on an inMemory MongoDB instance:

$ pbm backup --type=physical Starting backup '2022-05-09T19:19:50Z'.. .Error: get backup files: create backupCursor: (Location40324) Unrecognized pipeline stage name: '$backupCursor'

And pbm-agent:

2022-05-09T15:19:51.000-0400 D [backup/2022-05-09T19:19:50Z] init backup meta 2022-05-09T15:19:51.000-0400 D [backup/2022-05-09T19:19:50Z] nomination list for replset: [[localhost:37017]] 2022-05-09T15:19:51.000-0400 D [backup/2022-05-09T19:19:50Z] nomination replset, set candidates [localhost:37017] 2022-05-09T15:19:52.000-0400 I [backup/2022-05-09T19:19:50Z] backup started 2022-05-09T15:19:53.000-0400 I [backup/2022-05-09T19:19:50Z] mark RS as error `get backup files: create backupCursor: (Location40324) Unrecognized pipeline stage name: '$backupCursor'`: <nil> 2022-05-09T15:19:53.000-0400 I [backup/2022-05-09T19:19:50Z] mark backup as error `get backup files: create backupCursor: (Location40324) Unrecognized pipeline stage name: '$backupCursor'`: <nil> 2022-05-09T15:19:53.000-0400 E [backup/2022-05-09T19:19:50Z] backup: get backup files: create backupCursor: (Location40324) Unrecognized pipeline stage name: '$backupCursor' 2022-05-09T15:19:53.000-0400 D [backup/2022-05-09T19:19:50Z] releasing lock

The message should be more friendly to the user than throwing the Mongo error.

 

Environment

transitioned this issue to improvement and the solution should be discussed with

Activity

radoslaw.szulgo 
February 3, 2025 at 12:21 PM

For physical backups “InMemory” storage engine is not supported:

https://docs.percona.com/percona-backup-mongodb/features/physical.html?h=wired+tiger

 

PBM should return a user-friendly message that only WiredTiger storage engine is supported.

Details

Assignee

Reporter

Labels

Priority

Created May 9, 2022 at 7:20 PM
Updated February 3, 2025 at 12:21 PM