ADSM-L

Re: [ADSM-L] Why virtual volumes?

2007-08-23 10:56:02
Subject: Re: [ADSM-L] Why virtual volumes?
From: Richard Rhodes <rrhodes AT FIRSTENERGYCORP DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 23 Aug 2007 10:57:49 -0400
> Richard,
> I'm sorry I haven't made our situation clearer.  In the current phase
> of the project we are building a TSM server in Bloomington to backup
> local clients to disk which will be migrated to virtual volumes in
> Indianapolis. After migrating local clients to the new server, we
> plan to build a TSM server in Indianapolis which will backup nodes
> there to disk, which will be migrated to virtual volumes in
> Bloomington. Each data center will be the offsite backup and DR site
> of the other. But, now that we have virtual volumes working, I am
> looking at it and thinking 'yish!'.
>
> With best wishes,
> Keith

Hi Keith, thanks for more details.

Let me see if I fully understand . . . .

Bloomington
  TSM-a
    local clients backup to disk pool
    disk pool migrates to TSM-b/VV at Indianapolis
      ==> primary tape pool is on TSM-b/VV at Indianapolis
    vv server - contains primary pool from TSM-b

Indianapolis
  TSM-b
    local clients backup to disk pool
    disk pool migrates to TSM-a/VV at Bloomington
      ==> primary tape pool is on TSM-a/VV at Bloomington
    vv server - contains promary pool from TSM-a

Summary:
  - All clients backup to local TSM server to disk pool.
  - Disk pool gets MIGRATED to VV primary pool at other site.
  - There is NO copy pool at either site.


Is this correct?

Rick


-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.