Backup storage pool job - unreadable files

[PeterOakes]

Hi All,

During one of my back up storage pool jobs i am getting a message saying "unreadable files:108" see photo attached.it is the backup between the Diskpool directory and the copypool directory. what is the best way to resolve this?

let me know if you require further information.

Thanks

 

[LED888]

Is the data being deduped? If so, client side or server side dedupe or both?

Check the actlog and see if there are any error message(s).

Query Actlog BEGINDATE=MM/DD/YYYY BEGINTIME=HH:MM ENDTIME=HH:MM

Good Luck,
Sias

 

[PeterOakes]

Is the data being deduped? If so, client side or server side dedupe or both?

Check the actlog and see if there are any error message(s).

Query Actlog BEGINDATE=MM/DD/YYYY BEGINTIME=HH:MM ENDTIME=HH:MM

Good Luck,
Sias

Hi LED888,

Sorry only saw your response now. We only dedup on the server side. I get the following errors is the ACT LOG:


18-02-2021 05:08:10 ANR1331E Invalid frame detected. Expected magic 53454652
sequence number 1 server id 0 segment id
13199286663. (SESSION: 47792, PROCESS: 1464)
18-02-2021 05:08:10 ANR1330E The server has detected possible corruption in
an object that is being restored or moved. The actual
values for the incorrect frame are: magic 0 hdr
version 0 hdr length 0 sequence number 0
data length 0 server ID 0 segment ID
0 crc 0. (SESSION: 47792, PROCESS: 1464)
18-02-2021 05:08:10 ANR1331E Invalid frame detected. Expected magic 53454652
sequence number 1 server id 0 segment id
13199286666. (SESSION: 47792, PROCESS: 1464)
18-02-2021 05:08:10 ANR1330E The server has detected possible corruption in
an object that is being restored or moved. The actual
values for the incorrect frame are: magic 0 hdr
version 0 hdr length 0 sequence number 0
data length 0 server ID 0 segment ID
0 crc 0. (SESSION: 47792, PROCESS: 1464)
18-02-2021 05:08:10 ANR1331E Invalid frame detected. Expected magic 53454652
sequence number 1 server id 0 segment id
13199286669. (SESSION: 47792, PROCESS: 1464)

 

[LED888]

Looks like there may be some corrupted data.
Do suggest that we run audit volume ..fix=yes . If there are damage data, the server will attempt to fix it.
If the data can not be fix, it will be marked damage and the file(s) will be backed up at the next schedule backup.

Good Luck,
Sias