ADSM-L

Re: Betr.: Re: Erasing recovery log volumes

2003-01-24 07:57:14
Subject: Re: Betr.: Re: Erasing recovery log volumes
From: Halvorsen Geirr Gulbrand <gehal AT WMDATA DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 24 Jan 2003 13:58:23 +0100
You could also backup db, which should commit recovery log to database, thus
emptying out the log. Another way (if you have additional diskspace
somewhere else), is to create another log volume the other place, at least
the same size as the current, and after it is finished creating the new
volume, delete the old volume. TSM moves the data from the old to the new
volume. Of course - you need extra disk somewhere to handle this, and your
TSM server OS, must be able to see this as a "local" disk drive.

Just my thoughts on this...

Rgds.
Geirr G. Halvorsen

-----Original Message-----
From: Robin van der Vliet [mailto:r.van_der.vliet AT DAS DOT NL]
Sent: 24. januar 2003 12:22
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Betr.: Re: Erasing recovery log volumes


Thanks for the fast reply!

Just one problem: my volumes are not empty. The volumes are all defined and
used by TSM.
An example:

Volume Name (Copy 1) /tsm/log/daslogL3014002.LOG
Copy Status Sync'd
Volume Name (Copy 2) -
Copy Status -
Volume Name (Copy 3) -
Copy Status -
Available Space (MB) 1196
Allocated Space (MB) 1196
Free Space (MB) 0

So the next question would be: how can I change these volumes into an empty
status so I can safely proceed with the erasing.

Robin



 

                      PAC Brion Arnaud

                      <Arnaud.Brion@PAN         Aan:
ADSM-L AT VM.MARIST DOT EDU

                      ALPINA.COM>               cc:

                      Verzonden door:           Onderwerp:     Re: Erasing
recovery log volumes                                         
                      "ADSM: Dist Stor

                      Manager"

                      <[email protected]

                      .EDU>

 

 

                      24-01-2003 12:00

                      Antwoord a.u.b.

                      aan "ADSM: Dist

                      Stor Manager"

 

 





Hi Robin,

>From what you showed us, you have "Maximum Reduction (MB)  7144" for your
log space, that means you could easily do a "reduce log" to free some of
the log volumes belonging the log, and thereafter delete them with "del
logvol". But first of all do a "q logvol" to check if the volumes you are
going to delete are empty.
This is naturally only a temporary solution : as your log is going to be
reduced in size, it will be filled faster, and therefore re-activate the
trigger, that itself is going to re-create new logvolumes : the snake bytes
it's own tail ! My opinion is you should preferably use a db backup
trigger, specifying to do a db backup as soon as log reaches x percent,
than permanently creating new log volumes. Of course this advice is only
valid if you do your db backups on tape, if you do them on a disk that is
nearly full, no way (you where not really clear on that point).
Hope it helped !

arnaud

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| Arnaud Brion, Panalpina Management Ltd., IT Group     |
| Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland |
| Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01       |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=



-----Original Message-----
From: Robin van der Vliet [mailto:r.van_der.vliet AT DAS DOT NL]
Sent: Friday, 24 January, 2003 11:21
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Erasing recovery log volumes


Hi all,

To my suprise I found my TSM mountpoint completely filled to the maximum.
This mountpoint holds the TSM Database, Incremental DB backups, Recoverylog
volumes and our DiskPool. This left me with a lot of urgent messages
concerning TSM not being able to create new files needed for incremental DB
backups and additional recoverlog volumes.

I did manage to erase some old incremental DB backup files, but I am still
needy for some more diskspace in this mountpoint.

I´ve found my recoverylog (although in RollForwardMode) has consumed way
too much space allready in time so I have reset the recoverylog consumption
and the recoverylog´s maximum utilisation which looked great  in the
details... but did not provide more diskspace yet.

Since I can be quite sure not all of my volumes now hold recover
information I wonder if it is possible to delete the last set of volumes,
freeing some more desperate needed diskspace.

Initially I´ve set the first recoverlog to 2 GB which was fine for a long
period of time. After some severe problems though extra volumes have been
created (the triggers work fine... ....)

My current recoverylog details are:

Available Space (MB)          7168
Assigned Capacity (MB)  7168
Maximum Extension (MB)  0
Maximum Reduction (MB)  7144
Page Size (bytes)       4096
Total Usable Pages            1834496
Used Pages              5252
Pct Util                      0.2
Max. Pct Util                 0.2
Physical Volumes        8
Log Pool Pages          512
Log Pool Pct. Util            1.41
Log Pool Pct. Wait            0.00
Cumulative Consumption (MB)   19.39
Consumption Reset Date/Time   2003-01-24 08:30:08.000000

TSM 4.2.1.8 on AIX 4.3.3


Is it possible to erase some of the recoverylog volumes WITHOUT the need
for an unload of the database, and if so... how can this be done?


Thanks in advance,

Robin van der Vliet
DAS Rechtsbijstand

<Prev in Thread] Current Thread [Next in Thread>