T1 simply is not enough. Just some math:
1.536 MB/s * 3600 sec/h = 5529.6 MB/h (5.4 GB/h)
5.4 GB/h * 24h/day = 129.6 GB/day
129.6 GB/day * 7 days/week = 907.2 GB/week
Having 90 GB daily change you are very very close to the limit - for real
disaster recovery you will need also TSM DB backup/snapshot at DR site and
you did not pointed how big is DB. And for sure there is no enough
throughput for weekend's SAP DB (even being one and the only).
So you have to reconsider something.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:        Disaster Recovery Site

Hi,

I am currently putting together a plan to make one of our sites a disaster
recovery site.  I have it visualized how I would like to do it, but I
thought I would run it past you more experienced TSM'ers in hopes you
might
catch my flaws or give me some better advise.  Here are the details:

Colorado

NSM Server -- AIX 4.3.3,  TSM 4.1.3
      We will be changing to from a NSM server to a TSM server V5.1 in the
      near future.
LTO 3584
2 Domains:
    DM1 - 46 Servers
    SAP - 19 Servers
Clients run the gamout from V3.7.2.19 to V4.2.1.32
Average 90 gig on weekdays and 1.5 TB on weekends (due to SAP database)


New Jersey Site 1

2 Domains:
    DM1 (this is part of the DM1 in Colorado) - 2 Servers
    LAB - 1 Server and 3 Workstations
Both Domains combined have 20 gig total data
Using Backup Exec with DLT drives attached to servers


New Jersey Site 2

1 Domain:
    DM1 (this is part of the DM1 in Colorado) - 2 Servers
17 gig total data
Using Backup Exec with DLT drives attached to servers


Here is what I would like to do:

   Put a TSM Server  and LTO 3583 in New Jersey Site 1 to backup both New
   Jersey sites.
         We would do this with a T1 that is dedicated to only the backups.
         The TSM server would be a W2K server.
   Use the New Jersey Site 1 as a disaster recovery site for Colorado and
   vise versa.
         I would backup the tapepool in Colorado to a special Copypool
         (i.e. COLOcopypool) in New Jersey
         I would backup the tapepool in New Jersey to a special Copypool
         (i.e. NJcopypool) in Colorado.
         We have two option to get the data back and forth (my LAN WAN
         person is investigating this for me):
            Dedicated line between the two sites
            A T1 (dedicated ot just backups) going through a frame.


Here are my questions:

   Since they will be Disaster Recovery sites for each other, does the TSM
   server need to be the same operating system?
   Would the backup tapepool to copypool be the best way to do this?
   Has anyone else setup a system like this and how did you do it?
   Also has anyone had to provide an ROI for TSM?  I can think of some
   basic things like saving on headcount (but I have been a one person
team
   for years so that wont fly).


Sorry this email is so long.  Any advise would be greatly appreciated.

Lori Cundiff
Backup Engineer