|
Hello,
You can try adding the -p option to the command line of the Storage daemon. The SD will then try to continue after errors, but the error is serious enough that it is unlikely to work, the SD will at some point probably seg fault when it read bad data. Another approach would be to attempt to restore an older backup, and if that is successful restore one by one each job that ran after the backup that worked. Then you can examine in detail the restore that failed, and see if you can find older backups of the files. Also, if you use the -p option on the Job that fails, you may be able to get something. A more radical approach would be to force the Director to save the bsr, then you modify it and remove either just the references to bad blocks or all records for Volume-Diario-0009 and try the restore. Obviously this will not get back everything, but maybe if you are lucky, it will get back what you need. You can then use the catalog to find out what files are on the Volume and see if they were previously saved either elsewhere on the same volume or preferably on a different Volume. This will be a good deal of work, but if you dig into it and understand pretty much what you are doing, you will be surprised what you can recover. Best regards, Kern On 03/09/2017 08:44 PM, Wanderlei Huttel wrote:
|
------------------------------------------------------------------------------ Announcing the Oxford Dictionaries API! The API offers world-renowned dictionary content that is easy and intuitive to access. Sign up for an account today to start using our lexical data to power your apps and projects. Get started today and enter our developer competition. http://sdm.link/oxford
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
