Storage Management | Symantec Connect

Storage Management IdeasRSS

Volume Status description vs Volume State in vxprint output

By beautwaves | November 1, 2009 4:37PM

The Volume Status table in the SFW 5.1 admin guide lists lots of status values as well. However, after finding the Degraded status showing up as "-" in the vxprint output, I wondered how the rest of the possible Status values will look like in real-life. I'm unable to simulate many anomaly scenarios with our limited test systems. Read more

Tagged with: Storage Foundation for Windows, In Review, Storage Management

Products:

Topics

idea RSS

Suggested November 10, 2009 1:35AM by Gaurav Sangamnerkar

Veritas SF product till 4.1 was by default taking & keeping 5 backup copies of diskgroups under /etc/vx/cbr/bk directory. Starting 5.0, this was reduced to only one copy. In most of the cases, diskgroup configuration gets modified the same day & issue occurs on the same day. As a result we are not left with any last known good config copy. It would be great if this is changed default to 5 copies as was in previous versions. I agree that since 5.0 can support very large ...

No comments yet.

Status:

In Review

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.

3 Comments (last comment 6 days 19 hours ago)

Status:

In Development

0 votes

Suggested November 9, 2009 9:02PM by Gaurav Sangamnerkar

In all versions of Storage Foundation suite, Symantec provides a feature of IOFencing to prevent Cluster Split Brain situation & prevent data corruption. As per design, IOFencing is a passive module i.e it doesn't react live unless there is any GAB port membership change. In case cluster keeps running fine, there is no check which is done by IOFencing module. It would be great if IOFencing module is made intelligent so that it performs frequent checks whether the coordinator disks ...

No comments yet.

Status:

In Review

0 votes

Suggested October 15, 2009 9:54AM by Kapalin

Installing the ASL when the VxFS file system is mounted creates an issue like I/O hang at times. Support team always suggests to umount the file system in safer side and install the ASL. But there is no information about this in the ASL technotes. It would be better if we can give some safe guidelines before installing the ASL.

No comments yet.

0 votes

Suggested September 2, 2009 2:09PM by gmartino

Please add VxVM support for Sun Storage 7000 Unified Storage Systems. Currently this is not supported under Solaris VxVM 5.0 MP3.

No comments yet.

Status:

Reviewed

Suggested August 10, 2009 5:58PM by Tomer Gurantz

vxevac command only takes "Media Names" (i.e. individual disks) as an argument for where you want to evacuate from and to. This command should be updated to accept options like "ctlr:c1" and "enclr:array0" type options. There should be some care, as this could cause a lot of evacuations to run at once, but hey, you're root. Perhaps these should run in sequence (instead of in parallel). Keep in mind, the only way this could cause a lot of work to ...

1 Comments (last comment 14 weeks 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 2 weeks 2 days ago)

Status:

Reviewed

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 4 weeks 2 hours ago)

Status:

In Review

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 26 weeks 2 days ago)

Status:

Implemented

Show Listings per page

Volume Status description vs Volume State in vxprint output

Share This

Community Feed