All topics
56 / 60
Adminintermediate

Cloning EBS Environments with RapidClone

Explain the standard process and considerations for cloning an EBS environment using RapidClone

RapidClone copies an EBS environment — usually production to a test instance — so that testing happens against real data and volume.

Cloning an EBS environment is like making a working replica of a factory floor for training purposes — you copy the actual equipment and production line setup (application/database), but critically, you must disconnect it from the real shipping dock and real customer order pipeline (external interfaces) before letting trainees run test batches through it, or you risk shipping fake orders to real customers.

Key Concepts

1
Two stages.
    on the source:  adpreclone.pl on the database tier
                    adpreclone.pl on the application tier
                    -> gathers configuration, prepares templates
2
    on the target:  copy the file systems and the database
                    adcfgclone.pl on each tier
                    -> reconfigures for the new hostnames, ports,
                       and SID
3
adcfgclone is what makes the copy a working environment rather than a copy of production's configuration pointing at production's servers.
adcfgclone
4
The post-clone work is what interviews are actually about, and it is longer than the clone.
5
  - **Change the passwords.** The clone has production's, including
    APPS and every application account.
  - **Repoint or disable RFC-style destinations** and any interface
    that would reach a real external system.
  - **Cancel or disable scheduled concurrent requests.** The clone
    carries production's schedule and will run it.
  - **Reset the Notification Mailer**, or the test system emails real
    customers and suppliers.
  - **Repoint printers.**
  - **Scramble or restrict personal data.**
6
The mailer and the interfaces are the ones that cause incidents. A cloned environment sending real purchase orders to real suppliers, or approval emails to real managers, is a genuine and recurring event — and it happens within minutes of the clone starting, before anyone thinks to check.
7
So the sequence is: clone with the application tier down, do the disabling, then start it.
8
Data protection is not optional. The clone holds real customer and employee records in an environment with looser access and more users. Either mask it or protect it to the same standard as production, because it is the same data.
9
And the practical point. A refresh is routine and its checklist is not. The environment that mailed suppliers is always one where somebody did the clone correctly and skipped the list.
10
What the interviewer is probing.1. "What are the steps in RapidClone?" Probing: the mechanics. Stalls: "Copy the files." Moves up: preclone on source for both tiers, copy the filesystem and database, then postclone configuration on the target.
11
2. "What must be done after cloning production into test?" Probing: the critical part. Stalls: "Nothing." Moves up: scrub it — disable or redirect email, workflow mailer and printing, reset passwords, and cancel scheduled interfaces to real partners.
12
3. "What is the classic incident here?" Probing: experience. Stalls: "None." Moves up: a cloned instance emailing real customers or sending real payment files, because the mailer was left enabled.
13
4. "How do you keep clones repeatable?" Probing: the discipline. Stalls: "Documentation." Moves up: script the post-clone steps so a refresh is one run, not a checklist someone works through from memory at 2am.
Use cases:rapidcloneadprecloneadcfgcloneenvironment-refreshde-identification