The max mount points is 10, that's the number of tape drives we have... This is the first time we've done a hot backup during the afternoon. Hopefully, taking the database down this afternoon will give us better preformance.
Thanks for your help, Debbie PAC Brion Arnaud <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> 08/17/2005 11:14 AM Please respond to "ADSM: Dist Stor Manager" To: ADSM-L@VM.MARIST.EDU cc: Subject: Re: [ADSM-L] SUSPECT: (MSW) Resourceutilization & Backup Question Debbie, What is the maxnummp value for this node ? You should not get such a problem if your client has enough mount points ... Concerning the variable duration for your oracle DB backup, I believe it's simply due to the activity on this DB : few people using it at night = most of the cpu available for backup, and few internal activity for Oracle. Inversely, during the day, you'll get less cpu for backup, and Oracle will be very busy commiting his transactions. Just my humble opinion (and some experience in such an environment)... Cheers. Arnaud ************************************************************************ ****** Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: [EMAIL PROTECTED] ************************************************************************ ****** -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Debbie Bassler Sent: Wednesday, 17 August, 2005 16:32 To: ADSM-L@VM.MARIST.EDU Subject: SUSPECT: (MSW) Resourceutilization & Backup Question Is there any benefit to having the resourceutilization parameter set to 5 when the backup is collocated? The other sessions go into media wait status, waiting on a tape that one of the other sessions is using. Does this cause contention, slowing the server down? Also, I have another question. I'm not sure anyone else uses this technique, but, I'll throw it out there any way. We do hot backups on our oracle databases via a command script using TSM. We create filelists for our files. A hot backup means the database can be updated while the backup is running. We usually run our backup at 9:00 PM, it backs up 200G of data, and takes approx 5 hours to complete. However, due to some maintenance we wanted to do yesterday, we started the backup at 4:30 PM. It had only backed up 130G of data in 5 hours. In an effort to start the maintenance, I cancelled the backup. However, it was decided a good backup was needed, so, we put the maintenance off until tonight. I started the backup, again, last night at 22:35 and it took 5 hr and 25 minutes to complete the 201G backup. I can't understand why the big time difference. There was no more activity in TSM during the slow backup than there is when the backup normally executes. We have an internal Gig switch in our SP environment. Our server level is 5.1.1 and the client level is 5.1.1.5. We're going to bring the database down, at 4:30 this afternoon, and perform the backup again. I need to ensure it will execute in the allotted 5 hour time frame. We don't want to have people waiting 5 hours in hopes of performing maintenace, just to send them home again. Any ideas or suggestions will be greatly appreciated..... Thanks for any help, Debbie