****Any *SMers using NT Journal Backups****
**This question is posed to Tivoli Client Development [Andy Raibeck] or
Tivoli Storage Solutions Software Development [Pete Tanenhaus] if
possible!!!!**
----------------------------------------------------------------------------
-----------------------------------------------
-----------------------------------------------
I have read all of the information about Journal Backups in the "Tivoli
I have read all of the information about Journal Backups in the "Tivoli
Storage Manager for Windows Using the Backup-Archive Client" Manual and also
the "4.2.1 READMe for NT" and it seems that there is more information needed
on the behavior of Journal-Based Backups!
I have an NT 4.0 client with TSM 4.2.1.15 (I will soon be upgrading to
4.1.2.20) client installed which it processes approximately 290,000 objects
with about 2,200 (less than 1%) changing on a daily basis.
If the amount of daily change activity is less than 5% is it still
beneficial to use Journal Backups?
When I first upgraded to 4.2.1.15 from 4.1.2.0, I decided not to perform a
Journal backup on this particular client, so I DISABLED the service. On
Tuesday, I started the Journal Service so it could begin its journaling
process and log any changed objects or its attributes in the journal
database. The backup still took 9.5 hours to complete with the same
behavior as without Journaling. So, I continued to let it run the next night
and it still took 9.5 hours as well.
It seems as if the Journal Engine Service is not working properly! I still
see sessions terminating due to the extensive processing/querying that the
producer thread does while in an idlewait status.
An excerpt from the dsmsched.log----->
21:32:08 ANS1898I ***** Processed 73,500 files *****
21:33:00 ANS1898I ***** Processed 74,000 files *****
21:34:06 ANS1898I ***** Processed 74,500 files *****
21:35:24 ANS1898I ***** Processed 75,000 files *****
21:36:28 ANS1898I ***** Processed 75,500 files *****
21:37:33 ANS1898I ***** Processed 76,000 files *****
21:38:41 ANS1898I ***** Processed 76,500 files *****
21:39:48 ANS1898I ***** Processed 77,000 files *****
21:40:57 ANS1898I ***** Processed 77,500 files *****
21:42:21 ANS1898I ***** Processed 78,000 files *****
21:43:45 ANS1898I ***** Processed 78,500 files *****
*************STILL PROCESSING UNTIL********************
23:51:44 ANS1898I ***** Processed 151,500 files *****
00:02:09 ANS1898I ***** Processed 155,000 files *****
00:02:10 ANS1898I ***** Processed 156,500 files *****
00:02:17 ANS1898I ***** Processed 157,000 files *****
00:11:39 ANS1898I ***** Processed 162,000 files *****
00:12:58 ANS1898I ***** Processed 163,000 files *****
00:14:06 ANS1898I ***** Processed 163,500 files *****
00:16:54 ANS1898I ***** Processed 165,000 files *****
00:19:23 ANS1898I ***** Processed 165,500 files *****
00:19:25 ANS1898I ***** Processed 166,500 files *****
00:20:05 ANS1898I ***** Processed 167,000 files *****
00:20:31 ANS1898I ***** Processed 167,500 files *****
Between 21:32:08 and 00:20:31 (almost 3 hrs) is when I see multiple sessions
terminating due to the idlewait time of 60 mins.
Should I increase the IDLEWAIT time to 180 mins. (3 hrs) or will that only
eliminate the multiple sessions timing out or increase the performance of my
backup?
Also, if anyone can explain this message it would be greatly appreciated?
"psFsMonitorThread(tid 1044): Object 'C:\WINNT\Temp\TMP5.tmp' was deleted
after notification."
Thanks,
Demetrius Malbrough
UNIX/TSM Administrator
|
