Anonymous_User Absent Member.
Absent Member.
1228 views

Multiple IP addrs for cluster volumes?

We recently installed the Legato Networker 7.2.1 backup client that backs
up cluster virtual servers rather than physical volumes. The problem is
we have an isolated network for backups to keep traffic off the primary
LAN. However, the cluster virtual servers are not visible to the backup
server on the isolated LAN so we currently need to back them up over the
primary LAN. We would like to avoid doing this if possible.

Do you know if it would be possible to assign another secondary IP
address to each cluster virtual server so it would also be visible on our
isolated backup LAN? I'm thinking this probably would not work due to
SLP and SMDR issues.

The other thought I had was to establish a static route on each cluster
node that would allow the server to route the backup traffic from its own
mounted cluster volumes to the backup LAN.

Any other ideas on a solution? Thanks,

-Chuck
Labels (1)
0 Likes
9 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Multiple IP addrs for cluster volumes?

Hi,

I use multiple secondary IP addresses for my cluster volumes and it
seems to work fine.
Just add another 'add secondary ipaddress x.x.x.x' to your load script
and 'del secondary ipaddress x.x.x.x' to your unload script.

Adrian.


chuck_perilli_nospam@navyfederal.org wrote:
> We recently installed the Legato Networker 7.2.1 backup client that backs
> up cluster virtual servers rather than physical volumes. The problem is
> we have an isolated network for backups to keep traffic off the primary
> LAN. However, the cluster virtual servers are not visible to the backup
> server on the isolated LAN so we currently need to back them up over the
> primary LAN. We would like to avoid doing this if possible.
>
> Do you know if it would be possible to assign another secondary IP
> address to each cluster virtual server so it would also be visible on our
> isolated backup LAN? I'm thinking this probably would not work due to
> SLP and SMDR issues.
>
> The other thought I had was to establish a static route on each cluster
> node that would allow the server to route the backup traffic from its own
> mounted cluster volumes to the backup LAN.
>
> Any other ideas on a solution? Thanks,
>
> -Chuck

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Multiple IP addrs for cluster volumes?

Hi,

I use multiple secondary IP addresses for my cluster volumes and it
seems to work fine.
Just add another 'add secondary ipaddress x.x.x.x' to your load script
and 'del secondary ipaddress x.x.x.x' to your unload script.

Also, you may want to add some entries (backup servers isolated ip
address) to your sys:/etc/hosts file to be sure name resolution doesn't
redirect traffic over your primary LAN.

Hope that helps,
Adrian.


chuck_perilli_nospam@navyfederal.org wrote:
> We recently installed the Legato Networker 7.2.1 backup client that backs
> up cluster virtual servers rather than physical volumes. The problem is
> we have an isolated network for backups to keep traffic off the primary
> LAN. However, the cluster virtual servers are not visible to the backup
> server on the isolated LAN so we currently need to back them up over the
> primary LAN. We would like to avoid doing this if possible.
>
> Do you know if it would be possible to assign another secondary IP
> address to each cluster virtual server so it would also be visible on our
> isolated backup LAN? I'm thinking this probably would not work due to
> SLP and SMDR issues.
>
> The other thought I had was to establish a static route on each cluster
> node that would allow the server to route the backup traffic from its own
> mounted cluster volumes to the backup LAN.
>
> Any other ideas on a solution? Thanks,
>
> -Chuck

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Multiple IP addrs for cluster volumes?


you can add _many_ secondary ip addresses.

if you're concerned about bnandwidth consumption during backups, i
would investigate moving the tape drive onto your fibre channel
network.


--
Cheers!
Richard Beels
~ Network Consultant
~ Sysop, Novell Support Connection
~ MCNE, CNE*, CNA*, CNS*, N*LS


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Multiple IP addrs for cluster volumes?

Actually, fibre based backups are the next thing we are looking at. We
currently back up to a 24TB disk array and then to tape for off site
archive. Thanks,

-Chuck

>
> you can add _many_ secondary ip addresses.
>
> if you're concerned about bnandwidth consumption during backups, i
> would investigate moving the tape drive onto your fibre channel
> network.
>
>
> --
> Cheers!
> Richard Beels
> ~ Network Consultant
> ~ Sysop, Novell Support Connection
> ~ MCNE, CNE*, CNA*, CNS*, N*LS
>
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Multiple IP addrs for cluster volumes?

Thanks. I'll give it a try.

-Chuck

> Hi,
>
> I use multiple secondary IP addresses for my cluster volumes and it
> seems to work fine.
> Just add another 'add secondary ipaddress x.x.x.x' to your load script
> and 'del secondary ipaddress x.x.x.x' to your unload script.
>
> Also, you may want to add some entries (backup servers isolated ip
> address) to your sys:/etc/hosts file to be sure name resolution doesn't
> redirect traffic over your primary LAN.
>
> Hope that helps,
> Adrian.
>
>
> chuck_perilli_nospam@navyfederal.org wrote:
> > We recently installed the Legato Networker 7.2.1 backup client that

backs
> > up cluster virtual servers rather than physical volumes. The problem

is
> > we have an isolated network for backups to keep traffic off the

primary
> > LAN. However, the cluster virtual servers are not visible to the

backup
> > server on the isolated LAN so we currently need to back them up over

the
> > primary LAN. We would like to avoid doing this if possible.
> >
> > Do you know if it would be possible to assign another secondary IP
> > address to each cluster virtual server so it would also be visible on

our
> > isolated backup LAN? I'm thinking this probably would not work due to
> > SLP and SMDR issues.
> >
> > The other thought I had was to establish a static route on each

cluster
> > node that would allow the server to route the backup traffic from its

own
> > mounted cluster volumes to the backup LAN.
> >
> > Any other ideas on a solution? Thanks,
> >
> > -Chuck


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Multiple IP addrs for cluster volumes?


disk to disk and then to tape is the way to do it....


--
Cheers!
Richard Beels
~ Network Consultant
~ Sysop, Novell Support Connection
~ MCNE, CNE*, CNA*, CNS*, N*LS


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Multiple IP addrs for cluster volumes?

Richard Beels [SysOp] wrote:

> disk to disk and then to tape is the way to do it....


how about SAN to 6 drive fiber channel tape drive? 🙂

--
Joe Moore
Novell Support Forums SysOp
http://just.fdisk-it.com
http://www.caledonia.net/jmdns.html
http://www.caledonia.net/nesadmin.html
http://www.caledonia.net/jmttb.html
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Multiple IP addrs for cluster volumes?


that works too and is better than local-attached tape (YUK! 🙂 but
having the disk to disk is still less intrusive to user bandwidth.

plus you have a whole duped set of data on disk so if something (knock
on wood) would ever happen to the fiber channel disk trays, you still
have the sata tray that you can quickly unmask for the users to hit...


--
Cheers!
Richard Beels
~ Network Consultant
~ Sysop, Novell Support Connection
~ MCNE, CNE*, CNA*, CNS*, N*LS


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Multiple IP addrs for cluster volumes?

Richard Beels [SysOp] wrote:

> plus you have a whole duped set of data on disk


yeah, that is a nice little benefit

--
Joe Moore
Novell Support Forums SysOp
http://just.fdisk-it.com
http://www.caledonia.net/jmdns.html
http://www.caledonia.net/nesadmin.html
http://www.caledonia.net/jmttb.html
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.