Short version:
1. Install the Journal Engine; next backup is a full scan.
2. Stop the Journal Engine for any reason; next backup is a full scan.
3. Journal DB becomes full; next backup is a full scan.
4. Nothing bad happens all day; next backup is a Journal backup.
The servers we use the Journal service on also happen to be scheduled
for regular (weekly, monthly) reboots, but if they were not on a
schedule we would stop and start the Journal service on a regular basis.
Andy Huebner
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Mochnaczewski
Sent: Wednesday, May 07, 2008 1:36 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Journal Engine install on Windows
IBM states that once you install journal based backups that they are NOT
meant to replace incremental backups. They recommend running a regular
old fashioned incremental to make sure all files are backed up on a
regular basis ( once a week or once every tow weeks ). Journal based
backups are not perfect. If the service goes down on the client or the
client reboots ( because that NEVER happens in the Windows ) , and you
didn't put the service to auto start or if it doesn't start for whatever
reason, TSM will default to running an incremental to save you, so that
long backup time for that night will come back for that backup session.
Also if TSM detects that the service went down for a short while during
the day, then this essentially will have corrupted the flatfile backup
list because TSM will not know if any files were updated during that
outage . What happens when the next backup runs ? It will not be a
journal based backup, but a typical incremental will run.
Rich
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
James Choate
Sent: Wednesday, May 07, 2008 2:15 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Journal Engine install on Windows
Very cool..................
I can't believe the difference it makes.
>From 4 hours to 8 minutes. Unbeleiveable.........
When are they coming out with one for Linux? I see only AIX & Windows
available.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Kelly Lipp
Sent: Wednesday, May 07, 2008 12:11 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Journal Engine install on Windows
No, you are good to go. What that statement assumes is that you
installed the Journal Engine before you ever ran the backup and that you
shouldn't be surprised to see a longer than normal backup take place.
Cool, huh? Those guys at IBM...
Kelly Lipp
CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777
www.storserver.com
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
James Choate
Sent: Wednesday, May 07, 2008 12:08 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Journal Engine install on Windows
I installed the backup archive client (5.4.2.0) on Windows 2003 Server.
I ran a full backup of 2.7 TB.
I scheduled the regular incremental backups to run nightly. I noticed
that the backup was taking anywhere from 4 - 9 hours to complete. The
client was scanning thru approximately 5 million files to backup 40GB -
150GB a night.
I installed the Journal engine on the Windows server, and now I notice
that I'm spending 8 minutes - 30 minutes a night to backup the client.
I ran across a couple posts that say the following:
"you'll need a full backup after the journal engine starts"
What does that mean based on me having installed the journal engine
after I had already done a full backup? Does that mean I need to delete
my filespaces, and do a brand new full incremental?
If anyone can clairify this for me I would greatly appreciate it.
Thanks,
James Choate
Standard Life : 175 ans au coeur de nos vies
Standard Life: Part of our lives for 175 years
This e-mail (including any attachments) is confidential and may be legally
privileged. If you are not an intended recipient or an authorized
representative of an intended recipient, you are prohibited from using, copying
or distributing the information in this e-mail or its attachments. If you have
received this e-mail in error, please notify the sender immediately by return
e-mail and delete all copies of this message and any attachments.
Thank you.
|
