Backing up to a NAS

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Posts: 7
Comments: 19

Hi,

New to this product and currently trying it on my WD MyBookLive 2TB NAS drive after dreadful, dreadul problems with WD's own Smartware package.

As a first attempt I selected to perform a single backup to a newly created private share on the NAS drive (MyBookLive>private_share). TI2013 asked me to enter a user name and password which I did and off we went and completed a full backup in a few hours.

But now I cannot access the private_share. It is as though TI2013 has kept control or ownership of the private_share. I might perhaps understand this if I had scheduled a backup to occur automatically at some future point - but I haven't, it was a one off backup.

What does the team think - has TI2013 kept ownership of the private_share? If it has, how might I release it so that other PC users on my home network might be able to access the private_share and it's contents.

Nice looking product though, good first impressions although I am slightly nervous of recent postings here of users trying to recover from images on their NAS drives.

Mon, 02/11/2013 - 23:17
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Hero
Posts: 87
Comments: 9259
mvp

Can you explain what you mean by "I cannot access the private_share"? If you restart your computer, does the problem go away?

Note: you definitely want to test restoring from the NAS. Remember that restoring an image to a partition needs to be tested from the Acronis recovery CD (ie do not launch the restore process from within Windows). To test this, boot on the recovery CD, setup the NAS connection, then restore a couple of files and folders from your image.

Tue, 02/12/2013 - 02:31
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
Forum Member
Posts: 7
Comments: 19

Many thnaks for your reply. By saying 'I cannot access the private share' I literally did mean that. Before launching TI2013 I could access the private share by opening explorer, clicking on the share, enetring the user name and password and hey presto I was 'in'. But later I launched TI2013, I set it up to backup to that private share. In order to do that TI propted me for the user name and password - when I did this TI set off nicely and did my backup.

After performing the backup I closed down TI, opened up explorer and went to access the private share to see what TI had deposited there. But I could not get back into the share. I was prompted for the username, password etc but it simply would not let me in to the share. I thought maybe TI had acquired ownership of the share (reasonable) and had not let go because the backup plan required TI to update the backup daily - in order to do that it would need access to the share, and if I wasn't present to enter the share access details then it might not be able to perform the subsequent backups.

However, when I powered up the laptop this morning I could access the private share in the normal way via explorer!! I have not been impressed with the WDMyBookLive Nas drive - it seems very temperamental and somewhat flakey so maybe that was the problem.

However it does follow on to another issue (I have to remember I am new to the TI product and things that I may think are issues are more than likely to be inexperience on my part) but I would like to like to pick the forums brains - if you can help me out please.

The first backup I did last night was performed at 22.27. I have set the backup plan to be daily>every hour. The laptop on which TI is installed was switched off overnight. I powered up this morning and noted TI was perfoming a backup almost straightaway (time= 0905). I had assumed it would perform another backup at 1005. But it didn't do so. I clicked on the TI2013 icon on the desktop to have a looksee, Window7 aksed me if I was happy for TI to make changes to my computer. I clicked 'yes' and almost straightaway TI started to perform the next backup (time = 1030).

I left the house, leaving the laptop powered up and returned at around 1145. I had expected TI to have performed another backup at 1130. But it hadn't. Again I clicked on the desktop TI2013 desktop icon, said 'yes' when W7 asked if I was happy for TI to make changes to the PC and almost immediately TI started to perform the next backup (time = 1145).

So, for whatever reason TI2013 is not routinely performing a backup. I had assumed this would be an entirely background task with no intervention required by me. So I am confused. Grateful for any advice.

Tue, 02/12/2013 - 12:12
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Posts: 7
Comments: 19

Well this is all very strange.

Given the above timings I had expected TI maybe to have performed backup at 1245 - but it hadn't. I left the laptop powered up and perhaps expected a backup at 1345 - but it didn't do anything then either. I tried the same 'trick' as per my previous post (opening up TI from the desktop item etc) but this time it never attempted any sort of backup.

I have looked at Task manager and can see two Acronis processes:
TibmounterMonitor.exe *32 described as: Acronis TIB monitor
TruesImageMonitor.exe *32 described as Acronis True Image Monitor

I am absolutely no expert on all this, but it does look as though there are a couple of Acronis background tasks running -that I might maybe have expected to have been part of some sort of utility to automatically set these backups off.

As it currently appears I have 5 Acronis backups taken at somewhat random times today.

I get no error messages at all.

Tue, 02/12/2013 - 18:10