System restoration requires the following six steps.

  1. Re-install Centro software (if needed)
  2. Restore the database.
  3. Restore the Catalog Resources
  4. Restore Job progress and 3D Search DB files
  5. Restore Configuration files
  6. Restore the license file

Install Centro

Re-install Centro from the Centro installation files. It is recommended to install from the same version of Centro in which the back up was taken from.

  • CentroWebApp
    • STOP the webapp as soon as it is installed
  • PipelineHostService
  • PipelineManagerService
    • STOP all the services as soon as they are installed
  • Verify the CentroPool and PipelineHostManager services have the correct “Login as” User assigned

Database Restore

  1. The ActifyDB should already be installed
  2. Restore the database with the following command.
arangorestore --server.database ActifyDB --input-directory "dump"

"C:\Program Files\<ARANGO Version>\usr\bin\arangorestore" --server.database ActifyDB --output-directory "dump"

If the arangod.conf was modified to point to a non-IP address, use additional option below
Insert after the "arangorestore" path
arangodump --server.endpoint tcp:///

Catalog Resources

Restore the backed up files to configured location of the CatalogResources. By default, the files and folders can be found at C:\inetpub\wwwroot\Centro\CatalogResources.

The Path is defined in the C:\inetpub\wwwroot\Centro\Configuration\appSettings.config file

Job Progress and 3D Search DB

Restore the backed up files back to the C:\ProgramData\Actify\Centro7 folder.

Configuration files

Restore the following file;

  • C:\inetpub\wwwroot\Centro\web.config
    Note: Path may be different based on your installation

Restore the following folder;

  • C:\inetpub\wwwroot\Centro\Configuration

Restore up the following folders:

  • C:\Program Files\Actify\Centro\PipelineHostService\Configuration
  • C:\Program Files\Actify\Centro\PipelineManager\Configuration

License file

Restore the backed up license file;



  •  Switch to using the new server by changing;
    • ArangoDB IP address if necessary
    • DNS entry