Re: cloptset broken for Windows 4.1.2.X client
On Tue, Apr 10, 2001 at 09:02:13AM -0400, Kleynerman, Arthur wrote: > Suad, did you specify force=yes (to override the options in the dsm.opt > file)? > > For example: > > def clientopt opt_set 'Exclude ' seq=0 force=yes Aaarrggghh ... found out what the story is. When I actually demonstrated the 4.1 "daylight savings bug-fix" client install for a desktop (desktops get the "only backup the documents directory" Cloptset), I noticed a whole bunch of files in \winnt and \program files were getting backed-up. I kept quitting the incremental thinking the program ignored the exclude directives. The old 3.7 client was an obediant little surf and did what I told it to do. It didn't occur to me they were the system-files part of the "System Object". Cheers, Suad -- (off to the pub to sedate my remaining sane braincells)
Re: AIX Gurus.. .Help Needed..
Hi George in 4.3.2 you can use the 2.2.32.7 version. 2.2.33.x needs 4.3.3 for your OS. > -Message d'origine- > De : George Lesho [mailto:[EMAIL PROTECTED]] > Envoyé : mardi 10 avril 2001 21:43 > À : [EMAIL PROTECTED] > Objet : Re: AIX Gurus.. .Help Needed.. > > > Shawn, This is not as simple as it sounds, I am at 4.3.2 > maint level 0 and > require two maint level upgrades to be able to install the > new perfagent.tools > fileset. We will be going to 4.3.3 soon on all our boxes and > the one we are > testing currently is at 4.3.3 -07 and svmon works great > there. Will probably > just hang in there until I get the O/S upgraded to avoid > having to fumble > through a change control process to upgrade 4.3.2 when 4.3.3 > has already been > approved. Thanks > > George Lesho > Storage/System Admin > AFC Enterprises > > > > > > > Shawn Raymond <[EMAIL PROTECTED]> on 04/10/2001 07:46:03 AM > > Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > cc:(bcc: George Lesho/Partners/AFC) > Fax to: > Subject: Re: AIX Gurus.. .Help Needed.. > > > > > > Update your perfagent.tools to 2.2.33.50. svmon was broken > in the previous > few releases. > > -- > Shawn Raymond > Sr. Technical Consultant > Synergy, Inc. > 518-782-3457 > > > > Shekhar > DhotreTo: > [EMAIL PROTECTED] > BAYER.COM>Subject: > Re: AIX Gurus.. .Help > Needed.. > Sent by: "ADSM: > Dist Stor Manager" > <[EMAIL PROTECTED] > EDU> > > > 04/09/01 04:53 PM > Please respond to > "ADSM: Dist Stor > Manager" > > > > > > > > > I am trying to execute svmon but , getting following > error ..any idea ? > > medrs2:ps -aef | grep dsmserv > root 42134 1 0 Apr 02 - 2474:14 dsmserv > root 48518 47810 1 16:36:56 pts/10 0:00 grep dsmserv > > > medrs2:sh /usr/bin/svmon -P 42134 > sh: /usr/bin/svmon: 0403-006 Execute permission denied. > > medrs2:id > uid=0(root) gid=0(system) > groups=2(bin),3(sys),7(security),8(cron),10(audit) > medrs2: > > > medrs2:svmon > open: No such file or directory > > medrs2:/usr/bin/svmon > open: No such file or directory > > medrs2:cd /usr/bin > > medrs2:./svmon > open: No such file or directory > > medrs2:sh svmon > sh: svmon: 0403-006 Execute permission denied. > > medrs2:echo $PATH > /usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin > > Thanks > shekhar .. > > > > > George Lesho <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 04/09/2001 > 03:19:45 PM > > Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > > To: [EMAIL PROTECTED] > cc: > > Subject: Re: AIX Gurus.. .Help Needed.. > > > Herve, Where am going wrong here??? > > # ps -aef | grep dsmserv > root 30300 34772 0 Apr 07 - 606:00 dsmserv quiet > # svmon -P 30300 > > Pid Command Inuse Pin > Pgspace > 64-bit > 30300*** process does not exist *** > > Drop me a note off line and help me out... I am not sure why > it is coming > back > and > saying that my TSM server is not running thanks- > > George Lesho > Storage/System Admin > AFC Enterprises > > > > > > > > "Chibois, Herve" <[EMAIL PROTECTED]> on 04/06/2001 10:23:05 AM > > Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > cc:(bcc: George Lesho/Partners/AFC) > Fax to: > Subject: Re: AIX Gurus.. .Help Needed.. > > > > Hi Richard, > > to know exactly how many RAM TSM is eating, try the following : > > % ps -eaf | grep dsmserv --> GET PID > % svmon -P > >--- physical RAM pages (4Ko) ---+ >v > Pid CommandInusePin > Pgspace > 11638 dsmserv.4255741 16 >37293 >| > Pid: 11638+> 217 MB > Command: dsmserv.42 > > Segid Type Description InusePin Pgspace Address Range > 1ba6 pers /dev/hd3:93 0 00 0..0 > 7a1 pers /dev/hd3:88 0 00 0..0 > ... > > Hope this helps > rv > > > > -Message d'origine- > > De : Dearman, Richard [mailto:[EMAIL PROTECTED]] > > Envoy > >
Re: Error in Backupset Expiration
Ahhh but notice this little problem I've tried everything to get the volume free'd up, I've deleted everything I can... but the little bugger just hangs in there... tsm: TSMSRV07>q backupset ANR2034E QUERY BACKUPSET: No match found using this criteria. ANS8001I Return code 11. tsm: TSMSRV07>q volhist t=backupset Date/Time: 03/22/00 12:23:29 Volume Type: BACKUPSET Backup Series: Backup Operation: Volume Seq: 1 Device Class: 3590DEVC Volume Name: AAF002 Volume Location: Command: generate backupset ggmaix test devc=3590devc tsm: TSMSRV07>q libvol * aaf002 Library Name Volume Name Status OwnerLast UseHome Element --- -- -- - TSM3494LIB7AAF002Private tsm: TSMSRV07> tsm: TSMSRV07>q node ggmaix ANR2034E QUERY NODE: No match found using this criteria. ANS8001I Return code 11. tsm: TSMSRV07> tsm: TSMSRV07>q vol aaf002 ANR2034E QUERY VOLUME: No match found using this criteria. ANS8001I Return code 11. tsm: TSMSRV07> tsm: TSMSRV07>del backupset ggmaix test begind=- endd=today ANR2034E DELETE BACKUPSET: No match found using this criteria. ANS8001I Return code 11. tsm: TSMSRV07>del backupset * * begind=-999 endd=today ANR2034E DELETE BACKUPSET: No match found using this criteria. ANS8001I Return code 11. tsm: TSMSRV07>del volhist t=all tod=-5 Do you wish to proceed? (Yes/No) y ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were successfully deleted. (I already did this yesterday) tsm: TSMSRV07>q volhist t=backupset Date/Time: 03/22/00 12:23:29 Volume Type: BACKUPSET Backup Series: Backup Operation: Volume Seq: 1 Device Class: 3590DEVC Volume Name: AAF002 Volume Location: Command: generate backupset ggmaix test devc=3590devc tsm: TSMSRV07> -Original Message- From: Mark Stapleton [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 10, 2001 11:14 PM To: [EMAIL PROTECTED] Subject: Re: Error in Backupset Expiration "Cook, Dwight E" wrote: > Oh, this is a HOOT ! > you may do a "q volhist t=backupset" > but you may NOT do a "del volhist t=backupset ..." > you can see'em but you can't delete'em ! > (unless you purge everything...) It's not quite a big a HOOT! as you might think. DEL BACKUPSET BEGIND= ENDDATE=-14 (If you want to keep 14 days' worth of backupsets.) -- Mark Stapleton ([EMAIL PROTECTED])
Re: Error in Backupset Expiration
When deleting VOLHIST for database backups, you can never delete the most current version using DEL VOLHIST and the database backup volumes will NOT show up when doing a Q VOL. Is perhaps the same sort of thing taking place here? Al Alan Davenport Selective Insurance [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: > > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Date: Wed, 11 Apr 2001 06:50:55 -0500 > Subject: Re: Error in Backupset Expiration > > Ahhh but notice this little problem > I've tried everything to get the volume free'd up, I've deleted everything I > can... > but the little bugger just hangs in there... > tsm: TSMSRV07>q backupset > ANR2034E QUERY BACKUPSET: No match found using this criteria. > ANS8001I Return code 11. > > tsm: TSMSRV07>q volhist t=backupset > >Date/Time: 03/22/00 12:23:29 > Volume Type: BACKUPSET >Backup Series: > Backup Operation: > Volume Seq: 1 > Device Class: 3590DEVC > Volume Name: AAF002 > Volume Location: > Command: generate backupset ggmaix test devc=3590devc > > tsm: TSMSRV07>q libvol * aaf002 > > Library Name Volume Name Status OwnerLast UseHome > Element > --- -- -- - > > TSM3494LIB7AAF002Private > > tsm: TSMSRV07> > tsm: TSMSRV07>q node ggmaix > ANR2034E QUERY NODE: No match found using this criteria. > ANS8001I Return code 11. > > tsm: TSMSRV07> > tsm: TSMSRV07>q vol aaf002 > ANR2034E QUERY VOLUME: No match found using this criteria. > ANS8001I Return code 11. > > tsm: TSMSRV07> > tsm: TSMSRV07>del backupset ggmaix test begind=- endd=today > ANR2034E DELETE BACKUPSET: No match found using this criteria. > ANS8001I Return code 11. > > tsm: TSMSRV07>del backupset * * begind=-999 endd=today > ANR2034E DELETE BACKUPSET: No match found using this criteria. > ANS8001I Return code 11. > > tsm: TSMSRV07>del volhist t=all tod=-5 > > Do you wish to proceed? (Yes/No) y > ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were > successfully deleted. (I already did this yesterday) > > tsm: TSMSRV07>q volhist t=backupset > >Date/Time: 03/22/00 12:23:29 > Volume Type: BACKUPSET >Backup Series: > Backup Operation: > Volume Seq: 1 > Device Class: 3590DEVC > Volume Name: AAF002 > Volume Location: > Command: generate backupset ggmaix test devc=3590devc > > tsm: TSMSRV07> > > -Original Message- > From: Mark Stapleton [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 10, 2001 11:14 PM > To: [EMAIL PROTECTED] > Subject: Re: Error in Backupset Expiration > > "Cook, Dwight E" wrote: > > Oh, this is a HOOT ! > > you may do a "q volhist t=backupset" > > but you may NOT do a "del volhist t=backupset ..." > > you can see'em but you can't delete'em ! > > (unless you purge everything...) > > It's not quite a big a HOOT! as you might think. > > DEL BACKUPSET BEGIND= ENDDATE=-14 > > (If you want to keep 14 days' worth of backupsets.) > > -- > Mark Stapleton ([EMAIL PROTECTED])
Re: Windows Client Support of LTO drives
Mark, I was testing HP's Ultrium 230 External tape drive on a Compaq Proliant server. The local OS recognized the drive and I could do a local backup and restore using NT Backup (Just testing of course!). We have another single external IBM LTO connected to our TSM server (AIX). What I wanted was the ability to create a backset at the server to the locally attached LTO drive. Then I could take this portable media to an NT server with a locally attached LTO drive and using the TSM Windows client perform a restore from the Locally attached LTO drive. But appears that the new LTO drives are not a supported Tape device for performing this task, here is an excerpt from the 4.1.2.12 docs. The backup set is usually stored on media like tape, CD-ROMs, JAZ disks, or ZIP disks. These tape devices are supported: DLT, 4mm, 8mm, 3590, and 3570. Bruce E. Lowrie Sr. Systems Analyst Global Information Technology Services Storage, Output, Legacy *E-Mail: [EMAIL PROTECTED] *Voice: ?(517) 496-6404 *Post:Mail: CO2111, (DC2 1st Floor) -Original Message- From: Mark Stapleton [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 11, 2001 12:01 AM To: [EMAIL PROTECTED] Subject: Re: Windows Client Support of LTO drives Bruce Lowrie wrote: >Yes I know the SERVER supports it but I am not finding any support for the >Windows client. This way I could use an external drive to do Backup Set >restores. > >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] >>Yes, it should , I have a LTO 3580 on my W2K advance server with TSM 4.1.2 > . > >>From: Bruce Lowrie [mailto:[EMAIL PROTECTED]] >>>Does anyone have any information on when the Windows Client will support >>>local LTO drives to perform Backup set restores? I was hoping that 4.1.2.12 >>>had it but it does not The TSM Windows client doesn't have to talk to the LTO drive. When you attempt to run a restore from a backupset accessed from a locally-attached drive, the client talks to the LTO drive through the OS. You need to look at the tape driver's documentation to get details about compatibility with W2K. -- Mark Stapleton ([EMAIL PROTECTED]) _ This message has been checked for all known viruses by the MessageLabs Virus Control Centre. For further information visit http://www.messagelabs.com/stats.asp _ This message has been checked for all known viruses by the MessageLabs Virus Control Centre. For further information visit http://www.messagelabs.com/stats.asp
Exclude List for NT 4.0
Just finished upgrading to AIX 4.1.2 Server & on my NT servers I am having a problem with excludes that used to work on 3.1. I am using client version 4.1.2 These are the 2 files on one of my servers but this is happening on a lot them. I am also using a client option set. Here are the options I have defined: Exclude *:\WINNT\system32\asat0*.tmp Exclude *:\apps\mrswin\DB\Mrs.log Here are the errors: 04/10/01 13:18:40 ANE4987E (Session: 892, Node: CANCERDATA_NT40) Error processing '\\cancerdata_nt40\d$\apps\mrswin\DB \MRS.LOG': the object is in use by another process 04/10/01 13:19:10 ANE4987E (Session: 892, Node: CANCERDATA_NT40) Error processing '\\cancerdata_nt40\c$\WINNT\system32 \asat0004.tmp': the object is in use by another process I set these up manually & also using the setup wizard through the backup client. Tried using with & with out quotes. Tried using *:\winnt & D:\winnt. All producing the same results. -- Bruce Kamp Network Analyst II Memorial Healthcare System P: (954)987-2020 x4542 F: (954)985-1404 E: [EMAIL PROTECTED]
Re: ADSM database backup to a file.
Hi , Can I also create this 'flatfile' on a AIX system ( server-a ) and restore the server on a Solaris system ( server-b ) ? I would like to use this solaris-adsm/tsm- server only for a quick restore of data previously backed up on server-a which uses copy-Storagepools via server-server on a third system- (server-c) and I don't want to use this solaris system for backup, because it only has disks and no library ... someone using such a configuration -or is this quite anomalous ? ( Szenario : server-a and Clients from this server-a (with 'client-data-copys-send-to-server-c' ) are completely destroyed - then trying to restore latest active backups for the Clients as fast as possible on server-b using just the copy from server-c ) Thanks in advance for any hints ! Rainer "Cook, Dwight E" wrote: > > Sure, to move an adsm environment across town where I was a few states away > and didn't want to fly in for a half day... > define a device class of "FILE" and use it to backup the DB. > I did a full, then FTP'ed it over to a new machine that was to become the > server... as soon as I got the full FTP'ed over I did a restore with > commit=no, then I locked out clients, did an incremental, FTP'ed that one > over, did a restore with commit=yes and started up TSM. (while I was doing > that the DNS folks were doing there thing, then the clients just had to > bounce their schedulers...) > >>-DEFine DEVclass--device_class_nameDEVType--=--FILE---> > > .-MOUNTLimit--=--1. > >-+-+---> > '-MOUNTLimit--=--mountlimitvalue--' > > .-MAXCAPacity--=--4M. > >-+---+-> > '-MAXCAPacity--=--size--' > > .-DIRectory--=--current_directory_name--. > >-+---+>< > '-DIRectory--=--directory_name--' > > so something like > def devc FLATFILE devt=file maxcap=4096M dir=/usr/adsm/flatfile > then just use it like > backup db t=f s=y dev=flatfile > and it will create a file in /usr/adsm/flatfile > to automatically get rid of the file in that directory, do like you would > normally... del volhist t=dbb tod=-x and any db backup files in > /usr/adsm/flatfile older than "x" will be deleted... > > Dwight > > -Original Message- > From: Zosimo Noriega (ADNOC IS&T) [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 10, 2001 1:10 AM > To: [EMAIL PROTECTED] > Subject: ADSM database backup to a file. > > Hi everyone, > Can i backup my adsm db into a file because i usually backed up into tapes > using the devclass. > if possible, please provide the commands or steps how to do it and how to > restore it. > > thanks, > zosi -- Mit freundlichen Grüßen / best regards Rainer Wolf __ Rainer Wolf [EMAIL PROTECTED] Tel: 0731-50-22482 Fax: 0731-50-22471 University of Ulmhttp://www.uni-ulm.de/urz University Computing Center Albert-Einstein-Allee 11 AG Basissysteme 89069 Ulm
very few tapes expiring
Hello all, I am running TSM 4.1.3 (just upgraded from 4.1.1) on OS390 2.7. We have been up and running for about 5 months now and the tape people (who initially said tapes were returning from offsite) have told me that not to many tapes return from offsite. So I start looking at things. We have NETWARE, NT, AIX, SUN UNIX, DB2, SQL, ORACLE, and MS-EXchange servers + 100 desktops. I see that I have a lot of tapes that are still in use all the way back to when we were just testing things out 5 months ago. I can also see that the expiration process is running daily ( and not to the 3 hr limit). I can see that the tapes all have various amounts of reclaimable % of space on them, some all the way to 100%, but even though I see this from running Q VOL xx that when I run Q CONTENT x COUNT=100 that there are some files there. I know that the copygroups have been changed around, but they always had either VERSIONS DATA EXISTS < 45 or RETAIN EXTRA VERSIONS < 45. RETAIN ONLY VERSION is 60, everywhere. I know that I update the copy groups and activate the policysets every weekend to change the COPYMODE to/from ABSOLUTE/INCREMENTAL to force weekend fulls. (this shouldn't matter?) I see some NETWARE, AIX, DB2 files on these tapes that are 4 months old. I am at a loss as to what is wrong or what I am to new to know. Anybody have an idea as to where I should look or what I am not doing? many thanks Matt
Re: SV: DSMSERV UNLOADDB on S/390 running TSM 4.1.3
Is anyone else on the the list getting this message sent to them over and over? "Nilsson Niklas" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 04/10/2001 08:17:15 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: SV: DSMSERV UNLOADDB on S/390 running TSM 4.1.3 Hi! I did test both these parameters scratch=yes/no I have also tested 1-10 mount points.. One of the run i also specified 3 volumes (scratchtapes) but i got the same error... Here is my jcl: //TSM JOB MSGLEVEL=(1,1),REGION=128M,TIME=1440,CLASS=A,MSGCLASS=H //SERVER EXEC PGM=ANRSERV,DYNAMNBR=300,TIME=NOLIMIT, // PARM='/UNLOADDB DEVCLASS=KASS SCRATCH=YES' //OPT DD DSN=TSM.ANRSERV.OPTIONS,DISP=MOD //STEPLIB DD DSN=TSM.V41.LINKLIB,DISP=SHR //DSMAMENG DD DSN=TSM.V41.SANRMSG(ANRMENU),DISP=SHR //HLPAMENG DD DSN=TSM.V41.SANRHLP(ANRHENU),DISP=SHR //IMAGES DD DSN=TSM.V41.SANRIMG(WEBSERV2),DISP=SHR //IDL DD DSN=TSM.V41.SANRIMG(ANRIDL),DISP=SHR //DSK DD DSN=TSM.DISKLOG,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSTERM DD SYSOUT=* /* -Ursprungligt meddelande- Från: Chibois, Herve [mailto:[EMAIL PROTECTED]] Skickat: den 10 april 2001 14:16 Till: [EMAIL PROTECTED] Ämne: Re: DSMSERV UNLOADDB on S/390 running TSM 4.1.3 Hi Niklas, give me the command you typed for unloading your DB. Normally, if you specify scratch=yes, either with a tape devc or a file one, TSM will allocate one volume, then another... $ dsmserv unloaddb devc=DLTCLASS scratch=YES check how many mount points are available at the same time in your devc sned me your log offline if you want rv > -Message d'origine- > De : Nilsson Niklas [mailto:[EMAIL PROTECTED]] > Envoyé : mardi 10 avril 2001 11:22 > À : [EMAIL PROTECTED] > Objet : DSMSERV UNLOADDB on S/390 running TSM 4.1.3 > > > Hi! > > Has anybody had problem doing a unloaddb on an S/390 system > running 4.1.3??? > We are trying to do a unload to tape but when the tape get > full, the TSM > don't mount next tape. > Tried to do this to 3390-disc but got the same problem , when > the disc get > full , "he" unmounts > the disc but never mounts the next one. > There is no problem if you do an export to a deviceclass=file > or tape when > server is up and running. > > Regards > Niklas >
Re: very few tapes expiring
> Hello, do you mean tapes for copy stgp ? Do you run Reclamations ? > > René Lambelet > Nestec S.A. / Informatique du Centre > 55, av. Nestlé CH-1800 Vevey (Switzerland) > *+41'21'924'35'43 7+41'21'924'28'88 * K4-117 > email [EMAIL PROTECTED] > Visit our site: http://www.nestle.com > > This message is intended only for the use of the addressee and > may contain information that is privileged and confidential. > > > > -Original Message- > From: MC Matt Cooper (2838) [SMTP:[EMAIL PROTECTED]] > Sent: Wednesday, 11. April 2001 16:03 > To: [EMAIL PROTECTED] > Subject:very few tapes expiring > > Hello all, > I am running TSM 4.1.3 (just upgraded from 4.1.1) on OS390 > 2.7. We > have been up and running for about 5 months now and the tape people > (who > initially said tapes were returning from offsite) have told me that > not to > many tapes return from offsite. So I start looking at things. We > have > NETWARE, NT, AIX, SUN UNIX, DB2, SQL, ORACLE, and MS-EXchange > servers + 100 > desktops. >I see that I have a lot of tapes that are still in use all the way > back to > when we were just testing things out 5 months ago. >I can also see that the expiration process is running daily ( and > not to > the 3 hr limit). >I can see that the tapes all have various amounts of reclaimable % > of space > on them, some all the way to 100%, but even though I see this from > running > Q VOL xx that when I run Q CONTENT x COUNT=100 that there > are some > files there. > I know that the copygroups have been changed around, but they > always had > either VERSIONS DATA EXISTS < 45 or RETAIN EXTRA VERSIONS < 45. > RETAIN > ONLY VERSION is 60, everywhere. > I know that I update the copy groups and activate the policysets > every > weekend to change the COPYMODE to/from ABSOLUTE/INCREMENTAL to force > weekend > fulls. (this shouldn't matter?) > I see some NETWARE, AIX, DB2 files on these tapes that are 4 months > old. > I am at a loss as to what is wrong or what I am to new to know. > Anybody > have an idea as to where I should look or what I am not doing? > many thanks > Matt
Re: very few tapes expiring
Hello, do you mean tapes for copy stgp ? Do you run Reclamations ? René Lambelet Nestec S.A. / Informatique du Centre 55, av. Nestlé CH-1800 Vevey (Switzerland) *+41'21'924'35'43 7+41'21'924'28'88 * K4-117 email [EMAIL PROTECTED] Visit our site: http://www.nestle.com This message is intended only for the use of the addressee and may contain information that is privileged and confidential. > -Original Message- > From: MC Matt Cooper (2838) [SMTP:[EMAIL PROTECTED]] > Sent: Wednesday, 11. April 2001 16:03 > To: [EMAIL PROTECTED] > Subject: very few tapes expiring > > Hello all, > I am running TSM 4.1.3 (just upgraded from 4.1.1) on OS390 2.7. > We > have been up and running for about 5 months now and the tape people (who > initially said tapes were returning from offsite) have told me that not to > many tapes return from offsite. So I start looking at things. We have > NETWARE, NT, AIX, SUN UNIX, DB2, SQL, ORACLE, and MS-EXchange servers + > 100 > desktops. > I see that I have a lot of tapes that are still in use all the way back > to > when we were just testing things out 5 months ago. > I can also see that the expiration process is running daily ( and not to > the 3 hr limit). > I can see that the tapes all have various amounts of reclaimable % of > space > on them, some all the way to 100%, but even though I see this from > running > Q VOL xx that when I run Q CONTENT x COUNT=100 that there are some > files there. > I know that the copygroups have been changed around, but they always had > either VERSIONS DATA EXISTS < 45 or RETAIN EXTRA VERSIONS < 45. RETAIN > ONLY VERSION is 60, everywhere. > I know that I update the copy groups and activate the policysets every > weekend to change the COPYMODE to/from ABSOLUTE/INCREMENTAL to force > weekend > fulls. (this shouldn't matter?) > I see some NETWARE, AIX, DB2 files on these tapes that are 4 months old. > I am at a loss as to what is wrong or what I am to new to know. Anybody > have an idea as to where I should look or what I am not doing? > many thanks > Matt
Re: very few tapes expiring
Are you running reclamation? Try "upd stgp xxx recl=95". (long-term, use 60, not 95, but for now, that will tell TSM to copy-and-reclaim only tapes 5% used or less - much faster than copying a tape that's 40% used.) You should see a reclamation process kick off within a minute - it'll want two tape drives. You should do this on your copypool (ie your offsite pool) as well as your on-site tape pool, but do the on-site pool first if you're low on tapes - it'll be faster than waiting for the vault peple to send 'em back... Good luck.. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of MC Matt Cooper (2838) Sent: Wednesday, April 11, 2001 10:03 AM To: [EMAIL PROTECTED] Subject: very few tapes expiring Hello all, I am running TSM 4.1.3 (just upgraded from 4.1.1) on OS390 2.7. We have been up and running for about 5 months now and the tape people (who initially said tapes were returning from offsite) have told me that not to many tapes return from offsite. So I start looking at things. We have NETWARE, NT, AIX, SUN UNIX, DB2, SQL, ORACLE, and MS-EXchange servers + 100 desktops. I see that I have a lot of tapes that are still in use all the way back to when we were just testing things out 5 months ago. I can also see that the expiration process is running daily ( and not to the 3 hr limit). I can see that the tapes all have various amounts of reclaimable % of space on them, some all the way to 100%, but even though I see this from running Q VOL xx that when I run Q CONTENT x COUNT=100 that there are some files there. I know that the copygroups have been changed around, but they always had either VERSIONS DATA EXISTS < 45 or RETAIN EXTRA VERSIONS < 45. RETAIN ONLY VERSION is 60, everywhere. I know that I update the copy groups and activate the policysets every weekend to change the COPYMODE to/from ABSOLUTE/INCREMENTAL to force weekend fulls. (this shouldn't matter?) I see some NETWARE, AIX, DB2 files on these tapes that are 4 months old. I am at a loss as to what is wrong or what I am to new to know. Anybody have an idea as to where I should look or what I am not doing? many thanks Matt
Question on del volhist
Subject: Question on del volhist Attachment(s): My vol history for stgnew and stgdelete goes back to the beginning of time. I'd like to use Del Volhist to get rid of records that aren't needed any more. but I can't see how to do this without possibly corrupting the vol history. If I understand things correctly, if a tape is in stgdelete status as of a given point in time (let's say 30 days ago), then I should be able to delete all stgnew and stgdelete records prior to that time, right? However, if a tape is in stgnew status at that time, then I better not do any deletes using that time, right? So, how do I construct my Del Volhist command(s) to make such dynamic decisions for every volume in the volhistory? Note, we have DRM, so dbbackup entires are not a problem. System is TSM 4.1.2 on AIX 4.3.3. Bob Brazner Johnson Controls, Inc. (414) 524-2570 (Embedded image moved to file: pic08360.pcx) pic08360.pcx
I can't install TDP for Oracle Agent correctly.
Hello : I want to install TDP for Oracle 2.1.10 on HP 9000, but I get some error below. l "obndra"; resolving FUNC symbol (in file /orahome/ora805/lib//libnetwork.a[nzdo.o]) to OBJECT symbol (in file /orahome/ora805/lib//libclient.a[obndra.o]) ld: Type mismatch for symbol "oclose"; resolving FUNC symbol (in file /orahome/ora805/lib//libnetwork.a[nzdo.o]) to OBJECT symbol (in file /orahome/ora805/lib//libclient.a[oclose.o]) ld: Type mismatch for symbol "odefin"; resolving FUNC symbol (in file /orahome/ora805/lib//libnetwork.a[nzioa.o]) to OBJECT symbol (in file /orahome/ora805/lib//libclient.a[odefin.o]) ld: Type mismatch for symbol "oerhms"; resolving FUNC symbol (in file /orahome/ora805/lib//libnetwork.a[nzdo.o]) to OBJECT symbol (in file /orahome/ora805/lib//libclient.a[oerhms.o]) ld: Type mismatch for symbol "oexec"; resolving FUNC symbol (in file /orahome/ora805/lib//libnetwork.a[nzdo.o]) to OBJECT symbol (in file /orahome/ora805/lib//libclient.a[oexec.o]) ld: Type mismatch for symbol "olog"; resolving FUNC symbol (in file /orahome/ora805/lib//libnetwork.a[nzdo.o]) to OBJECT symbol (in file /orahome/ora805/lib//libclient.a[olog.o]) ld: Type mismatch for symbol "ologof"; resolving FUNC symbol (in file /orahome/ora805/lib//libnetwork.a[nzdo.o]) to OBJECT symbol (in file /orahome/ora805/lib//libclient.a[ologof.o]) ld: Type mismatch for symbol "oopen"; resolving FUNC symbol (in file /orahome/ora805/lib//libnetwork.a[nzdo.o]) to OBJECT symbol (in file /orahome/ora805/lib//libclient.a[oopen.o]) ld: Type mismatch for symbol "oparse"; resolving FUNC symbol (in file /orahome/ora805/lib//libnetwork.a[nzdo.o]) to OBJECT symbol (in file /orahome/ora805/lib//libclient.a[oparse.o]) ld: Unknown input file type: "/usr/lib/libobk.sl" I send the error log to Oracle and they tell me the reponse below. Explanation --- This is a known HP bug on the 64-bit release. Please refer to the release notes and review the 'Requried HP Patches'. Patch PHSS_15316 will alleviate the error messages. Solution Description Shutdown all Oracle instances and apply the HP patch PHSS_15316 to resolve the 'type mismatch' errors. Contact Hewlett-Packard for the patch. I did do what they say but I still get the same error log. Then I get a feekback from HP Taiwan Response Center, they tell me that the Oracle on HP is 64bit and the libobk.sl of TDP is 32bit. So I recieve the error message : type mismatch Is it right ?! I can't install TDP for Oracle 2.1.10 on HP with 64bit Oracle 8.0.5 . Does 64bit libobk.sl exist ? Is anyone have the same experience ? How to solve it ? Micahel Hsu
Re: Question on del volhist
Removing the STGNEW and STGDELETE volhist entries does not affect any data that may be on those tapes. Those entries do not participate in any type of DB recovery, either. The only thing I know of that those entries are used for is to provide a good idea what tapes need to be audited, if you ever have to do a DB restore and back-level your system. I believe it is safe to delete any of those entries that are older than your oldest DB backup. -Original Message- From: Brazner, Bob [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 11, 2001 10:26 AM To: [EMAIL PROTECTED] Subject: Question on del volhist Subject: Question on del volhist Attachment(s): My vol history for stgnew and stgdelete goes back to the beginning of time. I'd like to use Del Volhist to get rid of records that aren't needed any more. but I can't see how to do this without possibly corrupting the vol history. If I understand things correctly, if a tape is in stgdelete status as of a given point in time (let's say 30 days ago), then I should be able to delete all stgnew and stgdelete records prior to that time, right? However, if a tape is in stgnew status at that time, then I better not do any deletes using that time, right? So, how do I construct my Del Volhist command(s) to make such dynamic decisions for every volume in the volhistory? Note, we have DRM, so dbbackup entires are not a problem. System is TSM 4.1.2 on AIX 4.3.3. Bob Brazner Johnson Controls, Inc. (414) 524-2570 (Embedded image moved to file: pic08360.pcx)
Re: very few tapes expiring
Hello, did you check that the media access status is "readwrite" or it is "unavailable? - Original Message - From: MC Matt Cooper (2838) <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, April 11, 2001 17:03 Subject: very few tapes expiring > Hello all, > I am running TSM 4.1.3 (just upgraded from 4.1.1) on OS390 2.7. We > have been up and running for about 5 months now and the tape people (who > initially said tapes were returning from offsite) have told me that not to > many tapes return from offsite. So I start looking at things. We have > NETWARE, NT, AIX, SUN UNIX, DB2, SQL, ORACLE, and MS-EXchange servers + 100 > desktops. > I see that I have a lot of tapes that are still in use all the way back to > when we were just testing things out 5 months ago. > I can also see that the expiration process is running daily ( and not to > the 3 hr limit). > I can see that the tapes all have various amounts of reclaimable % of space > on them, some all the way to 100%, but even though I see this from running > Q VOL xx that when I run Q CONTENT x COUNT=100 that there are some > files there. > I know that the copygroups have been changed around, but they always had > either VERSIONS DATA EXISTS < 45 or RETAIN EXTRA VERSIONS < 45. RETAIN > ONLY VERSION is 60, everywhere. > I know that I update the copy groups and activate the policysets every > weekend to change the COPYMODE to/from ABSOLUTE/INCREMENTAL to force weekend > fulls. (this shouldn't matter?) > I see some NETWARE, AIX, DB2 files on these tapes that are 4 months old. > I am at a loss as to what is wrong or what I am to new to know. Anybody > have an idea as to where I should look or what I am not doing? > many thanks > Matt
Re: Question on del volhist
Don't over think it. Remember, information about volumes is in the database too and really, the only volume history record you are concerned about is the one indicating the most recent db backup tape. I routinely run, like daily, a delete volhist type=all todate=today-30. Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs CO 80949-1313 (719) 531-5926 Fax: (240) 539-7175 Email: [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Brazner, Bob Sent: Wednesday, April 11, 2001 8:26 AM To: [EMAIL PROTECTED] Subject: Question on del volhist Subject: Question on del volhist Attachment(s): My vol history for stgnew and stgdelete goes back to the beginning of time. I'd like to use Del Volhist to get rid of records that aren't needed any more. but I can't see how to do this without possibly corrupting the vol history. If I understand things correctly, if a tape is in stgdelete status as of a given point in time (let's say 30 days ago), then I should be able to delete all stgnew and stgdelete records prior to that time, right? However, if a tape is in stgnew status at that time, then I better not do any deletes using that time, right? So, how do I construct my Del Volhist command(s) to make such dynamic decisions for every volume in the volhistory? Note, we have DRM, so dbbackup entires are not a problem. System is TSM 4.1.2 on AIX 4.3.3. Bob Brazner Johnson Controls, Inc. (414) 524-2570 (Embedded image moved to file: pic08360.pcx)
Re: very few tapes expiring
Hello, did you check that the media access status is "readwrite" or it is "unavailable? Cyril Todorov System Administrator BULBANK AD 7 Sv. Nedelya Sq. Sofia1000 Bulgaria tel.: +359 2 98412662 email: [EMAIL PROTECTED] > - Original Message - > From: MC Matt Cooper (2838) <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, April 11, 2001 17:03 > Subject: very few tapes expiring > > > > Hello all, > > I am running TSM 4.1.3 (just upgraded from 4.1.1) on OS390 2.7. > We > > have been up and running for about 5 months now and the tape people (who > > initially said tapes were returning from offsite) have told me that not to > > many tapes return from offsite. So I start looking at things. We have > > NETWARE, NT, AIX, SUN UNIX, DB2, SQL, ORACLE, and MS-EXchange servers + > 100 > > desktops. > > I see that I have a lot of tapes that are still in use all the way back > to > > when we were just testing things out 5 months ago. > > I can also see that the expiration process is running daily ( and not to > > the 3 hr limit). > > I can see that the tapes all have various amounts of reclaimable % of > space > > on them, some all the way to 100%, but even though I see this from > running > > Q VOL xx that when I run Q CONTENT x COUNT=100 that there are some > > files there. > > I know that the copygroups have been changed around, but they always had > > either VERSIONS DATA EXISTS < 45 or RETAIN EXTRA VERSIONS < 45. RETAIN > > ONLY VERSION is 60, everywhere. > > I know that I update the copy groups and activate the policysets every > > weekend to change the COPYMODE to/from ABSOLUTE/INCREMENTAL to force > weekend > > fulls. (this shouldn't matter?) > > I see some NETWARE, AIX, DB2 files on these tapes that are 4 months old. > > I am at a loss as to what is wrong or what I am to new to know. Anybody > > have an idea as to where I should look or what I am not doing? > > many thanks > > Matt >
lan free for DB2 on Windows NT
According to the tivoli site: http://www.tivoli.com/products/index/storage_mgr/storage_mgr_concepts.html DB2 Lan-free is available. I thought it wasn't available yet. Any ideas whether this is true or not? Richard. Richard Bates Storage Specialist ITS - SB - Enterprise Consultancy Services == Voice : +44 (0) 1926 462298 (Hicom : 662298) IBM Mobile: +44 (0)775 386 8289 (Mobex : 270798) [EMAIL PROTECTED]
Can I install TDP for Oracle on HP 9000/800 (64bit) and Oracle 8. 0.5 (64bit) ?
> -Original Message- > From: 321 880053 ®}¸Î¹F > Sent: Wednesday, April 11, 2001 11:02 PM > To: '[EMAIL PROTECTED]' > Subject: Can I install TDP for Oracle on HP 9000/800 (64bit) and > Oracle 8.0.5 (64bit) ? > > Can I install TDP for Oracle on HP 9000/800 (64bit) and Oracle 8.0.5 > (64bit) ? > > I check the document of TDP for Oracle , > I see the section about AIX 32bit environment and AIX 64bit environment. > I also see the section about Solaris 32bit environment and Solaris 64bit > environment. > But I only see the section about HP client environment. > Does it mean the TDP for Oracle only could be installed on HP 32bit > environment ? > > Michael Hsu >
Re: very few tapes expiring
I see tapes from both the copypool and my onsite tapepool. -Original Message- From: Lambelet,Rene,VEVEY,FC-SIL/INF. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 11, 2001 10:18 AM To: [EMAIL PROTECTED] Subject: Re: very few tapes expiring Hello, do you mean tapes for copy stgp ? Do you run Reclamations ? René Lambelet Nestec S.A. / Informatique du Centre 55, av. Nestlé CH-1800 Vevey (Switzerland) *+41'21'924'35'43 7+41'21'924'28'88 * K4-117 email [EMAIL PROTECTED] Visit our site: http://www.nestle.com This message is intended only for the use of the addressee and may contain information that is privileged and confidential. > -Original Message- > From: MC Matt Cooper (2838) [SMTP:[EMAIL PROTECTED]] > Sent: Wednesday, 11. April 2001 16:03 > To: [EMAIL PROTECTED] > Subject: very few tapes expiring > > Hello all, > I am running TSM 4.1.3 (just upgraded from 4.1.1) on OS390 2.7. > We > have been up and running for about 5 months now and the tape people (who > initially said tapes were returning from offsite) have told me that not to > many tapes return from offsite. So I start looking at things. We have > NETWARE, NT, AIX, SUN UNIX, DB2, SQL, ORACLE, and MS-EXchange servers + > 100 > desktops. > I see that I have a lot of tapes that are still in use all the way back > to > when we were just testing things out 5 months ago. > I can also see that the expiration process is running daily ( and not to > the 3 hr limit). > I can see that the tapes all have various amounts of reclaimable % of > space > on them, some all the way to 100%, but even though I see this from > running > Q VOL xx that when I run Q CONTENT x COUNT=100 that there are some > files there. > I know that the copygroups have been changed around, but they always had > either VERSIONS DATA EXISTS < 45 or RETAIN EXTRA VERSIONS < 45. RETAIN > ONLY VERSION is 60, everywhere. > I know that I update the copy groups and activate the policysets every > weekend to change the COPYMODE to/from ABSOLUTE/INCREMENTAL to force > weekend > fulls. (this shouldn't matter?) > I see some NETWARE, AIX, DB2 files on these tapes that are 4 months old. > I am at a loss as to what is wrong or what I am to new to know. Anybody > have an idea as to where I should look or what I am not doing? > many thanks > Matt
Re: very few tapes expiring
The media access is eather read/write, offsite, and a few pending that are on there way back. It is not a situation where nothing is cleaning up. It just seams like at half of the tapes that were cut 4 months agao are still out there. THe tape management people say that there are only a few coming back. All the DB backups seem to cycle fine and some of the other one do also. But not all Matt -Original Message- From: Cyril Todorov [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 11, 2001 10:54 AM To: [EMAIL PROTECTED] Subject: Re: very few tapes expiring Hello, did you check that the media access status is "readwrite" or it is "unavailable? Cyril Todorov System Administrator BULBANK AD 7 Sv. Nedelya Sq. Sofia1000 Bulgaria tel.: +359 2 98412662 email: [EMAIL PROTECTED] > - Original Message - > From: MC Matt Cooper (2838) <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, April 11, 2001 17:03 > Subject: very few tapes expiring > > > > Hello all, > > I am running TSM 4.1.3 (just upgraded from 4.1.1) on OS390 2.7. > We > > have been up and running for about 5 months now and the tape people (who > > initially said tapes were returning from offsite) have told me that not to > > many tapes return from offsite. So I start looking at things. We have > > NETWARE, NT, AIX, SUN UNIX, DB2, SQL, ORACLE, and MS-EXchange servers + > 100 > > desktops. > > I see that I have a lot of tapes that are still in use all the way back > to > > when we were just testing things out 5 months ago. > > I can also see that the expiration process is running daily ( and not to > > the 3 hr limit). > > I can see that the tapes all have various amounts of reclaimable % of > space > > on them, some all the way to 100%, but even though I see this from > running > > Q VOL xx that when I run Q CONTENT x COUNT=100 that there are some > > files there. > > I know that the copygroups have been changed around, but they always had > > either VERSIONS DATA EXISTS < 45 or RETAIN EXTRA VERSIONS < 45. RETAIN > > ONLY VERSION is 60, everywhere. > > I know that I update the copy groups and activate the policysets every > > weekend to change the COPYMODE to/from ABSOLUTE/INCREMENTAL to force > weekend > > fulls. (this shouldn't matter?) > > I see some NETWARE, AIX, DB2 files on these tapes that are 4 months old. > > I am at a loss as to what is wrong or what I am to new to know. Anybody > > have an idea as to where I should look or what I am not doing? > > many thanks > > Matt >
Re: very few tapes expiring
Can we get some Q STG F=D, Q SCHED T=A, Q VOL F=D, Q DEVC, and Q DRM output for some effected tapes and tape pools? Alex -Original Message- From: MC Matt Cooper (2838) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 11, 2001 8:47 AM To: [EMAIL PROTECTED] Subject: Re: very few tapes expiring The media access is eather read/write, offsite, and a few pending that are on there way back. It is not a situation where nothing is cleaning up. It just seams like at half of the tapes that were cut 4 months agao are still out there. THe tape management people say that there are only a few coming back. All the DB backups seem to cycle fine and some of the other one do also. But not all Matt -Original Message- From: Cyril Todorov [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 11, 2001 10:54 AM To: [EMAIL PROTECTED] Subject: Re: very few tapes expiring Hello, did you check that the media access status is "readwrite" or it is "unavailable? Cyril Todorov System Administrator BULBANK AD 7 Sv. Nedelya Sq. Sofia1000 Bulgaria tel.: +359 2 98412662 email: [EMAIL PROTECTED] > - Original Message - > From: MC Matt Cooper (2838) <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, April 11, 2001 17:03 > Subject: very few tapes expiring > > > > Hello all, > > I am running TSM 4.1.3 (just upgraded from 4.1.1) on OS390 2.7. > We > > have been up and running for about 5 months now and the tape people (who > > initially said tapes were returning from offsite) have told me that not to > > many tapes return from offsite. So I start looking at things. We have > > NETWARE, NT, AIX, SUN UNIX, DB2, SQL, ORACLE, and MS-EXchange servers + > 100 > > desktops. > > I see that I have a lot of tapes that are still in use all the way back > to > > when we were just testing things out 5 months ago. > > I can also see that the expiration process is running daily ( and not to > > the 3 hr limit). > > I can see that the tapes all have various amounts of reclaimable % of > space > > on them, some all the way to 100%, but even though I see this from > running > > Q VOL xx that when I run Q CONTENT x COUNT=100 that there are some > > files there. > > I know that the copygroups have been changed around, but they always had > > either VERSIONS DATA EXISTS < 45 or RETAIN EXTRA VERSIONS < 45. RETAIN > > ONLY VERSION is 60, everywhere. > > I know that I update the copy groups and activate the policysets every > > weekend to change the COPYMODE to/from ABSOLUTE/INCREMENTAL to force > weekend > > fulls. (this shouldn't matter?) > > I see some NETWARE, AIX, DB2 files on these tapes that are 4 months old. > > I am at a loss as to what is wrong or what I am to new to know. Anybody > > have an idea as to where I should look or what I am not doing? > > many thanks > > Matt >
deleting an undefined volume
Hi all, I'm sorry if this is a dumb question, but here goes... I labeled a volume and used this volume for a db backup. My problem is that I forgot to define the volume in my copy storage pool. Now, I cannot define it to the pool (because it was used for a db backup), nor can I give the volume a status of scratch... How can I get out of this mess? I'd like to simply delete and relabel the volume, I have no need to preseve the db backup. Thanks, Jon -- Jon Milliren Systems Administrator University of Pittsburgh Office of Institutional Advancement [EMAIL PROTECTED] (412) 624-2727 office (412) 480-8495 mobile
TSM password expiring on AIX client
I have TSM 3.7.2 client code installed on AIX 4.3. My backups failed last night due to a the password expiring. The password expiration is set to 90 days. It has been 42 days since the password has been reset. Has anyone else seen this problem? If so how did you correct it? Below is the errors I see in the activity log: 04/11/2001 12:09:14 ANR0406I Session 300586 started for node GRBAPT33 (AIX) (BPX-Tcp/Ip 32.32.51.240(-28695)). 04/11/2001 12:09:14 ANR0425W Session 300586 for node GRBAPT33 (AIX) refused - password has expired. 04/11/2001 12:09:14 ANR0403I Session 300586 ended for node GRBAPT33 (AIX). 04/11/2001 12:09:14 ANR0406I Session 300587 started for node GRBAPT33 (AIX) (BPX-Tcp/Ip 32.32.51.240(-28694)). 04/11/2001 12:09:14 ANR0425W Session 300587 for node GRBAPT33 (AIX) refused - password has expired. Here is my query node: tsm: ADSM2>q node grbapt33 f=d Node Name: GRBAPT33 Platform: AIX Client OS Level: 4.3 Client Version: Version 3, Release 7, Level 2.0 Policy Domain Name: STANDARD Last Access Date/Time: 04/11/2001 13:13:32 Days Since Last Access: <1 Password Set Date/Time: 02/28/2001 14:55:54 Days Since Password Set: 42 Invalid Sign-on Count: 0 Locked?: No Contact: TECH SUPPORT LOCAL Compression: Yes Archive Delete Allowed?: Yes Backup Delete Allowed?: No Registration Date/Time: 01/10/2001 08:34:10 Registering Administrator: JULPHINN Last Communication Method Used: BPX-Tcp/Ip Bytes Received Last Session: 2,951 Bytes Sent Last Session: 9.67 M Duration of Last Session: 388.22 Pct. Idle Wait Last Session: 88.58 more... ( to continue, 'C' to cancel) Invalid Sign-on Count: 0 Locked?: No Contact: TECH SUPPORT LOCAL Compression: Yes Archive Delete Allowed?: Yes Backup Delete Allowed?: No Registration Date/Time: 01/10/2001 08:34:10 Registering Administrator: JULPHINN Last Communication Method Used: BPX-Tcp/Ip Bytes Received Last Session: 2,951 Bytes Sent Last Session: 9.67 M Duration of Last Session: 388.22 Pct. Idle Wait Last Session: 88.58 more... ( to continue, 'C' to cancel) Pct. Comm. Wait Last Session: 2.97 Pct. Media Wait Last Session: 0.00 Optionset: GENERAL URL: Node Type: Client Password Expiration Period: Keep Mount Point?: No Maximum Mount Points Allowed: 1 tsm: ADSM2>
Looking for support advice
I've been charged with the task of identifying how to integrate our 24 x 7 operations staff into looking at TSM problems before paging out to the administrator. I'd like to set up an administrator with OPERATOR level authority to limit the scope of their activities. What procedures and processes are you folks turning over to your support staffs? appreciate the help in advance,,,thanks.
How Can I reduce the OffSitePool
We are having problems with our DBsize and Recovery Log size. We are in a disk crunch. So I have been looking for ways to reduce the # of files that our DB and Recover Log file keeps track of. Our OnSitePool and our OffSite pool are almost idential in the number of files that are contained in them. We use this pool for DRM. My thought is that if we TRULY have a DR situation we need only provide the last ACTIVE files to our clients. I do not think that we need to provide 18 generations of data files to our company is not producing our product! Therefore, if I could only produce offsitepool information that contained the last active file it would reduce the number of tapes useds, reduce the # of files managed, etc. and maybe help us Anyone know if this could be done or not or have any workarounds that would still fit into a DRM scenario? _ Diana Cline Ross Products Division 614 / 624-3788
Re: deleting an undefined volume
Do something like: del volhist todate=-4 type=dbbackup where the -4 is the number of days ago that you did the backup. Warning: This will release >ALL< database backup volumes prior to then. However, it this volume is your only backup, it will not be released. On Wed, 11 Apr 2001, Jon Milliren wrote: > Hi all, > > I'm sorry if this is a dumb question, but here goes... I labeled a > volume and used this volume for a db backup. My problem is that I forgot > to define the volume in my copy storage pool. Now, I cannot define it to > the pool (because it was used for a db backup), nor can I give the > volume a status of scratch... > > How can I get out of this mess? I'd like to simply delete and relabel > the volume, I have no need to preseve the db backup. > > Thanks, > > Jon > > -- > Jon Milliren > Systems Administrator > University of Pittsburgh > Office of Institutional Advancement > > [EMAIL PROTECTED] > (412) 624-2727 office > (412) 480-8495 mobile >
Re: very few tapes expiring
Well I think I found something big. It does not explain everything I see but it is definitely more than half. The first set of servers that we were working with were DB2 database stuff. I have been told that when using the DB2 API that DB2 ignores/overrides the copygroup parameters and everything is saved until the DB2 API is run to delete it. I was told by the DB2 guys that they thought they had this process running and they just forgot to tell me about it. Well it did not run. So I had them run it, on all there DB2 data bases on all there AIX nodes. I will have to wait till tomorrow after we run EXPIRATION processing, see what is not in a PENDING status, and re-evaluate this whole process. I may just wait till monday to get any easier view of what the whole old tape scene look like. I have found 2 'test' nodes and 1 node that has changed names with a hardware change (not a good idea). I am sure there is some 'ONLY COPY' files associated with them. IF I still have problems I will restate this topic. Thanks everyone for your help Matt -Original Message- From: Alex Paschal [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 11, 2001 12:20 PM To: [EMAIL PROTECTED] Subject: Re: very few tapes expiring Can we get some Q STG F=D, Q SCHED T=A, Q VOL F=D, Q DEVC, and Q DRM output for some effected tapes and tape pools? Alex -Original Message- From: MC Matt Cooper (2838) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 11, 2001 8:47 AM To: [EMAIL PROTECTED] Subject: Re: very few tapes expiring The media access is eather read/write, offsite, and a few pending that are on there way back. It is not a situation where nothing is cleaning up. It just seams like at half of the tapes that were cut 4 months agao are still out there. THe tape management people say that there are only a few coming back. All the DB backups seem to cycle fine and some of the other one do also. But not all Matt -Original Message- From: Cyril Todorov [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 11, 2001 10:54 AM To: [EMAIL PROTECTED] Subject: Re: very few tapes expiring Hello, did you check that the media access status is "readwrite" or it is "unavailable? Cyril Todorov System Administrator BULBANK AD 7 Sv. Nedelya Sq. Sofia1000 Bulgaria tel.: +359 2 98412662 email: [EMAIL PROTECTED] > - Original Message - > From: MC Matt Cooper (2838) <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, April 11, 2001 17:03 > Subject: very few tapes expiring > > > > Hello all, > > I am running TSM 4.1.3 (just upgraded from 4.1.1) on OS390 2.7. > We > > have been up and running for about 5 months now and the tape people (who > > initially said tapes were returning from offsite) have told me that not to > > many tapes return from offsite. So I start looking at things. We have > > NETWARE, NT, AIX, SUN UNIX, DB2, SQL, ORACLE, and MS-EXchange servers + > 100 > > desktops. > > I see that I have a lot of tapes that are still in use all the way back > to > > when we were just testing things out 5 months ago. > > I can also see that the expiration process is running daily ( and not to > > the 3 hr limit). > > I can see that the tapes all have various amounts of reclaimable % of > space > > on them, some all the way to 100%, but even though I see this from > running > > Q VOL xx that when I run Q CONTENT x COUNT=100 that there are some > > files there. > > I know that the copygroups have been changed around, but they always had > > either VERSIONS DATA EXISTS < 45 or RETAIN EXTRA VERSIONS < 45. RETAIN > > ONLY VERSION is 60, everywhere. > > I know that I update the copy groups and activate the policysets every > > weekend to change the COPYMODE to/from ABSOLUTE/INCREMENTAL to force > weekend > > fulls. (this shouldn't matter?) > > I see some NETWARE, AIX, DB2 files on these tapes that are 4 months old. > > I am at a loss as to what is wrong or what I am to new to know. Anybody > > have an idea as to where I should look or what I am not doing? > > many thanks > > Matt >
Wanted: Experiences with TDP Domino and Transaction Logging
Our shop is currently running Lotus Notes and for our remote WAN attached Notes servers we had to go to using the TDP Agent and daily incremental processing. This was because the amount of data to back up using the B/A client and *.NSF files was too much to fit in the window and bandwidth. We are now looking at moving to Domino. Our Notes admins have read some on the transaction logging and don't like what they read. They say that the hardware requirements to run logging are too much. Plus the fact that certain database functions (compact with space reduction...) assign a new DBIID to the database and the next TDP incremental would actually by another full backup since the DBIID has changed. I've been reading the TDP Domino manuals and archives and feel that since the compactions are scheduled on weekends, this is not that big of an issue. We would be doing full backups on weekends anyway. So I need some ammunition to convince 'them' that we can still use the TDP Agent and not loose any functionality. Their solution is to create a central Domino server with LOTS of disk and then replicate the databases back here and use TSM to back up this massive server. The main issue is the changing DBIID. THey are concerned that they would not be able to recover a database when it could possibly have multiple DBIID's associated with the same database within TSM. TIA, Bill Boyer "Some days you are the bug, some days you are the windshield." - ??
TSM password expiring on AIX client
Additional information. This AIX client is registered to an OS390/2.8 server and has TSM 3.7.4 installed. I submit a batch job monthly to reset the passwords. I have Novell and NT clients also registered to the same OS390 server. I do not have the same password problems with the other clients. - Forwarded by David Browne/Louisville/Humana on 04/11/2001 01:52 PM - David Browne To: [EMAIL PROTECTED] 04/11/2001 cc: 01:16 PM Subject: TSM password expiring on AIX client I have TSM 3.7.2 client code installed on AIX 4.3. My backups failed last night due to a the password expiring. The password expiration is set to 90 days. It has been 42 days since the password has been reset. Has anyone else seen this problem? If so how did you correct it? Below is the errors I see in the activity log: 04/11/2001 12:09:14 ANR0406I Session 300586 started for node GRBAPT33 (AIX) (BPX-Tcp/Ip 32.32.51.240(-28695)). 04/11/2001 12:09:14 ANR0425W Session 300586 for node GRBAPT33 (AIX) refused - password has expired. 04/11/2001 12:09:14 ANR0403I Session 300586 ended for node GRBAPT33 (AIX). 04/11/2001 12:09:14 ANR0406I Session 300587 started for node GRBAPT33 (AIX) (BPX-Tcp/Ip 32.32.51.240(-28694)). 04/11/2001 12:09:14 ANR0425W Session 300587 for node GRBAPT33 (AIX) refused - password has expired. Here is my query node: tsm: ADSM2>q node grbapt33 f=d Node Name: GRBAPT33 Platform: AIX Client OS Level: 4.3 Client Version: Version 3, Release 7, Level 2.0 Policy Domain Name: STANDARD Last Access Date/Time: 04/11/2001 13:13:32 Days Since Last Access: <1 Password Set Date/Time: 02/28/2001 14:55:54 Days Since Password Set: 42 Invalid Sign-on Count: 0 Locked?: No Contact: TECH SUPPORT LOCAL Compression: Yes Archive Delete Allowed?: Yes Backup Delete Allowed?: No Registration Date/Time: 01/10/2001 08:34:10 Registering Administrator: JULPHINN Last Communication Method Used: BPX-Tcp/Ip Bytes Received Last Session: 2,951 Bytes Sent Last Session: 9.67 M Duration of Last Session: 388.22 Pct. Idle Wait Last Session: 88.58 more... ( to continue, 'C' to cancel) Invalid Sign-on Count: 0 Locked?: No Contact: TECH SUPPORT LOCAL Compression: Yes Archive Delete Allowed?: Yes Backup Delete Allowed?: No Registration Date/Time: 01/10/2001 08:34:10 Registering Administrator: JULPHINN Last Communication Method Used: BPX-Tcp/Ip Bytes Received Last Session: 2,951 Bytes Sent Last Session: 9.67 M Duration of Last Session: 388.22 Pct. Idle Wait Last Session: 88.58 more... ( to continue, 'C' to cancel) Pct. Comm. Wait Last Session: 2.97 Pct. Media Wait Last Session: 0.00 Optionset: GENERAL URL: Node Type: Client Password Expiration Period: Keep Mount Point?: No Maximum Mount Points Allowed: 1 tsm: ADSM2>
Re: DIRMC - disadvantages only?
Back in November you described this implementation, which makes a major reduction in the time required to do a DIRMC offsite copy reclamation: > DIRPOOL primary DISK: NEXTPOOL->DIRFILE > DIRFILE primary SEQUENTIAL on DISK > DIRCOPYPOOL copypool TAPE Would you mind posting the output from a: query stg DIRFILE format=detail and a: query devclass I'm assuming "SEQUENTIAL on DISK" means a device class type of FILE. But I want to be sure, before making the change.
Re: How Can I reduce the OffSitePool
Diane, Look up export server or export node. This works for me to get only the active files copied to a set of offsite tapes. TSM01> help export node TSM01> help export server Denny P. -Original Message- From: Diana J.Cline [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 11, 2001 1:25 PM To: [EMAIL PROTECTED] Subject: How Can I reduce the OffSitePool We are having problems with our DBsize and Recovery Log size. We are in a disk crunch. So I have been looking for ways to reduce the # of files that our DB and Recover Log file keeps track of. Our OnSitePool and our OffSite pool are almost idential in the number of files that are contained in them. We use this pool for DRM. My thought is that if we TRULY have a DR situation we need only provide the last ACTIVE files to our clients. I do not think that we need to provide 18 generations of data files to our company is not producing our product! Therefore, if I could only produce offsitepool information that contained the last active file it would reduce the number of tapes useds, reduce the # of files managed, etc. and maybe help us Anyone know if this could be done or not or have any workarounds that would still fit into a DRM scenario? _ Diana Cline Ross Products Division 614 / 624-3788
Re: TSM password expiring on AIX client
Yopu may try the following setp to re-set the password, and see it works or not. >From TSM server; DSMADMC and logon to ADSM UPDATE NODEFORCEPWRESET=YES QUIT >From client node; DSMC Q SESSION type in new password, this will activate the password check Note: dsmc schedule needs to be running in the client node before you re-set the password; Otherwise, re-set passwordwon't work. To verify dsmc schedule is running, ps -ef | grep dsmc [at TSM server, AIX os prompt] if don't see the jobs, you have to start it by log in as super-user nohup /usr/lpp/adsm/bin/dsmc sched & Good Luck. Ming Lau Lam Research -Original Message- From: David Browne. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 11, 2001 10:57 AM To: [EMAIL PROTECTED] Subject: TSM password expiring on AIX client Additional information. This AIX client is registered to an OS390/2.8 server and has TSM 3.7.4 installed. I submit a batch job monthly to reset the passwords. I have Novell and NT clients also registered to the same OS390 server. I do not have the same password problems with the other clients. - Forwarded by David Browne/Louisville/Humana on 04/11/2001 01:52 PM - David Browne To: [EMAIL PROTECTED] 04/11/2001 cc: 01:16 PM Subject: TSM password expiring on AIX client I have TSM 3.7.2 client code installed on AIX 4.3. My backups failed last night due to a the password expiring. The password expiration is set to 90 days. It has been 42 days since the password has been reset. Has anyone else seen this problem? If so how did you correct it? Below is the errors I see in the activity log: 04/11/2001 12:09:14 ANR0406I Session 300586 started for node GRBAPT33 (AIX) (BPX-Tcp/Ip 32.32.51.240(-28695)). 04/11/2001 12:09:14 ANR0425W Session 300586 for node GRBAPT33 (AIX) refused - password has expired. 04/11/2001 12:09:14 ANR0403I Session 300586 ended for node GRBAPT33 (AIX). 04/11/2001 12:09:14 ANR0406I Session 300587 started for node GRBAPT33 (AIX) (BPX-Tcp/Ip 32.32.51.240(-28694)). 04/11/2001 12:09:14 ANR0425W Session 300587 for node GRBAPT33 (AIX) refused - password has expired. Here is my query node: tsm: ADSM2>q node grbapt33 f=d Node Name: GRBAPT33 Platform: AIX Client OS Level: 4.3 Client Version: Version 3, Release 7, Level 2.0 Policy Domain Name: STANDARD Last Access Date/Time: 04/11/2001 13:13:32 Days Since Last Access: <1 Password Set Date/Time: 02/28/2001 14:55:54 Days Since Password Set: 42 Invalid Sign-on Count: 0 Locked?: No Contact: TECH SUPPORT LOCAL Compression: Yes Archive Delete Allowed?: Yes Backup Delete Allowed?: No Registration Date/Time: 01/10/2001 08:34:10 Registering Administrator: JULPHINN Last Communication Method Used: BPX-Tcp/Ip Bytes Received Last Session: 2,951 Bytes Sent Last Session: 9.67 M Duration of Last Session: 388.22 Pct. Idle Wait Last Session: 88.58 more... ( to continue, 'C' to cancel) Invalid Sign-on Count: 0 Locked?: No Contact: TECH SUPPORT LOCAL Compression: Yes Archive Delete Allowed?: Yes Backup Delete Allowed?: No Registration Date/Time: 01/10/2001 08:34:10 Registering Administrator: JULPHINN Last Communication Method Used: BPX-Tcp/Ip Bytes Received Last Session: 2,951 Bytes Sent Last Session: 9.67 M Duration of Last Session: 388.22 Pct. Idle Wait Last Session: 88.58 more... ( to continue, 'C' to cancel) Pct. Comm. Wait Last Session: 2.97 Pct. Media Wait Last Session: 0.00 Optionset: GENERAL URL: Node Type: Client Password Expiration Period: Keep Mount Point?: No Maximum Mount Points Allowed: 1 tsm: ADSM2>
Re: How Can I reduce the OffSitePool
Hi Diana, the problem with this is that DRM is designed to provide a complete copy. A copy stgpool, is just that, it contains an exact duplicate of your primary pools. Why don't you just change the number modified files that get stored? Or be more specific with your management classes - maybe some file do need 18 generations, but most only need 3. If you have a very large files, like I do (Sybase database backups), sometimes I only store the files onsite. Of course, I don't do this for the production backs, but quite often we do 'extra' backups and there is no need to send these offsite. Look for your largest node (by backup space), use q auditocc. Find the largest node, then use q occ , find the largest file space, and work with it. None of these are of course a solution, you really should get more disk space. Miles --- Miles Purdy System Manager Farm Income Programs Directorate Winnipeg, MB, CA [EMAIL PROTECTED] ph: (204) 984-1602 fax: (204) 983-7557 --- >>> [EMAIL PROTECTED] 11-Apr-01 12:25:29 PM >>> We are having problems with our DBsize and Recovery Log size. We are in a disk crunch. So I have been looking for ways to reduce the # of files that our DB and Recover Log file keeps track of. Our OnSitePool and our OffSite pool are almost idential in the number of files that are contained in them. We use this pool for DRM. My thought is that if we TRULY have a DR situation we need only provide the last ACTIVE files to our clients. I do not think that we need to provide 18 generations of data files to our company is not producing our product! Therefore, if I could only produce offsitepool information that contained the last active file it would reduce the number of tapes useds, reduce the # of files managed, etc. and maybe help us Anyone know if this could be done or not or have any workarounds that would still fit into a DRM scenario? _ Diana Cline Ross Products Division 614 / 624-3788
TDP for Domino Schedules and Opt file
I am the Domino administrator for our company and I am experimenting and testing TDP for Domino on a test server before I install the program on our production servers. For the past week I have been running a schedule for archive of transaction logs to TSM storage. This was set to run every hour. This seemed to be working properly except we were noticing that it would dump about 21mb (small size since this is only a test server) to the TSM server. I thought that the archive log would archive only if the txn log is full. Today I set up another schedule to do an incremental backup of all databases and pointing to the same dsm.opt file as the archivelog schedule. Apparently both of the schedules kicked in at the same time and started complaining that the backup failed because the databases are currently being backed up. My question is do I have to have different opt files for the different schedules like archivelog, selective backup, incremental backup, and inactivate logs? Why is the archivelog that is being run every hour dumping around 21mb every hour? Our TSM Admin is questioning why it is dumping almost 350mb per day from a server which does not have any activity. Our two production servers are heavily used and I need to get a good handle on how often I should run the archivelog and how is it going to affect the operators as far as mounting tapes etc. Any help would be appreciated.
Re: very few tapes expiring
"MC Matt Cooper (2838)" wrote: > > Well I think I found something big. It does not explain everything I see > but it is definitely more than half. The first set of servers that we were > working with were DB2 database stuff. I have been told that when using the > DB2 API that DB2 ignores/overrides the copygroup parameters and everything > is saved until the DB2 API is run to delete it. I was told by the DB2 guys > that they thought they had this process running and they just forgot to tell > me about it. Well it did not run. So I had them run it, on all there DB2 > data bases on all there AIX nodes. I will have to wait till tomorrow after > we run EXPIRATION processing, see what is not in a PENDING status, and > re-evaluate this whole process. I may just wait till monday to get any > easier view of what the whole old tape scene look like. > I have found 2 'test' nodes and 1 node that has changed names with a > hardware change (not a good idea). I am sure there is some 'ONLY COPY' > files associated with them. IF I still have problems I will restate this > topic. ...and the lesson for today, folks is: When you use something other than the vanilla b/a client for backups, such as TDP or the DB2 API, that normal retention rules and expirations will not affect files backed up like that. Each TDP, and the DB2 API, has its own methods and utilities for expiring old file versions.[1] [1] Learned this the hard way with MS SQL files. When the mistake was finally caught and proper deletions and expiration were performed, the tape library lost 20% of its volume, and the TSM database went from 35Gb to 24Gb. -- Mark Stapleton ([EMAIL PROTECTED])
Re: Restoring Linux and Solaris
Quoting "Rosetti, Bill" <[EMAIL PROTECTED]>: > I have seen a few references to this in the archives but no real answer. > If > I have a complete failure of a Linux or Solaris client, what process do > I > use to restore it? I have tried reinstalling the OS, installing the > TSM > client, then doing a complete restore. (We are backing up everything but > the > swap on both OS's). This restore blows up when it tries to touch > /lib/libc. > Should I be excluding a bunch of files so this process will work? > > I believe someone must have written a 1,2,3 process for this. Can > anyone > point me the right direction? TIA I have done this kind of recovery with a Red Hat Linux system, although I am still working on writing a 1,2,3 process that would enable someone else to duplicate what I did. I set up an NFS server with a copy of the RedHat/instimage directory from an installation CD-ROM. I then added the sfdisk utility, the dsmc program, the TSM message file, dsm.opt, dsm.sys, and some shared libraries used by sfdisk and dsmc. I booted the dead Linux system from a network install diskette copied from the installation CD-ROM. I requested rescue mode and specified the NFS server as the source for the installation image. I used the sfdisk incorporated into the rescue image to partition the disks. I formatted the swap partition and enabled it. I created an empty file system in each of the other partitions. I created a /mnt/root directory and mounted the empty root file system over it. I created additional mount point directories and mounted the other empty file systems. I ran a series of dsmc restores into the empty file systems. I ran the lilo command to recreate the boot loader in the master boot record. I unmounted all the hard disk file systems, shut down, and rebooted from the hard disk. The process described above is suitable for situations where the new hardware configuration is identical to the old one. I am still working on a systematic procedure for recreating a Linux system on different hardware. I am not directly involved in disaster preparations for Solaris systems. The book "Unix Backup & Recovery", by W. Curtis Preston, describes a procedure for rebuilding a Solaris system from backup tapes. I think this procedure could be modified to use a TSM server.
Re: very few tapes expiring
Remember that DB2 backups come in as Backup data, not Archive. So after the DBA expires the file, you will keep it around for the Retain Only number of days. If the copy group for the management class they are stored under has that set at 90 days, you'll start getting tapes back in about 3 months. There are some tricks to this, so if you need help, you can probably get 3 or 4 different methods from the list here. Nick Cassimatis [EMAIL PROTECTED]
Re: deleting an undefined volume
You can't get rid of the most recent db backup. If you do another db backup, you can then do a delete volhist type=dbb todate=today That should get rid of all but the most recent db backup tape and return it to scratch. You might have to wait until tomorrow to delete today's db backup. I've fooled with this and sometimes it can be confounding. TSM does not want to let you delete the most recent db backup for obvious reasons. Thanks, Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs CO 80949-1313 (719) 531-5926 Fax: (240) 539-7175 Email: [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Jon Milliren Sent: Wednesday, April 11, 2001 11:15 AM To: [EMAIL PROTECTED] Subject: deleting an undefined volume Hi all, I'm sorry if this is a dumb question, but here goes... I labeled a volume and used this volume for a db backup. My problem is that I forgot to define the volume in my copy storage pool. Now, I cannot define it to the pool (because it was used for a db backup), nor can I give the volume a status of scratch... How can I get out of this mess? I'd like to simply delete and relabel the volume, I have no need to preseve the db backup. Thanks, Jon -- Jon Milliren Systems Administrator University of Pittsburgh Office of Institutional Advancement [EMAIL PROTECTED] (412) 624-2727 office (412) 480-8495 mobile
Multiple off-site/copy pools
Is anyone using multiple copy pools to maintain two offsite backups ( or one offsite and one out-of-library/on-site )?? I think my management is heading this direction and would like to get an idea if this is real common ?? Thanks Mike Walker
Defining IBM 3583 as a SCSI device under Windows 2000
I searched ADSM-L the last few days and did not find instructions on how to define an IBM 3583 as a SCSI device under Windows 2000. Here is how I got it to work. 1. Disable the Removable Storage (a.k.a. RSM) service 2. Install TSM 4.1.3. Note: Read the readme files. You must first remove TSM before installing 4.1.3. 3. From your original TSM 4.1.1 media install the License module. 4. I next attempted to use the GUI to define the library and drives. TSM generated the following commands and messages: ANR2017I Administrator ADMIN issued command: DEFINE LIBRARY lb6.0.0.5 libtype=scsi device=lb6.0.0.5 ANR8400I Library LB6.0.0.5 defined. ANR2017I Administrator ADMIN issued command: DEFINE DRIVE lb6.0.0.5 GENDRV_Tape0 device=\\.\Tape0 element=0 ANR8366E DEFINE DRIVE: Invalid value for ELEMENT parameter. ANR2017I Administrator ADMIN issued command: ROLLBACK ANR2017I Administrator ADMIN issued command: DEFINE DRIVE lb6.0.0.5 GENDRV_Tape1 device=\\.\Tape1 element=1 ANR8366E DEFINE DRIVE: Invalid value for ELEMENT parameter. ANR2017I Administrator ADMIN issued command: ROLLBACK ANR2017I Administrator ADMIN issued command: DEFINE DRIVE lb6.0.0.5 GENDRV_Tape2 device=\\.\Tape2 element=2 ANR8366E DEFINE DRIVE: Invalid value for ELEMENT parameter. ANR2017I Administrator ADMIN issued command: ROLLBACK ANR2017I Administrator ADMIN issued command: DEFINE DEVCLASS LTOCLASS1 devtype=LTO format=drive library=lb6.0.0.5 ANR2203I Device class LTOCLASS1 defined. ANR2017I Administrator ADMIN issued command: DEFINE STGPOOL LTOPOOL1 LTOCLASS1 maxscratch=500 ANR2200I Storage pool LTOPOOL1 defined (device class LTOCLASS1). The drive element numbers are those that match the documentation for Windows 2000/NT. However I think they are actually for RSM under Windows 2000/NT. When the RSM service is disabled the element number for the drives are 256-261. 5. I deleted the library, devclass, and stgpool definitions. The customer wanted the library name to be LTO instead of lb6.0.0.5, so I used the following definitions: DEFINE LIBRARY LTO libtype=scsi device=lb6.0.0.5 DEFINE DRIVE LTO drive1 device=//./tape0 element=256 DEFINE DRIVE LTO drive2 device=//./tape1 element=257 DEFINE DRIVE LTO drive3 device=//./tape2 element=258 DEFINE DEVCLASS LTOCLASS1 devtype=LTO format=drive library=LTO DEFINE STGPOOL LTOPOOL1 LTOCLASS1 maxscratch=500 6. I am now able to label, check in and check out tapes. A q libv shows the home elements starting at 4096.
Restoring Linux and Solaris
I have seen a few references to this in the archives but no real answer. If I have a complete failure of a Linux or Solaris client, what process do I use to restore it? I have tried reinstalling the OS, installing the TSM client, then doing a complete restore. (We are backing up everything but the swap on both OS's). This restore blows up when it tries to touch /lib/libc. Should I be excluding a bunch of files so this process will work? I believe someone must have written a 1,2,3 process for this. Can anyone point me the right direction? TIA Bill Rosetti Area Service Manager CompuCom Systems 907.762.9145 [EMAIL PROTECTED]
Migrating from TSM 4.1.1 on WinNT 4.0 to TSM 4.1.3 on Win2000
I am planning the migration of my existing WinNT 4.0 server to a new Windows 2000 server and in the process, upgrading the server code to 4.1.3. Can someone please lay out the steps I should take to get this task done. I am unsure on the proper procedures to do such a task. Any advice you could give me would be very helpful. Thanks much, Jay Volovsek
Re: Defining IBM 3583 as a SCSI device under Windows 2000
Ray, You are the new TSM guru. You are the first to make this work. Have them double whatever they are paying you. Seriously, thanks for sharing the steps. Did you have to install the IBM Ultrium Changer and Drive drivers or is ADSMSCSI doing all the work? Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs CO 80949-1313 (719) 531-5926 Fax: (240) 539-7175 Email: [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Ray Pratts Sent: Wednesday, April 11, 2001 4:00 PM To: [EMAIL PROTECTED] Subject: Defining IBM 3583 as a SCSI device under Windows 2000 I searched ADSM-L the last few days and did not find instructions on how to define an IBM 3583 as a SCSI device under Windows 2000. Here is how I got it to work. 1. Disable the Removable Storage (a.k.a. RSM) service 2. Install TSM 4.1.3. Note: Read the readme files. You must first remove TSM before installing 4.1.3. 3. From your original TSM 4.1.1 media install the License module. 4. I next attempted to use the GUI to define the library and drives. TSM generated the following commands and messages: ANR2017I Administrator ADMIN issued command: DEFINE LIBRARY lb6.0.0.5 libtype=scsi device=lb6.0.0.5 ANR8400I Library LB6.0.0.5 defined. ANR2017I Administrator ADMIN issued command: DEFINE DRIVE lb6.0.0.5 GENDRV_Tape0 device=\\.\Tape0 element=0 ANR8366E DEFINE DRIVE: Invalid value for ELEMENT parameter. ANR2017I Administrator ADMIN issued command: ROLLBACK ANR2017I Administrator ADMIN issued command: DEFINE DRIVE lb6.0.0.5 GENDRV_Tape1 device=\\.\Tape1 element=1 ANR8366E DEFINE DRIVE: Invalid value for ELEMENT parameter. ANR2017I Administrator ADMIN issued command: ROLLBACK ANR2017I Administrator ADMIN issued command: DEFINE DRIVE lb6.0.0.5 GENDRV_Tape2 device=\\.\Tape2 element=2 ANR8366E DEFINE DRIVE: Invalid value for ELEMENT parameter. ANR2017I Administrator ADMIN issued command: ROLLBACK ANR2017I Administrator ADMIN issued command: DEFINE DEVCLASS LTOCLASS1 devtype=LTO format=drive library=lb6.0.0.5 ANR2203I Device class LTOCLASS1 defined. ANR2017I Administrator ADMIN issued command: DEFINE STGPOOL LTOPOOL1 LTOCLASS1 maxscratch=500 ANR2200I Storage pool LTOPOOL1 defined (device class LTOCLASS1). The drive element numbers are those that match the documentation for Windows 2000/NT. However I think they are actually for RSM under Windows 2000/NT. When the RSM service is disabled the element number for the drives are 256-261. 5. I deleted the library, devclass, and stgpool definitions. The customer wanted the library name to be LTO instead of lb6.0.0.5, so I used the following definitions: DEFINE LIBRARY LTO libtype=scsi device=lb6.0.0.5 DEFINE DRIVE LTO drive1 device=//./tape0 element=256 DEFINE DRIVE LTO drive2 device=//./tape1 element=257 DEFINE DRIVE LTO drive3 device=//./tape2 element=258 DEFINE DEVCLASS LTOCLASS1 devtype=LTO format=drive library=LTO DEFINE STGPOOL LTOPOOL1 LTOCLASS1 maxscratch=500 6. I am now able to label, check in and check out tapes. A q libv shows the home elements starting at 4096.
Re: Defining IBM 3583 as a SCSI device under Windows 2000
I have just built a W2K server with TSM 4.1.3 accessing a 3584 Library across a SAN. I ran into the same errors that Ray did and I followed the same steps with the same results. The only problem I had was that the TSM Device Driver didn't want to start at first. After a reboot, it worked fine. I installed the Ultrium drivers before I installed TSM. -Original Message- From: Kelly J. Lipp [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 11, 2001 6:06 PM To: [EMAIL PROTECTED] Subject: Re: Defining IBM 3583 as a SCSI device under Windows 2000 Ray, You are the new TSM guru. You are the first to make this work. Have them double whatever they are paying you. Seriously, thanks for sharing the steps. Did you have to install the IBM Ultrium Changer and Drive drivers or is ADSMSCSI doing all the work? Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs CO 80949-1313 (719) 531-5926 Fax: (240) 539-7175 Email: [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Ray Pratts Sent: Wednesday, April 11, 2001 4:00 PM To: [EMAIL PROTECTED] Subject: Defining IBM 3583 as a SCSI device under Windows 2000 I searched ADSM-L the last few days and did not find instructions on how to define an IBM 3583 as a SCSI device under Windows 2000. Here is how I got it to work. 1. Disable the Removable Storage (a.k.a. RSM) service 2. Install TSM 4.1.3. Note: Read the readme files. You must first remove TSM before installing 4.1.3. 3. From your original TSM 4.1.1 media install the License module. 4. I next attempted to use the GUI to define the library and drives. TSM generated the following commands and messages: ANR2017I Administrator ADMIN issued command: DEFINE LIBRARY lb6.0.0.5 libtype=scsi device=lb6.0.0.5 ANR8400I Library LB6.0.0.5 defined. ANR2017I Administrator ADMIN issued command: DEFINE DRIVE lb6.0.0.5 GENDRV_Tape0 device=\\.\Tape0 element=0 ANR8366E DEFINE DRIVE: Invalid value for ELEMENT parameter. ANR2017I Administrator ADMIN issued command: ROLLBACK ANR2017I Administrator ADMIN issued command: DEFINE DRIVE lb6.0.0.5 GENDRV_Tape1 device=\\.\Tape1 element=1 ANR8366E DEFINE DRIVE: Invalid value for ELEMENT parameter. ANR2017I Administrator ADMIN issued command: ROLLBACK ANR2017I Administrator ADMIN issued command: DEFINE DRIVE lb6.0.0.5 GENDRV_Tape2 device=\\.\Tape2 element=2 ANR8366E DEFINE DRIVE: Invalid value for ELEMENT parameter. ANR2017I Administrator ADMIN issued command: ROLLBACK ANR2017I Administrator ADMIN issued command: DEFINE DEVCLASS LTOCLASS1 devtype=LTO format=drive library=lb6.0.0.5 ANR2203I Device class LTOCLASS1 defined. ANR2017I Administrator ADMIN issued command: DEFINE STGPOOL LTOPOOL1 LTOCLASS1 maxscratch=500 ANR2200I Storage pool LTOPOOL1 defined (device class LTOCLASS1). The drive element numbers are those that match the documentation for Windows 2000/NT. However I think they are actually for RSM under Windows 2000/NT. When the RSM service is disabled the element number for the drives are 256-261. 5. I deleted the library, devclass, and stgpool definitions. The customer wanted the library name to be LTO instead of lb6.0.0.5, so I used the following definitions: DEFINE LIBRARY LTO libtype=scsi device=lb6.0.0.5 DEFINE DRIVE LTO drive1 device=//./tape0 element=256 DEFINE DRIVE LTO drive2 device=//./tape1 element=257 DEFINE DRIVE LTO drive3 device=//./tape2 element=258 DEFINE DEVCLASS LTOCLASS1 devtype=LTO format=drive library=LTO DEFINE STGPOOL LTOPOOL1 LTOCLASS1 maxscratch=500 6. I am now able to label, check in and check out tapes. A q libv shows the home elements starting at 4096.
Restoring AIX (was Restoring Linux and Solaris)
I've got a similar query to those restoring Solaris and Linux but re AIX. It annoys me that while I have a full TSM backup of the AIX rootVG I can't use it. The bare metal redbook is no use, it just says to use mksysb I've come up with a process which almost works assuming two bootable disks are available 1. Restore a standard mksysb image, which includes the TSM client to one disk 2. Run the alt_disk_install command phases 1 & 2 to set up an alternate rootvg and restore the most recent mksysb for the box (this is just to get filesystem sizes). 3. Use standard TSM commands to restore the / /usr /var /home filesystems on the alternate disk to the latest TSM backup 4. run alt_disk_install phase 3 to setup the restored system for boot 5. boot from alternate. 6. clean up bootstrap disk 7. remirror rootvg Unfortunately step 4 fails as the alt_disk_install command plays with the alternate ODM in phases 1 & 2, but I revert to the original ODM in 3. I need to restore the original ODM because minor details like software installations are kept there. I really think that this process can be made to work if I could just save the appropriate bits of the ODM at 2.1 and put them back at 3.1. The question is what are the appropriate bits? Any AIX experts with good ODM knowledge out there? Regards Steve Harris AIX and ADSM Admin Queensland Health, Brisbane Australia
AW: Can I install TDP for Oracle on HP 9000/800 (64bit) and Oracl e 8. 0.5 (64bit) ?
Hy Michael, I had the same problem 3 weeks ago. You can use TDP for Oracle on HP 64bit environment, no problem but : you have to use the correct API. Here is what I got from the list : Hi Christoph, Yes. you can not run the TDPO 2.1.10 with the 3.7.2 client I logged a PMR with tivoli for this and this is the response I got. Customer is right. TDP for Oracle 2.1.10 on HP-UX requires the 3.7.1 API A higher level of the API like 3.7.2 API will not work. There is already a doc APAR IC27223 opened against this issue. The local fix of this APAR is to run the v3.7.2 Client in combination with the v3.7.1 API: - Save the TSM v3.7.1 API library (libApiDS.sl) to a separate directory, it should be installed by default in /opt/tivoli/tsm/client/api/bin - Install the latest version of the TSM v3.7.2 client. - Replace the current TSM v3.7.2 API library with the TSM API v3.7.1 library saved in the first step. NOTE: This solution will only work if the TSM v3.7.2 client does not require the use of the v3.7.2 API. For instance, logical volume backups (image backups) require the v3.7.2 API. I especially like the first sentence... This is what I do. 1. install TSM 3.7.1.0 b/a client including api. 2. install IBMADSMaob 2.1.0.7 (this is where the agent.lic file is) 3. copy the /opt/tivoli/tsm/client/api/bin/libApiDS.sl to /opt/tivoli/tsm/client/api/bin/libApiDS.sl.371 4. upgrade TSM b/a client to 3.7.2.x (i'm running 3.7.2.16) 5. copy /opt/tivoli/tsm/client/api/bin/libApiDS.sl /opt/tivoli/tsm/client/api/bin/libApiDS.sl.3.7.2 6. cp /opt/tivoli/tsm/client/api/bin/libApiDS.sl.371 /opt/tivoli/tsm/client/api/bin/libApiDS.sl This works, but you can't use the logical volume backups. This will work for oracle 32 bit only. = Best wishes Christoph > -Ursprüngliche Nachricht- > Von: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]] > Gesendet am: Mittwoch, 11. April 2001 17:24 > An: [EMAIL PROTECTED] > Betreff: Can I install TDP for Oracle on HP 9000/800 (64bit) and > Oracle 8. 0.5 (64bit) ? > > > -Original Message- > > From: 321 880053 ??? > > Sent: Wednesday, April 11, 2001 11:02 PM > > To: '[EMAIL PROTECTED]' > > Subject: Can I install TDP for Oracle on HP 9000/800 (64bit) and > > Oracle 8.0.5 (64bit) ? > > > > Can I install TDP for Oracle on HP 9000/800 (64bit) and Oracle 8.0.5 > > (64bit) ? > > > > I check the document of TDP for Oracle , > > I see the section about AIX 32bit environment and AIX 64bit environment. > > I also see the section about Solaris 32bit environment and Solaris 64bit > > environment. > > But I only see the section about HP client environment. > > Does it mean the TDP for Oracle only could be installed on HP 32bit > > environment ? > > > > Michael Hsu > >
