FW: TSM data on tape
From: Viljoen Corrie* arivia.kom (GP) Sent: Thursday, March 22, 2001 2:42 PM To: Moodley Desigan * arivia.kom (GP) Subject: TSM data on tape We are using 3480 / 3490 and 3490E tape technology with Silverton and Timberline drives for storing data via TSM software. We are experiencing problems for a while now with running out of tapes in all our storage pools and it is growing by the day. We are already occupying at least more than 5000 tapes in our NEARLINES. The reclamation processes are running everyday. There is a situation where I looked at all my volumes and realized that only a maximum of 900 MB is stored on a 2.3 GB tape. TSM then marks the tape as full. While it is writing it shows at a stage that only 35% odd is utilized on the 2.3 GB tape because it is 900 MB of 2.3 GB but then it stops and marks the tape as full. The message is ANR5334W to say that the end of the volume was reached before the maximum capacity of the tape which is suppose to be 2.3 GB at least. We tested the same volume by dumping a disc pack, which is 98% utilized, of at least 2.3 GB to the tape and it stored the full pack on the 1 volume which says the technology is 100%, 3490E. Then we stopped compression on the nodes as well as the device classes in TSM to let compression take place on the drive only. We did a test backup thereafter. The same scenario happened with only 900 MB stored. We are loosing over 1.4 GB per volume which is unacceptable. Any suggestions on where to look now or what to change to ensure we use all of the 2.3 GB on the 3490E technology? This will solve 99% of our tape headaches and will minimize the tape usage dramatically. Regards Corrie Viljoen [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] (w) 359-1731 083 294 2405
Re: TDP for SQL version 2.2 download?
Yes, the following is from the TDP for SQL Version 2 User's Guide: The extent to which TDP for SQL Version 2 changes the backup naming conventions, file space names and placement, and meta contents means that it is completely incompatible with TDP for SQL Version 1. You cannot query or restore backup objects created by one version with the other. Therefore, if you are storing backup objects created by Version 1, you must retain Version 1 for as long as you retain those backup objects. Both versions can coexist with each other. The Version 2 installation program will not replace any installed Version 1. In addition, the TDP for SQL Version 2 interfaces are not compatible with the Version 1 interfaces due to the great number of functional changes in Version 2. No migration tool is provided to help convert Version 1 command line scripts to Version 2 syntax. Note: Before automatically converting to TDP for SQL Version 2, users should have analyzed their backup and restore procedures to assess how and where the new capabilities can be applied. Bob KingIBM Global Services [EMAIL PROTECTED] From Mark Stapleton: Robert L King wrote: However, TDP for MS SQL 1.1.2 can do full and log backups of SQL 2000 databases. There are many other features and capabilities that make version 2 worth having but version 1 will do the basic backups and restores. Keep in mind, though, that backups created by version 1 cannot be restored using version 2, only version 1. Are you sure about that? It would contrary to the normal legacy privileges of TSM; that is, newer versions of clients can restore data backed up by an older version, but not the other way around.
WinNT Client Upgrade - Overwrite or Uninstall/Reinstall
Please excuse if this is obvious - several archive searches turned up nothing, and I didn't see a reference in Richard Sims' Quick Facts. Relevant Installation Info: TSM Server 4.1.1.0 on AIX 4.3.3 WinNT Clients: TSM Client 4.1.1.0 on Intel NT 4.0 SP5 or SP6 Goal: Upgrade of WinNT TSM Clients from 4.1.1.0 to 4.1.2.12 to handle DST problem before April 1 (avoiding 4.1.1.16 because of potential memory-leak problem (IC28969)) If I install the 4.1.2.12 client over the top of the existing 4.1.1.0 client, then I end up with two 'Tivoli Storage Manager Client' entries in the 'Control Panel--Add/Remove Programs' (and duplicate entries for the two installed products in the Registry as might be expected). The 'Installing the Clients' manual, Version 4.1, Chapter 4. has a section, 'Reinstalling the Client' , which implies that if you are installing to the same location, you can just install over the top of the previous version with no uninstall required. I want to provide our NT sysadmins a straight-forward procedure for doing this upgrade, and don't know whether to suggest an uninstall-reinstall (ensuring that they have a backup of the dsm.opt and dsmsched.log), or just have them do an install over the top of the existing client (and put the footnote about the duplicate registry entries in the 'Book of Who Cares'.) Any thoughts on best practices? Thanks, Scott Behrens
Recovery Log not reset after Incr. DB backup
Hi, I frequently observe that the recovery log utilization is not reset immediately after a full or incremental DB backup. It happens much later, eg. 30 or 40 minutes after the backup finished. The last cases I watched no sessions or processes were active after the backup finished. I opened a PMR for this case. Has anyone else seen the problem? My server is TSM 4.1.2.0 on AIX 4.3.3. Best regards Gerhard --- Gerhard Rentschleremail:[EMAIL PROTECTED] Regional Computing Center tel. ++49/711/685 5806 University of Stuttgart fax: ++49/711/682357 Allmandring 30a D 70550 Stuttgart Germany
Re: WinNT Client Upgrade - Overwrite or Uninstall/Reinstall
In cases such as this, it is much more advisable to go the full uninstall-reinstall route (after as you say, backing up the required files). Duplicate entries in the registry under Control Panel, more then once also refer to duplicate entries elswhere, so it's more then just a cosmetic. Where it comes to such stuff, go the long way allways. That's what I do. Mike -Original Message- From: Scott Behrens [SMTP:[EMAIL PROTECTED]] Sent: 22 2001 15:32 To: [EMAIL PROTECTED] Subject: WinNT Client Upgrade - Overwrite or Uninstall/Reinstall Please excuse if this is obvious - several archive searches turned up nothing, and I didn't see a reference in Richard Sims' Quick Facts. Relevant Installation Info: TSM Server 4.1.1.0 on AIX 4.3.3 WinNT Clients: TSM Client 4.1.1.0 on Intel NT 4.0 SP5 or SP6 Goal: Upgrade of WinNT TSM Clients from 4.1.1.0 to 4.1.2.12 to handle DST problem before April 1 (avoiding 4.1.1.16 because of potential memory-leak problem (IC28969)) If I install the 4.1.2.12 client over the top of the existing 4.1.1.0 client, then I end up with two 'Tivoli Storage Manager Client' entries in the 'Control Panel--Add/Remove Programs' (and duplicate entries for the two installed products in the Registry as might be expected). The 'Installing the Clients' manual, Version 4.1, Chapter 4. has a section, 'Reinstalling the Client' , which implies that if you are installing to the same location, you can just install over the top of the previous version with no uninstall required. I want to provide our NT sysadmins a straight-forward procedure for doing this upgrade, and don't know whether to suggest an uninstall-reinstall (ensuring that they have a backup of the dsm.opt and dsmsched.log), or just have them do an install over the top of the existing client (and put the footnote about the duplicate registry entries in the 'Book of Who Cares'.) Any thoughts on best practices? Thanks, Scott Behrens
Re: Recovery Log not reset after Incr. DB backup
We are having the same problem on an AIX 4.3.3 running TSM 4.1.2 - This system is running in roll forward mode and we have another system with the same setup and it does not have the problem although it is running in normal mode. Since this uses less log space the incremental trigger is not met and so this may be why we dont see the problem on the other server. I would be interested in IBM's response to your PMR. Regards, Mike (305) 552-2073
Re: FW: TSM data on tape
Any suggestions on where to look now or what to change to ensure we use all of the 2.3 GB on the 3490E technology? Corrie - Please post your Devclass Format specification plus OS type and ADSM/TSM server level, to give us more perspective. thanks, Richard Sims, BU
Re: SAN Datagateway with ADSM 3.1.2.50 on AIX 4.33 - Does it work ?
My understanding is that ADSM 3.1.2.50 won't work with a SAN Data Gateway. We upgraded when we added the SDG. -Original Message- From: Michael Donabauer [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 22, 2001 2:37 AM To: [EMAIL PROTECTED] Subject: SAN Datagateway with ADSM 3.1.2.50 on AIX 4.33 - Does it work? Is ist possible to use a SAN Datagateway with an ADSM Server 3.1.2.50 on AAIX 4.33? Are there any known problems? Thx in advance Mike
Cleaning Carts
Sometimes the operators leave stuff laying around and I have to figure out why. In the most current case I found 2 cleaning cartridges, one in the 3494 door that must have been ejected and another on a cart next to the 3494. I knew from watching the library that there would be a cleaning cartridge running out of cycles today. That is probably the one I just found in the door, but what about the one on the cart? Now that I have to insert a new cartridge I was wondering if the library manager knows if these two other cartridges are used up if I end up sticking one back in that may have just came out. Does the library manager keep track of the barcode numbers on these in case someone happens to do this? Will the library manager even take the cartridge if it is used up? I found a cartridge and want to stick it in but don't know if it is new or not. Does this show the total of all cleaning cartridges or just one at a time? operational state..Automated Operational State functional state...00 input stations.1 output stations1 input/output statusALL input stations empty ALL output stations empty machine type...3494 sequence number14813 number of cells888 available cells201 subsystems.5 convenience capacity...10 accessor config01 accessor statusAccessor available Gripper 1 available Gripper 2 not installed Vision system operational comp avail status..Primary library manager installed. Primary library manager available. Primary hard drive installed. Primary hard drive available. Secondary hard drive installed. Secondary hard drive available. Convenience input station installed. Convenience input station available. Convenience output station installed. Convenience output station available. library facilities.00 bulk input capacity0 bulk input empty cells.0 bulk output capacity...0 bulk output empty cells0 avail 3490 cleaner cycles..0 avail 3590 cleaner cycles..0 By the way, I posted a question yesterday but did not get any hits back on it so I wonder if it even went through. Here it is again in case it did not. A while back I set up a disk pool to keep all directory information readily available in case of a restore. The disk pool is set up to cache files but still migrate to keep a copy on tape. This morning I found the number of files on tape is much much more than the files on disk for all nodes. In some instances a node may not have any files on disk but does on tape. I'm not sure if my settings are incorrect or if there is another problem. Does anyone have a similar setup where they cache files on a disk pool but still send them to tape as backup? Can you verify that the number of files match? Is there a way for me to copy those files on tape to the disk pool so they match? As always, Thanks for the help. Geoff Gill NT Systems Support Engineer SAIC Computer Systems Group E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (888) 997-9614
Re: System Objects for Windows
Andrew, Thank you for the feedback. I looked at this once and I believe it does the same thing the adsm.sys file does in terms of what it captures. What do you do about the boot.ini, config.sys, ntldr, etc. that you might want multiple copies of? They don't get put into the system objects stored in adsm.sys, are they kept with the NT backup? Brenda -Original Message- From: Andrew Pearce [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 4:43 PM To: [EMAIL PROTECTED] Subject: Re: System Objects for Windows Brenda, We schedule NTbackup to backup the Windows 2000 System State to disk and then pick this up as a file via TSM. Not particularly elegant, but as a short term fix it meets our requirements. You obviuosly need to be familar with a recovery process that incorparates NTbackup to do this. I've heard that the inactive system objects issue may be addressed in the next release of the client (4.2) - certainly hope so - can anyone confirm this? Andrew Pearce email: [EMAIL PROTECTED] "Collins, Brenda" Brenda.Collins@WESTTo: [EMAIL PROTECTED] GROUP.COM cc: Sent by: "ADSM: DistSubject: System Objects for Windows Stor Manager" [EMAIL PROTECTED] U 20/03/2001 03:51 AM Please respond to "ADSM: Dist Stor Manager" Has anyone implemented a solution they would be willing to share that will keep copies of inactive system objects? Brenda Collins, Storage Solutions Group Phone: 651-848-5808 Email: [EMAIL PROTECTED] Disclaimer: "The views, opinions and judgements expressed in this message are solely those of the author. The message contents have not been reviewed or approved by West Group."
3494 Partitioning - moving TSM from MVS to AIX
We posted this on the IBM-MAIN listserver and have had no responses (I've reworded it a bit to try and make it clearer). Maybe someone on ADSM-L who has done a move from MVS to AIX with TSM could help us? We have a IBM 3494 with 2 Logical Libraries (VTS and Native); all the drives are 3590-E1A. We are moving TSM(ADSM) off of MVS to AIX (RS/6000 H80). In the Native Library, we currently have an L14, D14, D14, D14, then VTS configuration - we are going to be changing it to an L14, D12, D14, D14, etc. configuration, where the second frame is no longer to be used by MVS, but will now have six 3590-E1A Fibre attached drives, all drives in that frame connecting to the H80. Currently the drives in the second frame are defined to MVS and the frame (D14) is LIBPORT-ID=02 in the HCD definition. What will it be to MVS, if anything, when we partition it off? If it were SCSI, it would get 6 LIBPORT-ID numbers but it's Fibre - does that keep just the 02 ID or is it completely removed from HCD because it's being attached to the RS box (partitioned off MVS)? We can't find anything thing concrete at this point, we've been all around it - in Redbooks, IBM.Com, HCD, etc. Linnea Nichols Fairfax Co Govt, Fairfax, VA [EMAIL PROTECTED] Phone: 703/324-2708 FAX:703-324-3958
Recovery Log not reset after Incr. DB backup
Hi Gerhard, I'm having the sam problem with server 3.7.4.0 on AIX 4.3.3. best regards Rainer Gerhard Rentschler [EMAIL PROTECTED] am 22.03.2001 14:36:05 Bitte antworten an "ADSM: Dist Stor Manager" [EMAIL PROTECTED] An: [EMAIL PROTECTED] Kopie: (Blindkopie: Rainer Holzinger/HAINDL) Thema:Recovery Log not reset after Incr. DB backup Hi, I frequently observe that the recovery log utilization is not reset immediately after a full or incremental DB backup. It happens much later, eg. 30 or 40 minutes after the backup finished. The last cases I watched no sessions or processes were active after the backup finished. I opened a PMR for this case. Has anyone else seen the problem? My server is TSM 4.1.2.0 on AIX 4.3.3. Best regards Gerhard --- Gerhard Rentschleremail:[EMAIL PROTECTED] Regional Computing Center tel. ++49/711/685 5806 University of Stuttgart fax: ++49/711/682357 Allmandring 30a D 70550 Stuttgart Germany
README file for HP-UX fix test IC26906
I am preparing to install a client fix test on some of my HP-UX systems. I followed a link from the Tivoli Web server to the FTP server at service.boulder.ibm.com and found the directory containing fix tests for HP-UX 3.7 client code. In the course of figuring out which fixtest I needed I looked at the README file for fix test IC26906. The first few lines of this file are as follows: = Tivoli Storage Manager (TSM) Solaris 2.6/7 Client README Version 3, Release 7, Level 2 PTF IP21931 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2000. All rights reserved. Welcome to the Tivoli Storage Manager Version 3.7 HP-UX 11 Client! = Much of the substantive information in the file is specific to Solaris. Fortunately for me and my clients, I needed a different fix test. Even so, this breathtaking display of ineptitude makes me a little nervous about the soundness of any fix test.
Backupset restore
Hi all, I'm attempting to do a local restore of a backupset and am having a problem. Here's the situation: TSM Server: TSM for MVS 3.7.3 TSM client: TSM for Windows 3.7 I created a backupset writing to a file device class, which generated 4 files on my MVS system. I can restore the backupset from the Server via the GUI with no problem. I then FTP'd the backupset files to my LAN and burned them onto CD. When I pop the CD in specify the CD drive as the backupset location, I'm getting the following message: ANS1933E Error accessing file or device Anyone have an idea of what is wrong here? Any help will be greatly appreciated! Thanks, Cheri Howard Lead Software Systems Analyst 920-730-4700, ext. 4166 [EMAIL PROTECTED] Aid Association for Lutherans (AAL) 4321 N. Ballard Road, Appleton, WI 54919-0001 http://www.aal.org
Re: Cleaning Carts
Now that I have to insert a new cartridge I was wondering if the library manager knows if these two other cartridges are used up if I end up sticking one back in that may have just came out. Does the library manager keep track of the barcode numbers on these in case someone happens to do this? Will the library manager even take the cartridge if it is used up? I found a cartridge and want to stick it in but don't know if it is new or not. Geoff - Your Library Manager seems to be a lot more effective than your Operations Manager... When tapes are ejected via the Library Manager, they are considered gone as far as it is concerned, so it disposes of its database entries and stats for such volumes. Your "avail 3590 cleaner cycles" value is zero, hence such such a disposal has occurred. As far as I know, there is nothing intrinsic to a 3590 cleaning tape which records uses. (Some other tape technologies embed a writable/readable chip in the cartridge, which might facilitate such record-keeping in their environments.) So if you re-insert a used cleaning cartridge, I'd expect it to start over on it - not that I've tried this myself. One recourse might be to go to the 3494 operator station and go through its internal logs (easy to do) and search on your cleaner cartridge prefix (typically, "CLN") to possibly identify which of your cleaning cartridges had been in there. (I'm at home with no 3494 here to try it on, but I seem to recall from prior log inspection that the cleaning cartridges show up there.) Richard Sims, BU
Patch 3.7.2.19 now available for Alpha Windows client
The 3.7.2.19 patch for alpha processors is now available on our ftp site. Here is where you will find it: ftp site: ftp.software.ibm.com directory: storage/tivoli-storage-management/patches/client/v3r7/Windows/v372/alpha The file names all begin with IP21934_19. Be sure to review the IP21934_19_README.FTP for download and setup instructions, and IP21934_19_README.1ST for general info about the patch. Note: if you are already familiar with the 3.7.2.19 (IP21933_19) patch for the x86, it's the same material. This patch is functionally equivalent to the 3.7.2.19 code for x86 processors, and thus includes the fix for the Daylight Savings Time problem (among others). 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."
Re: Backupset restore
Hi Cheri, Have you tried to copy the file from the burned CD to local disk and then restore from there? How do you create the CD - with session open/close session/...? It may make things complicated. I met this message before when I tried to restore a backupset from tape drive while server and client were on the same machine, and it was solved by creating a FILE device class' backupset. Following are some other cases which gets the same error message. FYI. Regards, Phillip -- IC27617-CUSTOMER UNABLE TO RESTORE BACKUPSET TO LOCAL CLIENT WITH TSM CLIENT 3.7.2 ON NT IF THE BACKUPSET SPANS A VOLUME. IC27809-UNABLE TO RESTORE INDIVIDUAL FILES IN BACKUPSET VIA B/A GUI. IC29680- WHEN A NODE IS RENAMED ON THE SERVER, ANY BACKUPSETS GENERATED FOR IT CAN'T BE RESTORED EVEN THOUGH IT REPORTS SUCCESSFUL. IC29472-DOC NEEDS TO BE UPDATED FOR RESTORING BACKUPSETS USING THE NATIVE NT DEVICE DRIVER TO REFLECT DEVICE NAME OF \\.\TAPEX . IC25937-QUERY BACKUPSET AND RESTORE BACKUPSET EXAMPLES SHOW THE -LOC OPTION WITH INCORRECT SYNTAX. ERROR DESCRIPTION: The books Tivoli Storage manager Using the Backup Archive-Client for windows and unix have incorrect syntax in the examples for for windows and unix have incorrect syntax in the examples for the backupset commands. In the Unix book we have examples for restore backupset and query backupset that use the paramater " -loc=/dev/rmt0 " -loc can only take 'server', 'file', or 'tape'. In the Windows book query backupset has the location parameter taking g:\weeklydata.set as an argument. It can only take 'server' and 'file'. LOCAL FIX: Use the syntax from typing help from the tsm command line. Examples of correct syntax: query backupset "mybackupsetname" -loc=server query backupset /dev/rmt0 -loc=tape IC27164 - RESTORE BACKUPSET WILL NOT WORK FROM THE WIN32 GUI IF THE TSM SERVER IS NOT REACHABLE. TCP/IP FAILURE. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Cheri Howard Sent: Thursday, March 22, 2001 9:07 AM To: [EMAIL PROTECTED] Subject: Backupset restore Hi all, I'm attempting to do a local restore of a backupset and am having a problem. Here's the situation: TSM Server: TSM for MVS 3.7.3 TSM client: TSM for Windows 3.7 I created a backupset writing to a file device class, which generated 4 files on my MVS system. I can restore the backupset from the Server via the GUI with no problem. I then FTP'd the backupset files to my LAN and burned them onto CD. When I pop the CD in specify the CD drive as the backupset location, I'm getting the following message: ANS1933E Error accessing file or device Anyone have an idea of what is wrong here? Any help will be greatly appreciated! Thanks, Cheri Howard Lead Software Systems Analyst 920-730-4700, ext. 4166 [EMAIL PROTECTED] Aid Association for Lutherans (AAL) 4321 N. Ballard Road, Appleton, WI 54919-0001 http://www.aal.org
Disaster Happened!
I'll try to make this brief. Last night we were doing upgrades on some of our systems, most notably and RS6000 SP Node running AIX 4.3.3. During OS maintenance level update we lost connectivity from Control W/S with CDROM to the Client SP NOde - It went downhill from there! WE shortly couldn't even getb into the Node even from TTY. With great effort from IBM support we got in and got the NOde back in config but no way to get back where we were. Had to reload a new image on the node and then we loaded the TSM 4.1.0.0 client. (The node originally had 3.1.0.6 client with API interfacing to ORacle's EBU for Oracle 7.3.4 database _ Peoplesoft App.) DB's are on Extrenal IBM ESS so shouild be o.k. We have restored /usr, now restoring /var and will go to /home and then /. Looks good so far. We have never restored a complete AIX system from ADSM and certainlyu not an SP NODE. I just got back in from 3 hours sleep while another guy got us this far. I plan to call Tivoli, but wanted to check with anybody that has done this or similar with AIX. And anybody that also has SP experience would be helpful. Are we going down wrong path? What are gotcha's? What about SP issues? Default assumption is after we resotre these rootvg filesystems, we can reboot and everybody will live happily everafter?!?!?! We will not reboot until I can get some good feeling that it will come up as we may not be able to get back in. I know this may not make good sense as I'm not 10% today but that's why we are checking with others. I will also try to get "DR restore manual" from onluine at Tivle/IBM also. (We are alsio restoring a 30+ GB Novell volume - gues how long that will ytake!!) THanks in advance for any helpful comments. I will post our "Final Answer" when it's all back up! David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] "MMS health-first.org" made the following annotations on 03/22/01 14:14:48 -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. Ý==
Re: Disaster Happened!
Yeah, been there done that about 9 months ago, and on an SP node, I think at AIX 4.3.2. Nothing sneaky; Just as you are doing, we reloaded the image from a mksysb tape, then restored each filesystem from TSM to get current. If you've got multiple tape drives, open another window and start the restore of /home in parallel with /var -- and you can go /home faster! -Original Message- From: David Longo [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 22, 2001 2:09 PM To: [EMAIL PROTECTED] Subject: Disaster Happened! I'll try to make this brief. Last night we were doing upgrades on some of our systems, most notably and RS6000 SP Node running AIX 4.3.3. During OS maintenance level update we lost connectivity from Control W/S with CDROM to the Client SP NOde - It went downhill from there! WE shortly couldn't even getb into the Node even from TTY. With great effort from IBM support we got in and got the NOde back in config but no way to get back where we were. Had to reload a new image on the node and then we loaded the TSM 4.1.0.0 client. (The node originally had 3.1.0.6 client with API interfacing to ORacle's EBU for Oracle 7.3.4 database _ Peoplesoft App.) DB's are on Extrenal IBM ESS so shouild be o.k. We have restored /usr, now restoring /var and will go to /home and then /. Looks good so far. We have never restored a complete AIX system from ADSM and certainlyu not an SP NODE. I just got back in from 3 hours sleep while another guy got us this far. I plan to call Tivoli, but wanted to check with anybody that has done this or similar with AIX. And anybody that also has SP experience would be helpful. Are we going down wrong path? What are gotcha's? What about SP issues? Default assumption is after we resotre these rootvg filesystems, we can reboot and everybody will live happily everafter?!?!?! We will not reboot until I can get some good feeling that it will come up as we may not be able to get back in. I know this may not make good sense as I'm not 10% today but that's why we are checking with others. I will also try to get "DR restore manual" from onluine at Tivle/IBM also. (We are alsio restoring a 30+ GB Novell volume - gues how long that will ytake!!) THanks in advance for any helpful comments. I will post our "Final Answer" when it's all back up! David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] "MMS health-first.org" made the following annotations on 03/22/01 14:14:48 -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ===
Re: Disaster Happened!
Thanks, sounds good. We didn't have a usefil mksysb, we installed a new minimum image from the Control W/S, then confiured SP stuff and Network. Don't know if we will have some SP goytchas. It is in SP config o.k. now hopefully will stay there David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] [EMAIL PROTECTED] 03/22/01 02:17PM Yeah, been there done that about 9 months ago, and on an SP node, I think at AIX 4.3.2. Nothing sneaky; Just as you are doing, we reloaded the image from a mksysb tape, then restored each filesystem from TSM to get current. If you've got multiple tape drives, open another window and start the restore of /home in parallel with /var -- and you can go /home faster! -Original Message- From: David Longo [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 22, 2001 2:09 PM To: [EMAIL PROTECTED] Subject: Disaster Happened! I'll try to make this brief. Last night we were doing upgrades on some of our systems, most notably and RS6000 SP Node running AIX 4.3.3. During OS maintenance level update we lost connectivity from Control W/S with CDROM to the Client SP NOde - It went downhill from there! WE shortly couldn't even getb into the Node even from TTY. With great effort from IBM support we got in and got the NOde back in config but no way to get back where we were. Had to reload a new image on the node and then we loaded the TSM 4.1.0.0 client. (The node originally had 3.1.0.6 client with API interfacing to ORacle's EBU for Oracle 7.3.4 database _ Peoplesoft App.) DB's are on Extrenal IBM ESS so shouild be o.k. We have restored /usr, now restoring /var and will go to /home and then /. Looks good so far. We have never restored a complete AIX system from ADSM and certainlyu not an SP NODE. I just got back in from 3 hours sleep while another guy got us this far. I plan to call Tivoli, but wanted to check with anybody that has done this or similar with AIX. And anybody that also has SP experience would be helpful. Are we going down wrong path? What are gotcha's? What about SP issues? Default assumption is after we resotre these rootvg filesystems, we can reboot and everybody will live happily everafter?!?!?! We will not reboot until I can get some good feeling that it will come up as we may not be able to get back in. I know this may not make good sense as I'm not 10% today but that's why we are checking with others. I will also try to get "DR restore manual" from onluine at Tivle/IBM also. (We are alsio restoring a 30+ GB Novell volume - gues how long that will ytake!!) THanks in advance for any helpful comments. I will post our "Final Answer" when it's all back up! David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] "MMS health-first.org" made the following annotations on 03/22/01 14:14:48 -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. === "MMS health-first.org" made the following annotations on 03/22/01 14:33:27 -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity;
Re: Disaster Happened!
I agree with Wanda. I would add that we netboot/customize when we have a complete failure on the rootvg. The mksysb's are made weekly and stored on node pairs (in addition to being backed up to ADSM). In this manner we can get the rootvg rebuilt without going to tape, and then get picky about what we really need to bring back. Make sure that boot self-discovery and the ODM do not disagree (you never know after a while of small hardware changes - this has bit us in the past). Then once you've restored /dev and other important directories make sure it matches the physical. David "Prather, Wanda" [EMAIL PROTECTED]@VM.MARIST.EDU on 03/22/2001 12:17:42 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Disaster Happened! Yeah, been there done that about 9 months ago, and on an SP node, I think at AIX 4.3.2. Nothing sneaky; Just as you are doing, we reloaded the image from a mksysb tape, then restored each filesystem from TSM to get current. If you've got multiple tape drives, open another window and start the restore of /home in parallel with /var -- and you can go /home faster! -Original Message- From: David Longo [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 22, 2001 2:09 PM To: [EMAIL PROTECTED] Subject: Disaster Happened! I'll try to make this brief. Last night we were doing upgrades on some of our systems, most notably and RS6000 SP Node running AIX 4.3.3. During OS maintenance level update we lost connectivity from Control W/S with CDROM to the Client SP NOde - It went downhill from there! WE shortly couldn't even getb into the Node even from TTY. With great effort from IBM support we got in and got the NOde back in config but no way to get back where we were. Had to reload a new image on the node and then we loaded the TSM 4.1.0.0 client. (The node originally had 3.1.0.6 client with API interfacing to ORacle's EBU for Oracle 7.3.4 database _ Peoplesoft App.) DB's are on Extrenal IBM ESS so shouild be o.k. We have restored /usr, now restoring /var and will go to /home and then /. Looks good so far. We have never restored a complete AIX system from ADSM and certainlyu not an SP NODE. I just got back in from 3 hours sleep while another guy got us this far. I plan to call Tivoli, but wanted to check with anybody that has done this or similar with AIX. And anybody that also has SP experience would be helpful. Are we going down wrong path? What are gotcha's? What about SP issues? Default assumption is after we resotre these rootvg filesystems, we can reboot and everybody will live happily everafter?!?!?! We will not reboot until I can get some good feeling that it will come up as we may not be able to get back in. I know this may not make good sense as I'm not 10% today but that's why we are checking with others. I will also try to get "DR restore manual" from onluine at Tivle/IBM also. (We are alsio restoring a 30+ GB Novell volume - gues how long that will ytake!!) THanks in advance for any helpful comments. I will post our "Final Answer" when it's all back up! David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] "MMS health-first.org" made the following annotations on 03/22/01 14:14:48 -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ===
Re: Disaster Happened!
If you are installing AIX 4.3.3 Maintenance Level 6, do not mirror rootvg. There is a bug in ML-006 that may cause 555 in LEDS on a reboot if rootvg is mirrored. Denny P. -Original Message- From: Prather, Wanda [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 22, 2001 2:18 PM To: [EMAIL PROTECTED] Subject: Re: Disaster Happened! Yeah, been there done that about 9 months ago, and on an SP node, I think at AIX 4.3.2. Nothing sneaky; Just as you are doing, we reloaded the image from a mksysb tape, then restored each filesystem from TSM to get current. If you've got multiple tape drives, open another window and start the restore of /home in parallel with /var -- and you can go /home faster! -Original Message- From: David Longo [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 22, 2001 2:09 PM To: [EMAIL PROTECTED] Subject: Disaster Happened! I'll try to make this brief. Last night we were doing upgrades on some of our systems, most notably and RS6000 SP Node running AIX 4.3.3. During OS maintenance level update we lost connectivity from Control W/S with CDROM to the Client SP NOde - It went downhill from there! WE shortly couldn't even getb into the Node even from TTY. With great effort from IBM support we got in and got the NOde back in config but no way to get back where we were. Had to reload a new image on the node and then we loaded the TSM 4.1.0.0 client. (The node originally had 3.1.0.6 client with API interfacing to ORacle's EBU for Oracle 7.3.4 database _ Peoplesoft App.) DB's are on Extrenal IBM ESS so shouild be o.k. We have restored /usr, now restoring /var and will go to /home and then /. Looks good so far. We have never restored a complete AIX system from ADSM and certainlyu not an SP NODE. I just got back in from 3 hours sleep while another guy got us this far. I plan to call Tivoli, but wanted to check with anybody that has done this or similar with AIX. And anybody that also has SP experience would be helpful. Are we going down wrong path? What are gotcha's? What about SP issues? Default assumption is after we resotre these rootvg filesystems, we can reboot and everybody will live happily everafter?!?!?! We will not reboot until I can get some good feeling that it will come up as we may not be able to get back in. I know this may not make good sense as I'm not 10% today but that's why we are checking with others. I will also try to get "DR restore manual" from onluine at Tivle/IBM also. (We are alsio restoring a 30+ GB Novell volume - gues how long that will ytake!!) THanks in advance for any helpful comments. I will post our "Final Answer" when it's all back up! David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] "MMS health-first.org" made the following annotations on 03/22/01 14:14:48 -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ===
Define Drive
We are currently using our only 3575 as our ADSM data base backup. I would like to move that to our 8 mm drive so I entered: define drive 3575lib eightmm device=/dev/rmt0 Just as show in the book, but an error comes back and says I need to add the element. So I tried this: define drive 3575lib eightmm device=/dev/rmt0 element=10-60-00-5,0 and since I'm here, it didn't like that either. What is the proper format? Thanks Bill Dias AIX Systems Administrator Gerber Scientific.
Re: Backupset restore
Thanks for the suggestion, Phillip, but that didn't work either. I copied the backupset from the CD to local disk and specified the local disk as the location for the backupset, and still receive the same error. Has anyone else had this problem? Any ideas on how to resolve? Thanks, Cheri Howard Lead Software Systems Analyst 920-730-4700, ext. 4166 [EMAIL PROTECTED] Aid Association for Lutherans (AAL) 4321 N. Ballard Road, Appleton, WI 54919-0001 http://www.aal.org |+--- || Phillip Guan | || pguan@SANSIA| || .NET| || | || 03/22/2001 | || 11:54 AM | || Please | || respond to | || pguan| || | |+--- | || | To: [EMAIL PROTECTED] | | cc: (bcc: Cheri Howard/AAL) | | Subject: Re: Backupset restore | | Hi Cheri, Have you tried to copy the file from the burned CD to local disk and then restore from there? How do you create the CD - with session open/close session/...? It may make things complicated. I met this message before when I tried to restore a backupset from tape drive while server and client were on the same machine, and it was solved by creating a FILE device class' backupset. Following are some other cases which gets the same error message. FYI. Regards, Phillip -- IC27617-CUSTOMER UNABLE TO RESTORE BACKUPSET TO LOCAL CLIENT WITH TSM CLIENT 3.7.2 ON NT IF THE BACKUPSET SPANS A VOLUME. IC27809-UNABLE TO RESTORE INDIVIDUAL FILES IN BACKUPSET VIA B/A GUI. IC29680- WHEN A NODE IS RENAMED ON THE SERVER, ANY BACKUPSETS GENERATED FOR IT CAN'T BE RESTORED EVEN THOUGH IT REPORTS SUCCESSFUL. IC29472-DOC NEEDS TO BE UPDATED FOR RESTORING BACKUPSETS USING THE NATIVE NT DEVICE DRIVER TO REFLECT DEVICE NAME OF \\.\TAPEX . IC25937-QUERY BACKUPSET AND RESTORE BACKUPSET EXAMPLES SHOW THE -LOC OPTION WITH INCORRECT SYNTAX. ERROR DESCRIPTION: The books Tivoli Storage manager Using the Backup Archive-Client for windows and unix have incorrect syntax in the examples for for windows and unix have incorrect syntax in the examples for the backupset commands. In the Unix book we have examples for restore backupset and query backupset that use the paramater " -loc=/dev/rmt0 " -loc can only take 'server', 'file', or 'tape'. In the Windows book query backupset has the location parameter taking g:\weeklydata.set as an argument. It can only take 'server' and 'file'. LOCAL FIX: Use the syntax from typing help from the tsm command line. Examples of correct syntax: query backupset "mybackupsetname" -loc=server query backupset /dev/rmt0 -loc=tape IC27164 - RESTORE BACKUPSET WILL NOT WORK FROM THE WIN32 GUI IF THE TSM SERVER IS NOT REACHABLE. TCP/IP FAILURE. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Cheri Howard Sent: Thursday, March 22, 2001 9:07 AM To: [EMAIL PROTECTED] Subject: Backupset restore Hi all, I'm attempting to do a local restore of a backupset and am having a problem. Here's the situation: TSM Server: TSM for MVS 3.7.3 TSM client: TSM for Windows 3.7 I created a backupset writing to a file device class, which generated 4 files on my MVS system. I can restore the backupset from the Server via the GUI with no problem. I then FTP'd the backupset files to my LAN and burned them onto CD. When I pop the CD in specify the CD drive as the backupset location, I'm getting the following message: ANS1933E Error accessing file or device Anyone have an idea of what is wrong here? Any help will be greatly appreciated! Thanks, Cheri Howard Lead Software Systems Analyst 920-730-4700, ext. 4166 [EMAIL PROTECTED] Aid Association for Lutherans (AAL) 4321 N. Ballard Road, Appleton, WI 54919-0001 http://www.aal.org
Re: Need ADSM PTF v3.1.2.40 for NT
Hi Jelle, I'm trying to reach you for last couple of days but no luck. Anyway, I'm ready with the FTP logon and password, would you please send me an e-mail so that I could provide you the server details for uploading files for me, I'd appreciate. Thanks for your time. Prasanna [EMAIL PROTECTED] -Original Message- From: Jelle Komrij [mailto:[EMAIL PROTECTED]] Sent: Sunday, March 18, 2001 2:29 PM To: [EMAIL PROTECTED] Subject: Re: Need ADSM PTF v3.1.2.40 for NT I do have a copy. Is it no longer on the web ? Well if you really need this one, i can try to mail it to you. (Not sure my SP allows me to sent 70 Mb over mail) Perhaps you have a ftp site to sent it to. Just let me know, Jelle Komrij "Ghanekar, Prasanna" wrote: Anyone having a copy of ADSM PTF v3.1.2.40 for Windows NT ADSM server, Please let me know ASAP. I had to upgrade the server while recovering it and now it's running PTF v3.1.2.90 and I'm running into Database sort order problems while doing a restore from a client.(My existing env. is NT 4.0 + SP 5 and ADSM v3.1.2.90) I did audit the storage pool volumes after restoring the server but I don't know how to fix the database sort order problem. Does anybody have a checklist of things to do after the recovery, Let me know. Do I have to retouch all clients with the newer version? Thanks in advance, Prasanna Prasanna Ghanekar ...OLE_Obj... EDS Pontiac East 2100 S Opdyke Rd MI 48341 *: (248) 972-4547
Re: Define Drive
The proper syntax should be: define drive libname drivename device=/dev/rmt0 element=17 Thanks, Demetrius -Original Message- From: Dias, Bill (GTIWHQ) [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 22, 2001 1:58 PM To: [EMAIL PROTECTED] Subject: Define Drive We are currently using our only 3575 as our ADSM data base backup. I would like to move that to our 8 mm drive so I entered: define drive 3575lib eightmm device=/dev/rmt0 Just as show in the book, but an error comes back and says I need to add the element. So I tried this: define drive 3575lib eightmm device=/dev/rmt0 element=10-60-00-5,0 and since I'm here, it didn't like that either. What is the proper format? Thanks Bill Dias AIX Systems Administrator Gerber Scientific.
Re: Backupset restore
ANS1933E Error accessing file or device 'name'. Explanation: An error has occurred while accessing the file or device. System Action: Backup set operation is not completed. User Response: Verify that the file or device exists and is accessible. When you open the backup client to restore from the backupset, is there a BACKUPSET Icon with a + to expand? When I first tried this, for whatever reason, it took a little while to "see" the backupset. If you expand the BACKUPSET +, you should see SERVER and LOCAL. Choose Local hope this helps? Cheri Howard Cheri_HowardTo: [EMAIL PROTECTED] @AAL.ORGcc: Sent by: Subject: Re: Backupset restore "ADSM: Dist Stor Manager" [EMAIL PROTECTED] RIST.EDU 03/22/2001 03:19 PM Please respond to "ADSM: Dist Stor Manager" Thanks for the suggestion, Phillip, but that didn't work either. I copied the backupset from the CD to local disk and specified the local disk as the location for the backupset, and still receive the same error. Has anyone else had this problem? Any ideas on how to resolve? Thanks, Cheri Howard Lead Software Systems Analyst 920-730-4700, ext. 4166 [EMAIL PROTECTED] Aid Association for Lutherans (AAL) 4321 N. Ballard Road, Appleton, WI 54919-0001 http://www.aal.org |+--- || Phillip Guan | || pguan@SANSIA| || .NET| || | || 03/22/2001 | || 11:54 AM | || Please | || respond to | || pguan| || | |+--- | || | To: [EMAIL PROTECTED] | | cc: (bcc: Cheri Howard/AAL) | | Subject: Re: Backupset restore | | Hi Cheri, Have you tried to copy the file from the burned CD to local disk and then restore from there? How do you create the CD - with session open/close session/...? It may make things complicated. I met this message before when I tried to restore a backupset from tape drive while server and client were on the same machine, and it was solved by creating a FILE device class' backupset. Following are some other cases which gets the same error message. FYI. Regards, Phillip -- IC27617-CUSTOMER UNABLE TO RESTORE BACKUPSET TO LOCAL CLIENT WITH TSM CLIENT 3.7.2 ON NT IF THE BACKUPSET SPANS A VOLUME. IC27809-UNABLE TO RESTORE INDIVIDUAL FILES IN BACKUPSET VIA B/A GUI. IC29680- WHEN A NODE IS RENAMED ON THE SERVER, ANY BACKUPSETS GENERATED FOR IT CAN'T BE RESTORED EVEN THOUGH IT REPORTS SUCCESSFUL. IC29472-DOC NEEDS TO BE UPDATED FOR RESTORING BACKUPSETS USING THE NATIVE NT DEVICE DRIVER TO REFLECT DEVICE NAME OF \\.\TAPEX . IC25937-QUERY BACKUPSET AND RESTORE BACKUPSET EXAMPLES SHOW THE -LOC OPTION WITH INCORRECT SYNTAX. ERROR DESCRIPTION: The books Tivoli Storage manager Using the Backup Archive-Client for windows and unix have incorrect syntax in the examples for for windows and unix have incorrect syntax in the examples for the backupset commands. In the Unix book we have examples for restore backupset and query backupset that use the paramater " -loc=/dev/rmt0 " -loc can only take 'server', 'file', or 'tape'. In the Windows book query backupset has the location parameter taking g:\weeklydata.set as an argument. It can only take 'server' and 'file'. LOCAL FIX: Use the syntax from typing help from the tsm command line. Examples of correct syntax: query backupset "mybackupsetname" -loc=server query backupset /dev/rmt0 -loc=tape IC27164 - RESTORE BACKUPSET WILL NOT WORK FROM THE WIN32 GUI IF THE TSM SERVER IS NOT REACHABLE. TCP/IP FAILURE. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Cheri Howard Sent: Thursday, March 22, 2001 9:07 AM To: [EMAIL PROTECTED] Subject: Backupset restore Hi all, I'm attempting to do a local restore of a backupset and am having a problem. Here's the situation: TSM Server: TSM for MVS 3.7.3 TSM client: TSM for Windows 3.7 I created a backupset writing to a file device class, which generated 4 files on my MVS system. I can restore the backupset from the Server via the GUI with no problem. I then FTP'd the backupset files to my LAN and burned them onto CD. When I pop the CD in specify the CD drive as the
NT Restores
I'm looking for a way to streamline our NT server recovery procedure. Is there still an option to create bootable diskettes that will restore an NT box without writing to the c: drive? If not, does anyone have a more efficient way than the "creating a temp drive method"? Thanks in advance for any ideas! Neil
Re: Define Drive
Bill, You need to create the TSM device before you can access the drive from TSM. See the docs for how to define the drive from smitty, devices, TSM devices, etc. Steffan At 02:58 PM 3/22/2001 -0500, you wrote: We are currently using our only 3575 as our ADSM data base backup. I would like to move that to our 8 mm drive so I entered: define drive 3575lib eightmm device=/dev/rmt0 Just as show in the book, but an error comes back and says I need to add the element. So I tried this: define drive 3575lib eightmm device=/dev/rmt0 element=10-60-00-5,0 and since I'm here, it didn't like that either. What is the proper format? Thanks Bill Dias AIX Systems Administrator Gerber Scientific.
Re: Define Drive
Bill, If it's asking for an element number, it most likely thinks your 8mm is in the 3575lib. To tell the truth, that's what it looks like from your DEFINE DRIVE command, also. Is this the case? If it is, you'll need to find the element number corresponding to the physical location in your drive. You can find element numbers at: http://publib.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/A54O1003/C.0 If your 8mm is not in the library (mine isn't, it's in the rack), you'll need to DEFINE LIBRARY and create a manual library. Here's an example from the TSM 3.7 Admin Guide, page 53. Of course, this assumes the drive is already Available to AIX. Er... Or whatever OS you're using. define library manual8mm libtype=manual define drive manual8mm drive01 device=/dev/mt1 define drive manual8mm drive02 device=/dev/mt2 Good luck, Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Dias, Bill (GTIWHQ) [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 22, 2001 11:58 AM To: [EMAIL PROTECTED] Subject: Define Drive We are currently using our only 3575 as our ADSM data base backup. I would like to move that to our 8 mm drive so I entered: define drive 3575lib eightmm device=/dev/rmt0 Just as show in the book, but an error comes back and says I need to add the element. So I tried this: define drive 3575lib eightmm device=/dev/rmt0 element=10-60-00-5,0 and since I'm here, it didn't like that either. What is the proper format? Thanks Bill Dias AIX Systems Administrator Gerber Scientific.
Re: System Objects for Windows
Brenda, The NT systemstate contains most (but not all of the same things that are backed up by the TSM System Object), so in that respect it captures more than whats held in ADMS.SYS I know that the System Files component of the System State contains many of the O.S related files for Windows 2000. This includes files that are held in the WINNT directory. However, I'm not sure if the System Files component includes the boot files that sit in the root for the drive (boot.ini etc). We backup the C drive anyway so even if the boot.ini, config.sys etc aren't captured as part of the Windows 2000 System State backup, they get included in the file system backups. I know that it's likely that we're 'double-dipping' some files but it's better than not getting them at all : -). Our typical backup schedule works as follows: 1. Use the Windows 2000 Scheduler to trigger NTbackup to backup the System State to a disk file. On a system without Active Directory the file size isaorund 300mb. For a domain controller with would obviousl be bigger depending upon the size of your AD. 2. After a reasonable time window (to allow NTbackup to do it's stuff), do a TSM backup of C drive , System Object plus any other drives you need. The file created as by NTbackup is then backed up at this point. Other than using NTbackup the only other way that I thought that you could get around this problem would be to rename the System Object filespace on the TSM server to correspond with the backup date (or someother unique name). That way it would always remain active. Then if you need to restore it, you just need to reamne it again before starting the recvoery process. However, I haven't had anytime to reseach this, so I don;t know how 'doable' this is. The Ntbackup method seemed to be the quicked way to acheive a result, although probably not the cleanest. Andrew Pearce BHP Server Engineering, CSC Australia PO Box 261, Warrawong, NSW 2502 email: [EMAIL PROTECTED] Tel: 0242 75 7135 Fax: 0242 75 7923 "Collins, Brenda" Brenda.Collins@WESTTo: [EMAIL PROTECTED] GROUP.COM cc: Sent by: "ADSM: DistSubject: Re: System Objects for Windows Stor Manager" [EMAIL PROTECTED] U 23/03/2001 01:53 AM Please respond to "ADSM: Dist Stor Manager" Andrew, Thank you for the feedback. I looked at this once and I believe it does the same thing the adsm.sys file does in terms of what it captures. What do you do about the boot.ini, config.sys, ntldr, etc. that you might want multiple copies of? They don't get put into the system objects stored in adsm.sys, are they kept with the NT backup? Brenda -Original Message- From: Andrew Pearce [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 4:43 PM To: [EMAIL PROTECTED] Subject: Re: System Objects for Windows Brenda, We schedule NTbackup to backup the Windows 2000 System State to disk and then pick this up as a file via TSM. Not particularly elegant, but as a short term fix it meets our requirements. You obviuosly need to be familar with a recovery process that incorparates NTbackup to do this. I've heard that the inactive system objects issue may be addressed in the next release of the client (4.2) - certainly hope so - can anyone confirm this? Andrew Pearce email: [EMAIL PROTECTED] "Collins, Brenda" Brenda.Collins@WESTTo: [EMAIL PROTECTED] GROUP.COM cc: Sent by: "ADSM: DistSubject: System Objects for Windows Stor Manager" [EMAIL PROTECTED] U 20/03/2001 03:51 AM Please respond to "ADSM: Dist Stor Manager" Has anyone implemented a solution they would be willing to share that will keep copies of inactive system objects? Brenda Collins, Storage Solutions Group Phone: 651-848-5808 Email: [EMAIL PROTECTED] Disclaimer: "The views, opinions and judgements expressed in this message are solely those of the author. The message contents have not been reviewed or approved by West Group."
Re: System Objects for Windows
NT Backup of System State does not include boot.ini, it does include ntldr and ntdetect.com. I don't think it contains config.sys. TSM DOES NOT backup boot.ini as a regular file. It does not back up any files that are included as part of the System Object. Renaming the System Object on TSM after the backup does work - I've tested this out. This is documented in the TSM with W2K redpiece. One reason to use the NT backup method is that it gives you the ability to archive the system state which you cannot do at all with TSM. Tim Rushforth City of Winnipeg -Original Message- From: Andrew Pearce [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 22, 2001 3:45 PM To: [EMAIL PROTECTED] Subject: Re: System Objects for Windows Brenda, The NT systemstate contains most (but not all of the same things that are backed up by the TSM System Object), so in that respect it captures more than whats held in ADMS.SYS I know that the System Files component of the System State contains many of the O.S related files for Windows 2000. This includes files that are held in the WINNT directory. However, I'm not sure if the System Files component includes the boot files that sit in the root for the drive (boot.ini etc). We backup the C drive anyway so even if the boot.ini, config.sys etc aren't captured as part of the Windows 2000 System State backup, they get included in the file system backups. I know that it's likely that we're 'double-dipping' some files but it's better than not getting them at all : -). Our typical backup schedule works as follows: 1. Use the Windows 2000 Scheduler to trigger NTbackup to backup the System State to a disk file. On a system without Active Directory the file size isaorund 300mb. For a domain controller with would obviousl be bigger depending upon the size of your AD. 2. After a reasonable time window (to allow NTbackup to do it's stuff), do a TSM backup of C drive , System Object plus any other drives you need. The file created as by NTbackup is then backed up at this point. Other than using NTbackup the only other way that I thought that you could get around this problem would be to rename the System Object filespace on the TSM server to correspond with the backup date (or someother unique name). That way it would always remain active. Then if you need to restore it, you just need to reamne it again before starting the recvoery process. However, I haven't had anytime to reseach this, so I don;t know how 'doable' this is. The Ntbackup method seemed to be the quicked way to acheive a result, although probably not the cleanest. Andrew Pearce BHP Server Engineering, CSC Australia PO Box 261, Warrawong, NSW 2502 email: [EMAIL PROTECTED] Tel: 0242 75 7135 Fax: 0242 75 7923 "Collins, Brenda" Brenda.Collins@WESTTo: [EMAIL PROTECTED] GROUP.COM cc: Sent by: "ADSM: DistSubject: Re: System Objects for Windows Stor Manager" [EMAIL PROTECTED] U 23/03/2001 01:53 AM Please respond to "ADSM: Dist Stor Manager" Andrew, Thank you for the feedback. I looked at this once and I believe it does the same thing the adsm.sys file does in terms of what it captures. What do you do about the boot.ini, config.sys, ntldr, etc. that you might want multiple copies of? They don't get put into the system objects stored in adsm.sys, are they kept with the NT backup? Brenda -Original Message- From: Andrew Pearce [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 4:43 PM To: [EMAIL PROTECTED] Subject: Re: System Objects for Windows Brenda, We schedule NTbackup to backup the Windows 2000 System State to disk and then pick this up as a file via TSM. Not particularly elegant, but as a short term fix it meets our requirements. You obviuosly need to be familar with a recovery process that incorparates NTbackup to do this. I've heard that the inactive system objects issue may be addressed in the next release of the client (4.2) - certainly hope so - can anyone confirm this? Andrew Pearce email: [EMAIL PROTECTED] "Collins, Brenda" Brenda.Collins@WESTTo: [EMAIL PROTECTED] GROUP.COM cc: Sent by: "ADSM: DistSubject: System Objects for Windows Stor Manager" [EMAIL PROTECTED] U 20/03/2001 03:51 AM Please respond to "ADSM: Dist Stor Manager" Has anyone implemented a solution they would be willing to share that will keep copies of inactive system objects? Brenda Collins, Storage Solutions Group Phone: 651-848-5808 Email: [EMAIL PROTECTED] Disclaimer: "The
Re: Storage pools and Cached files
I do not understand quite well what you try to accomplish. But anyhow, cached data on disk only remains until a new backup needs the space. In the tape you will have all the data from the different versions you are keeping. So it is normal that you have much more data on tape than on disk. If you want to maintain the data on disk forever you will need a very large disk storagepool. Regards Maria - Original Message - From: Gill, Geoffrey L. [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, March 22, 2001 11:05 PM Subject: Storage pools and Cached files I have not heard from anyone on this so I'm going to ask again. I can't seem to find an answer so my guess is I can't copy this data from tape to disk. I have a disk pool with cached data on it. It does copy to tha offsite pool and to tape in the 3494. For whatever reason the copy on the disk is not the same as tape. There seems to be much more data on tape and I need it on disk. Is it possible to copy this data from a primary tape pool, or copy pool, to the disk pool? If not, if I delete the data on the tape will TSM then back up all the data from the clients again? I do need to get this data back on disk, but since it's from 100+ different nodes I need the easiest way to accomplish this. Thanks, Geoff Gill NT Systems Support Engineer SAIC Computer Systems Group E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (888) 997-9614
Archive not grabbing all directories
I did some snooping and couldn't see anyone mention this one. I've got a script running on one box (HPUX 11, 4.1.2 client) to run an archive: dsmc archive -se=tsm_x1_apps -archmc=6month -subdir=yes\ -desc="ADSM X1-FVO2 Online Backup"\ "/etc/*.ora" \ "/p/util/oracle/adm/FVO2/*"\ "/db/x1_oravlB1/ORACLE/FVO2/*"\ "/db/x1_oravlB2/ORACLE/FVO2/*"\ "/db/x1_oravlB3/ORACLE/FVO2/*" \ "/db/x1_oravlB4/ORACLE/FVO2/*" \ "/db/x1_oravlB5/ORACLE/FVO2/dbf/*"\ "/db/x1_oravlB5/ORACLE/FVO2/ctl/*"\ "/db/x1_oravlB5/ORACLE/FVO2/log/"/p/util/oracle/admin/dba/FVO2/backups/FVO2 _online.`date +\%y\%m\%d` 21 /dev/null When the script runs, it goes as far as grabbing the oravlB1 directory and then stops. No error message, nothing. As if the script ended at that point. It correctly dumps to the log file noted, so I know it sees the entire line. We have a shwack of other boxes running scripts in this format that have no trouble. Any thoughs? Paul
Re: Recovery Log not reset after Incr. DB backup
Gerhard, I'm seeing the same behavior on my system. I haven't timed it so I don't know how long it takes, but querying the DB / log status immediately after a DB backup (we do mostly full backups) shows that the log hasn't been zeroed. Sometime later it shows 0% utilized. We went from ADSM 3.1 to TSM. ADSM 3.1 zeroed the log immediately. We are running TSM 4.1.2.0 on AIX 4.3.3. Tab Trepagnier (now) TSM Administrator Laitram Corporation Gerhard Rentschler [EMAIL PROTECTED] on 03/22/2001 07:36:05 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Tab Trepagnier/Corporation/Laitram/US) Subject: Recovery Log not reset after Incr. DB backup Hi, I frequently observe that the recovery log utilization is not reset immediately after a full or incremental DB backup. It happens much later, eg. 30 or 40 minutes after the backup finished. The last cases I watched no sessions or processes were active after the backup finished. I opened a PMR for this case. Has anyone else seen the problem? My server is TSM 4.1.2.0 on AIX 4.3.3. Best regards Gerhard --- Gerhard Rentschleremail:[EMAIL PROTECTED] Regional Computing Center tel. ++49/711/685 5806 University of Stuttgart fax: ++49/711/682357 Allmandring 30a D 70550 Stuttgart Germany
AW: System Objects for Windows
Hi togehter first of all: 1. after you finished installing an win2k you should create a repairdisk. there you have the files you need. if you change some important system files, you'll be prompted to refresh your repaidisk. 2. boot.ini is not located in adsm.sys. look at the schedlog. there you will find the boot.ini. (with TSM V4.1.2.12) 15-03-2001 22:02:27 Preparing System Object - System VolumeNormal File-- 185 \\servername\c$\boot.ini [Sent] 3. config.sys is not a needed file to startup win2k. this is only for old an not win2k certified applications. 4. multiple copies of system objects (files) are not supported by ibm (or ms?). may in the next release or version? ok,ok, i never restored a win2k with tsm, but it's in pending state on my todo-list. a restore with nt backup is easy, problem free. have a nice weekend cd -Ursprngliche Nachricht- Von: Rushforth, Tim [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 22. Mrz 2001 22:58 An: [EMAIL PROTECTED] Betreff: Re: System Objects for Windows NT Backup of System State does not include boot.ini, it does include ntldr and ntdetect.com. I don't think it contains config.sys. TSM DOES NOT backup boot.ini as a regular file. It does not back up any files that are included as part of the System Object. Renaming the System Object on TSM after the backup does work - I've tested this out. This is documented in the TSM with W2K redpiece. One reason to use the NT backup method is that it gives you the ability to archive the system state which you cannot do at all with TSM. Tim Rushforth City of Winnipeg -Original Message- From: Andrew Pearce [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 22, 2001 3:45 PM To: [EMAIL PROTECTED] Subject: Re: System Objects for Windows Brenda, The NT systemstate contains most (but not all of the same things that are backed up by the TSM System Object), so in that respect it captures more than whats held in ADMS.SYS I know that the System Files component of the System State contains many of the O.S related files for Windows 2000. This includes files that are held in the WINNT directory. However, I'm not sure if the System Files component includes the boot files that sit in the root for the drive (boot.ini etc). We backup the C drive anyway so even if the boot.ini, config.sys etc aren't captured as part of the Windows 2000 System State backup, they get included in the file system backups. I know that it's likely that we're 'double-dipping' some files but it's better than not getting them at all : -). Our typical backup schedule works as follows: 1. Use the Windows 2000 Scheduler to trigger NTbackup to backup the System State to a disk file. On a system without Active Directory the file size isaorund 300mb. For a domain controller with would obviousl be bigger depending upon the size of your AD. 2. After a reasonable time window (to allow NTbackup to do it's stuff), do a TSM backup of C drive , System Object plus any other drives you need. The file created as by NTbackup is then backed up at this point. Other than using NTbackup the only other way that I thought that you could get around this problem would be to rename the System Object filespace on the TSM server to correspond with the backup date (or someother unique name). That way it would always remain active. Then if you need to restore it, you just need to reamne it again before starting the recvoery process. However, I haven't had anytime to reseach this, so I don;t know how 'doable' this is. The Ntbackup method seemed to be the quicked way to acheive a result, although probably not the cleanest. Andrew Pearce BHP Server Engineering, CSC Australia PO Box 261, Warrawong, NSW 2502 email: [EMAIL PROTECTED] Tel: 0242 75 7135 Fax: 0242 75 7923 "Collins, Brenda" Brenda.Collins@WESTTo: [EMAIL PROTECTED] GROUP.COM cc: Sent by: "ADSM: DistSubject: Re: System Objects for Windows Stor Manager" [EMAIL PROTECTED] U 23/03/2001 01:53 AM Please respond to "ADSM: Dist Stor Manager" Andrew, Thank you for the feedback. I looked at this once and I believe it does the same thing the adsm.sys file does in terms of what it captures. What do you do about the boot.ini, config.sys, ntldr, etc. that you might want multiple copies of? They don't get put into the system objects stored in adsm.sys, are they kept with the NT backup? Brenda -Original Message- From: Andrew Pearce [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 4:43 PM To: [EMAIL PROTECTED] Subject: Re: System Objects for Windows Brenda, We schedule NTbackup to backup the Windows 2000 System State to disk and then pick this up as a file via TSM. Not particularly elegant, but as a short term fix it meets
Re: TSM 4.1 Client with 3.7.4 Server
I have a 3.7.4.0 *SM server on AIX 4.3.3. I have *SM clients 4.1.0.0 on AIX, NT 4.0
and Netware 5.0. (Also have 3.1.x.x and 3.7.x.x clients on all these flavors). No
problem I've noticed in several months with 4.1 clients other than the normal stuff
you get with any version. (Also have some TDP MSSQL 1.1.2.01 agents with the 4.1
clients on NT 4.0 with MS SQL 6.5 and 7.0 DB's)
David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH 321.434.5536
Pager 321.634.8230
Fax:321.434.5525
[EMAIL PROTECTED]
[EMAIL PROTECTED] 03/22/01 05:59AM
Chaps,
I pretty much already expect the answer to be a resounding "yes" on this one - but its
best to be sure...
Can we run 4.1 Clients with a 3.7.4 server on AIX 4.3.3
Cheers,
Kind Regards,
Roy Lake
TBG European IT
Tel: 0208 526 8883
E-Mail: [EMAIL PROTECTED]
** IMPORTANT INFORMATION **
This message is intended only for the use of the person(s) ("the Intended Recipient")
to whom it is addressed. It may contain information which is privileged and
confidential
within the meaning of applicable law. Accordingly any dissemination, distribution,
copying
or other use of this message or any of its content by any person other than the
Intended
Recipient may constitute a breach of civil or criminal law and is strictly prohibited.
The views in this message or it's attachments are that of the sender.
If you are not the Intended Recipient please contact the sender and dispose of this
email
as soon as possible. If in doubt contact the Tibbett Britten European IT Helpdesk
on 0870 607 6777 (UK) or +0044 870 607 6777 (Non UK).
"MMS health-first.org" made the following
annotations on 03/23/01 02:44:53
--
This message is for the named person's use only. It may contain confidential,
proprietary, or legally privileged information. No confidentiality or privilege is
waived or lost by any mistransmission. If you receive this message in error, please
immediately delete it and all copies of it from your system, destroy any hard copies
of it, and notify the sender. You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the intended
recipient. Health First reserves the right to monitor all e-mail communications
through its networks. Any views or opinions expressed in this message are solely
those of the individual sender, except (1) where the message states such views or
opinions are on behalf of a particular entity; and (2) the sender is authorized by
the entity to give such views or opinions.
Ý==
Re: Recovery Log not reset after Incr. DB backup
Gerhard, we have the same problem, TSM 4.1.2.0 on AIX 4.3.3. running RollForward mode. I takes up to 15 minutes until recovery log utilization is reset after a db backup. Karl -- Karl Roessmann Tel. +49-711-689-1657 Max-Planck-Institut FKF Fax. +49-711-689-1632 Postfach 800 665 70506 Stuttgart email [EMAIL PROTECTED]
