ADSM-L

[no subject]

2000-05-15 09:11:12
From: Cody Cauchi <cody AT UWINDSOR DOT CA>
Date: Mon, 15 May 2000 09:11:12 -0400
     Hi Jack. I have tried the same test as you mentioned below. I received
the same results with the GUI, but not with the command line interface
using the -pick -inactive options. The only difference between our setup
and yours is as follows :

     ADSM Server Level        : ADSM 3.1 level 2.20
     AIX ADSM Server OS Level      : 4.3.3
     Policy                   : Keep max 3 inactive versions for a max 21
days each.
                                Keep last inactive version for 60 days.

     I am not sure if these factors altering my results. I know this is not
much, but maybe it will give you and idea or two.

RE: ---------->

Date:    Fri, 12 May 2000 11:20:43 -0400
From:    Jack Palmadesso <Jack.Palmadesso AT SWPC.SIEMENS DOT COM>
Subject: Possible problem with TSM BA client for windows?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Smart People,

This one is really getting me can anybody confirm this?  I am currently
testing
the new BA client for NT version 3 release 7 1.0.1.  Running ADSM 3.1 level
2.50
on AIX 4.3.2.

Policy in ADSM is set to keep 2 deleted versions and 7 active.  Using the
TSM BA
client I back up a dir and then restore it has no problems.  I back up the
dir
again delete the files in the dir from the client run another incremental
and
the report at the end of the backup says x files have been marked inactive.
This all looks good also.

At this point the file I am trying to restore only exists on the ADSM
server.
When I bring up the TSM client to restore the file with gui or command line
it
reports that no files exist!!   Also tried backing up a file renaming the
file
backing it up again.  This should mark the file inactive and back up the
new one
right.  The client reports that the file is marked inactive but when I try
to
restore the file ADSM says nothing exists!! WTF!!

Yes the show inactive files switch is on.

Performing the same steps with the IBM ADSM client using the same policy
has no
problems and works as expected.  All deleted versions show up.  Can
somebody
explain or confirm.  This is a really scary situtation.

Please respond to my e-mail as well as the list.

Thanks

Jack
<Prev in Thread] Current Thread [Next in Thread>
  • [no subject], Cody Cauchi <=