|
Re: [ADSM-L] file status by server?
2008-04-28 07:09:19
Bjørn -
I'll presume that when you say "server" you actually mean a TSM client.
This is a situation where you as TSM server administrator are being
called upon to compensate for mismanagement of that computer system,
where they claim to be interested in solving the problem but are
nevertheless consciously destroying logged evidence of what the
system is backing up...which they could readily save and look back on.
As Thomas has posted, you can conduct a gruesome traversal of your
Backups table looking for evidence (see "DEACTIVATE_DATE" in ADSM
QuickFacts), but the client administrator should be doing his job,
which I recommend that you insist upon. Involve your manager if
necessary. In addition to log preservation and research, the client
should do 'dsmc q inclexcl -detail' and 'dsmc q mgm -detail' to
review retention periods, in case values may not be what is expected.
Richard Sims
On Apr 28, 2008, at 6:44 AM, Bjørn Nachtwey wrote:
dear all,
one of my customers has some problems with his server: the machine
loses
data. unfortunately he does not know when it starts.
he thought of lokking at the tsm-logs, but the client logs lasts only
two days, so he cannot says when the first data was deleted by his
machine.
my question:
is there a way to query the TSM-DB when a certain file was marked as
deleted?
How can I query which files belonging to a node are going to get
expired?
|
|
|
