Articles in this section

See more

How to detach a specific server from the system

Avatar
Nx Support
  • Updated
Follow

Detaching a server is the action that can be performed if it is necessary to isolate a server from the current System. Usually, it is because of the maintenance of a specific server or some other field site requirements, but in general, this action is rarely performed.

How to detach a Server from the system

NOTE: Please export the license codes that were activated on the mediaserver you want to detach. This can be done in the License tab of the System Administration menu, with the Export option at the top right.

If you are going to replace the server, deactivate the license keys that were attached to the Server you're going to replace. 

The license keys can be activated to the new system running on the same hardware. Or, in case the hardware was replaced, could be activated on the new hardware if the affected license keys were deactivated prior to detaching it from the System. 

 

Method 1 – Through the WebAdmin: 

  1. Open the WebAdmin Client of the Mediaserver you want to detach
  2. Log in with the admin account
  3. Select the Settings tab and select the applicable Server
  4. Select Detach server from the System, and select Detach
  5. Your Server is detached, and you can either Setup New System or Add to Existing System

Method 2 – By Restoring a Server's Factory Defaults

  1. Log in to Web Admin interface of the server to be detached.
  2. Go to the Settings tab and click Restore Factory Defaults.
  3. Enter the Server password and confirm the action.

Known Limitations

An unexpected event can occur when merging two systems that both had the same resource at one point. A shared resource creates independent transactions on both servers' transaction logs according to how the resource was managed in each server. Certain changes to the resource that were done on one server but not on the other can cause unintended consequences. 

For example, take the scenario of two systems with the same camera (e.g., CamX): System A and System B. 

  1. In System A, an operator enables recording on CamX.
  2. Soon after, the operator deletes CamX from System B.
  3. The operator merges System A and System B together.

The merge will sync transactions from most recent transactions to oldest. Since the transaction in step 2 occurred after step 1, the camera will be deleted from the merged system before it can process the transaction in step 1.

This behavior will be resolved in future versions, but as a workaround for systems with the same resource, you can attempt the following:

  • If not merged yet: Perform a system backup and restore on all servers with the shared resource (this drops potentially unwanted transactions). Afterward, merge as originally intended.
  • Unmerge the systems and make sure all resources and settings are correct. Perform a system backup and restore on all servers with the shared resource. Afterward, merge the servers back together.

Questions

If you have any questions related to this topic, or you want to share your experience with other community members or our team, please visit and engage in our support community or reach out to your local reseller. 

Related articles

Comments

0 comments

Article is closed for comments.