Q : What type of pools does ISM support?

            A : ISM ships with the following pools for use in backup and cloning:

• ISMData - This pool Stores backups of your dbspaces when you are using a tape device.
• ISMLogs - This pool stores backups of your logical logs when you are using a tape device.
• ISMDiskData - This pool stores backups of your dbspaces when you are using a file type storage device.
• ISMDiskLogs - This pool stores backups of your logical logs when you are using a file type storage device.
• ISMDataClone - This pool stores clones of your storage dbspace backups.
• ISMLogsClone  - This pool stores clones of your storage logical log backups.

Q: Does ISM support auto rewind tape devices?

A: You MUST use a non rewind tape device because ISM writes a file mark on the storage volume at the end of each backup and then appends data onto the storage volume based on the position of the file mark. If the device rewinds the tape, the position of the file mark is lost and the next backup overwrites previously written data.

Q: Does ISM support Imported Restore?

A: Currently, you cannot perform an imported restore if the target machine name is different from the machine name where the archive backup was taken. This feature will be available in ISM 2.2. See BUG 97957 for reference.

Q: Is it possible for ISM to write to multiple devices in parallel?

A: From the 7.30 release notes SERVER_7.3

       Setting the Number of Devices for Target Sessions
     =======================================================
     Each ISM device has a "target sessions" attribute associated with it.
     This attribute sets the number of save streams that can be managed by the
     device and multiplexed to a volume.
     Consider, for example, two devices belonging to the ISMData pool. New
     devices have a default target sessions value of 4. This means that the
     first four of a set of parallel dbspace backups will go to the first
     device. To allow both devices to operate in parallel during the
     dbspace backup, we need to change the target sessions attribute to 1.
     This will cause each new backup stream to select the device with the
     fewest active streams.
     The value of the target sessions attribute cannot be seen or set by using
     the ISM GUI. This value, for each created device, is set by default to 4
     (and it is stored in the 'nsr.res' file). If this value is undesirable,
     for example in installations with more than one tape drive assigned to
     the ISMData pool, you can change the value by using the "nsradmin" 
     program (either on Unix, or on NT) as in the following sample
     session:

         C:\>nsradmin -s crete
         NetWorker administration program.
         Use the "help" command for help.
         nsradmin> show name; volume id; target sessions
         nsradmin> print name:"D:\optical\1"
         name: "d:\optical\1";
         target sessions: 4;
         volume id: 26407;
         nsradmin> update volume id: 26407; target sessions: 1
         target sessions: 1;
         volume id: 26407;
         Update? y
         updated resource id 87.0.39.1.157.66.235.52.137.69.101.68(27)
         nsradmin> quit

Q : How do I test the version number of an ISM installation?

A : To test the version number of an ISM installation use the following commnad:

        (echo print) | nsradmin -i - | grep Ed

Q : A customer is running IDS 7.30.UC2 on HPUX 10.20 and is getting the following
        errors in the /nsr/logs/daemon.log:
        nsrd: server notice: started.
        nsrck: index for itsflus6.aent.com is created.
        nsrmmdbd: media db is cross cheching the save sets.
        nsrmmdbd: media dbs is open for business.
        nsrindexd: RPC error, unknow host.
        nsrd: unable to start nsrindexd.

 A:  The solution in this particular case was to add the follwing entery in the nsswitch.conf file:
         hosts: files [NOTFOUND=countinue]DNS[NOTFOUND=continue] nis