ADSM-L

Re: Offsite Mirror of TSM server

2002-04-17 18:44:26
Subject: Re: Offsite Mirror of TSM server
From: StorageGroupAdmin StorageGroupAdmin <StorageGroupAdmin AT SYDNEYWATER.COM DOT AU>
Date: Thu, 18 Apr 2002 08:43:50 +1000
If I was setting this up......

I would use the remote mirroring of the disk (both MVS and Open
systems) using the available disk technologies (ie SRDF for EMC).

Base upon the fact that TSM does appear to recover 99% of the time even
if the server is not shutdown cleanly I  also assume the remote mirrored
disk should be sufficient to get back up and running in the event of a
DR at your primary site. (I am not saying no longer do dBASE backups
though. What I am say suggesting is the normal dBASE backups is your
second or even third point of call for recovery.  If you are using the
remote mirroring feature you would also probably have  the  timefinder
or flashcopy feature. These functions could also be considered to
enhance your recovery procedures)

Since in the event of a DR you need to have the infrastructure not only
to recover but to run normal operations whilst the primary site is put
back together I assume you would have a 3494 at the secondary site as
well. This would therefore allow you to write you primary tape pool
locally and the copy pool remotely. Telling TSM to recovery the STG
pools from the backups is a simple matter.

For the mainframe kit you would then also be able to automatically
write you volume dumps (including the TSM volumes) to remote tape via
ESCON extended over a  DWDM.  I personally believe TSM being a backup /
recovery system  should be able to support a shutdown if not daily then
once per week to also ensure the dump or disk copy is a clean copy. By
keeping multiple GDS copies of the volume dumps,  the TSM dBASE backup,
being the slowest of the recovery option, drops even further down the
recovery option queue.


Peter Griffin

>>> zforray AT VCU DOT EDU 04/18/02 03:46am >>>
Let me preface this with, I am not sure how to completely ask these
questions since I don't have all of the details but hopefully someone
can
give me some idea of how TSM can/will handle this, if at all possible.

Current configuration:  TSM 4.1 on OS/390 using 3590B tape drives in a
3494 ATL

Requirements as I understand them:  Setup a off-location "hot site"
backup
TSM server that will have copies of everything the main server and/or
other TSM server (we are working on splitting the TSM traffic/load
onto
another TSM server) has.   The "hot site" server will probably be an
AIX
box with 3590E (possibly FC) drives.

I have looked into the source/target server issue but am a little
confused
since the "target" server will only see things that come from the
"source"
server as archive objects.

If the building with the "source" server burns down (and this same
building also houses a majority of the clients that are backed up !),
how
would the "target" server be used to restore all of the client nodes ?

How about the database backups that are sent to the "target" server ?
What
use are they if you have to have the "source" server to identify what
is
on the "target" server ?

Should I/could I setup database mirror volumes on a remote (target ?)
server over simple IP connections or is this only possible with DASD
using
XRC processes....especially since the current, main database is on
OS390 ?
    If this was moved to an AIX box, how would this be handled ?  NFS
???

As you can tell, any and all guidance is greatly appreciated !!!
----------------------------------------------------------------------------------------------------
Zoltan Forray
Zoltan Forray
Virginia Commonwealth University - University Computing Center
e-mail: zforray AT vcu DOT edu  -  voice: 804-828-4807


-----------------------------------------------------------
This message has been scanned by MailSweeper.
This message has been scanned by MailSweeper.
-----------------------------------------------------------
-----------------------------------------------------------
-----------------------------------------------------------
This e-mail is solely for the use of the intended recipient
This e-mail is solely for the use of the intended recipient
and may contain information which is confidential or
privileged. Unauthorised use of its contents is prohibited.
If you have received this e-mail in error, please notify
the sender immediately via e-mail and then delete the
original e-mail.
-----------------------------------------------------------
=========================================================================
<Prev in Thread] Current Thread [Next in Thread>