Video Screencast Help
Storage and Availability Management
Showing posts tagged with Cluster Server
Showing posts in English
Sandeep Agarwal | 10 Sep 2009 | 0 comments

If you want to reduce extra traffic on the LLT links one small thing to do would be to add the following line to /etc/llttab on all the nodes in your cluster (say 2 node cluster):
exclude 2-31

What the above line does is that it assumes that your cluster will always have only 2 nodes (0 and 1) and hence extra packets will not be sent to discover the other nodes periodically. One caveat is that you won't be able to add a node to your cluster on the fly. You could also change the above line to be:
exclude 8-31
and in that case you can grow your 2 node cluster to a maximum of 8 nodes on the fly.

One more thing to note when using LLT is to never have spanning-tree enabled on the switch ports which are used to connect the LLT links. Spanning tree causes a delay in sending pkts when the port is enabled and this can cause the cluster nodes to not join properly. 

Sandeep Agarwal | 26 Jul 2009 | 0 comments

It seems that some customers want to create a trunk out of two links and then create vlans over that trunk and then run LLT over those two vlans.

This is how to do this on Solaris:

Create a trunk (aggregation first) out of the two bge links:
dladm create-aggr -d bge2 -d bge3 1 <--- to create a aggr1

Create vlans out of aggr1:
dladm create-vlan doesn't seem to work on Solaris 10u7 (beta).
So just do the following:
ifconfig aggr10001 plumb 1.1.1.1 up <----- to create /dev/aggr10001 (vlan id 10000)
ifconfig aggr20001 plumb 2.1.1.1 up <----- to create /dev/aggr20001 (vlan id 20000)

Then create /etc/llttab as follows:
link link1 /dev/aggr:10001 - ether - -
link link1 /dev/aggr:20001 - ether - -

And now you are up and running with LLT over vlanned trunks.
 

Sandeep Agarwal | 16 Jul 2009 | 0 comments

If you have LLT working over the ce driver on Solaris, one small change that you can make to help performance problems in your cluster would be the following:

The /etc/system file on all hosts should have:
set ce:ce_no_tx_lb=1
set ce:ce_taskq_disable=1
set ce:ce_reclaim_pending=1

A reboot is required.

Please read this tech note for details:
http://seer.entsupport.symantec.com/docs/292684.htm

Jerry Gowen | 09 Jun 2009 | 0 comments

IDC released its quarterly Storage Software Report yesterday, showing the market has experienced its first year-over-year decline in more than five years. And while most companies experienced a decline in revenue, Symantec was the only company that actually broke the trend and demonstrated growth during this same time period -- narrowing EMC’s market share in Overall Storage Software.

Part of Symantec’s success is due to its innovative storage and data protection software portfolio that helps organizations utilize current storage resources and ultimately save money.

The report shows the following about Symantec:

Symantec has narrowed EMC’s overall market share lead in Overall Storage Software (Symantec is number one among pure-play software providers)
Symantec continues to dominate market share in the Data Protection and File System categories over EMC and IBM, among others.
Symantec extends its market share lead over EMC in...

Eric.Hennessey | 27 Apr 2009 | 0 comments

A very useful - yet often overlooked - feature of Veritas Cluster Server is Limits and Prerequisites. This feature is often used in conjunction with Service Group Workload Management (SGWM), but can also be implemented on its own. In this post, I'll describe what this feature does and how you can put it to use.

Limits and Prerequisites are attributes in VCS. Limits are system attributes applied to the cluster member nodes, while Prerequisites are attributes applied to service groups. Both are key/value type attributes defined by the user. To better understand how these two attributes work together, it's best to use a common scenario as an example.

Let's say I have a VCS cluster consisting of four nodes and four Oracle database service groups. Let's assume that (1) each node is provisioned identically with the same processor and memory power and (2) each service group places about the same amount of load on each system. Implementing SGWM will automatically keep...

Rishi Manocha | 02 Apr 2009 | 0 comments

The following services have just been updated. Please find below new functionalities now available to you:

Veritas Installation Assessment Service [VIAS]

  • Combined Notification Center – Users can create user defined ad-hoc or environment specific notifications for new patches, ASL/APM releases, new versions of the HCL and updates to Veritas Operations Services (VOS) from one easy-to-use web application. Both the notification center and VIAS reports now connect directly with Patch Central allowing the applications to synergistically cross-leverage customer data
  • Windows Support (Beta) – Support for the SFWHA “ConfigChecker” application to pre-qualify Windows environments

Find Out More
Link to VIAS

...

Eric.Hennessey | 05 Mar 2009 | 0 comments

Hello from the Storage Foundation/High Availability Technical Product Management team, and welcome to the new Symantec Connect!  In this first VCS blog entry under the new format, we'll take a look at reducing the cost of HA by building larger, more "intelligent" clusters.

When most people think of clustering, they think of a 2-node, active/passive cluster in which a mission-critical application runs on one system (the active node) while a stand-by system (passive node) is ready to take over if something fails on the active node.  This approach works fine in an environment with one or maybe two mission-critical applications, but consider the costs of this approach in an environment with 10 or 15 or 20 mission-critical applications.

To avoid the costs of excessive hardware sparing, an "N+1" approach is often implemented in which "N" represents the number of active nodes and "+1" represents a single spare (idle) server....

Eileen | 28 Feb 2009 | 0 comments

Welcome to the new Symantec Connect and specifically to the Clustering and Replication Community. What a great opportunity to really build a vibrant and engaging community all about high availability and disaster recovery!

Now to introduce myself, I’m Eileen Allan, the new Clustering and Replication Community Manager. I’ll be managing and moderating the content for this area of Symantec Connect. Please feel free to drop me a note with your thoughts, ideas or suggestions. I’d be interested to learn what kind of information is important to you. What topics are of interest, or what problems are you trying to solve . . and by all means, let me know what you think of the new site.

Everyone is invited to participate and share technical knowledge and experience with the community. Take a few minutes to start a forum discussion or ask a question. Your expertise can help someone else in the community solve a problem. Why not write an article or a blog...

DLamorena | 06 Oct 2008 | 0 comments

Symantec's Dan Lamorena, Senior Product Marketing Manager, and Eric Hennessey, Director, Technical Product Management, continue their introduction of Veritas Cluster Server One and further explain its value in providing high availability in a multi-tiered, multi-platform application environment.

Eric: Another critical element of Veritas Cluster Server One (VCS One) is the ability to manage virtualized environments such as VMware, Solaris Containers and LDOMs, IBM mPars, and others. Most of these platforms have their own "high availability (HA)" solutions; however, these solutions don't have some of the enterprise-ready features that customers require like rich application monitoring and failover. Further, these HA solutions only work on that particular platform and most IT organizations have a mix of Windows, Unix, and server virtualization in their data centers. This means that the IT organization has different tools on different...