[FF4004] - After Migration from ADSM V2 to ADSM V3 the graphical administration tool dsmadm does not work - only an error message is shown.

ADSM version 3.x, AIX® client

In ADSM V3 no dedicated graphical administration program is included anymore. The newly introduced web interface or the traditional command line interface (command dsmadmc) has to be used for this purpose instead. Since the old program dsmadm is not automatically deleted during migration, it still can be invoked, but this will result in error messages for a version 3 environment.

[FF4005] - After Migration from ADSM V2 to ADSM V3 starting the backup/archive client fails with an error message that an entry in the file dsm.opt is wrong. What can trigger this?

ADSM version 3.x, AIX® client

When ADSM has been migrated from V2 to V3 the former entry NODENAME in file dsm.opt must be changed to VIRTUALNODENAME.

[FF4001] - Our data is not archived by means of the ADSM backup/archive client, but the application passes the data to ADSM by calling the API functions. Since the data in the archive is not displayed when using the ADSM backup/archive client, we cannot retrieve our files in this way. We are using ADSM V2. Is there any way to access this data directly without using the API interface?

ADSM version 2.x

The backup/archive client does not support access to data which has been written to ADSM by means of the API calls. This data can olny be retrieved by using the API interface as well. The only solution is to migrate to ADSM version 3.x.
 

ADSM version 3.1

A new function, called "Interoperability", provides a limited access to API objects from within the backup/archive client (command line only, not from GUI). These commands are supported for that purpose:

• delete archive
• delete filespace
• query
• restore
• retrieve
• set access

Please note that the name of the API object might not be related directly to an existing filesystem or directory name. The application which created the API object could have used own filespace names for this purpose. Since for restore/retrieve of these objects a fully qualified API object name has to be specified, it might be necessary to issue the appropriate query commands first.