Any server with a licensed agent can be used as a fileserver. I would advise against NAS storage if you are using Windows as your OS for the fileserver, since Windows requires you to login to map network drives. There are a few "work arounds" to this problem on the forum, but they introduce security loopholes. If you are going with NAS, use a Unix based operating system for your file server.
problem is that BL is saying that the Agent is not licensed so we cant even use it....any idea how to solve it?
Sorry if I am over simplifying this, but I would suggest you license the agent. Have you attempted this?
i did license the agent of course...:)
but when u want to use it, its saying is not licensed
You are probably hitting into an ACL problem here. Your mappings grant you with so little privileges that you cannot even state whether te agent is licenced.
If you want to use a NAS resource as your FileServer I'd advice that you do the following:
- Mount your NAS device on some server that has an agent,
- Setup the ACLs so that the AppServers (which are actually using the bladmin unix user) can write to the FileServer
- Create an alias to the FileServer (EG : blfs) on each AppServer of your environment.
- Define the FileServer where needed using the alias
By doing so, if you want to move the FileServer to some other place - EG mount the NAS resource on a different server - you just need to update the alias on the AppServers.
Is the file server on a VM ?
1 of 1 people found this helpful
Actually, that's slightly off. The file server will be written as whatever user in the console is creating the package object. you should create a non-privledged account on the file server, say "blfsuser". Your file server directory is say "/u01/storage".
Then run a 'chown -R blfsuser:blfsuser /u01/storage"
Then in the /usr/lib/rsc/exports file you put only:
In the users.local file you may need to put:
And leave users blank. And never push acls to this agent.