View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000811bareos-corefile daemonpublic2017-04-11 21:592017-04-11 21:59
Reporterasalvo Assigned To 
PrioritynormalSeverityfeatureReproducibilityalways
Status newResolutionopen 
Product Version16.2.4 
Summary0000811: Unable to relocate SQL Server database files on restore
DescriptionThe 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 ReproduceJust a plain restore with DB rename on the same host should be enough to reproduce.
Additional InformationI 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?
TagsNo tags attached.
bareos-master: impact
bareos-master: action
bareos-19.2: impact
bareos-19.2: action
bareos-18.2: impact
bareos-18.2: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2017-04-11 21:59 asalvo New Issue