Incr backup of old version
I am trying to figure out exactly what happened on one of our servers but Im not sure how TSM is supposed to behave in this instance. Any insight is greatly appreciated... Scenario: TSM 5.1. Incremental backup. Versions Data Exists = 10. Versions Data Deleted = 2. Retain Extra Versions = 45. Retain Only Version = 90. A file is backed up on 23 December 2003. The file is not changed until 10 October 2004. On 5 November 2004 the file is copied over with a saved copy of the file from 23 December 2003 retaining the 23 Dec timestamp. Result: 2 days later (after 2 nightly incrementals) a query of the TSM database shows only the version from 23 Dec... there is no active or inactive record of the file changed on 10 Oct 04. Question: Why doesnt the file version from 10 October 2004 show up in the TSM database? If the file is somehow expired in TSM, why doesnt the output in the schedlog show an expiration of the file from 10 Oct? Thanks in advance Steve
Incr backup of old version
I am trying to figure out exactly what happened on one of our servers but Im not sure how TSM is supposed to behave in this instance. Any insight is greatly appreciated... Scenario: TSM 5.1. Incremental backup. Versions Data Exists = 10. Versions Data Deleted = 2. Retain Extra Versions = 45. Retain Only Version = 90. A file is backed up on 23 December 2003. The file is not changed until 10 October 2004. On 5 November 2004 the file is copied over with a saved copy of the file from 23 December 2003 retaining the 23 Dec timestamp. Result: 2 days later (after 2 nightly incrementals) a query of the TSM database shows only the version from 23 Dec... there is no active or inactive record of the file changed on 10 Oct 04. Question: Why doesnt the file version from 10 October 2004 show up in the TSM database? If the file is somehow expired in TSM, why doesnt the output in the schedlog show an expiration of the file from 10 Oct? Thanks in advance Steve
Empty tape will not reclaim
Strange problem. AIX 4.3.3, TSM 5.1.5.4. Im trying to run reclamation on our copy storage pool. There is only one tape left, and reclamation continually starts and ends successfully for it without moving any data and no time passing: 11/18/03 06:53:26 ANR0984I Process 2215 for SPACE RECLAMATION started in the BACKGROUND at 06:53:26. 11/18/03 06:53:26 ANR1040I Space reclamation started for volume J00840, storage pool COPY_POOL_01 (process number 2215). 11/18/03 06:53:26 ANR0985I Process 2215 for SPACE RECLAMATION running in the BACKGROUND completed with completion state SUCCESS at 06:53:26. The volume in question reports as being "100% reclaimable", "0% utilized" and status of "full" from a q vol: >q vol j00840 f=d Volume Name: J00840 Storage Pool Name: COPY_POOL_01 Device Class Name: 3590CLASS Estimated Capacity (MB): 87,784.5 Pct Util: 0.0 Volume Status: Full Access: Offsite Pct. Reclaimable Space: 100.0 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 5 Write Pass Number: 1 Approx. Date Last Written: 11/06/03 16:02:32 Approx. Date Last Read: 11/11/03 16:04:00 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: VAULT Last Update Date/Time: 11/11/03 16:09:25 >From the database output I get a report that it is "99.9% reclaimable". >select * from volumes where volume_name='J00840' VOLUME_NAME: J00840 STGPOOL_NAME: COPY_POOL_01 DEVCLASS_NAME: 3590CLASS EST_CAPACITY_MB: 87784.4 PCT_UTILIZED: 0.0 STATUS: FULL ACCESS: OFFSITE PCT_RECLAIM: 99.9 SCRATCH: Yes ERROR_STATE: No NUM_SIDES: 1 TIMES_MOUNTED: 5 WRITE_PASS: 1 LAST_WRITE_DATE: 2003-11-06 16:02:32.00 LAST_READ_DATE: 2003-11-11 16:04:00.00 PENDING_DATE: WRITE_ERRORS: 0 READ_ERRORS: 0 LOCATION: VAULT CHG_TIME: 2003-11-11 16:09:25.00 >move data j00840 stgp=copy_pool_01 ANR2232W This command will move all of the data stored on volume J00840 to other volumes within the same storage pool; the data will be inaccessible to users until the operation completes. Do you wish to proceed? (Yes (Y)/No (N)) y ANR2209W Volume J00840 contains no data. ANS8001I Return code 11. >q content j00840 ANR2034E QUERY CONTENT: No match found using this criteria. ANS8001I Return code 11. Any idea what is going on? Thanks in advance, Steve
Informix TDP restore to another server
We're running Informix TDP 4.1, TSM client 5.1 on AIX 4.3.3 trying to restore to another client running same O/S and TDP/TSM version. Our TSM server version is at 5.1 on AIX 4.3.3. The cross-server restore is failing because it is trying to log in as the "INFORMIX" node... which doesnt exist. I have set the virtualnodename in the api dsm.opt file and also changed the nodename in the api dsm.sys file. We can do normal TDP backup and restores to/from the same server and it uses the right name and works fine. Any idea why now its trying to use a different nodename (its the name of the user running the process) and how to overcome it? Thanks Steve
Does Informix TDP backup go to backup or archive copygroup?
Does Informix TDP backup go to backup or archive copygroup?
Re: Informix TDP AIX Configuration problems
That did it! Thanks a bunch! -Original Message- From: Gene Greenberg [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 03, 2003 3:43 PM To: [EMAIL PROTECTED] Subject: Re: Informix TDP AIX Configuration problems Just a thought, but make sure in /usr/lib you have a link for ibsad001.a >/usr/tivoli/tsm/client/api/bin/libXApi.a and ibsad001.o > /usr/tvioli/tsm/client/informix/bin/bsashr10.o. Hope this helps. Gene Greenberg Jr. "Conko, Steven" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Sent by: "ADSM: cc: Dist StorSubject: Informix TDP AIX Configuration problems Manager" <[EMAIL PROTECTED] .EDU> 09/03/03 02:09 PM Please respond to "ADSM: Dist Stor Manager" I cant seem to filter out the info I need from searching the archive... TSM server is AIX 4.3.3-10, TSM5.1.5 TSM client is AIX 4.3.3-09, TSM5.1.5 TDP Informix 4.1.3 Informix - (not sure what version, but I was told its compatible) Trying to get it set up correctly, the DBA tells me OnBar can connect to the XBSA libs but not contact the TSM server. I can connect using the tdpipaswd command. It would appear all environment variables are set as well as dsm.opt and dsm.sys in the api directory. The database has been restarted as well. Any ideas?
Re: TDP for Informix password initialization problem
Did you register a node in the TSM Server? Include that nodename in the stanza in the dsm.sys file as "nodenameNAME_OF_YOUR_NODE_HERE" -Original Message- From: Mario Behring [mailto:[EMAIL PROTECTED] Sent: Thursday, September 04, 2003 10:20 AM To: [EMAIL PROTECTED] Subject: Re: TDP for Informix password initialization problem Steven, There is no such directory like /usr/tivoli/tsm/client/ba/bin/ at the AIX server (hostname g40). The contents of both dsm files located at /usr/tivoli/tsm/client/api/bin are below: dsm.sys SErvername srv004 COMMmethod TCPip TCPPort 1500 TCPServeraddress 192.168.0.144 PasswordAccess generate dsm.opt SErvername srv004 I created the AIX node, called g40, using the Web Administrators interface, but I am not so sure that this is the right process when using TDP for Informix (other BAC nodes are already working fine). Could you give me a hand with this ? Thanks. Mario "Conko, Steven" <[EMAIL PROTECTED]> wrote: Make sure the /usr/tivoli/tsm/client/api/bin/dsm.opt file specifies the same servername as is in /usr/tivoli/tsm/client/api/bin/dsm.sys, and that the nodename you registered and is listed in that dsm.sys file is different than the BA client specified in /usr/tivoli/tsm/client/ba/bin/dsm.sys. -Original Message- From: Mario Behring [mailto:[EMAIL PROTECTED] Sent: Thursday, September 04, 2003 9:57 AM To: [EMAIL PROTECTED] Subject: TDP for Informix password initialization problem Hi list, I am trying to initialize the password for the TDP for Informix on a AIX 4.3.3 32 bits machine. The node is already registered at the TSM Server (or so it seems to be) and I get the following error when running the tdpipswd program: *** * TDP for Informix Backup * * Password file initialization program * *>> this must be run by the ROOT user if updating the value <<* *** Enter your current password: Enter your new password: Enter your new password again: *** Server signon failed: ANS1353E (RC53) Session rejected: Unknown or incorrect ID entered I just have to perform an online backup from an Infomix DB at this AIX server using TSM. Any help is appreciated. Thanks. Mario - Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software - Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software
Re: TDP for Informix password initialization problem
Make sure the /usr/tivoli/tsm/client/api/bin/dsm.opt file specifies the same servername as is in /usr/tivoli/tsm/client/api/bin/dsm.sys, and that the nodename you registered and is listed in that dsm.sys file is different than the BA client specified in /usr/tivoli/tsm/client/ba/bin/dsm.sys. -Original Message- From: Mario Behring [mailto:[EMAIL PROTECTED] Sent: Thursday, September 04, 2003 9:57 AM To: [EMAIL PROTECTED] Subject: TDP for Informix password initialization problem Hi list, I am trying to initialize the password for the TDP for Informix on a AIX 4.3.3 32 bits machine. The node is already registered at the TSM Server (or so it seems to be) and I get the following error when running the tdpipswd program: *** * TDP for Informix Backup * * Password file initialization program* *>> this must be run by the ROOT user if updating the value <<* *** Enter your current password: Enter your new password: Enter your new password again: *** Server signon failed: ANS1353E (RC53) Session rejected: Unknown or incorrect ID entered I just have to perform an online backup from an Infomix DB at this AIX server using TSM. Any help is appreciated. Thanks. Mario - Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software
Re: Informix TDP AIX Configuration problems
should ibsad001.o be linked to /usr/tivoli/tsm/client/bin/bsashr10.o? they currently have it linked to /home/informix/prod/lib/libbsa.o. -Original Message- From: Gene Greenberg [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 03, 2003 3:43 PM To: [EMAIL PROTECTED] Subject: Re: Informix TDP AIX Configuration problems Just a thought, but make sure in /usr/lib you have a link for ibsad001.a >/usr/tivoli/tsm/client/api/bin/libXApi.a and ibsad001.o > /usr/tvioli/tsm/client/informix/bin/bsashr10.o. Hope this helps. Gene Greenberg Jr. "Conko, Steven" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Sent by: "ADSM: cc: Dist StorSubject: Informix TDP AIX Configuration problems Manager" <[EMAIL PROTECTED] .EDU> 09/03/03 02:09 PM Please respond to "ADSM: Dist Stor Manager" I cant seem to filter out the info I need from searching the archive... TSM server is AIX 4.3.3-10, TSM5.1.5 TSM client is AIX 4.3.3-09, TSM5.1.5 TDP Informix 4.1.3 Informix - (not sure what version, but I was told its compatible) Trying to get it set up correctly, the DBA tells me OnBar can connect to the XBSA libs but not contact the TSM server. I can connect using the tdpipaswd command. It would appear all environment variables are set as well as dsm.opt and dsm.sys in the api directory. The database has been restarted as well. Any ideas?
Informix TDP AIX Configuration problems
I cant seem to filter out the info I need from searching the archive... TSM server is AIX 4.3.3-10, TSM5.1.5 TSM client is AIX 4.3.3-09, TSM5.1.5 TDP Informix 4.1.3 Informix - (not sure what version, but I was told its compatible) Trying to get it set up correctly, the DBA tells me OnBar can connect to the XBSA libs but not contact the TSM server. I can connect using the tdpipaswd command. It would appear all environment variables are set as well as dsm.opt and dsm.sys in the api directory. The database has been restarted as well. Any ideas?
Re: TDP Oracle config question
Does this mean the error is going to be produced every time we run the backup? Is this a known issue with TSM? Can we safely ignore it, then? -Original Message- From: Neil Rasmussen [mailto:[EMAIL PROTECTED] Sent: Thursday, July 17, 2003 10:10 AM To: [EMAIL PROTECTED] Subject: Re: TDP Oracle config question Steve, The reason that you are seeing this error is that Oracle/Rman first tries to delete the backuppiece that it is about to create on the TSM Server. In this way Oracle/Rman ensures that only one copy of the backuppiece exists on the Backup Media so Rman tries to delete the backuppiece in case it already exists. The Rman specifications state that only one copy of a backuppiece will exist at one time on Media Manager (DP for Oracle). Unfortunately, Oracle/Rman also specifies that the delete routine act as single and seperate operation, so when Oracle tries to delete a backuppiece that does not exist, that is an error and DP for Oracle returns that error. There is no way for DP for Oracle to determine if the deletion is a true delete of a backuppiece or if Oracle is checking for backuppiece existence prior to backup. Hope this helps clear things up. -- Date:Wed, 16 Jul 2003 13:13:39 -0600 From:"Conko, Steven" <[EMAIL PROTECTED]> Subject: Re: TDP Oracle config question Thanks for that bit of information... it definitely clears some things up. According to the docs, we should be using unique TDPO_FS names for each node we are backing up using TDP, correct? After doing the query and some further investigation into the BACKUPS table, it appears we are getting this message because of a missing "-" When I do a select in the BACKUPS table, the LL_NAME shows up as: c-3756527612-2003-0714-02 However, in the error we are getting, the name of the object is: c-3756527612-20030714-02 Any idea why this is?? Steve Regards, Neil Rasmussen Software Development TDP for Oracle
Re: TDP Oracle config question
So is this an expected error message every time we run the TDP? Does that mean it can be ignored? -Original Message- From: Neil Rasmussen [mailto:[EMAIL PROTECTED] Sent: Thursday, July 17, 2003 10:10 AM To: [EMAIL PROTECTED] Subject: Re: TDP Oracle config question Steve, The reason that you are seeing this error is that Oracle/Rman first tries to delete the backuppiece that it is about to create on the TSM Server. In this way Oracle/Rman ensures that only one copy of the backuppiece exists on the Backup Media so Rman tries to delete the backuppiece in case it already exists. The Rman specifications state that only one copy of a backuppiece will exist at one time on Media Manager (DP for Oracle). Unfortunately, Oracle/Rman also specifies that the delete routine act as single and seperate operation, so when Oracle tries to delete a backuppiece that does not exist, that is an error and DP for Oracle returns that error. There is no way for DP for Oracle to determine if the deletion is a true delete of a backuppiece or if Oracle is checking for backuppiece existence prior to backup. Hope this helps clear things up. -- Date:Wed, 16 Jul 2003 13:13:39 -0600 From:"Conko, Steven" <[EMAIL PROTECTED]> Subject: Re: TDP Oracle config question Thanks for that bit of information... it definitely clears some things up. According to the docs, we should be using unique TDPO_FS names for each node we are backing up using TDP, correct? After doing the query and some further investigation into the BACKUPS table, it appears we are getting this message because of a missing "-" When I do a select in the BACKUPS table, the LL_NAME shows up as: c-3756527612-2003-0714-02 However, in the error we are getting, the name of the object is: c-3756527612-20030714-02 Any idea why this is?? Steve Regards, Neil Rasmussen Software Development TDP for Oracle
Re: Multi session backup restore question
We have a similar issue too. Is collocation of filespaces the only way (besides carving your system up in to multiple nodes) to acheive multiple restore sessions? Will it occur autmatically from a singe dsmc restore or do you need to manually invoke multiple sessions? Steve -Original Message- From: David Longo [mailto:[EMAIL PROTECTED] Sent: Thursday, July 17, 2003 10:25 AM To: [EMAIL PROTECTED] Subject: Re: Multi session backup restore question In order to have multi session "simultaneous" restore from tape pool then you must have this data in a pool that has collocation by filespace. If you have a big enough disk pool such that if you did a restore before migration had moved the data, then a multi session restore would use the disk pool and be multi session. 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.5509 [EMAIL PROTECTED] >>> [EMAIL PROTECTED] 07/17/03 09:48AM >>> Hello all, I am trying to work in a multi session backup and be able to use a multi session restore. What I have found is that with the maxresourceutilization set to 8 that my 350GB 8 processor AIX client is using only 4 data sessions and 4 control sessions. The data all goes to the disk pool and then the migration will use only 1 tape drive for this data. I then assume a multi session restore is not going to work. 1) how can I get this backup to use more sessions for data transfer? 2) Am I correct in believing that the multi-session restore is out because of the actions of the migration process? MUST this go direct to tape to have multi session backup and RESTORE? Thanks in advance, Matt ## 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: TDP Oracle config question
So, we should just ignore the error? -Original Message- From: Neil Rasmussen [mailto:[EMAIL PROTECTED] Sent: Thursday, July 17, 2003 10:10 AM To: [EMAIL PROTECTED] Subject: Re: TDP Oracle config question Steve, The reason that you are seeing this error is that Oracle/Rman first tries to delete the backuppiece that it is about to create on the TSM Server. In this way Oracle/Rman ensures that only one copy of the backuppiece exists on the Backup Media so Rman tries to delete the backuppiece in case it already exists. The Rman specifications state that only one copy of a backuppiece will exist at one time on Media Manager (DP for Oracle). Unfortunately, Oracle/Rman also specifies that the delete routine act as single and seperate operation, so when Oracle tries to delete a backuppiece that does not exist, that is an error and DP for Oracle returns that error. There is no way for DP for Oracle to determine if the deletion is a true delete of a backuppiece or if Oracle is checking for backuppiece existence prior to backup. Hope this helps clear things up. -- Date:Wed, 16 Jul 2003 13:13:39 -0600 From:"Conko, Steven" <[EMAIL PROTECTED]> Subject: Re: TDP Oracle config question Thanks for that bit of information... it definitely clears some things up. According to the docs, we should be using unique TDPO_FS names for each node we are backing up using TDP, correct? After doing the query and some further investigation into the BACKUPS table, it appears we are getting this message because of a missing "-" When I do a select in the BACKUPS table, the LL_NAME shows up as: c-3756527612-2003-0714-02 However, in the error we are getting, the name of the object is: c-3756527612-20030714-02 Any idea why this is?? Steve Regards, Neil Rasmussen Software Development TDP for Oracle
Re: TDP Oracle config question
Thanks again. One more quick question... does the filespace name, such as /adsmorc need to be "included" in the include/exclude list as the docs state? I suppose if so it would be on the TDP client? -Original Message- From: David Longo [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 3:23 PM To: [EMAIL PROTECTED] Subject: Re: TDP Oracle config question No idea about the missing "-". I believe the long name is built by Oracle/RMAN and not TSM. So need to look there. I don't know how that is put together, need to get with your DBA or Oracle on that. (I just looked at mine and all my RMAN backups use "_" as separators and have different numbering format, but still a long name.) We have unique names for each node with TDPO_FS, it's not really required though, you could use /adsmorc for each one. I think a good naming standard for your environment is best. David Longo >>> [EMAIL PROTECTED] 07/16/03 03:13PM >>> Thanks for that bit of information... it definitely clears some things up. According to the docs, we should be using unique TDPO_FS names for each node we are backing up using TDP, correct? After doing the query and some further investigation into the BACKUPS table, it appears we are getting this message because of a missing "-" When I do a select in the BACKUPS table, the LL_NAME shows up as: c-3756527612-2003-0714-02 However, in the error we are getting, the name of the object is: c-3756527612-20030714-02 Any idea why this is?? Steve -Original Message- From: David Longo [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 2:23 PM To: [EMAIL PROTECTED] Subject: Re: TDP Oracle config question You should NOT create a /adsmorc filesystem or mount point. The docs are correct, this is just the filespace name used on the server for this node name. You could change it to something else if you want with the TDPO_FS env variable. The message you are getting tells you that that particular object name does not exist on the server. Do a "q filespace blah" for the node name you are using and you should see /adsmorc. Is this happening when the RMAN scripts try to delete an object? 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.5509 [EMAIL PROTECTED] >>> [EMAIL PROTECTED] 07/15/03 03:42PM >>> TSM Server: AIX 4.3.3, TSM 5.1.5.4 RMAN Server: AIX4.3.3, TDP 5.2 RMAN Client: AIX 4.3.3, TSM 5.1.5, TDP5.2 The installation guide seems to be a little fuzzy on this topic... At some point during the backup process we get this error in our tdpoerror.log file: 23:28:55 ANS4994S TDP Oracle AIX ANU0599 ANU2602E The object /adsmorc//c-3756527612-20030714-03 was not found on the TSM Server After doing some of my own research I realize its telling me that the /adsmorc file space does not exist. My question is where is is supposed to exist? Am I supposed to create an adsmorc file system or directory on the TSM server, on the TDP/RMAN server, or the client? Is anything ever going to get put there? Does it need to be its own mount point? Any help would be greatly appreciated. Thanks in advance Steve ## 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. ## ## 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
Re: TDP Oracle config question
Thanks for that bit of information... it definitely clears some things up. According to the docs, we should be using unique TDPO_FS names for each node we are backing up using TDP, correct? After doing the query and some further investigation into the BACKUPS table, it appears we are getting this message because of a missing "-" When I do a select in the BACKUPS table, the LL_NAME shows up as: c-3756527612-2003-0714-02 However, in the error we are getting, the name of the object is: c-3756527612-20030714-02 Any idea why this is?? Steve -Original Message- From: David Longo [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 2:23 PM To: [EMAIL PROTECTED] Subject: Re: TDP Oracle config question You should NOT create a /adsmorc filesystem or mount point. The docs are correct, this is just the filespace name used on the server for this node name. You could change it to something else if you want with the TDPO_FS env variable. The message you are getting tells you that that particular object name does not exist on the server. Do a "q filespace blah" for the node name you are using and you should see /adsmorc. Is this happening when the RMAN scripts try to delete an object? 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.5509 [EMAIL PROTECTED] >>> [EMAIL PROTECTED] 07/15/03 03:42PM >>> TSM Server: AIX 4.3.3, TSM 5.1.5.4 RMAN Server: AIX4.3.3, TDP 5.2 RMAN Client: AIX 4.3.3, TSM 5.1.5, TDP5.2 The installation guide seems to be a little fuzzy on this topic... At some point during the backup process we get this error in our tdpoerror.log file: 23:28:55 ANS4994S TDP Oracle AIX ANU0599 ANU2602E The object /adsmorc//c-3756527612-20030714-03 was not found on the TSM Server After doing some of my own research I realize its telling me that the /adsmorc file space does not exist. My question is where is is supposed to exist? Am I supposed to create an adsmorc file system or directory on the TSM server, on the TDP/RMAN server, or the client? Is anything ever going to get put there? Does it need to be its own mount point? Any help would be greatly appreciated. Thanks in advance Steve ## 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: TDP Oracle config question
Neil, Im still waiting to find out from the DBA running it if he thinks it is succeeding or failing. Right now we dont have TDPO_FS defined so it is defaulting to adsmorc. My question is: is this only a filespace created within TSM Server storage or does there need to be an actual directory/mount point on a server somewhere? The documents mention including this filespace in the include/exclude list which leads me to believe I need to create the directory somewhere. Is that so? Thanks Steve -Original Message- From: Neil Rasmussen [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 11:35 AM To: [EMAIL PROTECTED] Subject: Re: TDP Oracle config question Steve, Can you answer me this? Does your backup actually fail, or is this just something that shows up during a successful backup? The /adsmorc filespace is a TSM Server filespace and is the default for TDP Oracle and will get created during the backup, if it doesn't already exist. Unless of course, you are specifying something other than the default (the option is TDPO_FS). -- Date:Tue, 15 Jul 2003 13:42:36 -0600 From:"Conko, Steven" <[EMAIL PROTECTED]> Subject: TDP Oracle config question TSM Server: AIX 4.3.3, TSM 5.1.5.4 RMAN Server: AIX4.3.3, TDP 5.2 RMAN Client: AIX 4.3.3, TSM 5.1.5, TDP5.2 The installation guide seems to be a little fuzzy on this topic... At some point during the backup process we get this error in our tdpoerror.log file: 23:28:55 ANS4994S TDP Oracle AIX ANU0599 ANU2602E The object /adsmorc//c-3756527612-20030714-03 was not found on the TSM Server After doing some of my own research I realize its telling me that the /adsmorc file space does not exist. My question is where is is supposed to exist? Am I supposed to create an adsmorc file system or directory on the TSM server, on the TDP/RMAN server, or the client? Is anything ever going to get put there? Does it need to be its own mount point? Any help would be greatly appreciated. Thanks in advance Steve Regards, Neil Rasmussen Software Development TDP for Oracle
TDP Oracle config question
TSM Server: AIX 4.3.3, TSM 5.1.5.4 RMAN Server: AIX4.3.3, TDP 5.2 RMAN Client: AIX 4.3.3, TSM 5.1.5, TDP5.2 The installation guide seems to be a little fuzzy on this topic... At some point during the backup process we get this error in our tdpoerror.log file: 23:28:55 ANS4994S TDP Oracle AIX ANU0599 ANU2602E The object /adsmorc//c-3756527612-20030714-03 was not found on the TSM Server After doing some of my own research I realize its telling me that the /adsmorc file space does not exist. My question is where is is supposed to exist? Am I supposed to create an adsmorc file system or directory on the TSM server, on the TDP/RMAN server, or the client? Is anything ever going to get put there? Does it need to be its own mount point? Any help would be greatly appreciated. Thanks in advance Steve
Compressed restore
AIX4.3.3,TSM5.1.5.4 - Server AIX4.3.3,TSM5.1.5 - Client When restoring compressed files, is it normal for the "reported" size to be different from the actual restored size as it is when backing up? Im restoring a large database and so far the the "live" report from the dsmc session reports 1.4GB restored when if you look at the directory, over 6GB have shown up. Im assuming this is normal... is it? Steve
Recovery Plan Retention
Is there any reason you would want your Recovery Plan retention set longer than your DBbackup retention?
Re: Restore slows to a crawl
Thanks. I'll try to provide as much information as I can. If I dont provide enough please let me know. Server: AIX 4.3.3, TSM 5.1.5 Client: AIX 5.1, TSM 5.1.5.4 Virtualnodename client: AIX 5.1 TSM 5.1.5.4 collocation is turned off. compression is off. maxnummp for both nodes is set to 6. we are using a 3494 tape library with 12 3590 tape drives. node disk storage is on an IBM ESS. the backup/restore LAN is gigabit. system 'A' was backed up to tape from 1 mount point. i am attempting to restore to system 'B' over 4 mount points. all filesystems are of type jfs2. nothing else is running on the TSM Server. Settings on TSM Server: TCPWindowsize 1048576 TCPBufsize32768 CommTimeOut 999 IdleTimeOut 60 Both clients have: Keep Mount Point = Yes largecommbuffers yes resourceutil 10 compressionyes tcpnodelay yes tcpbuffsize32 tcpwindowsize 64 txnbytelimit 2097152 since the restore is going to 4 separate mount points, i started four separate restores, broken down by destination mount point. The restores appear to begin running fine. Then at some seemingly arbitrary point, a session will suddenly slow to a crawl while in the middle of restoring a file... it will maybe get less than 1MB every few minutes. Eventually, all the sessions get to this point with files growing ever so slowly. The only way to "jump start" it is to cancel a session and restart the restore, which "usually" runs fine again for awhile until eventually slowing down to a crawl again. Is this enough information or should I provide more? -Original Message- From: Richard Sims [mailto:[EMAIL PROTECTED] Sent: Monday, July 07, 2003 2:37 PM To: [EMAIL PROTECTED] Subject: Re: Restore slows to a crawl >Has anyone else experienced a problem when restoring data where it starts >fine but then at some random point it slows down to a crawl? The wait time >starts to climb to 38 seconds, then resets to 0, then climbs to 38 seconds, >then back to 0 constantly until there is no other choice but to stop the >session. I was running a restore as with a virtualnodename, using several >restores at once (since im restoring almost 1TB). Without knowing the kind of restoral you were performing or its environment (disk/file system configuration, collocation, tape drive type and model, etc.) we can only offer general suggestions. In that you were running multiple restore sessions at a time, certainly waiting for tape dismount and mount will be aggravated. In http://people.bu.edu/rbs/ADSM.QuickFacts topic "Restoral performance", the minimization of MOUNTRetention will help a lot. Automatic tape drive cleaning between tape mounts will add unaccountable time. Directory congestion slows performance. Data spread over tapes, with tape technology which is poor at start-stop action is bad news. The more information you can gather and supply, the more we can offer. Richard Sims, BU
Restore slows to a crawl
Has anyone else experienced a problem when restoring data where it starts fine but then at some random point it slows down to a crawl? The wait time starts to climb to 38 seconds, then resets to 0, then climbs to 38 seconds, then back to 0 constantly until there is no other choice but to stop the session. I was running a restore as with a virtualnodename, using several restores at once (since im restoring almost 1TB). I found one other post out there that mentioned multiple sessions and a session waiting on a tape... in this case I was indeed running several sessions. Is this a known problem? I can only run a single restore at a time (for a particular node)? Server is AIX4.3.3, TSM 5.1.5, client is AIX 5.1, TSM 5.1.5.4 Thanks in advance Steve
Re: AIX backup command via TSM scheduler
We have an AIX server, so I dont know if the syntax is different, but we do have AIX clients. we run similar commands but dont use any quotes and dont include the "-c", an entry for us is like this: su - oracle /home/oracle/scripts/backup/db_backup.sh It usually runs fine. however, there are isolated instances where it may fail with the rc=1 yet still run from the command line. in each of those cases we have had to step through the entire process with debug statements to find out what the problem is (keeping in mind that with the su -, the profile is sourced first.) usually, there ends up being some problem in the environment or a problem with double sourcing a file. i have no idea why the scheduler has problems when it runs okay from the command line. but that is what we have had to to... debug the process. Steve -Original Message- From: Neilson Lui [mailto:[EMAIL PROTECTED] Sent: Thursday, June 05, 2003 8:45 PM To: [EMAIL PROTECTED] Subject: AIX backup command via TSM scheduler Environment: Server TSM v5.1.5 on W2k Client TSM v5.1.5 on AIX with Oracle running Our backup job is currently being scheduled by the cron daemon on AIX via the command ( issued as root ) su - userid -c 'sh /tsmscript/backup.sh' I was trying to have the same command defined on TSM scheduler. But i was getting a return code of 1 when the same command is issued by the TSM scheduler. Is there a way to let the TSM scheduler use another userid instead of root ? Any suggestions.
Re: problem with a su script
we couldnt get it to work with the -c ... most all servers work fine without it. -Original Message- From: Joe Pendergast [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 02, 2003 9:48 AM To: [EMAIL PROTECTED] Subject: Re: problem with a su script My system uses the -c option of the su commmand su - oracle "-c /home/oracle/scripts/backup/db_backup.sh" Amazing what a missing flag will cause. "Conko, Steven" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 04/02/2003 05:25:07 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To:[EMAIL PROTECTED] cc: Subject:Re: problem with a su script > On all of our database servers we run an archive nightly but instead of a > regular "archive" we run a command instead: > > su - oracle /home/oracle/scripts/backup/db_backup.sh > > this script handles all the processing of the database and calls a dsmc > archive command. on 97% of the servers it works fine. however, on just a > few of them... that dont appear to be any different, the script > immediately dies with a return code of 1 (no, its not permissions) > however tsm reports it as completed (another problem). it doesnt appear > the script ever gets run because we use a debugging statement for the > first line that never gets called. nothing in the environment seems to be > a problem and on one system it just suddenly stopped working without any > changes being made. > > any ideas whats going on here? we're running aix 4.3.3, tsm client 5.1.5 > and server aix 4.3.3 tsm 4.2.2... even on the servers it works on. > > Steven A. Conko > Senior Unix Systems Administrator > ADT Security Services, Inc. >
Re: problem with a su script
> On all of our database servers we run an archive nightly but instead of a > regular "archive" we run a command instead: > > su - oracle /home/oracle/scripts/backup/db_backup.sh > > this script handles all the processing of the database and calls a dsmc > archive command. on 97% of the servers it works fine. however, on just a > few of them... that dont appear to be any different, the script > immediately dies with a return code of 1 (no, its not permissions) > however tsm reports it as completed (another problem). it doesnt appear > the script ever gets run because we use a debugging statement for the > first line that never gets called. nothing in the environment seems to be > a problem and on one system it just suddenly stopped working without any > changes being made. > > any ideas whats going on here? we're running aix 4.3.3, tsm client 5.1.5 > and server aix 4.3.3 tsm 4.2.2... even on the servers it works on. > > Steven A. Conko > Senior Unix Systems Administrator > ADT Security Services, Inc. >
Re: TSM Upgrade from 4.1 to 5.x questions
> Are there any issues with upgrading from TSM Server V4.1.2 to version > 5.1.x? Or do we have to upgrade to 4.2.x first? > > Also, what is the best version to upgrade to? 5.1.5, 5.1.6.2 or something > else? > > We are running on AIX 4.3.3 ML 10. > > Thanks in advance! > > Steven A. Conko > Senior Unix Systems Administrator > ADT Security Services, Inc. >
Re: TSM 5.1 Client Install on Sun Solaris - Help Please
The README files are usually pretty idiot proof provided the idiot reads them. What version of Solaris are you running? I had a problem installing on a Solaris 5.7 and 5.8 client because it required certain patches to be installed from Sun for the libraries. Again, that would show up in the README. Steve -Original Message- From: Tony Morgan [mailto:[EMAIL PROTECTED] Sent: Thursday, March 27, 2003 9:05 AM To: [EMAIL PROTECTED] Subject: TSM 5.1 Client Install on Sun Solaris - Help Please Hi Tivoliworld, I am not a Unix Person, so I can't understand why my Unix people are having trouble getting TSM Client installed on some Sun boxes. My unix knowledge is about 6 commands, but I can edit files due to my VMS background (the basic editor is very similar to Digital kit 20+ years ago). Does anyone have a brief document which makes the task idiot proof... I really need to show these people that they are being silly!!! (or are they?) Also, What can I expect to see... I understand that the Unix TSM environment is not as good as NT/W2K. The alternative is to get a consultant in... expensive and hard to justify. Can anyone help please... ??? Many Thanks Tony Morgan
Re: stupid backup compatibility question
4.0G... it is supposedly only compatible up to version 4.1.3 of TSM. -Original Message- From: Wilcox, Andy [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 26, 2003 11:12 AM To: [EMAIL PROTECTED] Subject: Re: stupid backup compatibility question What version of Tru64 are you running? Cheers Andy Wilcox Midrange Services Aquila Networks Services Ltd > -Original Message- > From: Conko, Steven [SMTP:[EMAIL PROTECTED] > Sent: 26 March 2003 15:57 > To: [EMAIL PROTECTED] > Subject: Re: stupid backup compatibility question > > > okay, im going to ask a stupid question... does anybody have any ideas > how > > to backup a compaq tru64 client running tsm 4.1.3 to an aix 4.3.3 server > > running 5.1.5 server? i know these versions arent compatible, but we > cant > > upgrade the compaq's o/s to allow us to upgrade the tsm client software. > > we're stuck at 4.1.3. > > > > any ideas??? > > > > Steven A. Conko > > Senior Unix Systems Administrator > > ADT Security Services, Inc. > > > > > ** > ** > Confidentiality: This e-mail and any files transmitted with it are > confidential and intended solely for the use of the individual or entity > to whom they are addressed. If you have received this e-mail in error, > use of this information (including disclosure, copying or distribution) > may be unlawful. Please notify [EMAIL PROTECTED] and > delete the message immediately. > > Security: Internet e-mail is not a 100% secure communications medium. > > Viruses: This e-mail (and any attachments) has been checked (using Sophos > Sweep 3.63 + patches) and found to be clean from any virus infection > before leaving. > Therefore neither Aquila Networks Services Ltd nor Midlands Electricity > plc or any of their group undertakings (as defined by the Companies Act > 1989) (together referred to as the "Companies") accept legal > responsibility for this message or liability for the consequences of any > computer viruses which may have been transmitted by this e-mail. > > Monitoring: All electronic communications with the Companies may be > monitored in accordance with the UK Regulation of Investigatory Powers > Act, Lawful Business Practice Regulations, 2000. If you do not consent to > such monitoring, you should contact the sender of this e-mail. > > Aquila Networks Services Limited, > Registered office: Whittington Hall, Whittington, Worcester, WR5 2RB > Registered in England and Wales number 3600545 > This e-mail may be sent on behalf of any of the Companies. > ** > **
Re: stupid backup compatibility question
> okay, im going to ask a stupid question... does anybody have any ideas how > to backup a compaq tru64 client running tsm 4.1.3 to an aix 4.3.3 server > running 5.1.5 server? i know these versions arent compatible, but we cant > upgrade the compaq's o/s to allow us to upgrade the tsm client software. > we're stuck at 4.1.3. > > any ideas??? > > Steven A. Conko > Senior Unix Systems Administrator > ADT Security Services, Inc. >
sunOS 5.7 problem
Extremely slow backups from a sunOS 5.7 client with lots of collisions. does anyone know how to hardcode the interface to 100 Full Duplex? Sparc 20 model. Steven A. Conko Senior Unix Systems Administrator ADT Security Services, Inc.
Re: 5.1.5 only 32 bit for aix 4.3.3?
> Is version 5.1.5 only available as a 32 bit application for AIX 4.3.3? I > found the 64 bit b/a module for AIX 5.1, but only 32 bit for 4.3.3... any > idea why?? > > Steven A. Conko > Senior Unix Systems Administrator > ADT Security Services, Inc. >
Re: mtlib command
i believe we had the same problem. try this: mtlib -l /dev/lmcp0 -vC -Vvolser -tFFFB steve conko -Original Message- From: Tommy Templeton [mailto:[EMAIL PROTECTED] Sent: Thursday, March 06, 2003 11:39 AM To: [EMAIL PROTECTED] Subject: mtlib command Does anyone know the mtlib command to clear erroneous volumes from inventory. These volumes were in the library but have been checked out. We use a 3494 library. thanks Tommy Templeton
question on versions and downloads
i have seen a lot of messages fly by here about various 5.1 tsm clients and their stability (or sometimes lack thereof). the last i had heard, 5.1.4 was considered a very stable client and 5.1.5 was not. ibm's website only has 5.1 and 5.1.5 available for AIX clients... are these my only choices? if so, which is the better of the two? is 5.1.5 stable? thanks steve
Disk->Tape migration, cache and maxnummp
Question about how this scenario plays out Client starts an archive backup of a database to server at 1700 from cron job. Archive is straight to tape. Uses all mountpoints assigned to it (4). Client then starts a scheduled incremental "system-level" backup at 1800 while original cron'd backup is still running. Incremental goes to diskpool. Diskpool is at 98% utilized, but 0.2 % migratable. Cache is on. Incremental fails due to media mount not possible. Does TSM consider the connection to the diskpool as an extra mount point and therefore does not allow it because the client is already using its max number of mount points (4) on the original archive? TSM Server is AIX 4.3.3 ML10 running TSM V5.1.5 TSM Client is AIX 4.3.3 ML9 running TSM V5.1.5. Library is a 3494, 6 drives.
volume in volhistory as STGDELETE
quick question we've got some tapes in our vault that apparantly dont show up anywhere in tsm under the volume or libvolume listing. the only place i have been able to find information about them is in the volhistory table which shows they were placed into a STGDELETE state back in november 2002. again.. these tapes do not show up anywhere else... not in volumes, libvolumes, contents, drmedia or media. can i safely assume there is nothing on these tapes? this is version 4.2.2
ANR9999D and ANR0197E
sorry... i tried to search for this but i cant seem to get connected to adsm.org. any idea what is happening with these errors? TSM V4.2.2 running on AIX 4.3.3 ML10 connected to 3494 Library with 3590 Tape drives we have seen this error before... this time happens to be during a backup stgp 02/13/03 09:58:05 ANR8337I 3590 volume J00521 mounted in drive D1 (/dev/rmt6). 02/13/03 09:58:05 ANR1340I Scratch volume J00521 is now defined in storage pool COPY_POOL_01. 02/13/03 09:59:36 ANR0195W Attempting to remove extraneous database entries for volume J00521. 02/13/03 09:59:36 ANRD asalloc.c(663): ThreadId<61> Volume J00521 being accessed remotely - ending repair attempt. 02/13/03 09:59:36 ANR0197E Removal of extraneous database entries for volume J00521 failed due to contention with other server processes or activities. 02/13/03 09:59:36 ANR0195W Attempting to remove extraneous database entries for volume J00521. 02/13/03 09:59:36 ANRD asalloc.c(663): ThreadId<62> Volume J00521 being accessed remotely - ending repair attempt. now it seems okay q vol j00521 f=d Volume Name: J00521 Storage Pool Name: COPY_POOL_01 Device Class Name: 3590CLASS Estimated Capacity (MB): 46,575.5 Pct Util: 100.0 Volume Status: Filling Access: Read/Write Pct. Reclaimable Space: 0.0 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 1 Write Pass Number: 1 Approx. Date Last Written: 02/13/03 10:45:48 Approx. Date Last Read: 02/13/03 10:01:11 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: Last Update by (administrator): Last Update Date/Time: 02/13/03 09:58:05
Re: Measuring progress of copy stgpool operation
what i do is run the -prev=yes -wait=yes options, capture the total amount of bytes to be backed up, then when the backup is actually running i run a small script to query the backup sessions, capture the total bytes backed up, add them together, then get a percentage and amount remaining. these results will get skewed slightly if you continue running normal backups while the backup stgp is running or if you dont account for the fact that once its the near the end of the backup stg some of the sessions drop out of the list. -Original Message- From: PAC Brion Arnaud [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 23, 2003 8:55 AM To: [EMAIL PROTECTED] Subject: Measuring progress of copy stgpool operation Hi all, Everything is in the title : is there a way (sql query ?) to find out, during a copy stgpool process, how many objects, or even better how many MB remains to be copied for finishing the process. Basically, the goal would be having an idea of remaining duration till the job ceases Thanks in advance ! Arnaud =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | Arnaud Brion, Panalpina Management Ltd., IT Group | | Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland | | Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01 | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Re: Very Puzzling Sessions lost
ive tried both ways... to disk and to tape. during the day and at night. manually and scheduled. high load and no load. its always the same. -Original Message- From: George Hagopian [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 9:59 AM To: [EMAIL PROTECTED] Subject: Re: Very Puzzling Sessions lost I've had a similar problem...might be of some help I had a server that would never finish and almost always fail at a certain point, it would tell me session terminated by user...no other explanation...if I run the backups maually it would almost always finish...but that was also during the day and not at the scheduled backup time... What I did, was increase the number of drives that the server would use during the backup...originally it was one tape drive and increased it to two tapes drives...problem disappeared and not reoccurred...not sure if you are writing directly to tape or to a disk pool. My 2 cents ghag -Original Message- From: Conko, Steven [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 9:42 AM To: [EMAIL PROTECTED] Subject: Very Puzzling Sessions lost We have some very strange session lost errors showing up on our client. First the particulars: Server is AIX 4.3.3 ML 10, TSM V4.2.2 Client is AIX 4.3.3 ML 10, TSM V5.1.5.5 (upgraded several times from V4.2.2 at TSM Support request to deal with this problem) Client and server are on separate 100 Mb full duplex subnets. There are other AIX 4.3.3 ML 10 clients on the same subnet as the failing client that do not get any errors. network option (no) settings are the same on both clients. dsm options have been modified on the failing client to reflect those on the successful client in troubleshooting to ensure differing options are not causing a problem. The client having the problem will start a backup (incremental or archive, scheduled or manual) and suddenly "freeze" for several minutes before severing the socket connection and will proceed to reconnect/timeout almost continuously. Sometimes it appears to stop in the same spot, other times not. There doesnt appear to be any reason why certain files would cause a problem (i.e., they are not open at the time). Any idea what i can check? I have tried everything... all sorts of settings in dsm.sys and no settings. There are not any errors reported on the system itself. just "session lost" on the client and "session terminated" on the server. Ive been working with IBM TSM Support for quite sometime and they just keep wanting more traces and "upgrade to the latest client." Im at my wits end.
Very Puzzling Sessions lost
We have some very strange session lost errors showing up on our client. First the particulars: Server is AIX 4.3.3 ML 10, TSM V4.2.2 Client is AIX 4.3.3 ML 10, TSM V5.1.5.5 (upgraded several times from V4.2.2 at TSM Support request to deal with this problem) Client and server are on separate 100 Mb full duplex subnets. There are other AIX 4.3.3 ML 10 clients on the same subnet as the failing client that do not get any errors. network option (no) settings are the same on both clients. dsm options have been modified on the failing client to reflect those on the successful client in troubleshooting to ensure differing options are not causing a problem. The client having the problem will start a backup (incremental or archive, scheduled or manual) and suddenly "freeze" for several minutes before severing the socket connection and will proceed to reconnect/timeout almost continuously. Sometimes it appears to stop in the same spot, other times not. There doesnt appear to be any reason why certain files would cause a problem (i.e., they are not open at the time). Any idea what i can check? I have tried everything... all sorts of settings in dsm.sys and no settings. There are not any errors reported on the system itself. just "session lost" on the client and "session terminated" on the server. Ive been working with IBM TSM Support for quite sometime and they just keep wanting more traces and "upgrade to the latest client." Im at my wits end.
tcpwindowsize, tcpbuffsize
we're running AIX 4.3.3 server and clients. server is TSM V4.2.2, clients are generally 4.2 as well. what should we have our tcpwindowsize and tcpbuffsize set to? i know the suggested size is 64 and 32 respectively, but the book mentions increasing them if the resources are available. i have inherited this system and many server have these values at 2048 and 512. the server tcpwindowsize is set to 1048576. should i consider changing these to the recommended values for better performance?
RE: Réf. : tcp layer problem
tcp server address is set to IP, as well as client address. "severname" is using the dns short name. -Original Message- From: Guillaume Gilbert [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 2:55 PM To: [EMAIL PROTECTED] Subject: Réf. : tcp layer problem I had this problem on a new implementation. Is your tcpserveraddress coded with the dns name or the ip adress? We chenged it to the ip adress and the problems went away. There was probably an error somewhere in the vlans but I'm not an ip guru... Guillaume Gilbert CGI Canada "Conko, Steven" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 2003-01-15 14:39:26 Veuillez répondre à "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Envoyé par : "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Pour : [EMAIL PROTECTED] cc : Objet : tcp layer problem ive been going round and round with tsm support on this issue... we have an AIX 4.3.3 client that has been upgraded several times all the way to 5.1.5 client version without success backing up to an AIX 4.3.3 tsm 4.2.2 server over a 10/100 ethernet network (100 Full Duplex, no autonegotiate.) there arent any network errors and the switches are all configured correctly, and the tsm server is fine. they are beginning to insist our problem is system/network level... error: ANS1809W Session is lost; initializing session reopen procedure. appears almost constantly during backups. usually it will EVENTUALLY finish with a few errors but take forever to run. all our parameters appear to be okay by tsm support standards. with the combonation of the server message saying session was terminated they say the client is severing the connection... that tsm is getting the message from a lower layer. we dont have any network errors appearing anywhere else on the system for any other applications, there are no errors in errpt or /var/adm/messages and diags come back fine. what else can i do to diagnose this problem?
tcp layer problem
ive been going round and round with tsm support on this issue... we have an AIX 4.3.3 client that has been upgraded several times all the way to 5.1.5 client version without success backing up to an AIX 4.3.3 tsm 4.2.2 server over a 10/100 ethernet network (100 Full Duplex, no autonegotiate.) there arent any network errors and the switches are all configured correctly, and the tsm server is fine. they are beginning to insist our problem is system/network level... error: ANS1809W Session is lost; initializing session reopen procedure. appears almost constantly during backups. usually it will EVENTUALLY finish with a few errors but take forever to run. all our parameters appear to be okay by tsm support standards. with the combonation of the server message saying session was terminated they say the client is severing the connection... that tsm is getting the message from a lower layer. we dont have any network errors appearing anywhere else on the system for any other applications, there are no errors in errpt or /var/adm/messages and diags come back fine. what else can i do to diagnose this problem?
Re: move drmedia but tapes werent ejected
i cant quite seem to get this to work im using a 3494 automated library with the following commands: checkin libv 3494 j00544 status=private owner=sy00055 devtype=3590.. but that just waits for it in the inport (messages to insert in actlog) so i try to search... checkin libv 3494 search=yes status=private devtype=3590 volrange=j00544,j00544... it returns immediately saying "0 found" -Original Message- From: LeBlanc, Patricia [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 9:44 AM To: [EMAIL PROTECTED] Subject: Re: move drmedia but tapes werent ejected just do a checkin, and a checkout. -Original Message----- From: Conko, Steven [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 9:32 AM To: [EMAIL PROTECTED] Subject: move drmedia but tapes werent ejected we're running tsm 4.2 on aix 4.3.3. we run a daily move drmedia but in this case 3 tapes did not get ejected because they were mounted. however, the move drmedia command made changes to make it look like they are no longer in the database. short of actually opening up the library and removing them (its a BIG library) how can we either "reintroduce" the tapes and then eject them or just eject them?
move drmedia but tapes werent ejected
we're running tsm 4.2 on aix 4.3.3. we run a daily move drmedia but in this case 3 tapes did not get ejected because they were mounted. however, the move drmedia command made changes to make it look like they are no longer in the database. short of actually opening up the library and removing them (its a BIG library) how can we either "reintroduce" the tapes and then eject them or just eject them?
Re: unknown system error
sorry... client 5.1.5, server 4.2 -Original Message- From: Richard Sims [mailto:[EMAIL PROTECTED]] Sent: Monday, January 06, 2003 4:21 PM To: [EMAIL PROTECTED] Subject: Re: unknown system error >does anyone know how i can find out the underlying, i.e. system level, >problem for the following type of error? im running aix 4.3.3 ML10. > >ANS4014E Error processing '/u103/oradata/adachr01/payroll_dat.dbf': unknown >system error (157) encountered. Program ending. You didn't tell us the important thing - your ADSM/TSM client level. You may be running an old client, which in the past has run afoul of automount file systems, where stopping the automounter may be a circumvention. By reason, the "system error (nnn)" should reflect the Unix errno value returned by a system subroutine. But the AIX 4.3.3 errno does not go as high as 157 (see /usr/include/sys/errno.h), which indicates that there was some garbage in the errno global variable - possibly there when the client module invoked whatever subroutine it invoked, and which it assumes is meaningful when the subroutine returns control. Richard Sims, BU
session lost errors
hello *sm'ers. we have been getting continuous "Session is lost" errors ever since upgrading our aix 4.3.3 client to ML 10, and we have even upgraded the TSM client to 5.1.5 (server is 4.2). TSM support insists it is system or network level but so far we have been unable to identify any system or network functions with problems. any suggestions? 01/05/03 21:39:45 sessSendVerb: Error sending Verb, rc: -50 01/05/03 21:39:45 ANS1809W Session is lost; initializing session reopen procedure. 01/05/03 21:39:46 ANS1809W Session is lost; initializing session reopen procedure. 01/05/03 21:40:00 ANS1810E TSM session has been reestablished. 01/05/03 21:40:47 sessSendVerb: Error sending Verb, rc: -50 01/05/03 21:40:47 ANS1809W Session is lost; initializing session reopen procedure. 01/05/03 21:40:48 ANS1809W Session is lost; initializing session reopen procedure. 01/05/03 21:41:02 ANS1810E TSM session has been reestablished.
unknown system error
does anyone know how i can find out the underlying, i.e. system level, problem for the following type of error? im running aix 4.3.3 ML10. ANS4014E Error processing '/u103/oradata/adachr01/payroll_dat.dbf': unknown system error (157) encountered. Program ending.
Re: Gigabit Ethernet speed
we're running aix 4.3.3 ML 10, so we have to have our gig e network cards set to auto_negotiate as they do not have a setting for 1000. a check of the device reports it IS running at 1000 MB full duplex. for our primary backups (i.e. database/large file) we are typically seeing between 8K - 15K. for system level backups (smaller files* we have seen up to 20K. we do not have jumbo frames enabled, but i think we could do so because the gigabit backbone is dedicated to backups. if we enable jumbo frames, what should we set the mtu size to? -Original Message- From: Kelly J. Lipp [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 24, 2002 5:36 PM To: [EMAIL PROTECTED] Subject: Re: Gigabit Ethernet speed What kind of performance are you seeing? I would expect a number greater than 20,000 KB/sec as reported by a client summary. I also would expect it to be highly variable and dependent on client speed. I believe that Gig E is going to be faster than just about anything else in all but the highest end systems so suspect a bottleneck elsewhere. As with 100 Mbit networks, duplex and link speed incompatibilities are killers. 100/1000 full is the way to go. Stay away from Auto unless you have un-managed network switches. Thanks, Kelly Kelly J. Lipp STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com or www.storserver.com (719)531-5926 Fax: (240)539-7175 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Conko, Steven Sent: Tuesday, December 24, 2002 7:44 AM To: [EMAIL PROTECTED] Subject: Gigabit Ethernet speed anybody have any tips on what type of "Network transfer rate" we should be seeing for our backups over gigabit ethernet? the clients backup via copper Gb ethernet dedicated for backups to a tsm server connected to a 3494 tape library with 10 3590 tape drives via fibre channel/brocade switch. there is only one client on one gigabit interface and 3 on another. any tips for improving network performance? thanks Steven A. Conko Senior Unix Systems Administrator ADT Security Services, Inc.
Gigabit Ethernet speed
anybody have any tips on what type of "Network transfer rate" we should be seeing for our backups over gigabit ethernet? the clients backup via copper Gb ethernet dedicated for backups to a tsm server connected to a 3494 tape library with 10 3590 tape drives via fibre channel/brocade switch. there is only one client on one gigabit interface and 3 on another. any tips for improving network performance? thanks Steven A. Conko Senior Unix Systems Administrator ADT Security Services, Inc.
Re: Many, almost empty volumes ??
i know this is a stupid question, but here goes... what is your reclamation threshold set to for that storage pool? are there other tapes available to reclaim to? -Original Message- From: John [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 11:21 AM To: [EMAIL PROTECTED] Subject: Many, almost empty volumes ?? Hi TSM'rs I am sure someone has had this before.. TSM Server 4.2 (Windows 2000) connected to a SAN based 18 slot LTO 3583. The total amount of storage is around 60GB which means there should never really be more that two, or at worst three tapes in the offsite pool. I have five. These are data tapes, not DBBackup tapes. Even after doing reclamation of the offsite pool the three tapes in question remain offsite and remain at 0.5, 2.1, 0.6 percent used. Is this normal. I was under the impression that reclamation is supposed to avoid this. Would appreciate any thoughts on this Rgds John
tape paths offline
i finally figured out why my incrementals to the diskpool were failing... large files were trying to go directly to tape ALL MY TAPE PATHS ARE OFFLINE!! how the heck does that happen?
Re: Idle system fails with Media mount not possible
well, by using the piecemeal method of successfully individually backing up everything that failed i have finally been able to run a successfull system wide backup. strange. is it possible with a 1GB filesize limit on the diskpool that several files added up to more than 1 gb? would that cause a problem? -Original Message- From: Kent Monthei [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 9:59 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible On the client, do a 'dsmc show opt' and a 'dsmc q inclexcl' to check for stray management-class bindings that are different from your other working clients. If all your clients don't belong to a common domain, then check the server for missing copygroup definitions, incorrect target pool, target pool with no associated volume, and/or policysets that haven't been 'activate'd. "Conko, Steven" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 18-Dec-2002 09:29 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: ADSM-L cc: Subject:Re: Idle system fails with Media mount not possible The strange thing as that other clients are backing up fine... these are three very similar, nearly identical clients, all configured exactly the same. the others backup fine, and this incremental keeps failing in the same spot with the media mount not possible. -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 9:12 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible I've also seen this where Unix hasn't released the drives from the OS. TSM seems them as available but not Unix. I have had to delete the drive and redefine so that they can be used. It was a bug in a certain code of TSM but I can't remember which one or even if that is truly your problem. Thanks, Rob. From: "Conko, Steven" <[EMAIL PROTECTED]> on 12/18/2002 09:03 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Idle system fails with Media mount not possible the client was already set to 2 mount points. the storage pool does not fill up. any other suggestions? -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 7:47 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible Query the node with F=d and change Number of Mount points from 0 to at least number of drives you have in library. What happened is stgpool probally filled up and the backup tried to continue on tape, but with Number of Mount points set to 0 said no and it failed. Thanks, Robert Rippy From: "Conko, Steven" <[EMAIL PROTECTED]> on 12/17/2002 04:19 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Idle system fails with Media mount not possible strange one... and ive looked at everything i can think of. In client dsmerror.log: 12/17/02 15:01:54 ANS1228E Sending of object '/tibco/logs/hawk/log/Hawk4.log' failed 12/17/02 15:01:54 ANS1312E Server media mount not possible 12/17/02 15:01:57 ANS1312E Server media mount not possible In activity log: ANR0535W Transaction failed for session 1356 for node SY00113 (AIX) - insufficient mount points available to satisfy the request. There is NOTHING else running on this TSM server. All 6 drives are online. The backup is going to a 18GB diskpool that is 8% full, there are plenty of scratch tapes, i set max mount points to 2. keep mount point=yes. it starts backing up the system then just fails... always at the same point. the file its trying to back up does not exceed the max size. all drives are empty, online. diskpool is online. i see the sessions start and then just after a minute or 2 just abort. any ideas?
Re: Idle system fails with Media mount not possible
yes, everything is going to the disk storage pool that has pleny of space. these systems dont use multiple management classes. -Original Message- From: John Naylor [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 10:24 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible So are you saying that the management class that the directories are atracting is pointing them to the same disk storage pool which you said had plenty of space. ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **
Re: Idle system fails with Media mount not possible
everything checks out so far. now what i have done is a specific backup of just the directory it was failing on... "dsmc incr /tibco/logs/ -subdir=yes" that ran fine and when i ran the system wide backup again it got further and failed on another subdirectory of /tibco. i then did a backup of THAT directory and it was successful. then the system wide backup got further but failed in ANOTHER /tibco directory. so right now im piecemealing it together. i cant understand why it keeps failing on these subdirectories. some /tibco/... dirs work. some dont. -Original Message- From: Kent Monthei [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 9:59 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible On the client, do a 'dsmc show opt' and a 'dsmc q inclexcl' to check for stray management-class bindings that are different from your other working clients. If all your clients don't belong to a common domain, then check the server for missing copygroup definitions, incorrect target pool, target pool with no associated volume, and/or policysets that haven't been 'activate'd. "Conko, Steven" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 18-Dec-2002 09:29 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: ADSM-L cc: Subject:Re: Idle system fails with Media mount not possible The strange thing as that other clients are backing up fine... these are three very similar, nearly identical clients, all configured exactly the same. the others backup fine, and this incremental keeps failing in the same spot with the media mount not possible. -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 9:12 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible I've also seen this where Unix hasn't released the drives from the OS. TSM seems them as available but not Unix. I have had to delete the drive and redefine so that they can be used. It was a bug in a certain code of TSM but I can't remember which one or even if that is truly your problem. Thanks, Rob. From: "Conko, Steven" <[EMAIL PROTECTED]> on 12/18/2002 09:03 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Idle system fails with Media mount not possible the client was already set to 2 mount points. the storage pool does not fill up. any other suggestions? -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 7:47 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible Query the node with F=d and change Number of Mount points from 0 to at least number of drives you have in library. What happened is stgpool probally filled up and the backup tried to continue on tape, but with Number of Mount points set to 0 said no and it failed. Thanks, Robert Rippy From: "Conko, Steven" <[EMAIL PROTECTED]> on 12/17/2002 04:19 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Idle system fails with Media mount not possible strange one... and ive looked at everything i can think of. In client dsmerror.log: 12/17/02 15:01:54 ANS1228E Sending of object '/tibco/logs/hawk/log/Hawk4.log' failed 12/17/02 15:01:54 ANS1312E Server media mount not possible 12/17/02 15:01:57 ANS1312E Server media mount not possible In activity log: ANR0535W Transaction failed for session 1356 for node SY00113 (AIX) - insufficient mount points available to satisfy the request. There is NOTHING else running on this TSM server. All 6 drives are online. The backup is going to a 18GB diskpool that is 8% full, there are plenty of scratch tapes, i set max mount points to 2. keep mount point=yes. it starts backing up the system then just fails... always at the same point. the file its trying to back up does not exceed the max size. all drives are empty, online. diskpool is online. i see the sessions start and then just after a minute or 2 just abort. any ideas?
Re: Idle system fails with Media mount not possible
yes, it is always failing on the same file(s) in the same directory. how would it attract a different management class? this is using the default management class and we dont have any includes or excludes set up. -Original Message- From: John Naylor [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 9:35 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible Does it fail on the same file or directory every time, and does that file or directory attract a management class which is pointing to a different storage pool "Conko, Steven" <[EMAIL PROTECTED]> on 12/18/2002 02:29:12 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc:(bcc: John Naylor/HAV/SSE) Subject: Re: Idle system fails with Media mount not possible The strange thing as that other clients are backing up fine... these are three very similar, nearly identical clients, all configured exactly the same. the others backup fine, and this incremental keeps failing in the same spot with the media mount not possible. -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 9:12 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible I've also seen this where Unix hasn't released the drives from the OS. TSM seems them as available but not Unix. I have had to delete the drive and redefine so that they can be used. It was a bug in a certain code of TSM but I can't remember which one or even if that is truly your problem. Thanks, Rob. From: "Conko, Steven" <[EMAIL PROTECTED]> on 12/18/2002 09:03 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Idle system fails with Media mount not possible the client was already set to 2 mount points. the storage pool does not fill up. any other suggestions? -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 7:47 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible Query the node with F=d and change Number of Mount points from 0 to at least number of drives you have in library. What happened is stgpool probally filled up and the backup tried to continue on tape, but with Number of Mount points set to 0 said no and it failed. Thanks, Robert Rippy From: "Conko, Steven" <[EMAIL PROTECTED]> on 12/17/2002 04:19 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Idle system fails with Media mount not possible strange one... and ive looked at everything i can think of. In client dsmerror.log: 12/17/02 15:01:54 ANS1228E Sending of object '/tibco/logs/hawk/log/Hawk4.log' failed 12/17/02 15:01:54 ANS1312E Server media mount not possible 12/17/02 15:01:57 ANS1312E Server media mount not possible In activity log: ANR0535W Transaction failed for session 1356 for node SY00113 (AIX) - insufficient mount points available to satisfy the request. There is NOTHING else running on this TSM server. All 6 drives are online. The backup is going to a 18GB diskpool that is 8% full, there are plenty of scratch tapes, i set max mount points to 2. keep mount point=yes. it starts backing up the system then just fails... always at the same point. the file its trying to back up does not exceed the max size. all drives are empty, online. diskpool is online. i see the sessions start and then just after a minute or 2 just abort. any ideas? ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **
Re: Idle system fails with Media mount not possible
The strange thing as that other clients are backing up fine... these are three very similar, nearly identical clients, all configured exactly the same. the others backup fine, and this incremental keeps failing in the same spot with the media mount not possible. -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 9:12 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible I've also seen this where Unix hasn't released the drives from the OS. TSM seems them as available but not Unix. I have had to delete the drive and redefine so that they can be used. It was a bug in a certain code of TSM but I can't remember which one or even if that is truly your problem. Thanks, Rob. From: "Conko, Steven" <[EMAIL PROTECTED]> on 12/18/2002 09:03 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Idle system fails with Media mount not possible the client was already set to 2 mount points. the storage pool does not fill up. any other suggestions? -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 7:47 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible Query the node with F=d and change Number of Mount points from 0 to at least number of drives you have in library. What happened is stgpool probally filled up and the backup tried to continue on tape, but with Number of Mount points set to 0 said no and it failed. Thanks, Robert Rippy From: "Conko, Steven" <[EMAIL PROTECTED]> on 12/17/2002 04:19 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Idle system fails with Media mount not possible strange one... and ive looked at everything i can think of. In client dsmerror.log: 12/17/02 15:01:54 ANS1228E Sending of object '/tibco/logs/hawk/log/Hawk4.log' failed 12/17/02 15:01:54 ANS1312E Server media mount not possible 12/17/02 15:01:57 ANS1312E Server media mount not possible In activity log: ANR0535W Transaction failed for session 1356 for node SY00113 (AIX) - insufficient mount points available to satisfy the request. There is NOTHING else running on this TSM server. All 6 drives are online. The backup is going to a 18GB diskpool that is 8% full, there are plenty of scratch tapes, i set max mount points to 2. keep mount point=yes. it starts backing up the system then just fails... always at the same point. the file its trying to back up does not exceed the max size. all drives are empty, online. diskpool is online. i see the sessions start and then just after a minute or 2 just abort. any ideas?
Re: Idle system fails with Media mount not possible
yes, its at ML 10. -Original Message- From: David Longo [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 17, 2002 7:12 PM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible You didn't mention the Maint Level of AIX 4.3.3. If you have less than ML 10, then I would upgrade to that as one step. David Longo >>> [EMAIL PROTECTED] 12/17/02 05:15PM >>> How strange.. I just went through something similar. Running on AIX 4.3.3, TSM 4.2.1.7. What are you running? The short answer was to reboot the AIX operating system, and everything started working fine.. The long answer follows (well, not really an answer, just my situation, and what I tried to resolve it). Server AIX 4.3.3 TSM 4.2.1.7 Nodes W2K Storage Agent 4.2.1.7 BA Client 4.2.1.32 TDP for SQL 2.2 SQL 2000 and WinNT4 Storage Agent 4.2.1.7 BA Client 4.2.1.15 TDP for SQL 1.1 SQL 6.5 Relevant TSM server storage as follows... diskpool_sql_meta (no next storage pool intended only for the */.../meta/.../* info) diskpool_sql (next storage pool is ltotape_sql, intended for smaller databases) ltotape_sql (collocation of FILESPACE since /stripes=2 backups are kept here) The SQL 2000 server had been having issues over the last few months where backups to ltotape_sql with /stripes=2 of a 265GB database would fail with a "server media mount no possible" error, but /stripes=1 differential backups would back up fine. Oddly, increasing the Maximum Mount Points for the node by one would allow the /stripes=2 backup to succeed, but the next time a /stripes=2 backup would run, it would fail (until I increased the MMP again). I had 5 drives, all free and unused and 7 MMP for the node when... this new wrinkle occurred. The SQL 6.5 server started having problems backing up certain databases: the smaller system databases; master, model, msdb, pubs, tempdb, with and error message of "server media mount not possible". All the DBs on this server have a destination of ltotape_sql. Like you, plenty of room in the storage pool, plenty of scratch. Called support Got level one.. told him a few things.. he didn't even want to try it.. and immediately escalated to level two. While I waited for a call back from level two, the following occurred. I noticed that there are some databases in diskpool_sql that haven't migrated to ltotape_sql. Kicking off a migration gets a similar error message "media mount not possible", which, oddly, is the same message I got from the storage agent when backing up tapes to ltotape_sql. I carefully detailed what it took to migrate those 3 files from diskpool_sql to ltotape_sql, which is a whole other chapter by itself, involving changing maxscratch up and down, moving data, and a few other hoops, and I was unable to get some tapes to "move" with a move data command (tapes that had only one master or msdb or tempdb type database on them). Level two calls back. I go through the entire situation, including the fact of the Max Mount Point having to change every time I did I /stirpes=2 backup (I wasn't sure if that was a related issue or not). She is baffled, and wants to think it over and search databases etc to see what she can come up with. Within 30 mins, she calls back and asks me to reboot the TSM server's OS (uptime reported a whopping 82 days), just to see what would happen. I do. Migrations go. Backups /stripes=1 go. Backups /stripes=2 go (even with MMP set back to 4 for that node, instead of 7 ( with only 5 tape drives remember). This was Friday. Sunday night, the TSM server did something odd (haven't reported this to TSM support yet). It just stopped. It showed link status on the fiber cards, and network cards, but you couldn't ping it, the server console wouldn't wake up, nothing. Even the display on the front was dark, but the power light was on steady like it was operational, not flashing like it would be if you did a proper shutdown. I "reset" it Monday morning when I found it that way, and then had to do a clean shutdown and power on to get the fiber cards to see the library correctly. Very weird. So, I am taking Monday morning (yesterday) as the start time to see how long it takes until I have to increase my MMP on the one node just to get a /stripes=2 backup. The saga continues... "Conko, Steven" To: [EMAIL PROTECTED] <[EMAIL PROTECTED] cc: M> Fax to: Sent by: Subject: Idle system fails with Media mount not possible "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] IST.EDU> 12/17/2002 03:19 PM Please respond to "
Re: Idle system fails with Media mount not possible
the client was already set to 2 mount points. the storage pool does not fill up. any other suggestions? -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 7:47 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible Query the node with F=d and change Number of Mount points from 0 to at least number of drives you have in library. What happened is stgpool probally filled up and the backup tried to continue on tape, but with Number of Mount points set to 0 said no and it failed. Thanks, Robert Rippy From: "Conko, Steven" <[EMAIL PROTECTED]> on 12/17/2002 04:19 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Idle system fails with Media mount not possible strange one... and ive looked at everything i can think of. In client dsmerror.log: 12/17/02 15:01:54 ANS1228E Sending of object '/tibco/logs/hawk/log/Hawk4.log' failed 12/17/02 15:01:54 ANS1312E Server media mount not possible 12/17/02 15:01:57 ANS1312E Server media mount not possible In activity log: ANR0535W Transaction failed for session 1356 for node SY00113 (AIX) - insufficient mount points available to satisfy the request. There is NOTHING else running on this TSM server. All 6 drives are online. The backup is going to a 18GB diskpool that is 8% full, there are plenty of scratch tapes, i set max mount points to 2. keep mount point=yes. it starts backing up the system then just fails... always at the same point. the file its trying to back up does not exceed the max size. all drives are empty, online. diskpool is online. i see the sessions start and then just after a minute or 2 just abort. any ideas?
Idle system fails with Media mount not possible
strange one... and ive looked at everything i can think of. In client dsmerror.log: 12/17/02 15:01:54 ANS1228E Sending of object '/tibco/logs/hawk/log/Hawk4.log' failed 12/17/02 15:01:54 ANS1312E Server media mount not possible 12/17/02 15:01:57 ANS1312E Server media mount not possible In activity log: ANR0535W Transaction failed for session 1356 for node SY00113 (AIX) - insufficient mount points available to satisfy the request. There is NOTHING else running on this TSM server. All 6 drives are online. The backup is going to a 18GB diskpool that is 8% full, there are plenty of scratch tapes, i set max mount points to 2. keep mount point=yes. it starts backing up the system then just fails... always at the same point. the file its trying to back up does not exceed the max size. all drives are empty, online. diskpool is online. i see the sessions start and then just after a minute or 2 just abort. any ideas?
Re: TDP Exchange Failing
i triple checked the activity log and there were no pending requests for tape mounts. it appears to backup the DIR portion fine but always fails (3 straight days now) on the IS portion. -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Monday, December 16, 2002 10:51 AM To: [EMAIL PROTECTED] Subject: Re: TDP Exchange Failing Check prior to that message for other related issues like no drives available or storage pool full. Looks like no resources available for backup. No tape drives or it could of been preempted by another higher process. Just look prior to what you have below. I would search activity log like this : 'Q AC BEGIND=12/15/2002 BEGINT=00:00 ENDD=12/15/2002 S=MAILJAXEX' Thanks, Robert Rippy From: "Conko, Steven" <[EMAIL PROTECTED]> on 12/16/2002 10:45 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: TDP Exchange Failing hi all! running into a problem here. TSM Server = AIX 4.3.3/TSM 4.2, 3494 Tape Library, 3590 type drives TDP Client = WinNT 4.0, TSM Client 4.2, TDP Version Getting this error in the Server Activity log: 12/15/02 22:01:25 ANE4993E (Session: 139502, Node: MAILJAXEX) TDP MSExchgV2 NT ACN3502 TDP for Microsoft Exchange: full backup of Information Store from server MAILJAX failed, rc = 418. 12/15/02 22:01:25 ANR2579E Schedule FUL_EXH_BACKUP_2200 in domain ADT_NT for node MAILJAXEX failed (return code 402). Got this message from the client log: 12/15/2002 22:01:25 ANS1309W (RC9)Requested data is offline 12/15/2002 22:01:25 Retrying failed backups... 12/15/2002 22:01:25 Total storage groups requested for backup: 1 12/15/2002 22:01:25 Total storage groups backed up: 0 12/15/2002 22:01:25 Total storage groups expired: 0 12/15/2002 22:01:25 Total storage groups excluded: 0 12/15/2002 22:01:25 Throughput rate:6,558.73 Kb/Sec 12/15/2002 22:01:25 Total bytes transferred:344,961,289 12/15/2002 22:01:25 Elapsed processing time:51.36 Secs any idea whats going on here?
TDP Exchange Failing
hi all! running into a problem here. TSM Server = AIX 4.3.3/TSM 4.2, 3494 Tape Library, 3590 type drives TDP Client = WinNT 4.0, TSM Client 4.2, TDP Version Getting this error in the Server Activity log: 12/15/02 22:01:25 ANE4993E (Session: 139502, Node: MAILJAXEX) TDP MSExchgV2 NT ACN3502 TDP for Microsoft Exchange: full backup of Information Store from server MAILJAX failed, rc = 418. 12/15/02 22:01:25 ANR2579E Schedule FUL_EXH_BACKUP_2200 in domain ADT_NT for node MAILJAXEX failed (return code 402). Got this message from the client log: 12/15/2002 22:01:25 ANS1309W (RC9)Requested data is offline 12/15/2002 22:01:25 Retrying failed backups... 12/15/2002 22:01:25 Total storage groups requested for backup: 1 12/15/2002 22:01:25 Total storage groups backed up: 0 12/15/2002 22:01:25 Total storage groups expired: 0 12/15/2002 22:01:25 Total storage groups excluded: 0 12/15/2002 22:01:25 Throughput rate:6,558.73 Kb/Sec 12/15/2002 22:01:25 Total bytes transferred:344,961,289 12/15/2002 22:01:25 Elapsed processing time:51.36 Secs any idea whats going on here?
Re: tape-to-tape performance
thanks for that insight. i forgot to mention we are running fibre channel and not scsi drives. yes, the data is must have... it is all production data and is being copied for DRM. how much of a performance hit will it take to turn compression on at the client level? -Original Message- From: Cook, Dwight E [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 20, 2002 3:22 PM To: [EMAIL PROTECTED] Subject: Re: tape-to-tape performance Is 1.6 TB the amount of "must have/critical" information ? and is that already compressed ? Knowing each tape mount runs about 90 seconds, any way to reduce tape mounts will speed up copies. If you have collocation on, turning it off ~could~ help... and collocation can/is set on both primary pools and copy pools. Now if the data isn't compressed by the client the data is uncompressed at the drive, moved through the processor as ~full size~ data, then recompressed at the destination drive. If your clients have the horsepower, turn on client compression, that way not so much data is moved across the processor's buss. Don't daisy chain any of your 3590's if they are older scsi. You might be able to reduce your data down if you force the application owners to review their required CRITICAL/MUST HAVE data and send it to isolated pools for copies to take offsite. just some thoughts... Dwight -----Original Message- From: Conko, Steven [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 20, 2002 1:26 PM To: [EMAIL PROTECTED] Subject: tape-to-tape performance we run a 3494 tape library with 3590 tape drives. after our backup are finished, we run a backup stgpool to a copy pool on about 1.6TB of data. as you can imagine, even with 8 drives this takes some time. are there any server, device or other parameters we can tune to improve the tape-to-tape performance? steve
tape-to-tape performance
we run a 3494 tape library with 3590 tape drives. after our backup are finished, we run a backup stgpool to a copy pool on about 1.6TB of data. as you can imagine, even with 8 drives this takes some time. are there any server, device or other parameters we can tune to improve the tape-to-tape performance? steve
Re: Multiple sessions per tape
why does having the diskpool in between improve performance? -Original Message- From: Alexander Lazarevich [mailto:alazarev@;HERA.ITG.UIUC.EDU] Sent: Wednesday, October 30, 2002 4:35 PM To: [EMAIL PROTECTED] Subject: Re: Multiple sessions per tape Totally. We used to backup to tape. But since putting a disk spool inbetween, the performance has significantly improved. Alex ------ Alex Lazarevich | Systems | Imaging Technology Group [EMAIL PROTECTED] | (217)244-1565 | www.itg.uiuc.edu ------ On Wed, 30 Oct 2002, Joshua Bassi wrote: > It is restricted to one. The best way to backup your data is to a disk > pool first, then bleed the diskpool to tape and you will get much better > performance out of your single session than you would if you backed up > directly to tape. > > > -- > Joshua S. Bassi > IBM Certified - AIX 4/5L, SAN, Shark > Tivoli Certified Consultant - ADSM/TSM > eServer Systems Expert -pSeries HACMP > > AIX, HACMP, Storage, TSM Consultant > Cell (831) 595-3962 > [EMAIL PROTECTED] > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU] On Behalf Of > Conko, Steven > Sent: Wednesday, October 30, 2002 10:16 AM > To: [EMAIL PROTECTED] > Subject: Multiple sessions per tape > > We're running ADSM 4.2 on AIX 4.3.3, 3494 library, 3590 drives. > > Is there any way to control the number of sessions per tape or is it > restricted to one? > > Steven A. Conko > Senior Unix Systems Administrator > ADT Security Services, Inc. >
Multiple sessions per tape
We're running ADSM 4.2 on AIX 4.3.3, 3494 library, 3590 drives. Is there any way to control the number of sessions per tape or is it restricted to one? Steven A. Conko Senior Unix Systems Administrator ADT Security Services, Inc.
