Suggest you have a mirror disk and alternative boot disk for best resilience.
Check out
You will need another disk preferably on a different controller as large, or larger than your existing root disk paritions.
If disk has been added in-flight without rebooting.
'devfsadm -c disks'
'vxdctl enable'
'vxdisk list' - should show new disk
'/etc/vx/bin/vxdisksetup -i cNtNdN' - init new disk
'vxdg -g rootdg adddisk altboot=cNtNdN' - add to rootdg
'vxedit set nconfigall nlog=all rootdg' - keep VxVM config on all rootdg disks
'/etc/vx/bin/vxrootmir altboot' - mirror root partition
'vxassist -g rootg mirror swapvol altboot' - add swap
.. add any other (/opt, /var) from your root disk as above
'/etc/vx/bin/vxbootsetup altboot' - make it bootable
using eeprom command add altboot devalias to nvramrc and set use-nvramrc? to true
'vxprint | grep altboot' - note subdisk and plex names
'vxplex -o rm dis rootvol-0? swapvol-0?' - remove plexes
'vxedit set reserve=on altboot' - prevent VxVM from using
fsck all the partitions since they will be dirty
mount -Fufs /devv/dsk/cNtNdNs0 /mnt
create a file in /mnt indicating when copy was taken
edit /mnt/vfstab with new device names cNtNdNs0,1..
edit /mnt/etc/system, delete rootdev references to prevent VxvM trying to start on contingency disk boot
Test boot on contingency disk 'ok> boot altboot' check root is mounted as a standard not a VxVm device.
Have a look at using the Veritas persistent Data Change Object combined with snapshotting to enable a really quick resynchronisation.
JB