DSMFMT & EXTEND commands 2

[almond247]

Hello all,

We were getting the following messages in the TSM server log. As you can the /backup1 mount point was out of space and the incremental backup was falling. It kept triggering
a DATABASE Backup but it keep failing and it was to the point where I could not login to the TSM server.


ANR2997W The server log is 99 percent full. The server will delay transactions by 300 milliseconds.
ANR4561I Triggered database backup retry delay ended; checking database backup trigger criteria.
ANR0984I Process 843 for DATABASE BACKUP started in the BACKGROUND at 09:09:41.
ANR4553I Incremental database backup triggered; started as ANR8340I FILE volume /backup1/55906582.DBB
ANR0513I Process 843 opened output volume /backup1/55906582.DBB.
ANR1360I Output volume /backup/55906582.DBB opened ).
ANR8785E Out-of-space in file system for FILE volume
/backup1/55906582.DBB.
ANR4573E Database backup terminated - excessive write errors encountered. ANR0987I Process 843 for DATABASE BACKUP running in the BACKGROUND processed 44480 items with a completion state of FAILURE

The problem was corrected, but for future reference I want to be sure of the sequence of the commands that I use to correct this.

Is it the log first and then the DB backup for example if I wanted to format and then extend the recovery log DSMFMT 100mb would the sequence be the following?

Cd to /server/bin

DSMFMT -m -log /tsmlog1/log2.dsm 100 100
DSMFMT -m -log /backup1>>>>
extend db 100
restart the server? Using dsmserv extend?

TSM 5.3.2
AIX 5.3

Thanks in advance!

 

[RMGBELGIUM]

dsmfmt –log tsm.logxxx 501
dsmadmc -> def logvol /adsm_b_log/tsm.logxxx
extend log 500

dsmfmt –db tsm.dbxxx 1001
dsmadmc -> def dbvol /adsm_b_db/tsm.dbxxx
extend db 1000

no restart needed of dsmserv


rgds,

R.

 

[LED888]

There is really no need to use the DSMFMT unless the TSM Server is down.

If the TSM Server is still running, from the command line interface (dsmadmc) just need to issue the following:

To extend the database:
define dbvolume /path/new.dbvolume #
#- is a numeric value in MB.

extend db #

Before extending the database, issue q db and check the
max extention parameter. If there is a value present, then you can extend the db by that value without needing to create a new dbvolume.

To extend the recovery log:
define logvolume /path/new.logvolume #
#-is a numeric value in MB.

extend log #


Good Luck,
Sias