AIX memory recommendation
Hi All, We are in the process of migrating an AIX TSM server from 5.5.3 to 6.2.x. Now I know that IBM only specifies 12GB for the server (no dedup), but I was wondering if there is some calculation on how much memory really is required. The server has about 500-550 clients and will get a Diskpool from SAN and Tape from a 3494. Any advice or reference will be appreciated. Thanks in advance, Richard.
Re: Problem adding random access storage pool volumes
I ran into that problem a few years back. You will have to reduce your volumes. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Mueller, Ken Sent: Thursday, April 07, 2011 9:00 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Problem adding random access storage pool volumes You may be running out of file handles. Based on your numbers, I'd guess there is a per-process limit of 1024 file handles. Your storage volumes are using most of them and there aren't enough left over for TSM to do what it needs to (open a message file, etc). Assuming mainframe Linux is equivalent to other platforms, look into the ulimit command (ulimit -a will show the various resource limits). -Ken On Apr 7, 2011, at 9:30, "Thomas Denier" wrote: > We have a TSM 5.5.4.0 server running under mainframe Linux. The server has > two random access disk storage pools with a total of 726 volumes. Most of > the volumes are 2 GB. A few are smaller to fit in space left over after > populating file systems with as many 2 GB volumes as possible. Yesterday we > attempted to add 233 more volumes to one of the pools. We had added 214 > when a volume formatting process failed. Shortly after that we starting > seeing a wide range of errors. Reclamation processes failed. The server > refused TCP/IP connection requests from both nodes and administrative > command line clients. Sessions for scheduled backups (with prompt mode > scheduling) hung. The activity log reported that message texts were > unavailable for a variety of message numbers. Many header fields in query > output contained something like 'HEADER NOT AVAILABLE'. The server was > unable to write accounting records. I restarted the server, and the > symptoms came back within minutes after the restart. I removed the new > volumes and restarted the server again. The server then behaved normally. > > Am I correct in suspecting that the problem had to do with the number > of storage pool volumes, and that I will be able to enlarge the storage > pool safely if I replace existing 2 GB volumes with volumes in the 10 > to 20 GB range, and use the same size for new volumes? This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: Copypool storage advice
On Apr 7, 2011, at 11:07 PM, Paul_Dudley wrote: > I currently have a lot of copypool storage tapes which are between 50 - 60% > utilization. Expiration runs daily and I run reclaimation daily on this > copypool, set to 50. > > Is there anything I can do to try and consolidate the data onto fewer > copypool tapes? I would conclude that you have your collocation on the copypool set to something other than "none." My back-up theory is that you're using a "dur=" parameter on your reclaim commands, and they simply are not finishing. Are these tapes marked as being off-site? Are they in "filling" status or "full"? "Filling" tapes normally are excluded from reclamation if they're allegedly still in the library. I'm not sure why it would matter, but what's your TSM server level? > Thanks & Regards > > Paul Nick
Re: AIX memory recommendation
Richard, I allocate 32 GB for a TSM 6.2 AIX server, this value is aligned with IBM TSM specialists. Best regards, Kurt -Oorspronkelijk bericht- Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Richard van Denzel Verzonden: vrijdag 8 april 2011 10:29 Aan: ADSM-L@VM.MARIST.EDU Onderwerp: [ADSM-L] AIX memory recommendation Hi All, We are in the process of migrating an AIX TSM server from 5.5.3 to 6.2.x. Now I know that IBM only specifies 12GB for the server (no dedup), but I was wondering if there is some calculation on how much memory really is required. The server has about 500-550 clients and will get a Diskpool from SAN and Tape from a 3494. Any advice or reference will be appreciated. Thanks in advance, Richard. *** Disclaimer *** Vlaamse Radio- en Televisieomroeporganisatie Auguste Reyerslaan 52, 1043 Brussel nv van publiek recht BTW BE 0244.142.664 RPR Brussel http://www.vrt.be/gebruiksvoorwaarden
Re: TDp and retention settings question
>>is that the case? tdp manages the inactivating of the prior full on the TSM >>side? so this can be related to be akin to similar to a file backup where >>once the file is deleted (or marked inactive by TDP) the backup falls under >>the 30 day expiration window. << With rman and TSM for DB (oracle), each backup "file" that TSM gets is a unique name. Therefore it is always "active" to TSM and TSM won't expire it. From the "Data Protection for Oracle for UNIX and Linux Installation and User’s Guide" manual: "RMAN uses the format parameter (in the RMAN script) to generate unique backup file names. Because all backup objects inserted into the Tivoli Storage Manager backup storage pool have unique file names, they never expire on the Tivoli Storage Manager server. As a result, Data Protection for Oracle requires these special Tivoli Storage Manager policy domain settings: Backup copy group values Data Protection for Oracle provides the tdposync utility to remove unwanted backup objects from the Tivoli Storage Manager server. It is recommended that the following Tivoli Storage Manager backup copy group options be set: v verdeleted 0 v retonly 0Then, when Data Protection for Oracle marks a backup object inactive, that object is deleted from the Tivoli Storage Manager server the next time expiration processing occurs. A backup object is marked for immediate expiration when you delete it through RMAN using the Data Protection for Oracle interface or with the tdposync utility. Note that an inactive backup object cannot be restored through RMAN using the Data Protection for Oracle interface. Notes: 1. The Tivoli Storage Manager administrator must also register your node by specifying backdelete yes in order for backup objects to be deleted. However, be aware that a backup object is marked for immediate expiration when backdelete yes and you delete it through RMAN using the Data Protection for Oracle interface or with the tdposync utility." >>> js1000 4/6/2011 3:59 PM >>> The posting doesn't specify which TDP, which would help understanding. TDP for sql with a variety of different versions depending on which server Which means that to TSM they are all active backups and TSM will therefore not expire them. They have to be expired/deleted from the TDP side, e.g. rman for oracle. is that the case? tdp manages the inactivating of the prior full on the TSM side? so this can be related to be akin to similar to a file backup where once the file is deleted (or marked inactive by TDP) the backup falls under the 30 day expiration window. +-- |This was sent by jonathan.s...@osumc.edu via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: ANS1417W Protected system state file 'C:\Windows\System32\wuauclt.exe' is backed up to the drive file space, not system state file space.
Hi Timothy, yes, the ANS5283E would trigger the rc 12. The next step would be to review the dsmerror.log for messages between the time the backup started (around midnight?) and 00:01:42 when ANS5283E was issued to see if there are further details about the error. Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager "ADSM: Dist Stor Manager" wrote on 2011-04-07 09:49:57: > From: "Hughes, Timothy" > To: ADSM-L@vm.marist.edu > Date: 2011-04-07 10:04 > Subject: Re: ANS1417W Protected system state file 'C:\Windows > \System32\wuauclt.exe' is backed up to the drive file space, not > system state file space. > Sent by: "ADSM: Dist Stor Manager" > > Andy, > > I looked further as you suggested and found the problem I think? > Notice the last message "ANS5283E the operation was unsuccessful". > Though still not quite sure exactly causing that unsuccessful operation. > > > > 4/07/2011 00:01:42 ANS1959I Removing previous incomplete group > '\System State\0\SystemState' Id:0-75703620 > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'ASR' > using shadow copy. > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'This > is the path to the boot BCD store and the boot managers. > All the files in this directory need to be backed up.' using shadow copy. > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'Select > this volume (C:) if it is a critical volume. > Critical volumes are those which ASR must restore.' using shadow copy. > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'Select > to include disk #0 (of signature 0xac61e698) for ASR restore.' using > shadow copy. > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'Select > to include disk #1 (of signature 0x1de944bd) for ASR restore.' using > shadow copy. > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'Select > to include disk #2 (of signature 0xf01ed94c) for ASR restore.' using > shadow copy. > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'Select > to include disk #6 (of signature 0x7581cf48) for ASR restore.' using > shadow copy. > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'Select > to include disk #8 (of signature 0xad94f4eb) for ASR restore.' using > shadow copy. > 04/07/2011 00:01:42 Backing up object 'COM+ REGDB Writer' component > 'COM+ REGDB' using shadow copy. > 04/07/2011 00:01:42 Backing up object 'Registry Writer' component > 'Registry' using shadow copy. > 04/07/2011 00:01:42 Backing up object 'Cluster Database' component > 'ClusterDatabase' using shadow copy. > 04/07/2011 00:01:42 Backing up object 'IIS Config Writer' component > 'IISCONFIG' using shadow copy. > 04/07/2011 00:01:42 Backing up object 'IIS Metabase Writer' > component 'IISMETABASE' using shadow copy. > 04/07/2011 00:01:42 Backing up object 'WMI Writer' component > 'Windows Managment Instrumentation' using shadow copy. > 04/07/2011 00:01:42 ANS5283E The operation was unsuccessful. > > > Regards > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On > Behalf Of Andrew Raibeck > Sent: Wednesday, April 06, 2011 2:55 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: ANS1417W Protected system state file 'C:\Windows > \System32\wuauclt.exe' is backed up to the drive file space, not > system state file space. > > Timothy, > > The TSM return codes are set based on the highest severity issue that was > encountered during the backup. There is a chapter in the client manual on > return code that discusses the "rules" for how messages determine the > return code (just in case you aren't already familiar with that > information). In older client manuals it used to be part of the chapter on > scheduling, but in the current manual it has its own chapter. > > In the messages you showed here, I see nothing that would cause the RC to > be set to 12. Check dsmsched.log and dsmerror.log for other messages that > might indicate a problem. There has to be some error message there > (unrelated to skipped files) that is triggering the RC 12. > > Best regards, > > Andy Raibeck > IBM Software Group > Tivoli Storage Manager Client Product Development > Level 3 Team Lead > Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS > Internet e-mail: stor...@us.ibm.com > > IBM Tivoli Storage Manager support web page: > http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/ > Tivoli_Storage_Manager > > "ADSM: Dist Stor Manager" wrote on 2011-04-06 > 11:21:57: > > > From: "Hughes, Timothy" > > To: ADSM-L@vm.marist.edu > > Date: 2011-04-06 11:47 > > Subject: Re: ANS1417W Protected system state file 'C:\Windows > > \System32\wuauclt.exe' is backed up to the drive file space, n
Re: ANS1417W Protected system state file 'C:\Windows\System32\wuauclt.exe' is backed up to the drive file space, not system state file space.
Thanks Andy, . Yes..the backup started around midnight Regards -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Andrew Raibeck Sent: Friday, April 08, 2011 9:20 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: ANS1417W Protected system state file 'C:\Windows\System32\wuauclt.exe' is backed up to the drive file space, not system state file space. Hi Timothy, yes, the ANS5283E would trigger the rc 12. The next step would be to review the dsmerror.log for messages between the time the backup started (around midnight?) and 00:01:42 when ANS5283E was issued to see if there are further details about the error. Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager "ADSM: Dist Stor Manager" wrote on 2011-04-07 09:49:57: > From: "Hughes, Timothy" > To: ADSM-L@vm.marist.edu > Date: 2011-04-07 10:04 > Subject: Re: ANS1417W Protected system state file 'C:\Windows > \System32\wuauclt.exe' is backed up to the drive file space, not > system state file space. > Sent by: "ADSM: Dist Stor Manager" > > Andy, > > I looked further as you suggested and found the problem I think? > Notice the last message "ANS5283E the operation was unsuccessful". > Though still not quite sure exactly causing that unsuccessful operation. > > > > 4/07/2011 00:01:42 ANS1959I Removing previous incomplete group > '\System State\0\SystemState' Id:0-75703620 > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'ASR' > using shadow copy. > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'This > is the path to the boot BCD store and the boot managers. > All the files in this directory need to be backed up.' using shadow copy. > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'Select > this volume (C:) if it is a critical volume. > Critical volumes are those which ASR must restore.' using shadow copy. > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'Select > to include disk #0 (of signature 0xac61e698) for ASR restore.' using > shadow copy. > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'Select > to include disk #1 (of signature 0x1de944bd) for ASR restore.' using > shadow copy. > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'Select > to include disk #2 (of signature 0xf01ed94c) for ASR restore.' using > shadow copy. > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'Select > to include disk #6 (of signature 0x7581cf48) for ASR restore.' using > shadow copy. > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'Select > to include disk #8 (of signature 0xad94f4eb) for ASR restore.' using > shadow copy. > 04/07/2011 00:01:42 Backing up object 'COM+ REGDB Writer' component > 'COM+ REGDB' using shadow copy. > 04/07/2011 00:01:42 Backing up object 'Registry Writer' component > 'Registry' using shadow copy. > 04/07/2011 00:01:42 Backing up object 'Cluster Database' component > 'ClusterDatabase' using shadow copy. > 04/07/2011 00:01:42 Backing up object 'IIS Config Writer' component > 'IISCONFIG' using shadow copy. > 04/07/2011 00:01:42 Backing up object 'IIS Metabase Writer' > component 'IISMETABASE' using shadow copy. > 04/07/2011 00:01:42 Backing up object 'WMI Writer' component > 'Windows Managment Instrumentation' using shadow copy. > 04/07/2011 00:01:42 ANS5283E The operation was unsuccessful. > > > Regards > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On > Behalf Of Andrew Raibeck > Sent: Wednesday, April 06, 2011 2:55 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: ANS1417W Protected system state file 'C:\Windows > \System32\wuauclt.exe' is backed up to the drive file space, not > system state file space. > > Timothy, > > The TSM return codes are set based on the highest severity issue that was > encountered during the backup. There is a chapter in the client manual on > return code that discusses the "rules" for how messages determine the > return code (just in case you aren't already familiar with that > information). In older client manuals it used to be part of the chapter on > scheduling, but in the current manual it has its own chapter. > > In the messages you showed here, I see nothing that would cause the RC to > be set to 12. Check dsmsched.log and dsmerror.log for other messages that > might indicate a problem. There has to be some error message there > (unrelated to skipped files) that is triggering the RC 12. > > Best regards, > > Andy Raibeck > IBM Software Group > Tivoli Storage Manager Client Product Development > Level 3 Team Lead > Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS > Internet e-mail: stor...@us.ibm.com > > IBM Tivoli Storage Man
Re: ANS1417W Protected system state file 'C:\Windows\System32\wuauclt.exe' is backed up to the drive file space, not system state file space.
Yes, so make sure you are checking all messages between the time the backup started and occurrence of the ANS5283E, I would think there should be something there indicating an issue. Also note that the ANS1959I message (from the output below) also implies that the previous system state backup was unsuccessful, so maybe there is a problem with that, and system state backup is not completing. Maybe a problem creating the VSS snapshot. Also, did you look up the flash I mentioned the other day? You most definitely want to take the recommended action described in that flash (fix the registry entry, reboot) to eliminate those ANS1417W messages. This would seem to be a different issue, though, than what triggers the ANS5283E message, as the ANS1417W issue is insufficient to cause the system state backup to fail. Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager "ADSM: Dist Stor Manager" wrote on 2011-04-08 10:45:09: > From: "Hughes, Timothy" > To: ADSM-L@vm.marist.edu > Date: 2011-04-08 10:47 > Subject: Re: ANS1417W Protected system state file 'C:\Windows > \System32\wuauclt.exe' is backed up to the drive file space, not > system state file space. > Sent by: "ADSM: Dist Stor Manager" > > Thanks Andy, > . > Yes..the backup started around midnight > > > Regards > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On > Behalf Of Andrew Raibeck > Sent: Friday, April 08, 2011 9:20 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: ANS1417W Protected system state file 'C:\Windows > \System32\wuauclt.exe' is backed up to the drive file space, not > system state file space. > > Hi Timothy, yes, the ANS5283E would trigger the rc 12. The next step would > be to review the dsmerror.log for messages between the time the backup > started (around midnight?) and 00:01:42 when ANS5283E was issued to see if > there are further details about the error. > > Best regards, > > Andy Raibeck > IBM Software Group > Tivoli Storage Manager Client Product Development > Level 3 Team Lead > Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS > Internet e-mail: stor...@us.ibm.com > > IBM Tivoli Storage Manager support web page: > http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/ > Tivoli_Storage_Manager > > "ADSM: Dist Stor Manager" wrote on 2011-04-07 > 09:49:57: > > > From: "Hughes, Timothy" > > To: ADSM-L@vm.marist.edu > > Date: 2011-04-07 10:04 > > Subject: Re: ANS1417W Protected system state file 'C:\Windows > > \System32\wuauclt.exe' is backed up to the drive file space, not > > system state file space. > > Sent by: "ADSM: Dist Stor Manager" > > > > Andy, > > > > I looked further as you suggested and found the problem I think? > > Notice the last message "ANS5283E the operation was unsuccessful". > > Though still not quite sure exactly causing that unsuccessful operation. > > > > > > > > 4/07/2011 00:01:42 ANS1959I Removing previous incomplete group > > '\System State\0\SystemState' Id:0-75703620 > > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'ASR' > > using shadow copy. > > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'This > > is the path to the boot BCD store and the boot managers. > > All the files in this directory need to be backed up.' using shadow copy. > > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'Select > > this volume (C:) if it is a critical volume. > > Critical volumes are those which ASR must restore.' using shadow copy. > > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'Select > > to include disk #0 (of signature 0xac61e698) for ASR restore.' using > > shadow copy. > > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'Select > > to include disk #1 (of signature 0x1de944bd) for ASR restore.' using > > shadow copy. > > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'Select > > to include disk #2 (of signature 0xf01ed94c) for ASR restore.' using > > shadow copy. > > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'Select > > to include disk #6 (of signature 0x7581cf48) for ASR restore.' using > > shadow copy. > > 04/07/2011 00:01:42 Backing up object 'ASR Writer' component 'Select > > to include disk #8 (of signature 0xad94f4eb) for ASR restore.' using > > shadow copy. > > 04/07/2011 00:01:42 Backing up object 'COM+ REGDB Writer' component > > 'COM+ REGDB' using shadow copy. > > 04/07/2011 00:01:42 Backing up object 'Registry Writer' component > > 'Registry' using shadow copy. > > 04/07/2011 00:01:42 Backing up object 'Cluster Database' component > > 'ClusterDatabase' using shadow copy. > > 04/07/2011 00:01:42 Backing up object 'IIS Config Writer' component > > 'IISCON
