Recovery Log 1

[sqtran]

Hi,

Since we are adding more clients to TSM server, it seems like the recovery log /tsmlog is growing and now it reach to 98% full. /tsmlog is a filesystem of rootvg which is defined by 2 recovery log volumes and each recovery log is allocating 2GB.

I know that i can not change the size of the recovery log volume since it is already defined in TSM server, but i am not sure if i can allocate more space for /tsmlog filesystem and if i don't is the server is going to crash if /tsmlog is reaching to 100% used.

Please give me some ideas in this sistuation.

Thanks a lot

Sharon

 

[LED888]

Since I do not know what operating system that the TSM Server is running on.

If the TSM Server is down here are the steps for AIX:
For other operating system here is the link to the TSM Manuals.

http://publib.boulder.ibm.com/tividd/td/tdprodlist.html#S

You'll find the the process is the same regardless of the operating system.

1) In the dsmserv.opt file add the following at the bottom of the file:

EXPINTERVAL 0 <- Zero
DISABLESCHEDS YES
NOMIGRRECL

2) DSMFMT an additional recovery log
dsmfmt -m -log /usr/lpp/adsmserv/bin/temprec.log 100

This will create a 100MB temporary recovery log.

3) Use the DSMSERV EXTEND LOG command to do an emergeny recovery log extension....

dsmserv extend log /usr/lpp/adsmserv/bin/temprec.log 100

4) Remove or comment our the three lines that were added to the dsmserv.opt file.

If the TSM Server is running could do the following:

1) define dbvolume /usr/tivoli/tsm/server/bin/ formatsize=100

2) EXTend LOG 100

 

[LED888]

Forgot to add the following.

Once the recovery log is extended.
Perform a database backup of the TSM Server.
This will commit the data in the recovery log to the
database.

backup db devclass=device_class type=full

BTW: Since I do not know what version of TSM that you are running.
If we are using TSM 5.1 or 5.2 and the log mode is normal.
The recovery log should not be filling up. If this is the case need to running CLEANUP BACKUPGROUPS, for some odd reason this undocumented command will clear the issue.