replicator: different admin.id for target system?

Howdy Lum Dev Folks,

I'm looking to replicate our production luminis system to a test/dev system. The Lum 4.1 Installation Guide info for the replicator script says you have to have a different admin.id for the target system.

Under Installation Cautions, the document says:
When you install the target Luminis Platform 4 system, you must create an administrative user (using the admin.id property in the custom.conf file) that is different from the administrative user or any other user in use in the source system. This ensures that the data associated with the current administrative user is transferred correctly.

We are using virtual machines and I have been reusing snapshots and templates... I don't want to have to build a new base luminis 4 box for a different admin.id if I don't have to...

Has anyone tried or successfully replicated to a target system that was installed with the same admin.id as the source system?

--Ginny Lee/Colorado School of Mines

Syndicate content