Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.
Storage & Clustering Community Blog
Showing posts tagged with Features
Showing posts in English
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...

Karthikeyan Sundaram | 22 Apr 2009 | 1 comment

Get some Live sessions to make your setup more strong!

Here > https://symantecevents.webex.com

M.Pozzi | 08 Apr 2009 | 2 comments

Introduction:

This test regards the new smartmove feature introduced with MP3:

Enviroment:

OS AIX 5300-07-02-0806
Storage Fondation 5.0MP3RP1
Storage 2 LUNS XP24K 100GB

Test:
Mirror an empty filesystem

Initial situation:

diskgroup with a volume of  97.615 GB

root@/ #vxprint -Qqthg smartdg
dg smartdg      default      default  3000     1239178875.70.tx088sd1
dm disk0        xp12k0_0     auto     65536    204713728 -
dm disk1        xp12k0_1     auto     65536    204713728 -
v  smartvol0    -            ENABLED  ACTIVE...

Rishi Manocha | 10 Mar 2009 | 1 comment

A group of DBAs that manage large databases at a large federal government agency had the challenge of migrating a mission-critical 35 TB database from a Fujitsu 2500 running Solaris to an IBM P595 running AIX within a 4 hour maintenance window. Using the tools that the database vendor offered, the estimated time to move that much data was in the neighborhood of 3 weeks, which was unacceptable. Database migration tools from another company were evaluated but they were cost prohibitive.

A Symantec Sales Engineer suggested that these DBAs use the Portable Data Container (PDC) feature within Storage Foundation, which was already deployed in their infrastructure. He explained that with PDC, instead of moving the data from one storage location to another, the data can be unmounted from the Solaris system and mounted on the AIX system. The entire process would take no more than 30 minutes.

The PDC feature was tested in the customer’s lab environment and was put in...

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....

Kimberley | 27 Feb 2009 | 1 comment

Welcome to the Storage Management section of Symantec Connect! If you're coming here from the former Symantec Technology Network (STN) site, this may look pretty different. Connect is a new site, combining STN, Altiris Juice and the Altiris Technical Support Forums under one roof, along with a bunch of cool new features. To introduce myself, I'm Kimberley Bermender (username Kimberley), and I’ll be managing and modering the content for this section. Feel free to drop me a note if you have any questions, comments, suggestions or ideas.

While there’s a lot that’s new here, you’ll find familiar content from the STN Storage Foundation forums (Database Edition for Oracle, Storage Exec, Storage Foundation Family, Veritas Installation Assessment Service, Volume Manager, CommandCentral and Virtual Infrastructure), as well as articles that have all been migrated. There’s also a lot of new Storage content that the Development team has created, including...

Kimberley | 27 Feb 2009 | 0 comments

Written by: Thomas Cornely

What’s the Hardware Zero Reclaim functionality?  It basically refers to the array’s ability to scan a thin lun and look for pages of physical storage that contain ‘all zeroes’. When they find such a page, they reclaim the page (i.e. detach it from the thin lun) and put it back in the free pool. They can do this because the array returns ‘0’ to any I/O read it received on ‘unallocated space’ in a thin lun.

Who’s doing it?

Most hardware vendors are coming out with similar functionality. IBM XIV was the first one to have it. 3PAR has it. NetApp has it (they actually have true dedup in the array). Now Hitachi has it.

What are limitations of the Hardware Zero Reclaim functionality?

Hardware Zero Reclaim relies on the presence of 0 in the array to do the reclamation. In the context of a thick to thin migration, the process would be as follows:

  • start with 1...
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...

DLamorena | 06 Oct 2008 | 0 comments

Symantec's Dan Lamorena, Senior Product Marketing Manager, and Eric Hennessey, Director of Technical Product Management, introduce Veritas Cluster Server One.

Eric: Veritas Cluster Server One is the next evolution of Veritas Cluster Server, and its development has been driven by customer needs.

Veritas Cluster Server in its current form and architecture has been out for several years, and we found that we were starting to see limitations in what we could provide customers in very large, advanced environments-particularly those customers who are at the forefront of technology development and are quick to adopt new technologies to solve business problems.

These customer environments are multi-tiered. That is, they have a database server running on one OS platform, a middle tier application running on another, and a web tier on yet another. Veritas Cluster Server One gives these customers and their multi-tiered environments the ability to...

Ameya | 02 Apr 2007 | 0 comments

The Dynamic Multi Path (DMP) capability was first introduced in Volume Manager 2.5.7 release primarily to support A/A multi path arrays from Sun Microsystems. In those days, the early version of arrays had SCSI connections with fat and thick cables running from host to the array directly. Unlike the present day modern arrays, there was no concept of fabric switches, and no fiber channel (FC) technology enabled on the arrays. The first DMP could do only multi path operations such as load balancing using balanced path I/O policy, path failures and restoration by using SCSI inquiry commands. Since the number of devices were handful, the error processing and restore processing were all single threaded tasks. Further, as the number of supported arrays was small, the entire device discovery and reconfiguration was closely tied to the parent operating system.

The next major enhancements of DMP were introduced in Volume Manager 3.1.1 release that had support to co-exist with...