Re: [Bacula-users] Simple disk storage devices migrations/backups

2020-03-27 Thread Pierre Bernhardt
Am 27.03.20 um 21:26 schrieb Pierre Bernhardt:
> Am 27.03.20 um 18:26 schrieb Martin Simmons:

>>> Any idea how I can extract the single data für fileindex 932145 from the 
>>> disks for comparing?
>>> If the short block is only repeated as whole block on the next disk the 
>>> problem could be fixed
>>> by modify the database so the short block will not be read or by truncating 
>>> at short block on
>>> the DISK016 (?)
>> You can find the filename for fileindex 932145 by running bscan -r -vv and
>> then do a restore for that filename.

> By the way the restore (with bconsole?) will be work without getting a 
> problem? I will
> try to do it.

27-Mar 21:27 backup-sd JobId 47756: Ready to read from volume "DISK016" on File 
device "DiskStorage2" (/media/baculadisk2).
27-Mar 21:27 backup-sd JobId 47756: Forward spacing Volume "DISK016" to 
addr=971937834340
27-Mar 21:28 backup-sd JobId 47756: Error: block.c:682 [SE0208] Volume data 
error at 0:0! Short block of 57010 bytes on device "DiskStorage2" 
(/media/baculadisk2) discarded.
27-Mar 21:28 backup-sd JobId 47756: Error: read_records.c:160 block.c:682 
[SE0208] Volume data error at 0:0! Short block of 57010 bytes on device 
"DiskStorage2" (/media/baculadisk2) discarded.
27-Mar 21:28 backup-sd JobId 47756: End of Volume "DISK016" at 
addr=972406571008 on device "DiskStorage2" (/media/baculadisk2).
27-Mar 21:28 backup-sd JobId 47756: Ready to read from volume "DISK017" on File 
device "DiskStorage2" (/media/baculadisk2).
27-Mar 21:28 backup-sd JobId 47756: Forward spacing Volume "DISK017" to addr=213
27-Mar 21:28 backup-sd JobId 47756: End of Volume "DISK017" at addr=645332 on 
device "DiskStorage2" (/media/baculadisk2).
27-Mar 21:28 backup-sd JobId 47756: Elapsed time=00:00:15, Transfer rate=134.3 
K Bytes/second
27-Mar 21:28 backup-dir JobId 47756: Bacula backup-dir 9.4.2 (04Feb19):
  Build OS:   x86_64-pc-linux-gnu debian buster/sid
  JobId:  47756
  Job:RestoreFiles.2020-03-27_21.27.41_46
  Restore Client: nihilnihil-fd
  Where:  /tmp/restore
  Replace:Always
  Start time: 27-Mar-2020 21:27:44
  End time:   27-Mar-2020 21:28:07
  Elapsed time:   23 secs
  Files Expected: 1
  Files Restored: 1
  Bytes Restored: 2,122,031 (2.122 MB)
  Rate:   92.3 KB/s
  FD Errors:  0
  FD termination status:  OK
  SD termination status:  OK
  Termination:Restore OK -- with errors   27-Mar 21:28 backup-dir 
JobId 47756: Begin pruning Jobs older than 99 years .
27-Mar 21:28 backup-dir JobId 47756: No Jobs found to prune.
27-Mar 21:28 backup-dir JobId 47756: Begin pruning Files.
27-Mar 21:28 backup-dir JobId 47756: No Files found to prune.
27-Mar 21:28 backup-dir JobId 47756: End auto prune.

Looks like restoring has been worked although only with the shot block notice 
error message.

Now use a newer backup from tape to restore the same file and compare them with 
sha256sum.
Content and meta data are looks like correct after restore.

So my problem is only, because of failed migration because of short block 
notice, the
migrated database entries will not transfered after the migration back from 
disk to tape
has been proceed.

Is there a way so I can finish the migration maybe by a workaround?

Cheers,
Pierre



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Simple disk storage devices migrations/backups

2020-03-27 Thread Pierre Bernhardt
Am 27.03.20 um 18:26 schrieb Martin Simmons:
Hi,

>> Any idea how I can extract the single data für fileindex 932145 from the 
>> disks for comparing?
>> If the short block is only repeated as whole block on the next disk the 
>> problem could be fixed
>> by modify the database so the short block will not be read or by truncating 
>> at short block on
>> the DISK016 (?)
> You can find the filename for fileindex 932145 by running bscan -r -vv and
> then do a restore for that filename.
I found it on database with

select client.name, job.jobid, job.level, path.path, filename.name, file.lstat 
from file, filename, path, job, client where 
file.filenameid=filename.filenameid and file.pathid=path.pathid and 
file.jobid=job.jobid and job.clientid=client.clientid and job.jobid=47704 and 
file.fileindex=932145 order by job.endtime desc;

(Sorry for the long line ;-)

By the way the restore (with bconsole?) will be work without getting a problem? 
I will
try to do it.

Cheers,
Pierre



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Simple disk storage devices migrations/backups

2020-03-27 Thread Martin Simmons
> On Thu, 26 Mar 2020 23:31:43 +0100, Pierre Bernhardt said:
> 
> Am 26.03.20 um 16:48 schrieb Martin Simmons:
> > Looks like a bug to me, but a possible workaround is to limit the size of 
> > your
> Me2. If the short block is correctly identified at writing it should be 
> repeated
> or should be finished on the new disk. In both cases the data on the disks 
> should
> be ok. Only the reading has maybe than a problem.
> But if the tail data of the short block is lost, the data on the disks should 
> be
> incomplete

I think the short block should be repeated on the new disk.

> 21-Mar 20:23 backup-dir JobId 47704: Using Volume "DISK016" from 'Scratch' 
> pool.
> 21-Mar 20:23 backup-dir JobId 47704: Using Device "DiskStorage2" to write.
> 21-Mar 20:23 backup-sd JobId 47704: Wrote label to prelabeled Volume 
> "DISK016" on File device "DiskStorage2" (/media/baculadisk2)
> 22-Mar 07:47 backup-sd JobId 47704: [SI0201] Out of freespace caused End of 
> Volume "DISK016" at 972406513998 on device "DiskStorage2" 
> (/media/baculadisk2). Write of 64512 bytes got 57010.
> 22-Mar 07:47 backup-sd JobId 47704: End of medium on Volume "DISK016" 
> Bytes=972,406,513,998 Blocks=15,073,266 at 22-Mar-2020 07:47.
> 22-Mar 07:47 backup-sd JobId 47704:

OK, this look as expected.

> By the way I created a bscan. Here the lines about the disk change:
> 
> 
> bscan: bscan.c:442-0 Record: SessId=42 SessTim=1584646035 FileIndex=932145 
> Stream=23 len=62656
> bscan: bscan.c:442-0 Record: SessId=42 SessTim=1584646035 FileIndex=932145 
> Stream=23 len=62336
> bscan: bscan.c:442-0 Record: SessId=42 SessTim=1584646035 FileIndex=932145 
> Stream=23 len=61632
> bscan: bscan.c:442-0 Record: SessId=42 SessTim=1584646035 FileIndex=932145 
> Stream=23 len=62528
> bscan: bscan.c:442-0 Record: SessId=42 SessTim=1584646035 FileIndex=932145 
> Stream=23 len=62672
> 25-Mar 23:27 bscan JobId 0: Error: block.c:682 [SE0208] Volume data error at 
> 0:0! Short block of 57010 bytes on device "FileTmpVol" (/media/baculadisk2) 
> discarded.
> ...
> 
> Any idea how I can extract the single data für fileindex 932145 from the 
> disks for comparing?
> If the short block is only repeated as whole block on the next disk the 
> problem could be fixed
> by modify the database so the short block will not be read or by truncating 
> at short block on
> the DISK016 (?)

You can find the filename for fileindex 932145 by running bscan -r -vv and
then do a restore for that filename.

__Martin


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users