Skip to content

KB 00015

The quickstart documentation suggests setting up an Isolated mode installation for quick PoC and Trial testing. Should you want to convert to a system managed Production install mode, RackN recommends you re-install from scratch. However, the below article may help you convert or migrate should you choose to not do a fresh install.


There currently is no officually supported migration tool to move from an Isolated to Production install mode. However, any existing customizations, Machines, Leases, Reservations, Contents, etc. can be moved over from the Isolated install directory structure to a Production install directory, and you should be able to retain your Isolated mode environment.

All customized content is stored in the following default subdirectories as:

  • Isolated: in drp-data/ in the Current Working Directory the installation was performed in
  • Production: in /var/lib/dr-provision

The contents and structure of these locations is the same. Follow the below procedure to safely move from Isolated to Production mode.

  1. backup your current drp-data directory (eg tar -czvf /root/drp-isolated-backup.tgz drp-data/)
  2. pkill dr-provision service
  3. perform fresh install on same host, without the --isolated flag
  4. follow the start up scripts setup - BUT do NOT start the dr-provision service at this point
  5. copy the drp-data/* directories recursively to /var/lib/dr-provision (eg: unalias cp; cp -ra drp-data/* /var/lib/dr-provision/)
  6. make sure your startup scripts are in place for your production mode (eg: /etc/systemd/system/dr-provision.service)
  7. start the new production version with systemctl start dr-provision.service
  8. verify everything is running fine
  9. delete the drp-data directory (suggest retaining the backup copy for later just in case)


As of DRP Version v4.3.0, content writable objects are no longer stored in raw JSON files in these directories. They have been moved to new WAL (write-ahead-log) journalled database objects.


If you install a new version of the Digital Rebar Provision service, you must verify that there are no Content differences between the two versions. Should the dr-provision service fail to start up; it's entirely likely that there may be some content changes that need to be addressed in the JSON/YAML files prior to the new version being started. See the rs_upgrade notes for any version-to-version specific documentation.

Additional Information

Additional resources and information related to this Knowledge Base article.

See Also


v3.x to v4.3.0, but not including v4.3.0


dr-provision, isolated, production, migration, conversion

Revision Information

KB Article     :  kb-00015
initial release:  Wed Jun 10 11:20:19 PDT 2020
updated release:  Wed Jun 10 11:20:19 PDT 2020