The adsm.sys dir contains a copy of your registry. This is not the same as the files going into the SYSTEM OBJECT filespace. These files are needed to maintain a consistent system state. Some info from the help files:
Backing up system objects Certain Windows NT, 2000, and XP system objects can be backed up together or individually. However, Microsoft recommends all system objects be backed up together to maintain a consistent system state. The following are valid system objects: Active Directory (domain controller only) Certificate server database Cluster Database (cluster node only) COM+ database Event logs (system, security and application) Registry System and boot files System volume Removable Storage Management Database (RSM) Replicated file systems (FRS) Windows Management Instrumentation (WMI) To back up system objects using the GUI, select the system objects tree from the backup window. On the command line, use the backup systemobject command to back up all valid system objects. To back up system objects individually, see corresponding commands in Chapter 10, Using commands. For Windows 2000, XP: You can exclude system objects from backup processing using the exclude.systemobject option. See Exclude options for more information. gr. Karel -----Oorspronkelijk bericht----- Van: Fred Johanson [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 25 februari 2003 17:41 Aan: [EMAIL PROTECTED] Onderwerp: Binding SYSTEM OBJECT About half the machines in our central server domain are small and bound to a small server management class by an option set. It looks like 0 include ?:* smallserver 1-37 exclude the usual suspects 38 include c:\adsm.sys\...\* smallserver 39 dirmc smallserver. Sequence #s 0 and 39 do the right thing, but 38 does not, so the SYSTEM OBJECTs go to the default pool instead. What have I missed here? The server is 5.1.1.6 running on AIX.