Questions tagged [san]

Short for 'Storage Area Network', a SAN is a network for block level storage. One or more controllers present logical drives (called LUNs) to one or more hosts through a switched fabric.

Structure of a Storage Area Network

SAN is short for 'Storage Area Network', and is different from 'Network Attached Storage'1 in the protocols used, and to some extent the physical network media2. SANs consist of the following major components:

  • One or more controllers. A controller is a specialised computer that fronts one or more physical storage arrays and presents a block level interface similar to a disk.

  • A fabric. A fabric is a network consisting of one ore more switches. SAN media such as Fibre Channel are packet based, switched protocols at layer 2-33, and carry an application level protocol for block or mode page communication.

  • One or more hosts. A host is a computer that mounts volumes off the SAN controllers. The SAN volumes appear much like local disks to the host, which interacts with the controllers using a block level protocol.

A controller presents volumes through a network address and a Logical Unit Number (LUN), essentially pretending to be one or more disks. Fibre Channel devices have an addressing scheme called 'World Wide Name' (WWN), which is roughly analogous to a MAC address on Ethernet.

LUNs allow a single controller to make multiple volumes available through the same network address. The controller sets up arrays within its pool of attached disks, and volumes can be sliced off one or more of the arrays to be presented as a logical disk, identified through a LUN.

Block Level Protocols

Fibre Channel, iSCSI and FCoE carry a payload that is very similar to the SCSI mode page and block protocols. Fibre Channel uses dedicated hardware (Optical and copper connections are available) and a dedicated layer 2 data link protocol. iSCSI and FCoE use ethernet layers 1 and 2, and iSCSI adds IP at layer 3 with the payload sitting on top of an IP stack.

Fibre Channel offers redundancy right down to the individual disks - a fibre channel disk has two complete F/C interfaces, and a backplane supports two loops. A controller may present an interface through fibre channel, but use different interfaces such as SAS for the disks. Dual-domain SAS disks have two SAS channels, allowing the implementation ofa a similar 'no single point of failure' capability. A proprietary protocol called SSA is also used on IBM hardware.

The redundancy is exposed to the operating system through a facility called 'multipathing'. Multiple host interfaces and switches offering multiple paths to the controllers are exposed to the host, which can route requests over one or more of these paths. This is not transparent in the way that IP routing is, the paths are exposed to the host operating system, which must manage the options for different paths to the controllers.

Other features of SAN controllers

Apart from high availability through redundancy in the architecture, SAN controllers implement intelligence behind the scenes. Some features implemented by various SAN controllers include:

  • Journalling and consistent snapshot mechanisms: The controller can maintain a journal and a redundant set of mirrored storage. The mirror can be frozen for a backup, allowing the backup to be taken from a consistent view of the data. When the backup is finished the journal can be played forward on the mirror to bring it into sync with the main volume.

  • Tiered storage: A controller can cache hot data in fast disk or SSD storage with cooler data moving off onto cheaper, slower nearline disks. This can provide better performance over the top of a large amount of realitively cheap (but slow) nearline storage.

  • Replication: A controller can replicate journalled changes to a remote site, either over a fibre channel link (single-mode fibre can run for several 10's of KM) or a wide area network.

  • Deduplication and Compression: The controller can compress data, or match data items to a canonical copy through a hashing mechanism. If repeated data is present the controller can save on the redundant storage.

1 Network Attached Storage refers to file server appliances using file level protocols such as NFS or CIFS. Some controllers can do both block and file level protocols.

2 Certain media such as ethernet can carry block and file storage protocols. Fibre Channel can carry IP traffic, but is not normally used for file level protocols such as CIFS.

3 iSCSI tunnels SCSI over IP, which is a layer 3 protocol, whereas FCoE uses the Layer 1 and 2 (physical hardware and ethernet frame format) to transport the SCSI payload.

53 questions
31
votes
2 answers

I/O requests taking longer than 15 seconds

Usually our weekly full backups finish in about 35 minutes, with daily diff backups finishing in ~5 minutes. Since tuesday the dailies have taken almost 4 hours to complete, way more than should be required. Coincidentally, this started happening…
Mark S. Rasmussen
  • 1,455
  • 1
  • 14
  • 20
17
votes
3 answers

Is there any benefit to defragmenting SQL indexes in a SAN environment?

Our SQL server lives on a SAN. It contains dozens of OLTP databases, some with several tables containing over 1m records. We have been running Ola Hallengren's index maintenance scripts weekly, and it runs for several hours each time. Based on the…
9
votes
4 answers

SQL Server - Separating data, log, and TempDB files on a SAN

I have a SQL Server connected to a SAN. Our new storage vendor recommends that all LUNs span the entire disk array, which is RAID5. I would normally request 3 separate LUNs (data, log, and TempDB) from the SAN administrator, but given the new…
SomeGuy
  • 2,053
  • 8
  • 35
  • 48
8
votes
2 answers

SQL Disk Setup Advice - TempDB, Log DB, Data file placement question

We have a very active database server with a ecclectic collection of applications running on it. Two of the busiest are a Laserfiche database that does document scanning and workflow processing all day long (average of around 2800 batch requests /…
RThomas
  • 3,446
  • 6
  • 30
  • 48
7
votes
2 answers

Why does innodb_flush_method = O_DSYNC provide such a performance boost with SAN-backed storage?

I've seen some people suggest that O_DSYNC should be used with a SAN. The MySQL docs have this to say about O_DSYNC in general: In some versions of GNU/Linux and Unix, flushing files to disk with the Unix fsync() call (which InnoDB uses by default)…
HTTP500
  • 359
  • 3
  • 13
7
votes
2 answers

Multiple SQL Server data files on same SAN disk

I'm currently in the process of creating a new database, and have previously only ever used a single data file and a single log file. I've done some research online regarding the benefits of multiple data files, but I've found mixed opinions…
Shadowfoxx
7
votes
2 answers

SAN block size for SQL Server on 4KB NTFS

A potential customer wants to evaluate our storage system. They run Windows 2008R2 x64 with 4KB NTFS on a virtual test machine they've sent us. They did not seem to know this at hand, so I think it's reasonable to assume that environment was not…
3molo
  • 297
  • 2
  • 4
  • 8
6
votes
2 answers

Slow checkpoint and 15 second I/O warnings on flash storage

Last couple of weeks we've been working on getting to the root cause of what could likely be the cause of the occurrence of these I/O issues and slowdown of the checkpoints. At first glance it looks to be clearly an I/O subsystem error and the SAN…
6
votes
1 answer

SQL Server on SAN, same LUN: one logical drive vs multiple

First, let me start by saying that I did notice there are multiple similar questions to this, but neither of them is exactly what I want to ask, and not one of them has a definite answer. Second, let me confirm that I do understand, that it's…
mrQQ
  • 81
  • 1
  • 4
5
votes
1 answer

SQL Server Database File Groups on a SAN: Relevant or Not?

I am about to build out a new SQL Server and I was planning to make extensive use of file groups. I expect heavy growth, and heavy read/write to 5 different databases on this server. I was planning on creating 2 additional file groups (one for user…
DMill
  • 191
  • 1
  • 2
  • 4
4
votes
1 answer

Storing Tlogs and data files on the same drive

I'm looking for some clarification of various things I've read. I understand it to be best practice to store your transaction logs on a separate drive (spindle) than where you MDFs and NDFs are housed. Does this same principal hold true in a…
AKDiscer
  • 1,395
  • 6
  • 28
  • 40
4
votes
1 answer

Should I align my SQL Server file and growth sizes with the block sizes on my SAN?

It was brought to my attention that our (Hitachi) SAN handles data in 42MB blocks. It is tiered storage so each block is evaluated when the director makes decisions as to when it should promote/demote storage to faster/slower storage. In the absence…
swasheck
  • 10,755
  • 5
  • 48
  • 89
4
votes
1 answer

Logical Drives - I/O aside, does SQL Server care?

I'm one of those Accidental DBAs. Engineer at a medium sized company who worked for years to work without a DBA. We've since hired some (at my recommendation) and they're great but I'm trying to find the answer to a conversation I'm having with one…
Boudreaux
  • 41
  • 1
3
votes
3 answers

Slow SQL Server authentication, but fast SAN, fast querying?

I am asking you after days of research but I think I don't have required skills to understand what is happening. I have a slow authentication on a SQL Server 2008R2, which leads to a timeout for the linked application. Sometimes up to 20s for a…
3
votes
1 answer

Sql Server & NetApp Sql Snap Manager

Does anyone use netapp's sql snapmanager? We are in the process of trying to decide if it is right for us. I know of the more popular features, but am trying to get some real life experience stories. Can anyone answer the following: What problems…
HunterX3
  • 544
  • 5
  • 10
1
2 3 4