could be from an operating system major upgrade...

     Could also be if another node with a different operating system or
     different version of an operating system connected as that node (via
     the -node=blah in v2 or the dsm.sys option  "node blah" in v3) and
     performed a backup...

     I've seen behavior such as this when novell clients performed
     operating system version upgrades on their machine that radically
     altered the directory structure... so where there were two "SYS:"
     directories, each were unique and the files backed up from under that
     "drive" wouldn't have the proper information to be restored into the
     "other" SYS: environment

     later,
           DWight


______________________________ Reply Separator _________________________________
Subject: query occupancy odd output
Author:  joelf (joelf AT CAC.WASHINGTON DOT EDU) at unix,mime
Date:    6/25/98 2:15 AM


Why would I see the same file system repeated twice for the same host as
output from a "query occupancy"?

ADSM> query occ rmequip
(header exlcuded)
RMEQUIP           Bkup  /           BACKUPPOOL   453   1,686.56   1,686.02
RMEQUIP           Bkup  /           BACKUPPOOL   786       4.07       3.70
(similar duplication is repeated for other file systems)

Does this occur if do a backup from the baclient and then start doing
backups using the scheduler?  Or is it because some of the backups were done
on ADSM version 3.1.1.1 and the others on 3.1.1.3?

Any thoughts as to why they are treated separately.  I am using the released
policy and management classes.