Hadrian,

The May 2006 issue of storage magazine had an article on just that topic 
BUT i don't think it answers you're question directly.

From: 
http://storagemagazine.techtarget.com/magLogin/1,291245,sid35_gci1188735,00.html
===
The DR plan specifies only system RTOs, not data center RTOs.

Most companies that have negotiated RTOs have negotiated these numbers for 
individual systems. For example, a common RTO is that any system in the 
data center must be recovered within four hours. While this works fine for 
operational recoveries and system-level outages, it doesn't work when the 
entire data center is lost. It's usually assumed that a system that needs 
to be recovered is given access to all system resources. For example, a 
large database server that needs to be recovered is given access to all 20 
tape drives in the tape library. But what happens when 20 or 100 servers 
need to be recovered? They can't all be given access to all 20 tape drives 
in the tape library.

This is quite possibly the most difficult conversation that needs to occur 
between IT and those business units that need a DR plan. It brings to 
light one of the core problems with traditional backup and recovery: In a 
true disaster, it's fairly certain that the storage department isn't going 
to meet its RTOs or RPOs. Unless your company is able to live without its 
data for several days, the only way to have an entire data center's data 
available after a disaster is if it was "recovered" before the disaster 
happened. Traditionally, this has been accomplished with replication. 
Depending on the amount of data, it can also be accomplished with other 
technologies. But realistically, the working RPOs and RTOs of most 
companies don't allow the recovery of an entire data center to begin after 
a disaster. 
===

It's a good magazine and the subscription is free,


veritas-bu-bounces at mailman.eng.auburn.edu wrote on 08/14/2006 01:28:09 PM:

> I have the task of documenting RTO and RPO across our Enterprise and
> had some questions. 
> I feel like asking Departments how soon do you need restores will 
> yield? arguments and confusion. 
> Do most people present a few different solutions and cost and say pick 
one? 
> I somehow feel like the need to get data on "How much money do we 
> loose every minute of downtime" is going a bit high level, but 
> NECESSARY for establishing the RTO / RPOs in a realistic manner.
> What do you guys/gals think?  Any help for a burgeoning SAN / Backup
> engineer would be helpful :) 
> Hadrian Baron 
> Network Engineer 
> VEGAS.com 
> Office: 702-992-4853 
> Cell:    702-553-5699 _______________________________________________
> Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20060814/92175630/attachment.html