Unable to create storage for Veritas Backup Exec 16

Status
Not open for further replies.

rsudol

Cadet
Joined
Nov 8, 2017
Messages
4
Everytime i try to create Storage for Veritas Backup Exec 16, I get the following message in Veritas BE. Unable to create the disk storage - The Backup Exec service account does not have read / write permissions on the remote computer on which the network share is located. I can map to the url for the same location and place a text file with no trouble,
 
Last edited by a moderator:

styno

Patron
Joined
Apr 11, 2016
Messages
466
Are you saying you can write files with the user that the service is started with? (doublecheck services for the exact username)
 

rsudol

Cadet
Joined
Nov 8, 2017
Messages
4
actually as the Domain admin or the BackupExec Service Account i am not able too. Im pretty sure we set up ad integration.
 

styno

Patron
Joined
Apr 11, 2016
Messages
466
If you are not sure then this is where you start troubleshooting.
 

rsudol

Cadet
Joined
Nov 8, 2017
Messages
4
ok can you assist with AD integration as i cant seem to get it to work or see how to test it properly or make a ad user account work.
 

styno

Patron
Joined
Apr 11, 2016
Messages
466
I don't have an AD setup myself, but here is the relevant documentation: http://doc.freenas.org/11/directoryservice.html#active-directory
If you have trouble or run into issues with it you have to provide a lot more info before somebody on the forum can help you.
(At least provide the FreeNAS version & hardware configuration & setup, explain what you want to accomplish, explain what you already did and what procedure you followed and where you are stuck, then copy/paste the exact error message in the forum.)
Right now, somebody has to guess what issues you are running into.
 

rsudol

Cadet
Joined
Nov 8, 2017
Messages
4
ok i have verified that the AD setup is complete and my ad users show up successfully when looking at the volumes. At this point i do not know what i need to do to add multiple users to a volume or SMB share.
 
Status
Not open for further replies.
Top