Re: rollforward vs. normal mode

2002-07-29 Thread William Rosette
t by: "ADSM: cc: Dist Stor Subject: Re: rollforward vs. normal mode Manager" <[EMAIL PROTECTED] .EDU> 07/27/02 01:16 PM

Re: rollforward vs. normal mode

2002-07-29 Thread Bob Booth - UIUC
Workstation Data Save Facility On Mon, Jul 29, 2002 at 09:21:29AM -0400, William Rosette wrote: > Thank you Roger for the info. I'm curious about what WDSF stood for?

Re: rollforward vs. normal mode

2002-07-27 Thread Roger Deschner
Original Message----- >From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of >William Rosette >Sent: Wednesday, July 24, 2002 6:29 AM >To: [EMAIL PROTECTED] >Subject: Re: rollforward vs. normal mode > > >Hi Roger, > >I recently sent this memo to a TSM c

Re: rollforward vs. normal mode

2002-07-24 Thread William Rosette
| | To: [EMAIL PROTECTED] | | cc: |

Re: rollforward vs. normal mode

2002-07-24 Thread Roger Deschner
I've run it both ways. ROLLFORWARD is goodness that lets me sleep better at night, but it's expensive goodness, in terms of management effort and system performance. 1. Define your log to be 12gb, regardless of how big you think it should be. The max in V4+ is 13gb, and you want to leave yourself

Re: rollforward vs. normal mode

2002-07-23 Thread Steve Harris
Joni, There's a stat of cumulative log consumption that can be seen with Q LOG F=D, and can be reset with RESET LOGCONSUMPTION I'm not sure how this works in normal mode - I use rollforward - but it might be worth a look. Let us know how it turns out. Steve Harris AIX and TSM Admin Queenslan

Re: rollforward vs. normal mode

2002-07-23 Thread Joni Moyer
Wanda" cc: Sent by: "ADSM: Subject: Re: rollforward vs. normal mode Dist Stor Manager" <[EMAIL PROTECTED] T.EDU> 07/23/2002 09

Re: rollforward vs. normal mode

2002-07-23 Thread Prather, Wanda
Hi Joni, In my opinion, you should always use ROLLFORWARD, unless you run into a performance or capacity limitation that prevents you from doing so. If you use rollforward mode and you have a hardware crash or a software crash that causes you to have to restore your DB, TSM will restore the DB,