[Veritas-vx] couldn't encapsulate boot disk

2010-10-06 Thread Asiye Yigit
Hello; I have installed SP 5.1RP2 on solaris 10 system. I am trying to encapsulate the boot disk and after that I will make mirror. In the vxdisk list, It shows DEVICE TYPEDISK GROUPSTATUS disk_2 auto--

Re: [Veritas-vx] couldn't encapsulate boot disk

2010-10-06 Thread Christian Gerbrandt
As you can see, disk_2 is showing in 'error' state. But it should show as 'online invalid'. There seems to be an error with the disk. Check the status of the disk from OS/VxVM and SAN. From: veritas-vx-boun...@mailman.eng.auburn.edu [mailto:veritas-vx-boun...@mailman.eng.auburn.edu] On

Re: [Veritas-vx] couldn't encapsulate boot disk

2010-10-06 Thread Hudes, Dana
don't do it. There is no longer, with a Solaris 10 system such as your 5120, a valid reason to use VERITAS boot disk encapsulation. Use ZFS. As I recall the 5120 has hardware mirroring so you could use that or you could use ZFS mirroring. The advantage of hardware mirroring is that it doesn't

Re: [Veritas-vx] couldn't encapsulate boot disk

2010-10-06 Thread DeMontier, Frank
By default, the upgrade changes the naming from osn ( os native ) to ebn ( enclosure based ). Additionally, disk_0 will not necessarily be c0t0d0s2, it could be c0t1d0s2. Run the following command and see if this clears up some of the confusion: vxddladm set namingscheme=osn persistence=yes

Re: [Veritas-vx] couldn't encapsulate boot disk

2010-10-06 Thread Hudes, Dana
yes it is still supported. Veritas has to support the same features on any platform. that's part of the point of Veritas. go right ahead and do your experiment. while you're at it you could dig out the procedure for a more pure veritas disk. From:

Re: [Veritas-vx] couldn't encapsulate boot disk

2010-10-06 Thread William Havey
Since your following the Symantec suggestions, they state the boot disk must Ø Two free partitions. Ø 2048 consecutive sectors free. Ø Enclosure-based names (EBN) has not been implemented (pre 5.1). Ø Partition 2 spans the whole device with no defined file system. You've still got to deal

Re: [Veritas-vx] couldn't encapsulate boot disk

2010-10-06 Thread Asiye Yigit
Yes, But it is in error state. I will open a case to symantec support I think. From: Hudes, Dana To: Asiye Yigit; ger...@gotadsl.co.uk ; veritas-vx@mailman.eng.auburn.edu Sent: Wed Oct 06 18:46:49 2010 Subject: RE: [Veritas-vx] couldn't encapsulate boot disk

Re: [Veritas-vx] Solaris-SFS / MPxIO / VxVM failover issue

2010-10-06 Thread Venkata Sreenivasa Rao Nagineni
Hi Sebastien, In the first mail you mentioned that you are using mpxio to control the XP24K array. Why are you using mpxio here? Thanks, Venkata Sreenivasarao Nagineni, Symantec -Original Message- From: veritas-vx-boun...@mailman.eng.auburn.edu [mailto:veritas-vx-

Re: [Veritas-vx] Solaris-SFS / MPxIO / VxVM failover issue

2010-10-06 Thread Ashish Yajnik
MPxIO with VxVM is only supported with Sun storage. If you run into problems with MPxIO and SF on XP24K then support will not be able to help you. I would recommend using DMP with XP24K. Ashish -- Sent using BlackBerry - Original Message - From:

Re: [Veritas-vx] Solaris-SFS / MPxIO / VxVM failover issue

2010-10-06 Thread Victor Engle
This is absolutely false! MPxIO is an excellent multipathing solution and is supported by all major storage vendors including HP. This issue discussed in this thread has to do with improper behavior of DMP when multipathing is managed by a native layer like MPxIO. Storage and OS vendors have no

Re: [Veritas-vx] Solaris-SFS / MPxIO / VxVM failover issue

2010-10-06 Thread Christian Gerbrandt
We support several 3rd party multipathing solutions, like MPxIO or EMCs PowerPath. However, MPxIO is only supported on Sun branded Storages. DMP has also been known to outperform other solutions in certain configurations. When a 3rd party multipathing is in use, DMP will fail back into TPD mode