I'm thinking you're going to need to add tape drives before thinking of
doing something like this.  You are going to shorten your current daily
maintenance window because you have to squeeze in a portion of it to do a
second run.  Could be done if you can shorten your current window enough,
but I would think that would mean adding tape drives.  Getting your
reclaims done is going to be a problem as well with only single threaded
reclamation processes - if you currently run until 8pm sometimes and you
are going to need to shorten that - will be tough unless you break your
data up into more pools.

Sounds awfully ugly to me.  I think the correct answer is yes it is
technically possible, but do we REALLY need to do it this way.


______________________________
John Monahan
Senior Consultant Enterprise Solutions
Computech Resources, Inc.
Office: 952-833-0930 ext 109
Cell: 952-221-6938
http://www.computechresources.com




             "Kauffman, Tom"
             <KauffmanT@NIBCO.
             COM>                                                       To
             Sent by: "ADSM:           ADSM-L AT VM.MARIST DOT EDU
             Dist Stor                                                  cc
             Manager"
             <[email protected]                                     Subject
             .EDU>                     Running tapes off-site multiple
                                       times in a day?

             01/05/2006 08:54
             AM


             Please respond to
             "ADSM: Dist Stor
                 Manager"
             <[email protected]
                   .EDU>






Like I said -- the questions are crawling out of the wood-work.

Our management wants to reduce the possible data loss in the event of a
disaster by taking copies off-site both in the early morning and again
at the end of first shift.

Is anyone else doing this? Will this be as painfull as I expect it to
be?

I know I'll have issues with reclaims -- I currently run expire
inventory at noon, with reclaims kicking in shortly thereafter and
sometimes running to 8:00 PM, so I'll have to implement a reclaim
window.

Electronic off-siting isn't an option -- I've seen us cut 400 MB Oracle
redo logs for our SAP/R3 database at the rate of one every 2.5 minutes
for extended time periods (and this is explicitly the data that has to
go off-site). I'd need multiple T1 lines to cover the traffic, and the
cost of a single T1 is considered to be "too high".

I'm currently running TSM 5.1.6.3, planning on upgrading to 5.3.current
in the next two weeks.

TIA

Tom Kauffman
NIBCO Inc