Thanks for all of your replies.

 So far from these I think that Del hit on the issue Domino recovery
manager replaying the transaction against the data base. Unfortunately we
are restricted to a degree by the speed of the TSM server.  We are in the
process of re-evaluating the server as well as the platform that we are
running on.

 If the amount of data that we are applying isn't out of the ordinary then
we need to be mindful of this during our restoration process. I will look
at the dsmerror.log to see if I can find any information there regarding
this process.

 Thanks again everybody for the replies.

 - Brian


Brian L. Nick
Systems Technician - Storage Solutions
The Phoenix Companies Inc.
100 Bright Meadow Blvd
Enfield CT. 06082-1900

E-MAIL:  Brian.Nick AT phoenixwm DOT com
PHONE:   (860)403-2281




                   "Del Hoobler"
                   <[email protected]        To:     ADSM-L AT VM.MARIST DOT EDU
                   BM.COM>              cc:
                   Sent by:             Subject:     Re: TDP Restoration 
Process.
                   "ADSM: Dist
                   Stor Manager"
                   <ADSM-L AT VM DOT MA
                   RIST.EDU>


                   11/22/02
                   10:41 AM
                   Please
                   respond to
                   "ADSM: Dist
                   Stor Manager"






Brian,

Is it truly hung... or is the Domino recovery manager
still replaying transactions against the database?
This sounds like it is taking too long to me, assuming you
have a fast network and fast machine applying the logs.
If it is hung... then that is a different issue that
should probably be taken up with service.

As far as speeds... here is an *example* of some of our
internal IBM Domino servers and the setup and throughput speeds:

Domino server info:
===================
- RS/6000 SP wide nodes,  4x332 Mhz cpu, 3GB RAM, SSA DASD (10,000 rpm)
- ATM connection to TSM server
- Avg 200 GB data/1500 users per domino server
  (some as large as 350 GB total data)
- avg 22-23 txn logs archived per server per day
  => ~1.5GB/day/domino server
- avg 58-60 txn log archived per server per day (no archiving on Sunday)
- 4 to 6 domino servers per TSM server  (backup in parallel)

TSM server info:
================
- RS/6000 SP thin nodes, 4x375 Mhz cpu, 4GB RAM,
  700GB SSA (non-raid) dasd, scsi attached 3494 with 4x3590 E1A tape drives
- backup to disk pool  (some directly to tape)
- archived txn logs maintained on disk for 2 days

Procedure and Throughput info:
==============================
- Full backups 3 times/week  (Sun, Tue & Thurs)
- multiple TDP client sessions per domino server
- Incremental backups nightly when not full backup
- Txn Log Archives scheduled every hour with threshold
  option ONLY on DB servers
- Txn Log Archives scheduled as below
  (threshold option is only on dB server not on Mail servers)
                 0 6,10,14,18,22 * * 1-6
- Full backups complete within 4.5 hours
  (aggregate ~ 220 GB/hr per TSM server assuming ~ 1TB per TSM server)
- Restores of single mailboxes done to alternate server
- 900 MB mail file+roll forward through 2 days worth
  of txn logs in 7-10 minutes
- 7 to 9 MB/sec restore throughput
- 12 to 14MB/sec restore throughput

I hope this helps give you an idea of speeds that
can be obtained.

Standard Disclaimer: The above information is not a guarantee
of the speeds you should get but merely an example of
a real working configuration and setup.

Thanks,

Del

----------------------------------------------------

Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com

- Never cut what can be untied.
- Commit yourself to constant improvement.