Re: ADSM/TSM Admin pay scale
Have a look at: http://adsmsalarysurvey.8m.com/ Cheers, Suad -- On Mon, Apr 16, 2001 at 09:56:47PM -0700, Dwight Wood wrote: > Hi everyone, I have searched the archives and found only a few postings > about the pay scale of ADSM/TSM Admins. But I didn't see any numbers out > there in the reply responses. So I am hoping that everyone out there can > assist me with this one. > I have been working with ADSM for 2 1/2 years, the last 1 1/2 has been full > time. I feel it is time for a raise, but HR doesn't because they say that > they have nothing to compare my position to. So I have been asked to dig up > some real numbers in order to justify an increase. So the question is "What > is everyone making?" Actually, I am looking for pay scales, a low-end and > high-end, not your exact annual pay. I don't need detailed job descriptions, > just a pay scale range, what area of the country/world you live in and > whether or not you are full time with ADSM. If you are not full time, what > would be your other main responsibility? > Thanks in advance for everyone's assistance with this! > > I realize that some of you might not want this info displayed on the list, > so feel free to send your response to me privately at [EMAIL PROTECTED] > _ > Get your FREE download of MSN Explorer at http://explorer.msn.com
ADSM/TSM Admin pay scale
Hi everyone, I have searched the archives and found only a few postings about the pay scale of ADSM/TSM Admins. But I didn't see any numbers out there in the reply responses. So I am hoping that everyone out there can assist me with this one. I have been working with ADSM for 2 1/2 years, the last 1 1/2 has been full time. I feel it is time for a raise, but HR doesn't because they say that they have nothing to compare my position to. So I have been asked to dig up some real numbers in order to justify an increase. So the question is "What is everyone making?" Actually, I am looking for pay scales, a low-end and high-end, not your exact annual pay. I don't need detailed job descriptions, just a pay scale range, what area of the country/world you live in and whether or not you are full time with ADSM. If you are not full time, what would be your other main responsibility? Thanks in advance for everyone's assistance with this! I realize that some of you might not want this info displayed on the list, so feel free to send your response to me privately at [EMAIL PROTECTED] _ Get your FREE download of MSN Explorer at http://explorer.msn.com
Error in NT Event Log of ADSM server
Hi Everybody, Do you have any idea what these errors from NT event log of adsm server? The description for Event ID ( 7 ) in Source ( AdsmScsi ) could not be found. It contains the following insertion string(s): \Device\mt0.0.0.5. The description for Event ID ( 11 ) in Source ( AdsmScsi ) could not be found. It contains the following insertion string(s): \Device\mt0.0.0.5. regards, Zosi Noriega Analyst, Data Management ITD - ADNOC P.O. BOX 898 UAE
Re: Restoring AIX (was Restoring Linux and Solaris)
Nice try Ray. I'm aware of your product, and I've passed details to a local var, so that he can include it in an upcoming tender. This being govrnment that won't be complete for at least 6 months. Regards Steve. >>> Ray Schafer <[EMAIL PROTECTED]> 13/04/2001 6:06:50 >>> Steve, I work for The Kernel Group, and we have a product that will allow you to to a Bare Metal Restore of AIX, Solaris, HP, and NT using the data in ADSM/TSM. The recovery is highly automated. We have solved the issues you found and more. You can check out our web site: http://www.tkg.com/bmr/tsm Steve Harris wrote: > I've got a similar query to those restoring Solaris and Linux but re AIX. > > It annoys me that while I have a full TSM backup of the AIX rootVG I can't use it. >The bare metal redbook is no use, it just says to use mksysb > > I've come up with a process which almost works assuming two bootable disks are >available > 1. Restore a standard mksysb image, which includes the TSM client to one disk > 2. Run the alt_disk_install command phases 1 & 2 to set up an alternate rootvg and >restore the most recent mksysb for the box (this is just to get filesystem sizes). > 3. Use standard TSM commands to restore the / /usr /var /home filesystems on the >alternate disk to the latest TSM backup > 4. run alt_disk_install phase 3 to setup the restored system for boot > 5. boot from alternate. > 6. clean up bootstrap disk > 7. remirror rootvg > > Unfortunately step 4 fails as the alt_disk_install command plays with the alternate >ODM in phases 1 & 2, but I revert to the original ODM in 3. > I need to restore the original ODM because minor details like software installations >are kept there. > > I really think that this process can be made to work if I could just save the >appropriate bits of the ODM at 2.1 and put them back at 3.1. The question is what >are the appropriate bits? > > Any AIX experts with good ODM knowledge out there? > > Regards > > Steve Harris > AIX and ADSM Admin > Queensland Health, Brisbane Australia
Re: move a tape library between servers
We did this moving from an SP Node to an S7A on AIX. We had the database on external disk so we did a database backup, shut everything down, varyed off the disk with the log and db on it. Ftped the other important files. Cabled the disk to the new machine, imported the adsm volume groups and brought everything up. -Original Message- From: Michael Pirker [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 9:05 AM To: [EMAIL PROTECTED] Subject: move a tape library between servers Hello, I have got the problem that I want to sunset an existing TSM server with 5 TB of data on a library. The library will be reused on another already existing TSM system that is in production. I do not like the idea of creating a big amount of exported nodes. This would take much to long to be completed and is much to resource intensive. Another problem is that I do not have the storage space for this. I'm looking for a way to just unplug the library from the source system and plug it to the target system without moving any data exept the data that describes the stored data on the library in the source TSM server. So I need something like a database backup that has to be restored on the new server without distroying the already existing data on the new TSM server. Did somebody already do this (I'm sure yes) - please help me and give me some ideas. Mit freundlichen Grüßen / best regards Michael Pirker
Re: Autosys and ADSM???
Have at look at Control M from BMC. >>> [EMAIL PROTECTED] 04/13/01 01:43am >>> We currently have Autosys scheduling a series of ADSM backups or Oracle databases as well as numerous batch jobs all of which are running on AIX client mahines on an SP system. The Autosys server currently resides on a seperate NT server. Management wants to migrate the Autosys server to an AIX platform. The instability of the NT platform has prompted us to consider this migration to AIX. However, considering the level of support we have received from Computer Associates, or lack of regarding their Autosys product, in fixing our Autosys/ADSM problems, as well as the fact that we will upgrade our ADSM system to the latest version of TSM, we are seriously considering another scheduler. Does anybody have this kind of AIX / ADSM / AUTOSYS setup? Any ideas or successes? Jaime Diaz SP2 Administrator House2Home Support Services, MIS 949-442-5725 [EMAIL PROTECTED]
LAN Free Backup to Diskpool
Does anybody know whether it is/will be possible to do LAN Free backup to a server diskpool? The disk pool in question is SAN attached to the TSM server, and the SAN could be extended to the client. Also, when will the Backup/Archive clients for NT, AIX, etc be enabled for LAN Free? _ William Mansfield Senior Consultant Solution Technology, Inc
Re: Expanding ADSM DB Using Raw Logical Volumes. help please
TSM development recommedns using JFS, not raw - but Jack's right, it sure is quiker using raw. Anybody have a summary of the pros and cons? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Palmadesso Jack Sent: Monday, April 16, 2001 4:36 PM To: [EMAIL PROTECTED] Subject: Re: Expanding ADSM DB Using Raw Logical Volumes. help please Thanks to everybody who helped out today. The Db extend went great and was actually quicker than doing this with a jfs file system because you don't have to do a dsmfmt. Here are the steps I took: chose 2 stg vols on different disks. made sure no sessions or processes were active that could affect those vols performed a move data on both vols varied both vols offline matched vols in ADSM with those in AIX and took note deleted both vols from ADSM In Smitty I was able to rename both vols instead of deleting them Added the new vols back into ADSM if you ever do this make sure you name the new vol with a leading "r" This is nessasary to let ADSM know that it is a raw volume. example: /dev/radsm_db4 performed an extend DB :-) -Original Message- From: Cook, Dwight E [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 11:15 AM To: Palmadesso Jack Cc: '[EMAIL PROTECTED]' Subject: RE: Expanding ADSM DB Using Raw Logical Volumes. help please actually you should be able to vary offline a storage volume... if you have clients currently accessing your server (pushing data) the proper way to set a stg volume to readonly so you may move data off it and delete it would be vary offline some_stg_vol upd some_stg_vol acc=reado vary online some_stg_vol move data some_stg_vol (when done) delete some_stg_vol then do the smitty voodoo magic to delete the logical volume and redefine it with the new name of your choice, followed up with define dbvol xxx define dbcopy xxx yyy extend db then :-) :-) :-) -Original Message- From: Palmadesso Jack [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 9:03 AM To: 'Cook, Dwight E' Cc: '[EMAIL PROTECTED]' Subject: RE: Expanding ADSM DB Using Raw Logical Volumes. help please Thank you. I have not went ahead with anything yet. I was suspicious of the dsmfmt command because there is no filname to specify with raw volumes! I inherited 2 old ADSM servers that are using all raw vols for ADSM. I've never had to work directly with the volumes before and the admin V3 manuals really don't say much about them. So now would this be the correct proceedure? Database backup already performed by the way. 1. Move Data from chosen storage pool vols 2. Vary off the volumes I have already chosen from ADSM Storage pool vols cannot be varied off so I guess move to the next step? 3. Delete the vols from ADSM 4. In Smitty rename the volumes to reflect new status of DB vols instead of stg vols 5. Define db vol and copy 6. Extend DB And it should all be happy? Jack -Original Message- From: Cook, Dwight E [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 9:02 AM To: Palmadesso Jack; [EMAIL PROTECTED] Subject: RE: Expanding ADSM DB Using Raw Logical Volumes. help please OOOPPPSss with raw logical volumes you can't run dsmfmt against them... you just do a define dbvol & define dbcopy with the /dev/rblah I've used raw volumes in the past for db & log vols, that works... now though, I tend to go ahead and use JFS files for db & log and raws for storage volumes but I went through a wave of improper handling of raw volumes in AIX 4.2, you should still be OK in aix 4.1 DWight -Original Message- From: Palmadesso Jack [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 7:39 AM To: [EMAIL PROTECTED] Subject: Expanding ADSM DB Using Raw Logical Volumes. help please One of our older ADSM servers DB hit 98% over the weekend. I am putting together a proceedure to grow its DB. As far as I can tell these are the steps I need to take. First here is the hardware and software levels. RS6k F30 ADSM 3.1.2 level 40 (has been running smooth as silk for years)upgrade to 4 in progress AIX 4.1.5 (I know its old) Breece Hill Q47 w/3 DLT 4000 (attached as standard SCSI Library) All Storage pools and DB vols are on Raw Logical Volumes. We use ADSM mirroring for DBs These are the steps I've come up with. 1. Move Data from chosen storage pool vols 2. Vary off the volumes I have already chosen from ADSM 3. Delete the vols from ADSM 4. In Smitty rename the volumes to reflect new status of DB vols instead of stg vols 5. Peform DSMFMT for DB on newly renamed vols. 6. Add vols (1 primary and 1 mirror) to ADSM DB 7. Extend DB Anybody see anything wrong with these steps? Jack Palmadesso Siemens Westinghouse Power Corp.
Re: Expanding ADSM DB Using Raw Logical Volumes. help please
Thanks to everybody who helped out today. The Db extend went great and was actually quicker than doing this with a jfs file system because you don't have to do a dsmfmt. Here are the steps I took: chose 2 stg vols on different disks. made sure no sessions or processes were active that could affect those vols performed a move data on both vols varied both vols offline matched vols in ADSM with those in AIX and took note deleted both vols from ADSM In Smitty I was able to rename both vols instead of deleting them Added the new vols back into ADSM if you ever do this make sure you name the new vol with a leading "r" This is nessasary to let ADSM know that it is a raw volume. example: /dev/radsm_db4 performed an extend DB :-) -Original Message- From: Cook, Dwight E [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 11:15 AM To: Palmadesso Jack Cc: '[EMAIL PROTECTED]' Subject: RE: Expanding ADSM DB Using Raw Logical Volumes. help please actually you should be able to vary offline a storage volume... if you have clients currently accessing your server (pushing data) the proper way to set a stg volume to readonly so you may move data off it and delete it would be vary offline some_stg_vol upd some_stg_vol acc=reado vary online some_stg_vol move data some_stg_vol (when done) delete some_stg_vol then do the smitty voodoo magic to delete the logical volume and redefine it with the new name of your choice, followed up with define dbvol xxx define dbcopy xxx yyy extend db then :-) :-) :-) -Original Message- From: Palmadesso Jack [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 9:03 AM To: 'Cook, Dwight E' Cc: '[EMAIL PROTECTED]' Subject: RE: Expanding ADSM DB Using Raw Logical Volumes. help please Thank you. I have not went ahead with anything yet. I was suspicious of the dsmfmt command because there is no filname to specify with raw volumes! I inherited 2 old ADSM servers that are using all raw vols for ADSM. I've never had to work directly with the volumes before and the admin V3 manuals really don't say much about them. So now would this be the correct proceedure? Database backup already performed by the way. 1. Move Data from chosen storage pool vols 2. Vary off the volumes I have already chosen from ADSM Storage pool vols cannot be varied off so I guess move to the next step? 3. Delete the vols from ADSM 4. In Smitty rename the volumes to reflect new status of DB vols instead of stg vols 5. Define db vol and copy 6. Extend DB And it should all be happy? Jack -Original Message- From: Cook, Dwight E [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 9:02 AM To: Palmadesso Jack; [EMAIL PROTECTED] Subject: RE: Expanding ADSM DB Using Raw Logical Volumes. help please OOOPPPSss with raw logical volumes you can't run dsmfmt against them... you just do a define dbvol & define dbcopy with the /dev/rblah I've used raw volumes in the past for db & log vols, that works... now though, I tend to go ahead and use JFS files for db & log and raws for storage volumes but I went through a wave of improper handling of raw volumes in AIX 4.2, you should still be OK in aix 4.1 DWight -Original Message- From: Palmadesso Jack [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 7:39 AM To: [EMAIL PROTECTED] Subject: Expanding ADSM DB Using Raw Logical Volumes. help please One of our older ADSM servers DB hit 98% over the weekend. I am putting together a proceedure to grow its DB. As far as I can tell these are the steps I need to take. First here is the hardware and software levels. RS6k F30 ADSM 3.1.2 level 40 (has been running smooth as silk for years)upgrade to 4 in progress AIX 4.1.5 (I know its old) Breece Hill Q47 w/3 DLT 4000 (attached as standard SCSI Library) All Storage pools and DB vols are on Raw Logical Volumes. We use ADSM mirroring for DBs These are the steps I've come up with. 1. Move Data from chosen storage pool vols 2. Vary off the volumes I have already chosen from ADSM 3. Delete the vols from ADSM 4. In Smitty rename the volumes to reflect new status of DB vols instead of stg vols 5. Peform DSMFMT for DB on newly renamed vols. 6. Add vols (1 primary and 1 mirror) to ADSM DB 7. Extend DB Anybody see anything wrong with these steps? Jack Palmadesso Siemens Westinghouse Power Corp.
Tape Library errors
Has anyone ran across these errors??? The errors re-generate when a process tries to access it. Thanks. 04/16/01 07:47:08 ANR8300E I/O error on library AUTOLIB (OP=C0106C03, CC=315, KEY=05, ASC=3B, ASCQ=0D, SENSE=70.00.05.00.00.00.00.0D.00.00.00.00.3B.0D.00.00.00- .00.3B.0D.00., Description=The destination slot or drive was full in an attempt to move a volume). Refer to Appendix B in the 'Messages' manual for recommended action. 04/16/01 08:07:11 ANR8300E I/O error on library AUTOLIB OP=C0106C03, CC=315, KEY=05, ASC=3B, ASCQ=0D, SENSE=70.00.05.00.00.00.00.0D.00.00.00.00.3B.0D.00.00.00- .00.3B.0D.00., Description=The destination slot or drive was full in an attempt to move a volume). Refer to Appendix B in the 'Messages' manual for recommended action. 04/16/01 08:27:14 ANR8300E I/O error on library AUTOLIB (OP=C0106C03, CC=315, KEY=05, ASC=3B, ASCQ=0D, SENSE=70.00.05.00.00.00.00.0D.00.00.00.00.3B.0D.00.00.00- .00.3B.0D.00., Description=The destination slot or drive was full in an attempt to move a volume). Refer to Appendix B in the 'Messages' manual for recommended action. 04/16/01 08:48:01 ANR8300E I/O error on library AUTOLIB (OP=C0106C03, CC=315, KEY=05, ASC=3B, ASCQ=0D, SENSE=70.00.05.00.00.00.00.0D.00.00.00.00.3B.0D.00.00.00- .00.3B.0D.00., Description=The destination slot or drive was full in an attempt to move a volume). Refer to Appendix B in the 'Messages' manual for recommended action. _ Get your FREE download of MSN Explorer at http://explorer.msn.com
Re: Library audit (AGAIN)
You can find the mtlib command in the following book: IBM SCSI Tape Drive, Medium Changer, and Library Device Drivers: IBM_scsi_tape_iug.pdf from ftp://ftp.software.ibm.com/storage/devdrvr/ Regards Maria
Re: Expanding ADSM DB Using Raw Logical Volumes. help please
actually you should be able to vary offline a storage volume... if you have clients currently accessing your server (pushing data) the proper way to set a stg volume to readonly so you may move data off it and delete it would be vary offline some_stg_vol upd some_stg_vol acc=reado vary online some_stg_vol move data some_stg_vol (when done) delete some_stg_vol then do the smitty voodoo magic to delete the logical volume and redefine it with the new name of your choice, followed up with define dbvol xxx define dbcopy xxx yyy extend db then :-) :-) :-) -Original Message- From: Palmadesso Jack [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 9:03 AM To: 'Cook, Dwight E' Cc: '[EMAIL PROTECTED]' Subject: RE: Expanding ADSM DB Using Raw Logical Volumes. help please Thank you. I have not went ahead with anything yet. I was suspicious of the dsmfmt command because there is no filname to specify with raw volumes! I inherited 2 old ADSM servers that are using all raw vols for ADSM. I've never had to work directly with the volumes before and the admin V3 manuals really don't say much about them. So now would this be the correct proceedure? Database backup already performed by the way. 1. Move Data from chosen storage pool vols 2. Vary off the volumes I have already chosen from ADSM Storage pool vols cannot be varied off so I guess move to the next step? 3. Delete the vols from ADSM 4. In Smitty rename the volumes to reflect new status of DB vols instead of stg vols 5. Define db vol and copy 6. Extend DB And it should all be happy? Jack -Original Message- From: Cook, Dwight E [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 9:02 AM To: Palmadesso Jack; [EMAIL PROTECTED] Subject: RE: Expanding ADSM DB Using Raw Logical Volumes. help please OOOPPPSss with raw logical volumes you can't run dsmfmt against them... you just do a define dbvol & define dbcopy with the /dev/rblah I've used raw volumes in the past for db & log vols, that works... now though, I tend to go ahead and use JFS files for db & log and raws for storage volumes but I went through a wave of improper handling of raw volumes in AIX 4.2, you should still be OK in aix 4.1 DWight -Original Message- From: Palmadesso Jack [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 7:39 AM To: [EMAIL PROTECTED] Subject: Expanding ADSM DB Using Raw Logical Volumes. help please One of our older ADSM servers DB hit 98% over the weekend. I am putting together a proceedure to grow its DB. As far as I can tell these are the steps I need to take. First here is the hardware and software levels. RS6k F30 ADSM 3.1.2 level 40 (has been running smooth as silk for years)upgrade to 4 in progress AIX 4.1.5 (I know its old) Breece Hill Q47 w/3 DLT 4000 (attached as standard SCSI Library) All Storage pools and DB vols are on Raw Logical Volumes. We use ADSM mirroring for DBs These are the steps I've come up with. 1. Move Data from chosen storage pool vols 2. Vary off the volumes I have already chosen from ADSM 3. Delete the vols from ADSM 4. In Smitty rename the volumes to reflect new status of DB vols instead of stg vols 5. Peform DSMFMT for DB on newly renamed vols. 6. Add vols (1 primary and 1 mirror) to ADSM DB 7. Extend DB Anybody see anything wrong with these steps? Jack Palmadesso Siemens Westinghouse Power Corp.
Re: file name too long when?
Anne, the book that is wrong. See APAR IC29922. 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." "Short, Anne" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 04/16/2001 08:18:20 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: file name too long when? Sorry, Andy, but you've just confused me. Per the "TSM Manager for Windows Using the Backup-Archive Client" manual, in Chapter 8 - Setting Common Options: - LANGUAGE - AMENG (American English) is the default - USEUNICODEFILENAMES - NO is the default So how can the statement in the APAR text below be true?? - The default value for USEUNICODEFILENAMES is YES when LANGUAGE AMENG is in effect. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management
Re: move a tape library between servers
No, you can't do either: move the library with it's data to the new server, nor move the database of the old server to the new without destroying data. You could run two instances of TSM on the new server: one talking to your new hardware and the other talking to the old. However, in this setup, your clients would be talking to two TSM servers. At least for a while until the data on the old library expires. For data that isn't going to expire soon, you could do an export of that data and an import on the new server. 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 Michael Pirker Sent: Monday, April 16, 2001 8:05 AM To: [EMAIL PROTECTED] Subject: move a tape library between servers Hello, I have got the problem that I want to sunset an existing TSM server with 5 TB of data on a library. The library will be reused on another already existing TSM system that is in production. I do not like the idea of creating a big amount of exported nodes. This would take much to long to be completed and is much to resource intensive. Another problem is that I do not have the storage space for this. I'm looking for a way to just unplug the library from the source system and plug it to the target system without moving any data exept the data that describes the stored data on the library in the source TSM server. So I need something like a database backup that has to be restored on the new server without distroying the already existing data on the new TSM server. Did somebody already do this (I'm sure yes) - please help me and give me some ideas. Mit freundlichen Gr|_en / best regards Michael Pirker
Re: TDP for Domino problems with TSM server?
TDP for Domino should not abend the TSM server no matter the level(s). Are you sure the abend was not caused by the volume errors? You may want to pursue this via the normal service stream... Thanks, Bill William Degli-Angeli IGS TDP Development Endicott, NY (607) 752-6749 Internet [EMAIL PROTECTED] Tim Williams cc: Sent by: "ADSM: Dist Subject: TDP for Domino problems with TSM server? Stor Manager" <[EMAIL PROTECTED]> 04/13/2001 12:03 Please respond to "ADSM: Dist Stor Manager" I am having a unusual problem with a TDP client and TSM server. Does anyone know of any problems with TDP for Domino and TSM servers below 4.1 ? I am upgrading a NT client that has TSM 3.7.2.18 and the TDP for Domino. After I upgrade the 3.7.2.18 version to 4.1.2.12 and kick off a TDP for domino backup of a database it crashes our TSM server. I have tested this on TSM versions of 3.7.1, 3.7.2 & 3.7.4. There are no error msgs in the activity log, just a connection comment. 04/13/2001 10:37:51 ANR0406I Session 50 started for node DOM_GSBS3WM (TDP Domino NT) (Tcp/Ip 10.34.98.91(1190)). 04/13/2001 10:50:33 ANR1412W Volume 034228 access mode is "unavailable". 04/13/2001 10:50:33 ANR1412W Volume 034202 access mode is "unavailable". 04/13/2001 10:50:33 ANR1414W Volume 034200 access mode is "read-only" due to previous write error. 04/13/2001 10:50:33 ANR1414W Volume 034264 access mode is "read-only" due to previous write error. If I backup to a TSM 4.1 client there are no problems. If I clean off the TDP for Domino client before upgrading the flatfile client, then install the TDP client I can backup to any version server. Any hint/guess/comments/answer would be helpful Thanks [EMAIL PROTECTED]
Re: file name too long when?
Sorry, Andy, but you've just confused me. Per the "TSM Manager for Windows Using the Backup-Archive Client" manual, in Chapter 8 - Setting Common Options: - LANGUAGE - AMENG (American English) is the default - USEUNICODEFILENAMES - NO is the default So how can the statement in the APAR text below be true?? - The default value for USEUNICODEFILENAMES is YES when LANGUAGE AMENG is in effect. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management -Original Message- From: Andy Raibeck [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 9:40 AM To: [EMAIL PROTECTED] Subject: file name too long when? APAR IC27346 discusses this problem. This was fixed in an earlier 3.7.2.x patch, and the permanent fix went in to the 4.1.1.0 (and later) versions. I recommend that customers use either 3.7.2.19 or 4.1.2.12. I have included the text of the APAR below. Note that in the "RECOMMENDATION" section of the text, it says to not apply new maintenance until the fixing PTF is available. "Fixing PTF" was a reference to 4.1.1.0, which was not available at the time this APAR text was written. This fix was *not* available in 4.1.0.x, so the point of this caveat was to tell users who install 3.7.2.19 not to go to 4.1.0.x, but to wait for 4.1.1.0 (or higher). BEGIN APAR TEXT ABSTRACT: WINDOWS CLIENT CAN NOT BACK UP FILES WHOSE NAMES EXCEED THE WINDOWS OS LIMIT OF 260 CHARACTERS. ERROR DESCRIPTION: Windows permits a maximum path length of 260 characters (259 usable characters plus 1 for the string terminator). However, under certain conditions, the operating system permits files of greater lengths to be created. As a result, when the TSM Windows client attempts to access files whose path lengths exceed the OS limit, the I/O operation fails with Win32 return code 206 (ERROR_FILENAME_EXCED_RANGE). PROBLEM SUMMARY: * USERS AFFECTED: Windows client on NT and 2000. * * PROBLEM DESCRIPTION: The Windows client is unable to process * *files and directories whose names exceed the operating* *system-defined length of 259 characters. * * RECOMMENDATION: Apply fixing PTF when available. Users of* *fixtest 3.7.2.16 must not apply new maintenance until * *the fixing PTF for this APAR is available.* PROBLEM CONCLUSION: The Windows operating system defines a maximum path length of 260 characters (259 usable characters plus 1 character to terminate the path). However, under certain circumstances, it is possible to create files whose path lengths violate this limit. When this happens, many programs, including Windows Explorer, Notepad.exe, TSM, etc., can not access these files. The Microsoft Win32 API file I/O functions provide a circumvention to this problem that has been incorporated into the TSM client. The client will now be able to support (i.e. backup, restore, archive, retrieve) files that exceed the 259 character limit provided that the USEUNICODEFILENAMES NO client option is in effect. If USEUNICODEFILENAMES is set to YES, then the client will not be able to support these files. The following information should be noted with regard to this fix: - USEUNICODEFILENAMES NO must be in effect (as mentioned above). If USEUNICODEFILENAMES YES is in effect, then these longer file names are unsupported. Users should always use USEUNICODEFILENAMES NO unless they have Mac volumes. If users need to support both Mac volumes AND these longer file names, then they will need to make provisions to run backups for the Mac volumes separately from the non-Mac files, backing up the Mac volumes with USEUNICODEFILENAMES YES, and the non-Mac files with USEUNICODEFILENAMES NO. The default value for USEUNICODEFILENAMES is YES when LANGUAGE AMENG is in effect. For other LANGUAGE settings, the default for USEUNICODEFILENAMES is NO. Thus when LANGUAGE AMENG is in effect, users must explicitly code USEUNICODEFILENAMES NO in their client options file. - The maximum supported length of the file name itself (not including the directory in which it resides), is 255 characters. - The maximum supported length of the directory portion of the path in which the file resides (not including the file itself) is 1,024 characters. - The maximum supported length of any component within a directory path can not exceed 255 characters. "Component" refers to a part of a directory structure as delimited by the backslash character. To illustrate: Given a path of the form: x:/comp1/comp2/comp3/filename Each component "compx" can not exceed 255 characters. Likewise, "filename" c
Re: AIX Gurus.. .Help Needed..
# oslevel -q Known Maintenance Levels 4.3.3.0 4.3.2.0 4.3.1.0 Shawn Raymond <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 04/16/2001 09:21:02 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: AIX Gurus.. .Help Needed.. How about an oslevel -q ? -- Shawn Raymond Sr. Technical Consultant Synergy, Inc. 518-782-3457 Shekhar DhotreTo: [EMAIL PROTECTED] Subject: Re: AIX Gurus.. .Help Needed.. Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] EDU> 04/12/01 02:52 PM Please respond to "ADSM: Dist Stor Manager" # oslevel -l 4.3.3.0 # RETURNS NOTHING .. Shawn Raymond <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 04/12/2001 02:39:44 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: AIX Gurus.. .Help Needed.. Run oslevel -l 4.3.3.0 to list the filesets that are not up to date. You may have to do an update_all on all 4 of the AIX 4.3.3 CD's then run the ML8 update_all again. -- Shawn Raymond Sr. Technical Consultant Synergy, Inc. 518-782-3457 Shekhar DhotreTo: [EMAIL PROTECTED] Subject: Re: AIX Gurus.. .Help Needed.. Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] EDU> 04/10/01 06:04 PM Please respond to "ADSM: Dist Stor Manager" I installed ML08 on AIX 4.3.3 .0 today and issued command # oslevel 4.3.2.0 # instfix -ik 4330-08_AIX_ML All filesets for 4330-08_AIX_ML were found. # instfix -ciqk 4330-08_AIX_ML | grep ":-:" is this ok ---4.3.2.0 ? Shekhar Dhotre UniX /Tivoli Admin . Bayer Corp. 508-520-7821 . Shawn Raymond <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 04/10/2001 08:46:03 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: AIX Gurus.. .Help Needed.. Update your perfagent.tools to 2.2.33.50. svmon was broken in the previous few releases. -- Shawn Raymond Sr. Technical Consultant Synergy, Inc. 518-782-3457 Shekhar DhotreTo: [EMAIL PROTECTED] Subject: Re: AIX Gurus.. .Help Needed.. Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] EDU> 04/09/01 04:53 PM Please respond to "ADSM: Dist Stor Manager" I am trying to execute svmon but , getting following error ..any idea ? medrs2:ps -aef | grep dsmserv root 42134 1 0 Apr 02 - 2474:14 dsmserv root 48518 47810 1 16:36:56 pts/10 0:00 grep dsmserv medrs2:sh /usr/bin/svmon -P 42134 sh: /usr/bin/svmon: 0403-006 Execute permission denied. medrs2:id uid=0(root) gid=0(system) groups=2(bin),3(sys),7(security),8(cron),10(audit) medrs2: medrs2:svmon open: No such file or directory medrs2:/usr/bin/svmon open: No such file or directory medrs2:cd /usr/bin medrs2:./svmon open: No such file or directory medrs2:sh svmon sh: svmon: 0403-006 Execute permission denied. medrs2:echo $PATH /usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin Thanks shekhar .. George Lesho <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 04/09/2001 03:19:45 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: AIX Gurus.. .Help Needed.. Herve, Where am going wrong here??? # ps -aef | grep dsmserv root 30300 34772 0 Apr 07 - 606:00 dsmserv quiet # svmon -P 30300 Pid Command Inuse Pin Pgspace 64-bit 30300*** process does not exist *** Drop me a note off line and help me out... I am not sure why it is coming back and saying that my TSM server is not running thanks- George Lesho Storage/System Admin AFC Enterprises "Chibois, Herve" <[EMAIL PROTECTED]> on 04/06/2001 10:23:05 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc:(bcc: George Lesho/Partners/AFC) Fax to: Subject: Re: AIX Gurus.. .Help Needed.. Hi Richard, to know exactly how many RAM TSM is eating, try the following : % ps -eaf
Re: Should LOADDB take this long?
Quoting William Boyer <[EMAIL PROTECTED]>: > TSM 3.7.3.0 running on OS/390 2.9 > > Last night our automated processes to shut the system down didn't take > into > account that TSM would take a few extra minutes to halt due to > reclamation > running. The automation script ended up taking TCPIP and CA-TLMS and > DFSMSRmm (in warn mode) down while TSM was still up and trying to close > out > his tape processing. TSM ended up abending with a EC6. After our > downtime, > TSM wouldn't come back up. It would sit there in a CPU loop with no I/O. > The > last message in the joblog was "ANR0306I Recovery log volume mount in > progress." WOuld come up any farther. [Material deleted] > Also, if anyone has any ideas on how I could have averted having to do > the > DUMP/LOADDB processes I would be more than happy to hear them. I just > couldn't think of any way to bypass the recovery log processing during > startup, or to have the load cleared by itself. We have a TSM server, and used to have exactly the combinatation of release levels mentioned above. One day we did a system IPL and were unable to bring up the TSM server. There was no sign of trouble with the shutdown before the IPL, but the TSM initialization failure was just as described above. We called IBM and were advised to upgrade the server code to 3.7.4.0. We downloaded the code from an IBM FTP server, installed it, and were able to bring up the TSM server.
Re: Should LOADDB take this long?
There was a bug that caused TSM to hang coming up at "Recovery log mount in progress". And it just never comes up. I know it hit the NT server and AIX server at 3.7.2, and was fixed in 3.7.4. Not sure about OS/390, but check into it. I expect you need to upgrade to 3.7.4, or you will be subject to this happening again. Just putting on the fix was all we had to do, and TSM came right back up, did not have to restore the DB. -Original Message- From: William Boyer [mailto:[EMAIL PROTECTED]] Sent: Sunday, April 15, 2001 5:50 PM To: [EMAIL PROTECTED] Subject: Should LOADDB take this long? TSM 3.7.3.0 running on OS/390 2.9 Last night our automated processes to shut the system down didn't take into account that TSM would take a few extra minutes to halt due to reclamation running. The automation script ended up taking TCPIP and CA-TLMS and DFSMSRmm (in warn mode) down while TSM was still up and trying to close out his tape processing. TSM ended up abending with a EC6. After our downtime, TSM wouldn't come back up. It would sit there in a CPU loop with no I/O. The last message in the joblog was "ANR0306I Recovery log volume mount in progress." WOuld come up any farther. I managed to get an DUMPDB to run and it took only 1/2 hour and dumped over 78million database entries for a total of 6.9MB. I then did a FORMAT for all the db/log volumes and started the LOADDB last night at 20:15. It is still running and it is now 22 hours later and has only processed 70million of those database entries. I searched the archives, but there wasn't much on LOADDB. Should LOADDB take this long when the DUMPDB only took 1/2hour? Good thing this is a holiday weekend or the users and managers would be more upset than they are. I tell them, Hey it wasn't my shutdown script that corrupted the system!!! Also, if anyone has any ideas on how I could have averted having to do the DUMP/LOADDB processes I would be more than happy to hear them. I just couldn't think of any way to bypass the recovery log processing during startup, or to have the load cleared by itself. TIA, Bill Boyer "Some days you are the bug, some days you are the windshield." - ??
Re: Question on del volhist
Hi Glenn, Yes, all my tapes, primary and copy pools, are managed as SCRATCH. When a DR/copy pool tape becomes empty through reclamation, if is a stgpool tape and you have a REUSEDELAY set on the stgpool, it first becomes PENDING. It's DRM status is still VAULT. It stays in PENDING state for REUSEDELAY days, then it goes to EMPTY. At that point, the DRM status changes from VAULT to VAULTRETRIEVE. At that point, you should make arrangements to bring the tapes in VAULTRETRIEVE status back onsite. The next MOVE DRMEDIA you do, the DRM status changes to COURIERRETRIEVE. The stgpool status is still EMPTY. (You can skip the COURIERRETREIEVE status if you want.) One the tapes are back onsite, you are supposed to do a MOVE DRMEDIA to state ONSITERETRIEVE. THis is a little sneaky, because the tapes don't stay in that state. As soon as you move them to ONSITERETRIEVE, if you look carefully at the log, you will see TSM immediately deletes them from the storage pool. If you have already checked them back into the library, they will go back into library scratch status. If you haven't already checked them back in, then yes, they "disappear" and are shown nowhere in TSM. But at that point, you should put them back in the library and check them in as scratch. DRM doesn't do that checkin for you; when you bring the tapes back, you have to do the checkin yourself. We don't have any problem with this working OK. You just have to make sure that you (or your operations staff) has explicit instructions to make sure that the tapes get brought back onsite before somebody does that last MOVE DRMEDIA that gets them changed back to ONSITERETRIEVE, and thereby deleted from the storage pool listing. (As for your question about volhist, scratch tapes are not tracked there. Tapes become "scratch" by being checked into the library in scratch status. YOu can only see "scratch" tapes by looking at the library inventory: q libv) Hope this helps.. Wanda Prather The Johns Hopkins Applied Physics Lab 443-778-8769 [EMAIL PROTECTED] "Intelligence has much less practical application than you'd think" - Scott Adams/Dilbert -Original Message- From: Glenn MacIntosh [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 8:58 AM To: [EMAIL PROTECTED] Subject: Re: Question on del volhist Wanda, The issue that I THINK I have, is that I am using scratch tapes for all pools (copypools as well). Are your copypools private or scratch ?What I think happens, is that when a DR tape becomes empty (through expiration/reclamation), and changes from VAULT to VAULTRETRIEVE, that since it is a scratch tape, with no data on it, and not in my library (q libv), that it will simply cease to exist. If you are using category private tapes, you will not see this problem. If your tapes are scratch and still contain data, (status vault) you will not see this problem. Would an empty scratch tape only be tracked by volhistory entries ? (Where else would you find an entry for an empty scratch ?) P.S. Sorry for inadvertently replying to Kelly instead of the listserv. Thanks, Glenn MacIntosh Manager of Technical Services Sobeys Inc. 123 Foord St. Stellarton, Nova Scotia (902) 752-8371 Ext. 4017 -Original Message- From: Prather, Wanda [mailto:[EMAIL PROTECTED]] Sent: Friday, April 13, 2001 1:54 PM To: [EMAIL PROTECTED] Subject: Re: Question on del volhist OK, I ran a DELETE VOLHIST for all record types all the way back to January. I checked on the oldest volumes in my OFFSITE copypool, which are marked VAULT by DRM. They no longer have ANY entry in the volume history file; running select * from volhistory where volume_name='xx' gets no hits at all, but Q DRMEDIA * still shows that volume xx is marked VAULT. So I still believe that removing STGNEW/STGDELETE via DELETE VOLHIST has NO effect on storage pool volumes. But it will make to "disappear" volumes that are tracked ONLY via VOLUMEHISTORY, including DBBACKUP, DBSNAPSHORT, and EXPORT entries. Wanda Prather The Johns Hopkins Applied Physics Lab 443-778-8769 [EMAIL PROTECTED] "Intelligence has much less practical application than you'd think" - Scott Adams/Dilbert -Original Message- From: Kelly J. Lipp [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 12, 2001 12:12 PM To: [EMAIL PROTECTED] Subject: Re: Question on del volhist This was not my observation, but rather that of Glenn MacIntosh. I don't know if this is what happens or not. Glenn had responded to me and not to the list so I thought I'd post his reply to garner further input on the assertion. I wouldn't think deleting volhist records would cause this to happen in DRM. Kell
Library audit (AGAIN)
This is truly a surprise to find this happening so soon after the problem I listed last week. That one I still haven't fixed. The first problem is tapes in the library: U00288 0064 00 10 00 U01063 0064 00 10 00 U01076 0064 00 10 00 U01077 0064 00 10 00 that are supposed to be in the vault, which they are not because I looked myself. U00288 Vault09/25/00 11:22:21 U01063 Vault04/03/01 14:03:03 U01076 Vault04/03/01 14:03:03 U01077 Vault04/03/01 14:03:03 They won't check out through TSM. Now the problem is tapes that were in the vault this morning, moved to onsiteretrieve, put in the library, but won't check in to TSM, it thinks they are not there for whatever reason. U00136 FF00 00 10 00 U00151 FF00 00 10 00 I ran an audit on the library on Friday through TSM, now I'm wondering if there is a way to audit the library through AIX, then reaudit the library through TSM and have it pick up the changes. I don't have any books to refer to with the mtlib commands so I don't know what to do. If anyone knows an online manual with this stuff it would help. I'll probably call TSM on this but if anyone has any ideas that might help it would also be appreciated. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (888) 997-9614
Re: Can not checkout the tape through scheduled job
Some admin commands are not allowed for scheduling as admin schedules. However, you CAN schedule a RUN command that executes a TSM server script. . So if you put your CHECKOUT command in a named TSM server script, you should be able to schedule the script as "run scriptname". I schedule my CHECKINs that way.. -Original Message- From: Ganu Sachin, IBM [mailto:[EMAIL PROTECTED]] Sent: Friday, April 13, 2001 12:26 AM To: [EMAIL PROTECTED] Subject: Can not checkout the tape through scheduled job Hi, A query about TSM Administrative scheduling. We have TSM ,configured on AIX 4.3.3. I want to schedule a task which will checkout the volume. The volume is used for tsm database backup. When I define a new administrative task for checkout, I am getting following error. The command is used in the scheduling task is " CHECKOUT LIBVOLUME LIB0 TSK071 CHECKLABEL=NO FORCE=NO REMOVE=NO". I do not want to set FORCE option to YES. But if, I run the same command from server command prompt, command executed successfully. ERROR :- "ANR2755E DEFINE SCHEDULE or UPDATE SCHEDULE parameter CMD='CHECKOUT LIBVOLUME LIB0 TSK071 CHECKLABEL=NO FORCE=NO REMOVE=NO' - not eligible for scheduling. " Pls tell me whether it is possible to schedule the administrative task for checking out the volume, if yes pls explain. Thanks in advance Sachin Ganu
move a tape library between servers
Hello, I have got the problem that I want to sunset an existing TSM server with 5 TB of data on a library. The library will be reused on another already existing TSM system that is in production. I do not like the idea of creating a big amount of exported nodes. This would take much to long to be completed and is much to resource intensive. Another problem is that I do not have the storage space for this. I'm looking for a way to just unplug the library from the source system and plug it to the target system without moving any data exept the data that describes the stored data on the library in the source TSM server. So I need something like a database backup that has to be restored on the new server without distroying the already existing data on the new TSM server. Did somebody already do this (I'm sure yes) - please help me and give me some ideas. Mit freundlichen Grüßen / best regards Michael Pirker
Re: Expanding ADSM DB Using Raw Logical Volumes. help please
Thank you. I have not went ahead with anything yet. I was suspicious of the dsmfmt command because there is no filname to specify with raw volumes! I inherited 2 old ADSM servers that are using all raw vols for ADSM. I've never had to work directly with the volumes before and the admin V3 manuals really don't say much about them. So now would this be the correct proceedure? Database backup already performed by the way. 1. Move Data from chosen storage pool vols 2. Vary off the volumes I have already chosen from ADSM Storage pool vols cannot be varied off so I guess move to the next step? 3. Delete the vols from ADSM 4. In Smitty rename the volumes to reflect new status of DB vols instead of stg vols 5. Define db vol and copy 6. Extend DB And it should all be happy? Jack -Original Message- From: Cook, Dwight E [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 9:02 AM To: Palmadesso Jack; [EMAIL PROTECTED] Subject: RE: Expanding ADSM DB Using Raw Logical Volumes. help please OOOPPPSss with raw logical volumes you can't run dsmfmt against them... you just do a define dbvol & define dbcopy with the /dev/rblah I've used raw volumes in the past for db & log vols, that works... now though, I tend to go ahead and use JFS files for db & log and raws for storage volumes but I went through a wave of improper handling of raw volumes in AIX 4.2, you should still be OK in aix 4.1 DWight -Original Message- From: Palmadesso Jack [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 7:39 AM To: [EMAIL PROTECTED] Subject: Expanding ADSM DB Using Raw Logical Volumes. help please One of our older ADSM servers DB hit 98% over the weekend. I am putting together a proceedure to grow its DB. As far as I can tell these are the steps I need to take. First here is the hardware and software levels. RS6k F30 ADSM 3.1.2 level 40 (has been running smooth as silk for years)upgrade to 4 in progress AIX 4.1.5 (I know its old) Breece Hill Q47 w/3 DLT 4000 (attached as standard SCSI Library) All Storage pools and DB vols are on Raw Logical Volumes. We use ADSM mirroring for DBs These are the steps I've come up with. 1. Move Data from chosen storage pool vols 2. Vary off the volumes I have already chosen from ADSM 3. Delete the vols from ADSM 4. In Smitty rename the volumes to reflect new status of DB vols instead of stg vols 5. Peform DSMFMT for DB on newly renamed vols. 6. Add vols (1 primary and 1 mirror) to ADSM DB 7. Extend DB Anybody see anything wrong with these steps? Jack Palmadesso Siemens Westinghouse Power Corp.
Re: Question on del volhist (recanted)
All, I'm running some tests now ... and it looks like the volumes stay in VAULTRETRIEVE status as they should. I guess what might have happened is that we may have changed the state and caused the volumes to disappear.I will do some more testing, and IF I find anything amiss, I will update the listserv. For now, please treat the previous notes as the "premature ranting of a madman". Sorry. Glenn -Original Message- From: Prather, Wanda [mailto:[EMAIL PROTECTED]] Sent: Friday, April 13, 2001 1:54 PM To: [EMAIL PROTECTED] Subject: Re: Question on del volhist OK, I ran a DELETE VOLHIST for all record types all the way back to January. I checked on the oldest volumes in my OFFSITE copypool, which are marked VAULT by DRM. They no longer have ANY entry in the volume history file; running select * from volhistory where volume_name='xx' gets no hits at all, but Q DRMEDIA * still shows that volume xx is marked VAULT. So I still believe that removing STGNEW/STGDELETE via DELETE VOLHIST has NO effect on storage pool volumes. But it will make to "disappear" volumes that are tracked ONLY via VOLUMEHISTORY, including DBBACKUP, DBSNAPSHORT, and EXPORT entries. Wanda Prather The Johns Hopkins Applied Physics Lab 443-778-8769 [EMAIL PROTECTED] "Intelligence has much less practical application than you'd think" - Scott Adams/Dilbert -Original Message- From: Kelly J. Lipp [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 12, 2001 12:12 PM To: [EMAIL PROTECTED] Subject: Re: Question on del volhist This was not my observation, but rather that of Glenn MacIntosh. I don't know if this is what happens or not. Glenn had responded to me and not to the list so I thought I'd post his reply to garner further input on the assertion. I wouldn't think deleting volhist records would cause this to happen in DRM. 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 Prather, Wanda Sent: Thursday, April 12, 2001 9:57 AM To: [EMAIL PROTECTED] Subject: Re: Question on del volhist Yikes, I didn't know that! Thanks for pointing it out. If you think you have tapes disappearing and don't want to do a manual audit, you can write an audit program/script. 1)Pull a list of tapes that are physically in the library: q libv 2)Pull a list of tapes that are in DRM VAULT status: q drmedia * wherest=vault 3)Create a list of tapes that SHOULD be accounted for (either generate a tape range, if it's contiguous, or build a static list in a file). Have your script compare the volsers in list (3) to list (1) + (2). ANything that is on list 3, but isn't in either list (1) or (2), is MIA. It's much easier to go to the vault looking for a specific VOLSER, than to audit everything in there... I also run a script that compares (1) to (2) at least once a month, to make sure everything that was supposed to go to the vault actually did... -Original Message- From: Kelly J. Lipp [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 12, 2001 10:52 AM To: [EMAIL PROTECTED] Subject: FW: Question on del volhist Okay .. since we're talking del volhist ... Can someone clarify this point with the del volhist ? If I am using scratch tapes (no private tapes), and I am using the DR Module. It seems to me that if I have a DR tape, offsite, and empty (in retrieve state) and I delete the volhist entry, the tape seems to disappear totally from view. (i.e. a "q drm" command will no longer show it). I believe that scratch tapes will disappear if they are empty ... not a big deal if you know which ones they are, but if they disappear from view before you bring them back on site, how would you find them (without performing a manual offsite audit) ? (It is my understanding that tapes change from pending to empty "reuse" number of days (exactly) after they have gone pending. So you could have tapes changing from pennding to empty any time "3" days from the time the expiration freed it up.) How is anyone handling this (or are you doing what I'm doing and not deleting the volhist) ? Should I run my expiration weekly instead of daily ? Then I would know when my tapes would be changing to empty. Thanks, Glenn MacIntosh Manager of Technical Services Sobeys Inc. 123 Foord St. Stellarton, Nova Scotia (902) 752-8371 Ext. 4017 -Original Message- From: Kelly J. Lipp [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 11, 2001 11:51 AM To: [EMAIL PROTECTED] Subject: Re: Question on del volhist Don't over think it. Remember, information about volumes is in the database too and really, the only volume
Re: Library audit
If your actlog goes back that far, I would search the actlog for those volume numbers and see what the sequence of events was with them. With out IBM 3575 Library the operators soemntimes get in a hurry when processing out the DRM offsite tapes and issue a reply before they have emptied the I/O station and the next tape then will be left in library, although *SM thinks it'; out. Basically in actlog I see where prompt was to remove tape blah from slot blah instead of from the I/O slot and the operators don't look at message they just reply automatically. 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] 04/13/01 06:21PM >>> After returning today from a weeks worth of SS52B training I decided to check my library to see it's status. I find there are 11 volumes that show up with the following command: mtlib -l /dev/lmcp0 -qI, which are supposed to be in the vault. Of the 11 I know 4 are not physically in the vault but the other 7 are. If they are out of the library then why does this command show them as in? DRM shows all 11 in the vault. If I try to eject them TSM says they are not in the library. I tried to audit the library but I didn't see any synchronization between the library manager and TSM: (From the readme) If TSM detects inconsistencies, the server updates its inventory to reflect the current state of the library. TSM deletes missing volumes and updates moved volume locations. TSM does not automatically add new volumes; you must check in new volumes with the CHECKIN LIBVOLUME command. Maybe this doesn't talk to the anything except itself, I don't understand that if the tape is truly out of the library why does the mtlib command show it's in? And if the tape is really in the library why doesn't TSM update the DRM status? Any ideas from anyone? Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (888) 997-9614 "MMS " made the following annotations on 04/16/01 09:45:07 -- 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. ==
file name too long when?
APAR IC27346 discusses this problem. This was fixed in an earlier 3.7.2.x patch, and the permanent fix went in to the 4.1.1.0 (and later) versions. I recommend that customers use either 3.7.2.19 or 4.1.2.12. I have included the text of the APAR below. Note that in the "RECOMMENDATION" section of the text, it says to not apply new maintenance until the fixing PTF is available. "Fixing PTF" was a reference to 4.1.1.0, which was not available at the time this APAR text was written. This fix was *not* available in 4.1.0.x, so the point of this caveat was to tell users who install 3.7.2.19 not to go to 4.1.0.x, but to wait for 4.1.1.0 (or higher). BEGIN APAR TEXT ABSTRACT: WINDOWS CLIENT CAN NOT BACK UP FILES WHOSE NAMES EXCEED THE WINDOWS OS LIMIT OF 260 CHARACTERS. ERROR DESCRIPTION: Windows permits a maximum path length of 260 characters (259 usable characters plus 1 for the string terminator). However, under certain conditions, the operating system permits files of greater lengths to be created. As a result, when the TSM Windows client attempts to access files whose path lengths exceed the OS limit, the I/O operation fails with Win32 return code 206 (ERROR_FILENAME_EXCED_RANGE). PROBLEM SUMMARY: * USERS AFFECTED: Windows client on NT and 2000. * * PROBLEM DESCRIPTION: The Windows client is unable to process * *files and directories whose names exceed the operating* *system-defined length of 259 characters. * * RECOMMENDATION: Apply fixing PTF when available. Users of* *fixtest 3.7.2.16 must not apply new maintenance until * *the fixing PTF for this APAR is available.* PROBLEM CONCLUSION: The Windows operating system defines a maximum path length of 260 characters (259 usable characters plus 1 character to terminate the path). However, under certain circumstances, it is possible to create files whose path lengths violate this limit. When this happens, many programs, including Windows Explorer, Notepad.exe, TSM, etc., can not access these files. The Microsoft Win32 API file I/O functions provide a circumvention to this problem that has been incorporated into the TSM client. The client will now be able to support (i.e. backup, restore, archive, retrieve) files that exceed the 259 character limit provided that the USEUNICODEFILENAMES NO client option is in effect. If USEUNICODEFILENAMES is set to YES, then the client will not be able to support these files. The following information should be noted with regard to this fix: - USEUNICODEFILENAMES NO must be in effect (as mentioned above). If USEUNICODEFILENAMES YES is in effect, then these longer file names are unsupported. Users should always use USEUNICODEFILENAMES NO unless they have Mac volumes. If users need to support both Mac volumes AND these longer file names, then they will need to make provisions to run backups for the Mac volumes separately from the non-Mac files, backing up the Mac volumes with USEUNICODEFILENAMES YES, and the non-Mac files with USEUNICODEFILENAMES NO. The default value for USEUNICODEFILENAMES is YES when LANGUAGE AMENG is in effect. For other LANGUAGE settings, the default for USEUNICODEFILENAMES is NO. Thus when LANGUAGE AMENG is in effect, users must explicitly code USEUNICODEFILENAMES NO in their client options file. - The maximum supported length of the file name itself (not including the directory in which it resides), is 255 characters. - The maximum supported length of the directory portion of the path in which the file resides (not including the file itself) is 1,024 characters. - The maximum supported length of any component within a directory path can not exceed 255 characters. "Component" refers to a part of a directory structure as delimited by the backslash character. To illustrate: Given a path of the form: x:/comp1/comp2/comp3/filename Each component "compx" can not exceed 255 characters. Likewise, "filename" can not exceed 255 characters in length. In addtion, "x:/comp1/comp2/comp3" can not exceed 1,024 characters. Paths whose components exceed any of these limits are not supported. Note: forward slashes are substituted for backslashes in the above example because backslashes are not displayable in this APAR text. = END APAR TEXT = 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." From: Glass, Peter <[EMAIL PROTECTED]> One of our NT clients is getting a large number of 'ANE4018E ...: file name too long'
Re: Client restore requires multiple tapes from OVL location
Try something like... tsm: TSMSRV09>show volumeus prddb20 SHOW VOLUMEUSAGE started. Volume CAA443 in use by node PRDDB20. Volume CAA524 in use by node PRDDB20. Volume CAA657 in use by node PRDDB20. Volume CAA694 in use by node PRDDB20. Volume CAA742 in use by node PRDDB20. Volume CAA941 in use by node PRDDB20. Volume CAA987 in use by node PRDDB20. Volume CAB066 in use by node PRDDB20. Volume CAB120 in use by node PRDDB20. Volume CAB163 in use by node PRDDB20. Volume CAB225 in use by node PRDDB20. Volume CAB264 in use by node PRDDB20. Volume CAB290 in use by node PRDDB20. Volume CAB319 in use by node PRDDB20. Volume CAB341 in use by node PRDDB20. SHOW VOLUMEUSAGE completed. tsm: TSMSRV09> -Original Message- From: Anton Gubarkov [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 7:37 AM To: [EMAIL PROTECTED] Subject: Client restore requires multiple tapes from OVL location Dear colleges, I need to restore a server and I suppose it requires many media mounts. (I cannot afford collocation because I have only 13 slot library). How can I estimate what volumes are needed for this restore to check them in from overflow location before the restore starts and asks me for them one by one (like restore volume preview=yes for primary storage pool restoration from DR media)? I have TSM 4.1 for WinNT and WinNT BA client 4.1 Regards, Anton Gubarkov. Tel. +7 095 258 7626 Fax +7 095 258 7650
Re: AIX Gurus.. .Help Needed..
How about an oslevel -q ? -- Shawn Raymond Sr. Technical Consultant Synergy, Inc. 518-782-3457 Shekhar DhotreTo: [EMAIL PROTECTED] Subject: Re: AIX Gurus.. .Help Needed.. Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] EDU> 04/12/01 02:52 PM Please respond to "ADSM: Dist Stor Manager" # oslevel -l 4.3.3.0 # RETURNS NOTHING .. Shawn Raymond <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 04/12/2001 02:39:44 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: AIX Gurus.. .Help Needed.. Run oslevel -l 4.3.3.0 to list the filesets that are not up to date. You may have to do an update_all on all 4 of the AIX 4.3.3 CD's then run the ML8 update_all again. -- Shawn Raymond Sr. Technical Consultant Synergy, Inc. 518-782-3457 Shekhar DhotreTo: [EMAIL PROTECTED] Subject: Re: AIX Gurus.. .Help Needed.. Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] EDU> 04/10/01 06:04 PM Please respond to "ADSM: Dist Stor Manager" I installed ML08 on AIX 4.3.3 .0 today and issued command # oslevel 4.3.2.0 # instfix -ik 4330-08_AIX_ML All filesets for 4330-08_AIX_ML were found. # instfix -ciqk 4330-08_AIX_ML | grep ":-:" is this ok ---4.3.2.0 ? Shekhar Dhotre UniX /Tivoli Admin . Bayer Corp. 508-520-7821 . Shawn Raymond <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 04/10/2001 08:46:03 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: AIX Gurus.. .Help Needed.. Update your perfagent.tools to 2.2.33.50. svmon was broken in the previous few releases. -- Shawn Raymond Sr. Technical Consultant Synergy, Inc. 518-782-3457 Shekhar DhotreTo: [EMAIL PROTECTED] Subject: Re: AIX Gurus.. .Help Needed.. Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] EDU> 04/09/01 04:53 PM Please respond to "ADSM: Dist Stor Manager" I am trying to execute svmon but , getting following error ..any idea ? medrs2:ps -aef | grep dsmserv root 42134 1 0 Apr 02 - 2474:14 dsmserv root 48518 47810 1 16:36:56 pts/10 0:00 grep dsmserv medrs2:sh /usr/bin/svmon -P 42134 sh: /usr/bin/svmon: 0403-006 Execute permission denied. medrs2:id uid=0(root) gid=0(system) groups=2(bin),3(sys),7(security),8(cron),10(audit) medrs2: medrs2:svmon open: No such file or directory medrs2:/usr/bin/svmon open: No such file or directory medrs2:cd /usr/bin medrs2:./svmon open: No such file or directory medrs2:sh svmon sh: svmon: 0403-006 Execute permission denied. medrs2:echo $PATH /usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sb
Re: Database Size
I have 9 production AIX TSM servers, here are my numbers... as you see they vary greatly, so my favorite answer applies here "It depends" (that is, I don't think anything can be called "normal") hope this helps later, Dwight Available Assigned Maximum MaximumPage Total Used Pct Max. Space Capacity Extension ReductionSizeUsable Pages Util Pct (MB) (MB) (MB) (MB) (bytes) Pages Util - - - --- - - - - 11,148 10,476 67292 4,096 2,681,856 1,637,780 61.1 61.1 8,3725,568 2,80472 4,096 1,425,408 876,051 61.5 61.5 4,1323,620 512 564 4,096 926,72029,356 3.2 3.2 8,3727,680 692 808 4,096 1,966,080 894,399 45.5 45.9 8,3724,612 3,760 2,028 4,096 1,180,672 347,311 29.4 29.4 8,3724,100 4,272 364 4,096 1,049,600 742,776 70.8 71.5 25,116 19,000 6,116 724 4,096 4,864,000 3,278,326 67.4 67.5 8,3723,620 4,752 156 4,096 926,720 881,890 95.2 95.2 24,516 17,592 6,924 0 4,096 4,503,552 1,519,259 33.7 33.8 -Original Message- From: Marco Supino [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 6:55 AM To: [EMAIL PROTECTED] Subject: Database Size Hello. I would like to know from some of you what is the Database size, and how many pages does it contain ? i want to see if my Database is not normal by size. Thanks. Marco.
Re: Expanding ADSM DB Using Raw Logical Volumes. help please
OOOPPPSss with raw logical volumes you can't run dsmfmt against them... you just do a define dbvol & define dbcopy with the /dev/rblah I've used raw volumes in the past for db & log vols, that works... now though, I tend to go ahead and use JFS files for db & log and raws for storage volumes but I went through a wave of improper handling of raw volumes in AIX 4.2, you should still be OK in aix 4.1 DWight -Original Message- From: Palmadesso Jack [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 7:39 AM To: [EMAIL PROTECTED] Subject: Expanding ADSM DB Using Raw Logical Volumes. help please One of our older ADSM servers DB hit 98% over the weekend. I am putting together a proceedure to grow its DB. As far as I can tell these are the steps I need to take. First here is the hardware and software levels. RS6k F30 ADSM 3.1.2 level 40 (has been running smooth as silk for years)upgrade to 4 in progress AIX 4.1.5 (I know its old) Breece Hill Q47 w/3 DLT 4000 (attached as standard SCSI Library) All Storage pools and DB vols are on Raw Logical Volumes. We use ADSM mirroring for DBs These are the steps I've come up with. 1. Move Data from chosen storage pool vols 2. Vary off the volumes I have already chosen from ADSM 3. Delete the vols from ADSM 4. In Smitty rename the volumes to reflect new status of DB vols instead of stg vols 5. Peform DSMFMT for DB on newly renamed vols. 6. Add vols (1 primary and 1 mirror) to ADSM DB 7. Extend DB Anybody see anything wrong with these steps? Jack Palmadesso Siemens Westinghouse Power Corp.
Re: Question on del volhist
Wanda, The issue that I THINK I have, is that I am using scratch tapes for all pools (copypools as well). Are your copypools private or scratch ?What I think happens, is that when a DR tape becomes empty (through expiration/reclamation), and changes from VAULT to VAULTRETRIEVE, that since it is a scratch tape, with no data on it, and not in my library (q libv), that it will simply cease to exist. If you are using category private tapes, you will not see this problem. If your tapes are scratch and still contain data, (status vault) you will not see this problem. Would an empty scratch tape only be tracked by volhistory entries ? (Where else would you find an entry for an empty scratch ?) P.S. Sorry for inadvertently replying to Kelly instead of the listserv. Thanks, Glenn MacIntosh Manager of Technical Services Sobeys Inc. 123 Foord St. Stellarton, Nova Scotia (902) 752-8371 Ext. 4017 -Original Message- From: Prather, Wanda [mailto:[EMAIL PROTECTED]] Sent: Friday, April 13, 2001 1:54 PM To: [EMAIL PROTECTED] Subject: Re: Question on del volhist OK, I ran a DELETE VOLHIST for all record types all the way back to January. I checked on the oldest volumes in my OFFSITE copypool, which are marked VAULT by DRM. They no longer have ANY entry in the volume history file; running select * from volhistory where volume_name='xx' gets no hits at all, but Q DRMEDIA * still shows that volume xx is marked VAULT. So I still believe that removing STGNEW/STGDELETE via DELETE VOLHIST has NO effect on storage pool volumes. But it will make to "disappear" volumes that are tracked ONLY via VOLUMEHISTORY, including DBBACKUP, DBSNAPSHORT, and EXPORT entries. Wanda Prather The Johns Hopkins Applied Physics Lab 443-778-8769 [EMAIL PROTECTED] "Intelligence has much less practical application than you'd think" - Scott Adams/Dilbert -Original Message- From: Kelly J. Lipp [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 12, 2001 12:12 PM To: [EMAIL PROTECTED] Subject: Re: Question on del volhist This was not my observation, but rather that of Glenn MacIntosh. I don't know if this is what happens or not. Glenn had responded to me and not to the list so I thought I'd post his reply to garner further input on the assertion. I wouldn't think deleting volhist records would cause this to happen in DRM. 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 Prather, Wanda Sent: Thursday, April 12, 2001 9:57 AM To: [EMAIL PROTECTED] Subject: Re: Question on del volhist Yikes, I didn't know that! Thanks for pointing it out. If you think you have tapes disappearing and don't want to do a manual audit, you can write an audit program/script. 1)Pull a list of tapes that are physically in the library: q libv 2)Pull a list of tapes that are in DRM VAULT status: q drmedia * wherest=vault 3)Create a list of tapes that SHOULD be accounted for (either generate a tape range, if it's contiguous, or build a static list in a file). Have your script compare the volsers in list (3) to list (1) + (2). ANything that is on list 3, but isn't in either list (1) or (2), is MIA. It's much easier to go to the vault looking for a specific VOLSER, than to audit everything in there... I also run a script that compares (1) to (2) at least once a month, to make sure everything that was supposed to go to the vault actually did... -Original Message- From: Kelly J. Lipp [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 12, 2001 10:52 AM To: [EMAIL PROTECTED] Subject: FW: Question on del volhist Okay .. since we're talking del volhist ... Can someone clarify this point with the del volhist ? If I am using scratch tapes (no private tapes), and I am using the DR Module. It seems to me that if I have a DR tape, offsite, and empty (in retrieve state) and I delete the volhist entry, the tape seems to disappear totally from view. (i.e. a "q drm" command will no longer show it). I believe that scratch tapes will disappear if they are empty ... not a big deal if you know which ones they are, but if they disappear from view before you bring them back on site, how would you find them (without performing a manual offsite audit) ? (It is my understanding that tapes change from pending to empty "reuse" number of days (exactly) after they have gone pending. So you could have tapes changing from pennding to empty any time "3" days from the time the expiration freed it up.) How is anyone handling this (or are you doing what I'm doing and not deleting the volhist) ? Should I run my expi
Client restore requires multiple tapes from OVL location
Dear colleges, I need to restore a server and I suppose it requires many media mounts. (I cannot afford collocation because I have only 13 slot library). How can I estimate what volumes are needed for this restore to check them in from overflow location before the restore starts and asks me for them one by one (like restore volume preview=yes for primary storage pool restoration from DR media)? I have TSM 4.1 for WinNT and WinNT BA client 4.1 Regards, Anton Gubarkov. Tel. +7 095 258 7626 Fax +7 095 258 7650
Expanding ADSM DB Using Raw Logical Volumes. help please
One of our older ADSM servers DB hit 98% over the weekend. I am putting together a proceedure to grow its DB. As far as I can tell these are the steps I need to take. First here is the hardware and software levels. RS6k F30 ADSM 3.1.2 level 40 (has been running smooth as silk for years)upgrade to 4 in progress AIX 4.1.5 (I know its old) Breece Hill Q47 w/3 DLT 4000 (attached as standard SCSI Library) All Storage pools and DB vols are on Raw Logical Volumes. We use ADSM mirroring for DBs These are the steps I've come up with. 1. Move Data from chosen storage pool vols 2. Vary off the volumes I have already chosen from ADSM 3. Delete the vols from ADSM 4. In Smitty rename the volumes to reflect new status of DB vols instead of stg vols 5. Peform DSMFMT for DB on newly renamed vols. 6. Add vols (1 primary and 1 mirror) to ADSM DB 7. Extend DB Anybody see anything wrong with these steps? Jack Palmadesso Siemens Westinghouse Power Corp.
Re: ADSM database backup to a file.
Uhm I might just have to put me together a sun box & try this... Dwight -Original Message- From: France, Don G (Pace) [mailto:[EMAIL PROTECTED]] Sent: Friday, April 13, 2001 4:50 PM To: [EMAIL PROTECTED] Subject: Re: ADSM database backup to a file. There are specific-path references, and file-system-dependent things in the TSM data base - which makes each server you install PLATFORM-SPECIFIC. So... the short answer is "no". -Original Message- From: Rainer Wolf [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 11, 2001 6:04 AM To: [EMAIL PROTECTED] Subject:Re: ADSM database backup to a file. Hi , Can I also create this 'flatfile' on a AIX system ( server-a ) and restore the server on a Solaris system ( server-b ) ? I would like to use this solaris-adsm/tsm- server only for a quick restore of data previously backed up on server-a which uses copy-Storagepools via server-server on a third system- (server-c) and I don't want to use this solaris system for backup, because it only has disks and no library ... someone using such a configuration -or is this quite anomalous ? ( Szenario : server-a and Clients from this server-a (with 'client-data-copys-send-to-server-c' ) are completely destroyed - then trying to restore latest active backups for the Clients as fast as possible on server-b using just the copy from server-c ) Thanks in advance for any hints ! Rainer "Cook, Dwight E" wrote: > > Sure, to move an adsm environment across town where I was a few states away > and didn't want to fly in for a half day... > define a device class of "FILE" and use it to backup the DB. > I did a full, then FTP'ed it over to a new machine that was to become the > server... as soon as I got the full FTP'ed over I did a restore with > commit=no, then I locked out clients, did an incremental, FTP'ed that one > over, did a restore with commit=yes and started up TSM. (while I was doing > that the DNS folks were doing there thing, then the clients just had to > bounce their schedulers...) > >>-DEFine DEVclass--device_class_nameDEVType--=--FILE---> > > .-MOUNTLimit--=--1. > >-+-+---> > '-MOUNTLimit--=--mountlimitvalue--' > > .-MAXCAPacity--=--4M. > >-+---+-> > '-MAXCAPacity--=--size--' > > .-DIRectory--=--current_directory_name--. > >-+---+>< > '-DIRectory--=--directory_name--' > > so something like > def devc FLATFILE devt=file maxcap=4096M dir=/usr/adsm/flatfile > then just use it like > backup db t=f s=y dev=flatfile > and it will create a file in /usr/adsm/flatfile > to automatically get rid of the file in that directory, do like you would > normally... del volhist t=dbb tod=-x and any db backup files in > /usr/adsm/flatfile older than "x" will be deleted... > > Dwight > > -Original Message- > From: Zosimo Noriega (ADNOC IS&T) [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 10, 2001 1:10 AM > To: [EMAIL PROTECTED] > Subject: ADSM database backup to a file. > > Hi everyone, > Can i backup my adsm db into a file because i usually backed up into tapes > using the devclass. > if possible, please provide the commands or steps how to do it and how to > restore it. > > thanks, > zosi -- Mit freundlichen Grüßen / best regards Rainer Wolf __ Rainer Wolf [EMAIL PROTECTED] Tel: 0731-50-22482 Fax: 0731-50-22471 University of Ulmhttp://www.uni-ulm.de/urz University Computing Center Albert-Einstein-Allee 11 AG Basissysteme 89069 Ulm
Re: Can not checkout the tape through scheduled job
some tasks are just not allowed to run through the scheduler... If you must, you could set up a ksh script that would perform a dsmadmc -id=blah -pass=blah CHECKOUT LIBVOLUME LIB0 TSK071 CHECKLABEL=NO FORCE=NO REMOVE=NO and run it from cron on the tsm server... -Original Message- From: Ganu Sachin, IBM [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 12, 2001 11:26 PM To: [EMAIL PROTECTED] Subject: Can not checkout the tape through scheduled job Hi, A query about TSM Administrative scheduling. We have TSM ,configured on AIX 4.3.3. I want to schedule a task which will checkout the volume. The volume is used for tsm database backup. When I define a new administrative task for checkout, I am getting following error. The command is used in the scheduling task is " CHECKOUT LIBVOLUME LIB0 TSK071 CHECKLABEL=NO FORCE=NO REMOVE=NO". I do not want to set FORCE option to YES. But if, I run the same command from server command prompt, command executed successfully. ERROR :- "ANR2755E DEFINE SCHEDULE or UPDATE SCHEDULE parameter CMD='CHECKOUT LIBVOLUME LIB0 TSK071 CHECKLABEL=NO FORCE=NO REMOVE=NO' - not eligible for scheduling. " Pls tell me whether it is possible to schedule the administrative task for checking out the volume, if yes pls explain. Thanks in advance Sachin Ganu
Database Size
Hello. I would like to know from some of you what is the Database size, and how many pages does it contain ? i want to see if my Database is not normal by size. Thanks. Marco. begin:vcard n:Supino;Marco tel;cell:972-54-983653 tel;fax:972-9-9509118 tel;work:972-9-9708721 x-mozilla-html:FALSE url:www.innoveda.com org:Innoveda Ltd.;System adr:;;8 Hasadnaot st.;Herzlia;;46728;Israel version:2.1 email;internet:[EMAIL PROTECTED] title:Systems Administrator x-mozilla-cpt:;-31296 fn:Marco Supino end:vcard
Re: Library audit
try running an inventory on the library itself... if the tape(s) are actually outside the atl, this will update the info you see with the "mtlib" command. ALSO you need to note the status with which the tapes show up in the output of the "mtlib" command... if they show up with a FFFA that is a manual eject which would say they really aren't in there :-/ To physically purge any library records you may use the mtlib -l/dev/lmcp# -C -VXXX### -s -tFFFB where # is your library number, XXX### is your tape volser, and is the current status of the tape shown in the mtlib query of the volume... Yes, if the tape actually exists in the atl (say in FF00 insert mode) and your tsm system thinks it is not in the library inventory (of tsm) but is actually a private tape, an "audit libr blah" will NOT add the tape to your tsm library inventory, you will have to do that yourself with a "checkin libvol ..." hope this helps... later, Dwight -Original Message- From: Gill, Geoffrey L. [mailto:[EMAIL PROTECTED]] Sent: Friday, April 13, 2001 5:21 PM To: [EMAIL PROTECTED] Subject: Library audit After returning today from a weeks worth of SS52B training I decided to check my library to see it's status. I find there are 11 volumes that show up with the following command: mtlib -l /dev/lmcp0 -qI, which are supposed to be in the vault. Of the 11 I know 4 are not physically in the vault but the other 7 are. If they are out of the library then why does this command show them as in? DRM shows all 11 in the vault. If I try to eject them TSM says they are not in the library. I tried to audit the library but I didn't see any synchronization between the library manager and TSM: (From the readme) If TSM detects inconsistencies, the server updates its inventory to reflect the current state of the library. TSM deletes missing volumes and updates moved volume locations. TSM does not automatically add new volumes; you must check in new volumes with the CHECKIN LIBVOLUME command. Maybe this doesn't talk to the anything except itself, I don't understand that if the tape is truly out of the library why does the mtlib command show it's in? And if the tape is really in the library why doesn't TSM update the DRM status? Any ideas from anyone? Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (888) 997-9614
Re: Exclude List for NT 4.0
be carefull Don, the show inclexcl lists top-down ! R. Lambelet, Nestlé Vevey > -Original Message- > From: France, Don G (Pace) [SMTP:[EMAIL PROTECTED]] > Sent: vendredi, 13. avril 2001 23:38 > To: [EMAIL PROTECTED] > Subject: Re: Exclude List for NT 4.0 > > Check your clientopts... or, better yet, do a "show inclexcl" from an > interactive session, as it resolves both dsm.opt and clientopts. > Cloptsets > are added to the bottom of the list, so I would ensure no "include" is in > the clientopts, else could render your dsm.opt excludes ineffective. > > Don France > PACE - http://www.pacepros.com > > > -Original Message- > From: Bruce Kamp [mailto:[EMAIL PROTECTED]] > Sent: Thursday, April 12, 2001 7:16 AM > To: [EMAIL PROTECTED] > Subject:Re: Exclude List for NT 4.0 > > When I execute the command it shows all my client options from the server > & > then the excludes I have in the DSM.OPT file. The last line of my client > opt is INCLUDE *:\adsm.sys\...\* then from DSM.OPT Exclude > *:\WINNT\system32\asat0*.tmp. Could this order have anything to do with > it? > > > -Original Message- > From: Chibois, Herve [mailto:[EMAIL PROTECTED]] > Sent: Thursday, April 12, 2001 4:44 AM > To: [EMAIL PROTECTED] > Subject: Re: Exclude List for NT 4.0 > > > Hi Bruce, > > try dsmc > q inclexcl > > to see want TSM has understood of your inclexcl list. > > Remember to stop/start your scheduler when modifying dsm.opt > > rv > > > > -Message d'origine- > > De : Bruce Kamp [mailto:[EMAIL PROTECTED]] > > Envoyé : mercredi 11 avril 2001 14:52 > > À : [EMAIL PROTECTED] > > Objet : Exclude List for NT 4.0 > > > > > > Just finished upgrading to AIX 4.1.2 Server & on my NT > > servers I am having a > > problem with excludes that used to work on 3.1. I am using > > client version > > 4.1.2 These are the 2 files on one of my servers but this is > > happening on a > > lot them. I am also using a client option set. > > Here are the options I have defined: > > > > Exclude *:\apps\mrswin\DB\Mrs.log > > Here are the errors: > > 04/10/01 13:18:40 ANE4987E (Session: 892, Node: CANCERDATA_NT40) Error > > processing '\\cancerdata_nt40\d$\apps\mrswin\DB \MRS.LOG': > > the object is in > > use by another process 04/10/01 13:19:10 > > ANE4987E (Session: 892, Node: CANCERDATA_NT40) Error processing > > '\\cancerdata_nt40\c$\WINNT\system32 \asat0004.tmp': the > > object is in use by > > another process > > I set these up manually & also using the setup wizard through > > the backup > > client. Tried using with & with out quotes. Tried using *:\winnt & > > D:\winnt. All producing the same results. > > > > -- > > Bruce Kamp > > Network Analyst II > > Memorial Healthcare System > > P: (954)987-2020 x4542 > > F: (954)985-1404 > > E: [EMAIL PROTECTED] > > > >
How do I backup symbolic file ?
I want to backup symbolic file on UNIX . How do I do to make it work ? for example: /home/explink > /data/ /data is a directory I want to backup /data/*.* when I execute the command: dsmc inc -subdir=yes /home/ Otherwiles , if I create new symbolic in /homeI,for example otherlink ---> /data2/ , I want to backup /data2/*.* when I execute the command: dsmc inc -subdir=yes /home/ How do I do to make it work ? Michael hsu
