Copied Image to OffsIte location cannot be read by Hasleo (V6.0.2.0)

[Alberto]

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

[al3x]

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