View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000811 | bareos-core | file daemon | public | 2017-04-11 21:59 | 2024-02-28 09:50 |
Reporter | asalvo | Assigned To | bruno-at-bareos | ||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | won't fix | ||
Product Version | 16.2.4 | ||||
Summary | 0000811: Unable to relocate SQL Server database files on restore | ||||
Description | The plugin is able to restore a database with a different name than the original but I couldn't find a way to rename the actual database files or relocate them to another folder. This effectively prevents a database from being restored alongside the original unless restoring to file and then importing into the engine with the MOVE option. | ||||
Steps To Reproduce | Just a plain restore with DB rename on the same host should be enough to reproduce. | ||||
Additional Information | I think this is probably a limitation of the TSQL command to restore that seems to require previous knowledge of the database MDF/LDF records in order to move them. Could this be worked around by saving these records as metadata during backup and used, in conjunction with some relocation parameter, during restore? | ||||
Tags | No tags attached. | ||||
The requested feature doesn't get any community support, and as such will not get implemented. Please contact sales department if you want it, or be able to sponsor it in full or even in parts |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2017-04-11 21:59 | asalvo | New Issue | |
2024-02-28 09:50 | bruno-at-bareos | Assigned To | => bruno-at-bareos |
2024-02-28 09:50 | bruno-at-bareos | Status | new => closed |
2024-02-28 09:50 | bruno-at-bareos | Resolution | open => won't fix |
2024-02-28 09:50 | bruno-at-bareos | Note Added: 0005814 |