Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Copied Image to OffsIte location cannot be read by Hasleo (V6.0.2.0)
#1
Hasleo Backup Suite Free V6.0.2.0

I have implemented, outside of Hasleo, a Copy Offsite tool for the image files to another remote PC, via Tailscale.

The local Image, located at \NAS_LOCAL\BACKUP\...  can be mounted well.

The problem is that at the remote PC, with the other Hasleo V6.0.2.0, it refuses to  mount (double click on image) with error “The image file is corrupted (0x1C69013400000005)”

The same error occurs when I try to mount (double click) on the original PC accessing  the copied image \\REMOTE_NODE\BACKUP_OFFSITE\image.DBI

All chain of Full and Differentials are completed.

The alternative of Hasleo menu Restore ‘Browse image to restore’  cannot be used either because it shows only local Dives and the Network drives of the Remote Offsite shares are not shown.
Also, locally on the Remote PC, with Hasleo manu Restore 'Browse image to restore' it access the copied image and lets you navigate and select files, but when pressing the Proceed button to restore same error "image corrupted" appears.

This makes the Offsite Backup third copy strategy useless if I cannot read the copied images.

Regards,
Alberto
Reply
#2
Hmm, I can't replicate your issues unfortunately.

I installed Tailscale on 2 of my VMs, a Win11 and a Win10 machine. Then I created a shared folder on my Win10 machine and took a backup from the Win11 machine with the remote destination. The backup itself finished without problems.

Then I deleted the backup job and tried to mount the remote backup. This also worked without problems.

I took a little video while switching between the machines. Did I do something differently?



The error code you posted ends with "5", that could mean ERROR_ACCESS_DENIED (0x5), but I'm not sure about this.
Are you sure you entered the correct credentials in HBS when trying to mount the image?

Another possibility: Did you compare your local copy of the backup to the remote one? Do some of the files differ, for example when comparing checksums? Could it have been corrupted during the copy with your third party tool?

Cheers,
al3x
Reply
#3
@Alberto,

The image file is not tied to any specific computer. As long as the image file is intact and accessible, it should be able to be mounted and restored normally on any computer.

@al3x's suggestion is completely correct. Please compare the checksums (e.g., SHA-256 or MD5) of the original image and the copied image to rule out the possibility that the file was corrupted during the copy process.

If the checksums match exactly, then we need to consider whether the issue is caused by ERROR_ACCESS_DENIED (0x5, Access Denied). In that case, please follow the steps below to save the log file and send it to [email protected] for our further analysis.
[Image: attachment.php?aid=872]

Best regards,
Reply
#4
The Get-FileHash  image -Algorithm SHA256  gives the same Hash for the original image and for the copy.

The copy tool is made by me with Powershell using robocopy for the copy.

Please find the ‘Save Log File’. The last I did now was from Restore Menu ‘Browse Image to Restore’  and select the last copied Differential from the disk C: from the other PC.  It has there the complete path from Full to Differentials.  It then shows correctly the partions on the disk and I select the NTFS partition. Then correctly appears a navigation window, like explorer, to select the files to restore.  I can navigate correctly and all is apparently there. Select some files and when pressing Proceed the error of image corrupted appears.

Rgds,
Alberto


Attached Files
.zip   backup-suite-log-20261115111703.zip (Size: 647.52 KB / Downloads: 3)
Reply
#5
I think I’ve found the reason for the error.

In my Copy_Offsite tool, I’ve set a MaxSize for the Destination remote folder and, when the total size is greater, I delete the remote copied oldest file and check again until the total size is under MaxSize.

This way, when a Full image is deleted, its subsequent differentials remain until future checks delete them when total size is again greater than MaxSize.

When launching a Check Image from Tools for the last copied image file, the presence of those‘orphan differentials generate the message:
“The backup version on which backup version xx depends has been deleted, lost or corrupted.”

It looks that when mounting the image a quick check is done before, and the check of that orphan differentials generates the overall message ‘image is corrupted’.

If I delete, or just rename those orphans to *.DBI-Orphan, then it works and I can mount the Copied images from another PC.

Great! Another new thing learned from HBS.

Best Regards,
Alberto
Reply
#6
@Alberto, glad to hear you've figured out the problem.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)