Thanks for the reply buddie!
We didn't go with EVSVR as we didn't want to touch the prod db. However restoring vault store and dir db to an alternate spare SQL server worked together with installing EV (same version) on the same spare sql box. This saved the hassle of waiting for "downtime" to point existing EV to alternate DB and less risk
- amended the restored Dir DB ptn entry table to point to prod partitions(unc path) on the actual ev server
- changed some root path entries to the restored partitions i.e. data expired in 2008 was restored to alternate location and shared out.
- There was a trick to getting the prod EV alias to point to the restore ev server by amending the restored EV hostfile and amending computername alternate in the Directory DB computer entry table.
- Lastly like in a DR scenario run EV Configuration Wizard as new and it will find an existing EV Dir DB and "repair" the entries and start up the Admin and Directory and then set EV into backup mode before bringing up the Storage service.
-Checked that restored SQL DB had the saveset id's and then tested a few restores by doing dumpsaveset and then restored via Archive export wizard.
Brief steps here documented:
https://www.veritas.com/support/en_US/article.100037490
and https://www.veritas.com/support/en_US/article.100023864.html ( had to clear entries in Dir DB and manually amend computer entry table which was not mentioned in first article)
Really good to have this standby box environment ready to go at all times - just need to restore partition data/EV DB's to get it to work.
tldr Followed scenario 2 ( DR EV ) and amending hostfile on spare EV server was the key (as per https://www.veritas.com/support/en_US/article.100037490)
