[Veritas-vx] DR test with VxVM

[robertinoau]

>My question is, when I reboot on this new system disk
>what is my next step to re-enable a new, clean VM
>installation ? This is where I get stuck because I'm
>unclear what gets picked up from the old system.



Nothing will get picked up from the old system as your
new disk doesn't have a valid VM configuration
database (tag 15).  


>I assume I first run vxlicinst -k xxxx to insert a
>temporary key. 


Nope.  Just run vxinstall and enter your license key
and encapsulate.  


>an I just re-run vxinstall and re-configure  or will
>there be "legacy" files in the way ? Should I use
some
>combination of vxconfigd/vxdctl disable/enable and
>then vxedit to remove old volume details, or is this
>now irrelevant ?


Irrelevant as I explained above, you don't have a
valid configuration database so you will not any
volumes to begin with.  You will have to re-create
then all from scratch 





 --- Andrew Garnett <andrewwdg at yahoo.co.uk> wrote: 
> Thanks all for the useful feedback.
> Still running VM3.5 on Solaris 8 with an
> encapsulated
> and mirrored root.
> 
> I have to do a DR test by restoring all my backup
> tapes (ufsdump under Solaris 8) to a completely
> different server model, different disk sizes,
> numbers
> and layouts. I have an evaluation license key for
> VxVM. The DR company will provide me with a big
> enough
> server with one disk pre-installed with Solaris to
> save time over the CD install.
> My intention is to restore a clean system disk,
> reinitialise any other disks for data then build
> volumes and filesystems manually and restore to
> them.
> The new volumes will not have the same topology as
> the
> old ones. 
> 
> I will do this by the usual boot, format the second
> system disk & ufsrestore root & var to it, then
> mount
> it & edit all the relevant system files (devices
> etc).
> Here's the VM bit....
> I'll create an install-db, remove file from state.d
> ,comment out 2 lines in /etc/system and change
> vfstab,
> then install a boot block. I think this is all
> normal
> (correct me if I'm wrong). 
> 
> My question is, when I reboot on this new system
> disk
> what is my next step to re-enable a new, clean VM
> installation ? This is where I get stuck because I'm
> unclear what gets picked up from the old system.
> I assume I first run vxlicinst -k xxxx to insert a
> temporary key. 
> Can I just re-run vxinstall and re-configure  or
> will
> there be "legacy" files in the way ? Should I use
> some
> combination of vxconfigd/vxdctl disable/enable and
> then vxedit to remove old volume details, or is this
> now irrelevant ?
> 
> Thanks,
> A
> 
> 
> 	
> 	
> 		
>
___________________________________________________________ALL-NEW
> Yahoo! Messenger - all new features - even more fun!
>  http://uk.messenger.yahoo.com
> _______________________________________________
> Veritas-vx maillist  - 
> Veritas-vx at mailman.eng.auburn.edu
>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>  

Find local movie times and trailers on Yahoo! Movies.
http://au.movies.yahoo.com