Seems like overkill to me.

But yes, in the event of a disaster you ARE down to just one copy. If
your data volume is not huge and you can afford it, keep a second copy
pool.

Or, you could institute a policy of making portable backupsets of all
the critical nodes every month.  Then you'd have a month-old snapshot as
well as an up-to-date copy pool.  If you DID lose a tape, you wouldn't
lose everything then - you could still get most of it from your
month-old snapshot.

Not perfect, I now - but this is a useful trick anyway, because you'll
run into tape contention problems when you do a full restore of many
nodes at the same time (ie, unless you collocate your copy pool, two
nodes will be on the same tape, and the 2nd node will have to wait for
the first node to finish before grabbing tape.).  With portable
backupsets, you can restore them all in parallel, to the last snapshot -
then the TSM server just brings them all up to date.  Much less data
sent, less opportunity for contention.

So if you think that's a good idead for the tape-contention reason,
maybe you can also sell it as a sort of backup to the copypool, too.


Dale Gieseke wrote:
>
> SpamCop - Report spam:
> http://members.spamcop.net/sc?action=report&id=1059138
>
> We copy all our backup and archive data to copy storage pools each morning =
> and send these tapes offsite for disaster recovery purposes.=20
>
> It has been suggested that we should have two copies of all data offsite. =
> The thinking is that in the event of a true disaster, one of the copies =
> would be sent to the recovery site and the second copy be retained at the =
> offsite storage facility just in case the first copy is lost or destroyed =
> during shipping. Or is not readable at the hotsite.
> =20
> Do other ADSM shops keep more than one copy of data offsite for disaster =
> recovery purposes?    Any thoughts would be appreciated!
> =20
> Thanks,
> Dale

--
Mr. Lindsay Morris
Mr. Lindsay Morris
Gresham Enterprise Storage
lmorris AT openmic DOT com
606-253-8000