ADSM-L

Re: [ADSM-L] Tivoli "disk only" backup with data duplicated at two locations?

2009-07-29 14:56:58
Subject: Re: [ADSM-L] Tivoli "disk only" backup with data duplicated at two locations?
From: Shawn Drew <shawn.drew AT AMERICAS.BNPPARIBAS DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 29 Jul 2009 14:56:08 -0400
We used to do it this way, using the file device class and FCIP.  The 
problem was that we grew up to a point where managing all those file 
systems has a hassle.   In our DR test, we had to 
dismount/rezone/mask/mount more than 100 file systems to the DR host. 

Other than that, it was fine.  We eventually moved to a VTL.  We chose one 
that let's you use your existing storage, as opposed to buying disk from 
the VTL vendor.

With the VTL, we simply restore the DB at the new location, start up, 
update the IP for the server in everyone's "def server" assignment, and 
ready to go.


Regards, 
Shawn
________________________________________________
Shawn Drew





Internet
Adrian.Davis AT LEWISHAM.GOV DOT UK

Sent by: ADSM-L AT VM.MARIST DOT EDU
07/29/2009 11:02 AM
Please respond to
ADSM-L AT VM.MARIST DOT EDU


To
ADSM-L
cc

Subject
[ADSM-L] Tivoli "disk only" backup with data duplicated at two locations?






We are looking at a number of possibilities for a new backup system?

 

Until now we have a used a "traditional" tape based backup strategy -
but with falling disk and network bandwidth prices - we are looking at
the possibility of using a disk only backup solution.

 

One option is to use Tivoli.

 

We need to be able to have two copies of all data each copy at a
different physical location.

 

One idea that comes to mind is to backup to a disk storage pool, then
"BACKUP STGPOOL" this storage pool to another (copy) disk storage pool -
The second disk pool being a volume on a separate disk array at a remote
location.

 

We would also "BACKUP DB" the TSM database to the remote location.

 

In the event of the loss of the primary site - I'm thinking we could
"build" a TSM server, using the database backup up to the remote site,
mount the "remote" copy disk storage pool volume on the new server and
(as at that time the primary storage pool is "unavailable") access the
data on the disk copy storage pool directly in order to perform our DR
restores.

 

This seems like a (relatively) simple solution. However, as I have not
seen this documented in any of the manuals, I'm guessing that there is a
problem with this approach?

 

Does anybody have any comments -or- better ideas for a Tivoli disk only
backup with data duplicated at two sites?

 

Many Thanks,

   =Adrian=

DISCLAIMER

This message is confidential and intended solely for the use of the
individual or entity it is addressed to. If you have received it in
error, please contact the sender and delete the e-mail. Please note 
that we may monitor and check emails to safeguard the Council network
from viruses, hoax messages or other abuse of the Council’s systems.
To see the full version of this disclaimer please visit the following 
address: http://www.lewisham.gov.uk/AboutThisSite/EmailDisclaimer.htm

For advice and assistance about online security and protection from
internet threats visit the "Get Safe Online" website at
http://www.getsafeonline.org





This message and any attachments (the "message") is intended solely for 
the addressees and is confidential. If you receive this message in error, 
please delete it and immediately notify the sender. Any use not in accord 
with its purpose, any dissemination or disclosure, either whole or partial, 
is prohibited except formal approval. The internet can not guarantee the 
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) 
not therefore be liable for the message if modified. Please note that certain 
functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.