09-05-2014 04:43 AM
When I try and put in a UNC path for the Simplified Disaster Recovery Alternate Data Path, it does, it comes back with the error "the alternate data path is not valid" Then account it is trying to use has full rights to the path I'm putting in. what else could I check
Solved! Go to Solution.
09-17-2014 03:51 AM
Create a sub-folder in that share and provide the path. For egs ~
\\ServerName\SharePath\FolderName
09-05-2014 05:16 AM
The service account has to be able to access this path, not the account you are logged into the console as
- this is for a very simple reason: BE is designed to still run jobs when you are not logged in
09-09-2014 02:49 AM
the service account has acccess to backup the folder, shouldn't this be the same access?
09-09-2014 04:09 AM
Is that share hidden? (contains "$" on end ) ? If is, that's root of the problem.
09-17-2014 03:30 AM
No, I have a share created, with the backup logon account given full permissons, checked effective permissons on the share. Still getting the same errror.
09-17-2014 03:51 AM
Create a sub-folder in that share and provide the path. For egs ~
\\ServerName\SharePath\FolderName
09-17-2014 07:40 AM
using
\\IT-TOOLS.wihd.org\Backup Exec\SDR
09-17-2014 07:44 AM
I login as my service account from my Backup Exec server and I'm able to create\modify a file on the share.
09-17-2014 08:23 AM
Instead of naming it Backup Exec and SDR, would you pls try using other non-specific BE names.
Are you able to set an alternate path on the same server but different volume ? And have you tried setting it on a different server as well as a test ?
09-17-2014 08:37 AM
09-17-2014 10:19 AM
VJware, thatnk you for the response, but a share is a function of windows, if permissions are giving and logging in from the backup server with the service account and able to access that share, then the name of share is a non issue, unless now BE is having an issue. Are there naming conventions that BE cannot handle for shares? Putting the share on another Server\volume should not have an impact if I can use the service accoun to reach this share. I understand the thought process, but it seems BE is not recongizing the service account that is being used.
09-17-2014 01:14 PM
I changed the account and now it is working, Thank you for all the responses