System Backup

It is recommended to back up SpinFire Manage data on a timely basis in case of system failure.

There are five main areas of backup that are recommended.

  1. Catalog Resources
    For organizations that utilize the Catalog, the files that are uploaded to the Catalog are stored in a folder directory.
  2. Program Data
    SpinFire Manage keeps track of jobs that have been run and their association.
    The 3D Search DB is maintained in this location.
  3. Configuration files
    Backup current configuration files
  4. License file
    Use for the CAD Publishing process
  5. Arango database
    The information stored in the database which is the heart of SpinFire Manage.

In addition make note of the following for your records:

  • Version of SpinFire Manage used. If possible keep the applied installation files in a safe location for quick access in future.

  • Database IP address or hostname.

Stop applications and services

Before proceeding do the following;

  1. Stop the CentroPool application pool in IIS

  2. Stop the Pipeline service

  3. Stop the ArangoDB service

Catalog Resource Backup

Back up the CatalogStorageLocation folder. The default location is C:\inetpub\wwwroot\Centro\CatalogResources.

You may skip this step if this folder points to a network share and the files are already being backed up by IT.

See also Catalog Resource Location in Configuration.

Program Data

Back up the program data folder, which is C:\ProgramData\SpinFire\SpinFire Manage by default.

Configuration files

Back up the following config files and folders:

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

  • C:\inetpub\wwwroot\Centro\Configuration

  • C:\Program Files\SpinFire\SpinFire Manage\PipelineService\Configuration

License file

Save the license file at C:\ProgramData\SpinFire\SpinFire Insight\license.al.

Database Backup

Example:

arangodump --server.database CentroDB --include-system-collections --output-directory "dump"

To execute on Windows:

"C:\Program Files\<ARANGO_Version>\usr\bin\arangodump" --server.database CentroDB --include-system-collections --output-directory "dump"

Note: If arangod.conf was modified to point to a non-IP address, add the optional --server.endpoint option:

--server.endpoint tcp:///SERVERNAME.COMPANY.com:8529
A folder called “dump” is created with the database information in the bin folder. If the folder and file already exists then the command will fail. This is to avoid overwriting previous dump files.
If you’re certain that the file can be overwritten use the following command:
arangodump --server.database CentroDB --include-system-collections --output-directory "dump" --overwrite true

See also arangodump | ArangoDB Documentation