Re: TDp and retention settings question
You state Data Protection for SQL is the tdp you are referring to. Data Protection for SQL backups are automatically managed. You do not need to manually manage them. If you run a full backup, it will expire all previous full, log, and differential backups. At that point, according to your settings, RETEXTRA and RETONLY settings will then manage the lifetime of those backups. Are all of the backups FULL backups? Is it possible that you are running some out of band backups, thus creating more than one backup per day on some days? Are any of the backups 30 days? If you cannot figure this one out, open a PMR with IBM support. They can take a close look at your environment and find out what is going on. Thanks, Del ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 04/06/2011 03:59:36 PM: From: js1000 tsm-fo...@backupcentral.com To: ADSM-L@vm.marist.edu Date: 04/06/2011 04:08 PM Subject: TDp and retention settings question Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu 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.
Trying to install lin_tape
Anyone out there solved how to install the lin_tape padckage on redhat enterprise linux 6? Apparently, rebuild is not supported in their implementation of rpm. I've been looking at the rpm man page, but the light hasn't come on yet. Any pointers at this time would be helpful. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
reclamation question
We have three storage pools, the primary pool is a devtype FILE and the two copy pools are devtype LTO3. The offsite copy pools gets transferred offsite via DRM. Whenever I run a reclamation on the offsite copy pool the system grabs a scratch tape and then copies files from the primary pool and starts filling up tapes. I'm perfectly happy with that process. I have an issue when I do the reclamation of onsite tapes. It loads up a tape (might be scratch) and then another tape to copy the data from. It ends up doing a tape to tape copy. In a way it uses twice as many tape mounts as an offsite reclamation. And since I only have 6 drives it kinda cramps up my options sometimes. Is there a way to do a reclamation of the onsite copy pool and have it pull data from the primary pool instead of doing a tape to tape copy? I mean it can do it for the offsite pool, why not the onsite as well? David Tyree Interface Analyst South Georgia Medical Center 229.333.1155 Confidential Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Re: reclamation question
About the only way I can think of to do this is to mark the onsite copy pool volumes as unavailable. This would force data to be pulled from the primary file pool. The reason it does this for the offsite pool, is that offsite volumes are presumed to be unavailable, thus data must be pulled from the primary source. Hope this helps. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tyree, David Sent: Monday, April 11, 2011 12:54 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] reclamation question We have three storage pools, the primary pool is a devtype FILE and the two copy pools are devtype LTO3. The offsite copy pools gets transferred offsite via DRM. Whenever I run a reclamation on the offsite copy pool the system grabs a scratch tape and then copies files from the primary pool and starts filling up tapes. I'm perfectly happy with that process. I have an issue when I do the reclamation of onsite tapes. It loads up a tape (might be scratch) and then another tape to copy the data from. It ends up doing a tape to tape copy. In a way it uses twice as many tape mounts as an offsite reclamation. And since I only have 6 drives it kinda cramps up my options sometimes. Is there a way to do a reclamation of the onsite copy pool and have it pull data from the primary pool instead of doing a tape to tape copy? I mean it can do it for the offsite pool, why not the onsite as well? David Tyree Interface Analyst South Georgia Medical Center 229.333.1155 Confidential Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Re: reclamation question
Or just mark them offsite, even though they are still in the library. You could create a script that does update vol * wherestgpool=onsitecopy access=offsite before you start reclamation, then reverse it when reclamation finishes. W -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lee, Gary D. Sent: Monday, April 11, 2011 1:26 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] reclamation question About the only way I can think of to do this is to mark the onsite copy pool volumes as unavailable. This would force data to be pulled from the primary file pool. The reason it does this for the offsite pool, is that offsite volumes are presumed to be unavailable, thus data must be pulled from the primary source. Hope this helps. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tyree, David Sent: Monday, April 11, 2011 12:54 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] reclamation question We have three storage pools, the primary pool is a devtype FILE and the two copy pools are devtype LTO3. The offsite copy pools gets transferred offsite via DRM. Whenever I run a reclamation on the offsite copy pool the system grabs a scratch tape and then copies files from the primary pool and starts filling up tapes. I'm perfectly happy with that process. I have an issue when I do the reclamation of onsite tapes. It loads up a tape (might be scratch) and then another tape to copy the data from. It ends up doing a tape to tape copy. In a way it uses twice as many tape mounts as an offsite reclamation. And since I only have 6 drives it kinda cramps up my options sometimes. Is there a way to do a reclamation of the onsite copy pool and have it pull data from the primary pool instead of doing a tape to tape copy? I mean it can do it for the offsite pool, why not the onsite as well? David Tyree Interface Analyst South Georgia Medical Center 229.333.1155 Confidential Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Ang: reclamation question
As the previous 2 mentioned, if the tape is available, TSM will use it. If it's offsite, TSM will try to collect the data from primary volumes. So your issue is that the copypool tapes are actually available. It's kinda weird you get them reclaimed though, they should have been moved offsite long before reclaim is needed. Are you storing large database/mail/other application backups on them which expire regularly? Best Regards Daniel Sparrman -ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU skrev: - Till: ADSM-L@VM.MARIST.EDU Från: Tyree, David david.ty...@sgmc.org Sänt av: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Datum: 04/11/2011 18:53 Ärende: reclamation question We have three storage pools, the primary pool is a devtype FILE and the two copy pools are devtype LTO3. The offsite copy pools gets transferred offsite via DRM. Whenever I run a reclamation on the offsite copy pool the system grabs a scratch tape and then copies files from the primary pool and starts filling up tapes. I'm perfectly happy with that process. I have an issue when I do the reclamation of onsite tapes. It loads up a tape (might be scratch) and then another tape to copy the data from. It ends up doing a tape to tape copy. In a way it uses twice as many tape mounts as an offsite reclamation. And since I only have 6 drives it kinda cramps up my options sometimes. Is there a way to do a reclamation of the onsite copy pool and have it pull data from the primary pool instead of doing a tape to tape copy? I mean it can do it for the offsite pool, why not the onsite as well? David Tyree Interface Analyst South Georgia Medical Center 229.333.1155 Confidential Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Ang: Trying to install lin_tape
Which version are you running? You should have full support from 1.49. -ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU skrev: - Till: ADSM-L@VM.MARIST.EDU Från: Lee, Gary D. g...@bsu.edu Sänt av: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Datum: 04/11/2011 18:58 Ärende: Trying to install lin_tape Anyone out there solved how to install the lin_tape padckage on redhat enterprise linux 6? Apparently, rebuild is not supported in their implementation of rpm. I've been looking at the rpm man page, but the light hasn't come on yet. Any pointers at this time would be helpful. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: reclamation question
A more draconian method (not recommended) is to perform a Delete Volume for the copy storage pool volumes you would reclaim, where their former content would be freshly written to tape in the next Backup Stgpool. That leaves you with one less copy of the data, of course, so not the best approach. The reclamation of offsite copy pool tapes can put a drag on your TSM server, as the processing involves inventorying the files on the offsite tape to be reclaimed, then identifying the onsite tapes containing the files, and compile that into a list ordered so as to minimize mounts and repositioning. That can be a lot of database work, which can be observable as reclamation processing seems to pause for a time. Where realistic, I like to bring a batch of offsite tapes back onsite, check them all in at once, then start reclaiming, where the span-from and span-to companion volumes are thus likely to be mountable, preventing the process from having to revert to primary pool tapes for the duration of the volume reclaim because of the spanning. (It continues using the surrogate primary pool volume(s) even after having gotten past a span into the volume being reclaimed, where such processing can result in a bunch of primary pool tape mounts and think time between each, resulting in a reclaim which can run about 8x slower than a straight reclaim.) You can spot check for spanning by performing Query Content Volser F=D Count=1 for a span-into condition, and Query Content Volser F=D Count=-1 for span-out-of. To assess process progress, I employ a macro called 'processes', whose contents are: SELECT Char(PROCESS_NUM,6) as Number, PROCESS as Process , - Left(Char(START_TIME),19) as Start Time , - FILES_PROCESSED as Files , Char(BYTES_PROCESSED,14) as Bytes , - STATUS as StatusFROM PROCESSES This is more useful than Query PRocess in that you can directly see how much data has been checkpoint committed, not just how much has been physically operated upon thus far. Richard Sims http://people.bu.edu/rbs/ADSM.QuickFacts
Re: reclamation question
This is close to what we do, but we add stat=full to narrow it down better. At 01:38 PM 4/11/2011, Prather, Wanda wrote: Or just mark them offsite, even though they are still in the library. You could create a script that does update vol * wherestgpool=onsitecopy access=offsite before you start reclamation, then reverse it when reclamation finishes. W -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lee, Gary D. Sent: Monday, April 11, 2011 1:26 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] reclamation question About the only way I can think of to do this is to mark the onsite copy pool volumes as unavailable. This would force data to be pulled from the primary file pool. The reason it does this for the offsite pool, is that offsite volumes are presumed to be unavailable, thus data must be pulled from the primary source. Hope this helps. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tyree, David Sent: Monday, April 11, 2011 12:54 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] reclamation question We have three storage pools, the primary pool is a devtype FILE and the two copy pools are devtype LTO3. The offsite copy pools gets transferred offsite via DRM. Whenever I run a reclamation on the offsite copy pool the system grabs a scratch tape and then copies files from the primary pool and starts filling up tapes. I'm perfectly happy with that process. I have an issue when I do the reclamation of onsite tapes. It loads up a tape (might be scratch) and then another tape to copy the data from. It ends up doing a tape to tape copy. In a way it uses twice as many tape mounts as an offsite reclamation. And since I only have 6 drives it kinda cramps up my options sometimes. Is there a way to do a reclamation of the onsite copy pool and have it pull data from the primary pool instead of doing a tape to tape copy? I mean it can do it for the offsite pool, why not the onsite as well? David Tyree Interface Analyst South Georgia Medical Center 229.333.1155 Confidential Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: p...@cornell.edu
BACKUP DB DB08C000 lvmread.c(1245): Memory allocation failed: object Resync read page buffer, size 4096
I ran into an odd issue, and it took me a while to figure out the cause. I'm posting this because I found very few hits about lvmread.c, and none matched. Most gave info about memory consumption, which is no factor here. If you have to replace the OS on your TSM server, and you're not using AD, then be sure to re-take ownership of the storage volumes. I didn't notice problems with the FILE class stgpool volumes, but the DBB/DBS volumes, BACKUP DEVCONFIG, PREPARE, etc did fail. This kind of problem is more likely if you lose your user DB, because windows uses machine IDs to generate userIDs, and you don't really get to make your own UIDs. So, if you use AD and lose the user DB, or if you're not using AD and you replace the host but keep the stg drives, then this will be an issue. Here's a sample of the output, with the thread context reports omitted: 2011-04-11 06:00:30 ANR1360I Output volume H:\TIVOLI\TSM\SERVER1\02519629.DBS opened (sequence number 1). (SESSION: 2390, PROCESS: 234) 2011-04-11 06:00:30 ANR0132E lvmread.c(1245): Memory allocation failed: object Resync read page buffer, size 4096. (SESSION: 2390, PROCESS: 234) 2011-04-11 06:00:30 ANRD_1112316882 (iccopy.c:1625) Thread26: Unable to read from db volume. (SESSION: 2390, PROCESS: 234) 2011-04-11 06:00:30 ANRD Thread26 issued message from: (SESSION: 2390, PROCESS: 234) 2011-04-11 06:00:30 ANRD_2749162976 (icback.c:406) Thread26: Backup rc=6. (SESSION: 2390, PROCESS: 234) 2011-04-11 06:00:30 ANRD Thread26 issued message from: (SESSION: 2390, PROCESS: 234) 2011-04-11 06:00:30 ANR4581W Database backup/restore terminated - internal server error detected. (SESSION: 2390, PROCESS: 234) 2011-04-11 06:00:30 ANRD Thread26 issued message 4581 from: (SESSION: 2390, PROCESS: 234) 2011-04-11 06:00:30 ANRD Thread26 DB08C000 Unknown (SESSION: 2390, PROCESS: 234) ... -JD
