4 Upgrading a Standalone Oracle Key Vault Server
This upgrade includes the Oracle Key Vault server software and utilities that control the associated endpoint software
- About Upgrading a Standalone Oracle Key Vault Server
When you upgrade the Oracle Key Vault server software appliance, also upgrade the endpoint software to get access to the latest enhancements. - Step 1: Back Up the Server Before You Upgrade
Before you upgrade the Oracle Key Vault server, perform a one-time backup to a remote destination so that you can recover data in case the upgrade fails. - Step 2: Perform Pre-Upgrade Tasks for the Standalone Oracle Key Vault
To ensure a smooth upgrade to Oracle Key Vault, you should prepare the server you are upgrading. - Step 3: Add Disk Space to Extend the vg_root for the Release 21.2 Upgrade
Before upgrading to Oracle Key Vault release 21.2 from release 18x, you will need to extend thevg_root
to increase disk space. - Step 4: Upgrade the Oracle Key Vault Server
You can upgrade a standalone Oracle Key Vault server deployment. - Step 5: Upgrade the Endpoint Software
As part of the upgrade, you must reenroll endpoints created in earlier releases of Oracle Key Vault, or update the endpoint software. - Step 6: If Necessary, Add Disk Space to Extend Swap Space
If necessary, extend the swap space. Oracle Key Vault release 21.2 requires a hard disk size greater than or equal to 1 TB in size with approximately 64 GB of swap space. - Step 7: If Necessary, Remove Old Kernels
Oracle recommends that you clean up the older kernels that were left behind after the upgrade. - Step 8: If Necessary, Remove SSH-Related DSA Keys
You should remove SSH-related DSA keys left behind after the upgrade, because they can cause problems with some code analysis tools. - Step 9: Back Up the Upgraded Oracle Key Vault Server
You must perform server backup and user password tasks after completing a successful upgrade.
4.1 About Upgrading a Standalone Oracle Key Vault Server
When you upgrade the Oracle Key Vault server software appliance, also upgrade the endpoint software to get access to the latest enhancements.
However, the endpoint software downloaded from the previous Oracle Key Vault release will continue to function with the upgraded Oracle Key Vault server. Be aware that while the old endpoint software will continue to work with the upgraded Oracle Key Vault server, the new endpoint functionality may not work.
You must upgrade in the order shown: first perform a full backup of Oracle Key Vault, upgrade the Oracle Key Vault server, upgrade the endpoint software, and last, perform another full backup of the upgraded server. Note that upgrading requires a restart of the Oracle Key Vault server.
The Oracle Key Vault server is not available to endpoints for a limited duration during the upgrade. You can enable the persistent cache feature to enable endpoints to continue operation during the upgrade process.
Before you begin the upgrade, refer to Oracle Key Vault Release Notes for additional information about performing upgrades.
Parent topic: Upgrading a Standalone Oracle Key Vault Server
4.2 Step 1: Back Up the Server Before You Upgrade
Before you upgrade the Oracle Key Vault server, perform a one-time backup to a remote destination so that you can recover data in case the upgrade fails.
Caution:
Do not bypass this step. Back up the server before you perform the upgrade so that your data is safe and recoverable.
Parent topic: Upgrading a Standalone Oracle Key Vault Server
4.3 Step 2: Perform Pre-Upgrade Tasks for the Standalone Oracle Key Vault
To ensure a smooth upgrade to Oracle Key Vault, you should prepare the server you are upgrading.
4.4 Step 3: Add Disk Space to Extend the vg_root for the Release 21.2 Upgrade
Before upgrading to Oracle Key Vault release 21.2 from release 18x, you will need to extend the vg_root
to increase disk space.
vg_root
, then you can bypass this step.
Related Topics
Parent topic: Upgrading a Standalone Oracle Key Vault Server
4.5 Step 4: Upgrade the Oracle Key Vault Server
You can upgrade a standalone Oracle Key Vault server deployment.
- About Upgrading an Oracle Key Vault Server
In a standalone deployment you must upgrade a single Oracle Key Vault server. - Upgrading a Standalone Oracle Key Vault Server
A single Oracle Key Vault server in a standalone deployment is the most typical deployment in test and development environments.
Parent topic: Upgrading a Standalone Oracle Key Vault Server
4.5.1 About Upgrading an Oracle Key Vault Server
In a standalone deployment you must upgrade a single Oracle Key Vault server.
Note that persistent caching enables endpoints to continue to be operational during the upgrade process.
Note:
If you are upgrading from a system with 4 GB memory, first add an additional 12 GB memory to the system before upgrading.4.6 Step 5: Upgrade the Endpoint Software
As part of the upgrade, you must reenroll endpoints created in earlier releases of Oracle Key Vault, or update the endpoint software.
Related Topics
Parent topic: Upgrading a Standalone Oracle Key Vault Server
4.7 Step 6: If Necessary, Add Disk Space to Extend Swap Space
If necessary, extend the swap space. Oracle Key Vault release 21.2 requires a hard disk size greater than or equal to 1 TB in size with approximately 64 GB of swap space.
swapon -s
command. By default, Oracle Key Vault releases earlier than release 18.1 were installed with approximately 4 GB of swap space. After you complete the upgrade to release 18.1 or later, Oracle recommends that you increase the swap space allocation for the server on which you upgraded Oracle Key Vault. A new Oracle Key Vault installation is automatically configured with sufficient swap space. However, if you upgraded from a previous release, and your system does not have the desired amount of swap space configured, then you must manually add disk space to extend the swap space, particularly if the intention is to convert the upgraded server into the first node of a multi-master cluster.
Parent topic: Upgrading a Standalone Oracle Key Vault Server
4.8 Step 7: If Necessary, Remove Old Kernels
Oracle recommends that you clean up the older kernels that were left behind after the upgrade.
Parent topic: Upgrading a Standalone Oracle Key Vault Server
4.9 Step 8: If Necessary, Remove SSH-Related DSA Keys
You should remove SSH-related DSA keys left behind after the upgrade, because they can cause problems with some code analysis tools.
Parent topic: Upgrading a Standalone Oracle Key Vault Server
4.10 Step 9: Back Up the Upgraded Oracle Key Vault Server
You must perform server backup and user password tasks after completing a successful upgrade.
Parent topic: Upgrading a Standalone Oracle Key Vault Server