I have to rebuild a customer's DLO servers. For financial reasons they cannot run two parallel sets of servers at the same time.
Therefore we have to reprovision the old DLO servers and install Windows Server 2012R2 and DLO 7.6 on them. A new installation of DLO will be implemented and the new DLO 7.6 agent will be deployed to the company's endpoints.
My understanding is that this should not be an issue since the DLO agent should continue to backup files locally if the DLO servers are offline. The user should be able to recover files from their computer locally if they need to.
However, in my lab I have noticed that if I shut down the DLO serves the DLO agent seems to hang on the endpoint computer. Is there any way to prevent this from happening.
NB: I have noticed that if I set the DLO agent to work offline while the DLO servers are running there is not problem with the functioning of the DLO agent.
1. Is there any way to get the DLO agent not to crash under this circumstance?
2. Is there anyway to force the DLO agent to work offline?
Are all DLO agents exhibiting this behavior ?
Are these clients "DeDupe" enabled ?
What happens when you set "Work Offline" from the DLO Agent UI and the DLO server is shut down ?
Lastly, is the DUDF enabled ? If yes, is any quota set ?
P.S - There isn't any way to automatically force the DLO Agent to work offline.
Currently this is just in my lab.
How is Work Offline set on the DLP Agent set? Do you know if it is a registry key or a configuration file?
Verbatim from Admin Guide -
To change your connection status
1 Click the connection status on the lower right corner of the Desktop Agent.
2 Do one of the following:
Click Work Offline to place the Desktop Agent in offline mode.
Click Work Online to place the Desktop Agent in online mode.
Alternatively, right-click the DLO Agent from the system tray and choose Work Offline.