Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Logmode\s+RollForward\s+on\s+5\.1\.6\.2\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Logmode\s+RollForward\s+on\s+5\.1\.6\.2\s*$/: 7 ]

Total 7 documents matching your query.

1. Logmode RollForward on 5.1.6.2 (score: 1): Author: "Rushforth, Tim" <TRushforth AT WINNIPEG DOT CA>; Date: Thu, 6 Mar 2003 10:51:25 -0600; Is anyone running in logmode rollforward on 5.1.6.2? I'm currently testing 5.1.6.2 on W2K and this doesn't seem to be working. Issue set logmode rollforward to set to rollforward mode (q status confi; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-03/msg00278.html (11,277 bytes)
2. Re: Logmode RollForward on 5.1.6.2 (score: 1): Author: Andrew Raibeck <storman AT US.IBM DOT COM>; Date: Thu, 6 Mar 2003 10:52:41 -0700; Tim, I'm playing with this myself, and I don't see the problem you describe. Is it possible that a db backup is being run between the time you see the usage climb and when it goes back down? Regards,; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-03/msg00283.html (12,153 bytes)
3. Re: Logmode RollForward on 5.1.6.2 (score: 1): Author: "Rushforth, Tim" <TRushforth AT WINNIPEG DOT CA>; Date: Thu, 6 Mar 2003 14:16:56 -0600; OK this is bizarre! I tried this yesterday around 16:00. The last db backup was yesterday at 13:30 (according to volhist and searching actlog). This morning I could recreate this and showed a co-work; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-03/msg00295.html (13,042 bytes)
4. Re: Logmode RollForward on 5.1.6.2 (score: 1): Author: Andrew Raibeck <storman AT US.IBM DOT COM>; Date: Thu, 6 Mar 2003 13:30:03 -0700; OK Tim, I think I see the problem. The recovery log doesn't go into roll-forward mode until the next full database backup, which is necessary in order to have a baseline from which the log can be use; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-03/msg00299.html (14,221 bytes)
5. Re: Logmode RollForward on 5.1.6.2 (score: 1): Author: "Rushforth, Tim" <TRushforth AT WINNIPEG DOT CA>; Date: Thu, 6 Mar 2003 15:41:02 -0600; Ok, I'm not crazy! I've recreated this by: - used wizard to create another server instance using defaults - created an archivepool volume - defined a test client - update recovery log space trigger t; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-03/msg00300.html (13,433 bytes)
6. Re: Logmode RollForward on 5.1.6.2 (score: 1): Author: "Rushforth, Tim" <TRushforth AT WINNIPEG DOT CA>; Date: Fri, 7 Mar 2003 08:34:00 -0600; Thanks Andy! That was my problem. (Something I would only see in this test environment since normally our logmode is set to rollforward from the start!) OK Tim, I think I see the problem. The recover; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-03/msg00349.html (12,061 bytes)
7. Re: Logmode RollForward on 5.1.6.2 (score: 1): Author: David E Ehresman <deehre01 AT LOUISVILLE DOT EDU>; Date: Fri, 7 Mar 2003 10:18:25 -0500; I've been running TSM 5.1.6.2 server on AIX in production for two weeks in RollForward mode. Our log utilization increases steadily until we do our daily data base backup at which time it returns to; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-03/msg00355.html (11,567 bytes)

Current List: 1 - 7
Page: [1]