For those that are using the Tivoli client for file-level backups on
linux s/390, can anyone comment on their own experiences with Tivoli
client resource requirements? We've recently started backing up a new
file-server. As it was hitting its 430,000th file processed, top was
reporting memory
For those that are using the Tivoli client for file-level backups on
linux s/390, can anyone comment on their own experiences with Tivoli
client resource requirements? We've recently started backing up a new
file-server. As it was hitting its 430,000th file processed, top was
reporting
I've seen that behavior on a system with a lot of open files (it keeps
a
context entry to go back and check later in the run to see if the file
is closed and available), but that doesn't seem to be the case here.
Is
this the first backup of that filesystem on this server? Sometimes the
first
cc:
Sent by: Linux onSubject: Re: [LINUX-390] tivoli
storage manager client?
390 Port
[EMAIL PROTECTED]
IST.EDU
08/19/2004 02:57
PM
But, that said, no, that's not unusual. The TSM client is a pig for
resources.
It'd sure be nice if Tivoli would open-source the TSM client API
libraries...
-- db
--
For LINUX-390 subscribe / signoff / archive access
Guessing (WAG mode): Could this memory growth be caused by maintaining
symlink context?
It strikes me that if there are a lot of symlinks that there'd need to
be
kept a list of where they're pointing so that it could ensure
resolution.
Since I've *NO* knowledge of the internals of TSM (I
