Using existing journal filesystem after TSM Client upgrade

Posted on 2010-08-27
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.
Question by:abgtemp
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
LVL 68

Expert Comment

ID: 33542072
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.
LVL 68

Expert Comment

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

Author Comment

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.
The Eight Noble Truths of Backup and Recovery

How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.

LVL 68

Expert Comment

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 ...


Author Comment

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.
LVL 68

Accepted Solution

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.

Author Comment

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.

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

Question has a verified solution.

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

Suggested Solutions

How to fix error ""Failed to validate the vCentre certificate. Either install or verify the certificate by using the vSphere Data Protection Configuration utility" when you are trying to connect to VDP instance from Vcenter.
In this article we will learn how to backup a VMware farm using Nakivo Backup & Replication. In this tutorial we will install the software on a Windows 2012 R2 Server.
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…

733 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