Questions[veritas-cluster-server](server)

We are conducting bi-yearly resiliency test on a 4 node VCS cluster. With two applications running on nodes 1-3 and 2-4 resp. in active-standby mode.

When making a manual switch over, or a graceful shutdown on one node, application will nicely switch over to the other node.

When we turn off or reset a node however, it seems the absence of a handoff by the affected node triggers a reboot of the other cluster nodes. What's more, in case of a turn off, the remaining nodes do restart, but fail to join the cluster. When the killed server is resumed, all join again.

This is totally defeating the purpose of a cluster, obviously. Our vendor who provided the applications and the cluster software (with the hardware) proposes that such a case is not realistic and that servers always hand off nicely when going down.

We have no specialization in proprietary cluster technologies, so while we assume their statement is incorrect, we don't know what is possibly going wrong. I suspect however any commercially successful cluster software can handle these situations, but our implementation suffers configuration errors.

Any clue would be appreciated.

I run the vxprint -g rootdg on my Solaris machine (HW- NETRA T2000)

As we see here - rootvol & rootdisk7vol has missing lines (swapvol is OK)

How to fix the rootvol & rootdisk7vol in order to bring the missing lines as we see then in swapvol ?

  vxprint -g rootdg
  TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0  PUTIL0
  dg rootdg       rootdg       -        -        -        -        -       -

  dm rootdisk     c0t1d0s2     -        286617216 -       -        -       -
  dm rootmirror   c0t3d0s2     -        286617216 -       -        -       -

  v  rootdisk7vol gen          ENABLED  122112   -        ACTIVE   -       -
  pl rootdisk7vol-01 rootdisk7vol ENABLED 122112 -        ACTIVE   -       -
  sd rootdisk-03  rootdisk7vol-01 ENABLED 122112 0        -        -       -


  v  rootvol      root         ENABLED  253016064 -       ACTIVE   -       -
  pl rootvol-01   rootvol      ENABLED  253016064 -       ACTIVE   -       -
  sd rootdisk-02  rootvol-01   ENABLED  253016064 0       -        -       -


  v  swapvol      swap         ENABLED  33479040 -        ACTIVE   -       -
  pl swapvol-01   swapvol      ENABLED  33479040 -        ACTIVE   -       -
  sd rootdisk-01  swapvol-01   ENABLED  33479040 0        -        -       -
  pl swapvol-02   swapvol      ENABLED  33479040 -        ACTIVE   -       -
  sd rootmirror-01 swapvol-02  ENABLED  33479040 0        -        

I've got a Windows batch script which I'm trying to get Veritas Cluster Server to control using the process agent.

The batch script needs to run as a particular user, but when I try to online the resource I get the following error in the event log:

Source: AgentFramework

Event ID: 6532

Process:<<resource name>> Failed to launch the program <<path to batch script>>. Error = 1385

When I look up that error code here, it shows as:

Logon failure: the user has not been granted the requested logon type at this computer.

So the user account in question can't log on. That user account already runs some services, and has been granted the Logon as a service right. I've also added the Log on as a batch job right, but the problem persists.

So what rights do I need to assign to that account so that VCS can start a batch script as that user?

The operating system is Windows Server 2003, and VCS is version 5.0.

In the past I have used Veritas Cluster Server for HA clusters of Sybase and other databases at large financial institutions.

Now I am going to have locally written processes that could benefit from some similar behavior. e.g. "fail onto this machine if this process fails"

We will have VCS in the environment for various databases, so the overall skill set is not an issue; but this specific aspect.

Have you used VCS for custom application deployments? Was it worth it? Did it buy you much?

For the moment there's a lot of choices for setting up a Linux cluster.

For cluster manager: you can use Red Hat Cluster manager, Pacemaker or Veritas Cluster Server. The first one has the most momentum, the second one comes by default with RH subscriptions and the last one is very expensive and has a very good reputation ;-)

For storage: - You can replicate LUN's using software raid / md device - You can use the network using DRBD replication, which offers a bit more flexibility - You can use Veritas Storage Foundation technology to talk to your SANs replication technology.

Anyone has any recommandations or experience with these technologies?