Tony,
You have not said how much data you are restoring, so cannot see how many
gigabyte an hour.
However my experience of restoring large clients form backupsets is that the
speed of the restore is more than anything dependent
on the resources of the client box to which you are restoring.
    ,





"Garrison, Tony" <[EMAIL PROTECTED]> on 07/22/2002 04:55:19 PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:    (bcc: John Naylor/HAV/SSE)
Subject:  Re: General TSM Q's



what kind of problem did you have with the backupset?  we recovered 2 Aix
4.3.3 filespaces with backupsets this weekend.  The filespaces have approx
3.5 million files and was taking about 40hrs per filespace to perform a
normal restore.  the problem is running node collocation, it really
stretched our restore time to an unacceptable length of time.  we were able
to recover both filespaces with backup sets in approx 30 hrs each.  this
includes the time required to perform a replace if newer restore to get any
changes since the backupset was created.  Consequently we restored the
server in less then 40 hrs from start to finish.  Anyone else have
experience running backupsets that might be able to help us cut this time
even more?

T


Tony Garrison
I/T Sr. Systems Programmer
USAA
210-913-9836



-----Original Message-----
From: Cardoza, George [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 16, 2002 11:52 AM
To: [EMAIL PROTECTED]
Subject: Re: General TSM Q's


I'll bite... let me throw in my two cents worth:

1.  A 30GB TSM database is considered large.  We have a 30Gb TSM database
with 250 server nodes containing 70TB of data on an IBM 3584 Tape Library.
We have a 5GB log file and process approximately a TB a day in daily
changes.  This is all under the AIX platform, I think it is technically
possible to do it with NT, but the stability and recovery times may be
larger than the AIX platform.  (Our configuration:  2-way, Silvernode, 2GB
memory, SP Switch, 100TX, TSM V. 4.2.2, Fiber attached library/tape drives.

2.  An undersized library usually means you have a lot of "media waits"
while the tape drives fight for contention and available scratch tapes, or
slots.  This usually shows itself immediately with reclamation, migration,
data moves, etc.  If you can't run your scheduled reclamation and still make
your backup window for your scheduled jobs, then you probably need more tape
drives or a larger library.  Check your policies and retention periods.  As
is true with all TSM installations, your mileage may vary.

3.  We just did a disaster/recovery test at a remote site this past weekend
and here is at what we experienced.  The incremental backups worked fine,
the archive backup worked fine, the backupset did not.  We used the archive
tape and rolled forward to point-in-time restore to our disaster recovery
point.  We used Sysback/6000 to recovery the AIX servers with great
results... I highly recommend it.

4.  We are going to a second TSM server on AIX to start backing up key NT
workstations.  We have 9,000 seats but will probably only backup a small
percentage of IT, Finance, and administrative workstations.  We have an old
DLT tape library which we are redeploying for workstation use.  You might
want to consider the same thing with your old tape library as you consider
your purchase of a new one.

5.  Mixed library media on a TSM server is supported.  It should work just
fine.  We are running DLT and LTO tape libraries on a single AIX server for
the past year.  No problem.

Although TSM Server supports both NT and AIX platforms, and I have worked
with both, I have found AIX to be quicker to recover from and more reliable
of the two.  (No, I am not getting paid money from IBM or Microsoft for my
endorsement.  Just one man's opinion ...)

George Cardoza
Perot Systems
310.423.1670 - Office




-----Original Message-----
From: Miller Dave (RBNA/CIT1) [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 15, 2002 1:51 PM
To: [EMAIL PROTECTED]
Subject: General TSM Q's


Hello All,

We have recently deployed TSM at our site.  Being new to TSM, I have a few
questions I was hoping someone may be able to help with.

I am running TSM 4.2.1.9 with a Compaq ESL9198DLX on W2K

1) Our TSM database has grown surprisingly fast.  We tend to backup LOTS of
little tiny files and as a result our Database is currently around 30Gb.  I
understand that the technical limit for the DB is somewhere around 5TB.

Should I be concerned running a 30GB database on NT using a single server?
Would this be considered a small, average or large TSM installation?


2) We've also found that our library is a little under-sized.  (I regularly
find myself exporting tapes from our primary tape storage pool to make room
for scratch media).  I would like to replace two or three of the DLT40/80
drives in the library with SDLT units.  The ESL9198 hardware will support
Mixing DLT and SDLT drives and media.  Does any know or have experience
setting up a library with two media types?  Would TSM support this type of
environment?

Any help or information anyone can provide would be greatly appreciated!

Dave Miller
[EMAIL PROTECTED]








**********************************************************************
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.

Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**********************************************************************

Reply via email to