Re: [Veritas-vx] Stability of Veritas 5.1/6.0 compared to 5.0MP3

[Sengor]

Depending on your storage backend, we found that default VxDMP 5.1 and up
MinimumQ load balancing model was not as well/consistently performing as
Balanced under certain conditions on EMC Symmetrix hardware with many FA
paths (8+). This could hold true for other storage arrays. We've reverted
back to Balanced manually as it was per earlier patch revisions of 5.0 for
performance sensitive apps.


On 3 December 2012 19:11,  wrote:

> Hello,
>
> we have been using SFORA 5.0MP3 for quite long time. Since there is 5.1
> and 6.0
> for some time we are considering upgrade. Can anybody share his/her
> experience
> about stability of 5.1 and 6.0 compared to 5.0 (MP3) ? The stability is
> the most
> important for us and that is what concernes us.
>
>
> Regards
> Przemyslaw Bak (przemol)
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>



-- 
sengork
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

[Veritas-vx] Veritas SF Basic Licensing Keys

[Sengor]

Hi,

I cannot seem to find a straight answer as to why installer keeps
prompting for a valid license when installing SF Basic 5.1 (Solaris
x64 running within VMware - VRTS_SF_Basic_5.1_Solaris_x64.tar.gz).
According to official docs installer is meant to automatically handle
licensing on 2 CPU systems.

Bundled key doesn't seem to work either:

bash-3.00# cd storage_foundation_basic/
bash-3.00# ls -la
..
-rwxr-xr-x 1 root root 34 Jun 9 2006 .key
.
bash-3.00# cat .key
IEZH-I6ZX-KDYE-6PA6-J3PP-TOCP-NCP

bash-3.00# /opt/VRTS/bin/vxlicinst
Symantec License Manager vxlicinst utility version 3.02.34.0
Copyright (C) 1996-2008 Symantec Corporation. All rights reserved.
Enter your license key : IEZH-I6ZX-KDYE-6PA6-J3PP-TOCP-NCP
vxlicinst ERROR V-21-1-65 Invalid Operating System. Input license key
is not valid for this Operating System

bash-3.00# isainfo -vk
64-bit amd64 kernel modules
bash-3.00# psrinfo
0   on-line   since 04/12/2010 23:17:07
1   on-line   since 04/12/2010 23:17:11

bash-3.00# psrinfo -v
Status of virtual processor 0 as of: 04/12/2010 23:47:12
  on-line since 04/12/2010 23:28:12.
  The i386 processor operates at 3780 MHz,
and has an i387 compatible floating point processor.
Status of virtual processor 1 as of: 04/12/2010 23:47:12
  on-line since 04/12/2010 23:28:14.
  The i386 processor operates at 3780 MHz,
and has an i387 compatible floating point processor.

bash-3.00# uname -a
SunOS node1 5.10 Generic_141445-09 i86pc i386 i86pc


Any tips?

--
sengork
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] VxVm

[Sengor]

Guys,

A common misconception, I'm pretty sure PowerPath will failover stuff even
if you're using one of the native OS path devices as the filesystem mount
device. This is explicitly stated in the PP Admin guide and happens
transparently through the driver stack. Question should be which one of the
VxDMP or PP is actually actively doing multipathing, I'm guessing VxDMP goes
into passive mode when it sees PP.

Also there's a script which comes with VCS that'll probe your LUNs and
inquire whether they support any necessary SCSI reservations for the cluster
to operate. From memory it might have been vxfentsthdw.



On Wed, Mar 31, 2010 at 11:04 AM, Stuart Andrews <
stuart_andr...@symantec.com> wrote:

>  Colin
>
>
>
> OK – I see you are using enclosure naming – and BTW – the /dev/vx/dmp
> /dev/vx/dmp are just the same as disks BUT with the added provision of DMP
> to keep the device online.
>
> How many paths to these devices
>
> # vxdmpadm getsubpaths
>
> or
>
> # vxdisk path
>
>
>
> If a CLARiiON , and if only 2 paths – then set the array iopolicy to
> singleactive – this is most likely – see later for DMP
>
> # vxdmpadm listenclosure all
>
> # vxdmpadm setattr enclosure ENC_name iopolicy=singleactive
>
> If a CLARiiON , and if more than 2 paths – then set the array iopolicy to
> balanced – and DMP does know how to stop IO to the secondary paths.  Note –
> this is against EMC recommendations but it works.
>
> # vxdmpadm listenclosure all
>
> # vxdmpadm setattr enclosure ENC_name iopolicy=balanced
>
>
>
> I also notice that the enclosure names are lower case – indicating a V5.x
> release VxVM installed. – are the CLARiiON APMs running ?
>
> # vxdmpadm listapm all
>
> Check the CLARiiON are Active
>
>
>
> If a fencing cluster – then these are local LUNs at the point of
> /dev/vx/dmp names for the devices. And yes SCSI3 keys will be placed on them
> in a fencing cluster
>
> # gabconfig –a
>
> Check if there is Port b membership – if so then yes you have a fencing
> cluster.
>
>
>
> Check also the DMP block switch – it may be that with the iopolicy
> incorrect, and on low IO you did not reach the limit for
>
> # vxdmpadm gettune all
>
> dmp_pathswitch_blks_shift
>
> Now – when busy and IO chunks bigger than path switch level ( and with
> iopolicy incorrect ) a path switch will cause a trespass (check SAN logs)
>  AND a block, drain, resume on the DMP path. There will be a failover
> message logged in /etc/vx/dmpevents.log – check here also.
>
>
>
> Stuart
>
>
>  --
>
> *From:* veritas-vx-boun...@mailman.eng.auburn.edu [mailto:
> veritas-vx-boun...@mailman.eng.auburn.edu] *On Behalf Of *Collin
> *Sent:* Wednesday, 31 March 2010 2:09 AM
> *To:* William Havey
> *Cc:* veritas-vx@mailman.eng.auburn.edu
> *Subject:* Re: [Veritas-vx] VxVm
>
>
>
> Sorry for any confusion...
>
> I've got several powerpath devices from a dead system that I'm mounting
> temporarily on one node in my cluster.  I run a devfsadm -Cv and vxdctl
> enable.  After that I can see the powerpath devices listed as...
>
> emc_clarrion0_10  auto:none -  -online invalid
>
> I modified my /etc/vfstab file to mount the devices..
>
> /dev/vx/dmp/emc_clariion0_10s6   /dev/vx/rdmp/emc_clariion0_10s6   /u10
> ufs   3 yes -
>
> The device mounts and I can access the file system with all my data.  When
> the activity starts to increase on these temporary mount points, I see a
> count down on the console that port H has lost connectivity. After the 16
> seconds, the node panics and of course reboots.  However, if I mount the
> power path devices using a single path..
>
> /dev/dsk/c1t5006016100600432d10s6  /dev/rdsk/c1t5006016100600432d10s6
> /u10  ufs 3 yes -
>
> I never get the port H losing connectivity.
>
> I want to use the dmp name in case I lose a path to these disk.
>
> Any reason why using the dmp name causes port H to lose connectivity vs.
> using a single path?
>
> Thanks,
> Collin
>
> On Tue, Mar 30, 2010 at 10:48 AM, William Havey  wrote:
>
> The original message states "mount these disks as
> /dev/vx/dmp/_Xs6 ". Perhaps this is normal behavior. Mounts are
> of devices which receive I/O. A "/dev/vx/dmp/..." device entry isn't I/O
> capable.
>
> I think a clearer statement of what Collin intends to do is needed.
>
> Bill
>
>
>
> On Tue, Mar 30, 2010 at 3:01 AM, Dmitry Glushenok 
> wrote:
>
> Hello,
>
> Panic string and previous messages usually helps to understand cause..
> Release notes to RP2-RP3 also provides short descriptions of fixed issues
> like "Fixed the cause of a system panic when mutex_panic() was called from
> vol_rwsleep_wrlock()."
>
>
> On 29.03.2010, at 19:02, Collin wrote:
>
> > I've got the following
> >
> > Solaris 10
> > VxVM 5.0MP3RP1HF12
> >
>
> > I have a number of mount points that are being migrated from
> /dev/dsk/cXtXdXsX to clustered mount points.  The problem I'm having is if I
> mount these disk in the /dev/dsk/cXtXdXsX format I run the risk that if
> something

Re: [Veritas-vx] resize snapshot volume & original volume

[Sengor]

Hi,

Unfortunately you must unprepare, disassociate, remove Snap, expand original
volume, recreate new snap volume, associate and sync in full.
This is a big gotcha with VxVM Snaps even in 5.0!


On Wed, Mar 31, 2010 at 8:14 PM, Asiye Yigit  wrote:

>
>
>
>
> *Hello All;*
>
> * *
>
> *Is it possible to expand original volume and snapshot without needing
> snap prepare?*
>
> *When I resize original volume, is it a must to do snap prepare from the
> scratch?*
>
> * *
>
> * *
>
> *Regards;*
>
>
>
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>


-- 
sengork
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] Duplicate LUN id

[Sengor]

Hi,

Do you have EMC PowerPath installed on that box?

On Mon, Nov 2, 2009 at 9:53 PM, Fred  wrote:

> Hi all.
>
> I just wanted add 5 new LUN on a system running Solaris 10 and
> Veritas VERITAS-4.1_MP2_RP3.2.
>
> All ok with format. I was able to label the new 5 disks but Veritas
> doesn't.
> Also I can see duplicate LUN id like below
>
> EMC0_0   auto:sliced NSQ05NSQ-dg   online nohotuse
> EMC0_0   auto--error
> EMC0_1   auto:sliced NSQ06NSQ-dg   online nohotuse
> EMC0_1   auto--error
> EMC0_2   auto:sliced --online
> EMC0_2   auto--error
> EMC0_3   auto:sliced --online
> EMC0_3   auto--error
> EMC0_4   auto--error
> EMC0_4   auto:sliced --online
> EMC0_5   auto:sliced --online
> EMC0_6   auto:sliced --online
> EMC0_7   auto:cdsdisk--online
>
> vxdisk -e list
>
> EMC0_0   auto  NSQ05 NSQ-dg   online
> c3t5006048C4A377B67d270s2
> EMC0_0   auto  - -error
>  c3t5006048C4A377B67d270s2
> EMC0_1   auto  NSQ06 NSQ-dg   online
> c3t5006048C4A377B67d271s2
> EMC0_1   auto  - -error
>  c3t5006048C4A377B67d271s2
> EMC0_2   auto  - -online
> c3t5006048C4A377B67d278s2
> EMC0_2   auto  - -error
>  c3t5006048C4A377B67d278s2
> EMC0_3   auto  - -online
> c3t5006048C4A377B67d258s2
> EMC0_3   auto  - -error
>  c3t5006048C4A377B67d258s2
> EMC0_4   auto  - -error
>  c3t5006048C4A377B67d267s2
> EMC0_4   auto  - -online
> c3t5006048C4A377B67d267s2
> EMC0_5   auto  - -online
> c3t5006048C4A377B67d256s2
> EMC0_6   auto  - -online
> c3t5006048C4A377B67d253s2
> EMC0_7   auto  - -online
> c3t5006048C4A377B67d240s2
>
>
> Any clue?
>
> TIA
>
> Alfredo
>
>
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>


-- 
sengork
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] EMC PowerPath versus Veritas DMP?

[Sengor]

Hi,

EMC Powerpath has Symmetrix/Clariion optimised load balancing if you've got
the right licenses, and administratively speaking it's easier to identify
EMC specific SAN attributes via it's admin commands.

VxDMP's good enough for most cases providing you've got the appropriate ASL
installed for your array. However it's a bit more generic in terms of
identifying EMC specific components via it's admin interfaces.

On Tue, Oct 27, 2009 at 10:30 AM, Jon Price wrote:

>
> Hi,
>
> We have a Sun server running Solaris 9 connected to an EMC storage array
> via SAN.
> What are the advantages/disadvantages of using EMC PowerPath *instead 
> of*Veritas' dmp software?
>
> Thanks,
> Jon
>
>
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>


-- 
sengork
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] veritas scripts

[Sengor]

vea might be useful for visualising the end to end connectivity.

On Tue, Sep 8, 2009 at 12:33 AM, ajay raghuraj wrote:

> Hi Doug
>
> yes, i could do it manually. But there are so many volumes and so many
> hosts to check..i thought a script would be helpful
>
> Regards
> Ajay
>
> On Mon, Sep 7, 2009 at 10:30 PM, Doug Hughes  wrote:
>
>>  ajay raghuraj wrote:
>>
>>> Hi
>>>  I am looking for some veritas scripts on the net which will help me
>>> determine which plex has subdisks coming from two different arrays in a host
>>> based mirrored config.
>>>  Volume_xxx
>>> Plex0
>>> SD1
>>> SD2
>>> Plex1
>>> SD3
>>> SD4
>>>  SD1/2 are concatenated normally coming from one array and SD3/4 from
>>> another. The problem occurs  when SD1/2 come from two different arrays. I
>>> want to determine cuch faulty configs ..hence looking for a script
>>>  Regards
>>> Ajay
>>>
>>
>> Do you really need a script? run vxprint -ht. The subdisk is listed
>> directly under the plex it is associated with and has the plex name in
>> colunm 3. column 8 has the disk number. Depending upon whether your arrays
>> are split by controller or by tray (could be either), you can compare based
>> upon column 8.
>>
>> (you could check this with awk pretty trivially
>>
>
>
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>


-- 
sengork
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] vxdisk resize on EFI disk?

[Sengor]

Do you have powerpath on the box?
http://seer.entsupport.symantec.com/docs/292070.htm

On Tue, Apr 7, 2009 at 11:44 PM, Rongsheng Fang wrote:

> Hi,
>
> Is it possible to use "vxdisk resize" on a EFI disk? I tried it on a
> Solaris 10 5/08 with VxVM 5.0MP1 but got the following error:
>
> root # vxdisk -g backupDG resize backup-disk1
> VxVM vxdisk ERROR V-5-1-11476 Device backup-disk1: is an EFI
> device,resize operation not supported for EFI disks
>
> So basically I expanded the backend EMC CLARiiON LUN by 500GB to
> 1.5TB and was planning on dynamically resizing the LUN on Solaris.
> But this obviously doesn't work. Is there a VxVM patch in place for
> this to work, or any other way to fix this without tearing apart the
> LUN and re-doing everything?
>
> Thanks,
>
> Rongsheng
>
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>



-- 
sengork
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] SF 5.0 support for Sun Cluster 3.1 update 1

[Sengor]

I'm pretty sure you need v4.x for SC3.1. Check patchpro.sun.com &
http://docs.sun.com/app/docs/doc/819-1405/6n3p13hag?a=view

On Sat, Apr 4, 2009 at 12:51 AM, Asiye Yigit  wrote:

>  Hello All,
>
> In the web, there is nothing about the compatibility for Sun cluster 3.1
> update 1 and SF 5.0.
>
> Do you know whether I can use SF 5.0 with Sun cluster 3.1 update 1?
>
> Regards,
>
>
>
>
>
>
>
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>


-- 
sengork
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] Coexistence of DMP and MPxIO on same server

[Sengor]

Host based LUN Masking with pwwn-lun-blacklist won't help you in this
instance. I don't think you can exclude individual LUNs down the same path
out from MPxIO. I was going to suggest masking the ZFS and Vx LUNs to
different targets/array ports, and blacklsting them in MPxIO by target, but
this doesn't seem to be configurable at all on Solaris.

You could do zoning/masking for your ZFS/MPxIO LUNs down one HBA port & Vx
LUNs down the other HBA port. Once done, disable mpxio on the Vx LUNs HBA
port... But this will have single point of failure on either of the HBA
ports, not fully redundant as such...

Alternatively you could just enable MPxIO for both Vx and ZFS LUNs and just
make sure you don't end up mixing zpool LUNs with LUNs used in VxVM... This
way VxDMP will not be able to do any multipathing as it'll only see single
MPxIO device for each LUN and you'll not need to configure anything special
at driver level. We've got MPxIO and VxDMP on one system here, no issues
with it.

Take a look @ the sd.conf entries here
http://www.webservertalk.com/archive100-2005-4-1036354.html namely:

*Relevant "/kernel/drv/sd.conf" entries

[... omitted ...]
name="sd" parent="lpfc" target=0 lun=0 hba="lpfc0" mpxio-disable="no";
name="sd" parent="lpfc" target=1 lun=0 hba="lpfc0" mpxio-disable="no";
name="sd" parent="lpfc" target=2 lun=0 hba="lpfc1" mpxio-disable="no";
name="sd" parent="lpfc" target=3 lun=0 hba="lpfc1" mpxio-disable="no";
[... omitted ...]*
I wonder if this actually works, I can't find it in any f the documentation
but seems to be what you're looking for...
On Sat, Mar 28, 2009 at 4:28 AM,  wrote:

>
> Has anyone got any good advice on how to get DMP and MPxIO to coexist on a
> server with the disks sharing the same two HBA's??? I can get VxVM/DMP to
> ignore the disks ok, but trying to get MPxIO to do the same is proving to be
> a bit of a pain. Ideally I want to be able to exclude specific LUNs down
> each of the HBA paths. I thought I could do this via the
> 'pwwn-lun-blacklist' option in the fp.conf, but that just excluded the
> drives completely from the server. I need to do this as I've a requirement
> to use ZFS and VxVM on the same server. Any help or advice greatly
> appreciated.
>
> Cheers
> Phil.
>
> --
> This message is private and confidential and may also be legally privileged.  
> If you have received this message in error, please email it back to the 
> sender and immediately permanently delete it from your computer system.  
> Please do not read, print, re-transmit, store or act in reliance on it or any 
> attachments.
>
> British Airways may monitor email traffic data and also the content of 
> emails, where permitted by law, for the purposes of security and staff 
> training and in order to prevent or detect unauthorised use of the British 
> Airways email system.
>
> Virus checking of emails (including attachments) is the responsibility of the 
> recipient.
>
> British Airways Plc is a public limited company registered in England and 
> Wales.  Registered number: 177.  Registered office: Waterside, PO Box 
> 365, Harmondsworth, West Drayton, Middlesex, England, UB7 0GB.
>
> Additional terms and conditions are available on our website: www.ba.com
>
>
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>


-- 
sengork
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] EFI disk label on Solaris 10 with SF5.0 MP3

[Sengor]

format -e
> label
now choose EFI instead of SMI

On Wed, Mar 4, 2009 at 8:09 PM, Marianne Van Den Berg <
mvdb...@stortech.co.za> wrote:

>  Hi All
>
> I need some advise please. We tried to initialize new 1.2 TB luns (HDS
> AMS500). Error received: "Unable to read Disk geometry". We were working
> against time and did therefore not log a call with Symantec. The hardware
> engineers re-created 500Gb luns. After this, 'normal' VTOC was written and
> luns could be initialized.
>
> Research this morning shows that it's supposed to work (as per extract of
> 5.0 MP3 Release Notes below).
>
> Do you know if there are additional steps required to initialize EFI label
> disk?
>
>
> # uname -a
> SunOS node1 5.10 Generic_13-03 sun4v sparc SUNW,Sun-Blade-T6320
>
> Extract from Release Notes:
> Extensible Firmware Interface support (303294, 834313, Sun Bug ID 6226760)
> The Solaris 9 and 10 64-bit kernel Operating Systems provide support for
> disks
> larger than 1 terabyte. Disks of this size are formatted with the
> Extensible
> Firmware Interface (EFI) disk label rather than the VTOC disk label. EFI
> formatted
> disks are supported with Veritas Volume Manager only on Solaris 10 (SPARC).
>
> Kind regards
>
> Marianne
>
>
>
>  This email has been scanned for viruses and malware, and automatically
> archived by Mimecast SA (Pty) Ltd, an innovator in Software as a Service
> (SaaS) for business. Mimecast Unified Email Management ™ (UEM) offers
> email continuity, security, archiving and compliance with all current
> legislation. To find out more, contact 
> Mimecast.
> stormcid
>
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>


-- 
sengork
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] sfcfs configuration steps

[Sengor]

It mostlikely means you haven't told VxVM to initialise those disks. That is
they have not been used by VxVM previously and don't belong to a disk group.

On Mon, Mar 2, 2009 at 10:58 PM, Ravi kumar  wrote:

>
> Hi All,
>
> All my disks showing *online invalid, *some disk shows error.
> what is the probelm, how can we solve this.
> if anybody have idea please share to me.
>
>
> *server 1*
>
> -bash-3.00# vxdisk list
> DEVICE   TYPEDISK GROUPSTATUS
> c0t0d0s2 auto:none   --online invalid
> c0t1d0s2 auto:none   --online invalid
> c2t500601613060321Ad0s2 auto:none   --online
> invalid
> c2t500601613060321Ad1s2 auto--error
> c2t500601613060321Ad2s2 auto:none   --online
> invalid
> c2t500601613060321Ad3s2 auto:none   --online
> invalid
>
>
>
> *server 2*
>
> -bash-3.00# vxdisk list
>
> DEVICE   TYPEDISK GROUPSTATUS
> c0t0d0s2 auto:none   --online invalid
> c0t1d0s2 auto:none   --online invalid
> c2t500601613060321Ad0s2 auto:none   --online
> invalid
> c2t500601613060321Ad1s2 auto:none   --online
> invalid
> c2t500601613060321Ad2s2 auto:none   --online
> invalid
> c2t500601613060321Ad3s2 auto--nolabel
>
>
> Thanks,
>
>
>
> --
> Is your phone as unique as you are? Get a Windows Mobile phone, your style
> at Check it out! 
>
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>


-- 
sengork
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] VxFS & CFS compatibility for applications

[Sengor]

You should be asking the application vendor, you'll see the files with CFS
but whether app's going to cope with the simultaneous parallelism & not
corrupt the data, that's another question.

On Wed, Feb 18, 2009 at 8:24 PM, Pavel A Tsvetkov wrote:

>
> Hello all!
>
> Just one interesting question for me and perhaps for other people...
>
> There is some application running on VxFS (officially supported). We want
> to use this application on two nodes in parallel.
> It means we must use CVM and CFS.  Can we use CFS instead of VxFS  for that
> application?
>
> (In real life we have  IBM TSM for Space  Management 5.5/6.1  with HSM
> client on Solaris supporting VxFS4.1/VxFS5.0 )
>
> Thanks a lot , Pavel Tsvetkov
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>


-- 
sengork
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] Using Powerpath and DMP

[Sengor]

They can coexist. See
http://www.symantec.com/business/theme.jsp?themeid=yellowbooks "*Standardizing
Storage Management*"

On Wed, Feb 18, 2009 at 5:29 AM, Bhatla, Manish wrote:

>  Hi All,
>
>
>
> I am researching powerpath and DMP coexistence. I have several servers with
> Solaris 10 and Veritas 5.0 MP1.
>
> Powerpath 5.1 is the preferred failover/load balancing software used. I am
> trying to understand the implications of
>
> DMP and Powerpath coexistence.
>
>
>
> -  Is Powerpath and DMP allowed to coexist and if it does then is
> it recommended?
>
> -  Whats the best practices of setting up DMP with powerpath as
> failover/load balancing software?
>
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>


-- 
sengork
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] Help required in VCS cluster configuration

[Sengor]

One more thing:   https://vias.symantec.com/main.php

On Wed, Feb 11, 2009 at 11:05 AM, Sengor  wrote:

> Make use of the documnetation: http://sfdoccentral.symantec.com/
>
> Make use of the cluster simulator:
> http://www.symantec.com/business/products/utilities.jsp?pcid=pcat_business_cont&pvid=20_1
>
> Check compatibility matrices:
> http://www.symantec.com/business/support/documentation.jsp?language=english&view=comp&pid=15066
>
> On Wed, Feb 11, 2009 at 3:01 AM, alok tiwari  wrote:
>
>> Hi Andrey,
>>
>> I do not much about VCS , however I am well versed with VxVM.
>> I only know the basic concepts and have a understanding of cluster
>> configuration like Quorum etc.
>> I do not think that we can afford to hire any consultant or the VCS
>> configuration.
>> Do anyhaves some docs which containes some Peoplessoft specific cluster
>> config details.
>>
>> I will be highly thankful.
>>
>> Regards
>> Alok
>>
>> On Tue, Feb 10, 2009 at 2:30 AM, Andrey Dmitriev 
>> wrote:
>>
>>>  Documentation is available on Symatec's site.
>>>
>>>
>>>
>>> If you don't know anything about a product, I strongly suggest some
>>> training, and/or consultant help.
>>>
>>>
>>>
>>> -andrey
>>>
>>>
>>>
>>> *From:* veritas-vx-boun...@mailman.eng.auburn.edu [mailto:
>>> veritas-vx-boun...@mailman.eng.auburn.edu] *On Behalf Of *alok tiwari
>>> *Sent:* Monday, February 09, 2009 3:16 PM
>>> *To:* veritas-vx@mailman.eng.auburn.edu
>>> *Subject:* [Veritas-vx] Help required in VCS cluster configuration
>>>
>>>
>>>
>>> Hi All,
>>>
>>>
>>>
>>> I am going to do a VCS install and configuration. The cluster will run
>>> peoplesoft application and oracle database.
>>>
>>>
>>>
>>> I will be thankful if any one please sends me any manual or docs. I will
>>> be also thankful , if they can share any docs or issues faced when they have
>>> done the same.
>>>
>>>
>>>
>>> Thanks again. Waiting for some help.
>>> --
>>> With Regards:-
>>> Alok T
>>>
>>
>>
>>
>> --
>> With Regards:-
>> Alok Tiwari
>> 09819733350
>>
>> ___
>> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
>> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>>
>>
>
>
> --
> sengork
>



-- 
sengork
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] Help required in VCS cluster configuration

[Sengor]

Make use of the documnetation: http://sfdoccentral.symantec.com/

Make use of the cluster simulator:
http://www.symantec.com/business/products/utilities.jsp?pcid=pcat_business_cont&pvid=20_1

Check compatibility matrices:
http://www.symantec.com/business/support/documentation.jsp?language=english&view=comp&pid=15066

On Wed, Feb 11, 2009 at 3:01 AM, alok tiwari  wrote:

> Hi Andrey,
>
> I do not much about VCS , however I am well versed with VxVM.
> I only know the basic concepts and have a understanding of cluster
> configuration like Quorum etc.
> I do not think that we can afford to hire any consultant or the VCS
> configuration.
> Do anyhaves some docs which containes some Peoplessoft specific cluster
> config details.
>
> I will be highly thankful.
>
> Regards
> Alok
>
> On Tue, Feb 10, 2009 at 2:30 AM, Andrey Dmitriev wrote:
>
>>  Documentation is available on Symatec's site.
>>
>>
>>
>> If you don't know anything about a product, I strongly suggest some
>> training, and/or consultant help.
>>
>>
>>
>> -andrey
>>
>>
>>
>> *From:* veritas-vx-boun...@mailman.eng.auburn.edu [mailto:
>> veritas-vx-boun...@mailman.eng.auburn.edu] *On Behalf Of *alok tiwari
>> *Sent:* Monday, February 09, 2009 3:16 PM
>> *To:* veritas-vx@mailman.eng.auburn.edu
>> *Subject:* [Veritas-vx] Help required in VCS cluster configuration
>>
>>
>>
>> Hi All,
>>
>>
>>
>> I am going to do a VCS install and configuration. The cluster will run
>> peoplesoft application and oracle database.
>>
>>
>>
>> I will be thankful if any one please sends me any manual or docs. I will
>> be also thankful , if they can share any docs or issues faced when they have
>> done the same.
>>
>>
>>
>> Thanks again. Waiting for some help.
>> --
>> With Regards:-
>> Alok T
>>
>
>
>
> --
> With Regards:-
> Alok Tiwari
> 09819733350
>
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>


-- 
sengork
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] VxVM -- "Moving" Large Amounts of Data

[Sengor]

As others have pointed out, we don't really know which hardware and software
resources you've got at disposal.

- Most generic solution would be to use plexes to migrate the data.
- You'll need to mess around with zoning and masking on the SAN side
regardless of what option you take
- BCVs are going to be your friend if you're short on execution time, but
plentyful on planning time (and if you're just copying data within the same
array)
- Maybe SRDF is an option here too if you're moving from one array to
another.
- Joining and Splitting DGs would be my preference via either plex copies or
snapshots, but VxVM version might not allow you to do this natively (and
from what I recall you gotta  have licenses for certain types of snaps?).
- You could perhaps also do a ufsdump/vxdump or restore from your backups
infrastructure (this probably won't work for the raw vols, but depends how
it's backed up exactly).

All in all you'll need to look at the details and timeframes carefully
before deciding.

On Tue, Feb 10, 2009 at 12:14 PM, T  wrote:

> Hi all.
> Sorry about the vague subject.
>
> Here is the situation and I am really looking for any ideas or comments on
> the following:
>
> I have inherited 20TBs of data split between 2 Servers (
> Solaris/Sunfire/Sol8)
> 
>
> Each Server has 2 diskgroups.
> Oracle and Sybase Filesystems and Raw Volumes. ( Mixed between diskgroups )
>
> ** My main issue ( or so I think ) is going to be moving the Raw Volumes **
>
> ==
>
> I need to move ~5TBs from  to another server.  than move
> ~2TBs from 
>
> 1)  Get equal amount of EMC storage mapped to ServerC
>  Veritas mirror all the volumes from ServerA to ServerC
>  Break Mirror and "fix" any issues on ServerA.
>
> 2)   Would "FlashSnap" or any other "tool" allow me to copy/move volumes
> from 1  diskgroup   to another diskgroup.
> This would be the ideal situation, yes?
>
>
> Any ideas would be welcome and very much appreciated!
>
> Thank you.
>
> MWarnock
>
>
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>


-- 
sengork
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] Query 1

[Sengor]

Don't forget to freeze the node persistently.

On Tue, Feb 3, 2009 at 1:35 AM, i man  wrote:

> All,
>
> I plan to decomission one node which has a VCS and some disks assigned to
> VXFS.  The node has to be removed from VCS and then reinstall the OS on the
> system. VXFS has some disks coming from EMC SAN. Do I need to remove the
> disks from the VXFS before I reinstall the OS so as to not create any
> problems on the SAN side. I have switched off all the service groups and
> removed the node from the VCS cluster already. Also would it be wise to
> uninstall the VXFS from the node ?
>
> Ciao
>
>
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>


-- 
sengork
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] volume duplication

[Sengor]

http://prefetch.net/articles/veritasrecoveryfeatures.html
http://prefetch.net/blog/index.php/2006/11/19/recreating-veritas-configurations-with-vxmake/

On Wed, Nov 19, 2008 at 2:12 PM, Val Popa <[EMAIL PROTECTED]> wrote:
> I have a system that has ~200 raw volumes on a single
> dg and I have to create the same on a new system.
> Can anyone please educate me how to accomplish this
> the "easy way"
> Thanks
> V
>
>
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>



-- 
sengork
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] use fsadm to expand a filesystem while mounted

[Sengor]

I hope your filesystem doesn't hit 100% usage, else you'll have
troubles expanding it...

On Fri, Oct 24, 2008 at 5:23 AM, Hazel, Geoff <[EMAIL PROTECTED]> wrote:
> Doug, that makes perfect sense. Thanks!
>
>
>
> Geoff Hazel, UNIX System Engineer
> AT&T Mobility Network Operations
> Core Services Systems & Storage
> 425-877-5634 wireless
> 425-288-2034 desk
> [EMAIL PROTECTED]
>
> -Original Message-
> From: Doug Hughes [mailto:[EMAIL PROTECTED]
> Sent: Thursday, October 23, 2008 11:13 AM
> To: Hazel, Geoff
> Cc: veritas-vx@mailman.eng.auburn.edu
> Subject: Re: [Veritas-vx] use fsadm to expand a filesystem while mounted
>
> Hazel, Geoff wrote:
>> I'm going to be using fsadm tonight to expand a filesystem on an
>> existing volume.  The volume itself does NOT need expanding, it's big
>> enough, but the filesystem is smaller than the volume and I'm going to
>
>> enlarge it to the full size of the volume.
>>
>> 2 questions:
>>
>> I'm assuming I can do this "hot" while the filesystem is mounted and
>> all -- is that true?
> yes
>> Is there a flag on fsadm for "maxsize" to expand the filesystem to the
>
>> full size of the volume, or do I need to do calculations?
>>
> use the information from vxprint for the volume as the argument to -b.
> That's the proper way to do it.
>
>
>
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>



-- 
sengork
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] SF 5.0 : vxconfigd does not start with demo license key

[Sengor]

Did you remove /etc/vx/config.d/state.d/install-db ?

On Sun, Jul 20, 2008 at 11:05 AM, Marianne Van Den Berg
<[EMAIL PROTECTED]> wrote:
> Hi all
>
> We have recently installed SF5.0 on Solaris 10 with demo key (awaiting
> permament key).
>
> Demo key expires end of August. Error when trying to start vxconfigd:
>
> VxVM vxconfigd ERROR V-5-1-1589 enable failed: License has expired or is not
> available for operation
> transactions are disabled.
>
>
> I found 3 very old TechNotes, none of which are applicable (upgrade from Sol
> 2.6 to 8; missing localhost entry in /etc/hosts; system date set back).
>
> Any ideas?
>
> Kind regards
>
> Marianne
>
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>



-- 
_/ sengork.blogspot.com /

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] storage checkpoint - recommended ways to dump to tape

[Sengor]

Just a stab in the dark, but you should be able to mount the snapshot
into a temporary mount point and then try to do a normal filesystem
backup on the mounted filesystem. Alternatively could try something
like (cd /mnt; find . -depth | cpio -pvdm | gzip -f > dump.cpio.gz)

On Thu, May 15, 2008 at 12:19 PM,  <[EMAIL PROTECTED]> wrote:
> Hello,
>
> we are testing Solaris 10 + Veritas Storage Checkpoints.
> There is written in docs that vxdump/vxrestore doesn't work with
> Storage Checkpoints. Is tar the only way to dump (mounted)
> Storage Checkpoint to tape ?
>
> Regards
> przemol
>
> --
> http://przemol.blogspot.com/


-- 
_/ sengork.blogspot.com /

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] Disabled Controller Shows NONAME

[Sengor]

Try changing the disk naming convention forwards then backwards.
Seemed to work for us when we faced a similar situation.

On Mon, May 12, 2008 at 11:49 PM, Govind c <[EMAIL PROTECTED]> wrote:
> I have a lun serviced by mutliple paths .I had to disable one path for 
> reconfiguration purpose,since I longer need it.I disabled the controller c10 
> and I still get 5 paths with one path as NONAME device.
>
> How can i remove the NONAME without a reboot?
>
> Even vxdmpadm iostat command throws error because of the NONAME
>
> # vxdmpadm iostat show dmpnodename=c10t1d7s2 interval=5 count=10
> VxVM vxdmpadm ERROR V-5-1-8668 Invalid argument.
>
>
> # vxdisk list c10t1d7s2
> Device:c10t1d7s2
> devicetag: c10t1d7
> type:  auto
> hostid:eudrusadb
> disk:  name=index-vol2-1a-r5-3d id=1200522371.26.eudrusadb
> group: name=eudbdg id=1200521182.23.eudrusadb
> info:  format=sliced,privoffset=1,pubslice=4,privslice=3
> flags: online ready private autoconfig autoimport imported
> pubpaths:  block=/dev/vx/dmp/c10t1d7s4 char=/dev/vx/rdmp/c10t1d7s4
> privpaths: block=/dev/vx/dmp/c10t1d7s3 char=/dev/vx/rdmp/c10t1d7s3
> guid:  -
> udid:  
> STK%5FFLEXLINE%5F600A0B8000325F4246E83857%5F600A0B8000291BC66502478E0D60
> site:  -
> version:   2.1
> iosize:min=512 (bytes) max=2048 (blocks)
> public:slice=4 offset=0 len=877920256 disk_offset=98304
> private:   slice=3 offset=1 len=81663 disk_offset=16384
> update:time=1210623926 seqno=0.12
> ssb:   actual_seqno=0.0
> headers:   0 248
> configs:   count=1 len=60250
> logs:  count=1 len=9128
> Defined regions:
>  config   priv 17-000247[000231]: copy=01 offset=00 enabled
>  config   priv 000249-060267[060019]: copy=01 offset=000231 enabled
>  log  priv 060268-069395[009128]: copy=01 offset=00 enabled
> Multipathing information:
> numpaths:   5
> NONAME  state=disabled  type=primary
> c12t0d7s2   state=enabled   type=primary
> c13t4d7s2   state=enabled   type=secondary
> c1t203400A0B8325F42d7s2 state=enabled   type=primary
> c2t203500A0B8325F42d7s2 state=enabled   type=secondary
>
> # vxdmpadm getsubpaths ctlr=c10
> NAME STATE[A]   PATH-TYPE[M] DMPNODENAME  ENCLR-TYPE   ENCLR-NAME   
> ATTRS
> 
> NONAME   DISABLED   PRIMARY  c12t0d0s2FLEXLINE   -
> NONAME   DISABLED   SECONDARYc1t2d4s2 FLEXLINE   -
> NONAME   DISABLED   SECONDARYc12t0d5s2FLEXLINE   -
> NONAME   DISABLED   SECONDARYc12t0d2s2FLEXLINE   -
> NONAME   DISABLED   PRIMARY  c12t0d6s2FLEXLINE   -
> NONAME   DISABLED   PRIMARY  c12t0d1s2FLEXLINE   -
> NONAME   DISABLED   SECONDARYc12t0d3s2FLEXLINE   -
> NONAME   DISABLED   PRIMARY  c10t1d7s2FLEXLINE-
>
>
>
>
>  
> 
> Be a better friend, newshound, and
> know-it-all with Yahoo! Mobile.  Try it now.  
> http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>



-- 
_/ sengork.blogspot.com /

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] Study guide

[Sengor]

http://sfdoccentral.symantec.com/index.html

On Thu, May 1, 2008 at 9:29 PM, Kalpesh Khatlawala
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> HI everyone, can you send me the study guide for veritas SF or link of the
> study guide.
>
> regards,
>
> Kalpesh
>
>
> ___
>  Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
>  http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>



-- 
_/ sengork.blogspot.com /

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] Steps to upgrade from VERITAS 4.1 to 5.1

[Sengor]

I think some of the admin guides for 5.x might have a good basis for a plan

http://sfdoccentral.symantec.com/index.html

On Wed, Apr 16, 2008 at 2:58 PM, Mahajan, Mudit <[EMAIL PROTECTED]> wrote:
>
>
>
>
> Hi All,
>
>
>
> Just like to check if someone can share the upgrade steps from 4.1 to 5.1. I
> am running VERITAS with quick I/O + sybase version 12.5 database so I would
> appreciate if someone has tested.
>
>
>
> Thanks and Rgds,
>
>
>
> Mudit __
>
> This email is intended only for the use of the individual(s) to whom it is
> addressed and may be privileged and confidential.
> Unauthorised use or disclosure is prohibited.If you receive This e-mail in
> error, please advise immediately and delete the original message.
> This message may have been altered without your or our knowledge and the
> sender does not accept any liability for any errors or omissions in the
> message.
>
>
> ___
>  Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
>  http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>



-- 
_/ sengork.blogspot.com /

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] Enclosure-based naming and wrong order

[Sengor]

Someone correct me if I'm wrong.

As far as I know there is no strict relationship between the OS disk
device names and enclosure based naming. Patterns might be seen
visually in some cases but it's quite unintentional and coincidental.

On Tue, Apr 15, 2008 at 11:34 PM,  <[EMAIL PROTECTED]> wrote:
> Hi,
>
>  I have problem with disk names ordering. When I set operating
>  system-based naming:
>
>  bash-3.00# vxddladm set namingscheme=osn
>  bash-3.00# vxdisk -e list
>  DEVICE   TYPE  DISK GROUPSTATUS  
> OS_NATIVE_NAME
>  [...]
>  c2t50060E80102C6DC2d1s2 auto  - -error 
> c2t50060E80102C6DC2d1s2
>  c2t50060E80102C6DC2d39s2 auto  - -error 
> c2t50060E80102C6DC2d39s2
>  c2t50060E80102C6DC2d40s2 auto  - -error 
> c2t50060E80102C6DC2d40s2
>  c2t50060E80102C6DC2d41s2 auto  - -error 
> c2t50060E80102C6DC2d41s2
>  c2t50060E80102C6DC2d42s2 auto  - -error 
> c2t50060E80102C6DC2d42s2
>  c2t50060E80102C6DC2d43s2 auto  - -error 
> c2t50060E80102C6DC2d43s2
>
>  I get correct disk order. What I mean is that e.g. DEVICE *d39s2 is
>  OS_NATIVE_NAME *d39s2. From maintenance point of view the equal numbers 
> (here: 39) are important for us.
>  But when I change the naming scheme to enclosure-based:
>
>  bash-3.00# vxddladm set namingscheme=ebn
>  bash-3.00# vxconfigd -k
>  bash-3.00# vxdisk -e list
>  DEVICE   TYPE  DISK GROUPSTATUS OS_NATIVE_NAME
>  [...]
>  k2_0 auto  - -error 
> c3t50060E80102C6DC0d2s2
>  k2_1 auto  - -error 
> c3t50060E80102C6DC0d1s2
>  k2_2 auto  - -error 
> c3t50060E80102C6DC0d3s2
>  k2_3 auto  - -error 
> c3t50060E80102C6DC0d0s2
>  k2_4 auto  - -online 
> c2t50060E80102C6DC2d4s2
>  k2_5 auto  - -online 
> c2t50060E80102C6DC2d5s2
>  k2_6 auto  - -error 
> c3t50060E80102C6DC0d18s2
>
>  So the numbers are not equal (k2_6 != c3*d18s2). Is it possible to have
>  equal numbers ? Editing disks.info is not an option because when you
>  have huge number of luns ... no, it is not an option.
>
>  Why enclosure based naming behaves differently to os-based naming ?
>
>  Regards
>  przemol
>
>  --
>  http://przemol.blogspot.com/
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>  --
>  Poprowadz swoj klub do zwyciestwa!
>  Sprawdz >>> http://link.interia.pl/f1d76
>
>  ___
>  Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
>  http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>



-- 
_/ sengork.blogspot.com /

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] vxfs filesystem full - can not expand.

[Sengor]

Hi all,

I agree, there should be no special cases for what should be a routine
filesystem expansion. UFS can be grown any time, not matter what the
filesystem internals happen to be at the time of 100% fs full bonanza.
Even with sufficient monitoring in place, it's a bit hard to pickup
and prevent fastly growing filesystem usage from hitting the 100%
limit and stopping an application component. And it's especially
interesting seeing lots of SAN storage free on the DG only to realise
none of it can be used for growing the filesystem online.

Scott,

many thanks for the investigation into this. Seems we're not the only
ones facing this situation. We've grown the fs via other means
(application process freed up a bit of space eventually from one of
the files it was writing to, took a few hours).

Here's what we were able to do after growing the actual volume & above
process freeing the space up:

bash-2.05# fstyp -v /dev/vx/dsk/san/vol
vxfs
magic a501fcf5  version 7  ctime Fri May 18 11:19:20 2007
logstart 0  logend 0
bsize  8192 size  5288220 dsize  0  ninode 5288220  nau 0
defiextsize 0  ilbsize 0  immedlen 96  ndaddr 10
aufirst 0  emap 0  imap 0  iextop 0  istart 0
bstart 0  femap 0  fimap 0  fiextop 0  fistart 0  fbstart 0
nindir 2048  aulen 32768  auimlen 0  auemlen 1
auilen 0  aupad 0  aublocks 32768  maxtier 15
inopb 32  inopau 0  ndiripau 0  iaddrlen 1 bshift 13
inoshift 5  bmask e000  boffmask 1fff  checksum eb5643da
oltext1 11  oltext2 8708  oltsize 1  checksum2 0
free 376102  ifree 0
efree  8182 8580 8056 6205 4586 2886 1612 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0

bash-2.05# df -k .
Filesystemkbytesused   avail capacity  Mounted on
/dev/vx/dsk/san/vol   42305760 39291760 299355293%/san/vol

bash-2.05#  /usr/lib/fs/vxfs/fsadm -F vxfs -b 86708672 /san/vol
UX:vxfs fsadm: INFO: V-3-25942: /dev/vx/rdsk/san/vol size increased
from 84611520 sectors to 86708672 sectors

bash-2.05# df -k /san/vol
Filesystemkbytesused   avail capacity  Mounted on
/dev/vx/dsk/san/vol
 43354336 39291792 403390491%/san/vol

We've got a case open with Symantec, I'll email it separately... if I
can still find it that is...

-- 
_/ sengork.blogspot.com /

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] vxfs filesystem full - can not expand.

[Sengor]

On 3/17/08, Asim Zuberi <[EMAIL PROTECTED]> wrote:
>  Did you consider doing "fsck -F vxfs" on the filesystem?

Nope, since we need the fs to remain online.

-- 
_/ sengork.blogspot.com /

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] vxfs filesystem full - can not expand.

[Sengor]

On 3/17/08, Rajiv Gunja <[EMAIL PROTECTED]> wrote:
> Here is a trick I do. Find out the sizes of directories which are overly
> using space. Pick one which will bring the usage DOWN by 10%. Now tar/cpio
> the whole directory to a different partition and delete it.(of course
> logically, that directory should not be used by any of the applications
> actively. If they are, shutdown the app). Now expand it to whatever size you
> want to the hearts content. Veritas needs 5 to 10% of free space to do the
> actual expansion.

Tried that already, the issue with that approach was vxfs would not
even let any files be deleted or zeroed out from the affected
filesystem... So rm -fr and cat /dev/null would all fail with "no
space left" reasons.


-- 
_/ sengork.blogspot.com /

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] vxfs filesystem full - can not expand.

[Sengor]

On 3/15/08, Doug Hughes <[EMAIL PROTECTED]> wrote:
> You can still expand it, just pick a small number.. a block or two..
>  that gives you some space to expand it slightly more, and then slightly
>  more, and so in. It's not ideal, but it's a known issue and it works.
>  grow by a few bytes and then double and double and double until you get
>  where you want it to be.

Tried doing that as well, but not on such small quantities, lowest we
went to was about few MB. In either case I found this quite
surprising/dissapointing about vxfs.

Thanks for the tip, I'll keep it in mind for a certain next time encounter.

-- 
_/ sengork.blogspot.com /

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

[Veritas-vx] vxfs filesystem full - can not expand.

[Sengor]

Hi colleagues,

Recently we've had a situation where a mounted vxfs filesystem was @
100% usage (no free space) on Solaris 9, SF5. So we thought "great
we'll go and increase the volume & the filesystem and be done with
it".

To our unpleasant surprise fsadm returned error saying filesystem can
not be expanded due to it being full (even though volume has been
expanded already). We tried deleting some files from the affected fs,
to no avail. As root, even rm &  trying to zero out some of the files
simply refused to work due to the filesystem being full.

Now from what I understand there's no such thing as minfree root
reserved space for vxfs, which would allow the fs to be expanded once
it's full.

I'm quite disappointed to see vxfs not reserve any space on the side
for it's own administrative purposes, since fs being @ 100% is when
you need to expand the filesystem the most, out of any other case
scenarios.

How do people go about resolving or avoiding the issue of not being
able to expand the filesystem once it's full?

Are there any precautions/safeguards to consider when the fs is being
created initially? Perhaps some means of reserving administrative fs
space (without quotas) ?

Thank you.

-- 
_/ sengork.blogspot.com /

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] Remove CFS Mount?

[Sengor]

Hi Craig,

Easiest way is to use the GUI. hagui

On 2/27/08, Craig Simpson <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> I am running a SFRAC (Veritas VCS 5.0) cluster and want to remove a CFS
> mount.
>
> It is the one cut and pasted from the main.cf below.
>
>
>
> CFSMount cfsmount_devdata (
>
> Critical = 0
>
> MountPoint = "/oradata/data/dev"
>
> BlockDevice =
> "/dev/vx/dsk/oradatadg/devdatavol"
>
> MountOpt = "suid,rw"
>
> )
>
>
>
> How do I remove that from the clusters config?
>
>
>
>
>
> Thanks!
>
> Craig
>
>
>
>
>
>
> ___
>  Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
>  http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>


-- 
_/ sengork.blogspot.com /

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] vxdisk list shows disk in error status

[Sengor]

vxedit -fr rm might help

-- 
_/ sengork.blogspot.com /

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] QUESTIONS : Veritas Volume Manager from 3.5 to 5.0 data migration in Solaris 8/10

[Sengor]

Hi,

VxSF 5.0 supports DG versions 20-140. You don't need to upgrade and
the below procedure should work.

And yes as posted earlier by Mike, do make full backups of what you're
going to be migrating.

You might want to upgrade to a later version of DG once old server's
out of the picture.

On 1/21/08, Bill Mackler <[EMAIL PROTECTED]> wrote:
> Hi,
>
>
> Our current server "stanley" is running Solaris 8 and Veritas
> Foundation Suite for Oracle (VxVM/VxFS) 3.5-mp3.  All the disk groups
> in the associated storage has version 90 as below :
>
>
> "stanley" will be replaced by a new server with the same name running
> Solaris 10 and Veritas Storage Foundation 5.0-mp1.  Our plan is to
> attach all existing disk groups (version 90) from "stanley" to the new
> replacement server with Solaris 10 and latest Veritas Storage
> Foundation 5.0-mp1.  Please advise me the procedure to disconnect all
> existing disk groups from the "stanley" and reconnect them to new
>  replacement without going thru the upgrade of existing disk groups of
> version 90.   Our goal is to run Veritas 5.0 in the new "stanley"
> while accessing all original version 90 data in the disk group
>  hds9585dg.  We plan to just perform the steps -> 1.#deport hds9585dg
> 2. physical SAN disconnection of "stanley" and reconnection to new
> replacement server 3. #import hds9585dgPlease let us know if they
> are correct and if there is anything we are missing.
>
>
> Also, say we need to fall back to the old "stanely" serer running
> 3.5.  Is it possible to reverse the above steps after physically
> switch the SAN connection and  deport/import  from "version 90 disk
> group in Veritas 5.0" to "version 90 disk group in Veritas 3.5" ?  I
> want to make sure that there's no issue performing the steps in
> reverse.
>
>
> Thanks for your assistance,   Bill
>
>
> stanley# vxdg list hds9585dg
> Group: hds9585dg
> dgid:  1097031500.6964.stanley
> import-id: 0.11605
> flags:
> version:   90
> detach-policy: global
> copies:nconfig=default nlog=default
>  config:seqno=0.2252 permlen=28130 free=27921 templen=132
> loglen=4262
> :
> :
>
>
> stanley# pkginfo -l VRTSvxvm
>   PKGINST:  VRTSvxvm
>  NAME:  VERITAS Volume Manager, Binaries
>  CATEGORY:  system
>  ARCH:  sparc
>   VERSION:  3.5,REV=06.21.2002.23.14
>
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>


-- 
_/ sengork.blogspot.com /

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] Help with VCS

[Sengor]

Hi,

For quick reference:
http://eval.veritas.com/downloads/van/vcs_quickref.pdf
http://sysunconfig.net/vcs/vcs.html

For detailed install guides:
http://www.symantec.com/business/support/knowledge_base_results.jsp?content=all&SearchTerm=vcs+install&pdf=1&search=Search+Now

There is no such thing as a quickly instaled VCS cluster that works ;)

On 12/28/07, Rajinder Bhalla <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi Gurus,
>
>
>
> I have to urgently install and configure Veritas Cluster for a client but I
> have very limited knowledge on it. Can someone please help me with some
> useful documents or web links, I will be really grateful.
>
>
>
> Thanks in advance for your help. Any urgent help will be deeply appreciated.
>
>
>
> Regards,
>
> Raj
>  
>  Save all your chat conversations. Find them online.
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>


-- 
_/ sengork.blogspot.com /

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] vxresize with volume of type gen

[Sengor .]

On 12/13/07, A Darren Dunham <[EMAIL PROTECTED]> wrote:
> But you can always use 'fsadm','vxassist' in place of 'vxresize'.

Or VEA might help out with doing the 'details' :)


-- 
_/ sengork.blogspot.com /

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] vx_nospace

[Sengor .]

Hi,

I've got a feeling defragmenting the filesystem online might be worth a try.

On 12/14/07, Mohammed, Imtiaz U <[EMAIL PROTECTED]> wrote:
>
>
>
>
> I feel the filesysem is inconsistent and needs a fsck.
>
>
>
> If the server can be brought down to run level S, we can go for a fsck.
>
>
>
>
> If you can give the output of the vxprint –htg …. It would be more
> helpful.
>
>
>
> Regards
>
>
>
> Mohammed Imtiaz Uddin
>
> ANALYST APPS PROGRAMMING- SYS ADMIN (ITS- NCG)
>
> Building No.8, Ikon Towers, III Floor,
>
> Raheja IT park, Hitec City, Madhapur,
>
> Hyderabad - 500081
>
> Email: [EMAIL PROTECTED]
>
>  
>
>
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Asiye Yigit
>  Sent: Friday, December 14, 2007 2:51 AM
>  To: veritas-vx@mailman.eng.auburn.edu
>  Subject: [Veritas-vx] vx_nospace
>
>
>
>
> Hi,
>
>
>
> We are getting the following errors. However, there are plenty space in the
> file system according to the df –k command.  What things can cause such
> errors?
>
>
>
> Regards,
>
>
>
> Asiye Yigit
>
>
>
>
>
>
>
> Dec 12 20:10:55 sdpxp1 vxfs: [ID 702911 kern.notice] NOTICE: msgcnt 1 mesg
> 001: V-2-1: vx_nospace - /dev/vx/dsk/workdg01/u01vol file system full (256
> block extent)
>  Dec 12 20:11:01 sdpxp1 vxfs: [ID 702911 kern.notice] NOTICE: msgcnt 2 mesg
> 001: V-2-1: vx_nospace - /dev/vx/dsk/workdg01/u01vol file system full (8
> block extent)
>  Dec 12 20:11:07 sdpxp1 vxfs: [ID 702911 kern.notice] NOTICE: msgcnt 3 mesg
> 001: V-2-1: vx_nospace - /dev/vx/dsk/workdg01/u01vol file system full (8
> block extent)
>  Dec 12 20:11:13 sdpxp1 vxfs: [ID 702911 kern.notice] NOTICE: msgcnt 4 mesg
> 001: V-2-1: vx_nospace - /dev/vx/dsk/workdg01/u01vol file system full (8
> block extent)
>  Dec 12 20:11:19 sdpxp1 vxfs: [ID 702911 kern.notice] NOTICE: msgcnt 5 mesg
> 001: V-2-1: vx_nospace - /dev/vx/dsk/workdg01/u01vol file system full (257
> block extent)
>  Dec 12 20:11:25 sdpxp1 vxfs: [ID 702911 kern.notice] NOTICE: msgcnt 6 mesg
> 001: V-2-1: vx_nospace - /dev/vx/dsk/workdg01/u01vol file system full (41
> block extent)
>  Dec 12 20:11:31 sdpxp1 vxfs: [ID 702911 kern.notice] NOTICE: msgcnt 7 mesg
> 001: V-2-1: vx_nospace - /dev/vx/dsk/workdg01/u01vol file system full (17
> block extent)
>
>
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>


-- 
_/ sengork.blogspot.com /

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] VxVM 4.1, mirroring issue

[Sengor .]

Hi,

We've done this before to migrate data to new arrays and other servers
a while ago. After the plexes have fully synced you could do this:

- Dissasociate server B's LUNs from the DG:
vxplex -g  dis 
vxedit -g  -fr rm 
vxdg -g  -k rmdisk 

- Now unzone server B's LUNs from server A. (Alternative to rezoning,
you could rename the DG on server B's storage in the next step)

- Recreate the DG on server B, you'd need to use "vxdg -g  addisk
-k " option to recreate the DG (I can't recall exact
procedure for this).

- Start all the volumes on server B (vxvol -g  [startall|recover])

Hope that helps.

On 12/1/07, Rajinder Bhalla <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi Gurus,
>
>
>
> I have a small problem for which I need your help.
>
>
>
> My requirement is to copy data from one server A to a new server B but I
> have to do it only through Veritas VxVM mirroring. The disks from server B
> are dual zoned with server A. I have mirrored the plexes on Server A with
> the disks from server B but don have any idea how to mount them back on
> server B.
>
>
>
> Can someone please advice me with the steps on how can I do this. The OS I
> am using here is Solaris 8.
>
>
>
> Any quick help will be deeply appreciated.
>
>
>
> Regards,
>
> Raj
>  
>  Now you can chat without downloading messenger. Click here to know how.
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>


-- 
_/ sengork.blogspot.com /

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] rebuild of vxvm configuration for disaster recovery

[Sengor .]

Hi,

Perhaps you could utilise the capabilities of vxconfigbackup & vxconfigrestore.

see:
http://prefetch.net/articles/veritasrecoveryfeatures.html
http://prefetch.net/code/vxvmconfigbackup.html

On 11/28/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
> Hello Everyone,
>
> I am attempting to automate recovery of a multitude of servers for DR
> testing,  I have several servers using vxvm managed disk ranging from
> hundreds of volumes in multiple disk groups and terabytes of capacity, to
> single disk groups with a few gigabytes.
>
> I will gather metadata about each system that would allow me to recreate the
> vxvm configuration on test servers with a disk configuration that will be
> completely different hardware wise, but with at least as much or greater
> capacity.  The disks could be SAN connected or direct SCSI attached.  A high
> level summary of what I would like to do is listed below:
>
> 1.  Script to gather information about disk groups in use, such as number of
> dg's, names and total capacity.
> 2.  Script to gather information about volumes within each disk group.
> 3.  Script to gather information about mounted filesystems and volumes used
> by databases such as Oracle and Informix.
> 4.  Configure target server with adequate disk capacity to recreate the dg's
> and vxvm software.
> 5.  Script to create each disk group with at least as much or more capacity
> as the original group.
> 6.  Script to create volumes within each disk group.
> 7.  Script to create and mount filesystems on newly created volumes.
> 8.  Perform restores of filesystems and databases.
>
> Before I begin the creating the scripts required to facilitate the above
> process, I thought I would ask the experts on this list.  I know that there
> must be others that are doing the same thing for disaster recovery.
>
> Thanks,
>
>
> Richard Hale
> Unix System Administrator
> Pegasus Solutions Inc.
> 480-624-6598
> www.pegs.com
>
> This email, including any attached files, may contain confidential and
> privileged information. If you are not the intended recipient (or authorized
> to receive information for the recipient), you are hereby notified that any
> dissemination, distribution or copying of this communication is strictly
> prohibited. If you received this communication in error, please contact the
> sender by reply email and delete all copies of this message.
>
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>


-- 
_/ sengork.blogspot.com /

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] Veritas Upgrade - 3.5 to 4.0

[Sengor .]

http://seer.entsupport.symantec.com/docs/265468.htm
http://seer.entsupport.symantec.com/docs/265450.htm

On 11/27/07, Artur Baruchi <[EMAIL PROTECTED]> wrote:
> Hi Guys,
>
> I have to upgrade the veritas FS and veritas VM. Servers are running
> veritas 3.5 and I have to upgrade to 4.0. Does anybody have a
> procedure to do it?!
>
> Thanks
>
> Att.
> Artur Baruchi
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>


-- 
_/ sengork.blogspot.com /

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] DMP question

[Sengor .]

Thanks Thomas,

I've seen the new WP on VxDMP, only the old one seems to discuss VxDMP
& PP specifics. One of our clients has both VxDMP and PP installed on
the same (large) set of servers connected up to EMC DMX arrays.

I've never understood the reason nor result of having both VxDMP 5.0
and PP 4.5 together. Normally only one'd be sufficient for load
balancing & failover. The older WP seems to be the only one which
touches on this coexistence subject (nothing on powerlink either which
I could find).


On 11/2/07, Thomas Cornely <[EMAIL PROTECTED]> wrote:
> Sengor, Ajay,
>
> There's an updated version of the DMP whitepaper (covering the latest 5.0 
> enhancements) at:
> http://eval.symantec.com/mktginfo/enterprise/white_papers/ent-whitepaper_vsf_5.0_dynamic_multi-pathing_05-2007.en-us.pdf
>
> As far as load balancing is concerned, DMP has historically outperformed PP. 
> The names of the PP algorithms really is more marketing than anything else. 
> If you have a chance, try out DMP 5.0's Minimum Queue algorithm and compare.
>
> Thomas
>
>
> > -Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf
> > Of Sengor .
> > Sent: Wednesday, October 31, 2007 9:10 PM
> > To: robertinoau
> > Cc: ajay raghuraj; veritas-vx@mailman.eng.auburn.edu
> > Subject: Re: [Veritas-vx] DMP question
> >
> > VxDMP and PP can co-exist on the same server:
> >
> > http://eval.veritas.com/mktginfo/products/White_Papers/Storage
> > _Server_Management/sf_dmp_wp.pdf
> >
> > PP has EMC specific load balancing algorithms specific to
> > their arrays. I believe ASL's for EMC arrays do not have
> > array specific optimised versions of load balancing.
> >
> > On 11/1/07, robertinoau <[EMAIL PROTECTED]> wrote:
> > >
> > > You are running PowerPath, therefore what you are seeing is
> > 100% correct.
> > >
> > > Remove powerpath and install the ASL for you array if you want DMP.
> > >
> > >
> > > - Original Message 
> > > From: ajay raghuraj <[EMAIL PROTECTED]>
> > > To: veritas-vx@mailman.eng.auburn.edu
> > > Sent: Wednesday, 31 October, 2007 9:59:17 PM
> > > Subject: [Veritas-vx] DMP question
> > >
> > >
> > > Hi,
> > >
> > > It looks like multipathing is missing . But I am not sure
> > where it is
> > > enabled . Is it in veritas / powerpath / native as this is
> > Sol 10. On
> > > Sol 10 how do we check multipathing as been enabled or not ? Is it
> > > some option with stmsboot ?
> > >
> > > Secondly if I have to enable it in veritas , how do i do it
> > ? and how
> > > do I verify ?
> > >
> > > vxdmpadm listctlr all
> > >
> > > CTLR-NAME   ENCLR-TYPE  STATE  ENCLR-NAME
> > > =
> > > emcpEMC ENABLED  EMC0
> > > c4  EMC DISABLED EMC0
> > > c3  EMC DISABLED EMC0
> > > c1  DiskENABLED  Disk
> > > c4  EMC ENABLED  EMC1
> > > c3  EMC ENABLED  EMC1
> > >
> > > vxdisk -g mifd_prd_oradg list emcpower18s2
> > >
> > > Multipathing information:
> > > numpaths:   1
> > > emcpower18c state=enabled
> > > vxdisk -o alldgs list
> > > .
> > > .
> > > .
> > > EMC1_17  auto--error
> > > EMC1_17  auto--error
> > > EMC1_17  auto--error
> > > .
> > > .
> > > emcpowerXX
> > > emcpowerxy
> > > emcpowerxz
> > >
> > > Regards,
> > > Ajay
> > >
> > >
> > >  
> > >  Feel safe with award winning spam protection on Yahoo!7 Mail. Find
> > > out more.
> > > ___
> > > Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> > > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
> > >
> > >
> >
> >
> > --
> > _/ sengork.blogspot.com /
> >
> > ___
> > Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
> >
>


-- 
_/ sengork.blogspot.com /

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Re: [Veritas-vx] DMP question

[Sengor .]

VxDMP and PP can co-exist on the same server:

http://eval.veritas.com/mktginfo/products/White_Papers/Storage_Server_Management/sf_dmp_wp.pdf

PP has EMC specific load balancing algorithms specific to their
arrays. I believe ASL's for EMC arrays do not have array specific
optimised versions of load balancing.

On 11/1/07, robertinoau <[EMAIL PROTECTED]> wrote:
>
> You are running PowerPath, therefore what you are seeing is 100% correct.
>
> Remove powerpath and install the ASL for you array if you want DMP.
>
>
> - Original Message 
> From: ajay raghuraj <[EMAIL PROTECTED]>
> To: veritas-vx@mailman.eng.auburn.edu
> Sent: Wednesday, 31 October, 2007 9:59:17 PM
> Subject: [Veritas-vx] DMP question
>
>
> Hi,
>
> It looks like multipathing is missing . But I am not sure where it is
> enabled . Is it in veritas / powerpath / native as this is Sol 10. On Sol 10
> how do we check multipathing as been enabled or not ? Is it some option with
> stmsboot ?
>
> Secondly if I have to enable it in veritas , how do i do it ? and how do I
> verify ?
>
> vxdmpadm listctlr all
>
> CTLR-NAME   ENCLR-TYPE  STATE  ENCLR-NAME
> =
> emcpEMC ENABLED  EMC0
> c4  EMC DISABLED EMC0
> c3  EMC DISABLED EMC0
> c1  DiskENABLED  Disk
> c4  EMC ENABLED  EMC1
> c3  EMC ENABLED  EMC1
>
> vxdisk -g mifd_prd_oradg list emcpower18s2
>
> Multipathing information:
> numpaths:   1
> emcpower18c state=enabled
> vxdisk -o alldgs list
> .
> .
> .
> EMC1_17  auto--error
> EMC1_17  auto--error
> EMC1_17  auto--error
> .
> .
> emcpowerXX
> emcpowerxy
> emcpowerxz
>
> Regards,
> Ajay
>
>
>  
>  Feel safe with award winning spam protection on Yahoo!7 Mail. Find out
> more.
> ___
> Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>


-- 
_/ sengork.blogspot.com /

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx