Well, actually we wound up figuring it out ourselves. A restore of the afore mentioned volumes (for Solaris installation) did not work due to the packages loaded when initially installing the software.
So, we performed the following actions (and it worked!):
1. Rebuilt OS on system making prerequisite changes to various system files and installing required OS patches.
2. Installed CiscoWorks application from CD. Applied any patches which were on the current production system (in our case it was only IDU 2.0).
3. Stopped CiscoWorks (/etc/init.d/dmgtd -stop)
4. Restored the database backup directories.
* we back up the databases to $NMSROOT/database-backups, so that was restored from tape.
* also restored from tape the $NMSROOT/backup directory to the /tmp volume on the server as there are a few files we needed in there.
5. From the restored backup directory on /tmp, copied ../manifest/cmf/database/ani_DbVersion.txt and cmf_DbVersion.txt files to $NMSROOT/backup/manifest/cmf/database.
6. From the restored backup directory on /tmp, copied ../manifest/rme/database/rme_DbVersion.txt file to $NMSROOT/backup/manifest/rme/database.
7. Looked for the name of the directory with the newest timestamp in the restored $NMSROOT/database-backups directory.
8. Restored the databases using the restorebackup.pl command. We had to force the install, but it worked (see following syntax).
$NMSROOT/bin/perl $NMSROOT/bin/restorebackup.pl -FORCE -d $NMSROOT/database-backups/
9. Examined the backup log file for errors (which there were none). The backup log files can be found in /var/adm/CSCOpx/log/restorebackup.log
10. Restarted CiscoWorks application (/etc/init.d/dmgtd -start)
The nice thing is that all application customizations are restored (login module, installed packages, configuration files for devices, etc).
Let me know if you have any questions concerning this. It was a good 2 day learning lesson, but proved to be very valuable.
