Configuring Servers and Server Groups

This section describes general information about server storage and configuration tasks.

Servers that have local disks physically connect by using SCSI or IDE interfaces. In order to activate and deploy a server, you need to configure at least one boot volume with a bootable OS image on the volume. The disk volume must be equal to or greater than the size of the image. Consider the following when configuring servers and server groups.

• If you configure the server incorrectly, an error message appears advising you to change the configuration.

• The server names and IP addresses are listed. If the IP address is not available, because it has not been assigned yet, it displays: not assigned.

• In Active state, a warning is issued when changing images or when adding and removing a disk volume because the server needs to be shut down.

When managing an active server group and applying a new disk image, the selected image is applied to each server in the server group. This process causes down time because all the servers will reboot.

Each server interface typically connects to a different subnet. If the interfaces connect to the same subnet, you need to thoroughly understand how the operating system handles this situation. Connect one or both interfaces depending upon your requirement. For example, connect the web server to a front-end subnet and the database server to a back-end subnet for added security. Use the server group mechanism to group servers or not depending on your requirements. You have more control with individual servers, but easier management with server groups.

After the farm is Active, you can perform the following tasks:

• Create software images that include applications and data.

• Create server groups or grow a server group (multiple, identical servers).

• If your storage type allows, add storage volumes. Disk size depends upon the storage type you select from the drop-down list.