By Andrew Ness
This quick start guide describes how to prepare volumes on a Sun ZFS Storage Appliance to be used as common shares by a server running Microsoft SharePoint Server and how to set up the SharePoint Server to access these volumes.
This quick start guide provides an introduction to creating and preparing shares and block-protocol iSCSI LUNs on a Sun ZFS Storage Appliance to be published and used by a Microsoft Windows server running Microsoft SharePoint Server 2007 or Microsoft SharePoint Server 2010. A typical configuration is shown in Figure 1.
Figure 1. Typical configuration of a Microsoft SharePoint Server and clients used with a Sun ZFS Storage Appliance
Sun ZFS Storage Appliance uses an open-systems approach to combine general-purpose servers and storage components with an integrated storage software suite to offer effective, manageable, and scalable data storage while providing a simple and powerful browser-based interface (BUI) for administrators.
Microsoft SharePoint Server is a collaborative software product included in the Microsoft Office suite. An organization can use the Microsoft SharePoint Server to facilitate collaboration, provide content management features, implement business processes, and supply access to information that is essential to organizational goals and processes.
This document assumes the reader is familiar with the general purpose and functionality of the Sun ZFS Storage Appliance and Microsoft SharePoint Server. When appropriate, Microsoft SharePoint Server 2007 and Microsoft SharePoint Server 2010 are referred to collectively as Microsoft SharePoint Server, or SharePoint Server, in this document. The procedures in this document are illustrated with the Sun ZFS Storage Appliance Release 2010.Q3.
Microsoft SharePoint Server does not require a special network configuration. However, although the Microsoft SharePoint clients and the Sun ZFS Storage system do not need to be in the same domain or on the same subnet as the Microsoft SharePoint Server, they must all be able to reach the Microsoft SharePoint Server over the network.
You may prefer to configure a private network to handle the storage traffic between the server running Microsoft SharePoint Server and the Sun ZFS Storage Appliance. Depending on the model and configuration of the Sun ZFS Storage Appliance, additional network interfaces are provided that can be used for network aggregation or configuring IP multipathing. Figure 2 shows the Network Interface configuration dialog box in the Sun ZFS Storage Appliance. To display this dialog, select Configuration > Network and either edit an existing network interface by clicking the Edit (pencil) icon next to the network interface entry, or click the + icon next to the Interfaces heading to create a new network interface.
Figure 2. Configuring a network interface in the Sun ZFS Storage Appliance
Configuring the pool storage RAID layout requires balancing availability, capacity, and performance. The Sun ZFS Storage Appliance BUI provides information about the relative trade-offs between availability, capacity, and performance. You must weigh all three factors when deciding on a data profile. This section describes some considerations.
When the Microsoft SharePoint Server communicates with storage, the write I/O pattern is highly sequential while the read I/O pattern is highly random. Therefore, the best performance is usually achieved using the mirrored profile. Figure 3 shows the storage pool configuration options offered in the Sun ZFS Storage Appliance.
Figure 3. Configuring the storage pool in the Sun ZFS Storage Appliance
Sun ZFS Storage Appliance Analytics show the I/O request size of the SharePoint Server is usually around 32 KB due to the underlying Microsoft JET Database Engine. It is therefore advisable to select a volume block size of 64 KB to minimize the number of multi-block reads required to satisfy a single logical read. For more information about selecting a block size, see the blog entry “Stripe Sizing for Performance” at http://blogs.oracle.com/andrewness/entry/stripe_sizing_for_performance.
Depending on the model of the Sun ZFS Storage Appliance you are using, you may need to select a data profile for solid state devices (SSDs) used for logs in the configuration. Striping the log devices typically provides the best performance. However, mirroring the log devices provides an extra degree of log availability. If a log device is lost, log entries are written to a disk. Write performance may be degraded but the pool itself remains available.
If the Microsoft SharePoint Server (and Microsoft SQL Server) is to be newly installed, projects and shares must first be configured on the Sun ZFS Storage Appliance to present iSCSI volumes to the SharePoint Server. (See the Appendix: Recommendations for Using CIFS Shares for information about using CIFS shares for SharePoint Server storage.
The number of iSCSI volumes to be configured depends on business factors such as the granularity of required snapshots and clones. If replication is to be implemented, the layout of projects is also a consideration. The Sun ZFS Storage Appliance System replicates at the project level, so if different types of shared data are to be replicated on different schedules, you should configure the volumes into several projects, so that each project can be replicated according to its own schedule.
If you are creating multiple volumes (LUNs) under the same project, you can change the properties at the project level and those properties will be inherited by all LUNs in the project. Individual properties can be overridden at the LUN level as needed. The dialog box displayed when creating a new project is shown in Figure 4. To display this dialog box, go to Shares > Projects and select the + icon at the top of the Project table.
Figure 4. Creating a project in the Sun ZFS Storage Appliance
The iSCSI protocol allows clients (called initiators) to send SCSI commands to SCSI storage devices (targets) on remote servers.Targets are created on the Sun ZFS Storage Appliance. After a target has been defined, it can be published to or discovered by the host running Microsoft SharePoint Server. An initiator is then defined on the host and a connection established between the initiator and the target.
To create an iSCSI target on the Sun ZFS Storage appliance, complete the steps below:
Figure 5. Creating a new iSCSI target
Targets with the same target definition (such as iSCSI or Fibre Channel) can be logically combined into target groups. When a LUN is assigned to a target group, it will be presented to potential initiators using the protocol specified for the target group members.
Initiators can also be collected into groups. When the LUNs in an iSCSI target group are assigned to an initiator group, they will be accessible only to the initiators in that initiator group using iSCSI protocol.
To create a target group or add a target to an existing target group, complete these steps:
Figure 6. Creating an iSCSI target group
Figure 7. Editing the iSCSI target group
Figure 8. Rename the iSCSI Target Group
The iSCSI target must either be published to or discovered by the host running the SharePoint Server. Complete the following steps on the host:
Figure 9. Discovering the iSCSI target
Figure 10. iSCSI Target shown as inactive
Figure 11. Logging on to the iSCSI target
It is a good practice to create an iSCSI Initiator Group containing all the iSCSI initiators that require access to a LUN or LUNs. In the example below, an iSCSI Initiator Group is configured with a single initiator called SharePoint. However, if the SharePoint Server runs under a cluster is run as a service in a cluster at some point in the future, you can add other nodes to the group without affecting access to the LUN by current group members.
To create an iSCSI Initiator Group, complete these steps on the Sun ZFS Storage Appliance:
Figure 12. Creating an iSCSI Initiator Group
To prepare a volume to be used as a common share by a host running Microsoft SharePoint Server, you first need to create and configure an iSCSI LUN on a Sun ZFS Storage Appliance and then initialize it on the SharePoint Server host.
To create an iSCSI LUN, complete the steps below:
Figure 13. Creating an iSCSI LUN
Typically, all initiators are assigned to a default group that allows general access, unless a specific authentication mechanism has been put in place. However, you can modify the properties of a LUN to restrict access to a particular group of initiators by completing these steps:
Figure 14. Selecting a LUN to edit properties
Figure 15. Setting Share Options to restrict access to a LUN
To prepare an iSCSI LUN for use by the SharePoint Server, complete the steps below:
Figure 16. Rescanning disks to make the iSCSI LUN available to SharePoint Server host
Figure 17. Disk properties after initialization
Figure 18. Final step using New Partition Wizard
To install Microsoft SharePoint Server 2007, complete the steps below:
setup.cmdon the installation media. When the license key is requested, provide a valid license key.
C:drive or entering the location of the iSCSI LUN prepared for use by the SharePoint Server for data files in the section Creating and Preparing an iSCSI LUN. In the example, this location is the SharePoint disk
S:as shown in Figure 19.
I:(see Figure 19).
Figure 19. Selecting Sharepoint Server 2007 file locations
Microsoft SharePoint Server 2010 is installed using the Microsoft Windows Installer. When the auto-run feature is enabled, the installation process is initiated using the setup utility that starts automatically when the installation medium (usually a DVD) is inserted. You can also start the installation process by manually executing the setup utility
To install Microsoft SharePoint Server 2010, complete these steps
Figure 20. SharePoint Server 2010 installation dialog
Figure 21. Specifying the SharePoint Server 2010 search index file location
Note. A decision about whether to use a Standalone Server or implement a Server Farm is outside the scope of this article. Refer to the Microsoft SharePoint Server 2010 Release Notes and Installation Guide for further configuration information.
When the installation process is complete, the Microsoft SharePoint Server 2010 home page is displayed.
The Sun ZFS Storage Appliance offers an Analytics feature which includes analytics useful for observing the system workload. For example, network activity can be observed as interface bytes per second broken down by interface. iSCSI activity can be observed as operations broken down by initiator, LUN, latency, or client; bytes broken down by client or LUN, disk I/O, or operations per second broken down by latency.
Objects to be analyzed can be combined into a worksheet and saved for later reuse. A worksheet example is shown in Figure 22. Many more options are available through the appliance BUI under the topic Analytics.
Figure 22. Worksheet showing a selection of iSCSI operations analytics
The Sun ZFS Storage Appliance offers a variety of features to protect archived data, including the following:
For more information about creating snapshots and replicating data, see the procedures in the Shares topic in the documentation wiki that is embedded in the Sun ZFS Storage Appliance. You can view the documentation wiki by clicking on Help in the Sun ZFS Storage Appliance BUI or by going to:
https://<IP address for your installation>:215/wiki.
Sun ZFS Storage Appliance allows administrators to take advantage of a simple, powerful BUI to manage scalable, high performance data storage for use by a Microsoft SharePoint Server. This article has described how to configure iSCSI LUNs in the Sun ZFS Storage Appliance and how to configure the Microsoft SharePoint Server host to enable a SharePoint Server to use shared volumes on the Sun SFS Storage Appliance for storing data.
For more information, visit the Web resources listed in Table 1.Table 1. Web resources for further information
|Web Resource Description||Web Resource URL|
|Oracle Sun Unified Storage web page||http://www.oracle.com/us/products/servers-storage/storage/unified-storage/index.html|
|Sun Storage Appliance documentation:||http://www.oracle.com/technetwork/documentation/oracle-unified-ss-193371.html|
|Sun ZFS Storage Appliance web page||http://www.oracle.com/us/products/servers-storage/storage/unified-storage/sun-storage-7000-uss-103104.html|
|Oracle and Sun web page||http://www.oracle.com/us/sun/index.htm|
|Oracle Technology Network (OTN) web page||http://www.oracle.com/technetwork/index.html|
|Oracle OTN: System Admins and Developers web page||http://www.oracle.com/technetwork/systems/index.html|
|Oracle OTN Discussion Forum: Storage||https://community.oracle.com/community/server_%26_storage_systems/storage|
|Oracle OTN Discussion Forum: Servers||https://community.oracle.com/community/server_%26_storage_systems/servers|
|Storage Stop Blog||http://blogs.oracle.com/storage|
|Oracle Software Downloads site||http://www.oracle.com/technetwork/indexes/downloads/index.html|
|Oracle training courses||http://education.oracle.com|
|Microsoft SharePoint Server resources:|
|Microsoft SharePoint Server 2007 site||http://sharepoint.microsoft.com/en-us/product/2007/Pages/default.aspx|
|Microsoft SharePoint Server 2010 site||http://sharepoint.microsoft.com|
|Microsoft knowledge base article: Description of Support for Network Database Files in SQL Server||http://support.microsoft.com/kb/304261|
Sun ZFS Storage Appliance Systems provides storage resources that are published using either CIFS or iSCSI protocol and can be used as CIFS shares or iSCSI targets respectively to hold SQL Server database files. When used by Microsoft SQL Server to store data files and logs, an iSCSI target volume is seen as a standard (local) hard disk by the Microsoft Windows operating system. It is typically addressed by SQL Server using a drive letter.
On the other hand, a CIFS shared folder located on a remote system is addressed by SQL Server using its Microsoft universal naming convention (UNC) path. When a CIFS share is used, these recommendations should be followed:
Figure 23. Error message displayed when a non-supported installation file location is selected.
Figure 24. Error message displayed when creating a database without Trace Flag 1807 set
|Revision 1, 08/01/2011|