FAQ

   


FAQs by Category 

Installation Guide



 
 
FAQ No.:00192 
Category:Advanced Settings 

 
Question:How to use Curtain e-locker to protect NAS through iSCSI?
 
Answer:Currently most NAS storage servers are running Linux and they do not allow people to install program/software on the NAS. That means we cannot install Curtain Server Plug-in on a NAS storage server, to protect the share folders. Alternatively, we can protect the NAS by mounting it to a Windows server as local virtual disk through iSCSI. Firstly, you need to create iSCSI LUN (logical unit) on the NAS, and then use Windows iSCSI Initiator to create a virtual disk on the Windows server. Finally, you can share the virtual disk and protect it by Curtain e-locker.

P.S. We used Synology DiskStation to demonstrate how to do the setup. The interface and naming will be different if you are using other NAS servers.

Steps to create iSCSI LUN (logical unit) on NAS:
1. In my Synology DiskStation, go to DSM (DiskStation Manager), and click "Main Menu > Storage Manager" as below.


2. In the "Storage Manager" page, select the "iSCSI LUN" item as below. By default, there is no iSCSI LUN in the DSM system.


3. Click the "Create" button, it will pop the setup page. As follow figure:


4. In the "Choose a LUN type", select the "iSCSI LUN(Regular Files)" type, and click the "Next" button. As follow figure:


5. Set up iSCSI LUN properties in this step, we suggest you to set up the "Capacity(GB)" property only, the capacity room is up to you. If you have already set up, click the "Next" button. As follow figure:


6. In this step, you will create a new iSCSI target. Input the "Name" first, we suggest you to enable the CHAP and set up the password. To prevent anonymous use the iSCSI target, please follow figure:


7. Confirm the settings that you have set up, if no problem, click the "Apply" button to create the iSCSI LUN. As follow figure:


8. Now you have created the iSCSI LUN, in the "Storage Manager" page, you can see the iSCSI LUN that you have created. As follow figure:



Map the iSCSI Target to a local virtual disk on the Windows

9. In the Windows start menu, click the "Start Menu" -> "Administrative Tools" -> "iSCSI Initiator". As follow figure:


10. If pop up the follow tips when click the "iSCSI Initiator", please click the "Yes" button.


11. In the "iSCSI Initiator Properties" window, select the "Discovery" page, and click the "Discover Portal…" button. As follow figure:


12. Please input the NAS'IP. As follow figure:


13. Click the "OK" button, and return the "Targets" page, now you can see a new target in the targets list view. As follow figure:


14. Select the new iSCSI target in the list view, and click the "Connect" button. As follow figure:


15. Click the "Advanced…"button. As follow figure:


16. In the Advanced Settings window, check the "Enable CHAP log on" button, and input the name and password that have set up in step 6. As follow figure:


17. Click the "OK" button, it will return to "iSCSI Initiator Properties" window, you can see the new iSCSI Target's status have changed to "Connected". As follow figure:


18. Click the "OK" button to exit.

19. Open the Windows Disk Management, appears a new disk. As follow figure:


20. Select the new disk and right click, click the "Online". As follow figure:


21. Select the new disk, and right click, select the "Initialize Disk". As follow figure:


22. Select the "MBR" partition style, then click "OK", and right click the new disk, select the "New Simple Volume…". As follow figure:



23. Create "New Simple Volume", click "Next" to continue, then completing the New Simple Volume Wizard. As follow figure:


24. Now you can see a new volume "E:" appears in the Windows Explorer. As follow figure:


Share the virtual disk and protected with Curtain e-locker

25. Share the virtual disk.

26. Open the Curtain Admin, set the share virtual disk protected (Refer to FAQ 00085).

27. Now re-launch Curtain Client, and mapping protected network drive .

P.S. NAS share folder permission need to migrate to the Windows server manually by Administrators.