iSCSI target/LUN noob...need some advice, please

[Redflee]

So I came from a very simple setup on a DNS-323...one volume, bunch of folders in the volume, mapped volume as drive letter on each attached PC for file access. Simple, but effective...family members could access all files w/out any log-ins, could even re-map the drive w/a little training from me if they brought home a new PC and wanted access to the DNS-323.

I'd like to do something similar w/the DS212...end goal is:

- Family accesses files on DS212 via the same drive letter (M:) w/out having to enter a PW or go through any other gyrations after I do a one-time setup on their PCs, and that one-time setup is simple enough that I can give them a little cheat-sheet on doing it if they have a need and I'm not around.
- Family can all access the same folders at the same time, e.g., they can all be opening/saving docs in the Documents sub-folders, saving/viewing pictures, listening to music, etc., subject to file locking for open files, of course.
- I can maintain an "admin" area (i.e., drive N:) where I can manage access to software/utilities so my wife doesn't try to "fix things" on her own resulting in doubling the time it ends up taking me to actually fix things.

The drives would contain the following types of files and the space they use would have to be able to increase/decrease dynamically.

M: - Everyone will be set up to access. Contains:

- Docs folder with one sub-folder per family member, and a shared folder for common stuff

- Media folder with Music, Photos and Videos sub-folders

- Utilities folder, various sub-folders w/stuff that it's OK for family members to access

N: - Only I will access. Contains:

- Various folders/sub-folders

So is using iSCSI LUN/Targets the best way to do this? Or should I simply create a "Family" folder and put the sub-directories into it and map that to M: on each computer, and an "Admin" folder and only map that to a drive on my computer? What are the benefits (or costs?) of using iSCSI?

And if I do use iSCSI, do do I create folders and then add them to a LUN, or create the LUN and then create folders in the LUN. I've read through the user guide, and while it tells you how to create a LUN/Target, I don't see anything on how to get folders/data into it. I actually created a LUN/Target and still don't see a way to put folders/data into it, nor info on how to access it from a laptop client...

And when creating a LUN/Target, do I have to enable "Allow multiple sessions from one or more SCSI initiators" if I want to allow multiple PCs/laptops to connect to the same LUN/Target?

found this (http://www.windowsnetworking.com/articl ... I-SAN.html) do I have to complete a set of steps like this on each client? Thinking that iSCSI may be more complexity than my simple home network requires..

Appreciate the help, and (hopefully) minimal rolling of the eyes over another noob...

EDIT: OK, I followed the steps on the link above and was able to mount the iSCSI target that I created on one of my laptops.

What I still haven't had time to process is getting data into the target (other than copying it there from the computer where I map to the target) or whether I'll be able to map the same target to multiple computers...

At this point it looks like I'm going to end up just mapping a drive to shared folders on the DS212, as that will be something that my family can manage in an urgent situation in my absence, and seems to greatly simplify getting data to the DS212 (using USB 3.0 to copy directly from a WD external backup disk to the DS212 via the back USB 3.0 port - haven't used USB 3.0 before - pretty darn fast.

Hope this helps someone else...

[LYuan]

Hello,

I'm by no means an expert when it comes to iSCSI, however, from what you've described for what you will be using the NAS for, a shared folder from the Synology device is probably your easiest way to go; especially if you want multiple devices connecting to a specific share.

Speaking in the most general sense, for at least what I use it for, iSCSI is for situations where you need a volume that looks like a local disk to the system that you are working on. For example, a boot volume. So far, I've found many uses for iSCSI (network boot, sql serve backup disk, etc.), but for what you need it for, and specifically your mention of having multiple devices connect to it, iSCSI is not the solution.

Cheers,

Larry

[Noah]

Speaking in the most general sense, for at least what I use it for, iSCSI is for situations where you need a volume that looks like a local disk to the system that you are working on. For example, a boot volume. So far, I've found many uses for iSCSI (network boot, sql serve backup disk, etc.),

Larry

I am no expert either, but it was my baby-understanding too what you write. I am planning to use it for MS Outlook (seems not to like a netwerk share), Firefox (keep one uniform profile on my PC and my laptop) and a financial accounting package that refuses to work unless I buy the triple expensive 'network version', even 'though I am the only user.

[myCloud]

IMO, iSCSI should be used as a last resort at home and only for programs that won't work with a network share mapped to a letter drive. You don't have to configure your whole DiskStation for iSCSI--just enough space for that program.

For family use, go to Control Panel -> User and turn on User Home Service. Create short, easy to remember names for each family member. This gives them a private home directory only they (and admin) can see or use. Don't put any family member names, including your own, in the administrators group. Just leave them in the Users Group. Unless you really need it, disable the Guest account. Log in as admin when you need to do admin things and log in as your user-level account when you don't. This helps prevent you from doing catastrophic things in day-to-day use and it shows you what your other users are experiencing.

For shared access, go to Control Panel -> Shared Folders and create a shared folder as a common file area. I named ours "shared". On that area, click Privileges setup, change Local Users to Local Groups and give the group "users" read/write access to it.

If you want to create a shared folder everyone except you has only read access to and you have read/write, stay in Local Users and set up permissions accordingly.

Most email clients store your mail in your profile. If possible, use IMAP with them to keep your email on the mail server, synchronized to keep a copy on the Mac or PC.

Firefox also keeps the settings hidden away in your profile. It would be unwise to try to use the same profile on multiple computers.