Hi,

I have written a basic GUI java program that lets you crudely specify how
files are created and deleted within a filesystem & set up an imaginary
daily incremental backup.

You can set the retention parameters of the managment class you would like
to expire the data against, and watch entries in a pseudo-database
accumulate, go inactive and get expired.

It would be perfect for the situation you describe to see if you are keeping
enough versions of your data. (With a little added, you could also roughly
predict the impact on DB size and storage space if you take on a particular
backup)


....Now. Here's the catch. At the moment it contains a horrible little error
that I can't track down. It appears to work fine, but after a few operations
my pseudo-database stops behaving properly and I start to get stray entries
laying around. Try as I might, I can't for the life of me work out where its
going wrong.

If anyone Would like a copy and the documentation, and have a bash at
finding out where the problem lies (Once that problem is fixed it will be in
a usable state. All the other functionality is there already) I would be
more than happy to distribute it. I would be more than happy to collaborate
with anyone to help people get up to speed with my terrible oo design....

Matt.

_______________________________
Matthew Warren.          GZPTXW
MatthewJames.Warren AT eds DOT com <mailto:MatthewJames.Warren AT eds DOT com>
EDS Core Infrastructure,
UK Technical Services Group,
Wavendon Tower, Milton Keynes.
_______________________________


> -----Original Message-----
> From: Scott G Davis [mailto:Scott.G.Davis AT ALLTEL DOT COM]
> Sent: 28 August 2001 03:47
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Tivoli Setup
>
>
> I have one Tivoli Server servicing 63 Netware and NT clients.
>  I have a
> two part question-
> 1.   I run backup once a day.  I want to be able to restore
> anything for
> 30days.  After that, keep 30 versions for 120 days.  I do not want to
> get keep anything inactive past 120days.  I was running at NOLIMIT,
> NOLIMIT, 120, and 120.  I was retaining too much data so I
> reduced it to
> 30, 30, 120, 120.  Am I keeping too much still or not enough?
>
> 2.   I am wanting to upgrade my tape technology from DLT to SDLT and I
> am wondering the best way to accomplish this.  Along with
> this I want to
> switch to co-location to speed up restore times on large
> volumes.  I can
> add the drives to the libraries and issue move data commands for one,
> but what else could be done to get the data copied to new tapes and
> colocated at the same time?
>
>
> Thanks,
>
>
> Scott G Davis
> Alltel
>