Re: NOVELL Client 4.1.2 & 4.1.3
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Marc Levitan > 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. Are you backing up NDS? Are you using a resourceutilization line in the client's option file? > Also, Can Novell 4.1.3 be backed down to 4.1.2??? With the workaround of changing the node name. You'll end up not being able to restore from the 4.1.3 node's filesystems. -- Mark Stapleton ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MCSE
Re: TSM 4.2 - 5.1 Upgrade
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Wu, Jie > You need to delay your upgrade. We are running AIX 5L and TSM 5.1. Server > crashes everyday. The initial response from TSM support was that > all clients > need to have at lease version 4.2. This is pretty poor, alarmist advice. We have numerous clients running all flavors of Windows clients with an AIX 4.3.3 TSM server at the 5.x level, and none of them are experiencing problems of this sort. -- Mark Stapleton ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MCSE
Re: Veritas volumes for db storage
Veritas raw devices or VxFS filesystems? The latter might be disastrous to your performance. Read the thread "Disk volumes" (started 3 days ago) and especially the post of Scott Walters. Zlatko Krastev IT Consultant Joshua Bassi <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 27.09.2002 22:07 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: Veritas volumes for db storage There shouldn't be any performance problem with a RAID 10 configuration per say. This version of RAID offers the best level of price performance overall. -- Joshua S. Bassi IBM Certified - AIX 4/5L, SAN, Shark Tivoli Certified Consultant - ADSM/TSM eServer Systems Expert -pSeries HACMP AIX, HACMP, Storage, TSM Consultant Cell (831) 595-3962 [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of Chetan H. Ravnikar Sent: Thursday, September 26, 2002 12:08 PM To: [EMAIL PROTECTED] Subject: Veritas volumes for db storage Hi you gurus I am planning to use veritas (0+1) volumes defined into TSM as db volumes, anyone seen any performnace issue here. Platform SUN solaris 2.8 TSM 5.x.x. (not sure yet) Your experience will be a great help many thanks Chetan
Re: Exclude folies
Looking in "Using the Backup-Archive Client" we can find article "Using Wildcard Characters": "In a command, you can use wildcard characters in the file name or file extension *only*." Thus "[in,ex]clude \app_directory*\backup" will not work. You can use "\...\backup" instead but it might not produce the desired results. Last chance is still one by one listing in inclexcl file or dsm.opt. Zlatko Krastev IT Consultant "MCCANN,Tim" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 02.09.2002 04:39 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Exclude folies Hi All, Long time reader, first time poster. I would like to know if I can use pattern matching expression in an include/exclude statement for an .opt file What we have is something along the lines of \app_directory\backup \app_directory_1\backup \app_directory_2\backup \app_directory_3\backup \app_directory_4\backup \app_directory_5\backup \app_directory_6\backup \app_directory_7\backup All we want to backup are the backup directories that reside one level down. This continues on for about fifty some directories. What I would like to do is use pattern matching expression type of thing, so as I don't have an .opt file that goes on and on. If anyone has come across a situation like this before I would appreciate any tips. Thanks, Tim. Notice: The information contained in this e-mail message and any attached files may be confidential information, and may also be the subject of legal professional privilege. If you are not the intended recipient any use, disclosure or copying of this e-mail is unauthorised. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete all copies of this transmission together with any attachments.
Re: TSM Client in MSCS cluster (was Re: W2K Cluster files to exclude)
Prasanna, look at "Tivoli Storage Manager for Windows Backup-Archive Clients Installation and User?s Guide" (GC32-0788-00), Appendix F. Configuring the Backup-Archive Client in a Microsoft Cluster Server Environment. If info there is not enough ask the list again. Zlatko Krastev IT Consultant prasanna S ghanekar <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 27.09.2002 21:32 Please respond to gpresy To: [EMAIL PROTECTED] cc: Subject:Re: W2K Cluster files to exclude Hello Everyone, My question slightly varies from the original one but is it possible for anyone of you to outline procedure to start backing up cluster server using TSM backup client, I'd really appreciate. I'm about to get two new cluster nodes that would need to be backed up. Thanks in advance, Prasanna EDS -- On Fri, 27 Sep 2002 12:44:47 David Longo wrote: >Yes, they can be excluded. > >David Longo. > [EMAIL PROTECTED] 09/27/02 11:04AM >>> >We've just started backing up a W2K cluster with the 5.11 client. The >following files are locked exclusively: > >09/27/2002 00:02:41 ANS4987E Error processing >'\\xx\c$\WINNT\cluster ><\\cowsvd51\c$\WINNT\cluster> \CLUSDB': the object is in use by >another >process >09/27/2002 00:02:41 ANS4987E Error processing >'\\xx\c$\WINNT\cluster ><\\cowsvd51\c$\WINNT\cluster> \CLUSDB.LOG': the object is in use by >another process > >I'm assuming that these can be excluded because the Cluster DB is >backed up >as part of the System Object? > >Thanks, > >Tim Rushforth >City of Winnipeg > > >"MMS " made the following > annotations on 09/27/2002 12:46:04 PM >-- >This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. > >== > Tired of all the SPAM in your inbox? Switch to LYCOS MAIL PLUS http://www.mail.lycos.com/brandPage.shtml?pageId=plus
Re: bad media test!
--> 11. TSM will recreate the bad volume first using the checked in tapes and then completes the restore. The recreation times should be accounted in a restore !? Definitely NOT. Restoration of node's data from offsite tapes and restoration of primary volume are two distinct processes and none of them depends on the other. Whenever you have to restore a node and a primary tape is marked unavailable, TSM server will grab the offsite volume with a copy and will restore from it. You can restore primary copies to another volume but this is independant from node's restore. Therefore primary volume restoration time should not be counted towards node restore time! Zlatko Krastev IT Consultant "Chetan H. Ravnikar" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 06.09.2002 00:51 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:bad media test! Hello TSM gurus (thanks in advance for responding) Thanks for al the people who did send me with comments on how to go about doing data integrity tests for offsite media. I have a test-plan below, Please help me if I am doing this the right way and I understand it correctly 1. Set up a test TSM server 2. Get a client to backup its data on to a onsite-tapepool 3. Create offsite copies for the onsite tapes 4. Send tapes offsite via vaulting 5. Take rolling incrementals for a few days of the same client 6. Shut off backup on that client 7. Pick a volume from onsite and damage it manually (how do I do this!?) should I just mark it destroyed within TSM 8. Initiate a restore point-in-time of a filesystem 9. TSM will report unable to read the onsite tape and hence request for a bunch of tapes from offsite!? 10. Recall the tapes and as what should I check them in *private*? 11. TSM will recreate the bad volume first using the checked in tapes and then completes the restore. The recreation times should be accounted in a restore !? or is this the only way TSM does this. I have to run this test and prove restore times to the management so that we can set proper expectations with our customers. thanks for all your help and tups and, if there is a totally different procedure to test on-site bad media or offsite data integrity please let me know Cheers.. P.S this is not a test for DR
Re: Requirement for licence data collection
As we can see ITSM 5.1 internal license validation is still in old MgSysLAN,MgSysSAN,TDP for XXX, etc. scheme. I can bet a beer 6-pack that this is marketing decision to change licensing scheme short before 9-th April announcement. Development either was not notified or it was too late to allocate resources for such a change. Change from tier-based to processor-based licensing was for nearly all Tivoli products. Only small part of Tivoli product portfolio was not renamed to IBM Tivoli and kept its existing licensing scheme. As we all have seen only six week after announcement new ITSM processor-based licensing was put in the fridge for re-work and came out in last days of August changed to increase the mess :-((( Let's hope in v5.2 (or whatever number it will be) we will have this corrected. Zlatko Krastev IT Consultant Steve Harris <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 30.08.2002 02:50 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Requirement for licence data collection Hi All, I'm just going through a painful licence data collection exercise. I have some 80 nodes registered, but not all these need to be paid for as we set up one node per application on our clusters. Up till now I was managing this adequately with an excel spreadsheet because I just needed to keep track of separate machines:tier1 for Wintel and Tier 2 for everything else. Now, with new new licencing model I need to know how many CPUs as well and this information is not easy to get. I've "outsourced" the setting up of new nodes on non-AIX platforms to the platform support guys, and even if I manually intervened when I created new nodes, it is really easy for someone to move a node from one machine to another, or install a new CPU board and I don't get to know about it. I've looked into pushing scripts down to all my nodes and trying to run some sort of command to get the number of cpus, but this is very difficult to do. On Wintel there is a command, but only if you have the reskit installed and you can run the cscript command etc etc. There are even some boxes that I back up that I have no rights to and have never even had this sort of information. I therefore suggest that there is a requirement for 1. a data collection mechanism to return to the TSM server the number of CPUs and other relevent licencing information on a regular basis. This information should include the system serial number where this is available, or some sort of checksum based on installed equipment a-la Windows XP's anti-piracy feature where it is not. 2. This data to be stored appropriately in the database. 3. Audit lic to be updated to report licence compliance in the same terms as are required by Passport Advantage licencing. ie by number of CPUs on distinct machines. This requirement could be satisfied by simple extensions to the TSM database NODES table to hold the appropriate information. The information could be passsed at dsmc startup in the same way that the IP address is. The only difficult issue is that Intel architecture machines don't have serial numbers. THe windows XP checksum approach will work here even if it doesn't all that well on XP because we are only trying to make a unique checksum for comparison purposes. We don't care if it changes provided that it changes in the same way for all nodes that run on the machine. The checksum mechanism should also be the same for all OSes running on intel architecture so that correct licencing is available for machines logically partioned using VMware or equivalent products. I was recently involved in a backup product selection exercise and ease or difficulty of licence mangement was a huge issue amongst the admins at various levels in the organization, for several different products. At that time TSM had a big plus because managment was easy. It is no longer. Discussion? Steve Harris AIX and TSM Admin Brisbane Australia ** This e-mail, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost if you receive it and you are not the intended recipient(s), or if it is transmitted/ received in error. Any unauthorised use, alteration, disclosure, distribution or review of this e-mail is prohibited. It may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this e-mail in error, you are asked to immediately notify the sender by telephone or by return e-mail. You should also delete this e-mail message and destroy any hard copies produced. **
Re: upgrade to 4.2 server - what client levels supported?
v2 client is not supported against both v4.1 and v4.2 server. This does not automatically mean it does not work but in case of any problem the only answer from IBM would be "upgrade it". So you are on your own (and maybe the ADSM-L list). TSM v4.2 server can work and is supported with clients v4.1, v4.2 and v5.1 (the client itself for v4.1 being out of support). The best approach is to find the latest client supporting your version of AIX - v3.1 for AIX 4.2.1 for example. Zlatko Krastev IT Consultant Michelle DeVault <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 04.09.2002 23:06 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:upgrade to 4.2 server - what client levels supported? I recently inherited the TSM admin duties, so please bear with my ignorant questions ... I'm getting ready to upgrade from 4.1 to 4.2 TSM server for AIX. I've noticed that I have two AIX clients that are at (gasp) 2.1.08. We've been backing them up to the 4.1 server with absolutely no problem. Anyone know of problems I might have if I upgrade the server to 4.2? I've checked the client requirements page at www.tivoli.com, but (surprise) they don't mention anything about a client level that old. Thanks, M. __ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com
Re: Backup reporting: SUMMARY TABLE ISSUE IS FOUND
select sum(cast( ... as decimal)) Total GB should become select sum( ... ) as "Total GB" from summary Quotes around column headings are important. The "as" keyword too (in fact Paul also missed it somewhere :) Zlatko Krastev IT Consultant "Chetan H. Ravnikar" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 28.09.2002 03:12 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: Backup reporting: SUMMARY TABLE ISSUE IS FOUND I get this error running any of the select queries below. any ideas thanks == ANR2905E Unexpected SQL identifier token - 'GB'. | .V. select sum(cast(bytes/1024/1024/1024 as decimal(6,3))) Total GB == ... > > > > select sum(cast(bytes/1024/1024/1024 as decimal(6,3))) "Total GB > > Backup" from summary where start_time>=current_timestamp - 1 day and > > activity='BACKUP'
Re: TSM 5.1 license registration failed?
I have always had to copy the license files off the CD itself. Check on there for the file and see if it says 5.1. Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -Original Message- From: Dan Foster [mailto:[EMAIL PROTECTED]] Sent: Sunday, September 29, 2002 12:10 AM To: [EMAIL PROTECTED] Subject: TSM 5.1 license registration failed? I'm stumped by something (simple?) relating to TSM licensing. We've got a pretty plain vanilla TSM 5.1 setup with a 3584 tape library. No additional features purchased or in use (SAN, TDP, NMDP, etc). The 3584 requires a managed library license, as I understand it (has 12 drives and 610 tapes spanning the L32 and D32), so we paid for that license, along with the number of client nodes we wanted to use. Didn't receive any paperwork or anything special -- just TSM 5.1 CDs with all the filesets that were appropriate. So then, once I've got the 5.1 server set up... went to do: tsm> register license file=library.lic tsm> query license Now says: [...snip...] Number of Managed Libraries licensed: 1 Server License Compliance: FAILED What did I do wrong? Why did it fail? How do I fix so that I can have both 1 managed library AND server compliance = SUCCESS? The documentation is extremely sparse in this area, to put it charitably. ;) Did I install the wrong filesets for AIX 5.1 server? For the license, I have these filesets installed: # lslpp -l|grep tivoli|grep -i license tivoli.tsm.license.aix5.rte64 tivoli.tsm.license.cert5.1.0.0 COMMITTED Tivoli Storage Manager License This is for a brand new TSM 5.1 install on a brand new AIX 5.1 install. No existing nodelock file was present, nor were anything restored. The only thing I wonder about, after looking at the library.lic file is a line that says this: ProductVersion=4.2 Does that mean the license certificate file is specific only to TSM 4.2? Finally, in previous versions (ADSM 3.1, TSM 4.2, etc), I had to register an appropriate license for the number of nodes I'd paid for. But there's no client license certificate files nor anything mentioning it in the TSM 5.1 'q license', nor in the 5.1 docs...? Does that mean I continue to pay for client node licenses (I'm not here to rip anyone off!) but just simply don't need to register them with the server...? -Dan
[no subject]
-- Thanks, Matt
Re: TSM 5.1 license registration failed?
Two aspects: - instead of grep-ping why you do not use `lslpp -L tivoli.tsm\*` or `tivoli.tsm\*license\*`. In this way you can see the version of filesets and ensure there is no one left from v4.2. You may also check "reverse lookup" - `lslpp -w /usr/tivoli/tsm/server/bin/library.lic` - number of libraries licensed is one. Either you have two libraries or 3584 is partitioned and look like two libs or some other stanza is having insufficient number of registered licenses. Can you provide full output of `q lic`? Zlatko Krastev IT Consultant Dan Foster <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 29.09.2002 07:10 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:TSM 5.1 license registration failed? I'm stumped by something (simple?) relating to TSM licensing. We've got a pretty plain vanilla TSM 5.1 setup with a 3584 tape library. No additional features purchased or in use (SAN, TDP, NMDP, etc). The 3584 requires a managed library license, as I understand it (has 12 drives and 610 tapes spanning the L32 and D32), so we paid for that license, along with the number of client nodes we wanted to use. Didn't receive any paperwork or anything special -- just TSM 5.1 CDs with all the filesets that were appropriate. So then, once I've got the 5.1 server set up... went to do: tsm> register license file=library.lic tsm> query license Now says: [...snip...] Number of Managed Libraries licensed: 1 Server License Compliance: FAILED What did I do wrong? Why did it fail? How do I fix so that I can have both 1 managed library AND server compliance = SUCCESS? The documentation is extremely sparse in this area, to put it charitably. ;) Did I install the wrong filesets for AIX 5.1 server? For the license, I have these filesets installed: # lslpp -l|grep tivoli|grep -i license tivoli.tsm.license.aix5.rte64 tivoli.tsm.license.cert5.1.0.0 COMMITTED Tivoli Storage Manager License This is for a brand new TSM 5.1 install on a brand new AIX 5.1 install. No existing nodelock file was present, nor were anything restored. The only thing I wonder about, after looking at the library.lic file is a line that says this: ProductVersion=4.2 Does that mean the license certificate file is specific only to TSM 4.2? Finally, in previous versions (ADSM 3.1, TSM 4.2, etc), I had to register an appropriate license for the number of nodes I'd paid for. But there's no client license certificate files nor anything mentioning it in the TSM 5.1 'q license', nor in the 5.1 docs...? Does that mean I continue to pay for client node licenses (I'm not here to rip anyone off!) but just simply don't need to register them with the server...? -Dan
Re: Compare TSM/Legato and Veritas - Version 2
Find below what I think needs correction (for version 2.01 :). Correct me where I am wrong. Generic comment - the document is somewhat one-sided comparing which Networker features exist/do not exist in TSM, the reverse comparison which TSM features Networker does not have is weak or missing. I've tried to fill the gap partially but it needs more work. On the end table is only for Networker and TSM. To be complete and closer to the subject we still need the third column for NetBackup Terms 10: client file index - its TSM equivalent is node files' entries in BACKUPS table + DIRMC written data to pool. Definitely is not the whole DB. Terms 16: media database - TSM tables VOLUMES and As.Segments (latter is hidden and inaccessible through select queries). Again not the whole DB Terms 18+: parallelism - Networker - number of clients backing to server or number of clients writing to a volume (p.115 Admin's Guide), TSM - number of parallel sessions from one or more clients Terms 18++: reclamation - Networker - N/A, TSM - reconcile free space on a volume when is under-utilized Terms 20: save set - roughly equivalent to TSM filespace, could be either a filesystem or directory identified by virtualmountpoint Terms 21: save set consolidation - definitely is *not* "~ backupset".This is manual and post-factum consolidation performing small part of "progressive backup". If consolidated backups can be performed for *each* client and *each* save set the functionality would be somewhat similar to TSM's (otherwise good old well-known full+incremental). Consolidated backups are not done on-the-fly and are subject to too many limitations described on p.320-321 WinAG. Still far from version tracking "progressive backup" provides in TSM. Terms N+1 - no TSM terms described Platforms 13&16: Linux - ITSM on the end supports Linux, Red Hat and SuSE plus maybe others Platforms 36+: IBM NAS - TSM supports them (through integrated Windows client) Platforms 36++: IBM OS/2 - TSM does have client Platforms 48 - ADSM client can backup SunOS to TSM server (being old version is unsupported, I do not know and am interrested to know does really Legato support SunOS) Platforms 94: SAP R/3 on Oracle - TSM does not support Oracle on Compaq Tru64 and Linux, so ... maybe the cell was copied with intention for edit ,-) Functions 9+: retention - Networker - for whole save set, TSM - using management classes down to individual file/directory Functions 9++: deleted files - Networker does not have handling of deleted files (you have to find when the file was deleted), TSM completely handles versions and retension of deleted files Functions 10: archive - Networker requires additional pool (and volumes) for archives Functions 10+: archive retention - Networker - none (indefinite), TSM - based on archive copygroup settings Functions 14: cacheing of staged save sets - a TSM functionality is better to be described with neutral or TSM terms Functions 24: communication method - TSM supports also Named pipes (plus NetBIOS and IPX/SPX for old clients) Functions 28+: data streams to/from client - NetWorker - 1 (manual&static division to several client/save set backups is the only way for more), TSM - up to 10 threads/sessions (according to manual, even I was able to get more) with dynamic load-spreading for backup/archive/restore. Look Functions 40. Functions 30: devices - Networker - 4/16/32 for the server + 16/32 for each storage node (p.116 or 249 Admin's Guide, max 256 for any server+nodes combination), TSM - up to 256 per library/devclass (total is practically unlimited - in SAN a TSM library manager server can perform mounts while other servers/STAs will do writes) Functions 31+: media reclamation - Networker - none (has to wait all save sets on a volume to expire), TSM - automatic based on volume's freed (reclaimable) space. As described in Other 21 Functions 36+: parallelism - Networker - 32/64 for the server + 32 for each storage node (p.116 Admin's Guide), TSM - unlimited (p.974 in Admin Ref, GC32-0769-00, same URL with 0769) Functions 36++: parallel scheduled sessions narrowing - Networker - none, TSM - MAXSCHEDSESSIONS percentage (p.759 Admin Ref) Functions 37: password protection - Networker - manual define/change (not enabled by default), TSM - Yes (with automatic expiration/change + mail of new pass) Functions 40: multi-session parallelism - Networker - static & manual, TSM - dynamic & automatic Functions 43+: server script schedules - lack of server scripting leads to lack of need for administrative schedules Other 2: archiving on UNIX clients - TSM can retrieve single files from any archive on any platform Other 3: bootstrap, backup - the TSM database can be backed up manually, by administrative schedule and by backup trigger (p- 513). TSM DB backups can be either Full or Incrmental. Networker bootstrap is only full, isn't it. Other 7: Client, renaming - TSM is one step process for UNIX and might need more steps for Windows (filespaces have to
Baltimore/Wash DC/NoVa TSM User Group Meets Oct 17
The TSM user group for Baltimore, Washington, DC, and Northern Virginia will meet Oct 17 in Fairfax, Va. In fact, we frequently host participants from the entire mid-Atlantic area - including Maryland, Pennsylvania, & West Virginia as well. We have a terrific program planned for Oct. 17, so please join us if you can (it's free). For agenda, registration details, directions, & contact info please visit: http://www.jasi.com/TSMUG/Meeting_Information/Meetings_for_2002/meetings_for _2002.html We hope you can join us!
Re: ANR8403E DEFINE DRIVE: Operation not allowed for SHARED libraries.
Can you ping the library client from the library manager server (did the crossdefine what it ought to) ? There are not too many steps to err in. Zlatko Krastev IT Consultant Michael Donabauer <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 05.09.2002 16:20 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:ANR8403E DEFINE DRIVE: Operation not allowed for SHARED libraries. Hi * I am on AIX 4.3.3 ML 09 with TSM 5.1.1.4. The Library is an 3584 LTO Ultrium with 8 drives at the moment. Because of some special reason we need a second TSM Server on our Backupserver. On the Library Manager: We have already a working installation of the Lanless-Backup Feature. Therefore i guess that the configuration of the shared library is ok. The pathes needed should be ok too. On the Libary Client: I configured the Server step by step with the manual. 1. define server ... > ping server tsm1 > OK 2. define libary 3584LIB1 libtype=shared primarylibmanager=tsm1 > OK 3. define drive 3584LIB1 3584LIB1DRIVE1 > FAILED because of the following error. Libraryname and Drivenames are the same as on the library manager. > tsm: DCTM>define drive 3584LIB1 3584LIB1DRIVE1 > ANR8403E DEFINE DRIVE: Operation not allowed for SHARED libraries. > ANS8001I Return code 3. 4. I can't define paths because the pathdefinition need the drive configured before. Thx Mike
Re: TSM 5.1 license registration failed?
If you're doing an upgrade install to V5R1, there's a new license file on the install media which, for AIX at least is a new file, so it doesn't get pulled in with the rest. Check your install media for files called license or some such and install them all. Quoting "Seay, Paul" <[EMAIL PROTECTED]>: > I have always had to copy the license files off the CD itself. Check on > there for the file and see if it says 5.1. > > Paul D. Seay, Jr. > Technical Specialist > Naptheon Inc. > 757-688-8180 > > > -Original Message- > From: Dan Foster [mailto:[EMAIL PROTECTED]] > Sent: Sunday, September 29, 2002 12:10 AM > To: [EMAIL PROTECTED] > Subject: TSM 5.1 license registration failed? > > > I'm stumped by something (simple?) relating to TSM licensing. > > We've got a pretty plain vanilla TSM 5.1 setup with a 3584 tape library. No > additional features purchased or in use (SAN, TDP, NMDP, etc). > > The 3584 requires a managed library license, as I understand it (has 12 > drives and 610 tapes spanning the L32 and D32), so we paid for that > license, > along with the number of client nodes we wanted to use. > > Didn't receive any paperwork or anything special -- just TSM 5.1 CDs with > all the filesets that were appropriate. > > So then, once I've got the 5.1 server set up... went to do: > > tsm> register license file=library.lic > tsm> query license > > Now says: > > [...snip...] >Number of Managed Libraries licensed: 1 > Server License Compliance: FAILED > > What did I do wrong? Why did it fail? How do I fix so that I can have both > 1 > managed library AND server compliance = SUCCESS? The documentation is > extremely sparse in this area, to put it charitably. ;) > > Did I install the wrong filesets for AIX 5.1 server? For the license, I > have > these filesets installed: > > # lslpp -l|grep tivoli|grep -i license > tivoli.tsm.license.aix5.rte64 > tivoli.tsm.license.cert5.1.0.0 COMMITTED Tivoli Storage Manager > License > > This is for a brand new TSM 5.1 install on a brand new AIX 5.1 install. No > existing nodelock file was present, nor were anything restored. > > The only thing I wonder about, after looking at the library.lic file is a > line that says this: > > ProductVersion=4.2 > > Does that mean the license certificate file is specific only to TSM 4.2? > > Finally, in previous versions (ADSM 3.1, TSM 4.2, etc), I had to register > an > appropriate license for the number of nodes I'd paid for. But there's no > client license certificate files nor anything mentioning it in the TSM 5.1 > 'q license', nor in the 5.1 docs...? Does that mean I continue to pay for > client node licenses (I'm not here to rip anyone off!) but just simply > don't > need to register them with the server...? > > -Dan > Fred Johanson
