Did you restart the scheduler at the client side after making a
change to the dsm.opt file?

I believe the options files (dsm.sys and dsm.opt) are only read
in when the dsmc process is started. Any changes to the files do
not take effect until the process is restarted.

 -- Tom

"If I could dot the 'i' in a Michigan     Thomas A. La Porte
 game and the good lord came to take me   Archivist, Feature Animation
 the next day ... at least I could        DreamWorks SKG
 die happy." - Beano Cook, ESPN           <tlaporte AT anim.dreamworks DOT com>

On Fri, 11 Apr 1997, Naveed Mustafa wrote:

>Hi there,
>
>I have a question regarding the domain parameter, which contains the
>filesystem names, in the dsm.opt file of the UNIX systems.
>
>Day 1.    I have the following values:
>     Domain        /  /usr  /var  /home  /u01  /u02   /u03   /u04   /u05
>
>     The backup was scheduled to run at 19:00 and went fine.
>
>Day 2.    I updated the domain of the dsm.opt file with the following
>values:
>     Domain        /  /usr  /var  /home  /serv1/app1  /serv2/app2  /serv3/app3
>/serv4/app4
>
>     Again the backup was scheduled to run at 19:00.
>
>The next day (Day 3) when I executed the command "query filespace
>servername",  I get the following results:
>
>Servername          /
>Servername          /usr
>Servername          /var
>Servername          /home
>Servername          /u01
>Servername          /u02
>Servername          /u03
>Servername          /u04
>Servername          /u05
>
>but the new filesystems were never got backed up.  I looked up in the
>dsmsched.log file of the server and evidently the server did not even try
>to backup the new mounted filesystems.
>
>I am running the ADSM version 2.1.0.12 server on AIX 3.2.5 machine.  The
>client is AIX 4.1.4 and is running ADSM version of 2.1.0.6 .
>
>Does any one has any suggestion why the new updated filesystems were never
>got backed up?
>
>Thanks,
>Naveed.
>