Re: How to delete Volhistory...
Try audit library X checklabel=barcode from the library client. That worked for me. Maria Ilieva On Fri, Jan 16, 2009 at 8:14 AM, KIRAN-SYSTEMS ki...@dqentertainment.com wrote: I am using the below command to delete volhis of a library client server from library manager server Del volhis vol=volume name force=yes -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Steven Harris Sent: Friday, January 16, 2009 11:24 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] How to delete Volhistory... We need detail Kiran, if we are to help. Please post the command you are using and the output when it doesn't work. also the output of a select * from volhistory where volume_name='XYZ000L3' - with your volume of interest substituted Thanks Steve Steven Harris TSM Administrator, Sydney Australia KIRAN-SYSTEMS ki...@dqentertai NMENT.COM To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager ads...@vm.marist Subject .EDU Re: [ADSM-L] How to delete Volhistory... 16/01/2009 04:12 PM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU The below command is not working for me.Iam using TSM Server 5.5.0 -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Robben Leaf Sent: Friday, January 09, 2009 1:02 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] How to delete Volhistory... Not entirely true. The product doesn't provide a DOCUMENTED way to do this. There are some undocumented parameters for the DELETE VOLHIST command. Specifically, you can add vol=VOLNAME force=yes to the command to remove the volume forcibly from the volhistory. We have found this command necessary when our library manager thinks another TSM server instance still owns a tape, when that instance has forgotten all about it. Robben Leaf From: Richard Sims r...@bu.edu To: ADSM-L@VM.MARIST.EDU Date: 01/08/2009 06:14 AM Subject: Re: [ADSM-L] How to delete Volhistory... Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU On Jan 8, 2009, at 12:27 AM, KIRAN-SYSTEMS wrote: Please let me know how to delete volume history of a particular Volume. The product does not provide a way to do this. Richard Sims U.S. BANCORP made the following annotations - Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. - Disclaimer: This email message (including attachments if any) may contain privileged, proprietary, confidential information, which may be exempt from any kind of disclosure whatsoever and is intended solely for the use of addressee (s). If you are not the intended recipient, kindly inform us by return e-mail and also kindly disregard the contents of the e-mail, delete the original message and destroy any copies thereof immediately. You are notified that any dissemination, distribution or copying of this communication is strictly prohibited unless approved by the sender. DQ Entertainment (DQE) has taken every reasonable precaution to minimize the risk of transmission of computer viruses with this e-mail; DQE is not liable for any damage you may sustain as a result of any virus in this e-mail. DQE shall not be liable for the views expressed in the e-mail. DQE reserves the right to monitor and review the content of all messages sent to or from this e-mail address Disclaimer: This email message (including attachments if any) may contain privileged, proprietary, confidential information, which may be exempt from any kind of disclosure whatsoever and is intended solely for the use of addressee (s). If you are not the intended recipient, kindly inform us by return e-mail and also kindly disregard the contents of the e-mail, delete the original message and destroy any copies thereof immediately. You are notified that any dissemination, distribution or copying of this
Re: Inactive Version
you may also reduce it to filespaces with : select count(*) from backups where state='INACTIVE_VERSION' and filespace_name='YOUR_FILESPACENAME' John Bremer jbre...@lanl.gov Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 16/01/2009 00:16 Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] Inactive Version select count(*) from backups where state='INACTIVE_VERSION' and node_name='YOUR_NODENAME' warning that trolling through the backups table can be very time consuming and expensive. John At 03:33 PM 1/15/2009, you wrote: Hello Everyone, Is there a select statement that will tell me how many active and inactive versions of files are on the nodes that are backing up. Thank you James Lepre Senior Server Specialist Solix, Inc. 100 S. Jefferson Road Whippany, NJ 07981 Phone: 973-581-5362 Cell: 973-223-1921 --- Confidentiality Notice: The information in this e-mail and any attachments thereto is intended for the named recipient(s) only. This e-mail, including any attachments, may contain information that is privileged and confidential and subject to legal restrictions and penalties regarding its unauthorized disclosure or other use. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action or inaction in reliance on the contents of this e-mail and any of its attachments is STRICTLY PROHIBITED. If you have received this e-mail in error, please immediately notify the sender via return e-mail; delete this e-mail and all attachments from your e-mail system and your computer system and network; and destroy any paper copies you may have in your possession. Thank you for your cooperation.
Re: 2 Windows 2003 clients with huge # of files consistently failing
Basically the app is recording all calls into our customer service reps (CSR) via WAV and AVI (for screen activity). The files are all very small but there are alot of them and because there are about 100 CSRs, they create a new directory for each call. As an example, on Jan 14 2009, there were 592 AVI and 592 WAV files but they live in in 4043 directories. Ridiculous! Unfortunately as per regulations, we need to keep the call data. I've contact Verint (maker of Ultra, the app) to see if they have alternatives to how they're data is stored. I can't imagine ever having to restore this server, ever. I'll go back and start researching image backups again, although I couldn't get them to work the first time. It backed up about 12G and then just hung and never progressed any further. No errors anywhere I looked (actlog,event viewer,tsmerror.log etc). I also thought about possibly using Tivoli Continuos Data Protection (CDP). Think that is an option? Thanks for all your help and ideas, John ANR0481W Session 16603 for node SERVERNAME (WinNT) terminated - client did not respond within 9000 seconds. (SESSION: 16603) If TSM is struggling to get through the directories, then applications associated with the data may be suffering the same problem. This may be the result of indifferent directory layout (far too many files in directories) or disk hardware issue or contention or file system issue (where chkdsk or equivalent might be run). The hardware may simply be underpowered for the amount of data involved (e.g., 5400 rpm disks or perhaps older ATA pathing). Or the file system type may be an inefficient choice. Large-scale data deployments cry out for a knowledgeable data architect in order to be successful and to scale - and that skill is often absent. The owners of the data should be strongly advised to regard the backup problem as a proportional indication of how very painful a file- oriented restoral would be, where reconstructing Windows directory entries is notoriously time-consuming. Richard Sims I have two separate Windows 2003 boxes both running running v5.5.1.10 client that are both failing their incrementals every night. Both of these boxes have hundreds of thousand of files all spread into multiple directories. In fact, each day, a new directory is created and then multiple subdirectories are created under it and thousand of files in each of those subdirectories. The reason I say this is because I don't think it is a candidate for multiple virtual nodes because of the new directories that are created every day. I do have journaling turned on although it doesn't seem to help with the large number of files either as when I run an incremental manually,it takes forever and never seems to finish. are you sure that the journal is running and has enough space? In these cases, having the journals on a separate filesystem might be a very good idea. I have the feeling that there is not enough space for the TSM journal database... I thought about doing image backups of the drive where the thousands of files live but when I tried it, it backed up about 14g and then just hung and never continued. I had to cancel it after waiting for an hour or so. and to what type of storage do these images go? I'd think that in case of an image backup you'd want a management class that makes them go directly to tape. My guess is that these were going to disk volumes? What is my best strategy for dealing with these two boxes that are generating thousands of new files in new directories every day? The huge number of objects in the TSM DB are starting to cause quite a few problems with daily processing also as expiration is running longer and longer since I think it is choking on the number of objects. I'd say that image backups are a good idea in cases of very active filesystems. Filesystems on windows with huge numbers of files are always a cause of problems, not only with TSM. And to make it even weirder, they both fail incrementals at night and the only error I can find is: ANR0481W Session 16603 for node SERVERNAME (WinNT) terminated - client did not respond within 9000 seconds. (SESSION: 16603) meaning that indeed the client is indeed choking on the size of the directories. I'm starting to think that TSM is just not the backup solution for either of these boxes. I'm also thinking that if you have a piece of software creating 1000's of files per day in a filesystem, that this is a very big workload. I'm very sure that with VSS snapshots and image backups, you are on the right track and no other product could do a better job of backing up these filesystems.
Re: 2 Windows 2003 clients with huge # of files consistently failing
John, Perhaps you could get creative here... Assuming there is a way of grouping files by date... Let's say all files are saved to: D:\20090114\... D:\20090115\... D:\20090116\... Etc.. You could at the cost of some disk space do the following: 1. Run a batch/script before the backup window which tars/zips that day's files and saves them to some backup directory, and also cleans up old tars/zips in the backup directory 2. Exclude the directories where your files reside 2. Let the backup run and backup the backup directory Kind of treat it like you would dumping a db to a flat file so it can be backed up. Then the restore will be such that you restore the backup directory and then have an additional step to unzip/untar. Hope this helps to give you another way of looking at the problem. Justin -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of John C Dury Sent: Friday, January 16, 2009 8:45 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 2 Windows 2003 clients with huge # of files consistently failing Basically the app is recording all calls into our customer service reps (CSR) via WAV and AVI (for screen activity). The files are all very small but there are alot of them and because there are about 100 CSRs, they create a new directory for each call. As an example, on Jan 14 2009, there were 592 AVI and 592 WAV files but they live in in 4043 directories. Ridiculous! Unfortunately as per regulations, we need to keep the call data. I've contact Verint (maker of Ultra, the app) to see if they have alternatives to how they're data is stored. I can't imagine ever having to restore this server, ever. I'll go back and start researching image backups again, although I couldn't get them to work the first time. It backed up about 12G and then just hung and never progressed any further. No errors anywhere I looked (actlog,event viewer,tsmerror.log etc). I also thought about possibly using Tivoli Continuos Data Protection (CDP). Think that is an option? Thanks for all your help and ideas, John ANR0481W Session 16603 for node SERVERNAME (WinNT) terminated - client did not respond within 9000 seconds. (SESSION: 16603) If TSM is struggling to get through the directories, then applications associated with the data may be suffering the same problem. This may be the result of indifferent directory layout (far too many files in directories) or disk hardware issue or contention or file system issue (where chkdsk or equivalent might be run). The hardware may simply be underpowered for the amount of data involved (e.g., 5400 rpm disks or perhaps older ATA pathing). Or the file system type may be an inefficient choice. Large-scale data deployments cry out for a knowledgeable data architect in order to be successful and to scale - and that skill is often absent. The owners of the data should be strongly advised to regard the backup problem as a proportional indication of how very painful a file- oriented restoral would be, where reconstructing Windows directory entries is notoriously time-consuming. Richard Sims I have two separate Windows 2003 boxes both running running v5.5.1.10 client that are both failing their incrementals every night. Both of these boxes have hundreds of thousand of files all spread into multiple directories. In fact, each day, a new directory is created and then multiple subdirectories are created under it and thousand of files in each of those subdirectories. The reason I say this is because I don't think it is a candidate for multiple virtual nodes because of the new directories that are created every day. I do have journaling turned on although it doesn't seem to help with the large number of files either as when I run an incremental manually,it takes forever and never seems to finish. are you sure that the journal is running and has enough space? In these cases, having the journals on a separate filesystem might be a very good idea. I have the feeling that there is not enough space for the TSM journal database... I thought about doing image backups of the drive where the thousands of files live but when I tried it, it backed up about 14g and then just hung and never continued. I had to cancel it after waiting for an hour or so. and to what type of storage do these images go? I'd think that in case of an image backup you'd want a management class that makes them go directly to tape. My guess is that these were going to disk volumes? What is my best strategy for dealing with these two boxes that are generating thousands of new files in new directories every day? The huge number of objects in the TSM DB are starting to cause quite a few problems with daily processing also as expiration is running longer and longer since I think it is choking on the number of objects. I'd say that image backups are a good idea in cases of very active filesystems. Filesystems on windows with huge numbers of files are always
Re: 2 Windows 2003 clients with huge # of files consistently failing
John - In a logging-files environment such as you cite, where the data is largely write-only and historic, a hierarchical storage approach would be a more reasonable thing, where data over like a week old would migrate to a cheaper, lower level mass storage area whose entirety would not have to be regularly scanned for backup. (It's easy to incite an Incremental backup on just the data identified by the migration task.) Recent data would be held in a higher level area of much smaller size, whose performance would meet the needs of the application and be much more reasonable to scan for backup. We TSM administrators often end up the victims of data architectures which weren't thought out for all aspects of their management (in our case, Backup and Restore), and we aren't in a position to re-engineer the layout. If the new data is in some way identifiable by name or timestamp in the directory name, or by identification in some application logging, it might be possible to focus Incremental backups on that subset of the file system, rather than Incremental over the whole thing. Beyond that, Image or CDP backups may be worth pursuing further. Also have the organization consider whether just mirroring will meet recovery needs: in some implementations, conventional file backups may not be necessary. Richard Sims
Re: 2 Windows 2003 clients with huge # of files consistently failing
I guess I have different questions than I have already seen. How is the memory usage on the node? Is it 32 or 64 bit? Is the agent hanging or working during the 9000 seconds? We have 2 systems that back 10M+ objects in an equally crazy number of directories and we have not seen the error you have. 1 machine is 32 bit and is using memory efficient disk cache and the other one is 64 bit and does not needs memory help. Both have static file systems during the backup. (That is another story.) We have seen a similar error to yours on 2003 servers with SP2. Take a look at Microsoft KB 948496 if the server is running SP2. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of John C Dury Sent: Thursday, January 15, 2009 8:27 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] 2 Windows 2003 clients with huge # of files consistently failing I have two separate Windows 2003 boxes both running running v5.5.1.10 client that are both failing their incrementals every night. Both of these boxes have hundreds of thousand of files all spread into multiple directories. In fact, each day, a new directory is created and then multiple subdirectories are created under it and thousand of files in each of those subdirectories. The reason I say this is because I don't think it is a candidate for multiple virtual nodes because of the new directories that are created every day. I do have journaling turned on although it doesn't seem to help with the large number of files either as when I run an incremental manually,it takes forever and never seems to finish. I thought about doing image backups of the drive where the thousands of files live but when I tried it, it backed up about 14g and then just hung and never continued. I had to cancel it after waiting for an hour or so. What is my best strategy for dealing with these two boxes that are generating thousands of new files in new directories every day? The huge number of objects in the TSM DB are starting to cause quite a few problems with daily processing also as expiration is running longer and longer since I think it is choking on the number of objects. And to make it even weirder, they both fail incrementals at night and the only error I can find is: ANR0481W Session 16603 for node SERVERNAME (WinNT) terminated - client did not respond within 9000 seconds. (SESSION: 16603) I'm starting to think that TSM is just not the backup solution for either of these boxes. 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: How to figure collocation overhead
Don't forget collocation by group. All of our nodes belong to one group or another and we can then be pretty sure that collocation will do what we need. Mostly, our tape pools are collocated by group. Some nodes are in a group all by themselves and some (e.g. workstations) have many nodes in their group. We only use collocation by filespace if it is really needed for the largest nodes. Bob -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Sam Rawlins Sent: Thursday, January 15, 2009 2:20 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] How to figure collocation overhead Hi Bill, I like Wanda's point. MAXSCRatch is the best way to control tape usage. You can probably write a fun select to see how many nodes have data on the average tape. In Wanda's example, there are about 2 nodes per tape. If you see that that number gets too high, you can increase MAXSCRatch. On Thu, Jan 15, 2009 at 11:53 AM, Wanda Prather wanda.prat...@jasi.comwrote: Collocation consumes as much of the library as you tell it to. When you set MAXSCRATCH on a storage pool, TSM will confine the pool to that number of tapes. If you have less tapes available than you have clients, you get a do the best you can collocation. There are plenty of sites who have more clients than slots in their library. If you have 100 clients and set MAXSCRATCH for the pool to 50 tapes, TSM will put each client on a different tape until it hits 50, then it will double up. You still get a decent amount of collocation; it's a lot faster for a restore to skip over another clients data on the same tape, than it is to rewind, dismount, mount, and reposition to a different tape. What you have to remember if you are collocating, is that you have to check your pools periodically and reevaluate maxscratch for the pool. If your total amount of data is growing, you will need to up the maxscratch periodically so that you maintain enough available free tapes in the pool to provide a reasonable level of collocation. W On Thu, Jan 15, 2009 at 1:34 PM, Evans, Bill bev...@fhcrc.org wrote: Is there a guide or rule of thumb for determining what collocation will do to library space? It is being considered for improving restore speeds. I'm backing up 80TB in 30 volumes(filespaces) on a solaris server. Currently there is no collocation set, all data goes to a long-term management class, single onsite and off-site tape pools, data churn averages 1TB/night. Using a 650 slot L700 library, LTO3, TSM 5.5, AIX 5.3. The library is 80% full, so, I'm concerned that starting collocation for the volumes will consume the rest of the library. Each filespace collocation may end up with one tape not full (or 30 in this case). Thanks, Bill Evans Research Computing Support FRED HUTCHINSON CANCER RESEARCH CENTER -- Sam Rawlins This electronic transmission and any documents accompanying this electronic transmission contain confidential information belonging to the sender. This information may be legally privileged. The information is intended only for the use of the individual or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on or regarding the contents of this electronically transmitted information is strictly prohibited.
Re: How to delete Volhistory...
I am not sure which parms are absolutely required, but this is the command I used to get rid of an old entry. DELETE VOLHISTORY type=backupset volume=D:\88894302.OST force=yes todate=today Bob. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of KIRAN-SYSTEMS Sent: Friday, January 16, 2009 12:15 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] How to delete Volhistory... I am using the below command to delete volhis of a library client server from library manager server Del volhis vol=volume name force=yes -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Steven Harris Sent: Friday, January 16, 2009 11:24 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] How to delete Volhistory... We need detail Kiran, if we are to help. Please post the command you are using and the output when it doesn't work. also the output of a select * from volhistory where volume_name='XYZ000L3' - with your volume of interest substituted Thanks Steve Steven Harris TSM Administrator, Sydney Australia KIRAN-SYSTEMS ki...@dqentertai NMENT.COM To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager ads...@vm.marist Subject .EDU Re: [ADSM-L] How to delete Volhistory... 16/01/2009 04:12 PM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU The below command is not working for me.Iam using TSM Server 5.5.0 -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Robben Leaf Sent: Friday, January 09, 2009 1:02 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] How to delete Volhistory... Not entirely true. The product doesn't provide a DOCUMENTED way to do this. There are some undocumented parameters for the DELETE VOLHIST command. Specifically, you can add vol=VOLNAME force=yes to the command to remove the volume forcibly from the volhistory. We have found this command necessary when our library manager thinks another TSM server instance still owns a tape, when that instance has forgotten all about it. Robben Leaf From: Richard Sims r...@bu.edu To: ADSM-L@VM.MARIST.EDU Date: 01/08/2009 06:14 AM Subject: Re: [ADSM-L] How to delete Volhistory... Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU On Jan 8, 2009, at 12:27 AM, KIRAN-SYSTEMS wrote: Please let me know how to delete volume history of a particular Volume. The product does not provide a way to do this. Richard Sims U.S. BANCORP made the following annotations - Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. - Disclaimer: This email message (including attachments if any) may contain privileged, proprietary, confidential information, which may be exempt from any kind of disclosure whatsoever and is intended solely for the use of addressee (s). If you are not the intended recipient, kindly inform us by return e-mail and also kindly disregard the contents of the e-mail, delete the original message and destroy any copies thereof immediately. You are notified that any dissemination, distribution or copying of this communication is strictly prohibited unless approved by the sender. DQ Entertainment (DQE) has taken every reasonable precaution to minimize the risk of transmission of computer viruses with this e-mail; DQE is not liable for any damage you may sustain as a result of any virus in this e-mail. DQE shall not be liable for the views expressed in the e-mail. DQE reserves the right to monitor and review the content of all messages sent to or from this e-mail address Disclaimer: This email message (including attachments if any) may contain privileged, proprietary, confidential information, which may be exempt from any kind of disclosure whatsoever and is intended solely for the use of addressee (s). If you are not the intended recipient, kindly inform us by return e-mail and also kindly disregard the contents of the e-mail,
Windows 2003 Clients failing all of sudden after TSM server upgrade
Hi all, For the past few days an abnormal number of Windows Clients have been failing with the following error (s). I have noticed that most if not all are windows 2003 clients with TSM client 5.5. It has been happening on some clients every day and others off and on. Also, these errors seemed to start after we upgraded our TSM Servers to 5.5.2. However it’s only occurring on two TSM Servers with Windows clients we have 2 other servers that have a bunch of Windows 2003 clients and they do not have this issue? I am not sure which error is the problem or is it a combination? Why would these occur suddenly after and upgrade to 5.5.2 TSM server? ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-896708239 01/13/2009 00:13:48 ANS1327W The snapshot operation for 'SNJCUS\SystemState\NULL\System State\SystemState' failed with error code: 51 ANS1351E Session rejected: All server sessions are currently in use or in some cases 01/14/2009 00:15:39 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/14/2009 00:15:39 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. Thanks for any help or suggestions! Sorry for the long list 01/12/2009 00:11:13 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/13/2009 00:10:58 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-896708239 01/13/2009 00:13:48 ANS1327W The snapshot operation for 'SNJCUS\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/13/2009 00:13:48 ANS1228E Sending of object 'SNJCUS\SystemState\NULL\System State\SystemState' failed 01/13/2009 00:13:48 ANS1351E Session rejected: All server sessions are currently in use 01/13/2009 00:13:48 ANS1375E The snapshot operation failed. 01/13/2009 00:13:48 ANS1351E Session rejected: All server sessions are currently in use 01/13/2009 00:13:48 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 09/2009 07:58:19 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/09/2009 07:58:19 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/12/2009 00:18:08 ANS1327W The snapshot operation for 'ADABAS1\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/12/2009 00:18:08 ANS1228E Sending of object 'ADABAS1\SystemState\NULL\System State\SystemState' failed 01/12/2009 00:18:08 ANS1351E Session rejected: All server sessions are currently in use 01/12/2009 00:18:08 ANS1375E The snapshot operation failed. 01/11/2009 00:47:20 ANS1327W The snapshot operation for 'SIFT22\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/11/2009 00:47:20 ANS1228E Sending of object 'SIFT22\SystemState\NULL\System State\SystemState' failed 01/11/2009 00:47:20 ANS1351E Session rejected: All server sessions are currently in use 01/11/2009 00:47:20 ANS1375E The snapshot operation failed. 01/11/2009 00:47:20 ANS1351E Session rejected: All server sessions are currently in use 01/11/2009 00:47:20 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/12/2009 00:23:03 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/13/2009 00:19:07 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-896738674 01/13/2009 00:20:27 ANS1327W The snapshot operation for 'SNC180\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/13/2009 00:20:27 ANS1228E Sending of object 'SNC180\SystemState\NULL\System State\SystemState' failed 01/13/2009 00:20:27 ANS1351E Session rejected: All server sessions are currently in use 01/13/2009 00:20:27 ANS1375E The snapshot operation failed. 01/13/2009 00:20:27 ANS1351E Session rejected: All server sessions are currently in use 01/13/2009 00:20:27 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/14/2009 00:20:45 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-897022474 Thanks, 01/15/2009 01:52:31 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/15/2009 01:52:31 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/15/2009 00:17:00 ANS1327W The snapshot operation for 'Nownty\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/15/2009 00:17:00 ANS1228E Sending of object 'Nownty\SystemState\NULL\System State\SystemState' failed 01/15/2009 00:17:00 ANS1375E The snapshot operation failed. 1/15/2009 00:47:06 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-897704807 01/15/2009 00:47:42 ANS1327W The snapshot operation for 'COISI4\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/15/2009 00:47:42 ANS1228E Sending of object 'COISI4\SystemState\NULL\System State\SystemState' failed 01/15/2009 00:47:42 ANS1351E Session rejected: All server sessions are currently in use 01/15/2009
SQL Select Stement Subtracting Time from Summary Table
Is there a way to have a select statement perform much like the function of the q act begint=-8 ? I'm writing a SQL query to determine OS Backups are backing up DB files systems by doing a select from the summary table, with nodename, sched name, bytes recvd 50GB etc, but need to find a way to say only look back x # of Hours ... I've even checked my SAL in 21Min book and cant find anything... Hope all is well with everyone and good luck in this new challenging year! Regards, Charles This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
Re: How to figure collocation overhead
Thanks for all the advice. Now to go try some things. I'll update the list when I have some data. Thank you, Bill Evans Research Computing Support FRED HUTCHINSON CANCER RESEARCH CENTER -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Bob Levad Sent: Friday, January 16, 2009 7:52 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] How to figure collocation overhead Don't forget collocation by group. All of our nodes belong to one group or another and we can then be pretty sure that collocation will do what we need. Mostly, our tape pools are collocated by group. Some nodes are in a group all by themselves and some (e.g. workstations) have many nodes in their group. We only use collocation by filespace if it is really needed for the largest nodes. Bob -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Sam Rawlins Sent: Thursday, January 15, 2009 2:20 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] How to figure collocation overhead Hi Bill, I like Wanda's point. MAXSCRatch is the best way to control tape usage. You can probably write a fun select to see how many nodes have data on the average tape. In Wanda's example, there are about 2 nodes per tape. If you see that that number gets too high, you can increase MAXSCRatch. On Thu, Jan 15, 2009 at 11:53 AM, Wanda Prather wanda.prat...@jasi.comwrote: Collocation consumes as much of the library as you tell it to. When you set MAXSCRATCH on a storage pool, TSM will confine the pool to that number of tapes. If you have less tapes available than you have clients, you get a do the best you can collocation. There are plenty of sites who have more clients than slots in their library. If you have 100 clients and set MAXSCRATCH for the pool to 50 tapes, TSM will put each client on a different tape until it hits 50, then it will double up. You still get a decent amount of collocation; it's a lot faster for a restore to skip over another clients data on the same tape, than it is to rewind, dismount, mount, and reposition to a different tape. What you have to remember if you are collocating, is that you have to check your pools periodically and reevaluate maxscratch for the pool. If your total amount of data is growing, you will need to up the maxscratch periodically so that you maintain enough available free tapes in the pool to provide a reasonable level of collocation. W On Thu, Jan 15, 2009 at 1:34 PM, Evans, Bill bev...@fhcrc.org wrote: Is there a guide or rule of thumb for determining what collocation will do to library space? It is being considered for improving restore speeds. I'm backing up 80TB in 30 volumes(filespaces) on a solaris server. Currently there is no collocation set, all data goes to a long-term management class, single onsite and off-site tape pools, data churn averages 1TB/night. Using a 650 slot L700 library, LTO3, TSM 5.5, AIX 5.3. The library is 80% full, so, I'm concerned that starting collocation for the volumes will consume the rest of the library. Each filespace collocation may end up with one tape not full (or 30 in this case). Thanks, Bill Evans Research Computing Support FRED HUTCHINSON CANCER RESEARCH CENTER -- Sam Rawlins This electronic transmission and any documents accompanying this electronic transmission contain confidential information belonging to the sender. This information may be legally privileged. The information is intended only for the use of the individual or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on or regarding the contents of this electronically transmitted information is strictly prohibited.
Re: Windows 2003 Clients failing all of sudden after TSM server upgrade
Perhaps you are reaching your max session limit? Look at the help for the following commands: Q STATUS (look for Maximum Sessions) SET MAXSESSIONS SET MAXSCHEDSESSIONS Regards, Shawn Shawn Drew Internet timothy.hug...@oit.state.nj.us Sent by: ADSM-L@VM.MARIST.EDU 01/16/2009 10:59 AM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] Windows 2003 Clients failing all of sudden after TSM server upgrade Hi all, For the past few days an abnormal number of Windows Clients have been failing with the following error (s). I have noticed that most if not all are windows 2003 clients with TSM client 5.5. It has been happening on some clients every day and others off and on. Also, these errors seemed to start after we upgraded our TSM Servers to 5.5.2. However it’s only occurring on two TSM Servers with Windows clients we have 2 other servers that have a bunch of Windows 2003 clients and they do not have this issue? I am not sure which error is the problem or is it a combination? Why would these occur suddenly after and upgrade to 5.5.2 TSM server? ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-896708239 01/13/2009 00:13:48 ANS1327W The snapshot operation for 'SNJCUS\SystemState\NULL\System State\SystemState' failed with error code: 51 ANS1351E Session rejected: All server sessions are currently in use or in some cases 01/14/2009 00:15:39 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/14/2009 00:15:39 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. Thanks for any help or suggestions! Sorry for the long list 01/12/2009 00:11:13 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/13/2009 00:10:58 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-896708239 01/13/2009 00:13:48 ANS1327W The snapshot operation for 'SNJCUS\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/13/2009 00:13:48 ANS1228E Sending of object 'SNJCUS\SystemState\NULL\System State\SystemState' failed 01/13/2009 00:13:48 ANS1351E Session rejected: All server sessions are currently in use 01/13/2009 00:13:48 ANS1375E The snapshot operation failed. 01/13/2009 00:13:48 ANS1351E Session rejected: All server sessions are currently in use 01/13/2009 00:13:48 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 09/2009 07:58:19 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/09/2009 07:58:19 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/12/2009 00:18:08 ANS1327W The snapshot operation for 'ADABAS1\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/12/2009 00:18:08 ANS1228E Sending of object 'ADABAS1\SystemState\NULL\System State\SystemState' failed 01/12/2009 00:18:08 ANS1351E Session rejected: All server sessions are currently in use 01/12/2009 00:18:08 ANS1375E The snapshot operation failed. 01/11/2009 00:47:20 ANS1327W The snapshot operation for 'SIFT22\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/11/2009 00:47:20 ANS1228E Sending of object 'SIFT22\SystemState\NULL\System State\SystemState' failed 01/11/2009 00:47:20 ANS1351E Session rejected: All server sessions are currently in use 01/11/2009 00:47:20 ANS1375E The snapshot operation failed. 01/11/2009 00:47:20 ANS1351E Session rejected: All server sessions are currently in use 01/11/2009 00:47:20 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/12/2009 00:23:03 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/13/2009 00:19:07 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-896738674 01/13/2009 00:20:27 ANS1327W The snapshot operation for 'SNC180\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/13/2009 00:20:27 ANS1228E Sending of object 'SNC180\SystemState\NULL\System State\SystemState' failed 01/13/2009 00:20:27 ANS1351E Session rejected: All server sessions are currently in use 01/13/2009 00:20:27 ANS1375E The snapshot operation failed. 01/13/2009 00:20:27 ANS1351E Session rejected: All server sessions are currently in use 01/13/2009 00:20:27 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/14/2009 00:20:45 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-897022474 Thanks, 01/15/2009 01:52:31 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/15/2009 01:52:31 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/15/2009 00:17:00 ANS1327W The snapshot operation for 'Nownty\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/15/2009 00:17:00 ANS1228E Sending of object 'Nownty\SystemState\NULL\System State\SystemState' failed 01/15/2009 00:17:00 ANS1375E The snapshot operation failed. 1/15/2009 00:47:06 ANS1959W
Re: SQL Select Stement Subtracting Time from Summary Table
Thanks Richard for pointing out the ADSM Faq - for subtracting time ... Our issue is we have OS backup backing up DB file systems via the OS backup schedule. (We have a separate node dbss0001 for the OS backup and a dbss0001-ORA for the RMAN backups. So we are going to use the query to Auto Ticket the Unix team for include Exclude challenges --- SELECT START_TIME, END_TIME, SCHEDULE_NAME, ENTITY, BYTES FROM SUMMARY WHERE ACTIVITY='BACKUP' AND (CURRENT_TIMESTAMP-END_TIME)HOURS = 16 HOURS and (SCHEDULE_NAME Is Not Null) and (BYTES = 600) -Original Message- From: Hart, Charles A Sent: Friday, January 16, 2009 10:04 AM To: ADSM-L@VM.MARIST.EDU Subject: SQL Select Stement Subtracting Time from Summary Table Is there a way to have a select statement perform much like the function of the q act begint=-8 ? I'm writing a SQL query to determine OS Backups are backing up DB files systems by doing a select from the summary table, with nodename, sched name, bytes recvd 50GB etc, but need to find a way to say only look back x # of Hours ... I've even checked my SAL in 21Min book and cant find anything... Hope all is well with everyone and good luck in this new challenging year! Regards, Charles This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
Re: Windows 2003 Clients failing all of sudden after TSM server upgrade
Thanks Shawn! Maybe that's it? I am checking the TSM Server log and I see many of these type messages ANR0429W Session 8894 for node ZDNBURG (WinNT) refused - maximum server sessions (75) exceeded. I wonder If the updrade to TSM 5.5.2 changed the parameter? could that have happen? So far I can't find any of the above messages from prior to the upgrade. I did a Q status here are the results. Maximum Sessions: 75 Maximum Scheduled Sessions: 75 regards Tim Shawn Drew wrote: Perhaps you are reaching your max session limit? Look at the help for the following commands: Q STATUS (look for Maximum Sessions) SET MAXSESSIONS SET MAXSCHEDSESSIONS Regards, Shawn Shawn Drew Internet timothy.hug...@oit.state.nj.us Sent by: ADSM-L@VM.MARIST.EDU 01/16/2009 10:59 AM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] Windows 2003 Clients failing all of sudden after TSM server upgrade Hi all, For the past few days an abnormal number of Windows Clients have been failing with the following error (s). I have noticed that most if not all are windows 2003 clients with TSM client 5.5. It has been happening on some clients every day and others off and on. Also, these errors seemed to start after we upgraded our TSM Servers to 5.5.2. However it’s only occurring on two TSM Servers with Windows clients we have 2 other servers that have a bunch of Windows 2003 clients and they do not have this issue? I am not sure which error is the problem or is it a combination? Why would these occur suddenly after and upgrade to 5.5.2 TSM server? ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-896708239 01/13/2009 00:13:48 ANS1327W The snapshot operation for 'SNJCUS\SystemState\NULL\System State\SystemState' failed with error code: 51 ANS1351E Session rejected: All server sessions are currently in use or in some cases 01/14/2009 00:15:39 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/14/2009 00:15:39 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. Thanks for any help or suggestions! Sorry for the long list 01/12/2009 00:11:13 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/13/2009 00:10:58 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-896708239 01/13/2009 00:13:48 ANS1327W The snapshot operation for 'SNJCUS\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/13/2009 00:13:48 ANS1228E Sending of object 'SNJCUS\SystemState\NULL\System State\SystemState' failed 01/13/2009 00:13:48 ANS1351E Session rejected: All server sessions are currently in use 01/13/2009 00:13:48 ANS1375E The snapshot operation failed. 01/13/2009 00:13:48 ANS1351E Session rejected: All server sessions are currently in use 01/13/2009 00:13:48 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 09/2009 07:58:19 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/09/2009 07:58:19 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/12/2009 00:18:08 ANS1327W The snapshot operation for 'ADABAS1\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/12/2009 00:18:08 ANS1228E Sending of object 'ADABAS1\SystemState\NULL\System State\SystemState' failed 01/12/2009 00:18:08 ANS1351E Session rejected: All server sessions are currently in use 01/12/2009 00:18:08 ANS1375E The snapshot operation failed. 01/11/2009 00:47:20 ANS1327W The snapshot operation for 'SIFT22\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/11/2009 00:47:20 ANS1228E Sending of object 'SIFT22\SystemState\NULL\System State\SystemState' failed 01/11/2009 00:47:20 ANS1351E Session rejected: All server sessions are currently in use 01/11/2009 00:47:20 ANS1375E The snapshot operation failed. 01/11/2009 00:47:20 ANS1351E Session rejected: All server sessions are currently in use 01/11/2009 00:47:20 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/12/2009 00:23:03 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/13/2009 00:19:07 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-896738674 01/13/2009 00:20:27 ANS1327W The snapshot operation for 'SNC180\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/13/2009 00:20:27 ANS1228E Sending of object 'SNC180\SystemState\NULL\System State\SystemState' failed 01/13/2009 00:20:27 ANS1351E Session rejected: All server sessions are currently in use 01/13/2009 00:20:27 ANS1375E The snapshot operation failed. 01/13/2009 00:20:27 ANS1351E Session rejected: All server sessions are currently in use 01/13/2009 00:20:27 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/14/2009 00:20:45 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-897022474 Thanks, 01/15/2009 01:52:31
[Fwd: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade]
I see that Maximum setting is 100, but it seems we have it set to 100 already unless we have to re-set it from the command line? This setting determines the maximum percentage of allowed client sessions that can be used for scheduling sessions. Specify a number between 0 and 100. Maximum percent.100 Original Message Subject: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade Date: Fri, 16 Jan 2009 13:14:49 -0500 From: Timothy Hughes timothy.hug...@oit.state.nj.us To: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU References: of6df0a779.f79b6849-on85257540.005c416a-85257540.005c6...@americas.bnpparibas.com Thanks Shawn! Maybe that's it? I am checking the TSM Server log and I see many of these type messages ANR0429W Session 8894 for node ZDNBURG (WinNT) refused - maximum server sessions (75) exceeded. I wonder If the updrade to TSM 5.5.2 changed the parameter? could that have happen? So far I can't find any of the above messages from prior to the upgrade. I did a Q status here are the results. Maximum Sessions: 75 Maximum Scheduled Sessions: 75 regards Tim Shawn Drew wrote: Perhaps you are reaching your max session limit? Look at the help for the following commands: Q STATUS (look for Maximum Sessions) SET MAXSESSIONS SET MAXSCHEDSESSIONS Regards, Shawn Shawn Drew Internet timothy.hug...@oit.state.nj.us Sent by: ADSM-L@VM.MARIST.EDU 01/16/2009 10:59 AM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] Windows 2003 Clients failing all of sudden after TSM server upgrade Hi all, For the past few days an abnormal number of Windows Clients have been failing with the following error (s). I have noticed that most if not all are windows 2003 clients with TSM client 5.5. It has been happening on some clients every day and others off and on. Also, these errors seemed to start after we upgraded our TSM Servers to 5.5.2. However it’s only occurring on two TSM Servers with Windows clients we have 2 other servers that have a bunch of Windows 2003 clients and they do not have this issue? I am not sure which error is the problem or is it a combination? Why would these occur suddenly after and upgrade to 5.5.2 TSM server? ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-896708239 01/13/2009 00:13:48 ANS1327W The snapshot operation for 'SNJCUS\SystemState\NULL\System State\SystemState' failed with error code: 51 ANS1351E Session rejected: All server sessions are currently in use or in some cases 01/14/2009 00:15:39 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/14/2009 00:15:39 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. Thanks for any help or suggestions! Sorry for the long list 01/12/2009 00:11:13 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/13/2009 00:10:58 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-896708239 01/13/2009 00:13:48 ANS1327W The snapshot operation for 'SNJCUS\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/13/2009 00:13:48 ANS1228E Sending of object 'SNJCUS\SystemState\NULL\System State\SystemState' failed 01/13/2009 00:13:48 ANS1351E Session rejected: All server sessions are currently in use 01/13/2009 00:13:48 ANS1375E The snapshot operation failed. 01/13/2009 00:13:48 ANS1351E Session rejected: All server sessions are currently in use 01/13/2009 00:13:48 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 09/2009 07:58:19 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/09/2009 07:58:19 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/12/2009 00:18:08 ANS1327W The snapshot operation for 'ADABAS1\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/12/2009 00:18:08 ANS1228E Sending of object 'ADABAS1\SystemState\NULL\System State\SystemState' failed 01/12/2009 00:18:08 ANS1351E Session rejected: All server sessions are currently in use 01/12/2009 00:18:08 ANS1375E The snapshot operation failed. 01/11/2009 00:47:20 ANS1327W The snapshot operation for 'SIFT22\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/11/2009 00:47:20 ANS1228E Sending of object 'SIFT22\SystemState\NULL\System State\SystemState' failed 01/11/2009 00:47:20 ANS1351E Session rejected: All server sessions are currently in use 01/11/2009 00:47:20 ANS1375E The snapshot operation failed. 01/11/2009 00:47:20 ANS1351E Session rejected: All server sessions are currently in use 01/11/2009 00:47:20 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/12/2009 00:23:03 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/13/2009 00:19:07 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-896738674 01/13/2009 00:20:27
Re: [Fwd: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade]
The Max sched sessions is just a percentage of the max sessions. So if you increase the max sessions, it will increase the max sched sessions. I would keep the max sched sessions to the default, then just increase the max sessions. Hopefully that made sense! Regards, Shawn Shawn Drew Internet timothy.hug...@oit.state.nj.us Sent by: ADSM-L@VM.MARIST.EDU 01/16/2009 01:57 PM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] [Fwd: Re: Windows 2003 Clients failing all of sudden after TSM server upgrade] I see that Maximum setting is 100, but it seems we have it set to 100 already unless we have to re-set it from the command line? This setting determines the maximum percentage of allowed client sessions that can be used for scheduling sessions. Specify a number between 0 and 100. Maximum percent.100 Original Message Subject:Re: Windows 2003 Clients failing all of sudden after TSM server upgrade Date: Fri, 16 Jan 2009 13:14:49 -0500 From: Timothy Hughes timothy.hug...@oit.state.nj.us To: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU References: of6df0a779.f79b6849-on85257540.005c416a-85257540.005c6...@americas.bnpparibas.com Thanks Shawn! Maybe that's it? I am checking the TSM Server log and I see many of these type messages ANR0429W Session 8894 for node ZDNBURG (WinNT) refused - maximum server sessions (75) exceeded. I wonder If the updrade to TSM 5.5.2 changed the parameter? could that have happen? So far I can't find any of the above messages from prior to the upgrade. I did a Q status here are the results. Maximum Sessions: 75 Maximum Scheduled Sessions: 75 regards Tim Shawn Drew wrote: Perhaps you are reaching your max session limit? Look at the help for the following commands: Q STATUS (look for Maximum Sessions) SET MAXSESSIONS SET MAXSCHEDSESSIONS Regards, Shawn Shawn Drew Internet timothy.hug...@oit.state.nj.us Sent by: ADSM-L@VM.MARIST.EDU 01/16/2009 10:59 AM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] Windows 2003 Clients failing all of sudden after TSM server upgrade Hi all, For the past few days an abnormal number of Windows Clients have been failing with the following error (s). I have noticed that most if not all are windows 2003 clients with TSM client 5.5. It has been happening on some clients every day and others off and on. Also, these errors seemed to start after we upgraded our TSM Servers to 5.5.2. However it’s only occurring on two TSM Servers with Windows clients we have 2 other servers that have a bunch of Windows 2003 clients and they do not have this issue? I am not sure which error is the problem or is it a combination? Why would these occur suddenly after and upgrade to 5.5.2 TSM server? ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-896708239 01/13/2009 00:13:48 ANS1327W The snapshot operation for 'SNJCUS\SystemState\NULL\System State\SystemState' failed with error code: 51 ANS1351E Session rejected: All server sessions are currently in use or in some cases 01/14/2009 00:15:39 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/14/2009 00:15:39 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. Thanks for any help or suggestions! Sorry for the long list 01/12/2009 00:11:13 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/13/2009 00:10:58 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-896708239 01/13/2009 00:13:48 ANS1327W The snapshot operation for 'SNJCUS\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/13/2009 00:13:48 ANS1228E Sending of object 'SNJCUS\SystemState\NULL\System State\SystemState' failed 01/13/2009 00:13:48 ANS1351E Session rejected: All server sessions are currently in use 01/13/2009 00:13:48 ANS1375E The snapshot operation failed. 01/13/2009 00:13:48 ANS1351E Session rejected: All server sessions are currently in use 01/13/2009 00:13:48 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 09/2009 07:58:19 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 01/09/2009 07:58:19 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 01/12/2009 00:18:08 ANS1327W The snapshot operation for 'ADABAS1\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/12/2009 00:18:08 ANS1228E Sending of object 'ADABAS1\SystemState\NULL\System State\SystemState' failed 01/12/2009 00:18:08 ANS1351E Session rejected: All server sessions are currently in use 01/12/2009 00:18:08 ANS1375E The snapshot operation failed. 01/11/2009 00:47:20 ANS1327W The snapshot operation for 'SIFT22\SystemState\NULL\System State\SystemState' failed with error code: 51. 01/11/2009 00:47:20 ANS1228E Sending of object
Re: 2 Windows 2003 clients with huge # of files consistently failing
I also have 2 problem child's like these. I turn on journaling, but the journaling ran out of memory (virtual). My only other option was to turn on memory efficient disk cache method to get thru the memory issue with journaling. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of John C Dury Sent: Thursday, January 15, 2009 6:27 AM To: ADSM-L@VM.MARIST.EDU Subject: 2 Windows 2003 clients with huge # of files consistently failing I have two separate Windows 2003 boxes both running running v5.5.1.10 client that are both failing their incrementals every night. Both of these boxes have hundreds of thousand of files all spread into multiple directories. In fact, each day, a new directory is created and then multiple subdirectories are created under it and thousand of files in each of those subdirectories. The reason I say this is because I don't think it is a candidate for multiple virtual nodes because of the new directories that are created every day. I do have journaling turned on although it doesn't seem to help with the large number of files either as when I run an incremental manually,it takes forever and never seems to finish. I thought about doing image backups of the drive where the thousands of files live but when I tried it, it backed up about 14g and then just hung and never continued. I had to cancel it after waiting for an hour or so. What is my best strategy for dealing with these two boxes that are generating thousands of new files in new directories every day? The huge number of objects in the TSM DB are starting to cause quite a few problems with daily processing also as expiration is running longer and longer since I think it is choking on the number of objects. And to make it even weirder, they both fail incrementals at night and the only error I can find is: ANR0481W Session 16603 for node SERVERNAME (WinNT) terminated - client did not respond within 9000 seconds. (SESSION: 16603) I'm starting to think that TSM is just not the backup solution for either of these boxes.
