Adrian

Network cost is not the only issue.  Latency can kill you.  However if
that is not a problem disk is a viable second site option.  Dont forget
that copypools are sequential, so even on disk you will have wasted
space, reclamation and perhaps mountpoint issues.

One possibility for quick recovery would be to mirror the TSM config
files,. db and log to the second site using either disk array facilities
or OS level volume mirroring.  Don't forget to plan for extended
operation at the second site -  it may take some time to get your prime
site back up and running.  Also plan for transition back to prime site
once normal operations resume.  Too many sites do a quick restore of the
TSM server in a DR test and a couple of apps and get self-satisfied.  In
a real emergency they'd be trying to back up the high priority app that
they restored yesterday and is now in use while still trying to restore
the lower priority app that the users are screaming for today.

Hope this helps

Steve

Steven Harris
TSM Admin, "Resting" in Sydney, Australia

Remco Post wrote:

On 29 jul 2009, at 17:02, Davis, Adrian wrote:

This seems like a (relatively) simple solution. However, as I have not
seen this documented in any of the manuals, I'm guessing that there
is a
problem with this approach?

There is only one thing you need to think of: how do you access the
disks on the remote site? Other than that this is a very valid design,
and I would certainly recommend it. My guess is that it is so simple
and straightforward that nobody ever thought of documenting this...

Does anybody have any comments -or- better ideas for a Tivoli disk
only
backup with data duplicated at two sites?

I would look at tape as well for the second site. Disk makes sense if
you have spare hardware at your remote site for a large number of your
servers. Tape is fast, cheap and green...

--

Met vriendelijke groeten/Kind regards,

Remco Post
------------------------------------------------------------------------


No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.392 / Virus Database: 270.13.35/2269 - Release Date: 07/28/09 
17:58:00