this is the only node of the cluster1 that I am trying to start VCS.

as my experience, after SFHA installation, the veritas can start automatically with Solaris OS boot.

the below is the procedure of my operation

1.after SFHA installation, I found it cann't run "vxdisk list" command, it showing "Configuration daemon is not accessible"

so I follow the article and solved it https://www.veritas.com/support/en_US/article.TECH67777

2.then, i completed the synchronization between cluster1 and cluster2

3.when I try to config GCO with gcoconfig, it cann't work as well.at that time,I reboot the Solaris OS once and found it persist after reboot. so I try to start veritas with command "hastart -onenode" then I can config the GCO.

4.I completed all veritas configuration cluster1 and cluster 2 both.

5.I reboot the node of cluster1 and cluster2, after reboot, I found only the host of cluster1 cannot accese by VCS_Cluster_Manager_Java_Console. it show VCS ERROR V-16-10-106. But the host of cluster2 is fine.

please advice me.thanks in advance.

the detail information has been attached in files.

 this is the only node of the cluster1 that I am trying to start VCS.

as my experience, after SFHA installation, the veritas can start automatically with Solaris OS boot.

the below is the procedure of my operation

1.after SFHA installation, I found it cann't run "vxdisk list" command, it showing "Configuration daemon is not accessible"

so I follow the article and solved it https://www.veritas.com/support/en_US/article.TECH67777

2.then, i completed the synchronization between cluster1 and cluster2

3.when I try to config GCO with gcoconfig, it cann't work as well.at that time,I reboot the Solaris OS once and found it persist after reboot. so I try to start veritas with command "hastart -onenode" then I can config the GCO.

4.I completed all veritas configuration cluster1 and cluster 2 both.

5.I reboot the node of cluster1 and cluster2, after reboot, I found only the host of cluster1 cannot accese by VCS_Cluster_Manager_Java_Console. it show VCS ERROR V-16-10-106. But the host of cluster2 is fine.

please advice me.thanks in advance.

the detail information has been attached in files.

Hi Community,

  I'm having a problem in my cluster, I'm having two nodes in cluster,I'm trying to add new node to the cluster, when I booted up the new node I got 

and errors on the current cluster, I guess the new node is trying to join the cluster.

V-16-1-10112 
System (xxxxxx) - Membership: 0x6, DDNA: 0x4

V-16-1-10077 
Received new cluster membership 

 LLT heartbeat link status changed. Previous status = e1000g0 UP e1000g2 UP; Current status = e1000g0 UP e1000g2 DOWN.  

  Now interface e1000g2 is down, but I've checked the phisical links, they are all up and running, please advise how to resolve this issue.

BR

Luay

Hi,

I am in need for more detailed information on the CleanProgram Attribute for the Application Resource.

I could not find any information in the documentation (including the Application Agent Configuration Guide) regarding this topic.
Is there any more-detailed information available somewhere?

The Veritas documentation only states:

It's an optional Attribute.
It's an executable file that forcibly kills the application and performs cleanup taks.

In the past I was not using this Attribute. Only the StartProgram Attribute, StopProgram Attribute and a MonitorProgram Attribute. Very recently I was trying to implement this CleanProgram Attribute. The script should kill a certain process and remove a lock-file.

My questions:

• When does the CleanProgram kicks in?
  Is it only when the StopProgram fails multiple times as definied in the xx?
• Can I include a new start of my actual application?
  Or will this be done by the StartProgram Attribute?
• Should you include any Veritas exit code to return the status to Veritas Cluster Server?
  Or can I just trust my MonitorProgram to handle this?
• Are there any sample CleanPrograms available?

Thanks in advance,

Sander

Hi

Can I create an extra dependency between this two main Resources I have?

I have a Service Group with two main Agent Resources, next to the usual Resources (storage, networking, ...) :

• an Application Agent Resource Type for my application
• a Database Agent Resource Type for my database

1. The first one, is for a custom application. I am using a StartProgram Attribute to start it, a StopProgram Attribute to stop it. For monitoring the application, I am using only the MonitorProgram Attribute (so no PIDFiles Attribute and no MonitorProcess Attribute). Which will check for a process from the systems process list output and returns the correct VCS exit code. The output displayed by the PS command does not match exactly, hence why MonitorProcess is not used but MonitorProgram.
2. The second one is an official VCS Agent from a database manufacturer.

Now this is all working very fine. However the application does not work functional correclty when only the application restarts. It needs a fresh restart of the database also. How can I tackle this issue incase of a failure of my application Resource (wich has happened before)? Because a restart of the database can only happen when the application really restarts. Not in case of an online or offline of my complete Service Group.

Thanks in avance for you help,

Sander

Any business service is typically made up of multiple components, databases, applications, and web servers. For a business service to work properly, all of its tiers and components must be up and working together. Tiers represent the logical dependencies between the resiliency groups and determine the relative order in which the resiliency groups start and stop. To ensure business continuity, make sure that not just the individual tiers are up and running but also the entire business service.

For example, a payroll business service might include a web server, a database, and a payroll application. The payroll application requires the web server, application, and the database to be up and running to provide payroll service. Even if one component were down, the payroll service would be down. From a business perspective, the payroll service is unavailable without the web server and the database also being available. The logical dependencies between the parts of the business service determine the relative order in which they must start and stop to continue to provide the service.

A virtual business service (VBS) is a multi-tier business service.

In Veritas Resiliency Platform, a VBS lets you group multiple services as a single unit for visualization, automation, recovery, and controlled start and stop in the desired order.

A VBS is composed of resiliency groups, the unit of management and control in Resiliency Platform. You organize related assets into a resiliency group and manage and monitor them as a single entity.

Within a VBS, resiliency groups are arranged in tiers. Tiers represent the logical dependencies between the resiliency groups and determine the relative order in which the resiliency groups start and stop.

For example, you can group a web server resiliency group, a database resiliency group, and a payroll business logic resiliency group into a VBS called payroll. The database resiliency group must start first, so the database resiliency group must go in the lowest tier. The application server resiliency group must start after the database resiliency group, so it goes in the next tier. The web server resiliency group must start last, so it goes into the top tier. 

The Resiliency Platform console lets you create a VBS by dragging and dropping resiliency groups into tiers. The console also includes a graphic representation of the order in which they start and stop.

Creating a virtual business service

Resiliency Platform also lets you customize a VBS to speed up start and stop operations of the resiliency groups within it if some dependencies are not required.

Customizing a virtual business service

Veritas Resiliency Platform documentation can be found on the SORT website.

Hello,

If the FS is corrupted  VxVM will initiate chkdsk by default, if we disable chkdsk option and if the Volume is corrupted, would  VxVM will force to mount the FS?  or wil wait ...

Hello,

We are running  Solaris  X 86 and added to virtual disk and trying to mirror the  root disk, but getting this error message.

Continue with encapsulation? [y,n,q,?]  (default: y)
  A new disk group rootdg will be created and the disk device c0t1d0 will
  be encapsulated and added to the disk group with the disk name rootdg01.

  VxVM  ERROR V-5-2-5711
The encapsulation operation failed with the following error:

    VxVM vxencap ERROR V-5-2-310 The c0t1d0 disk does not appear to be prepared for this system.

Hit RETURN to continue.

Encapsulate other disks? [y,n,q,?]  (default: n)

Veritas Risk Advisor (VRA) is a data protection and downtime avoidance risk assessment solution. VRA lets you diagnose disaster recovery and high availability (clustering) problems (also called “gaps”) and optimize data protection and reduce risk of downtime.

VRA scans your environment and alerts you to any potential gaps, best practice violations, or service level agreement (SLA) breaches.

What is a ticket?

When VRA detects a gap in your disaster recovery and/or high availability, it issues a ticket. The ticket specifies the problem and the environment entities associated with that problem. For example, VRA can identify:

• Critical data that is not protected properly.

• Standby hosts that do not have access to the replicated data.

• Service Level Agreements (SLAs) that are too strict or too lenient.

• Inconsistent access to storage by cluster nodes.

Searching for tickets

The VRA Tickets module lets you filter the list of tickets in your system to find a specific ticket or ticket type. After VRA displays your query search results, you can:

• Group the results by criteria that you specify.

• Drill down to see ticket details.

• View the network topology related to the ticket in the Topology module.

• Group the results by criteria that you specify.

A full description of the ticket is provided, including an explanation of the problem and the items in your environment that are involved. The impact on your system is also shown with suggestions on how to resolve the ticket.

Working with tickets

You can perform a variety of operations on a ticket during its lifecycle.

• Mark the ticket as resolved. The next time VRA scans your system, it will consider this issue closed.

• Suppress a ticket. A suppressed ticket indicates that you are aware of this problem, but you do not want to be informed about it again during the next full system scan.

• Open the Topology module. You can open the topology module displaying the items relevant to the ticket.

• Add a note to a ticket. You can add a note to a ticket that describes it in more detail. You can filter by note text to make it easier to find a specific ticket(s).

• Add a star rating to indicate its level of important. (One star is the lowest ticket rating and five stars the highest.) You can then sort your tickets by rating to quickly see your most important issues.

You can also perform operations on multiple tickets.

Learning more

For more information on working with tickets, see “Using the Tickets Module” in the Veritas Risk Advisor User’s Guide.

You can access the User’s Guide and other VRA documentation in the Documents area of the SORT website.

Hi, all.

Just upgrade an S10 cluster running 5.1SP1 to 6.0.5.

For the NIC resource, we have a red question mark, and in the logs:  NIC:nic:monitor:Cannot use IPv4 network host [IP deleted] for ping since Protocol is set to IPV4. Resource state: UNKNOWN

Probing does not clear it.  When we set the resource to blank (=IPV4 by default), it doesn't help.

Here's the main.cf:

/etc/VRTSvcs/conf/config]$ cat main.cf
include "OracleASMTypes.cf"
include "types.cf"
include "Db2udbTypes.cf"
include "OracleTypes.cf"
include "SybaseTypes.cf"

cluster proddb017 (
        UserNames = { admin = eLLlLGkHLqLOkTLp,
                 edisupport = GooMomNrpKpnOipHoxOkpL }
        Administrators = { admin }
        )

system proddb017-n1 (
        )

system proddb017-n2 (
        )

group webmethodsdb (
        SystemList = { proddb017-n1 = 0, proddb017-n2 = 1 }
        AutoStartList = { proddb017-n1, proddb017-n2 }
        Operators = { edisupport }
        )

        Db2udb webm (
                Critical = 0
                DB2InstOwner = db2inst1
                DB2InstHome = "/u01/home/db2inst1"
                DatabaseName = webm
                )

        DiskGroup proddb017dg (
                Critical = 0
                DiskGroup = proddb017dg
                )

        IP ediwmdb-ip (
                Critical = 0
                Device = igb0
                Address = "deleted"
                NetMask = "deleted"
                IfconfigTwice = 1
                )

        Mount db2_dbpath (
                Critical = 0
                MountPoint = "/db2_dbpath"
                BlockDevice = "/dev/vx/dsk/proddb017dg/vol_dbpath"
                FSType = vxfs
                FsckOpt = "-y"
                )

        Mount db2_diagnostics (
                Critical = 0
                MountPoint = "/db2_diagnostics"
                BlockDevice = "/dev/vx/dsk/proddb017dg/vol_diags"
                FSType = vxfs
                FsckOpt = "-y"
                )

        Mount db2_mirror_online_logs (
                Critical = 0
                MountPoint = "/db2_mirror_online_logs"
                BlockDevice = "/dev/vx/dsk/proddb017dg/vol_log2"
                FSType = vxfs
                FsckOpt = "-y"
                )

        Mount db2_online_logs (
                Critical = 0
                MountPoint = "/db2_online_logs"
                BlockDevice = "/dev/vx/dsk/proddb017dg/vol_log1"
                FSType = vxfs
                FsckOpt = "-y"
                )

        Mount db2_primary_log_archive (
                Critical = 0
                MountPoint = "/db2_primary_log_archive"
                BlockDevice = "/dev/vx/dsk/proddb017dg/vol_archive1"
                FSType = vxfs
                FsckOpt = "-y"
                )

        Mount db2_secondary_log_archive (
                Critical = 0
                MountPoint = "/db2_secondary_log_archive"
                BlockDevice = "/dev/vx/dsk/proddb017dg/vol_archive2"
                FSType = vxfs
                FsckOpt = "-y"
                )

        Mount db2backup (
                Critical = 0
                MountPoint = "/db2backup"
                BlockDevice = "/dev/vx/dsk/proddb017dg/vol_db2backup"
                FSType = vxfs
                FsckOpt = "-y"
                )

        Mount u01 (
                Critical = 0
                MountPoint = "/u01"
                BlockDevice = "/dev/vx/dsk/proddb017dg/vol_u01"
                FSType = vxfs
                FsckOpt = "-y"
                )

        NIC nic (
                Critical = 0
                Device = igb0
                NetworkHosts = { "deleted", "deleted", "deleted" }
                Protocol = IPV4
                )

        db2_dbpath requires proddb017dg
        db2_diagnostics requires proddb017dg
        db2_mirror_online_logs requires proddb017dg
        db2_online_logs requires proddb017dg
        db2_primary_log_archive requires proddb017dg
        db2_secondary_log_archive requires proddb017dg
        db2backup requires proddb017dg
        ediwmdb-ip requires nic
        u01 requires proddb017dg
        webm requires db2_dbpath
        webm requires db2_diagnostics
        webm requires db2_mirror_online_logs
        webm requires db2_online_logs
        webm requires db2_primary_log_archive
        webm requires db2_secondary_log_archive
        webm requires ediwmdb-ip
        webm requires u01

        // resource dependency tree
        //
        //      group webmethodsdb
        //      {
        //      Mount db2backup
        //          {
        //          DiskGroup proddb017dg
        //          }
        //      Db2udb webm
        //          {
        //          Mount db2_dbpath
        //              {
        //              DiskGroup proddb017dg
        //              }
        //          Mount db2_diagnostics
        //              {
        //              DiskGroup proddb017dg
        //              }
        //          Mount db2_mirror_online_logs
        //              {
        //              DiskGroup proddb017dg
        //              }
        //          Mount db2_online_logs
        //              {
        //              DiskGroup proddb017dg
        //              }
        //          Mount db2_primary_log_archive
        //              {
        //              DiskGroup proddb017dg
        //              }
        //          Mount db2_secondary_log_archive
        //              {
        //              DiskGroup proddb017dg
        //              }
        //          IP ediwmdb-ip
        //              {
        //              NIC nic
        //              }
        //          Mount u01
        //              {
        //              DiskGroup proddb017dg
        //              }
        //          }
        //      }

The types.cf file:

/etc/VRTSvcs/conf/config]$ cat types.cf
type Apache (
        static boolean IntentionalOffline = 0
        static keylist SupportedActions = { "checkconffile.vfd" }
        static str ArgList[] = { ResLogLevel, State, IState, httpdDir, SharedObjDir, EnvFile, PidFile, HostName, Port, User, SecondLevelMonitor, SecondLevelTimeout, ConfigFile, EnableSSL, DirectiveAfter, DirectiveBefore }
        static int ContainerOpts{} = { RunInContainer=1, PassCInfo=0 }
        str ResLogLevel = INFO
        str httpdDir
        str SharedObjDir
        str EnvFile
        str PidFile
        str HostName
        int Port = 80
        str User
        boolean SecondLevelMonitor = 0
        int SecondLevelTimeout = 30
        str ConfigFile
        boolean EnableSSL = 0
        str DirectiveAfter{}
        str DirectiveBefore{}
)

type Application (
        static keylist SupportedActions = { "program.vfd", "user.vfd", "cksum.vfd", getcksum }
        static str ArgList[] = { User, StartProgram, StopProgram, CleanProgram, MonitorProgram, PidFiles, MonitorProcesses }
        static int ContainerOpts{} = { RunInContainer=1, PassCInfo=0 }
        str User
        str StartProgram
        str StopProgram
        str CleanProgram
        str MonitorProgram
        str PidFiles[]
        str MonitorProcesses[]
)

type CoordPoint (
        static int InfoInterval = 300
        static int OfflineMonitorInterval = 60
        static str ArgList[] = { FaultTolerance }
        static str Operations = None
        int FaultTolerance
)

type DNS (
        static keylist SupportedActions = { "dig.vfd", "master.vfd", "keyfile.vfd" }
        static str ArgList[] = { Domain, TTL, TSIGKeyFile, StealthMasters, ResRecord, CreatePTR, OffDelRR }
        str Domain
        int TTL = 86400
        str TSIGKeyFile
        str StealthMasters[]
        str ResRecord{}
        boolean CreatePTR = 0
        boolean OffDelRR = 0
)

type DiskGroup (
        static keylist SupportedActions = { "license.vfd", "disk.vfd", "udid.vfd", "verifyplex.vfd", checkudid, campusplex, numdisks, joindg, splitdg, getvxvminfo, volinuse }
        static int NumThreads = 1
        static int OnlineRetryLimit = 1
        static str ArgList[] = { DiskGroup, StartVolumes, StopVolumes, MonitorOnly, MonitorReservation, tempUseFence, PanicSystemOnDGLoss, DiskGroupType, UmountVolumes }
        str DiskGroup
        boolean StartVolumes = 1
        boolean StopVolumes = 1
        boolean MonitorReservation = 0
        temp str tempUseFence = INVALID
        boolean PanicSystemOnDGLoss = 0
        str DiskGroupType = private
        int UmountVolumes
)

type DiskGroupSnap (
        static int ActionTimeout = 120
        static int MonitorInterval = 300
        static int NumThreads = 1
        static str ArgList[] = { TargetResName, FDSiteName }
        str TargetResName
        str FDSiteName
)

type ElifNone (
        static int OfflineMonitorInterval = 60
        static str ArgList[] = { PathName }
        static str Operations = None
        str PathName
)

type FileNone (
        static int OfflineMonitorInterval = 60
        static str ArgList[] = { PathName }
        static str Operations = None
        str PathName
)

type FileOnOff (
        static str ArgList[] = { PathName }
        str PathName
)

type FileOnOnly (
        static str ArgList[] = { PathName }
        static str Operations = OnOnly
        str PathName
)

type IP (
        static keylist SupportedActions = { "device.vfd", "route.vfd" }
        static str ArgList[] = { Device, Address, NetMask, Options, ArpDelay, IfconfigTwice, RouteOptions, PrefixLen }
        static int ContainerOpts{} = { RunInContainer=0, PassCInfo=1 }
        str Device
        str Address
        str NetMask
        str Options
        int ArpDelay = 1
        int IfconfigTwice
        str RouteOptions
        int PrefixLen
)

type IPMultiNIC (
        static int MonitorTimeout = 120
        static str ArgList[] = { "MultiNICResName:Device", Address, NetMask, "MultiNICResName:ArpDelay", Options, "MultiNICResName:Probed", MultiNICResName, IfconfigTwice, PrefixLen }
        static int ContainerOpts{} = { RunInContainer=0, PassCInfo=1 }
        str Address
        str NetMask
        str Options
        str MultiNICResName
        int IfconfigTwice
        int PrefixLen
)

type IPMultiNICB (
        static int MonitorInterval = 30
        static int OnlineRetryLimit = 1
        static int ToleranceLimit = 1
        static str ArgList[] = { BaseResName, Address, NetMask, DeviceChoice, RouteOptions, PrefixLen, IgnoreMultiNICBFailure, "BaseResName:Protocol" }
        static int ContainerOpts{} = { RunInContainer=0, PassCInfo=1 }
        str BaseResName
        str Address
        str NetMask
        str DeviceChoice = 0
        str RouteOptions
        int PrefixLen
        int IgnoreMultiNICBFailure
)

type Mount (
        static keylist SupportedActions = { "mountpoint.vfd", "mounted.vfd", "vxfslic.vfd", chgmntlock, "mountentry.vfd" }
        static str ArgList[] = { MountPoint, BlockDevice, FSType, MountOpt, FsckOpt, SnapUmount, CkptUmount, SecondLevelMonitor, SecondLevelTimeout, OptCheck, CreateMntPt, MntPtPermission, MntPtOwner, MntPtGroup, AccessPermissionChk, RecursiveMnt, VxFSMountLock }
        str MountPoint
        str BlockDevice
        str FSType
        str MountOpt
        str FsckOpt
        int SnapUmount
        int CkptUmount = 1
        boolean SecondLevelMonitor = 0
        int SecondLevelTimeout = 30
        int OptCheck
        int CreateMntPt
        int ReuseMntPt
        str MntPtPermission
        str MntPtOwner
        str MntPtGroup
        int AccessPermissionChk
        boolean RecursiveMnt = 0
        int VxFSMountLock = 1
)

type MultiNICA (
        static int MonitorTimeout = 300
        static int OfflineMonitorInterval = 60
        static str ArgList[] = { Device, NetMask, ArpDelay, RetestInterval, Options, RouteOptions, PingOptimize, MonitorOnly, IfconfigTwice, HandshakeInterval, NetworkHosts, Protocol }
        static str Operations = None
        str Device{}
        str NetMask
        int ArpDelay = 1
        int RetestInterval = 5
        str Options
        str RouteOptions
        int PingOptimize = 1
        int IfconfigTwice
        int HandshakeInterval = 20
        str NetworkHosts[]
        str Protocol
)

type MultiNICB (
        static int MonitorInterval = 10
        static int OfflineMonitorInterval = 60
        static str ArgList[] = { UseMpathd, MpathdCommand, ConfigCheck, MpathdRestart, Device, NetworkHosts, LinkTestRatio, IgnoreLinkStatus, NetworkTimeout, OnlineTestRepeatCount, OfflineTestRepeatCount, NoBroadcast, DefaultRouter, Failback, GroupName, Protocol }
        static str Operations = None
        int UseMpathd
        str MpathdCommand = "/usr/lib/inet/in.mpathd"
        int ConfigCheck = 1
        int MpathdRestart = 1
        str Device{}
        str NetworkHosts[]
        int LinkTestRatio = 1
        int IgnoreLinkStatus = 1
        int NetworkTimeout = 100
        int OnlineTestRepeatCount = 3
        int OfflineTestRepeatCount = 3
        int NoBroadcast
        str DefaultRouter = "0.0.0.0"
        int Failback
        str GroupName
        str Protocol
)

type NFS (
        static int RestartLimit = 1
        static str ArgList[] = { UseSMF, Nservers, LockFileTimeout }
        static str Operations = OnOnly
        int Nservers = 16
        int LockFileTimeout = 180
        boolean UseSMF = 0
)

type NFSRestart (
        static keylist SupportedActions = { "lockdir.vfd", "nfsconf.vfd" }
        static str ArgList[] = { LocksPathName, NFSLockFailover, LockServers, NFSRes, "NFSRes:LockFileTimeout", "NFSRes:UseSMF" }
        str NFSRes
        str LocksPathName
        boolean NFSLockFailover = 0
        int LockServers = 20
)

type NIC (
        static keylist SupportedActions = { "device.vfd" }
        static int OfflineMonitorInterval = 60
        static str ArgList[] = { Device, PingOptimize, NetworkHosts, Protocol, NetworkType }
        static str Operations = None
        str Device
        int PingOptimize = 1
        str NetworkHosts[]
        str Protocol
        str NetworkType
)

type NetBios (
        static str ArgList[] = { "SambaServerRes:ConfFile", "SambaServerRes:SambaTopDir", "SambaServerRes:LockDir", NetBiosName, NetBiosAliases, Interfaces, WinsSupport, DomainMaster }
        str SambaServerRes
        str NetBiosName
        str NetBiosAliases[]
        str Interfaces[]
        int WinsSupport
        int DomainMaster
)

type NotifierMngr (
        static int RestartLimit = 3
        static str ArgList[] = { EngineListeningPort, MessagesQueue, NotifierListeningPort, SnmpdTrapPort, SnmpCommunity, SnmpConsoles, SmtpServer, SmtpServerVrfyOff, SmtpServerTimeout, SmtpReturnPath, SmtpFromPath, SmtpRecipients }
        int EngineListeningPort = 14141
        int MessagesQueue = 30
        int NotifierListeningPort = 14144
        int SnmpdTrapPort = 162
        str SnmpCommunity = public
        str SnmpConsoles{}
        str SmtpServer
        boolean SmtpServerVrfyOff = 0
        int SmtpServerTimeout = 10
        str SmtpReturnPath
        str SmtpFromPath
        str SmtpRecipients{}
)

type Phantom (
)

type Process (
        static keylist SupportedActions = { "program.vfd", getcksum }
        static str ArgList[] = { PathName, Arguments }
        static int ContainerOpts{} = { RunInContainer=1, PassCInfo=0 }
        str PathName
        str Arguments
)

type ProcessOnOnly (
        static str ArgList[] = { IgnoreArgs, PathName, Arguments }
        static int ContainerOpts{} = { RunInContainer=1, PassCInfo=0 }
        static str Operations = OnOnly
        boolean IgnoreArgs = 0
        str PathName
        str Arguments
)

type Proxy (
        static int OfflineMonitorInterval = 60
        static str ArgList[] = { TargetResName, TargetSysName, "TargetResName:Probed", "TargetResName:State" }
        static str Operations = None
        str TargetResName
        str TargetSysName
)

type RVG (
        static int NumThreads = 1
        static str ArgList[] = { RVG, DiskGroup }
        str RVG
        str DiskGroup
        str StorageRVG
        str StorageDG
        str StorageHostIds
)

type RVGLogowner (
        static int NumThreads = 1
        static int OnlineRetryLimit = 5
        static str ArgList[] = { RVG, DiskGroup }
        str RVG
        str DiskGroup
        str StorageRVG
        str StorageDG
        str StorageHostIds
)

type RVGPrimary (
        static keylist SupportedActions = { fbsync }
        static int NumThreads = 1
        static int OnlineRetryLimit = 1
        static str ArgList[] = { RvgResourceName, AutoTakeover, AutoResync }
        str RvgResourceName
        int AutoTakeover = 1
        int AutoResync
)

type RVGShared (
        static int NumThreads = 1
        static str ArgList[] = { RVG, DiskGroup }
        str RVG
        str DiskGroup
)

type RVGSharedPri (
        static keylist SupportedActions = { fbsync, resync }
        static int NumThreads = 1
        static int OnlineRetryLimit = 1
        static str ArgList[] = { RvgResourceName, "RvgResourceName:RVG", "RvgResourceName:DiskGroup", AutoTakeover, AutoResync }
        str RvgResourceName
        int AutoTakeover = 1
        int AutoResync
        temp str VCSResLock
)

type RVGSnapshot (
        static keylist RegList = { Prefix }
        static int NumThreads = 1
        static str ArgList[] = { RvgResourceName, CacheObj, Prefix, DestroyOnOffline }
        str RvgResourceName
        str CacheObj
        str Prefix
        boolean DestroyOnOffline = 1
        temp str FDFile
)

type RemoteGroup (
        static int OnlineRetryLimit = 2
        static int ToleranceLimit = 1
        static str ArgList[] = { IpAddress, Port, Username, Password, GroupName, VCSSysName, ControlMode, OfflineWaitTime, DomainType, BrokerIp }
        str IpAddress
        int Port = 14141
        str Username
        str Password
        str GroupName
        str VCSSysName
        str ControlMode
        int OfflineWaitTime
        str DomainType
        str BrokerIp
)

type SANVolume (
        static int OnlineRetryLimit = 4
        static str ArgList[] = { SANVolume, SANDiskGroup, VolumeServer, Domain, ExclusiveUse, Preempt, AccessPolicy }
        str Domain
        str SANDiskGroup
        str SANVolume
        str VolumeServer
        boolean ExclusiveUse = 1
        boolean Preempt = 1
        str AccessPolicy = RDONLY
)

type SambaServer (
        static str ArgList[] = { ConfFile, SambaTopDir, LockDir, Ports, IndepthMonitorCyclePeriod, ResponseTimeout }
        str ConfFile
        str SambaTopDir
        str LockDir
        int Ports[] = { 139, 445 }
        int IndepthMonitorCyclePeriod = 5
        int ResponseTimeout = 10
)

type SambaShare (
        static str ArgList[] = { "SambaServerRes:ConfFile", "SambaServerRes:SambaTopDir", "SambaServerRes:LockDir", ShareName, ShareOptions, "SambaServerRes:Ports" }
        str SambaServerRes
        str ShareName
        str ShareOptions
)

type Share (
        static keylist SupportedActions = { "direxists.vfd" }
        static str ArgList[] = { PathName, Options, "NFSRes:State" }
        str NFSRes
        str PathName
        str Options
)

type VRTSWebApp (
        static int NumThreads = 1
        static str ArgList[] = { AppName, InstallDir, TimeForOnline }
        str AppName
        str InstallDir
        int TimeForOnline
)

type Volume (
        static int NumThreads = 1
        static str ArgList[] = { Volume, DiskGroup }
        str Volume
        str DiskGroup
)

type Zone (
        static str ArgList[] = { Pool, BootState, ShutdownGracePeriod }
        static int ContainerOpts{} = { RunInContainer=0, PassCInfo=1 }
        str Pool
        str BootState
        int ShutdownGracePeriod
)

type Zpool (
        static str ArgList[] = { PoolName, AltRootPath, ChkZFSMounts, ZoneResName, "ZoneResName:State" }
        str PoolName
        str AltRootPath
        boolean ChkZFSMounts = 1
        str ZoneResName
)

Any help would be greatly appreciated.

-Jay

With InfoScale 7.0, during installation or upgrade from an earlier release version to 7.0, you only get to choose from the simplified newly licensed InfoScale products. The earlier products were branded under the Storage Foundation and High Availability name, which has been rebranded to InfoScale. To know how the earlier products map to the new InfoScale products and to know the upgrade path,  see the Components of the Veritas InfoScale product suite.

With InfoScale 7.0, Veritas introduced four rebranded products, namely:

• Veritas InfoScale Foundation
• Veritas InfoScale Storage
• Veritas InfoScale Availability
• Veritas InfoScale Enterprise

Some of the other changes to install and upgrade procedures are:

• InfoScale 7.0 is the 7.0 first release to be available in ISO format.
• During installation, the installer script no longer prompts for the package list, but installs all packages bundled with the product.
• Prior to release 7.0, installer functions such as installvcs6.2 were used to install the product. In contrast, from 7.0 release onwards, after installation or upgrade, all the installer functions are invoked through the /opt/VRTS/install/installer script.
• With 7.0, you cannot install two products on the same system. For example, installation of Veritas InfoScale Enterprise includes Veritas InfoScale Storage and Veritas InfoScale Availability on all the systems.
• [Linux-only] The Linux RPMs now include digital signatures to verify their authenticity. You must import keys before you manually install the RPMs.
• The image file names are updated.
• RHEL and SLES are among the supported Linux flavors.

For more information on changes to installation and upgrades, refer to the respective platform links:

• Linux
• Solaris
• AIX

Veritas InfoScale documentation for other releases and platforms can be found on the SORTwebsite.

This error message is displayed if you do not lower the priority of the IP-enabled network adapter used for both the public and the Veritas Cluster Server (VCS) private network.

VCS uses private network communications between cluster nodes for maintenance. It configures Low Latency Transport (LLT) for communications between cluster nodes and Global Atomic Broadcast (GAB) for transmitting cluster heartbeats.

When creating new clusters or adding nodes to existing clusters, VCS validates the selected systems for the number of available network adapters. Each system must have at least two network adapters used as follows:

·         One IP-enabled network adapter is used for public network as well as VCS private network communication.

·         One network adapter is used exclusively for VCS private network communication.

To solve this issue, if there are only two network adapters on a system, Veritas recommends that you lower the priority of the IP-enabled network adapter that is used for both public and private network communication. To lower the priority, right-click the IP-enabled network adapter on the list and select Low Priority from the pop-up menu.

Note: The cluster configuration is not affected if you do not lower the priority of the adapter. However, LLT and GAB communication packets may be lost on the public network due to network congestion, which may cause problem for VCS.

Veritas recommends having three network adapters per system, one for the public network and two exclusively for the VCS private network. They provide the required redundancy in the communication path and enable VCS to discriminate between a network failure and a system failure.

For more information, see:

• UMI V-16-15-779
• Adding and removing cluster nodes

Veritas InfoScale documentation for products and error messages can be found on the SORT website.

We have a Netbackup master server cluster, the catalog/DB is sitting on a vxfs volume. 

There is a case open currently with Veritas and they have found massive delays (40 seconds!) at backup peak time on the Sybase database and have recommended we do a "nbdb_unload -rebuild" and "nbdb_admin -reorganize".

Meanwhile, we are looking at the IO on the catalog/DB volume. The technote below says the response shouldn't be more than 20ms. How do I determine the current response time, is there a Storage Foundation tool that can provide this?

Our host is running RHEL6.6.

Understanding the V-16-1-40130 error message for UNIX

The hares command administers resources in a Veritas Cluster Server (VCS) cluster. Resources are individual representations of the elements that are required for a service group to be available, such as a volume, a database, or an IP address. Among the many hares options, -display and –state are frequently used to display resource information:

# hares –display resource_name# hares -state resource_name

Error conditions

Sometimes, when you run theses commands, you get the following message:

VCS WARNING V-16-1-40130 Resource name does not exist in the local cluster

The error occurs when the resource is not configured in the local cluster. When the resource is configured in a remote cluster, the message is also displayed, but is followed with the resource state in the remote cluster.

Investigating the error

If you want to check the resources that are configured in the local cluster or in a global group, execute the following command:

# hares –list

Then you can examine the information of any resources appear in the output by re-entering either of the previous commands:

For resources in the local cluster:

# hares –display resource_name# hares -state resource_name

For resources in a global group:

# hares –display resource_name–clus local_cluster_name/remote_cluster_name# hares -state resource_name–clus local_cluster_name/remote_cluster_name

If you need to, you can also administer the resources by:

• Adding resources
• Deleting resources
• Modifying resources
• Linking or unlinking resources
• Bringing resources online
• Taking resources offline

You can find more Veritas InfoScale and SFHA Solutions documentation on the SORT website.

Hello All,

is it posible to save my data and start up from at least one good disk on a Solaris server in this case?:

[root@host1:/]$ vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c1t0d0s2     auto:sliced     rootdg01     rootdg       online failing
c1t1d0s2     auto:sliced     rootdg03     rootdg       online
-            -         rootdg02     rootdg       removed was:c1t1d0s2
[root@host1:/]$

I somehow started up the server from ramdisk. I'm in readonly mode, but I can manually mount FS if needed.

The problem is that c1t0d0s2 failed:

WARNING: /pci@1c,600000/scsi@2 (glm0):
        Resetting scsi bus, got incorrect phase from (0,0)
WARNING: /pci@1c,600000/scsi@2 (glm0):
        got SCSI bus reset
WARNING: /pci@1c,600000/scsi@2 (glm0):
        Resetting scsi bus, got incorrect phase from (0,0)
WARNING: /pci@1c,600000/scsi@2 (glm0):
        got SCSI bus reset
WARNING: /pci@1c,600000/scsi@2/sd@0,0 (sd0):
        auto request sense failed (reason=reset)

and the second disk c1t1d0s2 is in a strange state which I don't understand - it's part of rootdg02 which is ok and also part of rootdg03 which is removed. I can't mount this disk c1t1d0s0,1,3,4,... 

[root@host1:/]$ mount /dev/dsk/c1t1d0s1 /mnt
mount: I/O error
mount: Cannot mount /dev/dsk/c1t1d0s1
[root@host1:/]$

Thank you for your comments.

Network File System (NFS) allows network users to access shared files stored on an NFS server. NFS allows you to manage shared files transparently as if the files were on a local disk. For more information about NFS and configuring NFS service groups, refer to the following sections:

• About NFS
• Configuring NFS service groups

The NFSRestart agent is a Cluster Server (VCS) bundled agent. This agent is installed on the system when you install VCS. The NFSRestart agent is configured in conjunction with the NFS agent for failover type shared service groups.

The NFSRestart agent manages essential NFS locking services, network status manager, and network lock manager. The agent also manages NFS lock recovery service by recovering the NFS record locks after sudden server crash. The agent prevents potential NFS ACK storms by terminating NFS server services before closing all Transmission Control Protocol (TCP) connections with the NFS client.

Refer to the following sections for more information about the NFSRestart agent:

• Dependencies
• Agent functions
• State definitions
• Attributes
• Resource type definition
• Notes for NFSRestart agent
• Sample configurations
• Debug log levels

In a Veritas Cluster File System environment, instead of the NFSRestart agent, you must configure preonline and postonline triggers for managing NFS services. For more information, refer to the following section:

• Understanding how Clustered NFS works

The links in this article are specific to the Linux platform. Veritas InfoScale documentation for other releases and platforms can be found on the SORT website.

Hi All , 

we have a running solaris and veritas quick i/o files for oracle 9i database .

The files no longer exist in the database but somehow exist in the file system .

How do we remove the veritas files from the filesystem ?

  lrwxrwxrwx   1 oracle   oinstall      36 Sep 16  2011 b2bprddb_undotbs2.dbf03 -> .b2bprddb_undotbs2.dbf03::cdev:vxfs:

  -rw-r--r--   1 oracle   oinstall 2097160192 Oct 21 11:13 .b2bprddb_undotbs2.dbf03

  lrwxrwxrwx   1 oracle   oinstall      34 Sep 11  2011 javazone_data01.dbf09 -> .javazone_data01.dbf09::cdev:vxfs:

  -rw-r--r--   1 oracle   oinstall 2097160192 Sep 11  2011 .javazone_data01.dbf09

  lrwxrwxrwx   1 oracle   oinstall      35 Dec  7  2010 javazone_index01.dbf06 -> .javazone_index01.dbf06::cdev:vxfs:

  -rw-r--r--   1 oracle   oinstall 1572872192 Dec  7  2010 .javazone_index01.dbf06

Veritas Risk Advisor (VRA) is a data protection and downtime avoidance risk assessment solution that lets you diagnose disaster recovery and high availability (clustering) problems (also called “gaps”) and optimize data protection and reduce the risk of downtime.

VRA enables enterprises to effectively manage business continuity implementations to ensure that critical business data is protected. VRA automatically detects and alerts you to any potential gaps, best practice violations, or service level agreement (SLA) breaches.

VRA’s Report Generator automatically generates detailed reports describing your configuration and the gaps that it detected from information extracted from the VRA database.

VRA allows you generate multiple reports at the same time.

Also you can export the content into the MS Word, PDF, and MS Excel format.

VRA Report Types

VRA has the following reports:

• Scan Status
• System Event Log
• Ticket Details
• Storage Allocation Optimization
• Unreplicated Data on Replicated Hosts
• NetApp Filer Replication Summary
• Unsynchronized Remote Replication
• Old Replicas
• Standby Pairs and so on

Report scheduling

VRA also lets you schedule when reports are automatically generated and sent to one or more email destinations that you configure. New reports automatically generate each time before they are sent. You may also choose to save the generated reports in the file system and access them later.

Learning More

For more information on working with Reports, see “VRA reporting” in the Veritas Risk Advisor User’s Guide.

You can access the User’s Guide and other VRA documentation in the Documents area of the SORT Website.

Veritas Risk Advisor (VRA) is a data protection and downtime avoidance risk assessment solution that lets you diagnose disaster recovery and high availability (clustering) problems (also called “gaps”) and optimize data protection and reduce the risk of downtime.

VRA enables enterprises to effectively manage business continuity implementations to ensure that critical business data is protected. VRA automatically detects and alerts you to any potential gaps, best practice violations, or service level agreement (SLA) breaches.

What is Comparison Module

The Comparison module helps you identify the host configuration drifts hiding in your IT. Such drifts often fail cluster failover processes, and reduce the availability of your organization’s applications. In this module, you can create comparison groups that include hosts, clusters, or business entities, and easily track configuration differences between them.

The Comparison module uses worksheets and comparison groups.

Worksheet

A worksheet is a logical container of comparison groups. It also contains all suppressions and difference monitoring information. Worksheets are defined and saved at the user level, which means that each user has his/her own worksheet.

Comparison Groups

A comparison group is a dynamic group of hosts that you want to compare. The following types of comparison groups are available:

• Hosts
• Clusters
• Business Entities
• Golden Copy

Each group type behaves differently in terms of the group scope and comparison functionality.

You begin by creating a worksheet, and then by creating comparison groups. Once defined, comparison groups can be assigned to a worksheet.

Once the worksheets and comparison groups are created, you can compare the host configurations with the following options:

• Hardware
• Software
• Operating System
• Users and Groups
• OS Kernel Parameters / Limits

Learning More

For more information on working with Comparison Module, see “Using the Comparison module” in the Veritas Risk Advisor User’s Guide.

You can access the User’s Guide and other VRA documentation in the Documents area of the SORT Website.

Dear colleagues,

The question is simple: is HP StoreServ 7000/8000 compatible with Storage Foundation 5.1?

HCL for Storage Foundation 5.1 (http://www.veritas.com/docs/000008646) does not contain any information regarding StoreServ 7000/8000.

HCL for SF 6.0 (http://www.veritas.com/docs/000011772) has StoreServ 7000/8000 compatibility included.

So will StoreServ 7000/8000 be backward compatible with Storage Foundation 5.1? Are there any specifiic differences between SF 5.1 anf SF 6.0 that could prevent StoreServ from backward compatibility?