Solved

Using existing journal filesystem after TSM Client upgrade

Posted on 2010-08-27
7
1,085 Views
Last Modified: 2013-11-15
We are running TSM client 6.1 on a Windows 2008 64bit server and using the Journal Based Backup feature. Since we first started using JBB we have been having intermittent problems with the TSM Journal service crashing. It's now to the point where the service will crash immediately after it is started even if a backup is not running. While using TSM 6.1 we were able to get about a weeks worth of good Journal Based Backups. However, for the past couple of days since the Journal Service would not stay up, the backup reverted back to taking traditional incremental backups.

We decided to just upgrade the client from 6.1 to 6.2 and the Journal Service appears to be much stable now. Before the upgrade I made sure to keep the journal ini file, all of the journal filesystems, and their respective dbs, however the first run on 6.2 is telling me that the journal will be enabled after the backup completes. I was wondering since the upgrade, does the client have to start the Journal Based Backup over from scratch now.
0
Comment
Question by:abgtemp
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
7 Comments
 
LVL 68

Expert Comment

by:woolmilkporc
ID: 33542072
Hi,
when journaling stops (i.e. tsmjbbd goes offline while the journaled file system stays online) the journal db will by default be invalidated, that's to say it will be considered unusable when journalling comes back online, thus a new classic incremental will be done.
This is to accomodate the fact that any file system change activity which occurs while the journaled file system is offline will not be reflected in the journal database.
You can change this behaviour (but not a posteriori, of course!) by setting
PreserverDBOnExit   1
in the initialization file.
In Unix it's called tsmjbbd.ini. I don't know whether it's the same name on Windows, unfortunately.
wmp
0
 
LVL 68

Expert Comment

by:woolmilkporc
ID: 33542123
Typos, as always -
the parameter is
PreserveDBOnExit   1
and it must read "... which occurs while the journal service is offline ..."
My apologies!
0
 

Author Comment

by:abgtemp
ID: 33543300
Thanks. The file name is also tsmjbbd.ini in Windows also.  The PreserveDBOnExit is set to 1 in our ini file. We made sure to do that when we first setup the client.
0
Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

 
LVL 68

Expert Comment

by:woolmilkporc
ID: 33546291
Anyway, the journal db is unusable, else the client wouldn't tell you that it's going to do a "normal" incremental.

Might be an incompatibility between the journal db formats used by 6.1 resp. 6.2!

I will research a bit. Not sure if there is something to be  found, however ...

wmp
0
 

Author Comment

by:abgtemp
ID: 33547850
Sorry, I may have miscommunicated the normal backup part. The backup reverted back to the normal incremental when it was at version 6.1 after the TSM Journal service failed to start again. I know this is normal when the service does not work. However when I upgraded to 6.2 the backup used the journal service, but just stated that the journal service would not be enabled until after the backup completes. I was trying to figure out if it was trying to run a full backup all over again.
0
 
LVL 68

Accepted Solution

by:
woolmilkporc earned 500 total points
ID: 33549833
A backup will always be non-journalled  with an unusable journal db (for what reasons ever it became unusable). The journal service can only be enabled when this first non-journalled backup has set a definite starting point - a point where all files are backed up which need to, so that only files whose changes got recorded in the journal need to be taken into account in the future, which means that only the journal must be queried, not the files themselves during subsequent backups.
0
 

Author Comment

by:abgtemp
ID: 33554723
Thanks. I reran the backup using version 6.2 and the backup only took as long as a normal incremental and not as long as a full backup from scratch as I had feared. BB was enabled after the completion of the backup. I'm bumping the points up for your quick response to my question also.
0

Featured Post

Edgartown IT Case Study

Learn about Edgartown's quest to ensure the safety and security of the entire town's employee and citizen data. Read the case study!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A quick step-by-step overview of installing and configuring Carbonite Server Backup.
Microsoft will be releasing the Windows 10 Creators Update in just a matter of weeks. Are you prepared? Follow these steps to ensure everything goes smoothly and you don't lose valuable data on your PC.
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…

717 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question