ISM restore problem

Posted in 2016

HANS KAMANN — Tue, 02 Aug 2016 05:09:27 — source: IIUG Forums & Mailing Lists

I copied a large backup ( 1.3TB) to another server ( into /backup/Sicherung/B_DATA ) and followed the guidelines in ISM Admin's Guide and Backup and Restore. I created links with this litte script: ls /backup/Sicherung/B_DATA/1 > /tmp/myfiles.txt while read p; do ln -s /backup/Sicherung/B_DATA/1/$p /backup/ism_data/1/$p echo $p sleep 1 done </tmp/myfiles.txt Problem is, when running "ism_catalog -recreate_from /backup/ism_data/1" this appears to be never finished. I have the same "scanner: the following save sets continue on another volume:" message over and over. What's wrong here ? Some output: scanner: ssid 1456340636: 365 MB (of 2000 MB, 1 file(s)) written scanner: ssid 1456340663: continued scanner: ssid 1456340663: 2000 MB, 1 file(s) scanner: ssid 1456340738: continued scanner: ssid 1456340738: 2000 MB, 1 file(s) scanner: ssid 1456341111: continued scanner: ssid 1456341111: 503 MB (of 2000 MB, 1 file(s)) written scanner: ssid 1456341163: continued scanner: ssid 1456341163: 2000 MB, 1 file(s) scanner: ssid 1456341198: continued scanner: ssid 1456341198: 2000 MB, 1 file(s) scanner: ssid 1456341232: continued scanner: ssid 1456341232: 2000 MB, 1 file(s) scanner: ssid 1456341241: continued scanner: ssid 1456341241: 2000 MB, 1 file(s) scanner: ssid 1456341246: continued scanner: ssid 1456341246: 1806 MB (of 2000 MB, 1 file(s)) written scanner: done with file disk DATA_20160725_220654 scanner: the following save sets continue on another volume: dbx00013.tue <1>INFORMIX:/ol_dbx00013/rootdbs/0 7/25/16 22:08 f 2048000096 1 1456340505 E dbx00013.tue <4>INFORMIX:/ol_dbx00013/rootdbs/0 7/25/16 22:08 f 2048000096 1 1456340509 E dbx00013.tue <19>INFORMIX:/ol_dbx00013/rootdbs/0 7/25/16 22:08 f 2048000096 1 1456340529 E dbx00013.tue <30>INFORMIX:/ol_dbx00013/rootdbs/0 7/25/16 22:08 f 2048000096 1 1456340544 E dbx00013.tue <43>INFORMIX:/ol_dbx00013/rootdbs/0 7/25/16 22:08 f 2048000096 1 1456340560 E dbx00013.tue <104>INFORMIX:/ol_dbx00013/rootdbs/0 7/25/16 22:09 f 2048000096 1 1456340636 E dbx00013.tue <127>INFORMIX:/ol_dbx00013/rootdbs/0 7/25/16 22:10 f 2048000096 1 1456340663 E dbx00013.tue <191>INFORMIX:/ol_dbx00013/rootdbs/0 7/25/16 22:11 f 2048000096 1 1456340738 E dbx00013.tue <37>INFORMIX:/ol_dbx00013/rootdbs/0 7/26/16 3:47 f 2048000096 1 1456341111 E dbx00013.tue <83>INFORMIX:/ol_dbx00013/rootdbs/0 7/26/16 3:48 f 2048000096 1 1456341163 E dbx00013.tue <114>INFORMIX:/ol_dbx00013/rootdbs/0 7/26/16 3:49 f 2048000096 1 1456341198 E dbx00013.tue <3>INFORMIX:/ol_dbx00013/rootdbs/0 7/26/16 5:21 f 2048000096 1 1456341232 E dbx00013.tue <11>INFORMIX:/ol_dbx00013/rootdbs/0 7/26/16 5:21 f 2048000096 1 1456341241 E dbx00013.tue <14>INFORMIX:/ol_dbx00013/rootdbs/0 7/26/16 5:21 f 2048000096 1 1456341246 E scanner: when next volume is ready, enter device name (or `q' to quit) [/backup/ism_data/1]? ### insgesamt 40 drwxrwx--- 4 informix informix 4096 29. Jul 10:25 .. -rw------- 1 root root 47 29. Jul 10:28 .nsr lrwxrwxrwx 1 root root 39 1. Aug 14:16 1456340503.0 -> /backup/Sicherung/B_DATA/1/1456340503.0 lrwxrwxrwx 1 root root 39 1. Aug 14:16 1456340504.0 -> /backup/Sicherung/B_DATA/1/1456340504.0 lrwxrwxrwx 1 root root 39 1. Aug 14:16 1456340505.0 -> /backup/Sicherung/B_DATA/1/1456340505.0 lrwxrwxrwx 1 root root 39 1. Aug 14:16 1456340506.0 -> /backup/Sicherung/B_DATA/1/1456340506.0 lrwxrwxrwx 1 root root 39 1. Aug 14:16 1456340508.0 -> /backup/Sicherung/B_DATA/1/1456340508.0 lrwxrwxrwx 1 root root 39 1. Aug 14:16 1456340509.0 -> /backup/Sicherung/B_DATA/1/1456340509.0 lrwxrwxrwx 1 root root 39 1. Aug 14:16 1456340510.0 -> /backup/Sicherung/B_DATA/1/1456340510.0 lrwxrwxrwx 1 root root 39 1. Aug 14:16 1456340511.0 -> /backup/Sicherung/B_DATA/1/1456340511.0 lrwxrwxrwx 1 root root 39 1. Aug 14:16 1456340513.0 -> /backup/Sicherung/B_DATA/1/1456340513.0 lrwxrwxrwx 1 root root 39 1. Aug 14:16 1456340514.0 -> /backup/Sicherung/B_DATA/1/1456340514.0 lrwxrwxrwx 1 root root 39 1. Aug 14:16 1456340516.0 -> /backup/Sicherung/B_DATA/1/1456340516.0 lrwxrwxrwx 1 root root 39 1. Aug 14:16 1456340517.0 -> /backup/Sicherung/B_DATA/1/1456340517.0 lrwxrwxrwx 1 root root 39 1. Aug 14:16 1456340519.0 -> /backup/Sicherung/B_DATA/1/1456340519.0 lrwxrwxrwx 1 root root 39 1. Aug 14:16 1456340520.0 -> /backup/Sicherung/B_DATA/1/1456340520.0 lrwxrwxrwx 1 root root 39 1. Aug 14:16 1456340521.0 -> /backup/Sicherung/B_DATA/1/1456340521.0 lrwxrwxrwx 1 root root 39 1. Aug 14:16 1456340522.0 -> /backup/Sicherung/B_DATA/1/1456340522.0 lrwxrwxrwx 1 root root 39 1. Aug 14:16 1456340524.0 -> /backup/Sicherung/B_DATA/1/1456340524.0 .. dbx00013.tue <14>INFORMIX:/ol_dbx00013/rootdbs/0 7/26/16 5:21 f 2048000096 1 1456341246 E scanner: when next volume is ready, enter device name (or `q' to quit) [/backup/ism_data/1]? scanner: starting file number (or `q' to quit) [0]? scanner: starting record number (or `q' to quit) [1]? scanner: continuing scan with disk on device `/backup/ism_data/1' scanner: scanning file disk DATA_20160725_220654 on /backup/ism_data/1 scanner: file disk DATA_20160725_220654 already exists in the media index scanner: ssid 1456340506: continued on ssid 1456340508 scanner: ssid 1456340506: 1806 MB (of 2000 MB, 1 file(s)) written scanner: ssid 1456340508: continued on ssid 1456340509 scanner: ssid 1456340508: 2000 MB, 1 file(s)

↪ replying to HANS KAMANN

HANS KAMANN — Wed, 07 Sep 2016 06:21:24 — source: IIUG Forums & Mailing Lists

It appears that ism /onbar are not able to restore a recent backup from another machine this way. The new machine, not member of any domain, was not able to restore from a backup of about 620 files and a size of 1.2TB