Thanks Richard
My log looks like this
=================================
tsm: JGHBACKUP>q log f=d
Available Space (MB): 7,168
Assigned Capacity (MB): 6,168
Maximum Extension (MB): 1,000
Maximum Reduction (MB): 6,160
Page Size (bytes): 4,096
Total Usable Pages: 1,578,496
Used Pages: 414
Pct Util: 0.0
Max. Pct Util: 29.5
Physical Volumes: 1
Log Pool Pages: 128
Log Pool Pct. Util: 7.20
Log Pool Pct. Wait: 0.04
Cumulative Consumption (MB): 1323.03
Consumption Reset Date/Time: 01/13/2005 11:53:21
=================================================
I doing a FULL DB backup every morning
I know that is better to set it in a ROLL-FOWARD mode ... what do U
think???
Thanks again
Luc Beaudoin
Network Administrator/TSM/SAN
Hopital General Juif S.M.B.D.
Tel: (514) 340-8222 ext:8254
Richard Rhodes <rrhodes AT FIRSTENERGYCORP DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
2005-01-17 01:39 PM
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: TSM RECOVERY LOG mode (TSM server windows 2000)
Make sure you understand the effect of moving to roll-forward mode.
- Is your log large enough
- how often will incrementals run
- will your log fill before incrementals finishes at peak processing
Here is info we collect each day from a script. It shows our log usage
over
the last 24 hours. NOTE - we are in NORMAL mode.
Specifically, note . . .
- Log comsumption
- log consumption over time
. . . . . from report run at 6am, a few says ago . . . .
=======================================================================
== q log ==============================================================
=======================================================================
ANS8000I Server command: 'q log f=d'
Available Space (MB): 12,288
Assigned Capacity (MB): 12,288
Maximum Extension (MB): 0
Maximum Reduction (MB): 10,488
Page Size (bytes): 4,096
Total Usable Pages: 3,145,216
Used Pages: 459,615
Pct Util: 14.6
Max. Pct Util: 19.0
Physical Volumes: 3
Log Pool Pages: 4,096
Log Pool Pct. Util: 0.04
Log Pool Pct. Wait: 0.00
Cumulative Consumption (MB): 11,530.15
Consumption Reset Date/Time: 01/13/05 06:47:22
ANS8002I Highest return code was 0.
=======================================================================
== log consumption and utilization ====================================
=======================================================================
date log-consumption pct-util max-pct-util
200501130700 90.04 18.8 19.0
200501130800 263.47 0.1 19.0
200501130900 527.75 0.5 19.0
200501131000 784.70 0.2 19.0
200501131100 913.95 0.3 19.0
200501131200 1,210.21 0.3 19.0
200501131300 1,433.90 0.9 19.0
200501131400 1,629.41 0.0 19.0
200501131500 1,865.29 0.0 19.0
200501131600 2,077.36 0.0 19.0
200501131700 2,338.80 2.2 19.0
200501131800 2,687.68 5.1 19.0
200501131900 3,521.16 0.1 19.0
200501132000 4,003.88 0.7 19.0
200501132100 4,644.21 4.4 19.0
200501132200 5,271.96 4.2 19.0
200501132300 6,146.77 11.3 19.0
200501140000 6,803.81 16.7 19.0
200501140100 8,080.01 2.2 19.0
200501140200 8,932.82 8.1 19.0
200501140300 9,683.12 7.5 19.0
200501140400 10,382.22 5.6 19.0
200501140500 11,002.79 10.4 19.0
200501140600 11,452.55 14.1 19.0
=======================================================================
== log pin info =======================================================
=======================================================================
==> 200501130700
(250) Session 9693785: Type=Node, Id=HP06
==> 200501130800
(323) procNum=6411, status=Primary Pool DISKPOOL, Copy Pool GO-COPYPOOL,
(323) descr=Backup Storage Pool, name=BACKUP STORAGE POOL,
cancelled=False
(323) procNum=6412, status=Primary Pool DISKPOOL, Copy Pool GO-COPYPOOL,
(323) descr=Backup Storage Pool, name=BACKUP STORAGE POOL,
cancelled=False
(323) procNum=6413, status=Primary Pool DISKPOOL, Copy Pool GO-COPYPOOL,
(323) descr=Backup Storage Pool, name=BACKUP STORAGE POOL,
cancelled=False
(323) procNum=6414, status=Primary Pool DISKPOOL, Copy Pool GO-COPYPOOL,
(323) descr=Backup Storage Pool, name=BACKUP STORAGE POOL,
cancelled=False
(323) procNum=6415, status=Primary Pool DISKPOOL, Copy Pool GO-COPYPOOL,
(323) descr=Backup Storage Pool, name=BACKUP STORAGE POOL,
cancelled=False
(323) procNum=6416, status=Primary Pool DISKPOOL, Copy Pool GO-COPYPOOL,
(323) descr=Backup Storage Pool, name=BACKUP STORAGE POOL,
cancelled=False
(323) procNum=6417, status=Primary Pool DISKPOOL, Copy Pool GO-COPYPOOL,
(323) descr=Backup Storage Pool, name=BACKUP STORAGE POOL,
cancelled=False
(323) procNum=6418, status=Primary Pool DISKPOOL, Copy Pool GO-COPYPOOL,
(323) descr=Backup Storage Pool, name=BACKUP STORAGE POOL,
cancelled=False
==> 200501130900
(238) Session 9710897: Type=Node, Id=GO-DCANYP
==> 200501131000
(379) Session 9697953: Type=Node, Id=ISOC-ORACD2U
==> 200501131100
(68) procNum=6434, status=Disk Storage Pool DISKPOOL, Moved Files: 249,
Moved
(68) descr=Migration, name=MIGRATION, cancelled=False
==> 200501131200
(49) procNum=6432, status=Disk Storage Pool DISKPOOL, Moved Files:
16433,
(49) descr=Migration, name=MIGRATION, cancelled=False
==> 200501131300
(58) procNum=6435, status=Disk Storage Pool DISKPOOL, Moved Files: 3815,
(58) descr=Migration, name=MIGRATION, cancelled=False
==> 200501131400
(79) procNum=6430, status=Disk Storage Pool DISKPOOL, Moved Files:
56934,
(79) descr=Migration, name=MIGRATION, cancelled=False
==> 200501131500
(79) procNum=6430, status=Disk Storage Pool DISKPOOL, Moved Files:
136102,
(79) descr=Migration, name=MIGRATION, cancelled=False
==> 200501131600
==> 200501131700
The recovery log is pinned by a data base backup that is currently
running.
==> 200501131800
The recovery log is pinned by a data base backup that is currently
running.
==> 200501131900
(104) procNum=6464, status=Volume G02334 (storage pool GO-COPYPOOL),
Moved
(104) descr=Space Reclamation, name=SPACE RECLAMATION, cancelled=False
==> 200501132000
(108) Session 9803043: Type=Node, Id=W2SAPITS10Q
==> 200501132100
(261) Session 9806401: Type=Node, Id=PTPLS-SRVR01N
==> 200501132200
(106) Session 9813530: Type=Node, Id=W3FWADMIN01P
==> 200501132300
(106) Session 9813530: Type=Node, Id=W3FWADMIN01P
==> 200501140000
(106) Session 9813530: Type=Node, Id=W3FWADMIN01P
==> 200501140100
(260) Session 9825349: Type=Node, Id=HPMV901P
==> 200501140200
(113) Session 9832068: Type=Node, Id=ISOC-ORACP3U
==> 200501140300
(260) Session 9825349: Type=Node, Id=HPMV901P
==> 200501140400
(480) Session 9849719: Type=Node, Id=HP06
==> 200501140500
(480) Session 9849719: Type=Node, Id=HP06
==> 200501140600
(480) Session 9849719: Type=Node, Id=HP06
Luc Beaudoin
<lbeaudoi AT IS DOT JGH. To: ADSM-L AT VM.MARIST
DOT EDU
MCGILL.CA> cc:
Sent by: "ADSM: Subject: TSM RECOVERY LOG
mode (TSM server windows 2000)
Dist Stor
Manager"
<[email protected]
.EDU>
01/17/2005 12:04
PM
Please respond to
"ADSM: Dist Stor
Manager"
Hi all
My actual TSM RECOVERY LOG is a NORMAL mode ... I wnat to change it to
ROLL-FORWARD mode .... is it better to wait while my TSM server is not
really working .. or I can do it at anytime
P.S. : is there precaution that I should take before changing the mode
....
Thanks
Luc
-----------------------------------------
The information contained in this message is intended only for the
personal
and confidential use of the recipient(s) named above. If the reader of
this
message is not the intended recipient or an agent responsible for
delivering it to the intended recipient, you are hereby notified that you
have received this document in error and that any review, dissemination,
distribution, or copying of this message is strictly prohibited. If you
have received this communication in error, please notify us immediately,
and delete the original message.
|
