Salta al contenuto principale

Moved backup?

Thread needs solution

Hello,

 I just installed and was trying out ATI WD Edition, Version 19.0.33 which I'm assuming is the most recent that's available. I'd made a back of my C drive (Win OS) and backed it up to one of my internal storage SSD's. That all went well, no problems at all. I was quite impressed I must say after having come from a history of using Windows own system backup and imaging tools which more often than not was a problem as far as recoveries go. I'm feeling good about having made a switch. However, regarding the ATI backup I'd just made and saved, I'd tried to make a 2nd backup (same source) to a different SSD. That seemed to go okay as a .TIB file was found at the 2nd location however the first backup file was gone; the one that was on a original SSD. I'm wondering if ATI simply transferred the original backup over to the 2nd SSD even though I'm pretty sure I'd had it set up correctly; same 'source' with the 2nd location selected.  Does it sound as like I might not have had the settings correct or is this a normal operation?

0 Users found this helpful

Sounds like you left the default backup name in place for both backups and used the same destination for both tasks.  That would create an overwrite situation.  Best to use separate individual folders as destination for each backup task to eliminate this.  Using unique file names is advised as well.

Yeah, I'm thinking there's a backup setting that's not correct. Odd thing is, I tried again to back up from the same source to one of the two SSD's; the one which now did not have a back up on it. Well, that worked... cool. What's strange however is once again, the other backup SSD no longer had an image file. It's as if ATI's not allowing more than one backup image file to be stored locally on my PC even if it's on a separate drive. I was wondering what you meant by "default backup name"; maybe that is the issue and all I need to do is either rename the 'source' file (if that's even possible) or before attempting to create a separate backup, changing the existing 'destination' file name prior to backing up. I do know Windows' system imaging program is extremely fickle with regards to backup file and folder re-naming practices which still seems to be the case in Windows 10 as it's still included as a legacy (Windows 7) program.  Time to read some directions... thanks.

David, there are several reasons why you may be seeing the behaviour you have reported.  Enchantech mentioned about using the default task name, i.e. 'Entire PC' which would result in the backup files being given that name, i.e. Entire PC_full_b1_s1_v1.tib.

Another reason is the backup scheme option you have chosen, i.e. if you have chosen to use Single version only then only one backup file will be allowed for the backup task.  If you are using the same backup task each time, this would remove the older files regardless of having switched destination location.

I would suggest starting again and creating separate tasks for each action you want to perform where there will be a difference in either the source or destination locations.  When the backup is initially created and shows 'Entire PC' by default, you can delete that name and put in your own unique task name but this should be done before you click on the Backup now button, so that the new name is used for the backup files.

In risposta a di truwrikodrorow…

I wasn't selecting the same destination for the 2nd backup so apparently, that was not the problem.  However, renaming as you'd suggested worked and prevented the program from removing and overwriting the one that had previously been made and stored on a separate drive.

Thanks!

In risposta a di truwrikodrorow…

Steve, the issue was that ATI (WD Edition), Version 19.0.33 does not include a number of program options that are part of Acronis' own application; selecting anything other than single, full version being one. That being the case, any previous versions are overwritten and as I found out, will be removed from ANY local drive if that location differs from the destination that's currently set in the program. Renaming as you and Enchantech suggested did solve the problem. 

Thanks!

David, thank you for the feedback and information on the differences for the WD version - useful to know as I have no direct experience of that version of the product, only having used the full version over the years.