mason and I are at the bookstore. He is reading he s reading. Can you believe it.
Removed association of PFMREPORT to the schedule backup for Daily_0100
using command
delete association ntsrv0 daily_0100 pfmreport
to add back to the schedule we will need to use the command
define association ntsrv0 daily_0100 pfmreport
test of imified to my tsm blog
I had a client node that went out of production. It kept showing as missing backups on my daily backup report. To remove it from the schedule I had to run this command
tsm: TSM>q sched linux0
Domain * Schedule Name Action Start Date/Time Duration Period Day
———— – —————- —— ——————– ——– —— —
LINUX0 DAILY_0100 Inc Bk 05/05/05 01:00:00 3 H 1 D Any
LINUX0 MONTHLY_ARC_FOU- Arch 06/04/05 01:00:00 5 H 1 Mo Any
RTH_0100
LINUX0 MONTHLY_ARC_FOU- Arch 06/04/05 02:00:00 1 H 1 Mo Any
RTH_0200
LINUX0 MONTHLY_ARC_FOU- Arch 06/04/05 03:00:00 1 H 1 Mo Any
RTH_0300
tsm: TSM>delete association linux0 daily_0100 dds-secondary
Do you wish to proceed? (Yes (Y)/No (N)) Y
ANR2511I Node DDS-SECONDARY disassociated from schedule DAILY_0100 in policy
domain LINUX0.
Had to define new drive path for the new library. Long command without the gui.
06/18/07 15:26:23 ANR2017I Administrator MMCCRARY issued command: DEFINE
PATH tsm drive21 srctype=server desttype=drive
library=lib2 device=/dev/rmt1 (SESSION: 146)
06/18/07 15:26:58 ANR2017I Administrator MMCCRARY issued command: DEFINE
PATH tsm drive22 srctype=server desttype=drive
library=lib2 device=/dev/rmt2 (SESSION: 146)
We have a new library IBM TS3310. 212 slots that will accomadate all our Tapepool volumes. It has 4 LTO3 drives. We currently use LTO2 tapes for our old tapecopy and tapepool volumes. I want to be able to run reclamation on tapecopy and make sure that a LTO2 tape is allocated when requested from the library.
To do this I defined the volume in the Tapecopy storage pool using this command
Define volume tapecopy 000471
I then checked in the pseudo scratch/private volume into the library as private
checkin libv lib2 000471 status=private
when starting reclamation on tapecopy, TSM then selects 000471 for the reclamation process. This ensures that Im not sending off one of my new LTO3 scratch tapes the next day with only a small utilization.
Im upgrading to version 5.3 of tsm server. Im having to upgrade some of my client releases to stay compliant. I ran this sql statement to identify which clients needed upgrading.
select node_name,client_version,client_release from nodes where client_release
It gave me this output.
NODE_NAME CLIENT_VERSION CLIENT_RELEASE
BLACKHOLE 5 1
DDS-SECONDARY 5 1
E-GATE-LINUX 5 1
NTSRV0BDC 5 1
NTSRV0PDC 5 1
PORTALSHRS 5 1
To run the schedule command in the background and to keep the client scheduler running, even if you log off your system, enter the following:
nohup dsmc schedule 2> /dev/null &
If a Tivoli Storage Manager password is required for your workstation and you want to run the schedule command in the background, enter the password with the command.
Root User: To start the client scheduler automatically, ensure that the passwordaccess option is set to generate in dsm.sys, then follow the procedure below for your operating system:
For non-z/OS UNIX, add the following entry to the /etc/inittab file:
itsm::once:/usr/bin/dsmc sched > /dev/null 2 >&1 # TSM scheduler
Look for tapes which have errors
select volume_name, read_errors,write_errors from volumes where read_errors>0 and stgpool_name='TAPEPOOL' or write_errors>0 and stgpool_name='TAPEPOOL'
This will give a list of tapes that have reported read and write errors. If you have a lot of these, consider upping the thresholds so you can concentrate on tapes with a lot of errors first.
List unavailable tapes
q volume access=readonly and q volume access=unavailable
This will give you list of tapes that have been put in this state, probably because the system has identified an error. However, a tape will be marked as unavailable if TSM tried to mount it and it is not in library.
Look for tapes which have errors
select volume_name, read_errors,write_errors from volumes where (read_errors > 0 or write_errors > 0)
This will give a list of tapes that have reported read and write errors. If you have a lot of these, consider upping the thresholds so you can concentrate on tapes with a lot of errors first.
To fix a problem, run the audit command
AUDIT VOLUME volser FIX=YES
If a part of a tape is faulty, the audit command will try to fix it. If cannot fix a problem file, and a copy exists on another tape, then you need to use the RESTORE VOLUME command. If there is no copy, then the AUDIT command just deletes the entry from the database.
If the tape is hopelessly trashed, and you do not have a copy, the only answer the ‘delete volume discard=yes’ command. However, its always worth trying a MOVE DATA command first to see if you can rescue something from the tape.
