Skip to main content
druva_logo.pngDruva
|
Documentation

How can we help you?

 

Trending articles:
Druva Documentation

Manage your server

  1. Last updated
  2. Save as PDF
Phoenix Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite

This topic contains the following sections:

Edit server name

  1. Log in to the Phoenix Management Console.
  2. In the menu bar, click All Organizations, and then select the required organization from the drop-down list.
  3. In the menu bar, click Protect > Windows/Linux Servers.
  4. In the Registered Servers page, select the server whose name you want to edit.
  5. Click More options, and then select Edit Server Name.
  6. In the Edit Server Name dialog box, enter the updated name in the Server Name field, and then click Save.

You can also edit the server name from the server details page. To do so, perform the following tasks:

  1. Log in to the Phoenix Management Console.
  2. In the menu bar, click All Organizations, and then select the required organization from the drop-down list.
  3. In the menu bar, click Protect > Windows/Linux Servers.
  4. In the Registered Servers page, click the server name. This brings up the server details page.
  5. In the server details page, click more options next to Add File Backup Set, and then click Edit Server Name.
  6. In the Edit Server Name dialog box, enter the updated name in the Server Name field, and then click Save.

Upgrade a server

You can upgrade the Druva Phoenix File server agents to the latest versions by downloading the upgraded version from the Druva Phoenix portal. This topic describes how you can upgrade the Druva Phoenix File server agent to the most recent version on a Windows and Linux server.

Note: The Agent Upgrade feature is supported from version 4.5 and above. You must manually upgrade to version 4.5 or above to use this feature.

Limitations 

  1. If you have installed a hotfix on your existing Druva Phoenix version, you cannot automatically upgrade to the next version from the Druva Phoenix portal. You must manually upgrade to the next available version.
  2. If the client machine restarts during the upgrade then you must manually upgrade or rollback the client version.
  3. After triggering the update, if you have any ongoing schedule backup and restore jobs, they will resume after the upgrade.
  4. If the old version is not present on the client machine then upgrade rollback will fail. In this scenario, you must manually upgrade or rollback the client.

To upgrade Phoenix agent 

  1. Log on to Phoenix Management Console. 
  2. On the menu bar, click All Organizations, and select the required organization from the drop-down list.
  3. On the menu bar, click Protect > Windows/Linux Servers.
  4.  The Registered Servers page displays all the registered servers and the status of their client versions.
  5. Under the Client Version column, you can view the current status for each agent. 
     
    Status Icon Description

    Latest

    		 Upgraded.png

    The current version is the latest version that is available.

    Not Upgradable 

    Not upgradeable.png

    The current version cannot be upgraded to the latest version through the Druva Phoenix portal. 

    Upgrade Scheduled

    queued.png

     There is an upgrade in progress.

    Note: Jobs that are in progress at the time of upgrade will restart after the upgrade is complete. Ongoing Backup now jobs will fail after triggering the upgrade.

    Upgradable 

    ready for upgrade.png

    The current version can be upgraded to the latest available version.
  6. Select one or more agents that you want to upgrade and click Upgrade.
  7. On the confirmation dialog box, click Yes.

Note: Automatic rollback for RPM upgrade is supported from version 4.6 and later.

Re-Register a server

If you have migrated a registered server in Druva Phoenix to a new server(replacement server), either as a part of your hardware refresh cycle or for disaster recovery purposes, you can use the Server re-registration option to replace the existing server with the replacement server in Druva Phoenix.

File Server Re-registration

  1. Log in to the Phoenix Management Console.
  2. On the menu bar, click All Organizations, and then select the organization that has the server to be re-registered.
  3. On the menu bar, click Protect > Windows/Linux servers.
  4. On the Registered Servers page, click the server that needs to be re-registered to view the server details.
  5. On the server details page, click more options, and then click Re-Register Server.
  6. In the Re-Register Server dialog box, click Proceed.
  7. In the Download and Install Agent on the Server section, click Check Pre-requisite to check the Phoenix agent prerequisites.  In the Select OS dropdown, select the operating system of the server where you will install the Phoenix agent, and then click Download. The agent download begins on the same browser page. The agent is not downloaded on the destination server unless you click Download through the Phoenix Management Console on the destination server.

    Re-register new server.png
     
  8. Click Copy Command to copy the activation command for the replacement server activation.
    Note: The replacement server must be activated with the activation token generated at this stage. Activating with any other activation token will register the replacement server as a new server with Druva Phoenix.
  9. After the agent is installed on the replacement server and it is activated with the token provided in the Re-Register New Server dialog box, the replacement server assumes the identity of the existing server in the Druva Phoenix system.  Details like server name, agent version, platform of the existing server are replaced with the appropriate details of the replacement server. 
  10. If the original and new server are separate servers (not the same server) and both servers are online, perform the following tasks on the original server: 

    • Stop the Druva Phoenix Service 

    • Delete the  C:\ProgramData\Phoenix directory

    • Uninstall the Phoenix agent 

       It is crucial to perform these steps on the original server to avoid any backup failures and conflicts on the new server.

  11. The restore points(snapshots) from the existing server can be viewed in the restore wizard of the replacement server and restores can be triggered from the restore wizard of the replacement server.

Note: Re-registration does not restore the non-default configuration parameters that might have been configured for the original server. Administrator must freshly configure these parameters after reactivation.

SQL Server Re-registration 

Use the Re-Register SQL Server option to replace a registered SQL server that hosts a standalone SQL instance with a replacement server in the Phoenix Management Console. You can use this option when you need to migrate a registered SQL server to a replacement server as part of a hardware refresh or disaster recovery. 

Note: The Re-Register option is only available for standalone SQL instances currently.

  1.  Log in to the Phoenix Management Console.
  2. On the menu bar, click the drop-down next to All Organizations and select the organization that has your existing MS-SQL server.
  3. On the menu bar, click Protect > MS-SQL Servers.
  4. On the All SQL Resources page, click the standalone instance hosted on the SQL server that needs to be re-registered.
  5. On the resource details page, in the top right corner, click more options, and click Re-Register Server.

    Re-register server.png

  6. In the Re-register Server dialog box, read the message, and click Proceed.

  7. In the Re-register Server dialog box, click Check Prerequisite to ensure that the replacement server meets the hardware and software requirements for the Druva Phoenix SQL agent.

    Re-register server wizard.png

  8. Download the Windows 64-bit SQL agent, and install it on the replacement SQL server. The agent download begins on the same browser page. The agent is not downloaded on the replacement SQL server unless you click Download through the Phoenix Management Console on the replacement SQL server. Install the agent on the SQL server.

  9. In the Re-register Server dialog box, click Copy token to activate the agent via the Phoenix agent installer shortcut on the SQL server.

    Re-register server- Copy token.png
    You can also click Copy Command to activate the Phoenix agent via the command line on the SQL server.

    Re-register server- Copy Command.png

Note: The replacement SQL server must be activated with the activation token generated at this stage. Activating with any other activation token will register the replacement server as a new SQL server in Druva Phoenix.

  1. After the agent is installed on the replacement server and it is activated with the token provided in the Re-Register Server dialog box, the replacement server assumes the identity of the existing server in the Druva Phoenix system.  Details like server name, agent version, platform of the existing SQL server are replaced with the appropriate details of the replacement SQL server. 

  2. If the original and new server are separate servers (not the same server) and both servers are online, perform the following tasks on the original server: 

    1. Stop the Druva Phoenix Service.

    2. Delete the  C:\ProgramData\Phoenix directory.
    3. Uninstall the Phoenix agent

 It is crucial to perform these steps on the original SQL server to avoid any backup failures and conflicts on the new SQL server.

  1. The restore points(snapshots) from the existing SQL server can be viewed in the restore wizard of the replacement SQL server and restores can be triggered from the restore wizard of the SQL replacement server.

Note: Re-registration does not restore the non-default configuration parameters that might have been configured for the original server. The administrator must freshly configure these parameters after reactivation.

Delete a server

Before deleting a server, ensure that you have deleted all of its associated backup sets. You can delete a server only after 7 days of the deletion of the last backup set mapped to the server. After deleting all the backup sets, the configuration status of the server changes to Unconfigured. If you are a cloud administrator, you can delete any server. If you are a group administrator, you can delete a server that belongs to the administrator group that you manage. After you delete a server, Druva Phoenix purges the backup data of that server from the warm storage, thus freeing up space. 

You can delete a server in the following scenarios:

  • You configured servers during evaluation, and you now want to reclaim the storage consumed.
  • You are planning to deprecate servers, and you no longer need to keep data.
  • You are planning to replace servers, and a backup of the replacement servers might consume additional storage for the same data.
  • You no longer want to back up a server.

Procedure

  1. Log in to the Phoenix Management Console.
  2. In the menu bar, click All Organizations, and then select the required organization from the drop-down list.
  3. In the menu bar, click Protect > Windows/Linux Servers.
  4. In the Registered Servers page, select the server that you want to delete.
  5. Click More options, and then select Delete.
  6. On the server details page, click More Actions > Delete.
Note: After deleting a server, the time required for purging data depends on the size of data that was backed up. For large-sized datasets, Druva Phoenix might take longer to complete a purge operation.

Determine the Phoenix agent version

You can determine the version of the Phoenix agent that is currently running on your servers. Each Druva Phoenix release comes with new features and enhancements, and to use these features, you must have the latest version of Phoenix agent. You can obtain the version details of the Phoenix agent instances from the Phoenix Management Console.

Ensure that you have the latest version of the Phoenix agent installed on your servers.

Procedure

  1. Log on to Phoenix Management Console.
  2. On the menu bar, click All Organizations, and select the required organization from the drop-down list.
  3. On the menu bar, click Protect > Windows/Linux Servers.
  4. The Registered Servers page displays all the registered servers. The Client Version column displays the version of the Phoenix agent on the server.
  5. Locate the server for which you want to determine the agent version.
  6. View the Phoenix agent version details that appear in the Client Version column. 

    Client version.png

View server details page

  1. Log on to Phoenix Management Console.
  2. On the menu bar, click All Organizations, and select the required organization from the drop-down list.
  3. On the menu bar, click Protect > Windows/Linux Servers.
  4. In the Registered Servers page, click the server name. The Server details page is displayed.

    Server Details.png

Manage Credentials

  1. Log in to the Phoenix Management Console.
  2. In the menu bar at the top, click All Organizations, and then select your organization.
  3. Click Protect > Windows/Linux servers. 
  4. In the Registered Servers page, select the Windows server or the SQL server whose credentials you want to manage, and then from More Options, select Manage Credentials.
  5. In the Manage Server Credentials dialog box, perform the following tasks:
Field Description

Add Credential

Create a new credential. In the Add Credentials dialog box, enter the following details:

  • Label: Enter a label that uniquely identifies the credential.
  • Username: Enter the username of the credential. If your account uses a domain, enter the username as domain\username — for example, DruvaCorp\jsmith.
  • Password: Enter the password of the credential.
  • Confirm Password: Re-enter the password of the credential.
Assign Assign the selected credential to the server. The selected credential replaces any previously assigned credential.

Unassign

Unassign the selected credential from the server.

Note: Some functions like a client upgrade may not work if the credentials are unassigned from the server.

Related articles