KernSafe Technology

I've tested the product, and it just doesn't do what I expect it to, so I need some help understanding how this works.

You have a target, which sits on a server and writes/reads requests to something

You have an initiator (client), which sends these requests.

Being that iSCSI is not NAS, what is the point of this storage? In other words, how do you access this stored information? The clients are not accessing online file shares, as the data between them for the same target is not concurrent. How do you concurrently access the data you stored somewhere?

I know my question might sound like I couldn't pour myself a glass of water, and trust me, that's the way I feel!

-Chicken

It seems that I have discussed before in the forum, you can visit:
viewtopic.php?f=5&t=268
You need not only ISTORAGE server, but also another software like metasan.

SpewChicken wrote:I've tested the product, and it just doesn't do what I expect it to, so I need some help understanding how this works.

You have a target, which sits on a server and writes/reads requests to something

You have an initiator (client), which sends these requests.

Being that iSCSI is not NAS, what is the point of this storage? In other words, how do you access this stored information? The clients are not accessing online file shares, as the data between them for the same target is not concurrent. How do you concurrently access the data you stored somewhere?

I know my question might sound like I couldn't pour myself a glass of water, and trust me, that's the way I feel!

-Chicken

The biggest advantage of using iSCSI instead of a SAN is that the iSCSI disk appears to be a "local" hard disk for the machine(s) accessing it. Meaning that you can set permissions on the files, run software that has to be installed locally, etc. A SAN requires the OS on the SAN to do that work. Example:

Take one HP DL320s. Add 9+ TB of drive space for employee personal drives. Now this is a single (yes, as in ONE) CPU server. Even running local backup routines can spike the CPU on the server. Add several hundred or thousand people logging into it and you have terrible performance.

So instead we use that server as an iSCSI device and mount those drives on a different machine. Now the CPU/Memory load is handled by the more than adequate DL380 G6 with 16 GB RAM. The CPU on the 320 only needs to handle the iSCSI software, so it has plenty of power. And by hooking the iSCSI to a switch attached to the 380's secondary NICs, we have plenty of bandwidth.

Even for smaller stuff. Need to allocate 200 GB for your personnel department? Setup a iSCSI partition and attach it straight to your Personnel server. Your document management system need more space? Same thing. By buying seperate chassis that are designed to handle lots of drive space you can keep your drive requirements on your servers lower and concentrate on CPU/Memory for the front ends. Those large storage volumes also allow for shadow-copies with their spare space, greatly easing backup woes.

Now if you start clustering things like Exchange, SCCM or anything like that then iSCSI or NFS is the only way to go as that type of software cannot run on a convention SAN share and has to be mounted on a block-level device.

There are many other reasons, hope that gives you an some ideas