Linux Archive

Linux Archive (
-   CentOS (
-   -   iscsi storage, LACP or Multipathing | Migration or rebuild? (

Svavar Örn Eysteinsson 08-15-2012 02:28 PM

iscsi storage, LACP or Multipathing | Migration or rebuild?
Hi Götz.
I'm running Centos 6.2 on a Proliant DL380 G7 server connected to a HP
Lefthand P4500
using multipath, and ALB(Adaptive Load Balancing) on the Lefthand box it

Regarding, multipath vs bonding read this ->

You will need to go through the storage manual for red hat enterprise 6
and read some chapters
regarding configuring your options/needs for your scenario.

Best regards,

Svavar O - Iceland


Götz Reinicke wrote:
> Hi,
> I do have one iscsi storage with 4 GBit nics of which currently only one
> is configured with an ip and which is in productive use by one cent os
> 6.3 server.
> Doing some research brought me to the idea to use some nic bonding or
> multipathing for that storage, but multipathing I did about four or five
> years ago only once :)
> Furthormore I can't find the ultimate answer (may be there is not such)
> what will be better for us:
> bonding or multipathing.
> The storage is used for backup; it's connected to an backupserver which
> pulls data from different servers ... may be at the same time or one
> after an other. The server uses two bonded nics to the LAN.
> My question regarding the setup is, what might be good or better:
> bonding or multipathing. We'd like to increase performance and nic
> failover if one link breaks.
> If multipathing is to be preferred, is it possible to preserve the data
> currently saved on the storages ext4?
> And googling shows up a lot of different how tos and the redhat doc; but
> I din not found one describing a straight forward setup.
> So thanks a lot for any suggestion or comments!
> Regards . Götz
> _______________________________________________
> CentOS mailing list

CentOS mailing list

All times are GMT. The time now is 11:55 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.