logpinned / Exchange 2010 TDP for mail 6.1.2 / BAC 6.2.3

[PaulWiley]

We have an Exchange 2010 envrioment in a DAG group. We have had inconsistent backups with TSM, so I started playing around with the backupdag.ps1 script to backup passive database copies. We have been having issues over the weekend where the logs are pinned and we thought it was some heavy hitting SQL databases pinning the logs. Well turned out that the Exchange backups are actually the culprit. INC backups work like a champ, but the full backups run over the weekend and pinn the logs resulting in a reboot to clear things up. Was hoping to find some relief to our problems using the method as described: http://www-01.ibm.com/support/docview.wss?uid=swg21433016 but not the case. Our enviroment has 10 mailbox databases ranging from 100 to 500 GB each for about a total of 1.5TB.

Based on the limited info I posted, not expecting an exact solution, just seeking info to see if anyone else has struggled through a log pinning issue with Exchange 2010 backups.

Thanks,
Paul


tsm: TSM>show logpinned
Dirty page Lsn=5490240.169.1974, Last DB backup Lsn=5490240.199.1625, Transaction table Lsn=5479000.21.3632, Running DB backup Lsn=0.0.0, Log truncation Lsn=5479000.21.3632
Lsn=5479000.21.3632, Owner=DB, Length=64
Type=Update, Flags=C2, Action=SetRange, Page=3305, Tsn=0:1.2757905293, PrevLsn=0.0.0, UndoNextLsn=0.0.0, UpdtLsn=5478993.22.2000 ===> Start=7167, Count=64
(3720) Generating SM Context Report:
(3720) *** no sessions found ***
(160) Generating SM Context Report:
(160) *** no sessions found ***
(3719) Generating SM Context Report:
(3719) Session 2802: Type=Node, Id=EXCHANGE2010
(3719) Platform=TDP MSExchg, NodeId=234, Owner=
(3719) SessType=4, Index=1, TermReason=4
(3719) RecvWaitTime=0.000 (samples=0)
(3719) Backup Objects ( bytes ) Inserted: 14899 ( 49.64670922 )
(3719) Backup Objects ( bytes ) Restored: 0 ( 0.0 )
(3719) Archive Objects ( bytes ) Inserted: 0 ( 0.0 )
(3719) Archive Objects ( bytes ) Retrieved: 0 ( 0.0 )
(3719) Last Verb ( ConfirmResp ), Last Verb State ( Sent )
Session 2802 is assoicated with this transaction.

 

[ad283m]

The log is getting pinned in TSM??

 

[ad283m]

Can you, instead of getting all the databases backed up at the same time, back them up like one by one??

 

[PaulWiley]

I can most certainly try to break it out. So there is a difference between:

tdpexcc backup * full /tsmoptfile=dsm.opt /logfile=excsch.log >> excfull.log

and:

tdpexcc backup DB01 full /tsmoptfile=dsm.opt /logfile=excsch.log >> excfull.log
tdpexcc backup DB02 full /tsmoptfile=dsm.opt /logfile=excsch.log >> excfull.log
tdpexcc backup DB03 full /tsmoptfile=dsm.opt /logfile=excsch.log >> excfull.log
..
..
..
..
?

 

[ad283m]

It can work, however, I suggest that you use diffetent log files for each database (it's easier to handle)

And no there is no difference between them, the * acts as a all purpose character, it means all the databases.

Best Regards and tell us how it worked out