Any DR procedure begins with the reinstallation or porting of the O/S and this procedure begins and ends with ignite. Some people make an O/S image when the O/S changes, other do it every Friday night via a cron script. Here is a URL:
http://www.software.hp.com/products/IUX/Bear in mind the clone ignite procedure since you'll have to consider porting to another server. For this to successfully port, you have to have a DR server of the same HW class. You can't get around this. And with the emergence of Itanium CPU's, this becomes an even bigger consideration.
Successful backups of your data should be obvious. BCV's via EMC Timefinder or Business Copy Volumes via HP's XP disk arrays and SAN's should also be reviewed. However, people have been exporting their daily oracle changes and ftp'ing up to there DR site for years. It???s all about recovery time. BCV's are more seamless while ftp'ing probably takes a few hours to restore. This is what a High Availability environment is all about and Service Guard. With Service Guard continental cluster its possible to failover to a DR site 100 miles or more away. See Dark Fibre, a very expensive WAN implementation.
Support Fatherhood - Stop Family Law
