The TSM server is down and the overnight backup has failed. When the TSM server is started it throws down a server error

sprasad
Posts: 24
Joined: Sun Oct 09, 2016 2:52 pm

The TSM server is down and the overnight backup has failed. When the TSM server is started it throws down a server error

Postby sprasad » Wed Oct 12, 2016 6:32 pm

Error Message:

a) ps –ef | grep dsm

The dsmserv quite or the rc.adsmserv process is not running

b) Tried starting TSM and got the following error message:

>> ./rc.adsmserv start
10/17/06 18:09:34 Starting Tivoli Storage Manager Server
ANR7838S Server operation terminated.
ANR7837S Internal error LOGSEG871 detected.
0x1008DAEC LogAllocSegment
0x1008A940 ForceLogPages
0x1008B344 LogWriterThread
0x10006D58 StartThread
0xD00080CC _pthread_body
ANR7833S Server thread 1 terminated in response to program abort.
ANR7833S Server thread 2 terminated in response to program abort.
ANR7833S Server thread 3 terminated in response to program abort.
ANR7833S Server thread 4 terminated in response to program abort.
ANR7833S Server thread 5 terminated in response to program abort.
ANR7833S Server thread 6 terminated in response to program abort.
ANR7833S Server thread 7 terminated in response to program abort.
ANR7833S Server thread 8 terminated in response to program abort.
./rc.adsmserv[19]: 32804 IOT/Abort trap(coredump)

San
Posts: 24
Joined: Sun Oct 09, 2016 2:53 pm

Re: The TSM server is down and the overnight backup has failed. When the TSM server is started it throws down a server e

Postby San » Wed Oct 12, 2016 6:34 pm

I had faced this issue in past,

The above error message indicates that the log volume on the TSM server has got full and hence the TSM server crashed and is not able to start up.

1. First navigate into the filesystem where your log volume resides on your TSM server.


> cd /var/adsmserv.log
> ls

log1.dsm lost+found

2. Check df –g for space in the filesystem

3. If there is adequate spaces execute the following command:

dsmfmt -m -log log2.dsm 100

This command increases the log space by 100 mb .

You would get the following output:
AIX Server DSMFMT Extent/Volume Formatting Program

Licensed Materials - Property of IBM

Actual allocation for log2.dsm will be 101 MB
Allocated space for log2.dsm: 105906176 bytes

> ls -l
total 413704
-rw-r--r-- 1 root sys 105906176 17 Jun 18:09 log1.dsm
-rw-r--r-- 1 root sys 105906176 18 Jun 10:09 log2.dsm

> pwd
/var/adsmserv.log

> df -k .
Filesystem 1024-blocks Free %Used Iused %Iused Mounted on
/dev/lv04 262144 46812 83% 19 1% /var/adsmserv.log



5.Now we have to present this extended space to the TSM server:

>cd /usr/tivoli/tsm/server/bin


 dsmserv extend log /var/adsmserv.log/log2.dsm 100
 You would get the following output:

ANR0900I Processing options file dsmserv.opt.
ANR0200I Recovery log assigned capacity is 100 megabytes.
ANR0201I Database assigned capacity is 200 megabytes.
ANR0306I Recovery log volume mount in progress.
ANR0984I Process 1 for EXTEND LOG started in the BACKGROUND at 10:11:51.
ANR0307I Recovery log extend in progress; 4 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 8 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 12 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 16 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 20 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 24 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 28 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 32 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 36 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 40 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 44 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 48 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 52 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 56 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 60 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 64 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 68 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 72 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 76 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 80 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 84 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 88 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 92 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 96 megabytes of 100 formatted.
ANR0307I Recovery log extend in progress; 100 megabytes of 100 formatted.
ANR2268I Recovery log assigned capacity has been extended.
ANR0988I Process 1 for EXTEND LOG running in the BACKGROUND processed 104,857,600 bytes with a completion state of SUCCESS at
10:12:39.
ANR7835I Server thread 3 terminated in response to server shutdown.
ANR7835I Server thread 4 terminated in response to server shutdown.
ANR0991I Server shutdown complete.

ps -ef | grep dsm
root 36360 33884 1 10:12:53 pts/1 0:00 grep dsm

Now we can start the TSM server:

> >> ./rc.adsmserv start



Sending nohup output to nohup.out.

r60-root> ps -ef | grep dsm
root 33790 4960 0 10:13:24 pts/1 0:07 dsmserv quiet
root 35786 33884 3 10:13:59 pts/1 0:00 grep dsm


> dsmadmc
Tivoli Storage Manager
Command Line Administrative Interface –
Enter your user id: admin

Enter your password:

Session established with server
tsm: XXADSM> Now check for q log

See this percentage and monitor it daily as part of TSM daily checks


Return to “TSM”

Who is online

Users browsing this forum: No registered users and 1 guest