Hot/Cold is problematic with NNMi since as soon as you restore your last backup your system will have a stale topology and will need to poll to bring it up to current conditions so you'll need to factor a full discovery time period that into your recovery timeline.
A straight backup and restore to another system will require some manual steps unless your DR site will duplicate the same IP addresses and hostnames as your production. The licenses are bound to the host IP addresses. Applying a restored DB to a system isnt an incremental update, its a complete overwrite and as such you'll need to keep several iterations around because you'll never know when a DB backup includes corruption so you'll want multiple copies as well as schedule regular times to test restoration so that you know your copies are good.
Have a nice day :)
Andy Kemp I've lasted longer in the technology industry than most certifications.
both cases need a licence, but my impression is that app-failover is a cheaper one that two NNM9 servers running completely independent of one another. the logic is that in app-failover, only one of them is really fully functional at any given time.
for the specifics, contact a sales rep or account rep, they should be able to quote you about the relative prices.
If we are using NNMi application failover feature then
1)If NNMi primary server is in DC and NNMi secondary server is in DR, what is the list of ports that needs to be opened between DC and DR NNMi for communication(any document will be helpful for this)
2)In DC we have integrated NNMi with OMW for events and uCMDB for CIs, then in case NNMi primary fails, will secondary NNMi report to OMW and uCMDB in same way.
3)as mentioned NNMi and OMW are integrated, if OMW primary fails and NNMi primary also fails, then where will NNMi secondary forward events, can events be forwared to secondary OMW, how to achieve this as we have insatlled OM agent separately on NNMi DR server. Please provide your thought on this.