Live-To-Test Synchronization
There are several steps involved in synchronizing a source system to a target system. In most cases, this would be from a live (production) system to a test system. If requested, Stibo Systems can provide a detailed, customer-specific document.
This documentation is considered a billable service, which is not included in the standard support agreement. Please be aware that certain requirements to the STEP setup must be met for Stibo Systems to be able to deliver this service. Please contact your Stibo Systems project manager for more information.
Back up the source system
The database and filesystem must be backed up. This can be done according to the procedures described in the System Maintenance documentation (here) or any other backup procedure currently used by your organization.
Restore the database on the target system
The database must be restored on the target system. The specific approach needed to do this depends on the strategy used to back up the database in question. As per the Backup and Recovery documentation (here), some examples of backup strategies are:
- Oracle Import (import or DataPump import)
- Oracle RMAN restore
- Restore of cold backup
Copy the source configuration to the target server
The target system must be identical to the source system, and therefore, the configuration on the target system must match that of the source – except for those parameters that are server specific.
Patch the target system
Unless the entire directory where STEP is installed has been restored from a backup on the source system, the target system should be patched to the same STEP patch level as the source. For patching the STEP system, please refer to the Patching STEP documentation (here).