Re: reclamation no longer working
I'm doing a move data now. Or trying too. The process has been running for about 30 minutes with zero bytes moved. Nothing showing from a q request, nothing showing from a q mount. All drives online and plenty of mount points. Have you tried to use straight command in foreground mode move data volume w=y? What are the results? CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software. Please consider the environment before printing this Email.
Re: reclamation no longer working
I started a reclamation on that pool yesterday afternoon and it sat there for several hours before it finally started moving anything. I guess I got behind doing the reclamation. But that doesn't make any sense because the offsite pool and the onsite pool have the same settings and the same content. Only difference is that one goes off site. I use the same settings when I run reclamation on both pools but I run them at completely different times and the times don't overlap. When I run the onsite copypool script the process starts without delay. The same settings for the offsite copypool takes forever to actually kick off. I guess I'll need to keep a closer eye on things -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Allen S. Rout Sent: Thursday, May 06, 2010 2:17 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] reclamation no longer working On Thu, 6 May 2010 11:11:34 -0400, Tyree, David david.ty...@sgmc.org said: I've run the threshold up and down from a few percentage points up to 80-90% hoping something would change but no difference. I have plenty of scratch tapes and mount points. Try running one at 99% and _no_ time limit, and expect it to run for days. There's a huge amount of bookkeeping work TSM does at the outset. If you've gotten yourself stuck somewhere, and lots of time has passed, you may have a large backlog. In that case, trying little nibbles is the only way to go. You could also approach this from the -OFFSITERECLAIMLimit--=--number_of_volumes- side, limiting it to just a few at a time. - Allen S. Rout
Re: reclamation no longer working
Bringing offsite tapes back and reclaiming them onsite is much faster; but, of course, then that data is not offsite. Richard Sims http://people.bu.edu/rbs/ Richard, from time to time I've had to do this. After checking in the tapes and updating them to r/o or r/w TSM doesn't always use them for the source on a 'move data'. Sometimes it does, sometimes it doesn't. It acts as if the tapes are not in the library even after I've verified them. Would you know any reason why? TSM 5.5.3 - LTO4 library. Individuals who have received this information in error or are not authorized to receive it must promptly return or dispose of the information and notify the sender. Those individuals are hereby notified that they are strictly prohibited from reviewing, forwarding, printing, copying, distributing or using this information in any way.
Re: reclamation no longer working
On May 7, 2010, at 2:35 PM, Johnny Lea wrote: Bringing offsite tapes back and reclaiming them onsite is much faster; but, of course, then that data is not offsite. Richard Sims http://people.bu.edu/rbs/ Richard, from time to time I've had to do this. After checking in the tapes and updating them to r/o or r/w TSM doesn't always use them for the source on a 'move data'. Sometimes it does, sometimes it doesn't. It acts as if the tapes are not in the library even after I've verified them. Would you know any reason why? In most of the cases I've examined, it is because the now-onsite tape begins with a segmented Physical File which is continued from a tape which is not available (e.g., marked Offsite), where the reclamation then runs with primary storage pool tapes only as it starts by copying the entirety of that first Physical File - which takes more time. A few cases have remained mysterious. Richard Simsat Boston University
Reducing fragmentation in disk storage pools of type disk.
(TSM Server 5.5.3.0 on Linux 2.6.9-89.0.11.ELsmp x86_64) I'm working with some disk storage pools (type disk) that traditionally have not been migrated to the point of being empty. There have been times recently when we've struggled to get the disk storage pool migrated quickly enough to keep it from filling almost enntirely. We suspect this is leading to the log getting pinned. We've adjusted the hi and lo migration thresholds, and have made some plumbing improvements to speed up migration. As a precaution, we're also migrating the disk storage pool until it is empty. My question is: Once the volumes in the disk storage pool are empty, would it further reduce any chance for fragmentation in the disk storage pool to remove and re-define the disk storage pool volumes? Thanks, [RC] 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. -
