Skip to main content
All CollectionsEnterprise WorkloadsProtect File ServersManage File Servers
Upgrade File server agent on Windows using installer
Upgrade File server agent on Windows using installer
Updated over a week ago

Druva performs the rollover of the PhoenixUpgrade.log file at the beginning of the upgrade operation. From second upgrade onward, the rolled-over PhoenixUpgrade.<date-time>.log file holds the contents of the first upgrade logs and similar successive upgrade operations. You can ignore the first rolled-over PhoenixUpgrade.<date-time>.log file, because it does not contain any upgrade information.

Before you begin

Ensure the following:

  • You are logged on to the server that has an existing installation of Hybrid Workloads agent / Enterprise Workloads agent as an administrator.

  • Your server matches the requirements listed in Prerequisites for File Server.

  • You have downloaded the latest Hybrid Workloads agent / Enterprise Workloads agent installer on your server. The installer is available on the Druva downloads page. You can also download the installer from the Management Console at the time of registering servers.

  • To upgrade a Hybrid Workloads agent / Enterprise Workloads agent manually, it is recommended to install a new version of the Hybrid Workloads agent / Enterprise Workloads agent without uninstalling the existing old agent. This avoids the need for reregistering the agent with Druva because the uninstallation process removes all the logs and the configuration-related information from the server.

To upgrade Hybrid Workloads agent / Enterprise Workloads agent

  1. Double-click the Druva installer.

  2. Click Next.

  3. In the Install location box, type or select the full path to the installation home directory.

  4. Click Install.

  5. After the installation completes, click Finish.


πŸ“ Note
​
​A system reboot is not required after manual or auto upgrade. After an upgrade, Hybrid Workloads agent / Enterprise Workloads agent is activated automatically. You do not require a separate Hybrid Workloads agent / Enterprise Workloads agent activation.


Did this answer your question?