Veritas-bu

[Veritas-bu] AIX - Sybase - SQLBackTrack

2006-06-28 14:14:21
Subject: [Veritas-bu] AIX - Sybase - SQLBackTrack
From: jlightner at water.com (Jeff Lightner)
Date: Wed, 28 Jun 2006 14:14:21 -0400
Wow this takes me back...

I used to work in a shop where we had Sybase and SQLBackTrack running on
HP-UX.  There too we ran into issues with shared memory because the
Sybase available was compiled as a 32 bit binary.  Even though the OS
itself was 64 bit we had the limitations of a 32 bit host for Sybase
(e.g. 1.75 GB Shared Memory limit).  Luckily HP had Memory Windows
available which allowed us to create multiple windows that allowed for
approximately 2 GB shared memory each.  We were able to get Sybase to
run an instance in each of these windows and thereby get around the
limitations of the 32 bit binary.  I'd hope that after all these years
Sybase has 64 bit binaries and that your hosts have 64 bit processors.
If the binaries are 32 bit you may want to investigate whether the OS
has something akin to HP memory windows.

-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of
Jack.Thweatt at protective.com
Sent: Wednesday, June 28, 2006 1:42 PM
To: veritas-bu at mailman.eng.auburn.edu
Subject: [Veritas-bu] AIX - Sybase - SQLBackTrack


Good afternoon,

We have an unusual configuration we're having quite a bit of trouble
trying
to get to run and I was wondering if anyone may have seen something
similar.

We are running NBU Enterprise 5.1MP4 under a Win2003 framework.  We need
to
migrate several AIX servers from production TSM to complete our
transition
to NBU.  We are testing a production like configuration of AIX on
several
RS/6000's with the NBU5.1MP4 client.  These servers are running Sybase
along with SQL BackTrack.  SQLBT handles the database dumps, which are
then
backed up with NBU to a DSSU via BMC's OBSI module (an API to NBU).
I've
worked with Symantec in ensuring the NBU / DSSU configuration for
maximum
performance, but the transfer to disk is still unacceptable when
compared
to TSM.  We have also worked with Sybase, BMC and IBM support.  We have
pinned the problem down to Sybase requesting shared memory which is not
present.  Per IBM, the shared memory cannot be increased.  We have cases
open with both Sybase and BMC, and the latest effort is focused on
reviewing SQLBT to see if it might not be keeping proper track of the
shared memory id's.

I would greatly appreciate hearing from anyone who may have seen such an
issue.

Thanks,

Jack Thweatt
205.268.5646  Office
205.337.8909  Cell
205.268.3474  Fax
jack.thweatt at protective.com




-----------------------------------------
Confidentiality Notice: This e-mail communication and any
attachments may contain confidential and privileged information for
the use of the designated recipients named above. If you are not
the intended recipient, you are hereby notified that you have
received this communication in error and that any review,
disclosure, dissemination, distribution or copying of it or its
contents is prohibited. If you have received this communication in
error, please notify me immediately by replying to this message and
deleting it from your computer. Thank you.

_______________________________________________
Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


<Prev in Thread] Current Thread [Next in Thread>