SCHEDULED Backup to a Network Share Fails Due to Connection Failure
I have a problem connecting to a network share when performing a "scheduled" backup using TI 2010 and WinXP Pro. I can connect the network drive using NET USE and also via UNC mapping. If I run a manual unscheduled task it always completes the backup perfectly. If I schedule the task with the same exact settings it fails like this: http://forum.acronis.com/content/5138
My NAS appliance does not allow user authentication. It simply just provides CIFS shares.
Any idea how I can run scheduled backups without a connection error?
Thank you,
John

- Anmelden, um Kommentare verfassen zu können

I'm not sure I can really help too much, because I'm seeing similar problems, but I did solve one problem that is like yours. I had a similar problem with Norton Ghost on an XP machine, so I'm not sure if it's really an Acronis or Win 7 problem.
My situation: Windows 7 64 bit Home Professional OS, with the Acronis True Image 2010. (I haven't yet applied the update that I downloaded yesterday, though.)
I was always able to browse the network backup and run manual backups, as you were, but my scheduled backups failed in the same way yours do.
My NAS (Netgear DuoNAS) does allow user accounts, but I'm not sure I needed one. (I did create one, however.)
Apparently you need to have a password-protected user account in order to supply credentials to the backup software. I'm not willing to saddle myself with a password to access my notebook at home, so I created an account with admin privileges, gave it a password, and configured my scheduled backup to use those credentials. Worked like a charm.
If you don't want to see the new account on the login screen, you can hide it with a registry key. Do a quick search on hidden account and you'll find it.
In your case, since you're part of a domain, would it help to use the credential checkbox to 'Use NT login'?
Hope this helps
Tom
- Anmelden, um Kommentare verfassen zu können

pointpeninsula wrote:I'm not sure I can really help too much, because I'm seeing similar problems, but I did solve one problem that is like yours. I had a similar problem with Norton Ghost on an XP machine, so I'm not sure if it's really an Acronis or Win 7 problem.My situation: Windows 7 64 bit Home Professional OS, with the Acronis True Image 2010. (I haven't yet applied the update that I downloaded yesterday, though.)
I was always able to browse the network backup and run manual backups, as you were, but my scheduled backups failed in the same way yours do.
My NAS (Netgear DuoNAS) does allow user accounts, but I'm not sure I needed one. (I did create one, however.)
Apparently you need to have a password-protected user account in order to supply credentials to the backup software. I'm not willing to saddle myself with a password to access my notebook at home, so I created an account with admin privileges, gave it a password, and configured my scheduled backup to use those credentials. Worked like a charm.
If you don't want to see the new account on the login screen, you can hide it with a registry key. Do a quick search on hidden account and you'll find it.
In your case, since you're part of a domain, would it help to use the credential checkbox to 'Use NT login'?
Hope this helps
Tom
Thanks for the response. I'll try to create a "hidden" account in XP and see if I can use those credentials.
What update were you referring to in your post? I checked the TI2010 updates and the last one was from Nov 2009.
-John
- Anmelden, um Kommentare verfassen zu können

I was writing that from work, so I didn't have the details. I installed the software in October, but never noticed the November update until a couple of days ago. I downloaded it, but haven't yet installed it.
Tom
- Anmelden, um Kommentare verfassen zu können

I did as you suggested and created a new user on my XP system that was NOT on the domain. I setup Acronis TI 2010 under the new login and the task runs fine. Quite a hassle but it's better then having no backups...
Thanks again for chiming in.
- Anmelden, um Kommentare verfassen zu können

I'm glad it helped. It does seem a little absurd to do all that on a private network, but whatever works.
- Anmelden, um Kommentare verfassen zu können