What we have setup (across three DCs) is that all the local nodes backup
to their local TSM server.
Then each TSM server is backed up by another across the WAN.

So, all theTSM Server sysback, and files are backed up remotely (such as
volhist, devconfig, etc.) but all the other clients backup locally.

This is a lot less bandwidth consuming than backing up all your clients
across a wan link.
If you're sending Tapes offsite anyway this is the most efficient
method.

See Ya'
Howard

> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Rolf van der Zwart
> Sent: Thursday, December 11, 2008 4:11 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] Setting up crossbackup datacenters with TSM
> 
> Hello,
> 
> I have to set up cross backup between 2 datacenters. What is the
> best/easiest way to do this?
> 
> As far as I can see I have to setup schedules/policy domains/policy
> sets/
> management classes/backup and archive copy groups for both datacenters
> to
> be able to backup nodes to different tape-robots (device classes) as
> this
> is configured with "Copy destination" in the copy groups.
> 
> Am I correct in this assumption? Anybody antoher idea?
> 
> Windows 2003/TSM server 5.3.
> 
> Rolf.