Unable to upgrade desktop laptop agent after upgrade from backup exec to the standalone DLO

[abwi]

Hi,

We just upgraded from backup exec 2010 R3 to the Desktop laptop option V7.

Install went well and everything is working as expected but whentrying to upgrade the agents on the desktops and laptops we have the following issue:

When trying to upgrade the agent the msi of the prievious version is needed to un-install the installed agent.

This msi is no longer present on the server because we un-installed backup exec since we only need the DLO option.

How can we extract this msi (dlo agent) from the installation media?

Is there a way to un-install the agent without need for the original msi used to install the agent? 

[CraigV]

Hi,

Have you tried to mount the ISO on the media server, share the drive and point the installation to this?

Otherwise if you mount the ISO on another machine you would be able to copy the installations off it...

Thanks!

[niss]

Hi,

You don't have to uninstall BE-DLO agent to upgrade it to Symantec DLO 7.0. All you need to do is upgrade the agent by push or pull installation method from the new Symantec DLO 7.0 administration console.

Push Install: From the admin console, tools menu --> Install agents and maintenance servers.

Pull Install : Access DLO agent share from the Symantec DLO 7.0's administration server via UAC path.

Use one of the above upgrade methods. Hope you will succeed.  Please update the result.

[ramcm]

Request you to use the forum https://www-secure.symantec.com/connect/backup-and-recovery/forums/desktop-laptop-option for issues pertaining to DLO.

[CraigV]

...moved to the correct location!

[Brian_Knight]

Has anyone found a way to fix this?  I'm having the same issue with a few agents.  They won't connect to the DLO admin server because it says the agent is disabled.  I can't remove the agent because it is looking for the msi file of the previous version.  Upgrading and running a repair doesn't work either.  Any ideas here would be great.

[ShyamKrishnegow]

We have seen a similar issue when trying to upgrade from one version to another. The observation was that the DLO agent works well on machines where the agent was running when the server upgrade is performed. If the agent is not running, then when it is eventually launched it goes to ‘Disabled’ state.

Two steps could bring the DLO agent back online.

1. Try to upgrade to DLO 7.0 by either push installation or pull installation and then launch the agent.

2. If it is not possible to execute the above step, Exit the agent > Go to the NUDF path of a user whose agent is disabled > Take a backup of the .recovery2 file that is present in .dlo folder > Remove the .recover2 file in .dlo > Launch the agent