Another verification failure this morning with error code 23.  No mrbak file was written to the storage (repository) device or shows under Existing Backup tab.   I have submitted the requested information to the Support staff.

I am running a manual backup and verification of the disk now.  I expect they will complete successfully.

How large is this f&f data set you're backing up?  I was thinking if it was easy enough, you might copy the XML to a dummy copy for editing and remove, say, half the data set.  Then try again.  See if you get the same issue.    I would be working trying to isolate whatever factor might be triggering it.  Like a particular file/folder that may be being backed up.  Or a potential backup file size issue.  Plus, if you say worked down the backup file size to something small enough for sending that still returns the error, you could send that data set to tech support, if you're inclined/don't mind them seeing the contents.

The manual backup I just ran failed verification at 4% (error code 121). 

I think I'll edit the definition file to exclude automatic verification and run it again.  If the backup is successful, I'll attempt to verify it manually.

+x

 

dbminter - 19 September 2023 1:15 PM

How large is this f&f data set you're backing up?  I was thinking if it was easy enough, you might copy the XML to a dummy copy for editing and remove, say, half the data set.  Then try again.  See if you get the same issue.    I would be working trying to isolate whatever factor might be triggering it.  Like a particular file/folder that may be being backed up.  Or a potential backup file size issue.  Plus, if you say worked down the backup file size to something small enough for sending that still returns the error, you could send that data set to tech support, if you're inclined/don't mind them seeing the contents.

Data size is about 80GB

Are the failure verification points roughly the same?  Always at 4% or at others?


I've backed up well more than 80 GB before in F&F backups.  In fact, my current monthly backup of changed files in temporary locations exceeds 300 GB right now for the year.  But, that backup set uses file splitting so I can't say if it's a potential F&F file size issue.

I edited the F&F definition file to exclude auto verify.  I ran the backup manually and it completed successfully.  Afterwards, I manually verified the mrbak. file.  It verified correctly although it dis hesitate a bit at the 4% point).  This file is shown in Existing Backups tab as well as on my storage (repository) device.

Just to clarify, I am having no issues with image backups (mrimg.) using the same USB port, cable, and storage device as the F&F backups.  All images are verifying correctly.  The only issue is with F&F verification.

+x

 

dbminter - 19 September 2023 1:56 PM

Are the failure verification points roughly the same?  Always at 4% or at others?


I've backed up well more than 80 GB before in F&F backups.  In fact, my current monthly backup of changed files in temporary locations exceeds 300 GB right now for the year.  But, that backup set uses file splitting so I can't say if it's a potential F&F file size issue.

2 failures at 4%. 1 failure  16%, 1 failure  64%

Interesting progression rates there.  2 4%'s then 16%, which is 4 squared, and then 64% which is 4 x 16.


Your further testing seems to indicate the issue is during the auto verification phase.  If you exclude auto verify, the backup completes successfully.  If you manually Verify that completed backup, the manual Verify completes.


At this point, it's probably best left up to the support people to look into.

+x

 

dbminter - 19 September 2023 4:30 PM

Interesting progression rates there.  2 4%'s then 16%, which is 4 squared, and then 64% which is 4 x 16.


Your further testing seems to indicate the issue is during the auto verification phase.  If you exclude auto verify, the backup completes successfully.  If you manually Verify that completed backup, the manual Verify completes.


At this point, it's probably best left up to the support people to look into.

Agreed.  I'll post back when I hear something

I believe the storage disk is failing.  I ran some other diagnostic tests and there were several read errors as well as semaphore timeouts.  I've disconnected the disk and have attached another external USB HD.  Backups, images, and verifications are completing successfully to this new destination.

Thanks to all who helped me with this.