 | ||
| Configuration requirements and best practices | ||
|---|---|---|
| Prev | Reviewing the prerequisites | Next |
Review the following configuration requirements and best practices:
The system and boot volumes must reside on a separate disk (Harddisk0) from the dynamic volumes used for the SQL user-defined databases and split-mirror snapshots.
Disk groups must be of a Storage Foundation 4.0 or later version. Upgrade any disk groups created using an earlier version of Volume Manager for Windows before creating Quick Recovery snapshots.
Quick Recovery snapshots are supported only on volumes belonging to an SFW dynamic disk group. They are not supported on volumes belonging to a Microsoft Disk Management Disk Group. For more information on Microsoft Disk Management Disk Groups, see Storage Foundation Administrator's Guide.
Database, transaction logs, and FILESTREAM filegroups must be stored on disks within a single dynamic disk group.
Database, transaction logs, and FILESTREAM filegroups should be on separate disks so that disk failure does not affect anyone of these filegroups.
User-defined database, transaction logs, and FILESTREAM filegroups may not be stored in the same volume as the SQL Server program files or system data files.
In order to perform a roll-forward recovery to the point of failure, database, transaction logs, and FILESTREAM filegroups must be in separate volumes.
Locate snapshot volumes on separate disks from any database, log, and FILESTREAM filegroup volumes so that the snapshot process will not interfere with database operations.
Locate the snapshot volumes for each database on separate disks from snapshots of other databases. This is recommended so that the process of creating the snapshot of one database doesn't interfere with any operations on another database.
Transaction logs should always be configured in a redundant layout. The preferred software layout is RAID 0+1 (mirrored striped) volumes as this provides better read and write performance than RAID 1 (mirrored) alone. The transaction log will generate the most I/O and thus should use the highest performance disks available.
The preferred layout for the database is hardware RAID 5, software RAID 1 (mirrored with logging enabled) or software RAID 0+1 (mirrored striped).