Hi,

I'm with Rui; the current behaviour is as it should be. That doesn't
mean that it couldn't be improved though. We often have filespaces that
are removed from the client. It is possible to empty the filespace on
the client and then perform an incremental backup. Files will then
expire naturally. However we often want to keep the filespaces around
for longer than the default retention, just in case.

It would be nice to be able, from the ADSM server, to notify ADSM that
the filespace isn't coming back, and force it to go through normal
expiration. Effectively this command would just be making all active
files inactive.

Of course this only applies to backups because archives already look
after themselves.

Trevor
------------------------------------------------------------------------
------------------------------------------------
------------------------------------------------
Trevor Foley
Trevor Foley
Bankers Trust Australia Limited
Phone: 61-2-9259 3944    Fax: 61-2-9259 2659


        -----Original Message-----
        From:   Rui Malheiro [SMTP:rmalheiro AT MAIL.TELEPAC DOT PT]
        Sent:   Monday, May 25, 1998 11:08 PM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Re: How do you deal with...?

        Replying to: Bob Matthews <Robert.Matthews AT SEINF.UNIGE DOT CH> (Mon,
25 May 1998
        11:07:07 +0200)

        >>I'm wondering how large shops deal with the problem that when
a filesystem
        >>is deleted from a client, ADSM will not expire backups of
files in that
        >>filesystem.   I had expected that it should treat them just as
deleted
        >>files,  ...
        >
        >I would also expect them to be treated as deleted files. What
is the philosophy behind this anomalous behaviour? Is it documented? I
don't think large shops should have to run around in circles looking for
this situation.
        >

        I don't see it as being anomalous behaviour. I don't want ADSM
to expire
        files if I unmount one filesystem for a couple of days. What
about a
        removable filesystem? It would be the same as expiring a client
files just
        because it's disconnected from the network.

        The point is, ADSM has no way of knowing if the filesystem has
been removed
        or is merely offline. It'll have to be the client to inform ADSM
that the
        filesystem/disk no longer exists.

        However, there could be an (definable) option to "delete" files
in a
        filesystem that doesn't backup for more than a certain number of
days.
        somethig in backup/archive copy groups.

        --
        Rui Malheiro,
        6 Mil - Tecnologias de Informacao
        URL: <http://www.6mil.pt/>