Editing Best practices of using the Synology DiskStation to host iSCSI Storage

__NOTOC__
[[Image:iSCSI.png|400px|center]]


==Overview==
This article will cover advanced aspects of using the Synology DiskStation for dedicated iSCSI Storage deployment. It's best to read this article in it's entirety and enable which options which is best suited for the network. Please be sure to have an iSCSI Target created on the DiskStation before proceeding. Refer to the [[How to use the iSCSI Target Service on the Synology DiskStation]] for further information. This article is aimed for experienced network administrators. 


*[[Best practices of using the Synology DiskStation to host iSCSI Storage#Basic Environment Settings for the DiskStation|Basic Environment Settings for the DiskStation]]
*[[Best practices of using the Synology DiskStation to host iSCSI Storage#Block or File-level iSCSI Targets?|Block or File-level iSCSI Targets?]]
*[[Best practices of using the Synology DiskStation to host iSCSI Storage#Thin Provisioning and Over-allocation|Thin Provisioning and Over-allocation]]
*[[Best practices of using the Synology DiskStation to host iSCSI Storage#Using CHAP|Using CHAP]]
*[[Best practices of using the Synology DiskStation to host iSCSI Storage#Using Target Masking|Using Target Masking]]
*[[Best practices of using the Synology DiskStation to host iSCSI Storage#High-availability Computer Clustering|High-availability Computer Clustering]]


==Basic Environment Settings for the DiskStation==
* [[List_of_Notifications_by_the_Synology_Disk_Station|Enable Email notification]]
** This will set the DiskStation where it will send an email out for any maintenance error or report to the administrator of the DiskStation
* [[wikipedia:Gigabit_Ethernet|Use a 1Gbps Network]] or higher speed network
** Using a 1Gbps Network, which includes 1Gbps [[wikipedia:Network interface controller|NICs]], [[wikipedia:Category 6 cable| Ethernet cables]], and [[wikipedia:Network switch|network switches]] will ensure that the iSCSI performance will operate at it's best potential. Using a lower grade speed interface will result in not the best performance of accessing the iSCSI Target.
* Restrict Initiator NICs to iSCSI Storage duties only
** On the Initiator NICs, it's recommended to disable all other protocols and services except for protocols for the iSCSI Service (mainly IPv4). This will reduce interference from the other protocols, and optimize the NIC for performance for accessing iSCSI Storage.
* Assigned Fixed IP Addresses for both the DiskStation and all servers.
** This will ensure that IP Address for all of these devices will remain consistent after a network/power interruption. 


==Block or File-level iSCSI Targets?==
[[Image:Iscsi-layer.png|600px|center]]


*With the Synology DiskStation, there are two "levels" of iSCSI:
**'''Block-level''': Operates at the level closest to the RAID level, offers greater performance. Using a Block-level iSCSI will create a target whose capacity will be equivalent to the size of the RAID Volume. 
**'''File-level''': Operates at the File-system level and offers greater flexibility, where the RAID Volume storage can be shared between regular file sharing duties, and virtual storage space. 
**Please look [[How_to_use_the_iSCSI_Target_Service_on_the_Synology_DiskStation#Step_4:|here]] for information on how to create a target using Block-level or File-level iSCSI Targets.
**Be sure to select a redundant RAID Volume, such as RAID-1, RAID-5, or RAID-6 when creating either type of iSCSI Target, to ensure at least 1-disk redundancy against disk failure. 
*When to use Block-level iSCSI Targets
**If the intention of the DiskStation will be strictly that Virtual Storage purposes only
***Please ensure that that the File System of the Initiator is capable of addressing a large hard drive (some file systems cannot recognize targets which are greater than 2TiB, for example)
*When to use File-level iSCSI Targets
**When the DiskStation will be used for shared storage duties, for file sharing, and hosting virtual storage. 
**When the File System of the Initiator cannot recognize a large hard drive.
***For example, a DS1010+ with 5x2TB drives in RAID-5 would provide 7.28TiB of Redundant Storage, to use this for iSCSI Storage, if the Initiator File System cannot recognize greater than 2TiB, then, 3x2TiB File-level iSCSI Targets will have to be created. And the remaining 1.28TiB can be used for another iSCSI Target or for regular file-sharing duties.


==Thin Provisioning and Over-allocation==
[[Image:Iscsi-thinProvisioningOverAllocate.png|500px|center]]


*Note: Thin Provisioning and Over-allocation is available for file-level iSCSI Targets only
*[[wikipedia:Thin_provisioning#Overview|Thin Provisioning]] allows for storage to grow on demand, where if there's a 100GB target, 100GB of space on the physical volume will be allocated for the use of the iSCSI Target. However, the physical storage will not be committed towards the iSCSI Target until it is utilized by the virtual space. 
**A larger benefit of using Thin Provisioning is where the iSCSI Target storage can be [[How_to_use_the_iSCSI_Target_Service_on_the_Synology_DiskStation#Step_1:_2|adjusted]] on the fly, allowing targets space to grow instantaneously from 100GB to 200GB with a single click. 
*[[wikipedia:Thin_provisioning#Over-allocation|Over-allocation]] allows for an iSCSI Target to virtually have greater space than what is physically available. This is mainly beneficial for those environments where it's not known how much space is required - so it's easier to create a large storage pool immediately, and be concerned about the physical storage needs at a later point. 
**However, the physical storage will have to be updated eventually, if the virtual storage requirements exceeds what is physically available, then no more data can be written within the virtual space, which may result in lost or damaged data. It is the administrator's responsibility to ensure that there is plenty of physical space to accommodate the virtual storage needs. 


==Using CHAP==
[[Image:Iscsi-chap.png|500px|center]]


*[[How_to_use_the_iSCSI_Target_Service_on_the_Synology_DiskStation#Step_6:|Setting CHAP]] will basically require a username and password to be used before an iSCSI Initiator will have access to an iSCSI Target. Using CHAP is recommended to ensure that only specific users will access the iSCSI Target. 
*Using Mutual CHAP is even a higher level of security, where both the iSCSI Initiator and Target will authenticate each other before access of the Target can be used.
*Please be sure to use strong passwords (letters, numbers) to help aid in the prevention of unauthorized users accessing the Target. 


==Using Target Masking==
[[Image:Iscsi-InitiatorMasking.png|250px|center]]


*[[How_to_use_the_iSCSI_Target_Service_on_the_Synology_DiskStation#Step_5:_2|Target Masking]] is where specific Initiators will have different capabilities to the iSCSI Target. Initiators can be denied access, have read only access, or have read/write access. 
*For securing iSCSI Targets against unauthorized access/discovery by random users on the LAN, it's best to set the default actions to deny all users, and select specific Initiators to have read/write or read only access.


==High-availability Computer Clustering==
[[Image:Iscsi-clustering.png|250px|center]]


*[[wikipedia:High-availability cluster|High-availability Computer Clustering]] is a service where multiple computers are communicating to the same iSCSI Target, and both computers are aware of the changes being to the iSCSI Target. Computer Clustering environments is used in a specific environments, and is recommended for experienced network administrators only. Using the DiskStation to host storage for a Computer Clustering environment requires the following
**Proceed to the [[How_to_use_the_iSCSI_Target_Service_on_the_Synology_DiskStation#Step_3:_2|iSCSI Target Advanced Options]] of the Synology DiskStation and enable '''Allow multiple sessions from one or more iSCSI Initiators'''
**Use a Cluster-capable file system; <font color=red>failure to use the correct file system can and will result in data loss and corruption</font>.
***A visual example would be to take a USB Hard drive and connect it to two different computers. Under normal conditions, neither computer would be aware of the other computer's changes, thus if they both access the same area of space on the hard drive to read/write data, data loss will occur.
**Known cluster-capable file systems are
***[[wikipedia:NTFS|Microsoft NTFS]]
****<font color=red>Requires iSCSI SPC-3 Persistent Reservation, available in Windows 2008 Server or Windows 2003 Clustering Services</font>
****[http://www.synology.com/support/download.php?lang=enu Synology DSM 3.0] or higher is required on the DiskStation.
****It's not recommended to enable compression abilities on the NTFS Volume
***[[wikipedia:OCFS|Oracle OCFS]]
***[[wikipedia:VMware VMFS|VMware VMFS]]


==Further Reading==
* [[How to use the iSCSI Target Service on the Synology DiskStation]]