the main problem is: If i do that, i have file, but its not a vmdk and not a raw file. It has the vadp restore infos in it, thats seems to be my problem.
Question is, how can i remove this. bareos_vadp_dumper seems not an option, because volume 2 from 14 is missing, vadp_dumper breaks here, because it can not find the next cbt entry. As far as i understand the backup with vadp_dumper: bareos_vadp_dumper read the drive info, put it in json and mark it with a magic-header with the cbt i think is the same, magic-header, json with start and length, maybe magic-header, data. next magic-header, json, data and so on. But my problem is, after data is restored, it "jumps" to the next magic-header and want to read this, but because of missing volume, it should ignore the next and maybe more headers, but it didt´n. I looked in the sources from bareos_vadp_dumper, i think i understand it, but my programming skills are not "so good" to change that behavior. Am Montag, 15. April 2019 15:05:51 UTC+2 schrieb Erik Šolc: > Hi, > you can restore it to director. Run restore from bconsole and modify job, > change the Client and Where to restore, so number 5 and 10. > OK to run? (yes/mod/no): mod > Parameters to modify: > 1: Level > 2: Storage > 3: Job > 4: FileSet > 5: Restore Client > 6: Backup Format > 7: When > 8: Priority > 9: Bootstrap > 10: Where > 11: File Relocation > 12: Replace > 13: JobId > 14: Plugin Options > > So it will restore vmdk of the machine to the path you set in No. 10. > > Erik -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
