We are on RSA L&G 7.0 P05 Appliance using RSA supplied db. There is a weekly VM snapshot backup in place. Would like to know what would be the procedure to restore the backed up VM snapshot into a new server (with a different host & IP). The aim is to replicate the same environment on a different server.
Hi Sean, we are using a local db, not a remote db.
Hi Sean, let me make myself clear. We are on the soft appliance with local db. The backed up content is a VM Snapshot of the whole server. Is it possible to restore this Snapshot into a new server.?
Hello Jesvin, Sean,
We are somehow having the same question for which we encountered an issue.
The idea is that we want to change the server where RSA IGL is running, so we are moving the db from one server to another:
1. new server (vm machine) was prepared with SLES 12 SP 2
2. we installed RSA IGL v7.1 and applied patch 04 (to be on same level as old server)
3. on the old server we turned off ACM and exported the database, as instructed in "Database Setup and Management Guide v.7.1" Chapter 3 "Back Up the Customer-Supplied Database"
4. we imported the database export from step 3 to the new server, as instructed in "Database Setup and Management Guide v.7.1" Chapter 3 "Importing AVUSER Schema/Data for a Customer-Supplied Database Restoration/Load"
5. RSA IGL was running on new server after these steps , showing up as "General Node", and the old server was showing as "SON"
6. we turned off all services on both the old and the new servers
7. the system administrators changed the hostname and IP addresses at server and network level (outside RSA IGL) and rebooted the machines
8. after this reboot and IP/hostname changes made by infrastructure team, I wanted to run the "modifyhostname.sh" script to change/update the hostname to the new correct value, on the new machine, but the script is failing (please check attached output file)
9. I have tried manually modifying the listener.ora and tnsnames.ora files with the new hostname but still AVDB service is not working and the db cannot start
Any feedback on how to start the db and change the hostname after such switch is highly appreciated.
Thank you for your time and assistance.
Kind regards,
Razvan
Hi Razvan, the problem is specifically at step 7. The OS Admins should not be changing the IP/hostname of the server manually at all.
You should use the modifyhostname.sh and modifynetworksettings.sh at this point to have the hostname and IP address changed. So I would recommend you first have them revert back any manual changes they did (plus any changes you did to the listener.ora, tnsnames.ora), restart the server, make sure the Oracle database is running again in the settings then use the previous 2 scripts to change the hostname and network settings.
In case you are wondering, the limitations here are from Oracle not our software. A lot of the oracle database components depend on the hostname and IP address and cannot be changed manually or offline. The database needs to be running in order to change those values using those scripts, otherwise the Oracle database will not start.
Thank you for the feedback, Mostafa.
Having a Software Bundle deployment (IGL with RSA provided local database), I was under the impression that all OS related settings (patching, upgrades, scaling etc.) are under the management of the client, and not RSA.
It seems in this particular case that the scripts are not only for the configuration of RSA provided software (application and db server) but also for OS?
Yes exactly. Oracle is very sensitive to hostname changes, which is why we provide the changehostname.sh script. The IP address change can be done manually as long as you remember to change all files (all network files and /etc/hosts … by default the oracle files use hostname not IP address).
The Importing AVUSER Schema/Data for a customer supplied database restoration/load section of the documentation applies here. You arent restoring the database itself but the master key data needs to be restored on the VM so it can properly communicate with the Oracle database.
Unzip the master key data in the master key storage directory.
This is the data that was zipped up in the procedure described in "Export the AVUSER
Schema/Data for an RSA Database Backup." (The master key storage directory is identified by
the rsavialg.security.keydir environment variable. The default directory is /home/oracle/security.)
Note: In a clustered environment, if separate copies of the key data are stored on each cluster
node, then only one copy of a key data (any node's key data) needs to be backed up as all areas
should contain the same key data. However, when reinstalling the data , if a node has a local
directory specified for storage of keys, then the key data should be reinstalled to each of these
local directories (as specified by the rsavialg.security.keydir environment variable which each
node has set).