System Restore
System restoration involves the following six steps:
Re-install SpinFire Manage software (if needed)
Restore the database
Restore the Catalog Resources
Restore Program Data
Restore Configuration files
Restore the license file
Switch networking to the new server (if needed)
Install SpinFire Manage
Re-install SpinFire Manage from the SpinFire Manage installation files. It is recommended to install from the same version of SpinFire Manage in which the back up was taken from.
STOP the Web App and Pipeline Service as soon as the installation is finished.
Verify the CentroPool application pool and Pipeline Service have the correct “Login as” User assigned.
Database Restore
The database should already be installed in ArangoDB (CentroDB)
Restore the database with the following command.
Example:
arangorestore --server.database CentroDB --include-system-collections --input-directory "dump" --create-database
To execute on Windows:
"C:\Program Files\<ARANGO_Version>\usr\bin\arangorestore" --server.database CentroDB --include-system-collections --input-directory "dump" --create-database
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
Catalog Resources
Restore the backed up files to configured location of CatalogStorageLocation. The default location is C:\inetpub\wwwroot\Centro\CatalogResources.
See also Catalog Resource Location in Configuration.
Program Data
Restore the backed up files back to the program data folder, which is C:\ProgramData\SpinFire\SpinFire Manage by default.
Configuration files
Restore the following config files and folders:
C:\ProgramData\SpinFire\SpinFire Manage\Configuration
C:\inetpub\wwwroot\Centro\web.configNote: Path may be different based on your installationC:\inetpub\wwwroot\Centro\Configuration
C:\Program Files\SpinFire\SpinFire Manage\PipelineService\Configuration
License file
Restore the backed up license file at C:\\ProgramData\\SpinFire\\SpinFire Insight\\license.al.
Networking
Switch to using the new server by changing;
ArangoDB IP address if necessary
DNS entry