path not found - 0x02260085c000003a

[JayDee]

Ran an existing backup (incremental)
and got the above error

My work-around:
 - delete the existing task
 - import the task from the existing backups

Run the imported task... that worked

I don't know if the number of incremental backups is significant
There were 64  so wondering if  i reached a binary limit condition.

JD

[admin]

Ran an existing backup (incremental)
and got the above error

My work-around:
 - delete the existing task
 - import the task from the existing backups

Run the imported task... that worked

I don't know if the number of incremental backups is significant
There were 64  so wondering if  i reached a binary limit condition.

JD

Have you changed the drive where the image files were saved, e.g. the backup files were copied to another drive?

[JayDee]

No... nothing was changed
I use this particular incremental backup task frequently throughout the day as I work
on a software project. The target is the local D: drive.

I guess something got changed in the backup task and by importing
the task everything was reset.

Of course, I keep a daily "off computer" backups as well

JD

[admin]

No... nothing was changed
I use this particular incremental backup task frequently throughout the day as I work
on a software project. The target is the local D: drive.

I guess something got changed in the backup task and by importing
the task everything was reset.

Of course, I keep a daily "off computer" backups as well

JD

This is so weird, this problem shouldn't happen without changing anything. Note that Hasleo Backup Suite uses the unique partition identifier instead of the drive letter to identify a driver, so even if the drive letter does not change after the destination drive is replaced, Hasleo Backup Suite will report the error "The system cannot find the path specified.".

[JayDee]

First and only time it's happened (for me at least)
I will certainly let you know if I ever get a repeat.

For future reference, I'll document the current
identifier so that I can verify whether it has
changed (if the error occurs).

Other than that, everything is working great .

JD

[admin]

First and only time it's happened (for me at least)
I will certainly let you know if I ever get a repeat.

For future reference, I'll document the current
identifier so that I can verify whether it has
changed (if the error occurs).

Other than that, everything is working great .

JD

Okay, thank you very much.

[trustycaftan]

Ran an existing backup (incremental)
and got the above error
My work-around:
 - delete the existing task
 - import the task from the existing backups
Run the imported task... that worked
I don't know if the number of incremental backups is significant
There were 64  so wondering if  i reached a binary limit condition.
JD

Have you changed the drive where the image files were saved, e.g. the backup files were copied to another drive?

Is there a way to organize old backup versions? (Because I often delete old backups that are not needed after confirming their integrity)

[admin]

Have you changed the drive where the image files were saved, e.g. the backup files were copied to another drive?

Is there a way to organize old backup versions? (Because I often delete old backups that are not needed after confirming their integrity)

I don't quite understand what you mean by "organize old backup versions", can you explain?