Any suggestion ?
Maybe Veritas/Symantec employees has any suggestion ?
Is it some bug ?
Regards
przemol
On Tue, Feb 19, 2008 at 12:21:51PM +0100, [EMAIL PROTECTED] wrote:
> Hi all,
>
> We are using Solaris 10 + 5.0MP1. While trying to dump to tape
> I have:
>
> bash-3.00# mt -f /dev/rmt/2 statu
Hi,
On an A/A array with iopolicy set as single-active, if a path failure
happens to the target should I observe a fail over or not?
--
Regards,
Chinmayee
___
Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman
On Wed, Feb 20, 2008 at 08:09:26AM +, Neil Swallow wrote:
> Having lost an encapsulated root disk (called rootdisk) running vxvm 3.5 on
> solaris 2.6, and kept the server running on the mirror (normal vx
> initialized disk) I can't now use vxdiskadm to replace the disk. When I go
> to replace
Have some notes on that:
Rollback to rootdisk
After a upgrade goes bad, shutown & poweroff server:
Shutdown -y -i5 -g0
When off pull rootdisk and push rootmirror back in.
Boot
##
I edited this:
http://sysunconfig.net/unixtips/jmr_Mirroring_Boot_Disks_Veritas_Volume_
Manager.htm
To fit ou
Neil Swallow wrote:
> Hello,
>
> Having lost an encapsulated root disk (called rootdisk) running vxvm 3.5 on
> solaris 2.6, and kept the server running on the mirror (normal vx
> initialized disk) I can't now use vxdiskadm to replace the disk. When I go
> to replace it, it insists that the public
Hello,
Having lost an encapsulated root disk (called rootdisk) running vxvm 3.5 on
solaris 2.6, and kept the server running on the mirror (normal vx
initialized disk) I can't now use vxdiskadm to replace the disk. When I go
to replace it, it insists that the public region is too small. Looking
