Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code

With Oracle TDP we are able to set the chunk/transaction size. By default it tries to do a whole database as a single transaction. We broke up the problem nodes into 2GB chunks. "Prather, Wanda" wrote: - Data Protection for * products, typically with large transactions that pin the log until

Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code

- Data Protection for * products, typically with large transactions that pin the log until the transaction is committed I'm assuming that a "transaction" for MSSQL = 1 data base when doing the requisite full dump yes? So in the case of ginormous SQL data bases that take hours to back up, what do

Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code

> At what point does the NDMP induced pinning get released? With NDMP, each file system is backed up as an image. Therefore each file system is backed up in its own transaction. The transaction is committed (pin released) when the backup for the file system completes. If the backup does not span

Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code

>>> Andrew Raibeck 5/16/2011 2:04 PM >>> >>Some things that can pin the recovery log: >> >>- NDMP backups that span more than one tape (the pin occurs at the time the >>first tape starts to rewind and another tape is needed) At what point does the NDMP induced pinning get released?

Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code

Wanda, Apologies if this was already mentioned (I haven't read this entire thread), but Expiration can have a dramatic impact when the log is pinned. It does not in itself typically pin the log for long periods of time. However, it can exacerbate the situation where the log is pinned, especia

Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code

Thank you Gentlemen, Much Appreciated! -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Schneider, Jim Sent: Monday, May 16, 2011 1:52 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code Answer to r

Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code

Hi Eric (and others following this thread), Just to clarify: we are not aware of any code defects in the TSM 5.5.5 server that would contribute to recovery log pin situations. Rather, it is likely related to workload. But having said that, we do not dismiss any possibility out of hand. Some thing

Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code

Answer to rookie question: All files backed up create an entry in the transaction log. When the file backup is complete the entry is eligible to be written to the database. TSM only writes the oldest entry in the transaction log. If a file backup takes a long time it can become the oldest entry

Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code

Hi Dave! Thank you VERY VERY much for your help I'm indeed contacted by your colleague, I filled the document and the script is currently collecting data. I'm absolutely willing to do the extra work, if it helps IBM fixing this issue, no problem! Thanks again! Kind regards, Eric van Loon KLM Ro

Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code

Rookie Question, What is Log Pinning? -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Loon, EJ van - SPLXO Sent: Monday, May 16, 2011 10:19 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code Hi Ri

Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code

Hi Richard! > So is 5.5.5.0 also having this issue with the log pinning? Yes. As soon as the log hist 80% TSM starts delaying transactions. In this level a bug was fixed which caused the log to fill too soon after it reached 80%. I'm running 5.5.5.2 and it's still filling to 80% multiple times a ni

Re: Trying to delete a filespace???

Thanks Grigori I was missing a space { NULL\System State }, so the below command worked. Thanks for your advice though. I'll try that next time :-/ Regards Farren delete filespace CHI-AS-SCCMEUR 'CHI-AS-SCCMEUR\SystemState\NULL\System State\SystemState' namet=uni -Original Message---

Re: Trying to delete a filespace???

Try namet=fsid and use filespace ID instead of name. FSID can be taken from "q fi f=d". You will avoid a lot of problems with cpecial characters in filespace name. Grigori G. Solonovitch -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Minns,

Ang: Trying to delete a filespace???

Hi What is the result you're getting from executing the delete filespace command? Are you getting an error? Or are you getting a successful completion state but the filespace is still there? It would be helpful if you also told us the result from executing the command. Have you tried doing "de

Trying to delete a filespace???

Hi all I'm trying to delete the following filespace and having no luck at all. The command I'm using is as below and I'm not getting any joy. Any ideas? Regards Farren delete filespace CHI-AS-SCCMEUR CHI-AS-SCCMEUR\SystemState\NULL\SystemState\SystemState type=any namet=uni Node Name: