The iSCSI-R3 Enterprise is a USB module not IDE, so make sure the motherboard has this USB pins available (we ship with an Internal USB cable though).
Your hardware setup looks good to start with for your RAID controller, CPU and RAM (start with 4GB). We have new drivers for the 3Ware so either choice is yours or contact 3Ware to see what they would recommend for growth capacity as this is called migrating. After migrating you need to go into the Console screen in Extended tools CTRL + ALT + X then use the PV Resizing tool. Then go to the Volume Manager (please read the manual for this topic) - then add additional space to your iSCSI volume. You will have to restart the Target Volume so the client will see the added space.
You will need to setup an iSCSI Target for each client as we do not support multiple initiators connecting to the same Target.
There is no setting for an idle shutdown for a mounted volume outside of just removing the Target from the Target Manager then enabling when you need to.
When Snapshot is scheduled to run it is exported via iSCSI and will be visible as new
drive which you shouldn't format. So if you have deleted data then copy from the Snapshot.
When a snapshot is taken the whole data is frozen on your local volume
and any changes you made are written in a Snapshot volume.
When it is fulfilled, the end time taken from schedule is reached, or the
Snapshot is manually closed the changes are committed.
Snapshot uses copy-on-write function to do this and is not continues. General rule for sizing the Snapshot is based on that amount of changes you believe will take place then times 3 for the Snapshot volume size. For example if you will have 50GB of changes then your Snapshot should be 150GB or more as a general rule.
You can test this to get a better understanding with sample data before committing to operations.
Link below to provide a better understanding of COW "Copy on Write" with our Snapshot. Other then that it is very simple.
I have the IDE thing, so I posted to the wrong forum (again) I guess - sorry.
Another question about hardware: For my iSCSI server, will more cpu cores or a hi GHz CPU be faster? I don't know how threads are handled in the open-e os when doing scsi->tcpip - so is a 2,6 GHz Intel core2duo (2 cores) faster then a 2,4ghz core2quad (2x2 cores) or vice versa?
About RAM: does RAM work as an additional read/write buffer on the system? If I add 8 GB of RAM, will i have a 8 GB (minus system) RAM cache for burst inputs?
So I need to use a SAN software if I want to have multiple users connect to one huge target - that's fine, I still don't need a metadata controller so I'm off a lot cheaper even if I use 10GB ethernet.
Still unsure about the snapshot issue, I opened a separate post about that. I got the basic technology behind snapshots but still I feel challenged at implementing the right snapshot strategy.
I tested some more with the different initiators. After having several connection lockups with the globalSAN initiator, I started up Parallels Workstation on my Mac and connected my VM to the target (win xp with ms iscsi initiator). I did this yesterday night. This morning, I accessed the target in my VM and it worked like a charm, everything behaved like it should, so I guess it's a globalSAN initiator issue. Oh well.
Yes the iSCSI-R3 Enterprise is a USB module not IDE. All IDE modules are EOL "End of Life" we do not sell this anymore only the iSCS-R3 Enterprise, NAS-R3 Enterprise and DSS.
Many engineers have stated the Dual Cores (fast GHz 3.0 and above) with highest amount of Cache on the CPU is best. The way this works is that our cache uses all available free memory strictly assigned to cache and this will rarely be released during write or read options until you reboot the system. The reason is this makes operations on storage much faster to have it available all the time instead of drawing from it when needed (another wait process that would hinder performance).
Yes you will need SAN software to connect to the same target. This is very expensive software almost 8 times more the cost of our iSCSI product. Look to these companies for more information.
thanks again for your thorough reply. For my OS X clients, I also found http://www.dieagenten.de/metasan.htm - attractive pricing. I have to fight 1000$/liscense from Apple's Xsan so I guess I'm fine.
OK, so no quadcore but rather a faster dualcore CPU. Thanks!
Reply With Quote