[Veritas-vx] How to fix write an active config db to each and every disk of the disk group ?

Hi List, When I have a healthcheck of my system, I found that some config db in the private region is broken as the following: #vxdg list mydg Group: mydg dgid: 1117663755.1265.my-db1 import-id: 0.3301 flags: version: 90 detach-policy: global copies:nconfig=d

Re: [Veritas-vx] How to fix write an active config db to each and everydisk of the disk group ?

Hi, I don't see anything in this configuration that is broken ? It appears that VxVM is using its default mode to distribute configDB/log copies across devices in the disk group. Note, disabled does not necessary mean broken. As for the command, it does not appear you have a object named "dg" ?

Re: [Veritas-vx] How to fix write an active config db to each and every

> config disk c3t10d0s2 copy 1 len=7489 state=clean online > config disk c3t11d0s2 copy 1 len=7489 state=clean online > config disk c3t12d0s2 copy 1 len=7489 state=clean online > config disk c3t13d0s2 copy 1 len=7489 disabled > config disk c4t10d0s2 copy 1 len=7489 state=clean online > config disk

[Veritas-vx] Disk Name reported as "NONAME" and dmpnodename as "NONAME"

The following was done on this solaris 9.0 host to remove access to certain SAN disks on c4 and c6. 1. vxdisk rm 2. luxadm -e offline 3. Zoning removed so that the host can no longer see the SAN disks 4. devfsadm -C to clear /dev/dsk and /dev/rdsk enteries 5. rm /dev/vx/dmp/ and /dev/vx/r

Re: [Veritas-vx] VRTSvxfs patch 119302-02 for 4.1 MP1

I had to manually modify the patch's "pkginfo" and "pkgmap" files. What's happening is pkginfo doesn't have those variables set, so it tries to unset them when it installs the patch (they're set to true - and there's another one you run into after the one you've seen). I modified the pkginfo

Re: [Veritas-vx] Storage Foundation on Solaris 10 ...

Thanks, Greg. We have called Sun and recommending hardware changes - but cannot confirm yet on what course of action they want to take. I created a flash archive off of another V890 (with Storage Foundation & Netbackup installed - which is up and running with no errors so far) and rebuilt this

Re: [Veritas-vx] VRTSvxfs patch 119302-02 for 4.1 MP1

This is a known issue. Please contact Symatec Tech Support. - Original Message From: Ganesh Persaud/SYS/NYTIMES <[EMAIL PROTECTED]> To: veritas-vx@mailman.eng.auburn.edu Sent: Thursday, 7 December, 2006 9:08:34 AM Subject: [Veritas-vx] VRTSvxfs patch 119302-02 for 4.1 MP1 The patch b

Re: [Veritas-vx] Disk Name reported as "NONAME" and dmpnodename as "NONAME"

Run the following commands to clean up the NONAME devices. vxdisk rm NONAMEs2 Run the above command until there are no "NONAME" disks in vxdisk list. rm /dev/dsk/NONAME* rm /dev/rdsk/NONAME* rm /dev/vx/dmp/NONAME* rm /dev/vx/rdmp/NONAME* mv /etc/vx/disk.info /etc/vx

[Veritas-vx] Error happened on the configDB, How to fix it ???

Hi List, In my configuration, I found the following information: #vxdg list mytestdg Group: mytestdg dgid: 1117663760.1274.my-db1 import-id: 32768.3295 flags: shared version: 90 detach-policy: global copies:nconfig=default nlog=default config:seqno=0.1284 perml

Re: [Veritas-vx] VRTSvxfs patch 119302-02 for 4.1 MP1

Hi Got this from our trainer (Don't know why Symantec hasn't published this in a TechNote): The following lines need to be added to all Solaris 10 VxFS patches: SUNW_PKG_ALLZONES=true SUNW_PKG_THISZONE=false SUNW_PKG_HOLLOW=true # grep pkginfo pkgmap 1 i pkginfo 514 37549 1129677685 # ls -l p