ADSM-L

Re: Constant Hot TSM Server

2005-05-17 09:39:54
Subject: Re: Constant Hot TSM Server
From: RAMNAWAZ NAVEEN <NAVEEN.NR AT SBM.INTNET DOT MU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 17 May 2005 09:37:07 +0400
Hello Andrew,

I have got an AIX server with aix 5.1 at my DR site. My TSM DB size is 10 GB. 
What i do, is as foolows and it meets my requirements more than enough:

1.0     After all my batch processes are over, a full tsm db abckup is 
extracted, compressed and then  ftp'ed to my DR site. This occurs at around 
07:00 and the whole process is automated and runs in cron.

2.0     At the remote site, once the tsm db is there, a script runs and 
replicates my TSM environment such that I have the same TSM environment at my 
DR site ready at latest by 08:30 a.m daily. 

3.0     If I want a hot-standy tsm environment as my production environment , I 
can just add more entries in my crontab so that the job is executed say at 
every 06:00 hr intervals, if need be. 

You might investigate to implement a similar setup, and if need be, I may send 
you my script. Just let me have your e-mail address. 

However, you will have to investigate and address your 9 hours bottleneck 
arising at the formatting stage.

Regards


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Kauffman, Tom
Sent: Monday, May 16, 2005 8:14 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Constant Hot TSM Server


Andrew --

Was the problem in recovering the TSM server, or recovering the
applications after the server recovery? What platform/version?

I've been recovering TSM (AIX) in about 4 to 6 hours for several years
now, and recovering SAP/R3 (Oracle) and MS-Exchange to most recent
available backups in 8 to 12 hours additional (R3 is now 1.2 TB).

As for the constant hot server -- 
1) Server itself
2) Library of sufficient size
3) Leased communication line large enough to handle the data traffic
        (This one will be the killer, depending on what you back up)
4) Increased administration costs

It would probably be much less expensive to work out corrections for
what failed.

Tom Kauffman
NIBCO, Inc

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Meadows, Andrew
Sent: Monday, May 16, 2005 9:12 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Constant Hot TSM Server

Hello everyone,
Ok we just returned from our DR Test and unfortunately it was a flop. No
big deal I learned something. 

Management now wants to know the cost involved at having TSM up
constantly at a hotsite. For some reason I cannot wrap my mind around
exactly what would be the best way to do this. Does anyone out there
currently do this and if so how?

Thanks in advance,
Andrew
********************************************
This message is intended only for the use of the Addressee and
may contain information that is PRIVILEGED and CONFIDENTIAL.

If you are not the intended recipient, you are hereby notified
that any dissemination of this communication is strictly prohibited.

If you have received this communication in error, please erase
all copies of the message and its attachments and notify us
immediately.

Thank you.
********************************************


This mail has originated from the Internet. The State Bank of Mauritius 
disclaims all liability as regards to its content.



Please verify its source and content before acting thereon.


The information contained in this e-mail message, and any attachment thereto, 
is confidential and may not be disclosed without our express permission. If you 
are not the intended recipient or an employee or agent responsible for 
delivering this message to the intended recipient, you are hereby notified that 
you have received this message in error and that any review, dissemination, 
distribution or copying of this message, or any attachment thereto, in whole or 
in part, is strictly prohibited. If you have received this message in error, 
please immediately notify us by telephone, fax or e-mail and delete the message 
and all of its attachments. Thank you.

Every effort is made to keep our network free from viruses. You should, 
however, review this e-mail message, as well as any attachment thereto, for 
viruses. We take no responsibility and have no liability for any computer virus 
which may be transferred via this e-mail message.


<Prev in Thread] Current Thread [Next in Thread>