...
New procedure and tools were introduced to support customers with migration of an existing DPOD Store data to a new DPOD installation in each of the scenarios above.
The procedure includes the following main steps :
- Gather needed artifacts from current (migrate from) DPOD installation.
- Install new DPOD "clean" installation.
- Import artifacts to the new DPOD installation.
Pre Requisites
- Both systems (current and new) must be with the same DPOD version, 1.0.6.0 and above.
- Only the Appliances installation (provided as ISO file) is supported for this migration procedure. SHACHAR
Collect Needed Artifacts from Source System
...
example for custom artifacts can be custom key stores used for DPOD SSL client authentication.
| Anchor | ||||
|---|---|---|---|---|
|
Install new System
Install new DPOD installation using version 1.0.2.0 ISO file and apply needed updates (fix) in order for the the current system and the new system to have the same DPOD version.
...
Since DPOD will not be available during the migration process we recommend to disable the monitored device's log targets on the current (old) DPOD installation as describe in "Disable / Enable DPOD's Log Targets".
...
The current transactions data is store in the BigData store located on the OS mount point /data (the configuration data is kept in the internal DB which was recovered in previous steps) .
| Note |
|---|
It is not mandatory to migrate the current transaction data to the new system. Not migrating the transaction data means loosing current transaction data ! |
...
For migrating the current transactions data to the new system please follow the procedure
If you choose NOT to migrate transaction data (only configuration data) skip to "Create Staging Directory"
Exporting The Data LVM Configuration (Volume Group)
...
Verify The Application Is Working Properly
TODO
| Anchor | ||||
|---|---|---|---|---|
|
Create staging directory on the new systemÂ
...