Articles in this section

See more

[Guide] Command Server Database Backup / Restore Procedure (for Linux)

Avatar
Jon
  • Updated
Follow

Command Server Database Backup / Restore Procedure (for Linux):

In anticipation of a catastrophic failure, you should always protect your NovaStor DataCenter command server, as this contains the database required to browse and track your backups.

The below instructions are for Linux based Command Server installations, and it assumes the new server that you are intending to make as the new Command Server, that you are recovering to, is also a client of the original Command Server.

 

  1. Ensure that you have the Linux installer for the Command Server portion of the software.  Stop all the services on the new server that we are going to bring up as the new replacement Command Server.
  2. On the new Command Server machine, run the installer for the Command Server portion of the software, keeping all of the defaults.
  3. Stop all of the NovaStor DataCenter services on the new Command Server machine.
  4. Either copy the /opt/NovaStor folder from the original Command Server or directly restore from a backup of the original Command Server (Example of how to do a GUI based direct restore on Windows is located at:  https://support.novastor.com/hc/en-us/articles/360009111954-Restoring-an-unindexed-SV-file-from-a-network-location) or command line direct restore at: https://dcmanual.novastor.com/help-html/dc/en/DirectRestore.html)
  5. On the new Command Server machine, copy all of those files into the \opt\NovaStor folder and overwrite the files and folders except for the /opt/NovaStor/DataCenter/Hiback/disk folder.  This folder contains the configuration for the disk pools, and we want to utilize the ones that are already there on the new / replacement server.
  6. On the new Command Server you will be required to edit the 'hosts' file (in Linux this is normally /etc/hosts) to place the old / previous Command Server's hostname so that it can point to the local host.  Various config files and database will still be referenced as the original Command Server's host name so that is why we need to do this.  An example hosts file entry is here: '127.0.0.1 OldCommandServer.domain.local OldCommandServer'.  Add a new entry to hosts to add an entry like so, of course change it to what your original / old Command Server's hostname was:mceclip1.png
  7. On the new Command Server machine you will need to be able to perform a ping to ping the old server's DNS name.  For example: 'ping OldCommandServer.domain.local' and 'ping OldCommandServer' should both resolve to the localhost at 127.0.0.1 and show a valid ping result.mceclip2.png
  8. On the new Command Server, Start the NovaStor DataCenter services.
  9. Login to the UI via IP address and port:  x.x.x.x:32333
  10. At that point you can restore files as normal that have been backed up.

 

If at this point you want clients to be able to back up to this new Command Server you need to add the IP address from the old Command Server server to the new / replacement Command Server server.

If that is not an option you can edit the central-server.properties file in /opt/NovaStor/DataCenter/conf folder on all of the agents to point to the new Linux Command Server.

Related articles