Re: ISM volume mount problem

Hi, finally I found a solution to make volume writable and usable for the next backups. My way: After the ISM startup I check the volume flags #> ism_show -volumes If there is a "d" flag, the volume is not writable and the volume is "d"efect. This only happens after a system crash or when you kill the ISM while a backup is running. The logical log which should be saved isn't marked as saved. To restore the ISM device I have to rebuild the volume index: #> scanner -iz /informix/baan/logarch - My ISM Device is /informix/baan/logarch... This step takes a while because all save sets on the device where touched and a new index will be build. It finished at corrupt save set and ask for an other device. I think the scanner program assumes that the save set is not complete and it is maybe stored on multiple devices. You can quit now by pressing "q". ( In a script you can simply do -> echo "q" | scanner - iz $DEV ). The index is rebuilt. Now I have to restart the ISM: #> ism_shutdown -q && ism_startup The device is now mounted as restore_only. I can change this by unmounting the device, set the volume to writable and mount the device again. #> ism_op -unmount /informix/baan/logarch #> ism_config -volume ISMLogs -only_restore no #> ism_op -mount /informix/baan/logarch Now I can use the device for backup and recovery again. What do you think about this solution. May I have problems with the scanner program...? Regards, Christian.