Re: All Local - Deleted Filesystems
1999-07-26 09:41:21
We do pretty much the same thing. We run the ADSM server on VM. We wrote an
exec to check once a month for all filespaces over 100 days old and create a
report that gets sent out. Then we delete them manually.
ADSM-L AT VM.MARIST DOT EDU on 07/22/99 03:47:40 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU @ INTERNET
To: ADSM-L AT VM.MARIST DOT EDU @ INTERNET
cc:
Subject: Re: All Local - Deleted Filesystems
Manually. We do a query of the filespaces about once a quarter for all
those that haven't backed up in over 90 days. Then contact the owner and
delete them manually.
> -----Original Message-----
> From: Mark Owens [SMTP:Mark_Owens AT PRODIGY DOT NET]
> Sent: Thursday, July 22, 1999 2:01 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: All Local - Deleted Filesystems
>
> Server - OS/390 2.1.0.18 (know its not supported... looking at Veritas)
> Clients - AIX 3.1.0.6/7
>
> HI Fellow ADSMers,
>
> We use the domain all-local technique in dsm.opt. Tried the domain
> filespacename
> approach but too many filesystems were being created that we weren't aware
> of , thus they were not being backed-up. My question revolves around
> filesystems
> that are backed-up (using domain all-local) and THEN deleted from the AIX
> client. These filesystems become "stuck" in the DB until the ADSM admin
> deletes them. If you're using all-local, how is everyone else managing
> these
> dead filesystems?
>
>
>
> Tia
>
> Mark Owens
> Prodigy Communications Corporation
|
|
|