Hi Tom,

If what is missing is just files/directories, AND you run backup against D:
again, ADSM will mark the missing files/directories as EXPIRING and delete
them like you want.

The easiest way to check is to look at your dsmsched.log file, those files
should show up as EXPIRING the next time backup is run.

If the whole drive letter D: is gone, OR you stop running backups against
D:, ADSM will ever mark the files/directories for expiring, and you are
stuck.

Hope this helps..

Wanda

> -----Original Message-----
> From: Kauffman, Tom [SMTP:KauffmanT AT NIBCO DOT COM]
> Sent: Tuesday, February 16, 1999 8:48 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Question on when versions no longer exist
>
> My NT staff is in the process of doing 'server consolidation'; I'm
> wondering
> what that is going to do to my ADSM database. The question becomes one of
> when (or if) ADSM will determine files no longer exist on a server.
> Basically, this is what is going on:
>
> On Server_a a directory path of D:\L\O\N\G\ with about 100 files in
> directory G. On Server_b, they create E:\L\O\ and then move N\G\ from
> Server_a to Server_b. Will ADSM note that the files formerly in G on
> Server_a are no longer there on the next backup? Directories N and G are
> *both* gone from Server_a.
>
> If ADSM does *not* expire the files on Server_a -- how do I do it? I do
> *not* have access to or control of the NT environment; I only have the
> server side of ADSM.
>
> TIA
>
> Tom Kauffman
> kauffmant AT nibco DOT com
>
> Senior Technical Analyst