I would like to sort out a solution to the question of multiple disaster recovery site options for a critical database.
Currently, I am running a database with HADR on a second machine at our primary physical site, with log shipping to a secondary physical site. If possible, I'd like to keep multiple machines running at the primary site in order to keep the convenience and safety of HADR, but I'm not really happy with log shipping as a remote solution. It meets the legal requirements for our business, but it's too easy to lose transactions in the case of a catastrophic primary site failure.
I'm curious about what other dbas with multiple standbys are doing as a solution.
We're running DB2 9.7.4 on Solaris/X86
Thanks in advance
-Andy

In SYNC or NEARSYNC mode you only lose in-flight transactions if the primary site fails, which would happen in any case, so?

Having read your post again, you use HADR locally, not remotely. Then you might consider a distributed storage mirror.