TIH 2011 - cannot find source partition with path...
See attached. I get this frequently on my laptop. Last time I just deleted my existing full/incrementals manually. Then when I started the backup it completed.
Today, I just edited the job (making no changes) and clicked on save. When I ran it, it warned me that the user cancelled the verification and then began to run. Looking at the destination afterwards, it created an incremental to go along with the full that was created back in June.
Is something changing the signatures on my drives and confusing TIH?
| Attachment | Size |
|---|---|
| tih_failure.png | 21.71 KB |
- Log in to post comments
I assume you mean different disks as 'targets' for the backup. Only one of those. It's an external drive connected to the eSata port.
I have no good evidence, but it's always seemed to crop up after I'd introduced new hardware, such as a new external drive.
However, I always make sure that my eSata backup drive maintains the same driver letter. Without that the backup would refuse to run anyway - or try to backup to what ever was drive J: on that day.
I wish TIH could become smart like GoodSync and SecondCopy - recognize the target by it's volume name. Then when I execute a backup, it can automatically find the destination.
Daily backups to devices fixed to a computer or to a device located in the same structure as the computer are of no use after an F5 comes through. TIH needs to be more friendly to off-site backup scenarios. Note, I don't have the bandwidth or time for cloud backups nor would I trust them. There's no Federal Data Insurance Corporation that can give me my data back should their could burst :-)
Lastly, what "local" partition is being referred to in that error message? Source or destination? Why not just use drive letters to identify Source and Destination?
- Log in to post comments
Your comments are well founded. I am aware of some users (that use multiple externals ) that take the time to change the serials on their external disks just to make sure all have the same signature.
For my own use, I restrict one task to one external but use multiple tasks and multiple externals.
- Log in to post comments