BRMS incremental Backup taking more time
Usually increamental backup using BRMS takes half hour where as the check point reaches in 4 or 5 mins....but last 3 days backup took more than 2 hours and check point reaches after one hour of delay, anyone pls suggest what would be the issue and how to resolve it?
Software/Hardware used:
V5R4
Software/Hardware used:
V5R4
ASKED:
August 4, 2011 2:36 PM
UPDATED:
March 31, 2012 7:15 PM
Approved Answer - Chosen by Explorer1910 (Question Asker)
Compare a joblog from an earlier save to one of your recent slow saves.
Match messages and timestamps between the two joblogs to determine which step(s) are using all of the extra time. Show us the last message in the joblog that has a reasonable timestamp and follow it with the first full message that shows that a step took an extra long time to complete.
The system save functions (the program names) that were running at those times can give a clue about what elements were being saved. A common example scenario is that authorities were changed, and the system has to start saving more authority relationships now.
There's no way we can tell anything without seeing what the system says it was doing.
Tom
Other Answers:
Latest Answer Wiki Contributors:
To see other answers submitted to the Answer Wiki: View Answer History.
A frequent problem occurs when doing save-while-active and some new process or job running longer keeps object locked until the delay time is reached or the objects become free. If this is the case you should see new objects not being saved. Again, the joblogs are the place to start.