Can we assume that the W2008 servers will be new hardware?

Best to setup a brand new cluster.

Zone storage to new systems, install application as per requirements in documentation (depending on application, you may need small 'dummy' volume(s) for initial installation) configure new Service Groups, using same virtual hostname(s) and IP(s) as original cluster. Refer to original main.cf for parameters.

You should now be able to deport dummy diskgroup (rename dg during deport) and offline Service Group on old cluster. 
Rescan SF for new devices. If visible on both nodes, online SG in new cluster.

Hi Marianne

yes Target system would be new Hardware

Few queries for new cluster setup

Should we deploy 5.1 first on new H/W on top of Windows 2008 R2

Hostname would be changed so any impact on migration? What precautions are to be taken?

I would go straight to 6.0.1. 
Please read agent guide for your application to verify requirements and possible changes to agent.
Double-check HCL as well as SCL.

New hostnames should not be a problem as long as application access is using the virtual hostname.

Hopefully Mike and Wally will be along soon with their thoughts!

See similar discussion here: https://www-secure.symantec.com/connect/forums/how-migrate-running-cluster-existing-two-node

Thanks marianne for this valuable info. Just simulating in lab to have confidence.

One thing missed was Domain Rename. Old cluster would be on abc.xyz.com and New cluster would be in agroup.com

What pre-cautions do we need to take for this

Your only concern with Domain rename will be application access using virtual name.

If FQDN is used for access, all remote systems will need to be updated.

AD helper will be configured during initial setup. DNS update during SG config.

You have the correct approach - simulate in lab first.

Application is Enterprise Vault 9.0.2

I have no experience with clustered EV. 

Does EV software include VCS agent? and documentation?

Have you confirmed that EV will support a Domain change? 

The VCS changes are easy - you need to find out if your proposed environment (especially domain change) is supported by EV.
 

EV does include an agent and documenation for VCS support on the EV media.  I'm not familar enough with EV to say if it supports a domain name change.  I would recommend posting that question to the EV forum to see what they say.

Hi Wally

As far i've tested in lab it did worked not sure if there are official statements on this. However it has been requirement coming up due to same corporate spilt and merger fact. So IT team has to look in to this too ;-). MS allows domain rename using their native tool and for EV after all it's SQL at back end 

There is actually a bit more to EV than just SQL....

See this White Paper about moving EV to a new domain: http://www.symantec.com/docs/HOWTO77280

Have we managed to answer your cluster upgrade/migration questions?