Root/Amin Privilege
My management has directed the move of the TSM Administrator function to our Operations department. We have a unix TSM server with a mixture of unix and NT clients. Software installation/planning would still be done on the Systems side of the house, but everything else would be handled in Operations. Do you know if this hand-off is possible without providing root/admin provileges on each client and the server to Ops? Thanks, Maria
ADSM 3.1.0.3 to 3.7.2.19
Server: AIX 4.3.2 TSM 3.7.2Clients: NT 4 ADSM 3.1.03 Any reason to upgrade our NT clients currently at ADSM v 3.1.03 to ADSM v 3.1.08 before upgrading to 3.7.2.19 as Tivoli support suggested? Thanks, Maria
4.1 Server/3.1 Clients
We're getting ready to move our TSM server from an SP node to an H70 (AIX 4.3.3). We are currently at 3.72 on the server and running a mixture of 3.7 and 3.1 clients. Are the 3.1 clients supported under 4.1? Should we go to 3.7.4 instead? Thank you, Maria Ragan
Memory Pool #23 doesn't exit
Could anyone tell me what this message in the dsmerror.log indicates? "mpDestroy: Memory Pool #23 doesn't exist." I've started getting this error on AIX clients I recently upgraded to TSM 4.1.2.0. The TSM server is AIX 4.3.3.0 running TSM 4.1.0.0. Thank you, Maria
Deleted Client/Export Node
I have a TSM client node (WinNt 4.00, ADSM v3.1.0.3) that has been deinstalled. The node and file spaces have not been deleted from the TSM server (AIX 4.3.3, TSM 4.1.0.0) because they're afraid they might need the data some day. The occupancy for this node includes only backed up data; no archiving. Would "Export Node" be appropriate for moving this node out of the server and tape pool onto tape that I can send to the vault? Thank you, Maria
SQLSCHED.LOG Pruning
Can anyone tell me how to prune the connect agent logs? I have SCHEDLOGRetention=14 in the dsm.opt file, but the sqlsched.log keeps growing. Thanks, Maria Maria Ragan Mid Range Systems Bear Creek Corporation
MSExchange Connect Agent
Any idea what is causing the following error: MSExchange Connect Agent Ver 1 Rel1 Level 0.0B; NT platform 9/3/2000 00:48:31,COMMAND LINE:D:\\WIN32APP\IBM\ADSM\agentexc\excdsmc/backup:is,full /adsmoptfile:D:\WIN32APP\IBM\ADSM\agentexc\dsm.opt/logfile:D:\\WIN32APP\IBM\ ADSM\agentexc\excsfull.log 9/3/2000 02:00:18,BACKUP(CLC) - Database:IS, Type:0,Actual bytes:N/A,Secs:0.00,Kb/Sec:0.00,Exchange Server: MAIL1,ADSM server:D\WIN32APP\IBM\ADSM\agentexc\dsm.opt,Status: Exchange Error: A read verification error occurred. Thanks, Maria Maria Ragan Mid Range Systems Bear Creek Corporation
Connect Agemt Error
SQL 7/NT4/ADSM Connect Agent 1.1.1A Trying to restore a production database into a new database created for the recovery. Getting the following error: Error: SQL server errors encountered. DB_LIB message: The file e:\mssql7\data\dbname.mdf cannot be used by Restore. Consider using the WITH MOVE option to identify a valid location for this file. Read on this site that for SQL 7.0 they require the original database file (.mdf file) to NOT exist before doing a "restore into". The suggestion was to rename the database .mdf file to something else or restore to a different SQL server. However, DBA has told me that the database is empty. It was created just to house this load from production. What are we missing? Thanks, Maria Maria Ragan Mid Range Systems Bear Creek Corporation
ANS1017E (RC-50)
server: ADSM Server 3.7.2.0AIX 4.3.2.0 client: NT 4.0; MS SQL Server 7.0; ADSMConnect Agent for MS SQL Server 1.1.1A I'm receiving the following error when backing up the logs on one database on this client. The full database backups complete successfully on this and other databases on this client. Incrementals complete successfully on other databases on this client. :\WIN32APP\IBM\ADSM\agentsql\dsm, SQL status: DB-LIB message: Write on '\\.\pipe\sqladsm\204541\4240' failed, status = 109. See the SQL Server error log for more details., ADSM status: ANS1017E (RC-50) Session rejected: TCP/IP connection failure Thanks, Maria Maria Ragan Mid Range Systems Bear Creek Corporation
5.1.1.6 Upgrade
Last week we moved the TSM server from an IBM H70 running AIX 4.3.3 and TSM 4.2.2.4 to an IBM 6H1 running AIX 5.1.0.2 then upgraded to TSM 5.1.1.6. My database is about 51 gigs in size. Tivoli support told me to run "cleanup backupgroup" to cleanup orphaned records when I ran into problems with expiration. I was told other activities (such as backing up the database and client backups) could take place while the command ran. After the "cleanup backupgroup" command was running for 5 hours and a backupdb had been running for 2 hours getting a 4th of the way finished when it normally, takes 30 minutes, I halted the server to kill the cleanup command. Support tells me the cleanup command could take 2 days. They also tell me the next release (2 weeks) should include the ability to background the command and restart where you left off. Does anyone have any experience running cleanup backupgroup to validate the 2 day run time? Thank you, Maria Maria Ragan Systems Engineer Unix Systems Group Yamanouchi Consumer, Inc.
SQL redirection
I'm trying to run this sql select statement and redirect the output to a file: select volume_name,state,location from drmedia where state='COURIERRETRIEVE'>/home/maria/from_vault Separating the query with double quotes produces the same error: ANR2907E-Unexected SQL operator token - '>' Thank you, Maria
TDP Delete
Client: NT 5.0; TSM vers 3.7.0.0; TDP for MS SQL ver 1.1.2 Server: AIX 4.3.3; TSM vers 4.1.0 Any idea why I do not see the two databases I wish to delete on the client's TDP GUI ? The databases do show up under a q occupancy on the TSM server. Thank you, Maria Maria Ragan Systems Engineer Unix Systems Group Yamanouchi Consumer, Inc.
