Re: backup systemobject hanging on win2k
Sp4 is released Full packeage (130 MB) http://download.microsoft.com/download/e/6/a/e6a04295-d2a8-40d0-a0c5-241bfec d095e/w2ksp4_en.exe Express Install (600K) http://download.microsoft.com/download/b/1/a/b1a2a4df-cc8e-454b-ad9f-378143d 77aeb/sp4express_en.exe -Original Message- From: Henrik Wahlstedt [mailto:[EMAIL PROTECTED] Sent: vrijdag 27 juni 2003 9:29 To: [EMAIL PROTECTED] Subject: Re: backup systemobject hanging on win2k Hello Joe and others, The problem might be that your w2k client doesnt 'tell' that the scheduled backup is complete when it contacts your TSM server, instead it starts another scheduled backup i.e. it loops. Probably, you cant locally backup system object either, client will crash. I dont recall the name of the security fix from MS that caused this problem, but we tried to uninstall the fix but that didnt solve the problem. In my case, I´m busy at the moment upgrading 250+ w2k servers to v.5.1.6.0. And the best part is... all security hotfixes will be in SP4 which will be released pretty soon. :D Andy -Do you this as a problem? Also, see previous threads this month about this. //Henrik Joe Howell jhowell_tsm@To: [EMAIL PROTECTED] YAHOO.COM cc: (bcc: Henrik Wahlstedt) Sent by: Subject: backup systemobject hanging on win2k ADSM: Dist Stor Manager [EMAIL PROTECTED] RIST.EDU 2003-06-26 15:25 Please respond to ADSM: Dist Stor Manager I'm running TSM 5.1.5 on OS/390 and backing up Win2K servers running the 5.1.5 client. I issue a define clientaction nodename action=command object='dsmc backup systemobject' from the server to each of my clients at the beginning of my backup cycle, followed by a define clientaction nodename action=incremental command. The first command gets scheduled right away, but it appears that in many cases the scheduled command takes hours to finish and get out of the way so that the incremental backup can begin. All I see in the server log is that the session times out and that eventually it reconnects and the schedule completes. I don't see any errors in the client log. Any ideas on what might be going on? I do see that the schedule prompter keeps bugging the client to start the incremental; is it possible that this is causing a problem for the client scheduler? Joe Howell Shelter Insurance Companies Columbia, MO - Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
Re: STK L700 upgrade from 6 to 8 tape drives
Tom, have you tried a reboot with -r (reconfigure and rediscover)on the solaris ... It should come up with the two extra drives .. Cmdline; reboot -- -r Have also verified the scsi id's it seems to have some duplicates .. Which is nevert good with scsi. Regards Marco Sjerps -Original Message- From: Tom Molloy [mailto:[EMAIL PROTECTED] Sent: vrijdag 14 maart 2003 16:02 To: [EMAIL PROTECTED] Subject: STK L700 upgrade from 6 to 8 tape drives We just upgraded our STK L700 library from 6 DLT8000 drives to 8 DLT8000 drives. When reinstalling the TSM Solaris device drivers it only recognizes 6 of the 8 tape drives. It recognizes 1 of the new ones and drops one of the preexisting ones. We verified that the tape drives where working from the OS. Each sbus card controls 2 drives and has the target id's set to 1 and 0 on each card. Anyone else had this problem? Any help would be greatly appreciated. Environment: TSM Server 5.1.5.1 - Sun Ultra Enterprise 4500, 4 GB RAM, OS: Solaris 2.7, Library: Storage Tek L700, 8 - DLT8000 drives SCSI attached. Thank You in advance. Tom Molloy Textron Financial Corporation Information Systems Email: [EMAIL PROTECTED]
Re: NOVELL Client 4.1.2 4.1.3
Install TSAup9 which is the tsa with TSM client 5.1.x and 4.2.1.x for me under Netware 5.x either with sp6a for 5.0 or sp3 with 5.1 regards -Original Message- From: Marc Levitan [mailto:[EMAIL PROTECTED]] Sent: vrijdag 27 september 2002 19:06 To: [EMAIL PROTECTED] Subject: Re: NOVELL Client 4.1.2 4.1.3 Netware 5.1 Thanks! ADSM: Dist Stor ManagerTo: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: RIST.EDUSubject: Re: NOVELL Client 4.1.2 4.1.3 09/27/2002 12:43 PM Please respond to ADSM: Dist Stor Manager I have been using the 4.2.1.29 the 5.1.x clients on my Netware 4.11 5.1 servers with no problems. What version of Netware are you using? Make sure you have the latest TSA500.NLM, TSANDS.NLM SMDR.NLM. Having older versions of these NLM's caused a lot of problems. I am running TSM 4.1.4.5 on AIX 4.3.3. --- Bruce Kamp Network Analyst II Memorial Healthcare System E: [EMAIL PROTECTED] P: (954) 987-2020 x4597 F: (954) 985-1404 -Original Message- From: Marc Levitan [mailto:[EMAIL PROTECTED]] Sent: Friday, September 27, 2002 12:32 PM To: [EMAIL PROTECTED] Subject: NOVELL Client 4.1.2 4.1.3 TSM Server 4.2.1.15 on AIX 4.3.3 I have a Novell client that crashes the server when an Incremental is run. Amazingly, if the Incremental is run separately by volumes it runs okay. For example, i /sys and then i /apps. But when you just run i it crashes the server. Does anyone know what this is caused by??? Also, Can Novell 4.1.3 be backed down to 4.1.2??? Thanks, Marc Levitan Storage Management Specialist PFPC Global Funds Services
Re: Redirect Output in Windows dsmadmc
Use the -out directive .. Works fine .. Even formatted if you want it's in the admin guide -Original Message- From: Richard Cowen [mailto:[EMAIL PROTECTED]] Sent: donderdag 25 juli 2002 15:30 To: [EMAIL PROTECTED] Subject: Re: Redirect Output in Windows dsmadmc When will we be able to do this with a select statement and use a greater than symbol under windows? -Original Message- From: Andy Raibeck [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 24, 2002 8:16 PM To: [EMAIL PROTECTED] Subject: Re: Redirect Output in Windows dsmadmc Consider it noted. Don't know if this will help, but if the Admin client is done in batch mode, then the redirection will work: dsmadmc -id=adminid -pa=x q se c:\test dir\qse.txt Regards, Andy
Re: Need help with ADSM3.1 and WIN NT 4.0 SCSI
Better even de-install the ntt tape driver or disable the tape device in 4mm dat in the section device of the control panel This willfor comee any conflict.. Regards Marco sjerps Universal International Music -Original Message- From: Hunny Kershaw [mailto:[EMAIL PROTECTED]] Sent: vrijdag 12 juli 2002 9:11 To: [EMAIL PROTECTED] Subject: Re: Need help with ADSM3.1 and WIN NT 4.0 SCSI Andy is correct. If you would like to use adsmscsi to claim the tape drive, you will have to stop the NT driver that claims your tape drive. Since the drive has been claimed by the Window driver and adsmscsi does not find other device it can claim, adsmscsi will not start and you will get the message The system cannot find the device specified.. You saw the device name \\.\tape0, that is a good indication that the drive has been claimed by the NT driver. Regards Hunny Kershaw Internet Address: [EMAIL PROTECTED] Tivoli Storage Manager - Device Driver Development Tel (408) 256-2828, T/L 276-2828 Quality Policy = Commit to Quality, Customer Satisfaction, Continual Improvement Andrew Raibeck/Tucson/IBTo: [EMAIL PROTECTED] M@IBMUS cc: Sent by: ADSM: Subject: Re: Need help with ADSM3.1 and WIN NT 4.0 SCSI Dist Stor Manager [EMAIL PROTECTED] .EDU 07/11/2002 04:12 PM Please respond to ADSM: Dist Stor Manager Did you try shutting down the Windows driver before starting the ADSMSCSI driver? Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply) The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. O. Oexmann [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/11/2002 15:03 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Need help with ADSM3.1 and WIN NT 4.0 SCSI Hello, i have to reactivate an old 3.1 installation which used a tape library with 6 cartridges. We do not have the old tape library anymore so i am currently trying to get an ordenary HP 1537A 4mm DAT to work. The Windows driver works fine and i can use the Windows backup program to backup and restore data to the tape but the ADSM SCSI just does not want to start. Is does not find the specific drive.. It is configured under Windows and the ADSM Wizard does find it, but the ADSM SCSI does not start. In the devconfig.out it says GENLIB1 and GENERIC_TAPE and \\.\tape0 Any suggestions or help is higly appreciated Kind regards O. Oexmann
Re: TSA500.NLM not releasing memory
Stephen, Have you tried client 4.2.1.29 first is stable and runs here with out any problems Nw 5.0 sp6a tsa update 8 Tsm Server nt4sp6a version4.2.1.13 -Original Message- From: Firmes, Stephen [mailto:[EMAIL PROTECTED]] Sent: woensdag 22 mei 2002 15:19 To: [EMAIL PROTECTED] Subject: 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
Stephen, You may add these parameter these will improve speed The will increase the comm buffers TXNBYTELIMIT25600 TCPWINDOWSIZE63 -Original Message- From: Firmes, Stephen [mailto:[EMAIL PROTECTED]] Sent: vrijdag 17 mei 2002 0:05 To: [EMAIL PROTECTED] Subject: 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 StorageNetworks, Inc Work: 781-622-6287 http://www.storagenetworks.com
Re: Sloooow Novell Backups
Stephen, Did you check on the half / full duplex setting on the network card ? Full-duplex advised If possible.. Did you also try to backup a large single file size ca 10mb's or larger, what is the performance then ? Regards marco -Original Message- From: Firmes, Stephen [mailto:[EMAIL PROTECTED]] Sent: vrijdag 17 mei 2002 15:11 To: [EMAIL PROTECTED] Subject: Re: Slw 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 StorageNetworks, Inc Work: 781-622-6287 http://www.storagenetworks.com
Re: system params for Solaris on TSM upgrade to 4.1.2.0
Dale, Which solaris version are your running 7 or 8 Don't forget to apply the various patches for each.. Platform and server.. set rpcmod:svc_default_stksize=0x4000 this parameter caused some panics here with out the patch for the solaris this is resolved by the big patch for your solaris version .. -Original Message- From: Jolliff, Dale [mailto:[EMAIL PROTECTED]] Sent: donderdag 18 april 2002 23:28 To: [EMAIL PROTECTED] Subject: system params for Solaris on TSM upgrade to 4.1.2.0 I'm getting kernel panics on reboot after upgrading to 4.2.1.0 on Solaris. Once we remove the changes that the README says are required to /etc/system the machine runs ok... Anyone seen this before? Here's the message from the admin: Here's the section of my '/etc/system' file that appears to be causing the kernel panic: *** *Following are parm values required for TSM backups *** *** lwp_default_stksize=0x4000 *** rpcmod:svc_default_stksize=0x4000 *** semsys:seminfo_semmap=50 *** semsys:seminfo_semmni=50 *** semsys:seminfo_semmns=300 *** semsys:seminfo_semmnu=150 *** semsys:seminfo_semopm=50 *** semsys:seminfo_semume=50 *** semsys:seminfo_semmsl=125 * * set lwp_default_stksize=0x4000 set rpcmod:svc_default_stksize=0x4000 set semsys:seminfo_semmap=50 set semsys:seminfo_semmni=50 set semsys:seminfo_semmns=300 set semsys:seminfo_semmnu=150 set semsys:seminfo_semopm=50 set semsys:seminfo_semume=50 set semsys:seminfo_semmsl=125 Thanks,
Re: ASR on NT Novell servers/clients
William, Mark, ASR is a compaq thing i believe, as for solving the abends Novell needs to be up the lastest service pack Nw 5.0 sp 6a Nw 5.1 sp 3 And don't forgett the tsa update to be at the lastest tsa versions.. Tsaupdate8 works for me And the Win 2000 thing install client patches 4.2.1.20 or higher see flash messages at the Tivoli site about the clients. -Original Message- From: William Rosette [mailto:[EMAIL PROTECTED]] Sent: vrijdag 12 april 2002 20:57 To: [EMAIL PROTECTED] Subject: Re: ASR on NT Novell servers/clients No on both accounts. The server reboots itself, and the only way of knowing is through event viewer. Remeta, Mark MRemeta@SELIGMA To: [EMAIL PROTECTED] NDATA.COM cc: Sent by: ADSM:Subject: Re: ASR on NT Novell servers/clients Dist Stor Manager [EMAIL PROTECTED] T.EDU 04/12/02 01:08 PM Please respond to ADSM: Dist Stor Manager Hi William, do you mean the Novell servers abend and the NT server's blue-screen? I have never heard of ASR (automatic server recover)??? Mark -Original Message- From: William Rosette [mailto:[EMAIL PROTECTED]] Sent: Friday, April 12, 2002 11:52 AM To: [EMAIL PROTECTED] Subject: Re: ASR on NT Novell servers/clients Hi SMer's, Anybody have any info. on TSM backups causing ASR (Automatic Server Recover (reboot)) on servers? We seem to be getting them at night during backups and we are not missing anything as far as the backup is concerned but this is causing trouble on the client side. We do have MacAffee running during backups which could be an issue. And there have been 3 boxes that have done this 2 Novells are at 4.1.2 on TSM and 5.0 on Netware. and the 1 Windows 2000 is at 4.2.1.18 on TSM and service pack 2 on Win 2000. Thanx in advanced Confidentiality Note: The information transmitted is intended only for the person or entity to whom or which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please delete this material immediately.
Re: TSM 5.1 Availability
Try this one Wanda ftp://service.boulder.ibm.com/storage/tivoli-storage-management -Original Message- From: Prather, Wanda [mailto:[EMAIL PROTECTED]] Sent: dinsdag 9 april 2002 21:12 To: [EMAIL PROTECTED] Subject: Re: TSM 5.1 Availability $%%^^!!!#! Anybody found what they have done with the Fixes Downloads page?!? -Original Message- From: Rushforth, Tim [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 09, 2002 11:24 AM To: [EMAIL PROTECTED] Subject: Re: TSM 5.1 Availability Do we now call it ITSM?! See http://www.tivoli.com/products/index/storage_mgr/ This product has changed from Tivoli Storage Manager to IBM Tivoli Storage Manager -Original Message- From: Steve Hnath [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 09, 2002 9:11 AM To: [EMAIL PROTECTED] Subject: Re: TSM 5.1 Availability The IBM announcement has more details on TSM v5.1 http://www1.ibmlink.ibm.com/cgi-bin/master?xh=Ncc35aWBhPP7Dz1USenGnN9332req uest=announcementsparms=H+202%2d078xfr=N Steve Hnath Code Relief LLC Makers of AutoVAULT
Re: TSM NDS
-Original Message- From: Flemming Hougaard [mailto:[EMAIL PROTECTED]] Sent: woensdag 10 april 2002 11:32 To: [EMAIL PROTECTED] Subject: TSM NDS Hi all I'm having a couple of questions regarding TSM and NDS on a NetWare Server. 1) When encrypting with the Client 4.2.1, is there a way to include the NDS in the encryption? 2) Recently I have noticed a couple of times, where the backup of the server holding the master replica was failing - the backup simply stops and wait for a NetWare username and password! Even though these informations is provided, the backup fails and prompts for the informations again! Anyone having a solution for this? (I have included the PASSWORDACCESS GENERATE NWPWFILE YES in the DSM.OPT) Best regards Flemming
Re: Help with Netware Client
Robert, Try at dmsc prompt 'q tsa' and or depending on NDS backup or not 'q tsa nds' First remove the tsm.pwd file from ba client directory. Had this problem to, and resolved this this way. If this doesn't try reinstalling the client on the server .. -Original Message- From: Robert Ouzen [mailto:[EMAIL PROTECTED]] Sent: zondag 17 maart 2002 8:33 To: [EMAIL PROTECTED] Subject: Help with Netware Client Hi to All I had a Netware 5.1 Client Tivoli 4.2.1.29 when I load the dsmc and run q mgm I got: Node Name: NOVADMINEW Please enter your user id NOVADMINEW I have to type NOVADMINEW to get the information. After quitting and coming back same scenario. I have on my dsm.opt: NODENAME NOVADMINEW Passwordaccessgenerate NWPWFILE yes What amazing too is I have this Client version on similar Netware without any problem !!! Help will be very appreciate .. T.I.A Regards Robert Ouzen [EMAIL PROTECTED]
Re: Communication settings for SUN Solaris
Marco, This is what is use and it works fine, Just a note that my backup server is tied via a seconded ethernet interface in thge same lan segment as the backup server. Dsm.opt SERVERNAME NLBRNNTBU01 DATEFORMAT 3 *QUIET DOMAIN / DOMAIN /var/run DOMAIN /u01 DOMAIN /u03 DOMAIN /u02 DOMAIN /u04 DOMAIN /opt DOMAIN /export Dsm.sys SERVERNAME NLBRNNTBU01 CHANGINGRETRIES 2 PASSWORDACCESS GENERATE TCPSERVERADDRESS10.131.2.119 TXNBYTELIMIT25600 TCPCLIENTADDRESS 10.131.50.35 TCPWINDOWSIZE 1023 SCHEDLOGRETENTION 30 INCLEXCL/opt/tivoli/tsm/client/ba/bin/inclexcl.lst MANAGEDSERVICES SCHEDULE WEBCLIENT PRESCHEDULE /etc/init.d/oracle_db stop POSTSCHEDULE/etc/init.d/oracle_db start SCHEDLOGNAME/opt/tivoli/tsm/client/ba/log/dsmsched.log ERRORLOGNAME/opt/tivoli/tsm/client/ba/log/dsmerror.log -Original Message- From: Marco Bianchi [mailto:[EMAIL PROTECTED]] Sent: donderdag 14 maart 2002 11:42 To: [EMAIL PROTECTED] Subject: Communication settings for SUN Solaris I'm implementing the BAClient on a Sun Enterprise 1. The TSM Server (4.1.2) is on a Windows NT machine and the data will travel on a specific backup LAN. Only TCP-IP is allowed on this LAN. The SUN 10K is connected to the Backup LAN using a Gigabit Ethernet and the TSM, now in Fast Ethernet using 2 adapters in team, will be also upgraded to Gigabit. The Connection is guarantee by a Cabletron Matrix 8000 dedicated to the Backup Lan. Can anyone give me some hint on the parameters for the TCP-IP config on the dsm.opt or dsm.sys of the SUN BAClient? Thanx in advance. Marco Bianchi Rome.
Re: Netware 5.0 Critical Error
Jesse, Update Your TSA to TSAup8 availble by Novel at there website. And Don't use the base code client 4.2.1.0, check for the patch level 19 or higher. It works fine with me (nw 5.0 with sp6a) Regards Marco Sjerps UMG IT Benelux Universal International Music Email : [EMAIL PROTECTED] -Original Message- From: Jesse Sanaseros [mailto:[EMAIL PROTECTED]] Sent: zaterdag 9 maart 2002 0:50 To: [EMAIL PROTECTED] Subject: Netware 5.0 Critical Error Hello, I need help. I'm running TSM Client 4.2.1 on Netware 5.0, I get the following message when my backup starts both manually (incremental) and on a schedule. Starting the schedule does not cause the problem. It happens when the backup actually starts backing up. RIOGRANDE:DSMC Loading module DSMC.NLM Tivoli Storage Manager Version 4.02a August 22, 2001 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2001. Auto-loading module ACPSAAS1.NLM TSM NetWare for SAA 1.3 Stub Version 4.02a August 22, 2001 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2001. Auto-loading module ACPSAAS2.NLM TSM NetWare for SAA 2.0 Stub Version 4.02a August 22, 2001 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2001. Auto-loading module CLIBAUX.NLM Novell NLM Auxiliary Shim Version 1.23b June 6, 2001 Copyright (c) 1996-2001 by Novell, Inc. All rights reserved. CLibAux.NLM is a library that normally exports symbols needed to shim more sup- port atop CLib.NLM. None of these symbols is needed at present. CLibAux.NLM has been unloaded as unnecessary. Loading module DSBACKER.NLM NetWare 5.0 Directory Services Backup Version 6.05a August 20, 1999 Copyright 1993-1998 Novell, Inc. All rights reserved. Patents Pending. Module DSBACKER.NLM unloaded The running process will be suspended. 3-08-2002 5:37:11 pm:SERVER-5.0-4631 [nmID=1001C] WARNING! Server RIOGRANDE experienced a critical error. The offending process was suspended or recovered. However, services hosted by this server may have been affected. Jesse Sanaseros Information Services Network Administrator [EMAIL PROTECTED]
Re: TSM and RAID on NT
Hi , Pétur Eyþórsson Advise for Nt based system for hardware raid is 16k bloks which have proven over the years Standaard i use compaq array controllers and tested various blok sizes and mainly at 16 blok the system preformed the best incombination with NT. A large cache on the raid controller like 64mb to 128mb improves that more. Marco sjerps MCSE/CCNA Universal International Music Email: [EMAIL PROTECTED] -Original Message- From: Pétur Eyþórsson [mailto:[EMAIL PROTECTED]] Sent: woensdag 13 februari 2002 14:41 To: [EMAIL PROTECTED] Subject: TSM and RAID on NT Hi what is the best RAID for TSM on NT and how large should the Stripe Size be on the RAID CONTROLER. Kvedja/Regards Petur Eythorsson Taeknimadur/Technician IBM Certified Specialist - AIX Tivoli Storage Manager Certified Professional Microsoft Certified System Engineer [EMAIL PROTECTED] Nyherji Hf Simi TEL: +354-569-7700 Borgartun 37105 Iceland URL:http://www.nyherji.is
