Enterprise Workloads Editions: ✅ Business | ✅ Enterprise | ✅ Elite
Edit server name
Edit server name
Log in to the Management Console.
Select the workload from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization and then select the workload.
In the Registered Servers page, select the server whose name you want to edit.
Click More options, and then select Edit Server Name.
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:
Log in to the Management Console.
Select the workload from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization and then select the workload.
In the Registered Servers page, click the server name. This brings up the server details page.
In the server details page, click more options next to Add File Backup Set, and then click Edit Server Name.
In the Edit Server Name dialog box, enter the updated name in the Server Name field, and then click Save.
Upgrade a server
Upgrade a server
You can upgrade the Druva File server agents to the latest versions by downloading the upgraded version from the Druva portal. This topic describes how you can upgrade the Druva 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
If you have installed a hotfix on your existing Druva version, you cannot automatically upgrade to the next version from the Druva portal. You must manually upgrade to the next available version.
If the client machine restarts during the upgrade then you must manually upgrade or rollback the client version.
After triggering the update, if you have any ongoing schedulebackup and restore jobs, they will resume after the upgrade.
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 Enterprise Workloads agent
Log on to Management Console.
Select the workload from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization and then select the workload.
The Registered Servers page displays all the registered servers and the status of their client versions.
Under the Client Version column, you can view the current status for each agent.
Latest: The current version is the latest version that is available.
Not Upgradable: The current version cannot be upgraded to the latest version through the Management Console.
Upgrade Scheduled: There is an upgrade in progress. 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: The current version can be upgraded to the latest available version.
Select one or more agents that you want to upgrade and click Upgrade.
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
Re-Register a server
If you have migrated a registered server to a new server(replacement server), or decommissioned a server in Druva, either as a part of your hardware refresh cycle or for disaster recovery purposes, you can use the Server re-registration option to replace or re-add the existing server with the replacement server in Druva.
Procedure
Log in to the Management Console.
Select File Servers from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization that has the server to be re-registered, and then select the workload.
On the Registered Servers page, click the server that needs to be re-registered to view the server details.
On the server details page, click more options, and then click Re-Register Server.
In the Re-Register Server dialog box, click Proceed.
In the Download and Install Agent on the Server section, click Check Pre-requisite to check the Enterprise Workloads agent prerequisites. In the Select OS dropdown, select the operating system of the server where you will install the Enterprise Workloads 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 Management Console on the destination server.
Click Copy Command to copy the activation command for the replacement server activation.
For Windows Server, perform the following:
Change the directory to:
C:\Program Files\Druva\Phoenix Agent(for agent version prior to 7.0.0)C:\Program Files\Druva\EnterpriseWorkloads(for agent version 7.0.0 and later)
Open Administrative cmd prompt and enter below command:
HybridWorkloadsAgent.exe fs-mssql activate -t <token>(for agent version prior to 7.0.0)EnterpriseWorkloadsAgent.exe fs-mssql activate -t <token>(for agent version 7.0.0 and later)EnterpriseWorkloadsAgent.exe fs activate -t <token>(for agent version 7.0.2-535205 and later)
Here token value will be the one obtained from step 6.
For Linux server, perform the following:
Change the directory to :
cd /opt/Druva/Phoenix/bin(for agent version prior to 7.0.0)cd /opt/Druva/EnterpriseWorkloads/bin(for agent version 7.0.0 and later)
In the terminal, enter the below command:
HybridWorkloadsAgent fs-mssql activate -t <token>(for agent version prior to 7.0.0)EnterpriseWorkloadsAgent.exe fs-mssql activate -t<token> (for agent version 7.0.0 and later)EnterpriseWorkloadsAgent.exe fs activate -t <token>(for agent version 7.0.2-535205 and later)
Here token value will be the one obtained from step 6.
📝 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.
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 system. Details like server name, agent version, platform of the existing server are replaced with the appropriate details of the replacement server.
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 service:
Hybrid Workloads Agent Client Service(for agent version prior to 7.0.0)Druva-EnterpriseWorkloads(for agent version 7.0.0 and later)
Delete the directory.
C:\ProgramData\Phoenix(for agent version prior to 7.0.0)C:\ProgramData\Druva\EnterpriseWorkloads(for agent version 7.0.0 and later)
Uninstall the Enterprise Workloads agent
❗ Important
It is crucial to perform these steps on the original server to avoid any backup failures and conflicts on the new server.
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.
Delete a server
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 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
Log in to the Management Console.
Select the workload from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization and then select the workload.
In the Registered Servers page, select the server that you want to delete.
Click More options, and then select Delete.
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 might take longer to complete a purge operation.
Determine the Enterprise Workloads agent version
Determine the Enterprise Workloads agent version
You can determine the version of the Enterprise Workloads agent that is currently running on your servers. Each Druva release comes with new features and enhancements, and to use these features, you must have the latest version of Enterprise Workloads agent. You can obtain the version details of the Enterprise Workloads agent instances from the Management Console.
Ensure that you have the latest version of the Enterprise Workloads agent installed on your servers.
Procedure
Log on to Management Console.
Select the workload from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization and then select the workload.
The Registered Servers page displays all the registered servers. The Client Version column displays the version of the Enterprise Workloads agent on the server.
Locate the server for which you want to determine the agent version.
View the Enterprise Workloads agent version details that appear in the Client Version column.
View server details page
View server details page
Log on to Management Console.
Select the workload from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization and then select the workload.
In the Registered Servers page, click the server name. The Server details page is displayed.
The following is the list of fields on the Server Details page.
FQDN/Hostname: The fully qualified domain name or hostname of the server.
Connection Status: The current connection status of the server.
Administrative group: The administrative group associated with the server.
OS: The operating system running on the server.
Client Version: Displays version of the Enterprise Workloads agent running on the server.
Configured Backup Sets: The file backup sets associated with the server.
Backup Set: The name of the backup set associated with the server. Click the backup set name for more details.
Backup Content: Hover over the backup content for details on the backup folders included for backup, subfolders excluded from backup, and the included/excluded file types.
Backup Policy: The name of the backup policy. Click the backup policy to view policy details.
Backup Enabled: The status of the backup policy.
Last Backup Status: This indicates the status of the last backup job associated with this backup set, when the job ran, and the job ID.
ActionsThe following is the list of actions on the Server Details page.
Add File Backup Set: Click the button to add a new File backup set to the selected server.
More options next to Add File Backup Set
Edit Server Name: Select this option to edit the server name. For more information, see Edit server name.
Upgrade Client: Select this option to upgrade the Enterprise Workloads agent on the selected server. For more information, see Upgrading the Enterprise Workloads agent.
Re-Register Server: Select this option to re-register the server. For more information, see Server re-registration.
Restore: Select a backup set and then click Restore, to restore data from that backup set. For more information, see Restore a File server to the original server and Restore a File server to an alternate server.
More options next to Restore
Backup Now: Select a backup set, click more options, and then click Backup Now to back up the server manually. For more information, see Manually back up a File server.
Edit: Select a backup set, click more options, and then Edit to edit the backup settings and backup content. For more information, see Edit a backup set.
Enable Backup: Select a backup set, click more options and then click Enable Backup to enable backups for the selected backup set. For more information, see Disable and enable backup of a backup set.
Disable Backup: Select a backup set, click more options and then click Disable Backup to disable backups for the selected backup set. For more information, see Disable and enable backup of a backup set.