The upgrade from Space platform 15.2 to 16.1 is one of the worst procedures I’ve seen in quite a while. It is complicated because the underlying CentOS is being upgraded at the same time, so I guess that’s part of the reason, but still, it could be a lot slicker and better tested.
In summary, you have to apply a couple of patches, the second of which backs your 15.2 data up somewhere else – ideally over SCP to a remote server. You then shut down your 15.2 VM, install a fresh 16.1 VM with the same IP addresses, and restore the data to it.
Sounds easy, but the 16.1 installation part can generally only be done by the customer’s VMware admin because it needs console access. So you’ve got to rely on them following lots of instructions quite well.
Recently a customer experienced some kind of failure in the restoration part, leaving me with a fresh installed 16.1, but no data. I SSHed on to the VM and could see the standard menu, but wasn’t offered any option to attempt another restore. After digging around for a while, I found you can kick it off again by running:
The restoration process looks like this:
[root@space-00505688180e bin]# pwd /usr/bin [root@space-00505688180e bin]# ./jmp_restore Please enter valid response. The Restore process might take several hours if the overall backup content including database size is in few Giga-Bytes... Restore Junos Space Backup 1> Remote Server 2> USB 3> Local Select option : 1 You have selected [ Remote Server ]. Do you want to Continue? [Y/N] Please enter Remote Server IP: XXX.XXX.XXX.XXX Please enter port number for Remote Server [ XXX.XXX.XXX.XXX ] : 22 Ping Remote Server [ XXX.XXX.XXX.XXX ] on Port number [ 22 ]... Remote Server [ XXX.XXX.XXX.XXX ] is available on Port number [ 22 ] ... Please enter Remote Server [ XXX.XXX.XXX.XXX ] user: root Please enter Remote Server user [ root ] password: Enter the path of the directory containing backup files: /mnt/space-15.2R2.4.tgz Verifying Remote server credentials....! Valid Credentials for [ XXX.XXX.XXX.XXX ] Remote Server...! Checking [ XXX.XXX.XXX.XXX:/mnt/space-15.2R2.4.tgz ] directory...! [ XXX.XXX.XXX.XXX:/mnt/space-15.2R2.4.tgz ] is not exist. Please enter valid response. Enter the path of the directory containing backup files: /mnt [ XXX.XXX.XXX.XXX:/mnt ] exist. Checking 15.2 R2 Backup Files.... Completed finding backup files...! File transfer is going to be started, Please wait.... File transfer completed. Validating MD5 Checksum of Backup file...! Valid MD5sum of backup file. Continuing Restore...! Shutting down services... Stopping WatchDog Services Stopping OpenNMS Services Stopped OpenNMS Services Extracting backup files... Restoring MySQL... Starting MySQL service... Starting MySQL data import.... Restoring pgsql... Starting postgres service... Restoring Application related files to /var/cache/jboss/jmp/payloads/backup/ Restoring Space configuration...... Doing /etc/pki/tls/ca_certs Doing /etc/pki/tls/ca_crls Upgrading Opennms Configuration Directory (/opt/opennms/etc) Starting Service Now Restore... Service Now version 15.1R3.14 Processing AIM-RESTORE.SH - STAGE - 0 Processing AIM-RESTORE.SH - STAGE - 1 Processing AIM-RESTORE.SH - STAGE - 2 Processing AIM-RESTORE.SH - STAGE - 3 Processing AIM-RESTORE.SH - STAGE - 4 Processing AIM-RESTORE-DB.SH - STAGE - 0 Processing AIM-RESTORE-DB.SH - STAGE - 1 Processing AIM-RESTORE-DB.SH - STAGE - 2 Processing AIM-RESTORE-DB.SH - STAGE - 3 Processing AIM-RESTORE-DB.SH - STAGE - 4 ls: cannot access /var/cache/jboss/jmp/payloads/backup/AIM/sn_backup/db-table/logFileData/*.sql: No such file or directory Processing AIM-RESTORE.SH - STAGE - 5 AIM-RESTORE-DATA.sh - Starting Service Now data restore... AIM-RESTORE-DATA.sh - Started to copy... AIM-RESTORE-DATA.sh - Changing permissions... AIM-RESTORE-DATA.sh - Completed Service Now data restore... Successfully completed processing AIM-RESTORE.SH Starting services... Starting Watch-Dog Service... Starting OpenNMS Service Starting Jboss Domain Controller Service Starting Jboss Service Space Upgrade has completed successfully [root@space-00505688180e bin]# [root@space-00505688180e bin]#