Skip to main content


 

 

druva_logo.pngDruva
|
Documentation

How can we help you?

Trending articles:

 

Druva Documentation

MS SQL VM Servers not visible in Phoenix Console

  1. Last updated
  2. Save as PDF
Heads up!

We've transitioned to a new documentation portal to serve you better. Access the latest content by clicking here.

 

Problem description:

Virtual Machine is not visible on the Phoenix Management Console due to the Clone VM.

 

Issue Scenario:

Original VM: Test1

Clone VM: Test2

SQL Instance Training is in Test2 VM.

Windows/Linux Servers: Test1 is available under registered servers

MS-SQL Servers: SQL Instance Training is displayed with server as Test1

Cause:

The original file server machine and the cloned virtual machine coexist in your environment. 

Solution

Original server

  1. Login to original server

  2. Stop the Druva Phoenix Agent Services.

  3. Rename the directory from  C:\ProgramData\Phoenix to C:\ProgramData\Phoenix_old

  4. Start the Druva Phoenix Agent Services.

  5. Open the Druva Client on server desktop

  6. Log in to the Phoenix Management Console.

  7. On the menu bar, click All Organizations, and then select the organization that has the server to be re-registered.

  8. On the menu bar, click Protect > Windows/Linux servers.

  9. On the Registered Servers page, click the server that needs to be re-registered to view the server details.

  10. On the server details page, click more options, and then click Re-Register Server.

  11. In the Re-Register Server dialog box, click Proceed.

  12. Click Copy Command to copy the activation command 

  13. Got to point 5 and paste the activation token 

  14. Server will be re-registered with a new activation token.

 

Clone server

  1. Login to clone server

  2. Stop the Druva Phoenix Agent Services.

  3. Rename the directory from  C:\ProgramData\Phoenix to C:\ProgramData\Phoenix_old

  4. Start the Druva Phoenix Agent Services.

  5. Open the Druva Client on server desktop

  6. Log in to the Phoenix Management Console.

  7. On the menu bar, click All Organizations, and then select the organization that has the server to be re-registered.

  8. On the menu bar, click Protect > Windows/Linux servers.

  9. Click Register New Server.

  10. Proceed to the Activate Server for Backup section.

  11. Under the Activation Token section, if there aren't any existing tokens, a Default Activation Token is generated.  This token is valid for  25 servers and for 7 days.  If this token has expired, click Generate New Token. In the Generate Token dialog box, enter the following details, and then click Generate. 

  12. In the Generate Token window, you can copy the generated token by clicking the Copy Token icon. Click Done. 

  13. Got to point 5 and paste the activation token 

  14. Server will be registered with a new activation token.

  15. Clone Server visible in Phoenix Management Console.