 | ||
| Before you configure a file share service group | ||
|---|---|---|
| Prev | About configuring file shares | Next |
Note the following prerequisites before you configure a file share service group:
Verify that you have local administrator privileges on the system from where you run the wizard.
If you have configured a firewall, add the required ports and services to the Firewall Exception list.
For a detailed list of services and ports used, refer to the product installation and upgrade guide.
Verify that the VCS high availability engine, HAD, is running on the system from which you run the wizard.
Verify that the directories to be shared reside on shared disks that are accessible from the nodes that will be part of the file share service group.
If your storage is SCSI-3 compliant and you wish to use SCSI-3 persistent reservations, enable SCSI-3 support using Veritas Enterprise Administrator (VEA). VEA is available with SFW HA only.
Mount the drives or LUNs containing the shared directories on the system where you run the wizard. Unmount the drives or LUNs from other systems in the cluster.
Verify that the Veritas Command Server service is running on all the systems in the cluster.
If NetBIOS is disabled over TCP/IP, you must set the Lanman agent's DNSUpdateRequired attribute value to 1 (True).
You can modify the Lanman resource attribute value after configuring the service group.
Verify that you have the following information ready. The wizard prompts you for these details:
A unique virtual computer name to be assigned to the file share server
This is the name that the clients use to access the file shares. The virtual name must not exceed 15 characters. If you specify a virtual computer name in lowercase letters, the name is converted to uppercase. For example, the name VCSServer is converted to VCSSERVER.
A unique virtual IP address to be assigned to the file share server
The virtual IP address is required only if you wish to configure an IPv4 address. In case of IPv6, the wizard prompts you to select the IPv6 network and automatically generates an IPv6 address that is valid and unique on the network. The wizard uses the prefix that is advertised by the router on the IPv6 network.
Note: |
Windows Server does not support accessing file shares using a virtual IP address. You can work around this restriction by using non-scoped file shares. |
The list of directories to be shared.
You can add existing shares to the VCS configuration. However, you cannot add special shares (shares created by the operating system for administrative and system use). For example, you cannot add the shares ADMIN$, print$, IPC$, and DriveLetter$ to the VCS configuration.