Thanks Daniel. I haven't even begun the database restore yet. Also I do not believe there is any log information since I erased the existing logs before I started the format.
Mark -----Original Message----- From: Daniel Sparrman [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 28, 2004 9:53 AM To: [EMAIL PROTECTED] Subject: Re: Database and log format question. Hi My guess is that it's commiting log information. During DB restore, the restore is sequential. However, when commiting the log information, it is commiting the log on a per transaction basis. If you're logs where highly used during your last db backup, this could explain why it's taking so long for the TSM server to mount the log. Remember, that during inital startup after a db restore, the TSM server will do a recovery log roll-back, and commit all transactions within the TSM log. Best Regards Daniel Sparrman ----------------------------------- Daniel Sparrman Exist i Stockholm AB Propellerv�gen 6B 183 62 T�BY V�xel: 08 - 754 98 00 Mobil: 070 - 399 27 51 "Remeta, Mark" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 2004-04-28 15:47 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To [EMAIL PROTECTED] cc Subject Re: Database and log format question. ok the server specs are a quad 1.4ghz pentium 4, 4gb memory running win2k advanced server. What I did was erase the old log and database volumes, then do a dsmserv -k format with the log and database volume specs. It created the volumes and formatted the recovery log volumes rather quickly. After it format's the recovery log volumes it does a recovery log volume mount. This is what is taking so long. I've been monitoring the IO and it seems to be doing something to the database disk, perhaps formatting the database volumes too? I don't know. I've done this before but never with a database this large. Thanks, Mark -----Original Message----- From: Justin Bleistein [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 28, 2004 9:35 AM To: [EMAIL PROTECTED] Subject: Re: Database and log format question. 3 hours? Wow!. What's are the hardware specs of your tsm server? What else is going on, on that system (topas, if AIX, or top)? I would probably consider running either a database audit or re-org, then try mounting it again. thanks! On more thing, are you starting the server up again in the foreground or background?. If your initially trying to start it up in the background, kill it and start it up in the foreground first then let it do all of it's redo log record and undo passes, as well as log mount. Then once it's up, and you get a tsm server prompt. Then halt the server and restart it in the background for production operation at that point. Just another thought. --Justin Richard Bleistein |---------+----------------------------> | | "Remeta, Mark" | | | <[EMAIL PROTECTED]| | | DATA.COM> | | | Sent by: "ADSM: | | | Dist Stor | | | Manager" | | | <[EMAIL PROTECTED]| | | .EDU> | | | | | | | | | 04/28/2004 09:19 | | | AM | | | Please respond to| | | "ADSM: Dist Stor | | | Manager" | | | | |---------+----------------------------> >--------------------------------------------------------------------------- ---------------------------------------------------| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Database and log format question. | >--------------------------------------------------------------------------- ---------------------------------------------------| Yesterday morning I had an incident and lost one of the drives I had about half my database volumes defined on. I'm in the process of reformatting the log and database volumes so I can do a database restore. The database is 100gb and my log size is 13gb. It's been mounting the log volumes for over 3 hours now. Does anyone have any experience with a database this large in as far as approximately how long it will take to format and mount the database/log volumes? Thanks in advance, Mark Remeta Confidentiality Note: The information transmitted is intended only for the person or entity to whom or which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please delete this material immediately. Confidentiality Note: The information transmitted is intended only for the person or entity to whom or which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please delete this material immediately.
