07-31-2012 08:12 AM
I have a small NAS device (DNS-323) and I wanted to try out backing up a PC to using System Recovery 2011.
The drive on the NAS is set to Read/Write for everyone. When setting up the backup job I can browse to the relevant directory on the NAS but get stuck when System Recover asks me for the drive's credentials as there isn't any.
I've tried creating a share on the drive for System Recovery and still the credentials get rejected.
Can this be done or am I missing the obvious?
Many thanks.
Richard
Solved! Go to Solution.
08-01-2012 08:54 AM
Many thanks for the info Chis.
This didn't work for me - the suggested menu options doesn't appear to be a System Recovery menu.
However, it did lead me to a solution.....
I went to Tasks -> Options and in 'General I typed the default backup destination into the relevant field (browsing didn't work).
I could then select the destination path from the drop down when creating the backup job.
Strange!
Again, thanks for your time on this.
Richard
07-31-2012 08:56 AM
This may help:
http://www.symantec.com/docs/TECH173534
08-01-2012 01:23 AM
Thanks Chris.
I did see that article but it didn't help. I just need to be able to enter (or skip) the network credentials when setting up the destination in the Define Backup Wizard.
08-01-2012 08:29 AM
Looks like someone else ran into this:
https://www-secure.symantec.com/connect/forums/backup-exec-desktopserver-edition-2010-force-you-use-network-credentials-backing-network-shar
08-01-2012 08:54 AM
Many thanks for the info Chis.
This didn't work for me - the suggested menu options doesn't appear to be a System Recovery menu.
However, it did lead me to a solution.....
I went to Tasks -> Options and in 'General I typed the default backup destination into the relevant field (browsing didn't work).
I could then select the destination path from the drop down when creating the backup job.
Strange!
Again, thanks for your time on this.
Richard
08-02-2012 12:38 AM
That's strange. I can't really explain why it works when you do it that way.
Anyway, thanks for the update and glad you got it working in the end.