ARGH!
My database is 30 GB. And I format it as 3 10 GB volumes. Our hot-site
config has three fiber HBAs into the disk, with SDD used for virtual
pathing; the format/format/db restore takes about 45 minutes.
They didn't, by chance, have the tape drives fiber-attached via the same
HBAs as the disk, did they? Our current hot-site contract specs six LTO1
fiber attach via two additional fiber HBAs.
If they didn't have the tape and disk on the same HBAs I would suspect a
funky microcode issue.
FWIW, our hot-site contract is expiring this year and we are in the
process of re-bidding it; I'm being very carefull to spec the disk
subsystem, the tape subsystem, and the individual host system fiber
requirements properly -- this is an easy area to get burned in.
(I'll let someone else address the NFS mounting for the mirror -- but
the thought of doing that over a significant distance scares the heck
out of me).
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 12:49 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Constant Hot TSM Server
Actually the problem was the server that we received from our Hot Site
provider.
The server is an AIX 5.1 server with TSM version 5.2.1 installed.
The problem was that the fibre attached disk that they gave us were
extreemely slow. I have a 48 GB database and formatting the database so
I could restore to it took 9 hours in itself, TSM was available in 12
hours. In a 24 hour DR Test this is not good....
As for the constant hot serer I was thinking of just NFS mounting the
seondary server and TSM Mirroring the database to that server. Would
that work?
Thanks again,
Andrew
-----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 11:14 AM
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 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.
********************************************
|
