Direkt zum Inhalt

Problems backing up to NAS

Thread needs solution

Problems backing up to NAS. Have an HP laptop that I have been able to use TIH to backup to my NAS just fine in the past. Via WiFi and wireless. The past couple of weeks it keeps failing. At times it looks complete and I can open it from TIH on my desktop and laptop. But when I try to validate it through TIH on my laptop or desktop it says it's corrupt.

I have deleted the backup listed and rebuilt it but this problem keeps coming back so it's not working. Any ideas?

Also, when I restored a backup about 1.5 months ago it restored it incorrectly and the drive partitions are not laid out the way they were in the backup.

0 Users found this helpful
SBMongoos wrote:

Problems backing up to NAS. Have an HP laptop that I have been able to use TIH to backup to my NAS just fine in the past. Via WiFi and wireless. The past couple of weeks it keeps failing. At times it looks complete and I can open it from TIH on my desktop and laptop. But when I try to validate it through TIH on my laptop or desktop it says it's corrupt.

I have deleted the backup listed and rebuilt it but this problem keeps coming back so it's not working. Any ideas?

Also, when I restored a backup about 1.5 months ago it restored it incorrectly and the drive partitions are not laid out the way they were in the backup.

Resuscitating this old "non" thread. This still occurs. I can get to the NAS with no issues at all with the laptop. Why does TIH struggle with this? Now using TIH 2013 with the same issue. Disregard the third paragraph as I'm still working this issue out but in another thread.

If there is a problem creating a good backup, my first recommendation would be to check the source disk for disk errors.

To further verify whether the backups are good or have issues, boot from the TI Recover CD and do a validation when booted from the CD.

Please post the exact path you are using to direct the backups to the NAS.
Have you reviewed the Acronis KB article about backups to a NAS. Another possibility is the wireless signal is weaker than before. You could try a direct connect as see if you have the same issues.

The most frequent cause of backup being restored to the wrong partition sequence is a user error as the program relies on the user to make the correct choices for their own specific system.

GroverH wrote:

If there is a problem creating a good backup, my first recommendation would be to check the source disk for disk errors.

I already am able to backup to the NAS from my desktop. I will admit that I have not done so directly in a while. What I currently do is backup using TIH 2013 on my desktop to another internal disc. Then at next bootup MS Synctoy syncs backups between the secondary internal disk and the NAS. I've been doing this for some time without issue for redundancy.

As for the path to the NAS Windows Explorer sees it as: W:\HP Laptop. Now, I also try to choose NAS Connections ... but it always switches to FTP for some reason even though I've chosen NAS. The path in TIH looks like "ftp://mongoose-media:21/Data_Backups/HP%20Laptop//\". I use the browse option to select the location and folder. Odd to me but this is what it is adding. At least I don't understand the //\ at the end. Sometimes it loads "\\192.168.0.1\Data_Backups\Hp Laptop\". But the backups always fail as it says "open the backup location failed". I can sit and watch this make it's five attempts to do so. So I can use browse to navigate to the location for the already existing backups are and save it but then it "open the backup location failed".

Edit: interesting. I did a validation in Windows Explorer from my desktop to my NAS to a smaller backup file and it says it's corrupt. I don't know as of yet but it appears the validation of the same file on my secondary internal disc is going to validate fine. I'm not sure how to check this Seagate Blackarmor NAS 220 for errors. Seems I can only runs S.M.A.R.T Short Drive Test from the GUI on the NAS which it passed not too long ago.

I'm considering doing a factory reset on the NAS. However, the backups on drive D: on my desktop are validating and I'm now trying to backup to this drive (as it's shared) from my HP laptop and I having the exact same issue. "Attempt 3/5 to open backup location failed. Time between atempts 30 sec.". Clearly this option is failing as well. I'm not confident it's the NAS as I have validated backups on the NAS in the past.

Im' noit sure your problem is NAS related. The check for disk errors is the to be done on the computer being backed up which is failing validation. I don't believe a factory reset on the NAS will solve your problem

The path does not appear correct and could be the cause of the files not found error or backup location not found.

I am unsure how you are getting this error. When the task is first created, part of the task creation is to browse to the storage folder (on the NAS) and assign a name to the *.tib file to be created. Once that is done, everything else is automatic without you doing any browsing.

On the NAS, each or your computers should have its own individual backup task pointing to its own indiviual path to the NAS, plus each task should point to its own storage folder. The path used for followup backups should be the same path as used when task created without any changes.

Examine some of the log files on both backups which were successful and also examine the ones that failed.
These could well give you information on what/where this is happening.

Are all your backups done via FTP? The 198...... address sounds like a router connection.

Added:
Here is a link on FTP:
http://kb.acronis.com/content/34224

NAS info
http://kb.acronis.com/content/23567

Perhaps some other users that have NAS could respond to this posting.
Have you consider getting help from Acronis on a paying basis.
I believe ther one time help charge is something like $9.99 per incident.

The \ at the end of the path seems incorrect, I recall this being a problem in 2012 which was fixed, but I'm unsure if this would cause the problem you are seeing.

Are you able to connect the NAS temporarily via cable to the laptop and see if the problem still occurs? I first thought like Grover that the WiFi could be the problem.

Was it build 5551 that worked OK or an earlier version of True Image?

Have you tried using the recovery media and see if the same problem occurs?

If you have Wireshark installed this might be useful in seeing of there is a traffic problem.

Currently I'm taking some steps to clean up to deal with these results. For the most part I think what I'm doing is unnecessary but never hurts to do every so often anyway. I moved my data off my NAS and reset it back to factory and am in the process of moving it back. This takes a while. I've also setup a USB drive to install a clean version of Win 7 Home Premium 64bit. The laptop came with a bunch of crap from Hewlett Packard some of which I removed. I know at one point there was a driver (for the accelerometer) that caused a BSOD with TIH so I installed an earlier version to fix the issue since Acronis tested and showed it was a problem.

I can access the files on the NAS just fine with this laptop via LAN or WiFi. Stream movies, etc. It was always very random whether a backup could complete to the NAS or not. Got worse over time. I was always suprised to see if I was away from home with the laptop that it took a long time for TIH to figure out it was not connected to the NAS and it always seemed problems would start after this. I would go through the process of deleting backups, schedules, etc and starting over and that would work for a while and then this issue would start all over again (doing so per Acronis). I've been doing WiFi backups to external drives and NAS for years. TIH just seems to have some problem from time to time. Rare there's an issue on my custom built desktop but the laptop is another story. The other day I decided to delete most of the laptop backups from the NAS and uninstall TIH 2103 and use their cleanup utility. Now I'm getting a BSOD having completed this only. Find a camera shot of this error attached. Just tired of all the issues so I'm thinking about wiping the drive and doing an install with a clean copy of Win 7 HP 64bit. I only have the restore partition but it has all the garbage that HP put on it as well. Plus, there are four partitions with this laptop.

BSOD error: attached

I bought a new Asus RT-AC66R WiFi router about two months ago and have been using all Cat6 cables for some time now.

Anhang Größe
144361-110281.jpg 3.45 MB

That error code relates to a driver, I'll research to see what driver that error code relates to.

I'm not sure on how different the networking action is between Home and Pro/Ultimate for W7, but there are some differences. I'm not convinced though that your problem relates to that. What would be worth checking is your RAM condition as TI pushes RAM to its limits. Have you tried running Memtestx86 for at least 4 hours and preferably overnight on your system?

Could I suppose. I upgraded the laptop's RAM back when I got to 8Gb of performance Samsung RAM.

Having similar issues in Windows 8.1. Cannot validate backups on my NAS. I can open them and drill down into folders and even copy files to the OS but cannot validate. Happening on Desktop with Win 7 Pro 64bit, Win 8.1 Pro 64bit and Win 7 Home Premium 64bit on laptop.

What is the make, model and firmware version of your NAS?

Is there any difference between using TI in Windows or from the recovery media?

Colin B wrote:

What is the make, model and firmware version of your NAS?

Is there any difference between using TI in Windows or from the recovery media?

Seagate BlackArmor NAS 220 using f/w 2000.1331.

My concern is backing up to the NAS and TIH being able to load its own image or find it. I can use TIH to browse to the file but the validations seem to be failing. So far I have been able to restore from the NAS from optical media but last time was this laptop about a month ago now. Also this is the same laptop where the partitions somehow got switched around on a restore and I hadn't done anything different in my backup process and doing a restore I'm sure I was choosing the full disk to restore.

If the image is copied back to a PC or just the NAS connected by USB does the image file become able to be validated?

Are you able to mount the image file?

So, the recovery media does allow you to see an drestore the image file? This is important as it si the best method for OS disk restoring.

As you are able to restore an image from the NAS, that rules out my next thought which was, "does the NAS encrypt the contents", apparently not.

Did you run the memory checker? All TI does when validating is to recalculate and check against the CRC checksums that are inserted into the image at various points. I'm still wondering if somehow the validation is causing either the PC or the NAS buffer to fill up and one or the other just gives up.

Colin: I'll do my best to address each of your points.

If the image is copied back to a PC or just the NAS connected by USB does the image file become able to be validated? Yes, I copied a backup back to the laptop and it verifies without issue. I also just completed a clean install of Win 7 on the laptop and it backed up to the NAS fine but failed validation. I notice that these failed validations happen almost immediately. There is no long pause it's a brief period and then I get the error I mentioned previously. Also, when I boot from TIH bootable media I can validate this same backup on the NAS just fine. Therefore I believe I could recover it as well via the media (and have done so in the past).

Are you able to mount the image file? I assume you mean do a recovery? If I navigate to the NAS where the backup is I can access the file easily. If I right click and choose Recover and window pops up with Acronis Recovery tab selected that has the name of the backup file and in the box just below it says "There are no previous versions". There is only one backup as I just completed it. It should have run the restore. I will admit I did some folder clean up and move things around a bit but no idea why this would impact a Recover.

As you are able to restore an image from the NAS, that rules out my next thought which was, "does the NAS encrypt the contents", apparently not? The Seagate BlackArmor NAS 220 is able to encrypt but I do not have this setup.

Did you run the memory checker? No I have not. My gut tells me this is not the issue so I have not done this. Another reason being when I copy the TIH backup file back to the laptop it Validates without issue and I'm seeing this happen on my desktop PC as well which runs the same version of TIH.

***Edit: here's something I find interesting. After having reset the NAS and rebuilt it, wiped the drive on the laptop and did a clean install of Win7 (not the HP factory recovery) I was able to do the things I listed above. However, I just now witnessed that is it not backing up and shutdown/restart as scheduled. So I chose to manually run the backup and it's doing what it was doing previously which is "attempt 2/5 to open backup location failed. Time between attempts 30 sec.". Of course it goes 5/5 and fails and then finally throws an error "Error occurred while opening the file. Please insert the last media of the archive and click Retry to continue. Otherwise click Cancel to stop this operation." There is no previous media as I'm trying to do a new backup (separate from the one earlier that I had success with and then moved to another folder on the NAS). This all happens when choosing NAS Connection. I notice I'm never asked to enter credentials. I read this option should be faster than FTP Connections. I click on FTP Connections but not getting a response (had in the past). There are three options to access the NAS with TIH. 1) FTP Connection 2) NAS Connection 3) I have folders on the NAS that are setup as mapped network folders. I'm going to delete the last scheduled backup process showing in the TIH GUI and rebuild it and see what happens. Will likely test using a mapped network drive to the NAS to see what happens.

The problem now is that we have a different set of problems that may or may not be related to the earlier ones that hadn't been resolved.

Don't use a mapped drive for True Image, it is very very fussy and will often fail, UNC or IP addressing is best for TI access.

I would also go into Windows Credential Manager and delete the entry you used for the NAS so that TI asks for your credentials the first time you make a new task.

By mounting I did mean mounting not restoring. I had assumed these were disk/partition images that you are making (where mounting the tib file is possible), but if you are making files and folder backups you will only be able to explore. From what you wrote though, this side of things was working fine.

I recall that I believe TI 2013 had a problem where validating as part of a task would fail but a manual validation would work, I was going to ask you to test to see if you had the same result, but now with other problems there is probably not much point at this moment.

*****edited typing errors.*****

Yes, it has been quirky using mapped drives. I remember that.

As for the Windows Credential Manager. It's a fresh install of Win 7 64bit Home Premium and there are none stored yet. So, no idea why TI does not bring up the login window asking for username/password to access the NAS via NAS Connection (nothing seems to happen when I try to access FTP Connection and I understand the NAS Connection is faster/better than FTP Connection).

Mounting. I blew that one. Yes I am using tib files. I do only disk images. I can mount the current backup I made earlier. I've always been in the habit of just double clicked on it in Explorer and never bothered to mount the tib files.

Somehow I got it to take and setup for a NAS Connection. I checked the Windows Credentials Manager and again nothing is there. I completed a full scheduled backup. I triggered by choosing a Windows Restart (as it's set to do so once at shutdown or restart). I can mount the backup but I still cannot validate the backup. I manually entered the credentials into the Windows Credential Manager and then tried the validation again and it still fails. Keeps throwing the same error "Failed to open backup"W:\HP Laptop Full Backup (non factory) full b1 s1 v1.tib. Make sure the backup location is accessible and contains all versions of the backup. This backup may also be corrupted." My first question here is I'm using a NAS Connection and when I look at the path in TIH under the Backup and Recovery tab the location shows: "\\192.168.0.103\Data_Backups\HP Laptop\" so why is the error message stating ""W:\HP Laptop Full Backup (non factory) full b1 s1 v1.tib" when that would be a mapped drive location and not NAS? The path in the error doesn't match the path in the actual backup settings. During these test I right click in TIH and choose delete "settings only" and then rebuild the settings. Is it somehow carrying old settings into a different function (NAS Connection vs mapped drive)?

When I test a validation stored on the NAS for my desktop PC I get the same error. However, the path shown in the error and the one in TIH do match. I hit cancel and it immediately comes back and says "the backup is valid" and a popup windows says the "Validation process was completed successfully" which is impossible as the size of the .tib shows as 126GB in TIH and it could not validate this size file in one second. I confirmed the file size in Windows Explorer. The same thing happens on the desktop PC if I try to validate a backup that's on the secondary internal HDD. This is where the backups are done every day.

Something is going on with validations. I'm not confident the file names are matching to what the validation is showing a fail even tho' I choose the file specifically then right click and choose True Image -> Archive -> Validate.

Miscellaneous:

I've always been in the habit of just double clicked on it in Explorer and never bothered to mount the tib files.

Here is a 3rd method of choosing single files or folders to restore from a normal full backup. Now you have multiile choices in how to restore a few files for folders.
http://forum.acronis.com/forum/46511

duplicate

When you create the new task, your path to the new backup should point to a new sub-folder and the path should appear very similar to this path for the NAS.
This is the location screen where this name is assigned.

"\\192.168.0.103\Data_Backups\HP Laptop_NEW\FULL.TIB"

Figure 8: Assign custom folder name and assign custom backup file name

The creation of custom backup tib file names can only be changed when positioned in the directory tree as indicated in Figure 8; whereas the task name or "backup name" can differ from the backup file name. Task name changed or re-assigned in figure 18,
In 2013, all backup files will have a program added suffix to the *.tib name such as
   user assigned name_FULL_B1_S1_V1.tib
   user assigned name_INC_B1_S2_V1.tib as per this link example
    http://forum.acronis.com/sites/default/files/mvp/user285/guides/test201…
Assigning custom names to storage folders and backup files:
Understand that the backup file name is not task name and the task name is not the backup file name. The task name (Backup name) and the backup file name are two separate entities. They both may or may NOT carry the same name controlable by the user. Custom Backup file name controlled in figure 8. Task name (Backup name) controlled in figure 18. Avoid the use of parenthesis indicators or periods as part of the backup file name. The best time to finalize or change the "Backup name" (task name) is just prior to pressing the SAVE button to save the task configuration. This will allow you to change the "Backup or Task name" without changing the custom backup tib file name.

What type of backup are you doing - Incremental or full.
I just changed from Full to Incremental (when I noticed I'd eaten 1TB of NAS space in a fem months) and this issue happens for me too.
Switched back to full - no issues - Weird?

Guess I'll just stick with full backup and make sure I delete down once a week.

Dan

Dan,
Set up your task to do the deletions automatically so you don't have to worry about a full disk.

http://forum.acronis.com/forum/46691

Dan -> It's listed as custom. Creates a full version ofter 5 incremental versions and then deletes chains other than 7 days.

GroverH -> I've only had a chance to skim your responses. I'm not clear on your point. I give pretty simple names to my backups and browse to the folder/subfolder using TIH to choose the location on where I'm going to save the backups (tib files).

SBMongoos wrote:

Dan -> It's listed as custom. Creates a full version ofter 5 incremental versions and then deletes chains other than 7 days.

GroverH -> I've only had a chance to skim your responses. I'm not clear on your point. I give pretty simple names to my backups and browse to the folder/subfolder using TIH to choose the location on where I'm going to save the backups (tib files).

That was my point.
User should select their own custom storage folder and the user should assign their own names to both the backup file and assign their name to the backup task and not let the program do the assigning.

Regarding you custom backup scheme. What number are you using in the
"Store no more than _______ recent version chains"?

That was my point.
User should select their own custom storage folder and the user should assign their own names to both the backup file and assign their name to the backup task and not let the program do the assigning.

Regarding you custom backup scheme. What number are you using in the
"Store no more than _______ recent version chains"?

I do no have this option selected for my HP laptop or my desktop. I use the "Delete version chains older than X days". Where X, in my case, equals 7 days.

OK. Thanks.

As each of your chains will comprise 6 backups (1 full + 5 inc), as I understand the process, the 7 day options will lbe calculated on the last incrmental or the "S6 slice " backup of each chain.

When the oldest S6 becomes older than 7 days, that entire chain will be automatically deleted based on the "Delete version chains older than 7 days". This auto deletion will immediately follow the creation of the newest full.

Based on my underwstandings and testing, the above is what I would expect the program to produce with those settings.

GroverH wrote:

OK. Thanks.

As each of your chains will comprise 6 backups (1 full + 5 inc), as I understand the process, the 7 day options will lbe calculated on the last incrmental or the "S6 slice " backup of each chain.

When the oldest S6 becomes older than 7 days, that entire chain will be automatically deleted based on the "Delete version chains older than 7 days". This auto deletion will immediately follow the creation of the newest full.

Based on my underwstandings and testing, the above is what I would expect the program to produce with those settings.

Okay...not to be rude or perhaps I'm missing something but does this help discern what my problem is for this thread?

You're right. At this point, so much has been covered, I am not sure of which which posting is the problem. I will cease my postings. Good luck.

GroverH wrote:

You're right. At this point, so much has been covered, I am not sure of which which posting is the problem. I will cease my postings. Good luck.

Feel free. Here's the orginal:

Problems backing up to NAS. Have an HP laptop that I have been able to use TIH to backup to my NAS just fine in the past. Via WiFi and wireless. The past couple of weeks it keeps failing. At times it looks complete and I can open it from TIH on my desktop and laptop. But when I try to validate it through TIH on my laptop or desktop it says it's corrupt.

Well.... I may be on the road to recovery. The thing that bothers me about TIH is I don't seem to find an "end all" answer. I had failed backup to my NAS from my laptop via WiFi. Odd thing is TIH said it failed and stated about four errors. Then I was able top open the .tib in explorer and was able to mount it as well and access the .tib. To top it off I ran a validation on this .tib via WiFi and it came back validated. Go figure. I've used TIH for a long time and it's got me out of some pinches but I've never seen such inconsistencies and events that cannot be explained or ultimately fixed. Perplexing.

Unfortunately, some of the text based error messages cover more than one fault/error/warning and I suspect so do some of the error codes.