Dear all,
I have had problems with journaling, so I deleted the journal files, installed
the last supported client version for wk2 server 5.3.4.0.
I always believed that to resume journaling all I had to do was perform an
incremental(complete) backup NOT a
always backup.
However a
He is not, you are.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
william dourado
Sent: woensdag 25 maart 2009 12:23
To: ADSM-L@VM.MARIST.EDU
Subject: Journaling
Dear all,
I have had problems with journaling, so I deleted the journal
Bill,
A successful incremental backup is all that's required to re-engage the
journal engine - although given the nature of systems which tend to use the
Journal Based Backup feature in the first place, this isn't always as quick
or straightforward as one would like.
/David Mc
London, UK
Just to expand on prior responses...
The latest client version for Windows 2000 is 5.3.6.x. Unless 5.3.4.0 was
a typo, I recommend reviewing the following:
http://www.ibm.com/support/docview.wss?uid=swg21286063
http://www.ibm.com/support/docview.wss?uid=swg24019078
Note that 5.3.4 is no longer
Greetings,
We have a Suse 10 Linux client running TSM client 5.4.2.0. It is
also running Samba on one of it's filesystems. When the nightly
incremental runs, it backs up the other filesystems, and then hangs on
the /samba filesystem. It always hangs somewhere around 20,000 files.
We also
Thanks All
Date: Wed, 25 Mar 2009 09:14:02 -0400
From: stor...@us.ibm.com
Subject: Re: [ADSM-L] Journaling
To: ADSM-L@VM.MARIST.EDU
Just to expand on prior responses...
The latest client version for Windows 2000 is 5.3.6.x. Unless 5.3.4.0 was
a typo, I recommend reviewing the
John -
The ANS4008E message is conventionally due to file locking. In a
Samba environment you can use its command 'smbstatus -L' to check on
what locks are in effect, where the DenyMode seems to have more to do
with the locking than what you see in the R/W column - which is to say
that even if
What file system did you use as a base? Reiser or ext3?
Have you tried running a backup with the SAMBA service down? (the whole
filesystem, yea, I know it'll take an outage). That will help you find
out if its SAMBA causing the problem, or if it's just the file system.
And, is this a Novell OES
Hi SQL specialists,
we have found a completely different behaviour when executing TSM SQL
statements on different platforms. The basic idea is to produce SQL
statements as an input for our analysing tool with its own (Orcale)
database. Our select statement (simplyfied example) and output
About 4 years ago some people here decided to bring in Netbackup. No
good reason at the time but everyone involved is making it sound as if
TSM was the problem. In a meeting we had yesterday to discuss moving
everything to TSM they are now making it sound like they can't get rid
of it, no
I'm responding only to the mainframe issue:
-TSM does not understand mainframe legacy filesystems (the legacy
filesystems contain the vast majority of mainframe files in most sites).
-Mainframe backup software does not understand UNIX or Windows filesystems.
So to backup mainframe legacy
To re-establish confidence in the log (so that the client will start
using it again), I tend to stop the scheduler and do a manual
incremental with -incrbydate.
Doing the two problematic filesystems (with 22M objects) in parallel,
and using incrybydate, I can get through the backup in about 3
On Wed, 25 Mar 2009 10:34:11 -0700, Gill, Geoffrey L.
geoffrey.l.g...@saic.com said:
I'd like to ask these questions to the group if you don't mind. Feel
free to add whatever you like if you think there is a better
question I should be asking
'What are your requirements'.
I'm biased, of
Howard,
I will try to find out what kind of filesystem it is; I didn't
set it up, and can't get to it from here (long story).
I had already discussed wanting an outage to try the backup
without samba running, but the customer base is resisting that because
of it being a hospital
On 21/03, Hart, Charles A wrote:
It works well if you understand your data and how you can push to it
with in reason before you deploy another. The IBM product likes more
CPU cores ... Understand these are x86 boxes... We see up to 500MBS
Writes to one of our VTL's that ingests Exchange
15 matches
Mail list logo
