HP StorageWorks Clustered File System 3.6.0 Windows Storage Server Edition Administration Guide (403103-005, January 2008)
Table Of Contents
- Contents
- HP Technical Support
- Quick Start Checklist
- Introduction to HP Clustered File System
- Cluster Administration
- Administrative Considerations and Restrictions
- Tested Configuration Limits
- Volume and Filesystem Limits
- User Authentication
- Start the Management Console
- Cluster Management Applications
- The HP CFS Management Console
- View Installed Software
- Start HP Clustered File System
- Stop HP Clustered File System
- Back Up and Restore the Cluster Configuration
- HP Clustered File System Network Port Numbers
- Configure Servers
- Configure Network Interfaces
- Configure the SAN
- Configure Dynamic Volumes
- Configure PSFS Filesystems
- Manage Disk Quotas
- Manage Hardware Snapshots
- Configure Security Features
- Configure Event Notifiers and View Events
- Overview
- Install and Configure the Microsoft SNMP Service
- Cluster Event Viewer
- Configure Event Notifier Services
- Select Events for a Notifier Service
- Configure the SNMP Notifier Service
- Configure the Email Notifier Service
- Configure the Script Notifier Service
- View Configurations from the Command Line
- Test Notifier Services
- Enable or Disable a Notifier Service
- Restore Notifier Event Settings to Default Values
- Import or Export the Notifier Event Settings
- Using Custom Notifier Scripts
- Cluster Operations on the Applications Tab
- Configure Virtual Hosts
- Configure Service Monitors
- Configure Device Monitors
- Advanced Monitor Topics
- SAN Maintenance
- Other Cluster Maintenance
- Management Console Icons
- Index
Chapter 5: Configure Servers 52
Migrate Existing Servers to HP Clustered
File System
In HP Clustered File System, the names of your servers should be
different from the names of the virtual hosts they support. A virtual host
can then respond regardless of the state of any one of the servers.
In some cases, the name of an existing server may have been published as
a network host before HP Clustered File System was configured. You can
either reassign the public name of the server to the virtual host, which is
generally the better solution, or keep the published name associated with
the server.
• Migrate the existing server name to a virtual hostname. In this case,
you will need to assign a new name to the server. External sites that
then access the original server name will actually be served by the
virtual host—basically, a failover-protected version of the server, with
no difference in appearance to the clients.
• Keep the existing name on the server. If you do not rename the
server, clients will need to use the new virtual host name to benefit
from failover protection. Clients can still access the server by its name,
but those requests are not protected by HP Clustered File System. If
the server fails, requests to the server’s hostname fail, whereas
requests to the new virtual hostname are automatically redirected by
HP Clustered File System to a backup server.
Configure Servers for DNS Load Balancing
HP Clustered File System can provide failover protection for servers
configured to provide domain name service (DNS) load balancing. DNS
load balancing allows you to set up servers so that requests are sent
alternately to each of the servers in a cluster. For example, clients could
access acmd1 and acmd2 in turn, enabling the servers to share the load of
accepting and responding to client requests.
DNS includes a round-robin feature using address records (A records) to
alternate requests between IP addresses. This feature provides a
straightforward way to gain load balancing capability and simplified load
balancing, resulting in improved response time.