ACSLS Lock error
When I start the TSM server the library does not get initialized due to the following error: 09/09/2002 10:58:27 ANR8855E ACSAPI(acs_lock_volume) response with unsuccessful status, status=STATUS_LOCK_FAILED. 09/09/2002 10:58:27 ANR8851E Initialization failed for ACSLS library LIBRARY1 will retry in 2 minute(s). I have recyled the TSM server and the ACSLS daemon, the ACSLS app and server, and I even rebooted both boxes. Still no luck. Any ideas? TSM 5.1.1.1 Solaris 8 ACSLS 6.0.1 Thanks for any help. Stephen Firmes TSM Engineer Tivoli Certified TSM Consultant StorageNetworks, Inc Work: 781-622-6287 http://www.storagenetworks.com
How to determine Backupset Size
Does anybody know how to see the size of a Backupset? When the backupset is completed you get a message stating how many files, but no sizes. ANR3501I Backup set for TEST_BOX as TEST.9549550 completed successfully - processed 2,348 files. TSM 4.2.1.9 Solaris 8 Thanks. Stephen Firmes TSM Engineer Tivoli Certified TSM Consultant StorageNetworks, Inc Work: 781-622-6287 http://www.storagenetworks.com
Re: Connecting with acsls
Jacque, Are you starting the ACSLS daemon that facilitates communications between TSM and ACSLS? This is the code I put in my DSMSERV.RC script and I am having no issues. This logic is executed before you start the TSM server. acsdir="/opt/tivoli/tsm/devices/bin" echo "Starting ACSLS daemon." cd $acsdir ./rc.acs_ssi quiet $* || "ACSLS Server (\"$acsdir\") error.. Aborting." Stephen Firmes TSM Engineer Tivoli Certified TSM Consultant StorageNetworks, Inc Work: 781-622-6287 http://www.storagenetworks.com -Original Message- From: Jacque Mergens [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 7:36 AM To: [EMAIL PROTECTED] Subject: Connecting with acsls I am setting up a tsm server and cannot define an acsls library. When I attempt the following command: define library acslib libtype=acsls acsid=0 The server times out and says that the library is not currently available. I am currently running samfs on an E450 that can connect and access the ACSLS server without any problem so I don't think that ACSLS is the problem. I have generated traces that seem to indicate that the communication between the servers is fine but it stops after the first TCP session. In short the TSM interrogates properly for the RPC port, attaches to the port, runs the TCP session and then just shuts up. The configuration is as follows: P640: AIX 4.3.3 TSM 5.1.1 SCSI attached LTO within an L180 UltraSparq 5 Solaris 8 ACSLS 6.0 Connected to an L180
Re: Performance of TSM 4.1.4 with Solaris
Are you using Raw volumes for your storage pool volumes, database volumes, and log volumes? We switched from UFS to RAW and saw a 500% increase in backup throughput. We went from approx 2mb/sec to 10 mb/sec. Stephen Firmes TSM Engineer Tivoli Certified TSM Consultant StorageNetworks, Inc Work: 781-622-6287 http://www.storagenetworks.com -Original Message- From: Charles Anderson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 26, 2002 11:07 PM To: [EMAIL PROTECTED] Subject: Performance of TSM 4.1.4 with Solaris Folks, I have TSM server 4.1.4 on a Sun E450 with 4 processors, 2Gb of ram, 21 disks as the primary stgpool across 3 SCSI busses. We have around 100 nodes backing up to this puppy, backing up around 90Gb nightly ( achiving 11Gb a night ). I'm seeing pretty consistent throughput from the nodes of around 1Gb every 12minutes. Does this sound right to y'all? The E450 is Gigabit ethernet connected to our backup network, but the nodes are almost all on 100Mb connections. Thanks for your help, Ed Anderson Unix Systems Administrator University of Mississippi Medical Center [EMAIL PROTECTED]
TSA500.NLM not releasing memory
I am having a problem with TSA500.NLM not releasing memory after restores. I have to reboot the Novell box in order to get back the memory. Novell is 5.1 service pack 4 with TSA5up9. Novell client is 5.1 TSM server is 4.2.1.9 on solaris 8 TSA500.NLM info: TSA500.NLM (Address Space = OS) Loaded from [SYS:SYSTEM\] NetWare 5.1 Target Service Agent Version 5.05aMarch 28, 2002 TSANDS.NLM info: TSANDS.NLM (Address Space = OS) Loaded from [SYS:SYSTEM\] TSA for Novell eDirectory 7.x, 8.x Version 10110.39eNovember 14, 2001 SMDR.NLM info: SMDR.NLM(Address Space = OS) Loaded from [SYS:SYSTEM\] NetWare SMS Data Requestor Version 5.06aMarch 28, 2002 The results from last night's restore are: Restore processing finished at 18:59:38. Total number of objects restored: 460,325 Total number of objects failed: 0 Total number of bytes transferred: 2.10 GB Data transfer time: 212.53 sec Network data transfer rate:10,379.44 KB/sec Aggregate data transfer rate:652.68 KB/sec Elapsed processing time: 00:56:19 The TSA500.nlm memory statistics are: Module 'TSA500.NLM' Information - Version: 5.05a Creation date: 3-28-2002 Address space:OS Bytes of memory required to load:194,227 Allocated memory: 30,011,392 100% On the system console the following messages appear: 5-22-2002 12:05:09 am:SERVER-5.0-0 [nmID=6001D] Cache memory allocator out of available memory. Thanks for any help. Stephen Firmes TSM Engineer Tivoli Certified TSM Consultant StorageNetworks, Inc Work: 781-622-6287 http://www.storagenetworks.com
Re: Sloooow Novell Backups
I made the tcpip performance changes to the dsm.opt and I am still getting slow transfer times. I tested via ftp and was able to tranfer 40,000 files in a few minutes. So it appears that the TSM client is still not working. here are the stats from my last selective backup: Total number of objects inspected: 600 Total number of objects backed up: 600 Total number of objects updated: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired: 0 Total number of objects failed: 0 Total number of bytes transferred: 230.73 KB Data transfer time:0.00 sec Network data transfer rate:0.00 KB/sec Aggregate data transfer rate: 0.21 KB/sec Objects compressed by:0% Elapsed processing time: 00:18:06 here is the new improved dsm.opt COMMMETHOD TCPip TCPSERVERADDRESScatamount TCPPORT 1500 tcpclientaddressxxx.xx.x.xxx txnbytelimit25600 tcpbuffsize 32 tcpwindowsize 63 largecommbuffersyes processorutilization15 MEMORYEFFICIENTBACKUP no NODENAME novell_test INCLUDE sys:...\* tape9940 INCLUDE extravol1:...\* tape9940 EXCLUDE sys:\system\secaudit.log EXCLUDE sys:\system\events.log EXCLUDE sys:\system\system.log EXCLUDE sys:\system\btrieve.trn EXCLUDE SYS:\system\tsa\err$hst.* EXCLUDE sys:\system\tsa\err$log.* EXCLUDE sys:\system\tsa\skip$log.* EXCLUDE sys:\system\tsa\tsa$temp.* EXCLUDE sys:\system\sys$log.err EXCLUDE sys:\_swap_.mem EXCLUDE sys:\vol$log.err EXCLUDE sys:\tts$log.err NWPWFILE YES passwordaccess generate managedservices schedule webclient Thanks for any help. Stephen Firmes TSM Engineer Tivoli Certified TSM Consultant StorageNetworks, Inc Work: 781-622-6287 http://www.storagenetworks.com -Original Message- From: Flemming Hougaard [mailto:[EMAIL PROTECTED]] Sent: Friday, May 17, 2002 6:59 AM To: [EMAIL PROTECTED] Subject: SV: Slw Novell Backups Hi Stephen I have some general experiences with the TSM client, and here goes: - Never use compress always! - The "INCLUDE SYS:*" wont work... you have to use "SYS:...\*" - I know it's supposed to be the same... but it isn't! - Tune on the following parameters: #TXNBYTELIMIT #TXNGROUPMAX #TCPBUFFSIZE #TCPWINDOWSIZE - Set "MEMORYEFFICIENTBACKUP NO" in the DSM.OPT file (should be standard, but...) Regards Flemming Hougaard Certified Novell Engineer -----Oprindelig meddelelse- Fra: Firmes, Stephen [mailto:[EMAIL PROTECTED]] Sendt: 17. maj 2002 00:03 Til: [EMAIL PROTECTED] Emne: Slw Novell Backups TSM server 4.2.1.9 on Solaris 8 TSM 5.1 client on Novell 5.1 Backing up a volume with 500,000 files approx 1k each. The files are being transfered to the tsm server approx 1/sec. This is just a little too sloow. When using ftp to transfer these same files, either by getting/putting the transfers fly. This is leading me to believe that the issue is with the TSM server/client settings. Does anybody have any ideas on any settings in the dsm.opt that could be changed to enhance performance? Also I want to bind all objects in two of the volumes to a specific mgt class. All that is being bound to it is the dirs. Long day. What am I doing wrong??? Here is the dsm.opt *** COMMMETHODTCPip TCPSERVERADDRESS catamount TCPPORT 1500 tcpclientaddressxxx.yy.z.zzz NODENAME novell_test INCLUDE sys:* tape9940 INCLUDE extravol1:* tape9940 EXCLUDE sys:\system\secaudit.log EXCLUDE sys:\system\events.log EXCLUDE sys:\system\system.log EXCLUDE sys:\system\btrieve.trn EXCLUDE SYS:\system\tsa\err$hst.* EXCLUDE sys:\system\tsa\err$log.* EXCLUDE sys:\system\tsa\skip$log.* EXCLUDE sys:\system\tsa\tsa$temp.* EXCLUDE sys:\system\sys$log.err EXCLUDE sys:\_swap_.mem EXCLUDE sys:\vol$log.err EXCLUDE sys:\tts$log.err NWPWFILE YES passwordaccess generate managedservices schedule webclient Thanks. Stephen Firmes TSM Engineer Tivoli Certified TSM Consultant Stora
Sloooow Novell Backups
TSM server 4.2.1.9 on Solaris 8 TSM 5.1 client on Novell 5.1 Backing up a volume with 500,000 files approx 1k each. The files are being transfered to the tsm server approx 1/sec. This is just a little too sloow. When using ftp to transfer these same files, either by getting/putting the transfers fly. This is leading me to believe that the issue is with the TSM server/client settings. Does anybody have any ideas on any settings in the dsm.opt that could be changed to enhance performance? Also I want to bind all objects in two of the volumes to a specific mgt class. All that is being bound to it is the dirs. Long day. What am I doing wrong??? Here is the dsm.opt *** COMMMETHODTCPip TCPSERVERADDRESS catamount TCPPORT 1500 tcpclientaddressxxx.yy.z.zzz NODENAME novell_test INCLUDE sys:* tape9940 INCLUDE extravol1:* tape9940 EXCLUDE sys:\system\secaudit.log EXCLUDE sys:\system\events.log EXCLUDE sys:\system\system.log EXCLUDE sys:\system\btrieve.trn EXCLUDE SYS:\system\tsa\err$hst.* EXCLUDE sys:\system\tsa\err$log.* EXCLUDE sys:\system\tsa\skip$log.* EXCLUDE sys:\system\tsa\tsa$temp.* EXCLUDE sys:\system\sys$log.err EXCLUDE sys:\_swap_.mem EXCLUDE sys:\vol$log.err EXCLUDE sys:\tts$log.err NWPWFILE YES passwordaccess generate managedservices schedule webclient Thanks. Stephen Firmes TSM Engineer Tivoli Certified TSM Consultant StorageNetworks, Inc Work: 781-622-6287 http://www.storagenetworks.com
Re: client acceptor problem
The problem is that you have /autostart:yes for the TSM Scheduler service. Since the TSM Acceptor service is responsible to start it you have a conflict. It can't be both "autostarted" and "Acceptor" started. Change the scheduler to /autostart:no and you should be all set. Stephen Firmes TSM Engineer Tivoli Certified TSM Consultant StorageNetworks, Inc Work: 781-622-6287 http://www.storagenetworks.com -Original Message- From: Burak Demircan [mailto:[EMAIL PROTECTED]] Sent: Friday, May 10, 2002 12:51 AM To: [EMAIL PROTECTED] Subject: client acceptor problem Hi, Do you remember my question about scheduler, client acceptor and remote agent services. I install service in the following way and I got following error.log message. I start the "TSM Acceptor" service and wait for the schedule to start backup and nothing happens?? Any help appreciated dsmcutil install /name:"TSM Scheduler" /node:KT_FILESRV1 /password:X /autostart:yes dsmcutil install CAD /name:"TSM Acceptor" /node:KT_FILESRV1 /autostart:yes /password:X /CADSCHEDNAME:"TSM Acceptor" dsmcutil install REMOTE /name:"TSM Agent" /node:KT_FILESRV1 /partnername:"TSM Acceptor" /password:X 10-05-2002 07:39:39 ANS0299E Scheduler cannot be started manually because the value of MANAGEDSERVICES option is SCHEDULE Regards, Burak
Re: Multimedia environment using ACSLS
I can only use devices defined to a library at a time. This is because I can't define the libraries as shared=yes. Not supported for ACSLS library types. tsm:>upd libr dltlib shared=yes ANR8416E UPDATE LIBRARY: The SHARED parameter is invalid for library type ACSLS. ANS8001I Return code 3. -Original Message- From: Prather, Wanda [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 10:20 AM To: [EMAIL PROTECTED] Subject: Re: Multimedia environment using ACSLS Can you explain what you mean by "only operate one at a time".. 18 months ago we had 9840's and DLT's in an STK9710 with ACSLS 5.2. No problem just defining two libraries on the same /dev/mchanger address. Wasn't that TSM supported it directly, there just wasn't anything to keep it from working. Did need to define the library as SHARED. We were on TSM 3.7 at the time, though, and the TSM server was AIX. -----Original Message- From: Firmes, Stephen [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 02, 2002 4:23 PM To: [EMAIL PROTECTED] Subject: Multimedia environment using ACSLS What I am trying to get working is this: I have an STK L700 lib with approx 384 slots 4 DLT7000 drives 1 STK 9940 drive 1 STK 9840 drive 1 STK 9840B drive I have the following media types: DLTIV - compat with DLT7000 9840 (STK1R) compat with 9840 and 9840B 9940 (STK2R) compat with 9940 drive I have defined 3 libraries within TSM DLTLIB 9940LIB 9840LIB I also have three corresponding device classes: DLT T9940 T9840 The issue that I am having is that the three libraries can only operate one at a time. This is because I can not define the library as SHARED=YES, because that option is only valid for 349X and SCSI. Solaris 8 ACSLS 6.0.1 TSM 4.2.1.9 Thanks for your help. Stephen Firmes TSM Engineer Tivoli Certified TSM Consultant StorageNetworks, Inc Work: 781-622-6287 http://www.storagenetworks.com
Multimedia environment using ACSLS
What I am trying to get working is this: I have an STK L700 lib with approx 384 slots 4 DLT7000 drives 1 STK 9940 drive 1 STK 9840 drive 1 STK 9840B drive I have the following media types: DLTIV - compat with DLT7000 9840 (STK1R) compat with 9840 and 9840B 9940 (STK2R) compat with 9940 drive I have defined 3 libraries within TSM DLTLIB 9940LIB 9840LIB I also have three corresponding device classes: DLT T9940 T9840 The issue that I am having is that the three libraries can only operate one at a time. This is because I can not define the library as SHARED=YES, because that option is only valid for 349X and SCSI. Solaris 8 ACSLS 6.0.1 TSM 4.2.1.9 Thanks for your help. Stephen Firmes TSM Engineer Tivoli Certified TSM Consultant StorageNetworks, Inc Work: 781-622-6287 http://www.storagenetworks.com
Audit an ACSLS Controlled Library
I am trying to audit my L700 via ACSLS to capture the new tapes that I have placed manually into the library. This is what I get: ACSSA> audit * server Audit: Audit completed, CAP 0, *,* in use. Audit: Audit of storage server, CAP 0, *,* in use. I checked the CAP and it appears to be available: ACSSA> q cap all 2002-04-30 16:04:00CAP Status Identifier Priority Size StateMode Status 0, 0,0 0 20online manual available ACSSA> Any ideas TSM 4.2.1.9 Solaris 8 ACSLS 6.0.1 Stephen Firmes TSM Engineer Tivoli Certified TSM Consultant StorageNetworks, Inc Work: 781-622-6287 http://www.storagenetworks.com
Issues with ACSLS?
Trying to get acsls 6.0 on an Ultra 10 Solaris 8 to work with an L700. I keep getting the following errors in the acsss_event.log entries: 2002-03-28 08:49:49 ERRV[0]: 202 N libacserrv.c 1 358 create_tmpdir: mkdir failed, errno = No such file or directory 2002-03-28 08:49:49 ERRV[0]: 0 E acserrv.c 1 291 createSecondaryTmpDir failed in acserrv.c at line 290 2002-03-28 08:49:49 storage server[0]: 354 N ss_main.c 3 790 ss_main: exit status (74), STATUS_PROCESS_FAILURE, received from acserrv 2002-03-28 08:49:50 storage server[0]: 361 N ss_main.c 3 937 ss_main: acserrv restarted, pid 1536 Tsm server 4.2.1.9 on an E450 running Solaris 8. Any ideas? Stephen Firmes BackPACS Engineer Tivoli Certified TSM Consultant StorageNetworks, Inc Work: 781-622-6287 http://www.storagenetworks.com
