View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001465 | bareos-core | file daemon | public | 2022-05-23 13:31 | 2023-12-13 15:36 |
Reporter | mdc | Assigned To | bruno-at-bareos | ||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | won't fix | ||
Platform | x86_64 | OS | CentOS | OS Version | stream 8 |
Product Version | 21.1.3 | ||||
Summary | 0001465: Use the virtual file path + prefix when no writer is set | ||||
Description | Creating the backup woks fine, but on restore there exists often the problem, that the restore must be done to an normal file like in the PostgreSQL or MariaDB add on. But when using the an dd or the demo code that is in the documentation, the file can only created in an absolute path. I think it will be better, when no writer command is set(or :writer=none), that the file restore is done to the file prefix (Where setting of the restore job) + path of the virtual file like it is done in the both python add-on's. Sample: bpipe:file=/_mongobackups_/foo_db.archive:reader=sh -c 'cat /foo/backup_pw_file | mongodump <OPT ... > --archive':writer=none" Then the file will written to <where>/_mongobackups_/foo_db.archive | ||||
Tags | bpipe | ||||
As it looks like more a feature request, why not proposing a PR with ? ;-) | |
Closing as no PR has been proposed | |
Date Modified | Username | Field | Change |
---|---|---|---|
2022-05-23 13:31 | mdc | New Issue | |
2022-05-23 13:31 | mdc | Tag Attached: bpipe | |
2022-09-21 16:02 | bruno-at-bareos | Note Added: 0004755 | |
2023-12-13 15:36 | bruno-at-bareos | Assigned To | => bruno-at-bareos |
2023-12-13 15:36 | bruno-at-bareos | Status | new => closed |
2023-12-13 15:36 | bruno-at-bareos | Resolution | open => won't fix |
2023-12-13 15:36 | bruno-at-bareos | Note Added: 0005637 |