This is what we do right now. Is there a way to mirror tsm_serverA to
tsm_serverB so that if tsm_serverA blows up, we can point to tsm_serverB
for the restore of our client nodes? Is this where the export/import
commands come into play?

> From: Jeff Bach [mailto:jdbach AT wal-mart DOT com]
> Sent: Thursday, September 27, 2001 09:45
> To: 'payne AT berbee DOT com'
> Subject: RE: TWO TSM SERVERS
>
>
> If you need to DR the first ADSM server before restoring, why has a second
> server?
>
> Extend a SAN network to a  second site, set it up to use a separate devices
> class.  Create a regular copy storage pool that uses this device class and
> copy the data.  The data is a two sites.  Make sure to backup the data to
> that device class and keep track of the needed files for a DR.
> Jeff Bach
> Home Office Open Systems Engineering
> Wal-Mart Stores, Inc.
>
> WAL-MART CONFIDENTIAL
>
>
>         -----Original Message-----
>         From:   Kyle Payne [SMTP:payne AT BERBEE DOT COM]
>         Sent:   Thursday, September 27, 2001 6:19 AM
>         To:     ADSM-L AT VM.MARIST DOT EDU
>         Subject:        Re: TWO TSM SERVERS
>
>         There are a few different ways to do this.
>
>         1)  If you have Site A and Site B then with the right high speed
> connection
>         you could backup the servers from Site A directory to 1 TSM server
> at Site
>         B.  Of course this may not be feasible if you have more data to
> backup in a
>         night then your window and the connection will allow.
>
>         2)  If you truly want a copy at both sites then I would use a copy
> pool but
>         by using virtual volumes.  Your copy pool would use a server device
> class
>         that is pointing to the other site's TSM server.  Then when you run
> your
>         storage pool backups they are put on the other TSM server.  Note
> that when
>         you do this, in a disaster you will need to DR the Site A (or first)
> server
>         at Site B.  This is because the server that stores the data only
> recognizes
>         it as archived objects through virtual volumes and not as real node
> date.
>         It is the DB from Server A that will distinguish this.
>
>         Sure you could try something with exports and imports but you are
> right that
>         doesn't make much sense.  In reality the key to the Site A and Site
> B
>         working is the connection you have between them.
>
>         Kyle Payne
>         payne AT berbee DOT com
>
>         -----Original Message-----
>         From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On 
> Behalf
> Of
>         Eduardo Martinez
>         Sent: Wednesday, September 26, 2001 19:56
>         To: ADSM-L AT VM.MARIST DOT EDU
>         Subject: TWO TSM SERVERS
>
>
>         I have two TSM Servers.
>         Each one of them has a library attached.
>         They are on two different locations (lets say A and B)
>
>         I want to backup all my clients in server A, but I also want to keep
> a
>         copy of those files on server B.
>         This is intended for redundancy purposes, and it is also intended to
>         avoid a courier carrying tapes among locations.
>         Is it possible to do this?
>         I've never worked with Virtual Volumes, and I dont know if they are
> the
>         solution for this schema.
>         I've also read about EXPORT and IMPORT data (also using Virtual
>         Volumes), but I think by doing this could be a very heavy process on
> a
>         daily basis, since Im going to export ALL data already backed up and
>         not only the changes.
>         I dont want to use Copy Storage Pools since I have to recreate first
>         all the tapes that could be destroyed and then restore.
>         Any ideas?
>
>         Thanks in advance.
>
>
>
>         =====
>         "Do or Do Not, there is no try"
>         -Yoda. The Empire Strikes Back
>
>         _______________________________________________________________
>         Do You Yahoo!?
>         Yahoo! Messenger: Comunicacisn instantanea gratis con tu gente -
>         http://messenger.yahoo.es
>
>
> **********************************************************************
> This email and any files transmitted with it are confidential
> and intended solely for the individual or entity to
> whom they are addressed.  If you have received this email
> in error destroy it immediately.
> **********************************************************************
>