tape drive unavailable WHEN THEY ARE!!!!!
Just moved my 1200 user production system to a new system and I've gotta solve this before my diskpool fills up completely!! I'm having a whole lot of problems with tape mounts and was wondering if anyone can summarize the known problems fixes for this. (what combination of devices.rte and TSM work without problems) I'm on AIX 4.3.3 with TSM 4.1.3. Its a 3466 NSM I've got a 3494 with two 3590s. In a nutshell: I can do a: backup stg diskpool copypool with NO PROBLEMS. But if I do: upd stg diskpool hi=1 low=0 migproc=2 I get : ANR8447E No drives are currently available in library 3494LIB. ANR1401W Mount request denied for volume 200332 - mount failed. I've also seen this with onsite and offsite reclamations. any help would be much appreciated. thanks joe.f. Joseph A Faracchio, Systems Programmer, UC Berkeley Private mail on any topic should be directed to : [EMAIL PROTECTED]
Numberformat
Resubmitting this message because until now I did not receive any reaction. Is this problem with the numberformat really a bug or did I forget something. This could really help me simplifying a number of scripts. M Engels -- Forwarded by Michel Engels/BE/Devoteam on 08/15/2001 07:56 AM --- MICHEL ENGELS 08/07/2001 09:56 AM To: [EMAIL PROTECTED] cc: Subject: Numberformat Environment: server: mvs 2.9 TSM 3.7.1 client: WinNT TSM 4.1.0 This client is used as an administrative client. A number of reports are generated and send to the conserned people. Now on the server the numberformat is set to 3 to display the numbers as "1 234.6". This works fine in the administrative GUI directly on the MVS but not on the client. What is missing or is this a bug? Michel Engels TSM Consultant Devoteam Belgium
Re: backing up only 1 directory on Windows
Hm... I'm surprised you didn't get a syntax error on the "include.dir" statement, as that is not a supported option. The following isn't pretty, but it might do what you need: * Exclude all files in root of each drive. exclude *:\* * Exclude all directories on all drives other than C:. exclude.dir [abd-z]:\* * Exclude all directories on C: except for C:\Users. exclude.dir c:\[a-tv-z0-9]* exclude.dir c:\U[a-rt-z0-9]* exclude.dir c:\Us[a-df-z0-9]* exclude.dir c:\Use[a-qs-z0-9]* exclude.dir c:\User[a-rt-z0-9]* exclude.dir c:\Users?* This should catch most of the stuff. If you use other characters in directory names, you can stick them between the square brackets as well. For example, to prevent backing up a hypothetical directory named C:\user$, you could rewrite the EXCLUDE.DIRs as: exclude.dir C:\[a-tv-z0-9$]* exclude.dir C:\U[a-rt-z0-9$]* ...etc. Then C:\Users and its files and subdirectories will be backed up by default. If you want to add a little extra protection, you could do this: * Exclude all files except C:\Users and its subdirectories. exclude *:\...\* include c:\users\...\* * Exclude all directories on all drives other than C:. exclude.dir [abd-z]:\* * Exclude all directories on C: except for C:\Users. exclude.dir c:\[a-tv-z0-9$]* exclude.dir c:\U[a-rt-z0-9$]* exclude.dir c:\Us[a-df-z0-9$]* exclude.dir c:\Use[a-qs-z0-9$]* exclude.dir c:\User[a-rt-z0-9$]* exclude.dir c:\Users?* Then if someone slips in a name similar to C:\Users, but with a character not covered in the list between the brackets (C:\User%, for example), at least only the directory structure will be backed up, but not the files. Yes, an include.dir option would be nice... Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. Joel Fuhrman <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 08/14/2001 18:35 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:backing up only 1 directory on Windows I have a Windows system running TSM client 4.2.0.0 from which I want to backup just the directory 'C:\Users' and all of its subdirectories and files. I don't want to backup any other directories or files from that system. I tried these dsm.opt specifications: exclude.dir "C:\*" include.dir "C:\Users\...*" A gui initiated incremental backup, excluded everything, including C:\Users\...\*, from the C: drive. Can you suggest the settings that will do what I want?
Re: Archiving vs. Incremental strategy
Big Brother tells me that Eduardo Martinez wrote: > Im trying to define a backup strategy that involves backing up my boxes > on a daily, weekly, monthly (full) and yearly (full) basis. > Daily backups will last only 3 days, weekly ones only three weeks, > monthly 3 months and yearly 3 years (because of taxes purposes). > > Is it a good strategy to mix archiving and incremental back ups with > this schema? > Since monthly and yearly are the ones which last more, will it be > convinient to archive these, and do an incremental on the other ones? > > I havent used too much the archive option, so I havent seen a real > useful usage of this option. A lot depends on how much data you actualy have, but... I would recommend that you do regular incremental backups of your data, and periodically make backupsets of your nodes (see GENERATE BACKUPSET). Alternately, you can EXPORT NODE FILEDATA=ALL all of your nodes to a set of tapes, which you can then date and store. Either of these will give you point in time restores to any point in time in which you exported or made a backupset. -- "There is no parameter that makes it impossibleJack McKinney for you to perform still more excellently." [EMAIL PROTECTED] -Mario Cuomo, on the lack of a clock in baseballhttp://www.lorentz.com 1024D/D68F2C07 4096g/38AEF076 PGP signature
backing up only 1 directory on Windows
I have a Windows system running TSM client 4.2.0.0 from which I want to backup just the directory 'C:\Users' and all of its subdirectories and files. I don't want to backup any other directories or files from that system. I tried these dsm.opt specifications: exclude.dir "C:\*" include.dir "C:\Users\...*" A gui initiated incremental backup, excluded everything, including C:\Users\...\*, from the C: drive. Can you suggest the settings that will do what I want?
Archiving vs. Incremental strategy
Im trying to define a backup strategy that involves backing up my boxes on a daily, weekly, monthly (full) and yearly (full) basis. Daily backups will last only 3 days, weekly ones only three weeks, monthly 3 months and yearly 3 years (because of taxes purposes). Is it a good strategy to mix archiving and incremental back ups with this schema? Since monthly and yearly are the ones which last more, will it be convinient to archive these, and do an incremental on the other ones? I havent used too much the archive option, so I havent seen a real useful usage of this option. Thanks in advance Regards. = "Do or Do Not, there is no try" -Yoda. The Empire Strikes Back ___ Do You Yahoo!? Yahoo! Messenger: Comunicacisn instantanea gratis con tu gente - http://messenger.yahoo.es
Re: Expiring DB2 backups
On Wed, Aug 15, 2001 at 12:39:06AM +0200, Eduardo Martinez wrote: > As you know, when you backup DB2 it stamps an unique id to its backup, > making it an active version forever, then you can't expire that backup. > Does anyone know how to expire this kind of backups? Use db2adutl's delete command to mark older versions for expiration. You can find the description of db2adutl in the db2 admin guide. -- bx "Seize the day - I heard him say - life will not always be this way, Look around, hear the sounds, cherish your life while you're still around."
Re: Database volhist
You can create a couple of admin schedules in order to get control over which volumes you use for TSM Database Backup: For example: a) backup db type=full devclass=your_dev_class volumenames=TAPE1,TAPE2,TAPE3,TAPE4 b) delete volhist type=dbbackup todate=today-3 You can schedule the delete volhist first, lets say 5 minutes before backup runs, in this way you ensure you have at least one tape available for your database backup. Hope this helps. Regards. --- Christian Astuni <[EMAIL PROTECTED]> escribis: > Fecha: Tue, 14 Aug 2001 14:13:35 -0300 > Responder a: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > De: Christian Astuni <[EMAIL PROTECTED]> > Asunto: Database volhist > Para: [EMAIL PROTECTED] > > I have a backup trigger as backup of ADSM database, and i have a pool > of 7 > volumes and I use one per day. > I run a backup full all the days. > When i want to reuse the first volumen, appearce a mesage as this: > > Scratch volume from library 3590LIB rejected - volume name is > already > in use. > > I want to delete this volume of the volume history, but I can't. I > specified al the parameters, but i receive a follow mesage: > 0 sequencial volume history entries were successfully deleted > > > Thank you very much for your help. > Regards Christian > > > Christian Astuni > IBM Global Services > > > = "Do or Do Not, there is no try" -Yoda. The Empire Strikes Back ___ Do You Yahoo!? Yahoo! Messenger: Comunicacisn instantanea gratis con tu gente - http://messenger.yahoo.es
Sleep Mode for MAC/PC
Does Tivoli wake up a MAC/PC from the sleep mode for a prompted schedule? How do I make this work, since Energy Saving is a major issue at my site. I have TSM Server 4.1 on Win2000 Server. Clients are MAC (75%) and PC(25%). People are used to Retrospect Backup which works even when the MAC is in the sleep mode. Any help is appreciated. Rajesh Oak Get 250 color business cards for FREE! http://businesscards.lycos.com/vp/fastpath/
Expiring DB2 backups
Hi *SMers. As you know, when you backup DB2 it stamps an unique id to its backup, making it an active version forever, then you can't expire that backup. Does anyone know how to expire this kind of backups? Thanks in advance. = "Do or Do Not, there is no try" -Yoda. The Empire Strikes Back ___ Do You Yahoo!? Yahoo! Messenger: Comunicacisn instantanea gratis con tu gente - http://messenger.yahoo.es
Re: AIX 4.3.3 list of excludable files & filesystems
Is the windows 2000 version available yet? On Mon, 13 Aug 2001, Ray Schafer wrote: > The Bare Metal Restore product from The Kernel Group > (http://www.tkg.com/products/bmr/tsm) has the ability to use the backup > data in TSM to recover your server. The "prepare to restore" operation > can be issued with a single command and will create a customized restore > procedure that will automatically recover the entire machine, or if you > prefer, just the rootvg. The prepare to restore operation will also > allocate the BMR file and boot server components so they will answer the > network boot and NFS requests of the server being recovered. > > It works well, and the restore is automated: prepare to restore and > network boot. That's it. > > Lisa Cabanas wrote: > > >Thanks for your reply, Herfried. It brings to mind some other questions > >regarding other volume groups. Say you have all your Oracle stuff on one > >or two different vgs. Would you need to have done a savevg sometime in > >the past to get the vg back, or at bare metal time would you need to > >manually create the volume group and lvs and fss associated with it, and > >then fill it with the data from TSM? > > > >I went and looked for a bare metal Redbook for AIX and found the one from > >1997 that deals with AIX 4.1-- is it still pretty applicable to 4.3.3? I > >wonder if TSM still "supports" a bare metal for AIX, or if it is now > >unsupported like Win2K is? > > > > > >thanks > >lisa > > > > > > > > > >Herfried Abel <[EMAIL PROTECTED]> > >08/09/2001 01:52 AM > >Please respond to "ADSM: Dist Stor Manager" > > > > > >To: [EMAIL PROTECTED] > >cc: (bcc: Lisa Cabanas/SC/MODOT) > >Subject:Re: AIX 4.3.3 list of excludable files & filesystems > > > > > > > >Lisa, > > > >All the filesystems within the rootvg are backed up with a mksysb as long > >as they are not explicit excluded from rthe mksysb. In general AIX does > >not > >delete (major) files on reboot as other UNIX's do ( eg /tmp ). > >This is how we do the restore of an AIX machine : > >1) restore mksysb > >2) restore "OS-definitions" via TSM ( rootvg filesystems eg. /etc ) ( TSM > >Client already restored by mksysb ) > >3) restore filesystems (non rootvg) via TSM > >4) restore application-data ( DBs eg. ORACLE,SAPDB, MSSQL etc ) via TDP > >Agents in necessary. > > > >Step 2) depends on the time-difference between the mksysb and the last > >config changes of AIX. Should not be necessary if you make a mksysb after > >every config change , as all of the sysadmins do :-) > > > >So what we do, we dont exclude files from the rootvg in the TSM backup ( > >AIX-OS is not really need much space ) but we exclude lots of temporary > >application files. We think that at this point we can find a lot of > >temporary data (eg. SAP rollfiles ).Of cause you have to know your > >application / Datebase very well, so that you dont exclude a file by > >mistake. > > > >herfried > > > > > > > > > > > >Lisa Cabanas <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 08.08.2001 > >18:20:26 > > > >Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > > >Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > > > > >To: [EMAIL PROTECTED] > >cc: > > > >Subject: AIX 4.3.3 list of excludable files & filesystems > > > > > >Has anyone ever compiled a list of files and/or file systems that can be > >excluded from backup either because they are dynamically created by the OS > >at > >reboot/syncvg etc > >or because they are included in a mksysb? > > > > > > > > > > > > > > > > > >The information contained in this transmission, which may be > >confidential and proprietary, is only for the intended recipients. > >Unauthorized use is strictly prohibited. If you receive this > >transmission in error, please notify me immediately by telephone > >or electronic mail and confirm that you deleted this transmission > >and the reply from your electronic mail system. > > > > > > >
Re: Need different files backuped on same Unix client.
OK, OK. Swapping inclexcl files is a bad idea. We all get one thoughtless post per year, don't we? ;-} > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of > Richard Sims > Sent: Tuesday, August 14, 2001 4:42 PM > To: [EMAIL PROTECTED] > Subject: Re: Need different files backuped on same Unix client. > > > >Well, Andy's right, of course. But if all you're doing is backing up > >ADDITIONAL files on Sunday, then the WEEKDAY files would still > be included. > > Swapping your include/exclude file is also problematic in that it does not > necessarily represent your full set of include-excludes: when > contemplating > changes to client options files always keep in mind that there may be > server-based Client Option Sets - or could suddenly be if there > aren't now, > depending upon server changes. > > Richard Sims, BU >
Re: Need different files backuped on same Unix client.
>Well, Andy's right, of course. But if all you're doing is backing up >ADDITIONAL files on Sunday, then the WEEKDAY files would still be included. Swapping your include/exclude file is also problematic in that it does not necessarily represent your full set of include-excludes: when contemplating changes to client options files always keep in mind that there may be server-based Client Option Sets - or could suddenly be if there aren't now, depending upon server changes. Richard Sims, BU
SCSI Multiplexer
TSMers, Is there any kind of restriction/know problem to interface a TSM Server and a tape library using a SCSI Multiplexer? Thanks, regards, Mauricio
TSM 4.2 client and UNICODE
I was just bitten by the UNICODE issue ("fioScanDirEntry(): Can't map object") with the TSM 4.2 client and a W2K server client. I did not realize there was a requirement to use the 4.2 client that also required the 4.2 server (no, I cannot install the TSM 4.2 server on OS390. Since it is a COST upgrade, I could not justfy it. The only way I got to 4.1.3 was because 3.1 had long expired). In fact, I thing the UNICODE issue has caused this client to go from 4-5GB backup to over 20GB (I canceled it after I saw all the errors in the DSMERROR.LOG file as well as the numerous blank and screwy entries in the DSMSCHED.LOG file). No, I can not ask the server owner to turn off UNICODE support since this is a university (note the "versity" part, as in "diversity"). Any way to get around this issue ? So far, the only thing I can figure is going back to the 4.1.3 client. === Zoltan Forray Virginia Commonwealth University University Computing Center e-mail: [EMAIL PROTECTED] voice: 804-828-4807
Re: Need different files backuped on same Unix client.
Well, Andy's right, of course. But if all you're doing is backing up ADDITIONAL files on Sunday, then the WEEKDAY files would still be included. Of course the SUNDAY files would be EXcluded on Monday, go into inactive status, and use the expiration versions/date parameters for deleted fileswhich, again, might be OK as long as you're aware of that. > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of > Andrew Raibeck > Sent: Tuesday, August 14, 2001 3:35 PM > To: [EMAIL PROTECTED] > Subject: Re: Need different files backuped on same Unix client. > > > I would definitely not recommend swapping include/exclude lists, as the > results are bound to be undesirable. The main reason is because EXCLUDE > not only excludes files from backup, but also expires any existing backup > versions of the excluded files. > > If you are looking to back up only a directory (or handful of > directories/files) during the week, then you might try this: > > 1) Define an incremental backup schedule that runs only on Sunday to back > up the entire machine. > > 2) Define a second backup schedule (incremental or selective, depending on > your needs) that runs on week-days, but also add the desired directories > to the OBJECTS setting in the schedule. For example: > >OBJECTS="/mylogs/" > > or > >OBJECTS="/mylogs/ /otherdir/*.log" > > etc. > > If you need to process subdirectories, then add the -SUBDIR=YES option to > the OPTIONS setting in the schedule. > > Don't exclude any files in your include/exclude list, unless they are > files that you *never* want to back up. > > Now the week-day schedule will back up only the files specified in the > schedule's OBJECTS setting, and the week-end schedule will process the > entire system. > > Regards, > > Andy > > Andy Raibeck > IBM Tivoli Systems > Tivoli Storage Manager Client Development > e-mail: [EMAIL PROTECTED] > > The only dumb question is the one that goes unasked. > The command line is your friend. > "Good enough" is the enemy of excellence. > > > > > > Lindsay Morris <[EMAIL PROTECTED]> > Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > 08/14/2001 12:03 > Please respond to lmorris > > > To: [EMAIL PROTECTED] > cc: > Subject:Re: Need different files backuped on same > Unix client. > > > > If you create two clients, TSM will treat them like two different > machines, > and you'll double the amount of storage used. > Maybe you're OK with that... > > What I'd try is setting up a cron job on sunday morning to run a script > like > this (untested - off top of head here): > > #!/bin/sh > # usage: chgincludes [ sunday | weekday ] > cd /usr/tivoli/tsm/client/ba/bin > cp inclexcl.$1 inclexcl > kill `ps -ef | fgrep dsmc sched | awk '{print $2}' ` > nohup dsmc sched & > > And in crontab > 0 0 * * 0 /my/scripts-dir/chgincludes sunday > 0 0 * * 1-6 /my/scripts-dir/chgincludes weekday > > And of course you'd have to manually set up your two include-exclude files > and name them inclexcl.sunday and inclexcl.weekday. And this assumes that > dsm.sys has a line in it like "inclexcl > /usr/tivoli/tsm/client/ba/bin/inclexcl" > > You could do the same trick using client option sets on the server, and an > administrative schedule instead of crontab. > > -Original Message- > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of > > Joe Spade > > Sent: Tuesday, August 14, 2001 2:51 PM > > To: [EMAIL PROTECTED] > > Subject: Need different files backuped on same Unix client. > > > > > > We are running TSM 4.1.3 server on a AIX system. The client on the same > > system is run with a schedule everynight to backup up certain log > > files. On Sunday we do an archive backup of all of the files. Thie > > archive backup takes to long (12 hours) and we would like to cut it down > > by using the normal incremental backup. I need to find a way to change > > the include-exclude file list on Sunday morning to insure a complete > > backup. I had heard that you can create two clients on the same > > system. If so, does anyone know how to do it and also how do you point > > it to a different dsm.sys and dsm.opt file? > > > > J. Spade > > R & L Carriers, Inc. >
Re: Need different files backuped on same Unix client.
I would definitely not recommend swapping include/exclude lists, as the results are bound to be undesirable. The main reason is because EXCLUDE not only excludes files from backup, but also expires any existing backup versions of the excluded files. If you are looking to back up only a directory (or handful of directories/files) during the week, then you might try this: 1) Define an incremental backup schedule that runs only on Sunday to back up the entire machine. 2) Define a second backup schedule (incremental or selective, depending on your needs) that runs on week-days, but also add the desired directories to the OBJECTS setting in the schedule. For example: OBJECTS="/mylogs/" or OBJECTS="/mylogs/ /otherdir/*.log" etc. If you need to process subdirectories, then add the -SUBDIR=YES option to the OPTIONS setting in the schedule. Don't exclude any files in your include/exclude list, unless they are files that you *never* want to back up. Now the week-day schedule will back up only the files specified in the schedule's OBJECTS setting, and the week-end schedule will process the entire system. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. Lindsay Morris <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 08/14/2001 12:03 Please respond to lmorris To: [EMAIL PROTECTED] cc: Subject:Re: Need different files backuped on same Unix client. If you create two clients, TSM will treat them like two different machines, and you'll double the amount of storage used. Maybe you're OK with that... What I'd try is setting up a cron job on sunday morning to run a script like this (untested - off top of head here): #!/bin/sh # usage: chgincludes [ sunday | weekday ] cd /usr/tivoli/tsm/client/ba/bin cp inclexcl.$1 inclexcl kill `ps -ef | fgrep dsmc sched | awk '{print $2}' ` nohup dsmc sched & And in crontab 0 0 * * 0 /my/scripts-dir/chgincludes sunday 0 0 * * 1-6 /my/scripts-dir/chgincludes weekday And of course you'd have to manually set up your two include-exclude files and name them inclexcl.sunday and inclexcl.weekday. And this assumes that dsm.sys has a line in it like "inclexcl /usr/tivoli/tsm/client/ba/bin/inclexcl" You could do the same trick using client option sets on the server, and an administrative schedule instead of crontab. > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of > Joe Spade > Sent: Tuesday, August 14, 2001 2:51 PM > To: [EMAIL PROTECTED] > Subject: Need different files backuped on same Unix client. > > > We are running TSM 4.1.3 server on a AIX system. The client on the same > system is run with a schedule everynight to backup up certain log > files. On Sunday we do an archive backup of all of the files. Thie > archive backup takes to long (12 hours) and we would like to cut it down > by using the normal incremental backup. I need to find a way to change > the include-exclude file list on Sunday morning to insure a complete > backup. I had heard that you can create two clients on the same > system. If so, does anyone know how to do it and also how do you point > it to a different dsm.sys and dsm.opt file? > > J. Spade > R & L Carriers, Inc.
Re: Need different files backuped on same Unix client.
> We are running TSM 4.1.3 server on a AIX system. The client on the same > system is run with a schedule everynight to backup up certain log > files. On Sunday we do an archive backup of all of the files. Thie > archive backup takes to long (12 hours) and we would like to cut it down > by using the normal incremental backup. I need to find a way to change > the include-exclude file list on Sunday morning to insure a complete > backup. I had heard that you can create two clients on the same > system. If so, does anyone know how to do it and also how do you point > it to a different dsm.sys and dsm.opt file? Joe - I would approach the everynight differently, to simplify things. Nightly, I would run a Selective backup to back up the log files, eliminating the need for the Include spec that otherwise complicates your life. The Sunday Incremental would thus process the whole file system without impediment. Richard Sims, BU
Re: Need different files backuped on same Unix client.
If you create two clients, TSM will treat them like two different machines, and you'll double the amount of storage used. Maybe you're OK with that... What I'd try is setting up a cron job on sunday morning to run a script like this (untested - off top of head here): #!/bin/sh # usage: chgincludes [ sunday | weekday ] cd /usr/tivoli/tsm/client/ba/bin cp inclexcl.$1 inclexcl kill `ps -ef | fgrep dsmc sched | awk '{print $2}' ` nohup dsmc sched & And in crontab 0 0 * * 0 /my/scripts-dir/chgincludes sunday 0 0 * * 1-6 /my/scripts-dir/chgincludes weekday And of course you'd have to manually set up your two include-exclude files and name them inclexcl.sunday and inclexcl.weekday. And this assumes that dsm.sys has a line in it like "inclexcl /usr/tivoli/tsm/client/ba/bin/inclexcl" You could do the same trick using client option sets on the server, and an administrative schedule instead of crontab. > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of > Joe Spade > Sent: Tuesday, August 14, 2001 2:51 PM > To: [EMAIL PROTECTED] > Subject: Need different files backuped on same Unix client. > > > We are running TSM 4.1.3 server on a AIX system. The client on the same > system is run with a schedule everynight to backup up certain log > files. On Sunday we do an archive backup of all of the files. Thie > archive backup takes to long (12 hours) and we would like to cut it down > by using the normal incremental backup. I need to find a way to change > the include-exclude file list on Sunday morning to insure a complete > backup. I had heard that you can create two clients on the same > system. If so, does anyone know how to do it and also how do you point > it to a different dsm.sys and dsm.opt file? > > J. Spade > R & L Carriers, Inc. >
Need different files backuped on same Unix client.
We are running TSM 4.1.3 server on a AIX system. The client on the same system is run with a schedule everynight to backup up certain log files. On Sunday we do an archive backup of all of the files. Thie archive backup takes to long (12 hours) and we would like to cut it down by using the normal incremental backup. I need to find a way to change the include-exclude file list on Sunday morning to insure a complete backup. I had heard that you can create two clients on the same system. If so, does anyone know how to do it and also how do you point it to a different dsm.sys and dsm.opt file? J. Spade R & L Carriers, Inc.
Re: Database volhist
Yes Richard, when I need to delete one volume to the backup series, because I need to reuse the volume. When run the comman " q volhist t=dbb" I saw the 7 volumes with series 1 ... 2 ... 3 ... up to 7. How is the correct form to delete this ? Because i try with the command " delete volhist t=dbb tod=, and i can't ... Thnk yuo very much. Christian Astuni IBM Global Services [EMAIL PROTECTED] Tel. 4898-4621 Hipolito Yrigoyen 2149 - Martínez (1640) Bs. As. - Argentina Richard Sims <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Sent by: cc: "ADSM: Dist Subject: Re: Database volhist Stor Manager" <[EMAIL PROTECTED] IST.EDU> 14/08/2001 14:55 Please respond to "ADSM: Dist Stor Manager" >I have a backup trigger as backup of ADSM database, and i have a pool of 7 >volumes and I use one per day. >I run a backup full all the days. >When i want to reuse the first volumen, appearce a mesage as this: > >Scratch volume from library 3590LIB rejected - volume name is already >in use. > >I want to delete this volume of the volume history, but I can't. I >specified al the parameters, but i receive a follow mesage: >0 sequencial volume history entries were successfully deleted Christian - I suspect that you are trying to delete one volume from a Backup Series, as in the Full that the subsequent Incremental(s) is/are dependent upon. Use Query VOLHistory to inspect it in context. Try to invoke DELete VOLHistory so that one whole, old Series is deleted. Richard Sims, BU
Re: Database volhist
I try to delete with grafich interface and the command line with: delete volhist tod=x t=dbb Christian Astuni IBM Global Services [EMAIL PROTECTED] Tel. 4898-4621 Hipolito Yrigoyen 2149 - Martínez (1640) Bs. As. - Argentina "Prather, Wanda" cc: Sent by: "ADSM:Subject: Re: Database volhist Dist Stor Manager" <[EMAIL PROTECTED] T.EDU> 14/08/2001 14:58 Please respond to "ADSM: Dist Stor Manager" What command did you use? -Original Message- From: Christian Astuni [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 14, 2001 1:14 PM To: [EMAIL PROTECTED] Subject: Database volhist I have a backup trigger as backup of ADSM database, and i have a pool of 7 volumes and I use one per day. I run a backup full all the days. When i want to reuse the first volumen, appearce a mesage as this: Scratch volume from library 3590LIB rejected - volume name is already in use. I want to delete this volume of the volume history, but I can't. I specified al the parameters, but i receive a follow mesage: 0 sequencial volume history entries were successfully deleted Thank you very much for your help. Regards Christian Christian Astuni IBM Global Services
Re: Database volhist
>I have a backup trigger as backup of ADSM database, and i have a pool of 7 >volumes and I use one per day. >I run a backup full all the days. >When i want to reuse the first volumen, appearce a mesage as this: > >Scratch volume from library 3590LIB rejected - volume name is already >in use. > >I want to delete this volume of the volume history, but I can't. I >specified al the parameters, but i receive a follow mesage: >0 sequencial volume history entries were successfully deleted Christian - I suspect that you are trying to delete one volume from a Backup Series, as in the Full that the subsequent Incremental(s) is/are dependent upon. Use Query VOLHistory to inspect it in context. Try to invoke DELete VOLHistory so that one whole, old Series is deleted. Richard Sims, BU
Re: Database volhist
What command did you use? -Original Message- From: Christian Astuni [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 14, 2001 1:14 PM To: [EMAIL PROTECTED] Subject: Database volhist I have a backup trigger as backup of ADSM database, and i have a pool of 7 volumes and I use one per day. I run a backup full all the days. When i want to reuse the first volumen, appearce a mesage as this: Scratch volume from library 3590LIB rejected - volume name is already in use. I want to delete this volume of the volume history, but I can't. I specified al the parameters, but i receive a follow mesage: 0 sequencial volume history entries were successfully deleted Thank you very much for your help. Regards Christian Christian Astuni IBM Global Services
Re: Client Backup Issue
Hi Richard, I was a customer at the time ADSM came out, so I was not privy to the original design. However, it is likely that the answer lies, at least in part, with RESTORE syntax, where we need to know whether the file spec is a directory or file (i.e. do we search high-level names or low-level names in the TSM database). Also, it is possible to have a file named 'A', back it up, delete it, create a directory called 'A', then back it up. So now you would have a directory named 'A' and a file named 'A'. The terminating backslash helps resolve the ambiguity. Another case is when you wish to restore to an alternate location. You need to specify the backslash on the target file spec (if it does not exist on the client file system) to indicate that the target is a directory, not a file name. For example, if I have a directory named DIR with nothing else in it except for a file named FILE, then I could say, res c:\dir\file c:\dir\x or res c:\dir\file c:\dir\x\ In the first case, the file would be restored as name 'x' in the 'DIR' directory. In the second case, the file would be restored as name 'file' in the DIR\x directory. Requiring the backslash on the backup file spec when dealing with a directory helps keep the syntax consistent. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. Richard Sims <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 08/14/2001 04:40 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: Client Backup Issue >In the schedule settings, you should change the OBJECTS from: > > C:\TSM Backup > >to > > C:\TSM Backup\ > >unless you only want to back up the single file or directory named "TSM >Backup", but I doubt that is what you want. Andy - I have to ask: why does the software require customers to add a slash or backslash (depending upon architecture type) to the end of a specification for the client to know that the object is a directory? As a programmer, I would write the software to simply test for the actual object being a directory or not, rather than silently fail to process the directory. That is, if the customer said to back up XYZ, I would do so upon discovering the existence of the object, be it a file or directory. The slash-backslash requirement is counter-intuitive for customers in general, where operating system commands never require adding a special character to the end of a spec to say that the object is a directory: such commands simply proceed to honor the invoker's request and process the object as found. This special TSM requirement needlessly confuses many customers, and is a pet peeve with the product. Richard Sims, BU
Database volhist
I have a backup trigger as backup of ADSM database, and i have a pool of 7 volumes and I use one per day. I run a backup full all the days. When i want to reuse the first volumen, appearce a mesage as this: Scratch volume from library 3590LIB rejected - volume name is already in use. I want to delete this volume of the volume history, but I can't. I specified al the parameters, but i receive a follow mesage: 0 sequencial volume history entries were successfully deleted Thank you very much for your help. Regards Christian Christian Astuni IBM Global Services
Re: TSM Win2K 4.2.0 client scheduler problems
Check the adsm-l archives at www.adsm.org for my response back on August 9 with regard to this issue. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. Jeff Bach <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 08/14/2001 06:00 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: TSM Win2K 4.2.0 client scheduler problems This sounds like a bad design. How about a Correction of the Design process? Jeff Bach -Original Message- From: Eliza Lau [SMTP:[EMAIL PROTECTED]] Sent: Thursday, August 09, 2001 3:49 PM To: [EMAIL PROTECTED] Subject:Re: TSM Win2K 4.2.0 client scheduler problems I just got off the phone with TSM level 2 support. This is a known problem with the Windows 2000 4.2.0 client. It is a timing issue. The client can't get the password from the server and tries 3 times. A second later it gets it. The developers have no fixes for this, no APAR either. They may just document it as "working as designed". Beside getting these erroneous errors in dsmerror.log and the event log, scheduled backup works just fine. Eliza > > I have the excact same experience - and have found no other solution than to > go back to TSM v4.1 lev. 2.19. Then the problem was gone. > > Server: TSM v4.1 lev 1.0 on OS/390 > Client: Windows NT 4.0, SP6 > > Henrik Bach Gravesen > Jyske Bank A/S, Denmark > [EMAIL PROTECTED] > > > > > A user of mine is using the TSM Win2K 4.2.0 client acceptor > > service to manage > > the client scheduler. The acceptor service wakes the > > scheduler every 12 hours > > and starts the scheduled backup with no problems. All is well except > > that she is getting the error code 4099 in the application > > event log every time > > the scheduler wakes up (every 12 hours). In dsmerrorlog, > >SessOpen: Error 137 from signon authentication (3 times) > > > > Password is set to generate. GUI, command line, and > > scheduled backups all > > run fine. The user is not prompted for the password. So > > there must not be > > any authenication problems and the password is stored in the registry. > > > > Has anyone seen this with their W2K 4.2.0 clients? Is this > > normal behavior? > > > > server - TSM 4.1.3 on AIX 4.3.3 > > client - Windows 2000 4.2.0 > > > > Thanks in advance, > > Eliza Lau > > Virginia Tech Computing Center > > [EMAIL PROTECTED] > > 540-231-9399 > > > ** This email and any files transmitted with it are confidential and intended solely for the individual or entity to whom they are addressed. If you have received this email in error destroy it immediately. **
Re: TSM Job "release"
>...The nightly scheduling of administrator >scripts will not work for me as the window for running >the jobs varies from night to night, thus the need to >"release" or run these scripts at appropriate >(varying) times. Anyone met this challenge? Rod - You could try a variant of the "bkup_stg_db" server script which is provided at the bottom of the scripts.smp file, which detects a certain deterring condition and reschedules itself to try again in 20 minutes. That is, you can have a server script scheduled to start trying at a certain time of night, and keep trying if a given condition is met...something as trivial as an operator session present/absent, to trigger the job. Lots of flexibility there. Richard Sims, BU
Re: Strange message from API client
> We have Version 1.1 of Tivoli Data Protection for Microsoft SQL Server > installed on a Windows NT system here. Yesterday I attempted to obtain > a list of database backups using the command 'sqldsmc /adsmquerydb'. > The command failed with the message 'ANS1245E Format unknown'. This > is strange on two counts. The message is documented as coming from the > command line client of the TSM client code. The message is documented > as occuring during attempts to retrieve or restore files, not during > queries. Can anyone shed any light on this? Thomas, This usually means that you have back-leveled your TSM API in some fashion or another. Once you use a later level TSM API to run backups, many times you cannot use a lower level TSM API anymore because the data is stored in a new "format" that older levels of the TSM API do not know about. Make sense at all? The message is coming from the TSM API and displayed by TDP for SQL. Upgrade your TSM API and retry. Thanks, Del Del Hoobler IBM Corporation [EMAIL PROTECTED] "It's a beautiful day. Don't let it get away." -- Bono Thomas Denier cc: Sent by: "ADSM: Subject: Strange message from API client Dist Stor Manager" <[EMAIL PROTECTED] EDU> 08/14/2001 11:25 AM Please respond to "ADSM: Dist Stor Manager"
TDP for Oracle
Does anyone know the answer to the following: Will Tivoli be implementing TDP for Oracle on True 64 anytime in the near future/or at all? You would think since Oracle spent time and money to develop Oracle to run on it Tivoli would too Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (888) 997-9614
TSM Job "release"
I'm looking for a way to have my operators run my nightly DB backup and Copypool backup scripts at an appropriate time. Set times available via administrator schedules will not work for me. The other challenge is to allow my operators to run nightly scripts without having an authority other than operator. I believe at least the DB backup requires more than operator priviledge (maybe system), and I don't want to give them the ability to compromise my system. The nightly scheduling of administrator scripts will not work for me as the window for running the jobs varies from night to night, thus the need to "release" or run these scripts at appropriate (varying) times. Anyone met this challenge? Rod Hroblak ADP __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/
Strange message from API client
We have Version 1.1 of Tivoli Data Protection for Microsoft SQL Server installed on a Windows NT system here. Yesterday I attempted to obtain a list of database backups using the command 'sqldsmc /adsmquerydb'. The command failed with the message 'ANS1245E Format unknown'. This is strange on two counts. The message is documented as coming from the command line client of the TSM client code. The message is documented as occuring during attempts to retrieve or restore files, not during queries. Can anyone shed any light on this?
Re: ADSM Monitor ...
Yes, I would like a copy. Thanks, Walt Schilling -Original Message- From: Sean Voyce [mailto:[EMAIL PROTECTED]] Sent: Monday, August 13, 2001 10:11 PM To: [EMAIL PROTECTED] Subject:ADSM Monitor ... Hi, A long time ago, I offered the list my ADSM Monitor. Today I'm offering my new improved deluxe version to anyone who wants a copy. This is an HTML interface to a monitor that checks at regular intervals for outstanding tape mounts. The "Lazy Operator" (that's me) can then mount the tape and click a button on his/her favorite browser to keep ADSM happy. Outstanding requests etc are effectively highlighted ;-) There are of course plenty of other features to make life easier, and this version also traps some of the common errors that our site manages to produce. (Adding more traps is easy to do). A slight re-write has made the whole thing a bit more "user friendly", halved the code base, saved a few dolphins and bought peace to computer rooms the world over. To run this you will need (or be able to convert from) ... A *nix machine (ours is AIX on RS/6000) capable of issuing "dsmadmc" commands (ie running ADSM) from a shell script, running a web server (we're using Apache), and PERL. (I'm sure I can ditch the PERL - it's only used in a very small cgi script. More research needed). I don't have an install script, and you will need to change a few settings here and there to suit your site. I have tried to make this as easy as possible though - maybe an hour to install and make any required changes. If you would like a copy, email me (seanv) at woolworths.co.nz - I'll respond ASAP. (It is of course FREE and less than 140k in size). To those who tried the old version - this one looks pretty much the same ... more functions & better code though. Well worth an upgrade. Sean Voyce. DISCLAIMER: "The information in this email and in any attachments is confidential and intended solely for the attention and use of the addressee(s). If this email is not intended for you, you must not use, read, distribute or copy it. If you have received this email by mistake please call the sender immediately on 64-9-2620772 and erase the email and any attachments, and any copies of the same. Internet communications are not secure and therefore Woolworths (NZ) Ltd does not accept legal responsibility for the contents of this message. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Woolworths (NZ) Ltd unless specifically stated."
Re: ADSM versions
http://www.tivoli.com/support/storage_mgr/requirements.html Will get you close. http://www.tivoli.com/support/storage_mgr/clients.html#hp Will get you dead on. Tons of information available here. 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 Evans, William C Sent: Tuesday, August 14, 2001 8:51 AM To: [EMAIL PROTECTED] Subject: ADSM versions Listers, I need to know the latest version of the ADSM client that will run on an HP v10.20 server. TIA, Bill Evans, UNIX System Administrator Phone: 719.535.4194 E-mail: [EMAIL PROTECTED] Pager: 1-800-pagemci PIN 1438754 AIM: bievans4194 <<...OLE_Obj...>> the recognized global leader in ensuring clients achieve superior value in the digital economy
ADSM versions
Listers, I need to know the latest version of the ADSM client that will run on an HP v10.20 server. TIA, Bill Evans, UNIX System Administrator Phone: 719.535.4194 E-mail: [EMAIL PROTECTED] Pager: 1-800-pagemci PIN 1438754 AIM: bievans4194 <<...OLE_Obj...>> the recognized global leader in ensuring clients achieve superior value in the digital economy
Stan Vernaillen is out of the office
I will be out of the office from 13/08/2001 until 20/08/2001. If you have any RS6000, E-server Pseries, AIX, Unix, SAP, APO, TSM, Milestone, Whatever issues, Please Contact Bruno Misseeuw at +32 2 529 14 28 or The ESC or < anyone but me >
Re: Upgrade Causes 30% more data?
1. What are the clients and client software levels? If there are a number of Win2K clients running at least TSM 3.7.2, changing the server from 3.1 to TSM 4.1 turns on the support for "SYSTEM OBJECT" backups, which causes most of the .dll and .exe files in the Windows/system32 directory to be backed up every day, whether changed or not. It's about 200MB per client per day additional, IF you have compression turned on, more without compression. We have 200+ Win2K clients; caused us a significant increase in the amount of data per day, plus significant growth of the TSM data base.. 2. Don't know 3. 1 implies 3 4. 2 will cause 4 -Original Message- From: Mark [mailto:[EMAIL PROTECTED]] Sent: Monday, August 13, 2001 6:00 PM To: [EMAIL PROTECTED] Subject: Upgrade Causes 30% more data? Hi all My customer upgraded ADSM 3.1 to TSM 4.1. Since the upgrade he has a number of problems which I believe could all be interelated. The symptoms are as follows: 1. 30% more data. 2. Less expiration going on. 3. Running out of scratch tapes 4. Reclamation used to free up scratch tape but this seems to be happening less frequently. Any ideas folks? Mark
media mount not possible
Hi: I've 1). added a copy group for archives of Novell files 2). validated and activated the policy When the Novell admin goes to do archives he gets: ANS1312E Server media mount not possible, yet the drives are available. Any suggestions? Policy Domain Name: NOVELL Policy Set Name: ACTIVE Mgmt Class Name: NOVCLASS Copy Group Name: STANDARD Copy Group Type: Archive Retain Version: 60 Copy Serialization: Dynamic Copy Frequency: CMD Copy Mode: Absolute Copy Destination: NOVARCHIV Last Update by (administrator): ADMIN Last Update Date/Time: 08/13/01 13:23:32 Managing profile: Storage Pool Name: NOVARCHIV Storage Pool Type: Primary Device Class Name: 3494BTAPE Estimated Capacity (MB): 0.0 Pct Util: 0.0 Pct Migr: 0.0 Pct Logical: 100.0 High Mig Pct: 90 Low Mig Pct: 70 Migration Delay: 0 Migration Continue: Yes Migration Processes: Next Storage Pool: Reclaim Storage Pool: Maximum Size Threshold: No Limit Access: Read/Write Description: Novell arch Overflow Location: Cache Migrated Files?: Collocate?: No Reclamation Threshold: 60 Maximum Scratch Volumes Allowed: 60 Delay Period for Volume Reuse: 0 Day(s) Migration in Progress?: No Amount Migrated (MB): 0.00 Elapsed Migration Time (seconds): 0 Reclamation in Progress?: No Volume Being Migrated/Reclaimed: Last Update by (administrator): ADMIN Last Update Date/Time: 08/13/01 13:20:40 Policy Domain Name: NOVELL Policy Set Name: ACTIVE Default Mgmt Class Name: NOVCLASS Description: Last Update by (administrator): ADMIN Last Update Date/Time: 06/25/01 14:33:33 Managing profile: Policy Domain Name: NOVELL Policy Set Name: NOVELLPOL Default Mgmt Class Name: NOVCLASS Description: Last Update by (administrator): ADMIN Last Update Date/Time: 06/25/01 14:33:33 Managing profile: tsm: BACKUP>q copy type=arch PolicyPolicyMgmt CopyRetain DomainSet Name Class Group Version NameName Name - - - - NOVELLACTIVENOVCLASS STANDARD60 NOVELLNOVELLPOL NOVCLASS STANDARD60
Re: TSM Win2K 4.2.0 client scheduler problems
This sounds like a bad design. How about a Correction of the Design process? Jeff Bach -Original Message- From: Eliza Lau [SMTP:[EMAIL PROTECTED]] Sent: Thursday, August 09, 2001 3:49 PM To: [EMAIL PROTECTED] Subject:Re: TSM Win2K 4.2.0 client scheduler problems I just got off the phone with TSM level 2 support. This is a known problem with the Windows 2000 4.2.0 client. It is a timing issue. The client can't get the password from the server and tries 3 times. A second later it gets it. The developers have no fixes for this, no APAR either. They may just document it as "working as designed". Beside getting these erroneous errors in dsmerror.log and the event log, scheduled backup works just fine. Eliza > > I have the excact same experience - and have found no other solution than to > go back to TSM v4.1 lev. 2.19. Then the problem was gone. > > Server: TSM v4.1 lev 1.0 on OS/390 > Client: Windows NT 4.0, SP6 > > Henrik Bach Gravesen > Jyske Bank A/S, Denmark > [EMAIL PROTECTED] > > > > > A user of mine is using the TSM Win2K 4.2.0 client acceptor > > service to manage > > the client scheduler. The acceptor service wakes the > > scheduler every 12 hours > > and starts the scheduled backup with no problems. All is well except > > that she is getting the error code 4099 in the application > > event log every time > > the scheduler wakes up (every 12 hours). In dsmerrorlog, > >SessOpen: Error 137 from signon authentication (3 times) > > > > Password is set to generate. GUI, command line, and > > scheduled backups all > > run fine. The user is not prompted for the password. So > > there must not be > > any authenication problems and the password is stored in the registry. > > > > Has anyone seen this with their W2K 4.2.0 clients? Is this > > normal behavior? > > > > server - TSM 4.1.3 on AIX 4.3.3 > > client - Windows 2000 4.2.0 > > > > Thanks in advance, > > Eliza Lau > > Virginia Tech Computing Center > > [EMAIL PROTECTED] > > 540-231-9399 > > > ** This email and any files transmitted with it are confidential and intended solely for the individual or entity to whom they are addressed. If you have received this email in error destroy it immediately. **
Re: cann't start adsm serv---Urgent
Yes , after upgrade to ver 3.7.4 dsmserv started successfuly.Thanks to all for help. Thomas Gaines cc: (bcc: MUSTAFA BAYTAR/ATIM/ICECEK) Sent by: Subject: Re: cann't start adsm serv---Urgent "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] IST.EDU> 14.08.2001 13:14 Please respond to "ADSM: Dist Stor Manager" Mustafa, I encountered the same problem after installing drivers for ATM NIC's on TSM v3.7.3; NT. I didn't want to restore the database, since the last one that had run had failed. Since it was unlikely support would address it until it was the latest fix level, I installed v.3.7.4 patch. The server started up fine after this. Cheers, Thomas. MUSTAFA BAYTAR <[EMAIL PROTECTED]> on 08/14/2001 07:31:00 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc:(bcc: Thomas Gaines/TO/SYD/IIBG) Subject: cann't start adsm serv---Urgent Hi TSM'ers wneh im traying to start TSM server it stops at the Recovery log volume mount in progress and cannot continue. that happened after EMC Fibre Channel interface driver installation. [tivolisrv@root]dsmserv ANR7800I DSMSERV generated at 23:08:28 on Apr 22 2000. Tivoli Storage Manager for AIX-RS/6000 Version 3, Release 7, Level 3.0 Licensed Materials - Property of IBM 5697-TSM (C) Copyright IBM Corporation 1999. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR0900I Processing options file dsmserv.opt. ANR0990I Server restart-recovery in progress. ANR0200I Recovery log assigned capacity is 600 megabytes. ANR0201I Database assigned capacity is 1000 megabytes. ANR0306I Recovery log volume mount in progress. any ideas
Re: SQL-BACKTRACK & ORACLE
We use sql-backtrack for Sybase, but not Oracle - never wanted to spend the money. We've also looked at RMAN, but rejected it for various reasons. The incremental hot seems good, but you're still just pulling out changed blocks, which is basically whats in the logs. The vast majority of our oracle databases run a hot once a week and full export on the other 6 nights as an integrity check. Logs are backed up nightly to tsm. On certain large and active databases, we run hots 3 times a week with 4 full exports. There is a lot of log activity on these systems, so we backup the logs to tsm each hour. All of our Hot backups are performed by a multi-threaded ksh script that creates a compressed backup on disk. The current project is to modify this script to handle raw volumes. Rick On 13 Aug 2001, at 15:49, Thiha Than wrote: > hi, > > >Our oracle DBA claims that 'hot' incremental backups of Oracle takes as = > >long as 'hot' full backups using SQL-BACKTRACK. Instead he does weekly = > >full 'hot' backups of the database and backups of the redo logs thru the > = > >week. > > >Is that how others using SQL-BACKTRACK and ORACLE do thier backups? > > > It's the same for backing up oracle databases using RMAN, incremental > takes almost as long as a full backup. I have never used sql-backtrack > before so I cannot comment on it. With RMAN, it has to scan through every > single Oracle data block to find the changed block. So the incremental > backup will take a long time, but the amount of data sent through can be > significantly less. > > regards, > Thiha >
Re: EMC, Timefinder, Oracle, and TSM
In general, yes you can. How were you planning to perform the bcv split? The normal ways are to either shutdown Oracle (cold backup) or put Oracle into backup mode (hot backup). Either way, once restored you can force oracle into recovery mode and roll forward through any logs. Yes, you will have to run in archive-log mode. Rick On 13 Aug 2001, at 20:52, E. J. wrote: > I have an Oracle DB on Sun in an EMC with Timefinder. > The plan is to use Timefinder to create BCV's of the > DB and then back up the BCV's to TSM. Question: How > can I use the BCV's and still provide the ability to > restore to the most recent point in time? If the > entire database is backed-up by attaching the BCV's to > a Backup Server then out to TSM, can the redo logs > created on the DB Server be applied to the full DB > backup taken via the BCVs and Backup Server? > > EJ > > > __ > Do You Yahoo!? > Make international calls for as low as $.04/minute with Yahoo! Messenger > http://phonecard.yahoo.com/ >
Re: Off Topic 3494 question.
>I have an AS400 connected to two drives in the 3494 which I theoretically >control. I use the other two drives for TSM on an RS6000. This AS400 is not >configured to communicate with the library and they are having trouble doing so >- for the last 9 months. They back up by opening the library and inserting >tapes directly into the drives. Good grief! In the absence of a 3494 device driver for AS/400, I would simply set up a mount server agent for them on your AIX system, which would perform mounts using either the 'mtlib' command or directly via ioctl() C functions, with filtration to assure that they don't conflict with your two drives (or tapes), and don't try to mount over an already-busy drive of theirs. I'm not familiar with AS/400 facilities: maybe they could use rsh to send their mount requests to your AIX-based agent - or at very worst case, email requests (yes, I've had to work with even that type). Dismounts are strictly drive-oriented events, so you would not have to be involved in that phase. Ejections from the library could also be handled by your agent. Email me directly, Steve, if you would like to hash this over more. Richard Sims, BU [EMAIL PROTECTED]
24x7 Policies and Procedures
Hi Everyone - Does anyone have documented policies and procedures for a 24x7 operation with TSM. I've been asked to put something together on what it would take to have 24x7 coverage for TSM. I don't need the "how to" docs for specific TSM procedures. Or if there is a manual or website you could point me to, that would be great also. Thanks, Diana
Re: cann't start adsm serv---Urgent
>wneh im traying to start TSM server it stops at the Recovery log volume mount in >progress and >cannot continue. You'll see many such postings in the www.adsm.org archives, with customers at 3.7.3, as you are. Going to 3.7.4 has solved such problems in the past, though your recent Fibre Channel interface driver installation may pose an additional issue for you. Richard Sims, BU
Re: Client Backup Issue
>In the schedule settings, you should change the OBJECTS from: > > C:\TSM Backup > >to > > C:\TSM Backup\ > >unless you only want to back up the single file or directory named "TSM >Backup", but I doubt that is what you want. Andy - I have to ask: why does the software require customers to add a slash or backslash (depending upon architecture type) to the end of a specification for the client to know that the object is a directory? As a programmer, I would write the software to simply test for the actual object being a directory or not, rather than silently fail to process the directory. That is, if the customer said to back up XYZ, I would do so upon discovering the existence of the object, be it a file or directory. The slash-backslash requirement is counter-intuitive for customers in general, where operating system commands never require adding a special character to the end of a spec to say that the object is a directory: such commands simply proceed to honor the invoker's request and process the object as found. This special TSM requirement needlessly confuses many customers, and is a pet peeve with the product. Richard Sims, BU
Re: cann't start adsm serv---Urgent
Hi, is it still running ? It can take a long time. Normally you get an error message in case of problems (in TSM, in the OS, in the EMC subsystem...) Regards, 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: MUSTAFA BAYTAR [SMTP:[EMAIL PROTECTED]] > Sent: Tuesday, August 14, 2001 11:31 AM > To: [EMAIL PROTECTED] > Subject: cann't start adsm serv---Urgent > > Hi TSM'ers > > wneh im traying to start TSM server it stops at the Recovery log volume > mount in progress and > cannot continue. > that happened after EMC Fibre Channel interface driver installation. > > [tivolisrv@root]dsmserv > ANR7800I DSMSERV generated at 23:08:28 on Apr 22 2000. > > Tivoli Storage Manager for AIX-RS/6000 > Version 3, Release 7, Level 3.0 > > Licensed Materials - Property of IBM > > 5697-TSM (C) Copyright IBM Corporation 1999. All rights reserved. > U.S. Government Users Restricted Rights - Use, duplication or disclosure > restricted by GSA ADP Schedule Contract with IBM Corporation. > > ANR0900I Processing options file dsmserv.opt. > ANR0990I Server restart-recovery in progress. > ANR0200I Recovery log assigned capacity is 600 megabytes. > ANR0201I Database assigned capacity is 1000 megabytes. > ANR0306I Recovery log volume mount in progress. > > > any ideas
Re: cann't start adsm serv---Urgent
Mustafa, I encountered the same problem after installing drivers for ATM NIC's on TSM v3.7.3; NT. I didn't want to restore the database, since the last one that had run had failed. Since it was unlikely support would address it until it was the latest fix level, I installed v.3.7.4 patch. The server started up fine after this. Cheers, Thomas. MUSTAFA BAYTAR <[EMAIL PROTECTED]> on 08/14/2001 07:31:00 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc:(bcc: Thomas Gaines/TO/SYD/IIBG) Subject: cann't start adsm serv---Urgent Hi TSM'ers wneh im traying to start TSM server it stops at the Recovery log volume mount in progress and cannot continue. that happened after EMC Fibre Channel interface driver installation. [tivolisrv@root]dsmserv ANR7800I DSMSERV generated at 23:08:28 on Apr 22 2000. Tivoli Storage Manager for AIX-RS/6000 Version 3, Release 7, Level 3.0 Licensed Materials - Property of IBM 5697-TSM (C) Copyright IBM Corporation 1999. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR0900I Processing options file dsmserv.opt. ANR0990I Server restart-recovery in progress. ANR0200I Recovery log assigned capacity is 600 megabytes. ANR0201I Database assigned capacity is 1000 megabytes. ANR0306I Recovery log volume mount in progress. any ideas
cann't start adsm serv---Urgent
Hi TSM'ers wneh im traying to start TSM server it stops at the Recovery log volume mount in progress and cannot continue. that happened after EMC Fibre Channel interface driver installation. [tivolisrv@root]dsmserv ANR7800I DSMSERV generated at 23:08:28 on Apr 22 2000. Tivoli Storage Manager for AIX-RS/6000 Version 3, Release 7, Level 3.0 Licensed Materials - Property of IBM 5697-TSM (C) Copyright IBM Corporation 1999. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR0900I Processing options file dsmserv.opt. ANR0990I Server restart-recovery in progress. ANR0200I Recovery log assigned capacity is 600 megabytes. ANR0201I Database assigned capacity is 1000 megabytes. ANR0306I Recovery log volume mount in progress. any ideas