Windows Server Failover Cluster Management Pack
To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Management. (If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.)
In the console tree, if the cluster that you created is not displayed, right-click Failover Cluster Management, click Manage a Cluster, and then select the cluster you want to configure.
In the console tree, click the plus sign next to the cluster that you created to expand the items underneath it.
If the clustered servers are connected to a network that is not to be used for network communication in the cluster (for example, a network intended only for iSCSI), then under Networks, right-click that network, click Properties, and then click Do not allow the cluster to use this network. Click OK.
Click Services and Applications. Under Actions (on the right), click Configure a Service or Application.
Review the text on the first page of the wizard, and then click Next.
Click File Server, and then click Next.
Follow the instructions in the wizard to specify the following details:
- A name for the clustered file server
- Any IP address information that is not automatically supplied by your DHCP settings—for example, a static IPv4 address for this clustered file server
- The storage volume or volumes that the clustered file server should use
After the wizard runs and the Summary page appears, to view a report of the tasks the wizard performed, click View Report.
To close the wizard, click Finish.
In the console tree, make sure Services and Applications is expanded, and then select the clustered file server that you just created.
Under Actions, click Add a shared folder.
The Provision a Shared Folder Wizard appears. This is the same wizard that you would use to provision a share on a nonclustered file server.
Follow the instructions in the wizard to specify the following settings for the shared folder:
- Path and name.
- NTFS permissions (optional).
- Advanced settings for the SMB protocol (optional). SMB is used by Windows-based clients. The settings include:
- User limits.
- Offline settings (caching).
- Access-based enumeration, described in, earlier in this guide.
- Whether the NFS protocol will be used, for support of UNIX-based clients (optional).
After completing the wizard, confirm that the clustered file server comes online. If it does not, review the state of the networks and storage and correct any issues. Then right-click the new clustered file server and click Bring this service or application online.
To perform a basic test of failover, right-click the clustered file server, click Move this service or application to another node, and click the available choice of node. When prompted, confirm your choice.
You might also like
Resume Revision Part 2 of 2by jobs2006
Technology Training Specialist (Place Worked) 8/05-8/06
* Designed and implemented a two-tiered content management system comprised of reservations and web based calendar functions for a small corporation of 100 employees.
* Provided on-site and remote troubleshooting assistance as needed.
Montessori Program Assistant (Place Worked) 8/04/8/05
* Conducted onsite research to discover how Open Source technology impacts the cognitive development in three year old children
How's this?by scottydog77
Still need to fill out the remaining job history, but here is a sneak peek:
Scott R Hinton
address and phone left out.
To obtain a creative and challenging position that enables me to gain valuable commercial experience and improve the web development and design skills that I gained through experience and academic projects.
Limited Graphic design and Photo editing
Enterprise Content Management with Microsoft SharePoint (Developer Reference)
Book (Microsoft Press)
Look beyond APM to unified performance monitoring — TechTarget
ORLANDO, Fla. -- The lack of interoperability among traditional performance monitoring tools means data centers must use -- and pay for -- multiple tools. But movement toward unified performance monitoring could change all that.