Restoring Files using Recovery Disk

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 4
Comments: 10

I have just started using a new PC running Windows 8 and am using True Image 2013 for backups. I have also just started using Seagate NAS drives for backups (rather than USB drives). I created a Recovery Disk for the new PC (though that was created before I installed the NAS drive, if that's relevant) and set about testing whether True Image can see the NAS drive on the network and backup/restore to/from it successfully.

True Image doesn't see the NAS drive as a NAS drive but it does see it as a network volume with a public directory (and therefore no need for credentials). True Image successfully creates backups on the NAS drive. I can also successfully restore individual files from those backups within the True Image application.

However, if I try to restore files from the NAS drive having booted the PC up from the Recovery Disk, it doesn't work. True Image sees the NAS drive OK - again as a public network volume. I go through the process of browsing for and selecting which archive to use, selecting where to restore the files to (back to my C: drive), selecting which files to restore and pressing 'Go'. The application reports that the operation was successful, however, when I reboot the machine normally and log in, the files that were supposed to have been restored aren't there.

This obviously isn't an urgent problem but I would rather know that everything works with the Recovery Disk before I tick this off my To Do list.

Any help gratefully received.

Thu, 10/10/2013 - 20:22
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 51
Comments: 3768

When using ATI with a network drive, use a UNC path to your NAS device for a backup destination, not a typical friendly "mapped" drive. e.g.
\\192.168.2.25\My Backups\

It should also be possible to use a UNC path that includes server name rather than IP, such as
\\server1\My Backups\

ATI will not automatically detect a NAS drive. Once you start typing the destination path (click "Browse", type in the "File name" field), you will be prompted for a username and password. You must use enter the username and password that has permissions to access the NAS share you are saving to.

Many users have issues with NAS, not because of True Image but because the router gets overloaded with data throughput and cannot keep a consistent enough connection with the NAS for True Image to image or restore. Certain models of router and known to suffer from this issue.

A user shared this:

From the "Destination drop down list in the backup dialog box" choose "Browse ..."
In the "Browse for Destination" dialog, enter the UNC path for your drive in the "File name:" input field.
If the "Authentication Settings" dialog does not pop up, click the blue arrow button to the right of the "File name:" input field so it does pop up,
Enter the login info for your share

Thu, 10/10/2013 - 20:42
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 4
Comments: 10

Thanks for that - glad I'm not alone in having issues with NAS drives. In fact I do access them using their ip addresses and have given them static addresses as well. I've not yet noticed an issue with performance. The PCs and the NAS drives are currently all plugged into the same Netgear Gigabit switch so I assume the router doesn't get involved (though I'm no networking expert).

Everything *seems* to work OK but it's just that the restored files aren't there when I go back into Windows. Could there be a permissioning issue? Does Windows 8 prevent the software on the Recovery Disk from writing to the C: drive?

Fri, 10/11/2013 - 10:43
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 4
Comments: 10

I've come back to this after a few weeks. In order to figure out whether it was the NAS disk causing the problem, I copied the True Image 2013 archive file to an external USB hard drive. I started the PC using the Acronis recovery disk and selected one file to restore from the archive and chose to place it in a directory on the PC's C: drive. When I pressed the button to do the restore, it said that the restore was successful. However, when I restarted the PC, the file that I chose to restore wasn't in the place I selected to restore it to.

Is there any sort of permissioning problem with Windows 8 that means Acronis isn't permitted to write to the C: drive? What else am I doing wrong? Is there a log file created when Acronis does a restore from the recovery disk that I can examine to find out whether anything went wrong during the restore?

I'm afraid that if I can't verify that the backup is usable for the purpose of restoring files, then Acronis is going to have to go and I'll find another backup product that I can be certain of.

Wed, 11/13/2013 - 15:17