ADSM-L

Re: Management Classes and Client Nodes

1998-06-12 12:16:14
Subject: Re: Management Classes and Client Nodes
From: Freddy Sjauw-En-Wa <FreddyS AT SEAGATESOFTWARE DOT COM>
Date: Fri, 12 Jun 1998 17:16:14 +0100
What if you create a new domain Called XYZ and move the clients in
there? You can then define any MGMT Class you like with whatever policy
(copies to keep, migration and such).

> -----Original Message-----
> From: Ganesan Ravishanker [SMTP:ravishan AT WESLEYAN DOT EDU]
> Sent: Friday, June 12, 1998 5:01 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Management Classes and Client Nodes
> 
> Hi All
>  
>     I am trying to accomplish the following:
>  
>     o I want to restrict desktops to be able to backup ONLY files in
> d:\backup and its subdirectories and have ONLY two copies of each
> file. I do not want the clients to be able to backup anything else nor
> do I want them to be able to keep more than two copies of a file. I
> would like to control all these at the server end, otherwise
> sophisticated users will modify the files on the client side (dsm.opt
> or dsm.sys) to bypass these restrictions.
>  
>     o So, I defined a management class called DESKTOP  under the
> STANDARD policy domain. This defines two copies of every file as
> opposed to 7 copies defined in the STANDARD management class.
>  
>     o I define a client option set in which has three client options,
> with force set to yes:
>  
>        INCLEXCL,0:   inclexcl exclude ?:\...\*
>        INCLEXCL,1:   inclexcl include d:\backup
>        SUBDIR,0:  yes 
>  
>     and I use this client option set in the client node definition for
> a client ABCD.
>  
>     o I do not see any way I can force the server to use DESKTOP
> management class for client node ABCD. As a result it is still using
> the STANDARD management class.
>  
>     Any help is very much appreciated.
>  
> Ravi
>  
<Prev in Thread] Current Thread [Next in Thread>