Clustering and Replication | Symantec Connect

Clustering and Replication IdeasRSS

Products:

Topics

idea RSS

Suggested May 22, 2009 6:26PM by .peter

Use this new feature to suggest new ideas for Symantec products or services - or even suggest new ideas for this website. Once your idea has been submitted, other community members can vote on it. The top ideas move to the top where they are reviewed by Symantec product managers. For a quick demo of how ideas work, watch this video:

2 Comments (last comment 24 weeks 1 day ago)

Status:

Implemented

Suggested September 30, 2009 9:39AM by sfha_user

Adding an install script for the Rolling patches like the MP's for Solaris would be very helpful. Lately Rolling Patches have been patching all the products so it takes time to figure out all the patches that need to be installed.

No comments yet.

Status:

In Review

0 votes

Suggested September 29, 2009 5:25PM by Istvan Takacs

Is it possible to add the support of this VCS agent type to the x64 Solaris based Agent Pack, please?

No comments yet.

Status:

In Review

Suggested September 13, 2009 7:32PM by Jeff Vandervoort

Prelude Initially, I wrote this about Backup Exec, because that's where I ran into this problem. I'm also a SAV & SEP veteran but don't recall seeing this heinous language in their KB articles. So maybe it's a Veritas thing. But, whatever... ...then it occurred to me that while BE may (or may not) be the only Symantec enterprise product to which the symptom applies, the cure is universal. Because it bridges a huge gap between the goals of Symantec Sales, Support, ...

15 Comments (last comment 5 weeks 5 days ago)

0 votes

Suggested August 25, 2009 8:06AM by dmauri

Customer needs to monitor Sybase DB installed on a Solaris branded zone, using Sybase enterprise agent configured with VXCluster and installed in a Solaris global zone. See case 240-989-061

No comments yet.

Status:

In Review

0 votes

Suggested August 24, 2009 12:51PM by kalyan subramaniyam

When a resrouce is getting restarted when configured with RestartLimit (type level attribute). In case if customer does not have notifier configured, does not able to get to know that the resrouce got restarted. we can use the ResStateChange trigger, but it is a group level and have impact in failover times and consume resoruces in large configuration (like 400 resrouces). how about have a trigger which is tied to the engine, and trigger an event when engine restarts an resrouce.

No comments yet.

Status:

In Review

Suggested August 19, 2009 10:50PM by Tomer Gurantz

On VCS UNIX the engine_A.log provides highly useful information, e.g. if an IP address already exists on the network, the IP resource in VCS will not bring it up due to duplicate IP addresses. You will see the following message in the engine_A.log: 2009/08/20 16:35:08 VCS NOTICE V-16-1-10301 Initiating Online of Resource ip2 (Owner: unknown, Group: ip2sg) on System train11 2009/08/20 16:35:08 VCS WARNING V-16-10001-4005 (train11) IP:ip2:online:Address 192.168.27.141 already exists: Resource ...

2 Comments (last comment 1 week 6 days ago)

Status:

Already Offered

Suggested July 13, 2009 4:03PM by Sunil Gawali

Most of the VCS admins are aware that if they have to run NFS HA, they have to ensure that respective major number for vxio and vxspec is unique across all the cluster nodes. Currently, VCS install script does not check for any discrepancy on this. The experienced [and/or trained] VCS admins know that this is "must" check before building the cluster, many relatively new VCS admins fail to check this before hand and face problems. How about the VCS install script checking this and ...

1 Comments (last comment 1 day 11 hours ago)

Status:

In Review

0 votes

Suggested July 10, 2009 8:57AM by Sampath Kari 7485039

- It would be useful to have support for Xen domU failover with VCS (similar to what you support for containers on Solaris10 now) -Also it would be useful to have support for VXFS and CFS on Xen dom0 so that we can use that setup to have Xen Cluster instead of using other native Novell SLES included products for this one-off setup while using Veritas Solutions for rest of the needs in the company.

No comments yet.

Status:

In Review

Suggested July 10, 2009 5:23AM by EGriffin

Windows: When offlining the Windows lanman agent, it does not remove the Windows DNS records (A and PTR). However, when failing over to the remote cluster the lanman agent does update DNS correctly. Unfortunately, during this process it leaves behind the original PTR record. After failing over, we now have two PTR records, one pointing to the Original IP and another one pointing to the New IP. Unix: When offlining the Unix DNS agent, it removes the appropriate A and PTR ...

1 Comments (last comment 1 week 6 days ago)

Status:

In Review

Show Listings per page

Share This

Community Feed