TIH 2011 won't validate or recover from a simple network share
build #6574
Win7 x64
going insane here guys just trying to do a simple data partition restore from a backup stored on a simple windows share. Data partition only, nothing complicated. I can see the .tib file just fine and i can read/write to the share in windows without limitation. I can even mount the backup image and browse all the files via the network.
I select "browse for backup", select the network share (in this case W:\backups) and add to backup list. The backup shows in the list but if i try to validate or recover it fails with:
Error occurred while opening the file
The system cannot find the path specified
Operation has completed with errors.
Call me crazy, but if i wrote this software this would probably be the 2nd functionality test it would have to pass for public release, the first being restore from local disk. FWIW, i'm trying to restore from network because i don't have enough local disk although i just ordered another 2TB drive becuase judging from search on this issue i could be in for a long wait...
Any ideas?
Chris...

- Accedi per poter commentare

yeah i tried both methods, i continually got connection failed error on the direct path typing. I tried all kinds of share permissions password, no password, domain, workgroup, everything failed although Windows could access the share just fine.
In the end i gave up and bought another 2Tb drive as my local temp store for backup recovery, LOL! At least recovery worked and i am able to access my business files again. I just need to remember to copy them off to the server drive until this terrible bug is fixed.
This whole episode was triggered by a bug in Intel Matrix Storage 8.9 dropping both my (perfectly good WD RE4) Raid 1 drives within 4 hrs. Luckily during those 4hrs before the array went down i had time to make a full backup of my data. Hard to imagine that a Raid 1 setup and then backup s/w can fail at the same time due to silly bugs, it's a bit like welcome to the 80's again...
Chris...
- Accedi per poter commentare

I don't know if it's relevant or not, but there's only one 'non-standard' thing I have setup in my networking that may (or may not) be important.
I relaxed the default (for Windows 7) NTLM authentication level so that an older XP system could 'net use' drives on the Windows 7 system. Since I never tried TI 2011 without the Win-7 'server side' having this 'relaxed' rule, I don't know one way or the other if this would have been needed (by TI 2011) or not.
I ran secpol.msc (on my Win 7 -64 system 'serving' the shared drive) and changed Local Policies/Security options/Network Security: LAN Manager authentication level. It was 'undefined' and I changed it to "Send NTLMv2 response only\refuse LM". (I think the default on Windows 7 is the next step higher at 'Send NTLMv2 response only\refuse LM and NTLM ').
Before I changed this, an older XP system would not connect to my Win-7 system (with plain old 'net use', etc). As I understand it, Win -7 upped the needed default security level.
If you're feeling adventurous you could see if that helps your situation or not...
-Greg
- Accedi per poter commentare

not sure if this is the issue but here is the path the logs say it is trying when the drive is mapped:
\\?\W:\Partition_backup_DataF_2.tib.metadata
I don't know what the \\? out front means but it is likely the problem. *sigh*
So far support email has replied twice with links to things i tried 10 times already. Obviously the network is not the problem, i can mount the backup using the acronis software just fine and copy files manually out of the partition archive.
- Accedi per poter commentare

support's latest suggestion "Please copy the image to an external drive and then try restore" *sigh*
i have 2 problems with this:
1. i told him i already did this in my first email
2. buying a $200 drive as as workaround to what is obviously untested software
I have had really great experiences with Acronis software over the last few years, i guess i was lucky i never had to contact support until now.
- Accedi per poter commentare

I am having the same issue. If I allow NTLM in GP then authentication works fine. I only want to allow NTLMv2. I have an open case with acronis support and they are escalating the case but no answer yet. I believe it's an issue with their Linux client not being able to use NTLMv2. Anyone out there solved this issued yet?
- Accedi per poter commentare