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, Storage Management

Products:

Topics

idea RSS

Suggested November 1, 2009 4:37PM by beautwaves

No comments yet.

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

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.

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 14, 2009 6:38AM by MDedek

I would like to see an update made to Symantec Command Central to support AIX VIO Servers, without this support you are unable to get a clear picture of all the storage assigned to those servers.

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

In Review

Suggested August 27, 2009 4:24AM by Marianne van de...

We know that site tagging is available in SF 5 for Unix. We need to be able to do the same in Windows. It does not seem to be available yet.

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 August 11, 2009 9:17AM by WizzardS10

It is often difficult to schedule outages on clusters with more than 1 active nodes. This is a High availability environment after all. Please provide an upgrade path to allow upgrading a single node at a time. Granted all of the new features may not be available until after all of the nodes have been upgraded.

4 Comments (last comment 5 weeks 2 days ago)

Status:

In Review

Suggested August 11, 2009 8:56AM by WizzardS10

We have been upgrading our clusters from Storage Foundation HA for Windows 4.3 to 5.1, with many stability issues after the upgrade. We often have the VMDg and MV agents fault randomly. We have opened many cases with Symantec, and have been told to set the Storage Agent service recovery actions to 'Take No Action'. A new install set's up this service correctly, but upgrades do not. Please modify the upgrade process to install all services, including ...

1 Comments (last comment 1 week 6 days ago)

Status:

Implemented

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 12 weeks 5 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

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

Volume Status description vs Volume State in vxprint output

Share This

Community Feed