|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] That scenario is not possible. Each set of libraries belongs to a legally separated company. And, granted the backup after the Domino backup runs for hours, however the longest that any one particular company is down is a few minutes. And there in an intranet site which lists the minutes your division was locked out the previous night. The users count on consistency. And, other job schedule entries do also. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Norbut, Jim" <Jim.Norbut@Grubb-Ellis.com> Sent by: midrange-l-admin@midrange.com 12/06/2002 05:27 PM Please respond to midrange-l To: <midrange-l@midrange.com> cc: Fax to: Subject: RE: Backup performance issue. Is it absolutely critical that you figure it out: You probably will waste more time than it would take to just change the next program to check to see if the device is ready...if not....pause 5 minutes....and check again and so on and so on. Assuming that scenario is possible in your workplace. -----Original Message----- From: rob@dekko.com [mailto:rob@dekko.com] Sent: Friday, December 06, 2002 4:16 PM To: midrange-l@midrange.com Subject: Backup performance issue. This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] I have a backup that uses the SAV command to save some Domino IFS files. It should fit in a four hour window between 8pm and 12 midnight. It uses a 3590 tape drive. Most nights it fits fine. However on occasion it takes too long and the next job that needs the tape drive aborts it. I choose the following problem question: How do I determine why the backup takes longer on one night versus others? I looked at the performance data, (iSeries nav, my connections, my400, Configuration and service, Collection services, right click on collection, Performance tools, performance data). Charts: Transaction count: I don't think it ever exceeded 500 Transaction response time: I don't think it ever exceeded 0.5sec. Total CPU utilized: I think it peaked at 10% Interactive CPU: I think it peaked at 0.37% Batch cpu: I think it peaked at 9% High disk utilization: peaked at 19% Machine pool faults: two spikes around 35, 2 around 20 and the rest below that. User pool faults: stayed under 100 Exception CPU utilization: Strange. One peak at 80. Two peaks at 70. The rest all around 0. I checked out SST tape statistics and noticed no temp read or write errors. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.