Jörg Nouvertné/FIRDU/Europe/MCKINSEY is out of the office.
I will be out of the office starting 26.09.2003 and will not return until 14.10.2003. I will respond to your message when I return. +-+ This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. +-+
Re: Move Drmedia ... Remove=BULK asks for a reply
With the option wait=yes the reply should not be necessary |+- || Ford,| || Phillip | || phillip.ford@| || SPCORP.COM | || Sent by: | || ADSM: Dist | || Stor Manager | || [EMAIL PROTECTED]| || IST.EDU | || 27.06.2003| || 14:28 | || Please respond| || to ADSM: Dist| || Stor Manager | || | |+- | | | | To: [EMAIL PROTECTED] | | cc: (bcc: Jörg Nouvertné/FIRDU/Europe/MCKINSEY) | | Subject: Re: Move Drmedia ... Remove=BULK asks for a reply | | We saw this problem also. We ended up writing an OS script that the operators start. It does the below command and then looks for one of two things. If a request is found then it replies to it. If the move drm process goes away then it stops. This has worked very good for us. But like you said the library and command do not do what the book says. -- Phillip Ford Senior Software Specialist Corporate Computer Center Schering-Plough Corp. (901) 320-4462 (901) 320-4856 FAX [EMAIL PROTECTED] -Original Message- From: Coats, Jack [mailto:[EMAIL PROTECTED] Sent: Thursday, June 26, 2003 5:13 PM To: [EMAIL PROTECTED] Subject: Re: Move Drmedia ... Remove=BULK asks for a reply I have suspected I saw it on occasion. But not well enough to document. I have a 3583, 6 LTO1 drives, 60 slots, and door with 12 slots. TSM on Win2K is 4.2.3.1 -Original Message- From: John Schneider [mailto:[EMAIL PROTECTED] Sent: Thursday, June 26, 2003 4:48 PM To: [EMAIL PROTECTED] Subject: Move Drmedia ... Remove=BULK asks for a reply Greetings, We recently installed a new TSM server on a pSeries 650 using TSM 5.1.6.5, and a 3584 Tape Library with a L32 and D32 frames with 15 LTO Gen 1 Tape drives. The library has the 10 i/o slot option. The server and library work great, except for one quirk. When we go to check out our drm media, we use: move drmedia * wherestate=mountable tostate=vault remove=bulk This performs the 'move drmedia' OK, but asks for a reply back after every tape checks out! According to the manual, a remove=bulk shouldn't require a reply, but for some reason it does on this library. The tapes do correctly get sent to the bulk loader in the library, so aside from the annoying request that gets generated, the checkout proceeds normally. We have a 3583 library, and issue the same command to it, and it doesn't ask for a reply. Has anyone seen this behavior, and know what to do to stop it? John Schneider *** * John D. Schneider Email: [EMAIL PROTECTED] * Phone: 636-492-0247 * Lowery Systems, Inc. * 1329 Horan Disclaimer: Opinions expressed here are * Fenton, MO 63026 mine and mine alone. *** * This message and any attachments are solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use or distribution of the information included in this message is prohibited -- Please immediately and permanently delete. +-+ This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. +-+
Jörg Nouvertné/FIRDU/Europe/MCKINSEY is out of the office.
I will be out of the office starting 18.06.2003 and will not return until 23.06.2003. I will respond to your message when I return. +-+ This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. +-+
Re: TSM Upgrade
On Thursday 05 April 2001 19:11, you wrote: Hi Geoff, I just received my TSM 4.1 upgrade CDs. So I'm faced with the fun of upgrading to 4.1 on my AIX system. I would love to see your document on the steps to do this properly. Thanks, Jim I did the upgrade from ADSM 3.1 to TSM 4.1.2 recently and it worked fine. But as stated in the docu, you will loose the drive devices, therefore you should have the information (via q dr and lsdev -Cc tape) handy. Jörg On Monday, February 5, 2001, at 02:07 PM, Jolley, Bill wrote: Before the upgrade, what model tape drive were you using? I currently have 3590-B11 and should I be investigating moving to an E J or K model before/during/after the upgrade. -Original Message- From: Gill, Geoffrey L. [mailto:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 1:07 PM To: [EMAIL PROTECTED] Subject: TSM Upgrade Info for all, Last Tuesday I upgraded my ADSM server running AIX 4.3.3 to TSM 4.1.2.0. For all those concerned about the upgrade I must say it was quite easy. Since I'm on AIX I can't speak for the other OS's. My 3494 did have old Atape drivers so I had to update those, and while I was at it I updated atldd drivers too. I have not had any problems, I know it's only been a week. Hopefully things will remain this way and all I'll need is some maintenance patches to fix bugs. I know we've had a lot of complaints about this, and it may well be deserved, but if you think about it nobody has a perfect product out of the box and software always has bugs...that's life I can't very well point fingers, I'm not a programmer and have enough problems just trying to learn it all I'd be glad to share a document I have with the steps I followed to anyone who'd like it. It also has some notes I made. It applies to AIX so I'm not sure if it will do others any good, I'll send it anyway if you like. Email me seperately if you'd like it. Thanks, Geoff Gill NT Systems Support Engineer SAIC Computer Systems Group E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (888) 997-9614 _/_/_/_/_/_/ Jim Jepson, LRE System Admin Networking _/_/ Apple Computer, Inc. _/_/ 3 Infinite Loop Cupertino, CA 95014 _/_/ _/_/ Direct: 408-974-6368 FAX: 408-996-3783 _/_/_/_/ _/_/_/_/MS:303-1SC, E-MAIL:
Re: Netware client problems
We had the same problem, and the solution was: TSA500 requires IPX to authenticate to the filesystem on the console. You will have the same effect with scrsaver.nlm. Trying to unlock, it will check your rights to the server object, which will fail without IPX. Regards, Jörg On Wednesday 14 March 2001 22:20, you wrote: We have the same problem with one of our Netware 5.0 servers after we upgraded the Service Pack to 6A. We applied the service pack to all 5.x boxes (about 10), however only 1 is having problems. Patrick Boutilier [EMAIL PROTECTED]@VM.MARIST.EDU on 03/14/2001 11:14:51 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Netware client problems Have you tried using a period in front of the name? eg. ..backupuser.orgunit.org Quoting Jim Kirkman [EMAIL PROTECTED]: Howdy, NW Client 4.1.1_18 talking to an ADSM 3.1.2.50 server on OS\390. I keep getting a login prompt when the scheduler kicks off, or if I run a manual. I'm using the fully qualified login name, and the pwd file has been established in two of the three instances. I type in username and password and get the error "Login denied to NewWare Target Service Agent 'blahblah'. However, the backup runs. Any ideas? It's like I'm getting access to the server and context, but not the tree. thank, -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884 Staff Sig...
Re: no delete volume because of segment references
On Monday 19 March 2001 19:56, you wrote: 03/19/01 17:24:46 ANRD asvol.c(2847): Volume 0BA40C cannot be deleted to SCRATCH - it still has SEGMENT references. We had that problem as well, and the only way to get rid of it, was to run an audit DB (must be at least ADSM 3.1.2.90). There is a switch to restrict the audit to the critical part, there is an APAR on this with detailed instructions. Search for SEGMENT at the knowledgebase. Jrg Arnaud - Have you tried a Move Data on the volume? There is some hope that it would locate the companion volume having the remainder of the file, and move both portions to a new volume. Richard Sims, BU
Re: Tape drive utilization
On Thursday 22 February 2001 05:16, you wrote: Environment is a 3466-C00 with a 3494 library and 3590-E1A drives. The symptoms are that the TSM Admin (me) just can't seem to understand that the number of tape drives being used is greater than the number of TSM processes (stg backup, stg reclaim and migration) plus the obvious number of recovers taking place. I recognize I must also consider TDP products. Is there a method to determine who/what is using tape drives??? Hi John, in certain circumstances, e.g.depending on the policy, large files might be sent direcly to tape bypassing the disk. This will occupy a tape drive with appearing in the process list. Unfortunately, I do not know any method to determine, is a session is currently using a tape drive. Regards, -- Joerg Nouvertne ... who still runs ADSM 3.1, but who will take the new adventure TSM 4.1 soon.
Re: Restore-Netware
On Thursday 22 February 2001 08:10, you wrote: Hy all, I started a restore from our AIX 4.3, TSM 3.7.4 Server to a Netware %.1 Client (TSM 3.7.2). We restored a complete Volume to a new clean Volume ( ' restore daten:* newdata:/ -subdir=all ' ). I started the restore yesterday evening to run over night. Today in the morning the netware-server stood with a message where I should say if an existing file should be overwritten ( the exact message text was answered by my college before I could see it, so I couldn't check the file/directory ). Why does TSM ask for overwriting on a complete new and empty volume ? For any explanations I thank you Christoph Hi Christoph, just a guess, do you have the same name space applied to the new volume? -- Joerg Nouvertne ... who still runs ADSM 3.1, but who will take the new adventure TSM 4.1 soon.
Re: deleting copypool tapes.
On Wednesday 14 February 2001 22:47, you wrote: I deleted one by one ..But don`t you feel that there should be a command to delete volumes by storage pool name ? Hope will get in TSM5 :- ) Thanks Shekhar . Why waiting for IBM if you can easily achieve this on your own? Write a script that collects a list of all tapes assigned to the dedicated stgpool and preform a loop with the command on that list. -- Joerg Nouvertne ... who still runs ADSM 3.1, but who will take the new adventure TSM 4.1 soon.
select to the actlog truncates message
Hi all, using the dsmadmc select command on the actlog table, I've observed the following: The message field is restricted to 250 characters (CHAR(250)), however some messages (like 8300 or 4990/4991) provide more information when querying through "query actlog". Example: 1. q actlog: 02/13/01 20:03:47 ANR8300E I/O error on library DUSLIB0 (OP=6C03, CC=314, KEY=05, ASC=3B, ASCQ=0E, SENSE=70.00.05.00.00.00.00.0C.00.00.00.00.3B.0E.00.00.00- .00.00.00., Description=The source slot or drive was empty in an attempt to move a volume). Refer to Appendix B in the 'Messages' manual for recommended action. 2. select from actlog: MESSAGE: ANR8300E I/O error on library DUSLIB0 (OP=6C03, CC=314, KEY=05,ASC=3B, ASCQ=0E,SENSE=70.00.05.00.00.00.00.0C.00.00.00.00.3B.0E.00.00.00.00.00.00- ., Description=The source slot or drive was empty in an attempt to move a volume). Refer to Appendi Question: Is the limit of 250 characters build into the select command, or is the table restricted to 250 character and the "q actlog" gets this info from somewhere else? Thanks, Jrg -- Joerg Nouvertne ... who still runs ADSM 3.1, but who will take the new adventure TSM 4.1 soon.
Re: I realy need your help
On Tuesday 13 February 2001 08:27, you wrote: Hi All I have a case in adsm 3.7 the following messages has been reported in the activity log of our adsm server ANR8302E I/O error on drive DRIVE2 (/dev/rmt2) (OP=READ, CC=0, KEY=03, ASC=11, ASCQ=00, SENSE=F0.00.03.00.04.00.0- 0.58.00.00.00.00.11.00.FE.0A.36.3A.00.30.00.03.01.91.00.- 19.31.71.ED.AD.08.00.04.33.35.00.80.33.35.40.88.33.3D.BE- ..5F.00.00.00.A5.14.00.73.ED.1F.00.00.02.FF.00.00.A5.14.0- 3.00, Description=An undetermined error has occurred). Refer to Appendix B in the 'Messages' manual for recommended action. 02/13/01 10:09:35 ANR8359E Media fault detected on 3570 volume 040126 in drive DRIVE2 (/dev/rmt2) of library 3570LIB1. please if you know ..any thing about that please help me out.. AFAIK the SCSI drive has reported an error to the ADSM server, where no corresponding translation is available. The SENSE data can be interpreted using the drive manual. Vaild SENSE data on a SCSI drive always starts with 70 and usually has a translation (Descritpion=Changer failure, etc.); every other code (like F0 in your case) does not meet the SCSI specifications and therefore reports an "undetermined error". It might be, that there was a short communication problem on the SCSI bus, however, I would contact the technical support of the vendor to get clarification. -- Joerg Nouvertne ... who still runs ADSM 3.1, but who will take the new adventure TSM 4.1 soon.
Re: TDP for Domino: Missing log information in ADSM 3.1
On Wednesday 07 February 2001 18:41, you wrote: Del, Jrg, It looks like you may have a legitimate problem here. Please open a problem with IBM/Tivoli support. I will open a call today, thanks. Thanks, Del Del Hoobler IBM Corporation [EMAIL PROTECTED] Joerg Nouvertne [EMAIL PROTECTED]@VM.MARIST.EDU on 02/06/2001 08:55:23 AM Please respond to [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: TDP for Domino: Missing log information in ADSM 3.1 Hello all, recently I've upgraded our TDP for Domino on NT to Version 1.1.1 including Testfix. As a result, the message numbers have changed from ANR4991 to ACDxxx, which works fine accept ACD5211, which is the statistic after backing up the archive logs; the statistics are missing and they are looking like this: 02/05/01 22:01:43 ANE4990I (Session: 8696, Node: EU-BACKUP01) TDP Domino NT ACD5211 Transaction log archive from server EU-BACKUP01 complete Have you experienced a similar problem? Will this work with TSM 4.1 (we'll upgrade soon)? Kind regards, Jrg -- Joerg Nouvertne ... who still runs ADSM 3.1, but who will take the new adventure TSM 4.1 soon.
Re: Novell DS issue?
On Tuesday 06 February 2001 16:22, you wrote: Greetings, We've got a Netware 5.1 server that's been a real problem child. The Netware Admin is curious if anyone is aware of problems with ADSM and version 7.44 of the Netware DS. This is evidently an older version of DS and he wants some evidence to back up his theory. [snipp] Could you please be a little bit more specific about the problem? We are running TSM 4.1 clients on NetWare 5.0 SP4 and SP6a with some minor issues. - Never use "unload dsmc" on the console. In most cases the server will abend. - Long filenames are not displayed for a restore. This make it sometimes hard to determine the right files. Beside that, everything works fine so far. Regards,
Volume has still SEGMENT references
Hi *SMers, I experience a strange behaviour with 2 tapes. After reclaiming all the data, they cannot be deleted from the storage pool. The following error is reported: 02/07/01 09:24:03 ANR2017I Administrator DUJNOUVE issued command:UPDATE VOLUME 17 access=unav 02/07/01 09:24:03 ANRD asvol.c(2733): Volume 17 cannot be deleted to SCRATCH - it still has SEGMENT references. 02/07/01 09:24:03 ANRD asvol.c(1626): Unknown result code (267) while deleting a volume. 02/07/01 09:24:03 ANR2032E UPDATE VOLUME: Command failed - internal server error detected. 02/07/01 09:24:03 ANR2017I Administrator DUJNOUVE issued command: ROLLBACK Since both are marked as "offsite" and an "update vol xxx access=readw" returns the same error, I cannot run an "audit vol" on it. Any ideas? Many thanks in advanced. -- Joerg Nouvertne ... who still runs ADSM 3.1, but who will take the new adventure TSM 4.1 soon.
Re: libstdc++-libc6.1-1.so.2 dependency in RedHat7.0 ?
On Wednesday 07 February 2001 11:54, you wrote: Sorry if this is off topic or already been answeared, but I couldn't access http://vm.marist.edu/htbin/adsm-l.html to search for it. The Tivoli 4.1 client won't run on a RedHat 7.0 based system with the error: dsmc: error while loading shared libraries: libstdc++-libc6.1-1.so.2: cannot open shared object file: No such file or directory ^^ This indicates, that the library running on your system has been found, but does not contain the expected object file. I know that RedHat 7.0 has a special version of the glibc and gcc installed, which is not binary compatible to non-RedHat binaries. Is this client compiled for RedHat 7.0? [cut off librarylist] So I thought the asked libary is already there. Michael Jung Kind regards, -- Joerg Nouvertne ... who still runs ADSM 3.1, but who will take the new adventure TSM 4.1 soon.
Re: Migration did not occur
On Wednesday 07 February 2001 11:00, you wrote: Hello ADSM co-workers Hello Neil, I am running ADSM 3.1.2.2 on a NSM C00. We have a disk storage pool called INCDISK with the high threshold set to 70 and the low set to 30. Our main clients are SQL servers. All clients backup to the SQLFLAT backup copy group which is tied to the INCDISK storage pool. The INCDISK storage pool will migrate to the INCTAPE storage pool when necessary. The issue that I have observed is that when the %utilised went over the 70% high threshold then migration did not kick in. I waited until the %utilised reached 92% and still migration did not occur. Query mount showed all drives had tapes mounted, but when I queried the activity log to try and understand what had mounted these volumes I could not come to and solid conclusion. What is the activity log telling you? Maybe you should lower the HI migration threshold to force migration and have a look to the actlog afterwards. Possible reasons why the migration does not kick in are e.g. Not enough scratch tapes available in the destination pool, no migration pool at all, etc. However I do suspect that restore operations where the culprit. This was further backed up by entries informing me that earlier migration processes had been pre-empted. I eventually dismounted the volumes half expecting migration to kick in, but it didn't. Even if all tape drives are in use by other processes, migration should kick in, but would wait for a mount device, and you should see it in the process list. I eventually got migration to work by lowering both thresholds to 0. This would force it. You can also move the data manually via "move data DISKPOOL stgpool=MIGRATIONPOOL wait=no". What I am not too sure about is whether migration is actually pre-empted by a restore operation. If this is the case then surly this is wrong. Surely migration is more important as this is the safety valve before the storage pool reaches 100%. Does anybody know the order of precedence for pre-emption? Can anybody confirm or add to me conclusions. Thanks for your time. Neil Sharp Merrill Lynch ADSM/TSM Administrator Work : 020-7573-0469 Mobile : 07769-741612 Pager : 01893-038277 e-mail : [EMAIL PROTECTED] Regards -- Joerg Nouvertne ... who still runs ADSM 3.1, but who will take the new adventure TSM 4.1 soon.
TDP for Domino: Missing log information in ADSM 3.1
Hello all, recently I've upgraded our TDP for Domino on NT to Version 1.1.1 including Testfix. As a result, the message numbers have changed from ANR4991 to ACDxxx, which works fine accept ACD5211, which is the statistic after backing up the archive logs; the statistics are missing and they are looking like this: 02/05/01 22:01:43 ANE4990I (Session: 8696, Node: EU-BACKUP01) TDP Domino NT ACD5211 Transaction log archive from server EU-BACKUP01 complete Have you experienced a similar problem? Will this work with TSM 4.1 (we'll upgrade soon)? Kind regards, Jrg
Re: Copypools for disks
On Tuesday 16 January 2001 21:57, you wrote: I'm nearly ready to activate DRM on a new server, but I have a worry about copypools for disk storage. One of the diskpools is for smaller servers which migrate to a limited number of collocated tapes. This pool is not yet very active, so there are many nodes which have not yet migrated off to tape. I have the time and resources to copy my diskpools to tape daily, but I wonder what sort of confusion I may be generating. For instance, what happens to cached files that are on tape as well as disk? Do I get two copies? or only the one that already exists from the backup of the tape? No, from a logical standpoint, each file exists only twice: The "original" in the primary storage pool, and a copy in the corresponding copy pool. A user does not have to care about the underlying storage media. The cached files are only another "pointer" for the file in the primary storage pool. What happens to a file that migrates to tape some time after a copy is made from disk? does it supercede the previous copy? or are there again two copies in the copypool? A file migrated from tape is the same file in the primary storage pool, and therfore it will not be copied again if a copy already exists. What happens in case of disaster requiring a restore storage operation? At this point, I really don't know what to expect All assistance will be gratefully accepted. --- Joerg Nouvertne .. who will leave the good old ADSM area shortly to take the new adventure TSM.
Re: ADSM
On Wednesday 17 January 2001 11:29, you wrote: Hello. I'm running ADSM Server on Unix Server and backing up NT server with ADSM Client 3.7.2.16. In the NT server we need to install one service named "ADSM Scheduler" . The problem is that the service "ADSM Scheduler " don't run and it gives the following error of NT: Error 1067: The process terminated unexpectedly How can I resovle it? I would remove the existing service via "dsmcutil remove /name:"ADSM Scheduler" and reinstall it again via "dsmcutil inst /name:...". Make sure to have no typo in the corresponding command. Thanks in advance. Francisco Javier Muqoz Soluziona Outsourcing e-mail:[EMAIL PROTECTED]
Re: Howto resolve ANR2362E without rebooting the server?
On Monday 15 January 2001 20:45, you wrote: If you are getting compressed log records then the utilization of your recovery log is not caused by missing data base backups. Data base backups are only needed to release log space when the log is in rollforward mode and log compression only occurs when the log is in normal mode. [snipp] Hi David, your explanation is very useful to understand how this works, and I will try your suggestion the next time we experience this. But I still do not understand the relation between the recovery log (in normal mode) and the database backup. After performing a DB BA, the recovery log will be reset, but sometimes it is reset automatically during the normal operation. How does this work? Thanks in advanced.
Re: Archiving
On Tuesday 16 January 2001 09:00, you wrote: Hy everyone, we are discussing the possibilities of archiving data with TSM or other products (from NT,UNIX). Our requirements are to archive data for about 30 years. TSM is in I don't know if this has changed with TSM. In ADSM 3.1, the maximum archive period is days (~25 years) discussion because we use it already for backup ( and in some cases we use the archive-command ). The policy domains for the clients for archiving will be (from my point of view) totally different to those for backup. We have different archive management classes (policies) for different timeframes (1year, 5years,etc) and choose the appropriate for the archives. Can anybody share his good (or bad) experience in long term archiving with whatever kind of library in the background (DVD or tape). Regarding tape technilogy, we are running a script that moves the data from any volume which has not been accessed for a longer period (e.g 1year). This make sure, that the data is readable even after 10 years. Thanks a lot Christoph
Howto resolve ANR2362E without rebooting the server?
Hi all, due to missing DB backups, our recovery log exeeded 95%. As a result, some records of the log got compressed, which prevent a DB backup to occur. The process stops with the following error: ANR2362E command: DATABASE BACKUP IS NOT CURRENTLY POSSIBLE - COMPRESSED LOG RECORDS EXIST IN THE CURRENT TRANSACTION CHECKPOINT. Regarding the help, I should issue the command at a later time, however I was waiting for hours, and had to increase the log to prevent the server from crashing; but the only way to perform a DB backup was: Rebooting the server: Does anybody know a way to force the backup, or may be a way to "uncompress" the compressed part after adding some space to the log? We are (still) using ADSM 3.1.2.20 on AIX 4.2.1.0. Thanks in advanced.
