Answers (hopefully) to your questions: >> I upgraded to 5.3.2.0, disabled the old journal service, created >> specific ones for each drive and installed a journal service for each, >> per your instructions. The services are running and there are journal >> dbs for each drive, but only the c: journal seems to be showing any >> activity, and backups of the other drives don't indicate they are using >> the journal.
The journal has to be valid before the backup will use the journal, and a full incremental backup (one that updates the Last Backup Completion date on the TSM server) must complete while the journal service is running in order for the journal to be marked as valid. You can verify the state of the journal with the dbviewb.exe utility (not shipped with the client, email me directly and I will send to you). >> One part I wasn't sure about was whether I needed to create custom >> dsm.opt files for each journal service, or if I could use multiple >> journalpipe stanzas. The backup client specifies which journal service to connect to by setting the JournalPipe client option to match the JournalPipe setting of the journal service you want to connect to. There should only be one JournalPipe setting per journal service, and each journal service must specify a different config file as explained in my previous note. Each backup client points to the specific journal service to use by specifying a JournalPipe client option which corresponds with the JournalPipe journal config setting of the particular journal service. This can be done either via the command line (dsmc -JournalPipe=) or via separate dsm.opt files. >>Is there a way to verify my install config, like what pipe each service >> is using? Unfortunately, short of turning on client tracing, no. One of the items on our development "to do" list is to implement a "Query Journal" command in the command line client which is capable of displaying the status of the journal service and file systems being journaled. Just our of curiosity, what is your reasoning behind running multiple journal services ? Hope this helps and please don't hesitate to post additional questions. Pete Tanenhaus Tivoli Storage Manager Client Development email: [EMAIL PROTECTED] tieline: 320.8778, external: 607.754.4213 "Those who refuse to challenge authority are condemned to conform to it" ---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on 11/10/2005 07:01 PM --------------------------- Please respond to "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> To: ADSM-L@VM.MARIST.EDU cc: Subject: Re: Fw: Multiple journal services, retry Pete, I upgraded to 5.3.2.0, disabled the old journal service, created specific ones for each drive and installed a journal service for each, per your instructions. The services are running and there are journal dbs for each drive, but only the c: journal seems to be showing any activity, and backups of the other drives don't indicate they are using the journal. One part I wasn't sure about was whether I needed to create custom dsm.opt files for each journal service, or if I could use multiple journalpipe stanzas. Is there a way to verify my install config, like what pipe each service is using? Steve Schaub Systems Engineer, WNI BlueCross BlueShield of Tennessee 423-752-6574 (desk) 423-785-7347 (cell) -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Pete Tanenhaus Sent: Tuesday, November 08, 2005 1:46 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Fw: Multiple journal services, retry I'm not sure if the procedure for installing multiple journal services made it into the client books so I will attempt to explain. The first step is to create a separate journal config file for each journal service which will be installed. Each config file should specify a different JournalPipe value, and should also specify different drives to journal so that the two services don't clash with each other. Note that attempting to have multiple journal services journal the same drive will cause problems since the different services will attempt to write to the same journal db unless this is specifically overridden in the the by specifying different journal dirs in the different config files. The next step is to install journal multiple services under different names. For example: dsmcutil install journal /name:"TSM Journal Service 1" /JBBCONFIGFILE:c:\journalconfig\tsmjbbd1.ini" dsmcutil install journal /name:"TSM Journal Service 2" /JBBCONFIGFILE:c:\journalconfig\tsmjbbd2.ini Backup clients should now be able to connect to the desired journal service by specifying the JournalPipe client option which corresponds with the JournalPipe journal service setting. Hope this helps and please post any additional questions. Regards, Pete Tanenhaus Tivoli Storage Manager Client Development email: [EMAIL PROTECTED] tieline: 320.8778, external: 607.754.4213 "Those who refuse to challenge authority are condemned to conform to it" ---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on 11/08/2005 12:43 PM --------------------------- Please respond to "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> To: ADSM-L@VM.MARIST.EDU cc: Subject: Re: Multiple journal services, retry We are running server 5.2.2.0 and client 5.3.0.5 Is there a doc with detailed instructions on either method? -steve -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Pete Tanenhaus Sent: Tuesday, November 08, 2005 10:02 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Multiple journal services, retry Yes, I've done it (actually I wrote the code to allow doing it). What version of the client are you running ? In client versions prior to 5.32, running multiple services really required installing the two instances of the journal daemon in different directories because I didn't have the foresight to implement a mechanism for allowing each journal service to point to a different config file. In 5.32 a registry setting can added (either manually or via DSMCUTIL) to point a specific instance of a journal service to a particular config (tsmjbbd.ini) file. As you say, the key to running multiple instances of the service is to specifiy a unique pipe name for the journal service via the JournalPipe config setting, and to use the corresponding client option to point the desired journal service. Hope this helps ..... Pete Tanenhaus, TSM Client Develop,emt Tuesday, November 08, 2005 9:48 AM To: ADSM-L@VM.MARIST.EDU cc: From: "Schaub, Steve" <[EMAIL PROTECTED]> Subject: Multiple journal services, retry I didnt see any response, so I'll try again - has anyone successfully installed multiple journal services on a single windows client? Steve Schaub Systems Engineer, WNI BlueCross BlueShield of Tennessee 423-752-6574 (desk) 423-785-7347 (cell) Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
