cancel
Showing results for 
Search instead for 
Did you mean: 

Sybase private installation with non cluster edition

suznCB
Participant
0 Kudos

Dears,

referring to this page:

https://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc00768.1570/html/ase_ce_u...

how can I implement as private installation (knowing that we have Sybase ASE15.7, with EE license , and license type is AC ),

as initial thinking, we are planning to do the first installation on the first node on SAN storage drive, then delete the installed directory SYBASE, and do the second installation on the second node on the same SAN drive, so two nodes will have syabse (SQL, BCK) services, and share the installed directory,

is there a better solution for that?
kindly note that our two nodes are linked to each other by windows fail over cluster (OS on both is windows server 2019)

Regards

Sriram2009
Active Contributor

Hi Suzn

Are you want to build the systems in a private environment without the windows failover cluster?

For this you can do the standalone installation (SAP CI & DB are same host)

Regards

SS

suznCB
Participant
0 Kudos

Thanks for your comment

I want to have two separate ASE installation on the same SAN drive,

maybe according to my browsing, it is implemented by using ASE HA on top of OS HA,isn't it?

Accepted Solutions (0)

Answers (3)

Answers (3)

Sriram2009
Active Contributor
0 Kudos

Hi Suzn,

It is not two ASE instances, it is a single ASE instance in the windows failover cluster(DB virtual name & IP) it can be active on any one of the nodes ( not on both nodes).

During the time of Failover testing, all the active connections are getting disconnected, it is a normal process of Windows Failover cluster, during the failover process, all the DB services, disks, virtual names & IP getting offline in the active node, and failover to the secondary node became online.

Regards

SS

c_baker
Employee
Employee
0 Kudos

If license type is 'AC' what application is running on top?

Chris

Sriram2009
Active Contributor
0 Kudos

Hi Suzn,

Without a Windows failover cluster, you may not install the ASE in two different nodes, because both nodes are hostnames are different, when you are installing the on a Windows Failover cluster, the DB instance is having one virtual name of both physical nodes.

Regards

SS

suznCB
Participant
0 Kudos

thank you

I know and I want to have a windows cluster, but I want also to have two ase instances,

please help me in the following:

we have a windows cluster of two nodes , they are map to SAN , on SAN we have a ssd hard (let's say E) it will be dedicated for sybase directory,

on the first node of cluster, we installed the sybase on E drive,

then to not rewrite above it, we deleted the sybase installed directory on E , and install ase on the second node also on E,

now the two nodes have ASE services, and view the installed directory which is in E,

when I try to test HA , I stop the ase service on the up node, and it took time to start on the second node, I want to minimize this time , for that I'm thinking about some solution that has:

two ase instances running but only one of them is up and users connected to it so during failover the ase in the second node is already running and clients will not wait a time to reconnect,

then I read something about ASE HA, which I ask for.