Did the backup job on 03-Oct fill the disk? Did you check for syslog messages
for that date too?
Also, did you include the complete output below from the backup jobid 12068?
I would expect more information to be printed between 03-Oct 23:06 and 03-Oct
23:19 about the volumes being used and the re
Hello Marko,
>> *21-Oct 05:46 backup-sd JobId 12612: Warning: block.c:682 [SE0208] Volume
>> data
>> error at 0:0! Short block of 42967 bytes on device "backup-device-data1"
>> (/data1) discarded. **
>> **21-Oct 05:46 backup-sd JobId 12612: Error: read_records.c:160 block.c:682
>> [SE0208] Volume
Just in time...
>>> *21-Oct 05:46 backup-sd JobId 12612: Warning: block.c:682 [SE0208] Volume
>>> data
>>> error at 0:0! Short block of 42967 bytes on device "backup-device-data1"
>>> (/data1) discarded. **
>>> **21-Oct 05:46 backup-sd JobId 12612: Error: read_records.c:160 block.c:682
>>> [SE020
Hi,
the backup job on 03-Oct definetly filled the volume 10, but not the
whole disk, it still has some free space.
*list volume
Automatically selected Catalog: MyCatalog
Using Catalog "MyCatalog"
Pool: Default
+-++---+-+-+--+-
Ah, so the short block is part of jobid 12065 and therefore the copy of jobid
12068 is very likely to be complete.
The "[SI0202] End of Volume" message means that write() wrote less that
expected. The only reasons I can think of are disk space shortage, I/O error,
some other process-specific limi
