Networker

[Networker] 64 bit linux

2009-05-29 17:21:14
Subject: [Networker] 64 bit linux
From: David Gold-news <dave2 AT CAMBRIDGECOMPUTER DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 29 May 2009 17:17:19 -0400
...and I ran into a situation where iscsi connected devices didn't work properly when using 32-bit networker on 64-bit linux. Never quite figured out why (although we had some theories about 32 versus 64 bit calls and iscsi code), since 64-bit NetWorker fixed it.

--Dave

Date:    Thu, 28 May 2009 21:55:43 +1000
From:    Preston de Guise <enterprise.backup AT GMAIL DOT COM>
Subject: Re: Running the Linux 64-bit package with the 2.6.x kernel may result in crashes

On 27/05/2009, at 22:52 , Clark, Patti wrote:

> We had been using 64-bit networker on Red Hat ES 4 server for a =20
> couple of years.  There were a number of crash issues, a patched =20
> nsrexecd, etc.  When 7.3.3 came out we switched to 32-bit and have =20
> had fewer problems.  There were no visible advantages to staying on =20=


> the 64-bit version.

My primary lab server has been 64-bit Linux for some time, with 64-bit =20=

7.4.[234] and more lately, 7.5.1. Being a lab machine, it gets quite a =20=

work out, but never a huge amount of daily data transfer.

For the most part I don't see many environments actually hugely =20
needing 64-bit NetWorker installs unless their primary platform of =20
choice is only available in 64-bit (e.g., Solaris/Sparc).

Typically when I've heard of 64-bit NetWorker issues on Linux they've =20=

been device related =96 I suspect if you've got, say, a backup server =20=

that only has disk backup units, with tape only on storage nodes, =20
you'd find 64-bit NetWorker not much of an issue for the server.

I've also noticed, but never been able to pin down, that Linux is =20
particularly ...distasteful... at error recovery on tape devices where =20=

you have the robot and a tape drive on the same SCSI chain, regardless =20=

of 32- or 64-bitness. Keeping robot heads on dedicated SCSI chains or =20=

using fibre-channel (even via fibre-channel bridges) increases the =20
reliability of NetWorker on Linux in relation to devices by (IMHO) =20
about 1000%.

Cheers,

Preston.

--
Preston de Guise


===================================
David Gold
Sr. Technical Consultant
Cambridge Computer Services, Inc.
Artists in Data Storage
Tel: 781-250-3000
Tel (Direct): 781-250-3260
Fax: 781-250-3360
dave AT cambridgecomputer DOT com
www.cambridgecomputer.com

===================================
 ----------------------------------------------------------------------------
*Any ideas, suggestion or comments are mine alone, and are not of my company*
To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the body of the email. Please write to networker-request 
AT listserv.temple DOT edu if you have any problems with this list. You can access the 
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

<Prev in Thread] Current Thread [Next in Thread>
  • [Networker] 64 bit linux, David Gold-news <=