Correct to replicate you will need 2 - iSCSI servers. Let me try another way as well.
Server A config:
FC HBA ---> (Direct connected or with Switch) to FC Storage system (DotHill, Infortrend..whoever).
iSCSI Target Logical Volumes created from FC Storage then marked for replication.
Target Volume is set to Source then add mirror IP Address of Destination Server.
Then select the Logical Volume to replicate start task.
Server B config:
FC HBA ---> (Direct connected or with Switch) to FC Storage system (DotHill, Infortrend..whoever).
iSCSI Target Logical Volumes created from FC Storage then marked for replication.
Target Volume is set to Destination then add mirror IP Address of Source Server.
The replicating Source Target Volumes where the data will be replicated to the Destination server not the configuration.
Never mind the DSS on the front end this was incase you needed additional 99.999% uptime and replying to your needs incase this was what you where interested in. But let's drop that configuration as this was not what you need and if you did I would send you a design on power point instead of text.
If you could be so kind as to add your knowledge on the VMware section of this Forum as did others to help them as well
Unless I am missing something you should be successful with our iSCSI-R3 Ent. version as we use lvm2 as well and the open-iscsi we support .
I am interested in your powerpoint...I just didn't get the point you wanted to make with the dds setup...
And I still don't see why replicating the volume data as it is on shared storage...I got the feeling you want to give the standby server it's own FC volume so all data will be available twice on the FC array...When I import a FC volume on a linux box and create volumes on it using LVM2 I can have any other linux box import the same FC volume and it sees all LVM2 created volumes...So only thing left to replicate would be target config, snapshot schedules and all other sorts of config files...
I guess it should also be possible when I have a single Open-E box using a FC backend and it completely dies to get my data back on line without anything missing ? A simple config backup of the Open-E box should do the trick (if possible)
I would be happy to post some stuff in the vmware section (rename to virtualisation software ??? ) As soon as I have a beta for the next version I will post some howto's...
For know linux users that do not have serious experience with iscsi can use Kiscsiadm a small desktop tool to makes iscsi initiator management very easy. http://sourceforge.net/projects/kiscsiadm/
If you do not plan on using the DSS for the front end and 2 x iSCSI-R3 Ent. on the back using the initiator built in from the DSS then will not be part of your needs.
We currently do not replicate the config (snapshot, backup, users….) only the iSCSI Volumes. But the config can be stored on the module and on your host system.
If possible download the Demo-CD. Over 90% that do usually have all the answers they need. New release to come out next week 1.21 for DSS.
We appreciate any updates to the VMware section and others will too.
Yes this is a great initiator management tool to for sharing this to every one.
I guess it shouldn't be a problem to backup config for each host system...that creates a setup where it is fairly easy to restore everything to a spare node...
For our case the iSCSI R3 dom's would fit great into the plan, but I think we will use the DDS dom's...NFS sharing is always nice to have and the other features might be handy some time as well...
I will download a demo version to try some stuff...but it will be hard to simulate my setup without the FC hardware available
When I find something usefull for this forum I will post it !
Reply With Quote
