File server requirements
A file server should meet the following requirements:
An RSCD agent must be installed and should be the same version as the Application Server.
Do not limit access to the file server by pushing agent ACLs to the agent on the file server. All users must be mapped to the same user on the file server.
As a minimum, a file server must have 72 GB of available, nonredundant, disk space. BMC recommends that the file server be allotted 200 GB or more of available RAID 5 disk space.
- Define a user name on the file server, and map all users to that user name. Without this mapping, a user may not be able to access a file that another user has stored on the file server. To accomplish the necessary mapping, create an entry like the following in the exports file (located by default at C:\Windows\rsc) on the file server:
<appServer> rw,user= <userName>
Where <appServer> is a comma-separated list of Application Server names or IP addresses (IPv4 or IPv6) and <userName> is the name to which all users are mapped.
- Map the internal System:System role/user to the user name defined on the file server. To accomplish the mapping, create an entry like the following in the users.local file (located by default at C:\Windows\rsc) on the file server:
Where <userName> is the name to which all users are mapped, typically bladmin or administrator.
If the required directory structure does not already exist on the file server, the system process attempts to create it.
For examples on configuring the file server agent ACLs, see Configuring the file server agent ACLs.
- If your file server location is on partition or a mounted storage, you must ensure that the mount point for the storage or partition is consistent even if the file server host is restarted.
For example, on Linux, you can ensure this by configuring the fstab file in the etc folder of your machine. The fstab file maps the Universally Unique Identifier (UUID) of a storage or partition to the directory it should be mounted on.